Fix various typos in markdown files.

Author: definitelynobody

docs/Contributing/Issues.md

@@ -55,6 +55,6 @@ To keep our work organised, we make heavy use of labels. These allow us to quick
 - [technology/sgx](https://github.com/enarx/enarx/labels/technology%2Fsgx): All SGX related issues
 - [technology/wasm](https://github.com/enarx/enarx/labels/technology%20wasm): All WASM related issues
 - [triage](https://github.com/enarx/enarx/labels/triage): news issues are tagged with this label automatically. 
-- [wontfix](https://github.com/enarx/enarx/labels/wontfix): Issuses that will not be worked on
+- [wontfix](https://github.com/enarx/enarx/labels/wontfix): Issues that will not be worked on
 
 You can click on a label name to see the issues that have been tagged with it.

docs/Contributing/Lab.md

@@ -8,7 +8,7 @@ This document explains the rules regarding these machines as well as how to acce
 
 ## Obtaining access
 
-Access to the Enax Lab machines is relatively open, and the machines are intended to be used by the community. We do expect you to have started contributing to the project and to know you a minimum first, so please join the [chat](https://chat.enarx.dev) if you haven't already done so.
+Access to the Enarx Lab machines is relatively open, and the machines are intended to be used by the community. We do expect you to have started contributing to the project and to know you a minimum first, so please join the [chat](https://chat.enarx.dev) if you haven't already done so.
 
 If you would like access to the Enarx infrastructure, please add yourself to both `users.conf` and `sshkeys.conf` at GitLab by doing a merge request:
 

docs/Contributing/RFCs.md

@@ -3,13 +3,13 @@ The Enarx project welcomes contributions!
 
 Would you like to help with the development of Enarx?
 
-This page will guide you towards submiting your first RFC – Request for Comment
+This page will guide you towards submitting your first RFC – Request for Comment
 –, the process used by the project to formally describe improvements or new
 ideas.
 
 There are many different skills needed to build Enarx, from low-level assembly
 code for platform-specific enablement (think SGX, SEV, etc.) to kernel-related 
-work, from WebAssembly to building and maintaining our infrastracture and automated
+work, from WebAssembly to building and maintaining our infrastructure and automated
 integration and testing (CI/CD), and more, so please don't hesitate to try your
 hand at any of these or to come and talk to us.
 

docs/Fellowship/Benefits.md

@@ -1,6 +1,6 @@
 # Benefits
 The Confidential Computing Fellowship offers a range of benefits, including:
-- Networking: be connected with like-minded individuals to share knowlege, best practices, and opportunities;
+- Networking: be connected with like-minded individuals to share knowledge, best practices, and opportunities;
 - Mentorship: be paired up with prominent mentors in the Confidential Computing space as well as adjacent technologies;
 - Internship: potentially be a recipient of a paid internship within a program like Outreachy or Google Summer of Code.
 - Resources: get access to resources like Lab machines (with Intel SGX, AMD SEV, ARM Realms, etc).

docs/Fellowship/Conclusion.md

@@ -2,4 +2,4 @@
 
 Confidential Computing is a new emerging field with lots of potential. The Confidential Computing Fellowship aims to provide a sustainable program to support individuals interested in learning, promoting, and researching Confidential Computing and adjacent technologies.
 
-Please apply by creating a [profile](https://docs.linuxfoundation.org/lfx/mentorship/mentees/create-a-mentee-profile) at LFX Mentorship and submiting your application to the [Confidential Computing Fellowship]( https://mentorship.lfx.linuxfoundation.org/project/3dbf9c76-1147-4d49-b4dc-a982061f0b9c) program.
+Please apply by creating a [profile](https://docs.linuxfoundation.org/lfx/mentorship/mentees/create-a-mentee-profile) at LFX Mentorship and submitting your application to the [Confidential Computing Fellowship]( https://mentorship.lfx.linuxfoundation.org/project/3dbf9c76-1147-4d49-b4dc-a982061f0b9c) program.

docs/Fellowship/Schedule.md

@@ -28,7 +28,7 @@ A sample schedule for a 12-week program could be:
 
 ## Graduation
 
-Fellows who successfuly complete the fellowship program will graduate and receive a Confidential Computing Fellowship certification. Further opportunities will be explored and presented to the fellow based on his/her interests.
+Fellows who successfully complete the fellowship program will graduate and receive a Confidential Computing Fellowship certification. Further opportunities will be explored and presented to the fellow based on his/her interests.
 
 ## Mentorship
 

docs/Installation/Introduction.md

@@ -4,6 +4,6 @@ Enarx currently has support for Intel SGX and AMD SEV-SNP. Please check the [Req
 
 On the [Initial Setup](Setup) page, you'll find instructions on how to install dependencies for Fedora, CentOS/Stream, and Debian/Ubuntu, including Rust and the toolchains.
 
-Next, you'll find instuctions on how to [install Enarx](Enarx) from crates.io, GitHub, or Nix.
+Next, you'll find instructions on how to [install Enarx](Enarx) from crates.io, GitHub, or Nix.
 
 Finally, on the [Running Enarx](Wasm) page, you'll build and run your first `Hello World` WebAssembly module in Enarx.

docs/Technical/AMD-SEV.md

@@ -3,5 +3,5 @@
 A system with SEV.
 
 ### Attestation overview
-* SEV is targetted at secure VMs.  You attest to a signature by AMD, which includes a hash of something they call firmware in this context.  This firmware is basically code injected into the VM. This firmware allows host to have some code within the TEE: that code will form an Enarx Keep.
+* SEV is targeted at secure VMs.  You attest to a signature by AMD, which includes a hash of something they call firmware in this context.  This firmware is basically code injected into the VM. This firmware allows host to have some code within the TEE: that code will form an Enarx Keep.
 * Enarx will run as this “firmware”, which is essentially injected into the VM.  AMD will provide a signature from a key burned into the CPU over a hash of the firmware that it is going to be loaded.

docs/Technical/TEE.md

@@ -16,4 +16,4 @@ HSM's (Hardware Security Modules) generally provide higher levels of protection
 ## Further reading
 - [Hardware with TEE support](Hardware)
 - [Vulnerabilities in and attacks on TEEs](Vulnerabilities-Attacks)
-- [Current Trusted Execution Environement Landscape](https://next.redhat.com/2019/12/02/current-trusted-execution-environment-landscape/), long-form article published in February 2020 by members of the Enarx team.
+- [Current Trusted Execution Environment Landscape](https://next.redhat.com/2019/12/02/current-trusted-execution-environment-landscape/), long-form article published in February 2020 by members of the Enarx team.