Skip to content

Commit c0fda99

Browse files
author
Ted Leahy
committed
Fix README.md grammar and typos (nvim-lua#1291)
1 parent 176ec3e commit c0fda99

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ If you are experiencing issues, please make sure you have the latest versions.
2424
External Requirements:
2525
- Basic utils: `git`, `make`, `unzip`, C Compiler (`gcc`)
2626
- [ripgrep](https://github.com/BurntSushi/ripgrep#installation)
27-
- Clipboard tool (xclip/xsel/win32yank or other depending on platform)
27+
- Clipboard tool (xclip/xsel/win32yank or other depending on the platform)
2828
- A [Nerd Font](https://www.nerdfonts.com/): optional, provides various icons
2929
- if you have it set `vim.g.have_nerd_font` in `init.lua` to true
3030
- Language Setup:
@@ -56,12 +56,12 @@ so that you have your own copy that you can modify, then install by cloning the
5656
fork to your machine using one of the commands below, depending on your OS.
5757

5858
> **NOTE**
59-
> Your fork's url will be something like this:
59+
> Your fork's URL will be something like this:
6060
> `https://github.com/<your_github_username>/kickstart.nvim.git`
6161
6262
You likely want to remove `lazy-lock.json` from your fork's `.gitignore` file
6363
too - it's ignored in the kickstart repo to make maintenance easier, but it's
64-
[recommmended to track it in version control](https://lazy.folke.io/usage/lockfile).
64+
[recommended to track it in version control](https://lazy.folke.io/usage/lockfile).
6565

6666
#### Clone kickstart.nvim
6767
> **NOTE**
@@ -101,7 +101,7 @@ nvim
101101
```
102102

103103
That's it! Lazy will install all the plugins you have. Use `:Lazy` to view
104-
current plugin status. Hit `q` to close the window.
104+
the current plugin status. Hit `q` to close the window.
105105

106106
Read through the `init.lua` file in your configuration folder for more
107107
information about extending and exploring Neovim. That also includes
@@ -114,9 +114,9 @@ examples of adding popularly requested plugins.
114114

115115
### FAQ
116116

117-
* What should I do if I already have a pre-existing neovim configuration?
117+
* What should I do if I already have a pre-existing Neovim configuration?
118118
* You should back it up and then delete all associated files.
119-
* This includes your existing init.lua and the neovim files in `~/.local`
119+
* This includes your existing init.lua and the Neovim files in `~/.local`
120120
which can be deleted with `rm -rf ~/.local/share/nvim/`
121121
* Can I keep my existing configuration in parallel to kickstart?
122122
* Yes! You can use [NVIM_APPNAME](https://neovim.io/doc/user/starting.html#%24NVIM_APPNAME)`=nvim-NAME`
@@ -174,7 +174,7 @@ run in cmd as **admin**:
174174
winget install --accept-source-agreements chocolatey.chocolatey
175175
```
176176

177-
2. install all requirements using choco, exit previous cmd and
177+
2. install all requirements using choco, exit the previous cmd and
178178
open a new one so that choco path is set, and run in cmd as **admin**:
179179
```
180180
choco install -y neovim git ripgrep wget fd unzip gzip mingw make

0 commit comments

Comments
 (0)