Merge pull request #765 from lightninglabs/docs-lnd

Update lnd documentation

Author: github-actions[bot]

docs/lnd/code_contribution_guidelines.md

@@ -337,7 +337,7 @@ Examples of common patterns w.r.t commit structures within the project:
     small scale, fix typos, or any changes that do not modify the code, the
     commit message of the HEAD commit of the PR should end with `[skip ci]` to
     skip the CI checks. When pushing to such an existing PR, the latest commit
-    being pushed should end with `[skip ci]` as to not inadvertantly trigger the
+    being pushed should end with `[skip ci]` as to not inadvertently trigger the
     CI checks.
     
 ## Sign your git commits

docs/lnd/debugging_lnd.md

@@ -78,7 +78,7 @@ prefix is overwritten by the `LNWL` subsystem.
 
 Moreover when using the `lncli` command the return value will provide the 
 updated list of all subsystems and their associated logging levels. This makes
-it easy to get an overview of the corrent logging level for the whole system.
+it easy to get an overview of the current logging level for the whole system.
 
 Example:
 

docs/lnd/release-notes/release-notes-0.19.0.md

@@ -251,6 +251,10 @@ The underlying functionality between those two options remain the same.
   [GoroutineManager](https://github.com/lightningnetwork/lnd/pull/9141) so that 
   its constructor does not take a context.
 
+* [Update protofsm 
+ StateMachine](https://github.com/lightningnetwork/lnd/pull/9342) to use the 
+  new GoroutineManager API along with structured logging.
+
 ## Tooling and Documentation
 
 * [Improved `lncli create` command help text](https://github.com/lightningnetwork/lnd/pull/9077)

docs/lnd/signing_release_candidate.md

@@ -50,7 +50,7 @@ Tip: Download the official release Manifest file to your local maschine and do:
 `diff lnd-v0.18.3-beta/manifest-v0.18.3-beta.txt ~/Downloads/manifest-v0.18.3-beta.txt`
 (example command for a release candidate called `v0.18.3-beta`)  
 Only if all hashes are identical, should you sign the release.  If the digests
-match, see the example signing comand, assuming your PGP signing key is
+match, see the example signing command, assuming your PGP signing key is
 available on your local device:  
 `gpg --local-user $KEYID  --detach-sig --output manifest-$USERNAME-v0.18.3-beta.sig manifest-v0.18.3-beta.txt`.  
 `USERNAME` being the name in the `[verify-install.sh](../scripts/verify-install.sh)`