Merge pull request #2294 from pareenaverma/content_review

Spell fixes

Author: pareenaverma

.wordlist.txt

@@ -4702,5 +4702,24 @@ GDM
 LPI
 nsec
 shortcode
-
+BSON
+joedog
+Seige
+Antonov
+jwt
+kbs
+Nfpl
+ZjnAMjLk
+hCpeYsarnnGv
+kbs
+rvps
+xcbTMTBX
+CDH
+RVPS
+Attester
+attester
+ATtestation
+CoCo
+procedureS
+NIC’s
 

content/learning-paths/servers-and-cloud-computing/cca-trustee/cca-trustee.md

@@ -86,7 +86,7 @@ A verifier driver parses the attestation evidence provided by the hardware TEE.
 1. Verifies the hardware TEE signature of the TEE quote and report provided in the evidence
 2. Receives the evidence and organizes the status into a JSON format to be returned
 
-In this Learning Path, the AS is configured to use an external CCA verifer.
+In this Learning Path, the AS is configured to use an external CCA verifier.
 
 [Linaro](https://www.linaro.org) provides such an attestation verifier for use with pre-silicon Arm CCA platforms.
 This verifier is built from the Open-Source [Veraison project](https://github.com/veraison).
@@ -138,8 +138,8 @@ FVP and the reference software stack, see the
 Learning Path.
 
 When the AS receives an attestation token from the realm via KBS:
-- it calls an external CCA verifer (the Linaro attestation verifier service) to obtain an attestation result.
-- the external CCA verifer checks the token's cryptographic signature,
+- it calls an external CCA verifier (the Linaro attestation verifier service) to obtain an attestation result.
+- the external CCA verifier checks the token's cryptographic signature,
   verifies that it denotes a confidential computing platform and provides an attestation result.
 - it also checks the token evidences against its own attestation policies and updates attestation result status and trustworthiness vectors.
 

content/learning-paths/servers-and-cloud-computing/cca-trustee/flow.md

@@ -199,7 +199,7 @@ Using JWK key from JWT header
 Error: verifying signed EAR from "ear.jwt" using "JWK header" key: failed verifying JWT message: jwt.Parse: failed to parse token: jwt.Validate: validation failed: "exp" not satisfied: token is expired
 ```
 
-Please obtain a new EAR message by re-runing the attestation command.
+Please obtain a new EAR message by re-running the attestation command.
 {{% /notice %}}
 
 

content/learning-paths/servers-and-cloud-computing/envoy-gcp/background.md

@@ -14,7 +14,7 @@ The C4A series provides a cost-effective alternative to x86 virtual machines whi
 
 To learn more about Google Axion, refer to the [Introducing Google Axion Processors, our new Arm-based CPUs](https://cloud.google.com/blog/products/compute/introducing-googles-new-arm-based-cpu) blog.
 
-## Envoy for service proxying and traffic management on Arm
+## Envoy for service proxy and traffic management on Arm
 
 Envoy is an open-source, high-performance edge and service proxy designed for cloud-native applications.
 

content/learning-paths/servers-and-cloud-computing/envoy-gcp/benchmarking.md

@@ -61,7 +61,7 @@ This runs the Envoy proxy with your configuration file (envoy_config.yaml) so it
 ```
 curl -v http://127.0.0.1:10000/get
 ```
-Running from another terminal returns a **200 OK** status, confirming that Envoy is running and successfully proxying requests.
+Running from another terminal returns a **200 OK** status, confirming that Envoy is running and successfully processing requests.
 
 3. Run a Time-based Load Test