Fix typos

Makefile.toml

@@ -62,7 +62,7 @@ PUBLISH_UNIFIED_VOLUME_SIZE = "22"
 # tools/pubsys/policies/ssm/README.md for more information.
 PUBLISH_SSM_TEMPLATES_PATH = "${BUILDSYS_ROOT_DIR}/tools/pubsys/policies/ssm/defaults.toml"
 
-# This can be overriden with -e to change the source path
+# This can be overridden with -e to change the source path
 # for the Licenses.toml file
 BUILDSYS_LICENSES_CONFIG_PATH = "${BUILDSYS_ROOT_DIR}/Licenses.toml"
 
@@ -1515,7 +1515,7 @@ script = [
    '''
 ]
 
-# This task will retrieve testsys logs from a test. You can add `--follow` to continue to recieve
+# This task will retrieve testsys logs from a test. You can add `--follow` to continue to receive
 # logs as they come in.
 [tasks.log-test]
 dependencies = ["test-tools"]

QUICKSTART-ECS.md

@@ -200,7 +200,7 @@ If you want to customize the behavior of your instance further, you can find the
 Now we can launch a Bottlerocket instance in our cluster!
 
 There are a few values to make sure you change in this command:
-* YOUR_KEY_NAME: your SSH keypair name, as registered with EC2
+* YOUR_KEY_NAME: your SSH key pair name, as registered with EC2
 * SUBNET_ID: the subnet you selected earlier
   * If you chose a public subnet, either add `--associate-public-ip-address` to the command, or attach an Elastic IP afterward.
 * BOTTLEROCKET_AMI_ID: the Amazon-provided AMI ID you found above, or the ID of an AMI you registered

QUICKSTART-EKS.md

@@ -31,7 +31,7 @@ If you have a recent `eksctl`, as mentioned above, most of Bottlerocket setup fo
 eksctl can use a configuration file to simplify setup.
 We have sample configuration files in the repo:
 * [`sample-eksctl.yaml`](sample-eksctl.yaml) - recommended for most setups.
-* [`sample-eksctl-ssh.yaml`](sample-eksctl-ssh.yaml) - for test clusters where you know you'll want SSH access.  Make sure to change the `publicKeyName` setting to the name of the SSH keypair you have registered with EC2.
+* [`sample-eksctl-ssh.yaml`](sample-eksctl-ssh.yaml) - for test clusters where you know you'll want SSH access.  Make sure to change the `publicKeyName` setting to the name of the SSH key pair you have registered with EC2.
 
 Pick the file most appropriate for you and make a copy, for example `my-eksctl.yaml`.
 In this file you can change your desired numbered of nodes and even set Bottlerocket settings in advance if you like.  The 'settings' section under 'bottlerocket' can include any [Bottlerocket settings](https://github.com/bottlerocket-os/bottlerocket/#description-of-settings).
@@ -344,7 +344,7 @@ If you chose a private subnet and you want to SSH in, you can do so from another
 Now we can launch a Bottlerocket instance in our cluster!
 
 There are a few values to make sure you change in this command:
-* YOUR_KEY_NAME: your SSH keypair name, as registered with EC2
+* YOUR_KEY_NAME: your SSH key pair name, as registered with EC2
 * SUBNET_ID: the subnet you selected earlier
   * If you chose a public subnet, either add `--associate-public-ip-address` to the command, or attach an Elastic IP afterward.
 * SECURITY_GROUP_ID_1, SECURITY_GROUP_ID_2: the two security groups you found earlier

sources/api/netdog/src/main.rs

@@ -412,7 +412,7 @@ where
     let interface = interface.as_ref();
     let path = path.as_ref();
     // TODO if we accumulate more of these we should have a better way to create than format!()
-    // Note: The dash (-) preceeding the "net..." variable assignment below is important; it
+    // Note: The dash (-) preceding the "net..." variable assignment below is important; it
     // ensures failure to set the variable for any reason will be logged, but not cause the sysctl
     // service to fail
     // Accept router advertisement (RA) packets even if IPv6 forwarding is enabled on interface

sources/api/netdog/src/net_config/mod.rs

@@ -1,4 +1,4 @@
-//! The net_config module contains the strucures needed to deserialize a `net.toml` file.  It also
+//! The net_config module contains the structures needed to deserialize a `net.toml` file.  It also
 //! includes contains the `FromStr` implementations to create a `NetConfig` from string, like from
 //! the kernel command line.
 //!

sources/api/prairiedog/src/error.rs

@@ -99,7 +99,7 @@ pub(super) enum Error {
     ParentBootConfigKey,
 
     #[snafu(display(
-        "Encounted unbalanced quotes when processing array elements in '{}'",
+        "Encountered unbalanced quotes when processing array elements in '{}'",
         input
     ))]
     UnbalancedQuotes { input: String },