Fix various spelling/grammar issues in release notes for 0.88.0 (#1175)

Author: IndigoLily

blog/2023-12-12-nushell_0_88_0.md

@@ -240,14 +240,14 @@ def foo [--switch] {
 Once again, [@WindSoilder](https://github.com/WindSoilder) has been working on the redirection
 system of Nushell, fixing a bug and adding a new very nice feature:
 - [#10851](https://github.com/nushell/nushell/pull/10851): one pipeline output stream can be
-    redirected and the other one used as input to the rest of the pipe
+    redirected and the other one used as input to the rest of the pipe.
     Given the following Bash script called `foo.sh` that outputs both to _stdout_ and _stderr_
     ```sh
     echo aaaaa
     echo bbb 1>&2
     echo cc
     ```
-    it is now possible to run the following command, redirecting `bbb` to the a file and the rest
+    it is now possible to run the following command, redirecting `bbb` to a file and the rest
     to the `lines | each { ... }` part of the pipeline:
     ```nushell
     bash test.sh err> err.txt | lines | each { str length}
@@ -370,7 +370,7 @@ to address two major bugs to two quite important filesystem commands: `rm` and `
 Below are some details about these two bug fixes:
 - [@IanManske](https://github.com/IanManske) fixed `rm` in
     [#11064](https://github.com/nushell/nushell/pull/11064) which has
-    [trouble to remove files after a `cd`](https://github.com/nushell/nushell/issues/11061)
+    [trouble removing files after a `cd`](https://github.com/nushell/nushell/issues/11061)
 - [@kubouch](https://github.com/kubouch) fixed a similar one about `cp` in
     [#11080](https://github.com/nushell/nushell/pull/11080), addressing
     [#10832](https://github.com/nushell/nushell/issues/10832)
@@ -407,7 +407,7 @@ but it is impossible to do `let env = 123`
 However, up until now and the work of [@KAAtheWiseGit](https://github.com/KAAtheWiseGit)
 in [#11169](https://github.com/nushell/nushell/pull/11169) and
 [#11228](https://github.com/nushell/nushell/pull/11228), it was possible to redefined these variables
-in command definition, the code would parse and run but you would get the internal values instead of
+in command definition: the code would parse and run, but you would get the internal values instead of
 the ones passed to the command, which is a nasty silent bug!
 From now on, the following will give an error
 ```nushell
@@ -421,7 +421,7 @@ def baz [in] { print $in }
 ```
 
 Also, because `$nu` and `$env` don't have spans by construction, i.e. they are not defined in any
-script where a span would make sense but rather internally when Nushell starts, accessing there
+script where a span would make sense but rather internally when Nushell starts, accessing their
 `metadata` does not make sense. This release makes the error more helpful:
 ```nushell
 metadata $env
@@ -442,7 +442,7 @@ With [#10941](https://github.com/nushell/nushell/pull/10941), completions should
 this release :partying:
 
 ## Our set of commands is evolving [[toc](#table-of-content)]
-As usual, new release rhyms with changes to commands!
+As usual, new release rhymes with changes to commands!
 
 ### New commands [[toc](#table-of-content)]
 - `is-terminal` by [@drbrain](https://github.com/drbrain) in [#10970](https://github.com/nushell/nushell/pull/10970)
@@ -479,7 +479,7 @@ Input/output types:
 ```
 
 ### Changes to existing commands [[toc](#table-of-content)]
-- thanks to [@KAAtheWiseGit](https://github.com/KAAtheWiseGit) in [#11195](https://github.com/nushell/nushell/pull/11195), `inpust list` will accept more input/output types
+- thanks to [@KAAtheWiseGit](https://github.com/KAAtheWiseGit) in [#11195](https://github.com/nushell/nushell/pull/11195), `input list` will accept more input/output types
 - the `list<string> -> string` I/O pair has been added to the `last` command by [@amtoine](https://github.com/amtoine) in [#11137](https://github.com/nushell/nushell/pull/11137)
 - with the work of [@IanManske](https://github.com/IanManske) in [#11258](https://github.com/nushell/nushell/pull/11258), `insert`, `update` and `upsert` should now work more consistently with `list`s, e.g.
 ```nushell