doc: fix typos

Author: JS-Zheng

CODE_OF_CONDUCT.md

@@ -1,6 +1,6 @@
 We, the maintainers, pledge to treat all contributors with respect and require that contributors reciprocate.
 
-The maintainers will not tolerate unwelcome, inpolite, abusive or unprofessional behaviour. 
+The maintainers will not tolerate unwelcome, impolite, abusive or unprofessional behaviour. 
 
 At the discretion of the maintainers, users who persist in behaving in a way that is unwelcome may be subject to a ban.
 

CONTRIBUTING.md

@@ -114,15 +114,15 @@ the maintainers have to keep it working forever.
 
 ### Small changes
 
-For bug fixes, documentation changes, gadget versin updates, etc. please just
+For bug fixes, documentation changes, gadget version updates, etc. please just
 send a PR, I'm super happy to merge these!
 
 If you are unsure, or looking for some pointers, feel free to ask in Gitter, or
 mention is in the PR.
 
 ### Larger changes
 
-For larger features that might be in any way controvertial, or increase the
+For larger features that might be in any way controversial, or increase the
 complexity of the overall plugin, please come to Gitter and talk to the
 maintainer(s) first. This saves a lot of potential back-and-forth and makes sure
 that we're "on the same page" about the idea and the ongoing maintenance.
@@ -184,7 +184,7 @@ Vimspector creator.
 
 ### Manual testing within the container
 
-To manually test with Vim withing the container, affter runnning the tests with
+To manually test with Vim within the container, affter running the tests with
 `--base-dir test-base-docker`, you can use this:
 
 ```

README.md

@@ -249,7 +249,7 @@ Why such a new vim ? Well 2 reasons:
 Why is neovim experimental? Because the author doesn't use neovim regularly, and
 there are no regression tests for vimspector in neovim, so it may break
 occasionally. Issue reports are handled on best-efforts basis, and PRs are
-welcome to fix bugs. See also the next section descibing differences for neovim
+welcome to fix bugs. See also the next section describing differences for neovim
 vs vim.
 
 Why Windows support experimental? Because it's effort and it's not a priority
@@ -342,7 +342,7 @@ $ git clone https://github.com/puremourning/vimspector ~/.vim/pack/vimspector/op
 ```
 
 2. Configure vimspector in your `.vimrc`, for example to enable the standard
-   mapings:
+   mappings:
 
 ```viml
 let g:vimspector_enable_mappings = 'HUMAN'
@@ -592,7 +592,7 @@ can (and probably will) change, including things like:
 - breaking changes to the configuration
 - keys, layout, functionality of the UI
 
-However, I commit to only doing this in the most extreme cases and to annouce
+However, I commit to only doing this in the most extreme cases and to announce
 such changes on Gitter well in advance. There's nothing more annoying than stuff
 just breaking on you. I get that.
 

autoload/vimspector/internal/balloon.vim

@@ -316,7 +316,7 @@ function! s:CreateNeovimTooltip( body ) abort
   call nvim_win_set_option( s:popup_win_id, 'number', v:false )
 
   " Move the cursor into the popup window, as this is the only way we can
-  " interract with the popup in neovim
+  " interact with the popup in neovim
   noautocmd call win_gotoid( s:popup_win_id )
 
   nnoremap <silent> <buffer> <Esc> <cmd>quit<CR>

autoload/vimspector/internal/channel.vim

@@ -64,7 +64,7 @@ function! vimspector#internal#channel#StartDebugSession( config ) abort
 
   let l:addr = get( a:config, 'host', '127.0.0.1' ) . ':' . a:config[ 'port' ]
 
-  echo 'Connecting to ' . l:addr . '... (waiting fo up to 10 seconds)'
+  echo 'Connecting to ' . l:addr . '... (waiting for up to 10 seconds)'
   let s:ch = ch_open( l:addr,
         \             {
         \                 'mode': 'raw',

autoload/vimspector/internal/neoterm.vim

@@ -19,7 +19,7 @@ let s:save_cpo = &cpoptions
 set cpoptions&vim
 " }}}
 
-" Ids are unique throughtout the life of neovim, but obviously buffer numbers
+" Ids are unique throughout the life of neovim, but obviously buffer numbers
 " aren't
 "
 " FIXME: Tidy this map when buffers are closed ?

autoload/vimspector/internal/state.vim

@@ -59,7 +59,7 @@ function! vimspector#internal#state#TabClosed( afile ) abort
 #   probably the vimspector UI tab that was closed)
 #
 # noevim helpfully provides the tab number that was closed in <afile>, so we
-# use that there (it also doens't correctly invalidate tab objects:
+# use that there (it also doesn't correctly invalidate tab objects:
 # https://github.com/neovim/neovim/issues/16327)
 
 if '_vimspector_session' in globals() and _vimspector_session:

doc/vimspector-ref.txt

@@ -444,7 +444,7 @@ Extending adapters ~
 
 You can specify a key 'extends' in the adapter configuration to inherit from an
 existing adapter. This is useful for defining adapters for remote debugging or
-where there are common options, varables etc. For example:
+where there are common options, variables etc. For example:
 >
   {
     "adapters": {
@@ -508,7 +508,7 @@ typical example looks like this:
         "filetypes": [ /* list of filetypes this applies to */ ],
         "configuration": {
           "request": "<launch or attach>",
-          <debug configutation>
+          <debug configuration>
         }
       }
     }
@@ -527,7 +527,7 @@ a set of supplied 'ad-hoc' configurations. You do with as follows:
 
 For example:
 >
-  let pid = <some_exression>
+  let pid = <some_expression>
   call vimspector#LaunchWithConfigurations( {
               \  "attach": {
               \    "adapter": "netcoredbg",
@@ -561,7 +561,7 @@ will use that configuration, unless it contains a key '"autoselect": false'.
 
 If any single configuration is found with '"default": true', that one is used.
 
-Otherwise, the user is propmted to select a configuration to use.
+Otherwise, the user is prompted to select a configuration to use.
 
 -------------------------------------------------------------------------------
                               *vimspector-ref-specifying-default-configuration*
@@ -724,8 +724,8 @@ a value, as in :
 Extending configurations ~
 
 Like adapters, you can include a 'extends' key in the configuration
-specification, which makes it "inherit" from the specified configuraiton. In
-practice that means any keys specified in this configuraiton override the
+specification, which makes it "inherit" from the specified configuration. In
+practice that means any keys specified in this configuration override the
 corresponding keys in the "base" configuration.
 
 This is useful in particular where there data that need to be the same across a
@@ -806,7 +806,7 @@ The resulting "derived" configuraition ends up like this:
   {
     "key1": "This key is unchanged",
     "key2": {
-      "key2.1": "This is the override valu",
+      "key2.1": "This is the override value",
       "key2.2": "This key is unchanged"
     }
   }
@@ -888,7 +888,7 @@ Vimspector then orchestrates the various tools to set you up.
             //   "args": [ "-o", "StrictHostKeyChecking=no" ]
             // },
   
-            // Command to launch the debugee and attach the debugger; 
+            // Command to launch the debuggee and attach the debugger; 
             // %CMD% replaced with the remote-cmdLine configured in the launch
             // configuration. (mandatory)
             "runCommand": [
@@ -919,8 +919,8 @@ Vimspector then orchestrates the various tools to set you up.
             // Command to get the PID of the process to attach  (mandatory)
             "pidCommand": [
               //
-              // Remember taht you can use ${var} to ask for input. I use this to
-              // call a custom command to returm the PID for a named service, so
+              // Remember that you can use ${var} to ask for input. I use this to
+              // call a custom command to return the PID for a named service, so
               // here's an examle:
               //
               "/path/to/secret/script/GetPIDForService", "${ServiceName}"
@@ -1055,7 +1055,7 @@ gdbserver and have to tell cpptools a few more options.
             ],
             //
             // If your application is started by a wrapper script, then you might
-            // need the followin. GDB can't pause an application because it only
+            // need the following. GDB can't pause an application because it only
             // sends the signal to the process group leader. Or something.
             // Basically, if you find that everything just hangs and the
             // application never attaches, try using the following to manually
@@ -1117,7 +1117,7 @@ port.
           "remote": {
             "container": "${container}", // Docker container id or name to exec into to.
   
-            // Command to launch the debugee and attach the debugger; 
+            // Command to launch the debuggee and attach the debugger; 
             // %CMD% replaced with the remote-cmdLine configured in the launch
             // configuration. (mandatory)
             "runCommand": [
@@ -1147,8 +1147,8 @@ port.
             // This command gets appended to "docker exec ${container}"
             "pidCommand": [
               //
-              // Remember taht you can use ${var} to ask for input. I use this to
-              // call a custom command to returm the PID for a named service, so
+              // Remember that you can use ${var} to ask for input. I use this to
+              // call a custom command to return the PID for a named service, so
               // here's an examle:
               //
               "sh", "-c", "pgrep", "-f", "${filename}"
@@ -1254,7 +1254,7 @@ language server [5].
 
 It is recommended to include the '$schema' declaration as in the above
 examples, but if that isn't present, the following JSON language server
-configuration [6] is recommened to load the schema from the Internet:
+configuration [6] is recommended to load the schema from the Internet:
 >
   {
     "json": {

doc/vimspector.txt

@@ -382,7 +382,7 @@ Why such a new vim ? Well 2 reasons:
 Why is neovim experimental? Because the author doesn't use neovim regularly,
 and there are no regression tests for vimspector in neovim, so it may break
 occasionally. Issue reports are handled on best-efforts basis, and PRs are
-welcome to fix bugs. See also the next section descibing differences for neovim
+welcome to fix bugs. See also the next section describing differences for neovim
 vs vim.
 
 Why Windows support experimental? Because it's effort and it's not a priority
@@ -478,7 +478,7 @@ by cloning this repository into your package path, like this:
   $ git clone https://github.com/puremourning/vimspector ~/.vim/pack/vimspector/opt/vimspector
 <
 1. Configure vimspector in your '.vimrc', for example to enable the standard
-   mapings:
+   mappings:
 >
   let g:vimspector_enable_mappings = 'HUMAN'
 <
@@ -750,7 +750,7 @@ probably will) change, including things like:
 - breaking changes to the configuration
 - keys, layout, functionality of the UI
 
-However, I commit to only doing this in the most extreme cases and to annouce
+However, I commit to only doing this in the most extreme cases and to announce
 such changes on Gitter well in advance. There's nothing more annoying than
 stuff just breaking on you. I get that.
 
@@ -1019,11 +1019,11 @@ To launch with an ad-hoc config you can use:
 
 - 'call vimspector#LaunchWithConfigurations( dict )'
 
-The argument is a 'dict' wich is the 'configurations' section of a .vimspector
+The argument is a 'dict' which is the 'configurations' section of a .vimspector
 file Pass one configuration in and that will be selected as the one to run. For
 example:
 >
-  let pid = <some_exression>
+  let pid = <some_expression>
   call vimspector#LaunchWithConfigurations({
               \  "attach": {
               \    "adapter": "netcoredbg",
@@ -1272,9 +1272,9 @@ named '.vimspector.session', but this can be changed globally by setting
 path when calling the command.
 
 Advanced users may wish to automate the process of loading and saving, for
-example by adding 'VimEnter' and 'VimLeave' autocommands. It's recommented in
+example by adding 'VimEnter' and 'VimLeave' autocommands. It's recommended in
 that case to use 'silent!' to avoid annoying errors if the file can't be read
-or writtten.
+or written.
 
 The simplest form of automation is to load the vimspector session whenever you
 start vim with a session file. This is as simple as doing this:
@@ -1314,7 +1314,7 @@ Scopes and variables are represented by the buffer 'vimspector.Variables'.
 If you prefer a more verbose display for variables and watches, then you can
 "let g:vimspector_variables_display_mode = 'full'". By default only the name
 and value are displayed, with other data available from hovering the mouse or
-triggering '<Plug>VimspectorBalloonEval' on the line contianing the value in
+triggering '<Plug>VimspectorBalloonEval' on the line containing the value in
 the variables (or watches) window.
 
 -------------------------------------------------------------------------------
@@ -1336,7 +1336,7 @@ All rules for 'Variables and scopes' apply plus the following:
 - Set the value of the variable with '<C-CR>' (control + '<CR>') or
   '<leader><CR>' (if 'modifyOtherKeys' doesn't work for you)
 
-- Use regular nagivation keys ('j', 'k') to choose the current selection;
+- Use regular navigation keys ('j', 'k') to choose the current selection;
   '<Esc>' (or leave the tooltip window) to close the tooltip.
 
   Image: variable eval hover (see reference [28])
@@ -1368,7 +1368,7 @@ The watches are represented by the buffer 'vimspector.StackTrace'.
 If you prefer a more verbose display for variables and watches, then you can
 "let g:vimspector_variables_display_mode = 'full'". By default only the name
 and value are displayed, with other data available from hovering the mouse or
-triggering '<Plug>VimspectorBalloonEval' on the line contianing the value in
+triggering '<Plug>VimspectorBalloonEval' on the line containing the value in
 the variables (or watches) window.
 
 -------------------------------------------------------------------------------
@@ -1401,7 +1401,7 @@ variables. This can be done from the Variables and Wathces windows with:
 On doing this, you're asked to enter a number of bytes to read (from the
 location associated with the current cursor line) and an offset from that
 location. A new buffer is displayed in the Code Window containing a memory dump
-in hex and ascii, simmilar to the output of 'xxd'.
+in hex and ascii, similar to the output of 'xxd'.
 
 **_NOTE_**: This feature is experimental and may change in any way based on
 user feedback.
@@ -2500,7 +2500,7 @@ autocommand, for example:
     call win_gotoid( g:vimspector_session_windows.code )
     " Clear the existing WinBar created by Vimspector
     nunmenu WinBar
-    " Cretae our own WinBar
+    " Create our own WinBar
     nnoremenu WinBar.Kill :call vimspector#Stop( { 'interactive': v:true } )<CR>
     nnoremenu WinBar.Continue :call vimspector#Continue()<CR>
     nnoremenu WinBar.Pause :call vimspector#Pause()<CR>
@@ -2564,7 +2564,7 @@ FAQ ~
    necessarily be easy to work out what to put in the '.vimspector.json'. As
    you can see above, some of the servers aren't really editor agnostic, and
    require very-specific unique handling. See the wiki [15] for details on
-   additonal language support
+   additional language support
 
 2. How do I stop it starting a new Terminal.app on macOS? See this comment
    [54]