treewide: find and fix typos

docs/manual/hacking/getting-started.md

@@ -4,12 +4,12 @@ You, naturally, would like to start by forking the repository to get started. If
 you are new to Git and GitHub, do have a look at GitHub's
 [Fork a repo guide](https://help.github.com/articles/fork-a-repo/) for
 instructions on how you can do this. Once you have a fork of **nvf**, you should
-create a separate branch based on the msot recent `main` branch. Give your
+create a separate branch based on the most recent `main` branch. Give your
 branch a reasonably descriptive name (e.g. `feature/debugger` or
 `fix/pesky-bug`) and you are ready to work on your changes
 
 Implement your changes and commit them to the newly created branch and when you
-are happy with the result, and positive that it fullfills our
+are happy with the result, and positive that it fulfills our
 [Contributing Guidelines](#sec-guidelines), push the branch to GitHub and
 [create a pull request](https://help.github.com/articles/creating-a-pull-request).
 The default pull request template available on the **nvf** repository will guide

docs/manual/hacking/guidelines.md

@@ -93,10 +93,10 @@ the commit followed by the description:
 ```
 languages/ruby: init module
 
-Adds a language module for Ruby, adds appropriate formatters and Treesitter grammers
+Adds a language module for Ruby, adds appropriate formatters and Treesitter grammars
 ```
 
-Long description can be ommitted if the change is too simple to warrant it. A
+Long description can be omitted if the change is too simple to warrant it. A
 minor fix in spelling or a formatting change does not warrant long description,
 however, a module addition or removal does as you would like to provide the
 relevant context, i.e. the reasoning behind it, for your commit.

docs/manual/hacking/testing.md

@@ -1,13 +1,13 @@
 # Testing Changes {#sec-testing-changes}
 
-Once you have made your changes, you will need to test them throughly. If it is
+Once you have made your changes, you will need to test them thoroughly. If it is
 a module, add your module option to `configuration.nix` (located in the root of
 this project) inside `neovimConfiguration`. Enable it, and then run the maximal
 configuration with `nix run .#maximal -Lv` to check for build errors. If neovim
 opens in the current directory without any error messages (you can check the
 output of `:messages` inside neovim to see if there are any errors), then your
 changes are good to go. Open your pull request, and it will be reviewed as soon
-as posssible.
+as possible.
 
 If it is not a new module, but a change to an existing one, then make sure the
 module you have changed is enabled in the maximal configuration by editing

docs/manual/quirks/nodejs.md

@@ -11,7 +11,7 @@ your formatting according to its own config (usually `.eslintrc.js`).
 
 The issue there is your formatting is made via prettierd.
 
-This results in auto-formating relying on your prettier config, while your
+This results in auto-formatting relying on your prettier config, while your
 eslint config diagnoses formatting
 [which it's not supposed to](https://prettier.io/docs/en/comparison.html))
 

docs/release-notes/rl-0.3.md

@@ -21,7 +21,7 @@ soon.
 
 - which-key section titles have been fixed. This is to be changed once again in
   a possible keybind rewrite, but now it should display the correct titles
-  instad of `+prefix`
+  instead of `+prefix`
 
 - Most of `presence.nvim`'s options have been made fully configurable through
   your configuration file.

docs/release-notes/rl-0.5.md

@@ -61,9 +61,9 @@ Release notes for release 0.5
 - LSP navigation helper with nvim-navbuddy, depends on nvim-navic (automatically
   enabled if navic is enabled)
 
-- Addeed nvim-navic integration for catppuccin theme
+- Added nvim-navic integration for Catppuccin theme
 
-- Fixed mismatching zig language description
+- Fixed mismatching Zig language description
 
 - Added support for `statix` and `deadnix` through
   [](#opt-vim.languages.nix.extraDiagnostics.types)
@@ -79,9 +79,9 @@ Release notes for release 0.5
 
 - Added bash LSP and formatter support
 
-- Disabled Lualine LSP status indicator for toggleterm buffer
+- Disabled Lualine LSP status indicator for Toggleterm buffer
 
-- Added `nvim-docs-view`, a plugin to display lsp hover documentation in a side
+- Added `nvim-docs-view`, a plugin to display LSP hover documentation in a side
   panel
 
 - Switched to `nixosOptionsDoc` in option documentation. To quote home-manager
@@ -107,7 +107,7 @@ Release notes for release 0.5
 
 - Removed redundant "Enable ..." in `mkEnableOption` descriptions
 
-- Add options to modify LSP key bindings and add proper whichkey descriptions
+- Add options to modify LSP key bindings and add proper which-key descriptions
 
 - Changed type of `statusline.lualine.activeSection` and
   `statusline.lualine.inactiveSection` from `attrsOf str` to

docs/release-notes/rl-0.7.md

@@ -301,7 +301,7 @@ To migrate to `nixfmt`, simply change `vim.languages.nix.format.type` to
 [Soliprem](https://github.com/Soliprem):
 
 - Add LSP and Treesitter support for R under `vim.languages.R`.
-  - Add formatter suppoort for R, with styler and formatR as options
+  - Add formatter support for R, with styler and formatR as options
 - Add Otter support under `vim.lsp.otter` and an assert to prevent conflict with
   ccc
 - Fixed typo in Otter's setupOpts