Fixed a bunch of typos.

Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>

Author: marvin-hansen

Handover.md

@@ -16,9 +16,9 @@ Add the new / active maintainer to the following files: MAINTAINERS.md, CODEOWNE
 
 ## Verify CI / Github actions:
 
-Currently, all GH actions trigger on pull request assuming branch protection is in place (as it should). 
+Currently, all GH actions trigger on pull request, unless stated otherwise, assuming[ branch protection is in place](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches) (as it should). 
 
-THe following GH actions are pre-configured:
+The following GH actions are pre-configured:
 
 - audit - security audit against a DB of all known vulnerabilities. Runs on every PR. Active by default.
 - linter / clippy - Checks against a massive database of known Rust lints. Runs on every PR. Active by default.
@@ -38,7 +38,7 @@ Rust packages are published to the crates.io registry. To do so, the following s
 2) Verify the pre-defined meta data in Cargo.toml. Repo & homepage is already set to https://github.com/timeplus-io/proton-rust-client
 3) Create a free account on https://crates.io/
 4) Create an API token in the dashboard
-5) login locally, from a terminal: ```cargo login``` Then at the prompt put in the token specified. 
+5) Login locally, from a terminal: ```cargo login``` Then at the prompt put in the token specified. 
 6) Conduct a dry run to see if everything is correct: ```cargo publish --dry-run```
 7) When the dry run completes without error, publish the first version: ```cargo publish```
 
@@ -52,7 +52,7 @@ The conventional Rust release process requires a fair amount of manual steps, su
 adding new git tags, generating changelog, publishing to crates.io etc. For full automation, the release-plz system
 has already been pre-configured. 
 
-Release-plz automates your relase process:
+Release-plz automates your release process:
 
 * CHANGELOG generation (with git-cliff).
 * Creation of GitHub/Gitea releases.
@@ -69,7 +69,7 @@ and add your crates.io API token as a Github secret.
 Once the release-plz is enabled, every push to main is added to a generated release PR. When the release PR
 is merged, a new release is fully automatically published to the cargo registry and the documentation is uploaded to rustdocs.org.
 
-For details on how to configure relese-plz, consult the documentation:
+For details on how to configure release-plz, consult the documentation:
 https://github.com/MarcoIeni/release-plz
 
 For details of how to add a GH secret, see the official GH documentation: