fix: typos (#82)

* docs(gotests): update and fix

* fix(health): typos

* docs(impl): update and fix typos

* docs(config): typos

* docs(iferr): update

* typos

* docs(struct_tags): update

* docs: fix typos

* docs: Capitalization

* docgen

CONTRIBUTING.md

···
 ```bash
 sudo pacman -S selene stylua
 # or whatever is your package manager
-# or way of installing pkgs
 ```
 
 For formatting use this following commands, or setup your editor to integrate with selene/stylua:
···
 ```
 
 ### Commit messages
+
 We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), please follow it.
 
 ### Testing
···
 
 You can run tests with:
 ```bash
-task test
-# also there are some aliases for that
 task tests
-task spec
 ```

README.md

···
 }
 ```
 
-## Configuratoin
+## Configuration
 
 > [!IMPORTANT]
 >

doc/gopher.nvim.txt

···
   Setup....................................................|gopher.nvim-setup|
   Install dependencies..............................|gopher.nvim-install-deps|
   Configuration...........................................|gopher.nvim-config|
-  Modifty struct tags................................|gopher.nvim-struct-tags|
+  Modify struct tags.................................|gopher.nvim-struct-tags|
   Auto implementation of interface methods..................|gopher.nvim-impl|
   Generating unit tests boilerplate......................|gopher.nvim-gotests|
   Iferr....................................................|gopher.nvim-iferr|
···
 ------------------------------------------------------------------------------
                                                              *gopher.nvim-setup*
                          `gopher.setup`({user_config})
-Setup function. This method simply merges default configs with opts table.
+Setup function. This method simply merges default config with opts table.
 You can read more about configuration at |gopher.nvim-config|
 Calling this function is optional, if you ok with default settings. Look |gopher.nvim.config-defaults|
 
···
                                                       *gopher.nvim-install-deps*
                              `gopher.install_deps`
 Gopher.nvim implements most of its features using third-party tools.
-To  install these tools, you can run `:GoInstallDeps` command
-or call `require("gopher").install_deps()` if you want ues lua api.
+To install these tools, you can run `:GoInstallDeps` command
+or call `require("gopher").install_deps()` if you want to use lua api.
 
 
 ==============================================================================
···
   local default_config = {
     --minidoc_replace_end
 
-    -- log level, you might consider using DEBUG or TRACE for degugging the plugin
+    -- log level, you might consider using DEBUG or TRACE for debugging the plugin
     ---@type number
     log_level = vim.log.levels.INFO,
 
···
                                                        *gopher.nvim-struct-tags*
 struct-tags is utilizing the `gomodifytags` tool to add or remove tags to struct fields.
 Usage ~
-- put your coursor on the struct
-- run `:GoTagAdd json` to add json tags to struct fields
-- run `:GoTagRm json` to remove json tags to struct fields
+
+How to add/remove tags to struct fields:
 
-note: if you dont spesify the tag it will use `json` as default
+------------------------------------------------------------------------------
+2. Run `:GoTagAdd json` to add json tags to struct fields
+3. Run `:GoTagRm json` to remove json tags to struct fields
 
-simple example:
+NOTE: if you dont specify the tag it will use `json` as default
+
+Example:
 >go
    // before
    type User struct {
···
 impl is utilizing the `impl` tool to generate method stubs for interfaces.
 Usage ~
 
-1. put your coursor on the struct on which you want implement the interface
-   and run `:GoImpl io.Reader`
-   which will automatically choose the reciver for the methods and
-   implement the `io.Reader` interface
-2. same as previous but with custom receiver, so put your coursor on the struct
-   run `:GoImpl w io.Writer`
-   where `w` is the receiver and `io.Writer` is the interface
-3. specift receiver, struct, and interface
-   there's no need to put your coursor on the struct if you specify all arguments
-   `:GoImpl r RequestReader io.Reader`
-   where `r` is the receiver, `RequestReader` is the struct and `io.Reader` is the interface
+1. Automatically implement an interface for a struct:
+   - Place your cursor on the struct where you want to implement the interface.
+   - Run `:GoImpl io.Reader`
+   - This will automatically determine the receiver and implement the `io.Reader` interface.
+
+2. Specify a custom receiver:
+   - Place your cursor on the struct
+   - Run `:GoImpl w io.Writer`, where:
+     - `w` is the receiver.
+     - `io.Writer` is the interface to implement.
+
+3. Explicitly specify the receiver, struct, and interface:
+   - No need to place the cursor on the struct if all arguments are provided.
+   - Run `:GoImpl r RequestReader io.Reader`, where:
+     - `r` is the receiver.
+     - `RequestReader` is the struct.
+     - `io.Reader` is the interface to implement.
 
-simple example:
+Example:
 >go
    type BytesReader struct{}
    //    ^ put your cursor here
···
 
    // this is what you will get
    func (b *BytesReader) Read(p []byte) (n int, err error) {
-   	panic("not implemented") // TODO: Implement
+       panic("not implemented") // TODO: Implement
    }
 <
 
···
 gotests is utilizing the `gotests` tool to generate unit tests boilerplate.
 Usage ~
 
-- generate unit test for spesisfic function/method
-  - to specift the function/method put your cursor on it
-  - run `:GoTestAdd`
+- Generate unit test for specific function/method:
+  1. Place your cursor on the desired function/method.
+  2. Run `:GoTestAdd`
 
-- generate unit tests for all functions/methods in current file
+- Generate unit tests for *all* functions/methods in current file:
   - run `:GoTestsAll`
 
-- generate unit tests only for exported(public) functions/methods
+- Generate unit tests *only* for *exported(public)* functions/methods:
   - run `:GoTestsExp`
 
-you can also specify the template to use for generating the tests. see |gopher.nvim-config|
-more details about templates can be found at: https://github.com/cweill/gotests
+You can also specify the template to use for generating the tests. See |gopher.nvim-config|
+More details about templates can be found at: https://github.com/cweill/gotests
 
 ------------------------------------------------------------------------------
                                                      *gopher.nvim-gotests-named*
 
-if you prefare using named tests, you can enable it in the config.
-but you would need to install `gotests@develop` because stable version doesn't support this feature.
-you can do it with:
+You can enable named tests in the config if you prefer using named tests.
+But you must install `gotests@develop` because the stable version doesn't support this feature.
+
 >lua
   -- simply run go get in your shell:
   go install github.com/cweill/gotests/...@develop
 
   -- if you want to install it within neovim, you can use one of this:
+  -- if you choose to install gotests this way i reocmmend adding it to your `build` section in your |lazy.nvim|
 
   vim.fn.jobstart("go install github.com/cweill/gotests/...@develop")
 
···
   }
 <
 
-if you choose to install `gotests` within neovim, i recommend adding it to your `build` section in your |lazy.nvim|
-
-
 ==============================================================================
 ------------------------------------------------------------------------------
                                                              *gopher.nvim-iferr*
-if you're using `iferr` tool, this module provides a way to automatically insert `if err != nil` check.
+If you're using `iferr` tool, this module provides a way to automatically insert `if err != nil` check.
 Usage ~
-execute `:GoIfErr` near any err variable to insert the check
+Execute `:GoIfErr` near any `err` variable to insert the check
 
 
 ==============================================================================

lua/gopher/config.lua

···
 local default_config = {
   --minidoc_replace_end
 
-  -- log level, you might consider using DEBUG or TRACE for degugging the plugin
+  -- log level, you might consider using DEBUG or TRACE for debugging the plugin
   ---@type number
   log_level = vim.log.levels.INFO,
 
···
 ---@private
 local _config = default_config
 
--- I am kinda secret so don't tell anyone about me
--- even dont use me
+-- I am kinda secret so don't tell anyone about me even dont use me
 --
--- if you don't belive me that i am secret see
+-- if you don't believe me that i am secret see
 -- the line below it says @private
 ---@private
 _config.___plugin_name = "gopher.nvim" ---@diagnostic disable-line: inject-field

lua/gopher/gotests.lua

···
 ---@tag gopher.nvim-gotests
 ---@text gotests is utilizing the `gotests` tool to generate unit tests boilerplate.
 ---@usage
---- - generate unit test for spesisfic function/method
----   - to specift the function/method put your cursor on it
----   - run `:GoTestAdd`
+--- - Generate unit test for specific function/method:
+---   1. Place your cursor on the desired function/method.
+---   2. Run `:GoTestAdd`
 ---
---- - generate unit tests for all functions/methods in current file
+--- - Generate unit tests for *all* functions/methods in current file:
 ---   - run `:GoTestsAll`
 ---
---- - generate unit tests only for exported(public) functions/methods
+--- - Generate unit tests *only* for *exported(public)* functions/methods:
 ---   - run `:GoTestsExp`
 ---
---- you can also specify the template to use for generating the tests. see |gopher.nvim-config|
---- more details about templates can be found at: https://github.com/cweill/gotests
+--- You can also specify the template to use for generating the tests. See |gopher.nvim-config|
+--- More details about templates can be found at: https://github.com/cweill/gotests
 ---
 
 ---@tag gopher.nvim-gotests-named
 ---@text
---- if you prefare using named tests, you can enable it in the config.
---- but you would need to install `gotests@develop` because stable version doesn't support this feature.
---- you can do it with:
+--- You can enable named tests in the config if you prefer using named tests.
+--- But you must install `gotests@develop` because the stable version doesn't support this feature.
+---
 --- >lua
 ---   -- simply run go get in your shell:
 ---   go install github.com/cweill/gotests/...@develop
 ---
 ---   -- if you want to install it within neovim, you can use one of this:
+---   -- if you choose to install gotests this way i reocmmend adding it to your `build` section in your |lazy.nvim|
 ---
 ---   vim.fn.jobstart("go install github.com/cweill/gotests/...@develop")
 ---
···
 ---     }
 ---   }
 --- <
----
---- if you choose to install `gotests` within neovim, i recommend adding it to your `build` section in your |lazy.nvim|
 
 local c = require "gopher.config"
 local ts_utils = require "gopher._utils.ts"

lua/gopher/health.lua

···
 local deps = {
   plugin = {
     { lib = "dap", msg = "required for `gopher.dap`", optional = true },
-    { lib = "plenary", msg = "required for everyting in gopher.nvim", optional = false },
-    { lib = "nvim-treesitter", msg = "required for everyting in gopher.nvim", optional = false },
+    { lib = "plenary", msg = "required for everything in gopher.nvim", optional = false },
+    { lib = "nvim-treesitter", msg = "required for everything in gopher.nvim", optional = false },
   },
   bin = {
     {

lua/gopher/iferr.lua

···
 ---@toc_entry Iferr
 ---@tag gopher.nvim-iferr
----@text if you're using `iferr` tool, this module provides a way to automatically insert `if err != nil` check.
----@usage execute `:GoIfErr` near any err variable to insert the check
+---@text If you're using `iferr` tool, this module provides a way to automatically insert `if err != nil` check.
+---@usage Execute `:GoIfErr` near any `err` variable to insert the check
 
 local c = require "gopher.config"
 local log = require "gopher._utils.log"

lua/gopher/impl.lua

···
 ---@tag gopher.nvim-impl
 ---@text impl is utilizing the `impl` tool to generate method stubs for interfaces.
 ---@usage
---- 1. put your coursor on the struct on which you want implement the interface
----    and run `:GoImpl io.Reader`
----    which will automatically choose the reciver for the methods and
----    implement the `io.Reader` interface
---- 2. same as previous but with custom receiver, so put your coursor on the struct
----    run `:GoImpl w io.Writer`
----    where `w` is the receiver and `io.Writer` is the interface
---- 3. specift receiver, struct, and interface
----    there's no need to put your coursor on the struct if you specify all arguments
----    `:GoImpl r RequestReader io.Reader`
----    where `r` is the receiver, `RequestReader` is the struct and `io.Reader` is the interface
+--- 1. Automatically implement an interface for a struct:
+---    - Place your cursor on the struct where you want to implement the interface.
+---    - Run `:GoImpl io.Reader`
+---    - This will automatically determine the receiver and implement the `io.Reader` interface.
 ---
---- simple example:
+--- 2. Specify a custom receiver:
+---    - Place your cursor on the struct
+---    - Run `:GoImpl w io.Writer`, where:
+---      - `w` is the receiver.
+---      - `io.Writer` is the interface to implement.
+---
+--- 3. Explicitly specify the receiver, struct, and interface:
+---    - No need to place the cursor on the struct if all arguments are provided.
+---    - Run `:GoImpl r RequestReader io.Reader`, where:
+---      - `r` is the receiver.
+---      - `RequestReader` is the struct.
+---      - `io.Reader` is the interface to implement.
+---
+--- Example:
 --- >go
 ---    type BytesReader struct{}
 ---    //    ^ put your cursor here
···
 ---
 ---    // this is what you will get
 ---    func (b *BytesReader) Read(p []byte) (n int, err error) {
----    	panic("not implemented") // TODO: Implement
+---        panic("not implemented") // TODO: Implement
 ---    }
 --- <
 

lua/gopher/init.lua

···
 
 ---@toc_entry Setup
 ---@tag gopher.nvim-setup
----@text Setup function. This method simply merges default configs with opts table.
+---@text Setup function. This method simply merges default config with opts table.
 --- You can read more about configuration at |gopher.nvim-config|
 --- Calling this function is optional, if you ok with default settings. Look |gopher.nvim.config-defaults|
 ---
···
 ---@toc_entry Install dependencies
 ---@tag gopher.nvim-install-deps
 ---@text Gopher.nvim implements most of its features using third-party tools.
---- To  install these tools, you can run `:GoInstallDeps` command
---- or call `require("gopher").install_deps()` if you want ues lua api.
+--- To install these tools, you can run `:GoInstallDeps` command
+--- or call `require("gopher").install_deps()` if you want to use lua api.
 gopher.install_deps = require("gopher.installer").install_deps
 
 gopher.impl = require("gopher.impl").impl

lua/gopher/struct_tags.lua

···
----@toc_entry Modifty struct tags
+---@toc_entry Modify struct tags
 ---@tag gopher.nvim-struct-tags
 ---@text struct-tags is utilizing the `gomodifytags` tool to add or remove tags to struct fields.
----@usage - put your coursor on the struct
---- - run `:GoTagAdd json` to add json tags to struct fields
---- - run `:GoTagRm json` to remove json tags to struct fields
+---@usage
+--- How to add/remove tags to struct fields:
+--  1. Place cursor on the struct
+--- 2. Run `:GoTagAdd json` to add json tags to struct fields
+--- 3. Run `:GoTagRm json` to remove json tags to struct fields
 ---
---- note: if you dont spesify the tag it will use `json` as default
+--- NOTE: if you dont specify the tag it will use `json` as default
 ---
---- simple example:
+--- Example:
 --- >go
 ---    // before
 ---    type User struct {
···
     end,
   })
 
-  -- decode goted value
+  -- decode value
   local tagged = vim.json.decode(table.concat(output))
   if
     tagged.errors ~= nil