Verify spelling fixes pass check-spelling

calico-cloud/_includes/release-notes/_v3.14.0-pre-release-notes.mdx

@@ -19,7 +19,7 @@
 - In BPF dataplane mode, Felix now handles single-block IPAM pools. Previously single-block pools resulted in a collision when programming the dataplane routes. [felix #2245](https://github.com/projectcalico/felix/pull/2245) (@fasaxc)
 - None required [felix #2233](https://github.com/projectcalico/felix/pull/2233) (@tomastigera)
 - None required [felix #2232](https://github.com/projectcalico/felix/pull/2232) (@tomastigera)
-- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@neiljerram)
+- [Openstack] Allow DHCP from the workload, on kernels where rp_filter doesn't already [felix #2231](https://github.com/projectcalico/felix/pull/2231) (@nelljerram)
 - all-interfaces host endpoints now supports normal network policy in addition to pre-dnat policy [felix #2228](https://github.com/projectcalico/felix/pull/2228) (@lmm)
 - Add FelixConfiguration option for setting route information source [libcalico-go #1222](https://github.com/projectcalico/libcalico-go/pull/1222) (@caseydavenport)
 - Added Wireguard configuration. [libcalico-go #1215](https://github.com/projectcalico/libcalico-go/pull/1215) (@realgaurav)
@@ -34,7 +34,7 @@
 - auto host endpoints have a default allow profile [kube-controllers #470](https://github.com/projectcalico/kube-controllers/pull/470) (@lmm)
 - Fix IPAM garbage collection in etcd mode on clusters where node name does not match Kubernetes node name. [kube-controllers #467](https://github.com/projectcalico/kube-controllers/pull/467) (@caseydavenport)
 - Use KubeControllersConfiguration resource for config [kube-controllers #464](https://github.com/projectcalico/kube-controllers/pull/464) (@spikecurtis)
-- Fix kube-controllers attempting to clean up non-existent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
+- Fix kube-controllers attempting to clean up nonexistent node resources [kube-controllers #461](https://github.com/projectcalico/kube-controllers/pull/461) (@fcuello-fudo)
 - kube-controllers can now automatically provision host endpoints for nodes in the cluster [kube-controllers #458](https://github.com/projectcalico/kube-controllers/pull/458) (@lmm)
 - Kubernetes network tutorials updated for v1.18. [calico #3447](https://github.com/projectcalico/calico/pull/3447) (@tmjd)
 - With OpenShift install time resources can be created. This means Calico resources can be created before the Calico components are started. [calico #3338](https://github.com/projectcalico/calico/pull/3338) (@tmjd)

calico-cloud/_includes/release-notes/_v3.16.0-release-notes.mdx

@@ -46,7 +46,7 @@ Calico now supports BGP communities! Check out the BGP configuration resource [r
 - In BPF mode, Felix now rate-limits stale BPF map cleanup in order to save CPU. [felix #2428](https://github.com/projectcalico/felix/pull/2428) (@fasaxc)
 - In BPF mode, Felix now detects BPF support on Red Hat kernels with backports as well as generic kernels. [felix #2409](https://github.com/projectcalico/felix/pull/2409) (@sridhartigera)
 - In BPF mode, Felix now uses a more efficient algorithm to resync the Kubernetes services with the dataplane. This speeds up the initial sync (especially with large numbers of services). [felix #2401](https://github.com/projectcalico/felix/pull/2401) (@tomastigera)
-- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@neiljerram)
+- eBPF dataplane support for encryption via Wireguard [felix #2389](https://github.com/projectcalico/felix/pull/2389) (@nelljerram)
 - Reject connections to services with no backends [felix #2380](https://github.com/projectcalico/felix/pull/2380) (@sridhartigera)
 - Implementation to handle setting source-destination-check for AWS EC2 instances. [felix #2381](https://github.com/projectcalico/felix/pull/2381) (@realgaurav)
 - In BPF mode, Felix now applies policy updates without reapplying the BPF programs; this gives a performance boost and closes a window where traffic was not policed. [felix #2363](https://github.com/projectcalico/felix/pull/2363) (@fasaxc)

calico-cloud/_includes/release-notes/_v3.16.1-release-notes.mdx

@@ -3,7 +3,7 @@
 ### Bug fixes
 
 - Fix population of etcd certificates in CNI config [cni-plugin #949](https://github.com/projectcalico/cni-plugin/pull/949) (@caseydavenport)
-- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@neiljerram)
+- Resolves an issue on nodes whose Kubernetes node name does not exactly match the system hostname [cni-plugin #943](https://github.com/projectcalico/cni-plugin/pull/943) (@nelljerram)
 - Fix flannel migration issues when running on Rancher [kube-controllers #506](https://github.com/projectcalico/kube-controllers/pull/506) (@songjiang)
 - Fix `kubectl exec` format for migration controller [kube-controllers #504](https://github.com/projectcalico/kube-controllers/pull/504) (@songjiang)
 - Fix flannel migration for clusters with multiple control plane nodes. [kube-controllers #503](https://github.com/projectcalico/kube-controllers/pull/503) (@caseydavenport)

calico-cloud/get-started/connect/operator-checklist.mdx

@@ -404,7 +404,7 @@ kubectl get tigerastatus
 | 2   | calico                        | TRUE      | FALSE       | FALSE    | 11m   |
 | 3   | cloud-core                    | TRUE      | FALSE       | FALSE    | 11m   |
 | 4   | compliance                    | TRUE      | FALSE       | FALSE    | 9m39s |
-| 5   | intrusion-detection            | TRUE      | FALSE       | FALSE    | 9m49s |
+| 5   | intrusion-detection           | TRUE      | FALSE       | FALSE    | 9m49s |
 | 6   | log-collector                 | TRUE      | FALSE       | FALSE    | 9m29s |
 | 7   | management-cluster-connection | TRUE      | FALSE       | FALSE    | 9m54s |
 | 8   | monitor                       | TRUE      | FALSE       | FALSE    | 11m   |

calico-cloud/image-assurance/scanners/overview.mdx

@@ -37,4 +37,4 @@ Image Assurance provides different versions of the scanner to accommodate differ
 | --------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
 | [Kubernetes cluster](./pipeline-scanner) | Scan any running image in the Kubernetes cluster including locally-built first-party images to fix critical bugs. | Runs automatically in the managed cluster in Manager UI | The Image Assurance dashboard provides an easy way to get started with vulnerability scanning and remediation, and defense-in-depth coverage without building your own scanning solution. |
 | [CI/CD pipeline](./cluster-scanner)      | Integrate the CLI scanner in your application build pipeline and private registries including: <br />- Customer-built images<br />- Local images<br />- Third-party images from public registries (for example Kafka, Redis) | A downloadable binary                                   | Incorporate the scanner as a lightweight runner in your build pipeline. Use the scanner offline and on-demand for ad hoc scanning and emergency patching. |
-| [Image registries](./registry-scanner)   | Scan images in registries (for example, Amazon ECR).         | A downloadable Docker image                              | Add a layer of defense for images that were not scanned in your build pipeline, but get published to your registry. |
+| [Image registries](./registry-scanner)   | Scan images in registries (for example, Amazon ECR).         | A downloadable Docker image                             | Add a layer of defense for images that were not scanned in your build pipeline, but get published to your registry. |

calico-cloud/image-assurance/scanners/pipeline-scanner.mdx

@@ -52,7 +52,7 @@ If you change the name of above heading, open a ticket to update the hardcoded C
    curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-linux-amd64
    ```
 
-   **MacOS**
+   **macOS**
 
    ```shell
    curl -Lo tigera-scanner {{clouddownloadbase}}/tigera-scanner/{{cloudversion}}/image-assurance-scanner-cli-darwin-amd64
@@ -77,7 +77,7 @@ You must download and set the executable flag each time you get a new version of
    ```
 ### Integrate the scanner into your build pipeline
 
-You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, Github actions). Ensure the following:
+You can include the CLI scanner in your CI/CD pipelines (for example, Jenkins, GitHub actions). Ensure the following:
 
 - Download the CLI scanner binary onto your CI runner
 - If you are running an ephemeral environment in the pipeline, include the download, and update the executable steps in your pipeline to download the scanner on every execution

calico-cloud/network-policy/beginners/calico-network-policy.mdx

@@ -68,7 +68,7 @@ metadata:
   name: allow-tcp-port-6379
 ```
 
-Because global network policies use **kind: GlobalNetworkPolicy**, they are grouped seperately from **kind: NetworkPolicy**. For example, global network policies will not be returned from `kubectl get networkpolicy.p`, and are rather returned from `kubectl get globalnetworkpolicy`.
+Because global network policies use **kind: GlobalNetworkPolicy**, they are grouped separately from **kind: NetworkPolicy**. For example, global network policies will not be returned from `kubectl get networkpolicy.p`, and are rather returned from `kubectl get globalnetworkpolicy`.
 
 ### Ingress and egress
 

calico-cloud/network-policy/hosts/host-forwarded-traffic.mdx

@@ -119,7 +119,7 @@ spec:
       - 22
 ```
 
-Save this as allow-ssh-maintenace.yaml.
+Save this as allow-ssh-maintenance.yaml.
 
 Apply the policy to the cluster:
 

calico-cloud/operations/monitor/metrics/bgp-metrics.mdx

@@ -82,7 +82,7 @@ Refer to [Configuring Prometheus](../prometheus/index.mdx) for information on ho
 
 ### BGP peers metric
 
-The metric `bgp_peers` has the relevant labels `instance`, `status` and `ip_verison`. Using this metric, you can identify how many peers have a specific BGP connection status with a given node instance and IP version. This metric will be available as a combination of `{instance, status, ip_verison}`.
+The metric `bgp_peers` has the relevant labels `instance`, `status` and `ip_version`. Using this metric, you can identify how many peers have a specific BGP connection status with a given node instance and IP version. This metric will be available as a combination of `{instance, status, ip_version}`.
 
 Example queries:
 
@@ -108,7 +108,7 @@ Valid BGP connection statuses are: "Idle", "Connect", "Active", "OpenSent", "Ope
 
 ### BGP routes imported metric
 
-The metric `bgp_routes_imported` has the relevant labels `instance` and `ip_verison`. Using this metric, you can identify how many routes are being successfully imported into a given node instance's routing table at a specific point in time. This number can increase or decrease depending on how BGP rules process incoming routes. This metric will be available as a combination of `{instance, ip_verison}`.
+The metric `bgp_routes_imported` has the relevant labels `instance` and `ip_version`. Using this metric, you can identify how many routes are being successfully imported into a given node instance's routing table at a specific point in time. This number can increase or decrease depending on how BGP rules process incoming routes. This metric will be available as a combination of `{instance, ip_version}`.
 
 Example queries:
 
@@ -126,7 +126,7 @@ irate(bgp_routes_imported{ip_version="IPv4"}[120s])
 
 ### BGP route updates received metric
 
-The metric `bgp_route_updates_received` has the relevant labels `instance` and `ip_verison`. Using this metric, you can identify the total number of BGP routes received by a given node over time. This number includes all routes that have been accepted & imported into the routing table, as well as any routes that were rejected as invalid, rejected by filters or rejected as already in the route table. This total number should only increase over time. This metric will be available as a combination of `{instance, ip_verison}`.
+The metric `bgp_route_updates_received` has the relevant labels `instance` and `ip_version`. Using this metric, you can identify the total number of BGP routes received by a given node over time. This number includes all routes that have been accepted & imported into the routing table, as well as any routes that were rejected as invalid, rejected by filters or rejected as already in the route table. This total number should only increase over time. This metric will be available as a combination of `{instance, ip_version}`.
 
 Example queries: