small typo fixes (#1528)

Signed-off-by: jacobdonenfeld <jedonenfeld@gmail.com>

Author: jacobdonenfeld

CONTRIBUTING.md

@@ -27,7 +27,7 @@ When your PR is ready for review and merging, ensure your commit messages and st
 
 Regarding the commit message: follow best practices. Here are two good resources for writing good commit messages:
 - [How to Write a Git Commit Message](https://cbea.ms/git-commit/)
-- [Git-scm.com's "Commit guildelines"](ttps://www.git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines)
+- [Git-scm.com's "Commit guidelines"](ttps://www.git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines)
 
 From the first resource, here are the seven rules of a great commit message:
 

docs/docs/100-reference/02-admin/03-computeclasses.md

@@ -41,6 +41,6 @@ affinity: # The same affinity fields for Pods
 If `memory.min`, `memory.max`, `memory.values`, `affinity`, and `tolerations` are not given, then there are no scheduling rules for workloads using the compute class. 
 
 ## Cluster Compute Classes
-Cluster Compute Classes are exactly the same as Project Compute Classes except that they are not namespaced. This means that Cluster Woerkload Classes are available to every app running in your cluster.
+Cluster Compute Classes are exactly the same as Project Compute Classes except that they are not namespaced. This means that Cluster Workload Classes are available to every app running in your cluster.
 
 Similar to Project Compute Classes, there can be only one default for the entire cluster. However, there can be a default Cluster Compute Class and a default Project Compute Class for any project; the Project Compute Class default will take precedence in this situation. Similarly, if a Cluster Compute Class and a Project Compute Class exist with the same name, then the Project Compute Class will take precedence. These rules are applied when deploying apps and also when using the [`acorn offerings volumeclasses`](100-reference/01-command-line/acorn_offerings_computeclasses.md) command.

docs/docs/100-reference/03-acornfile.md

@@ -255,7 +255,7 @@ containers: db: {
 `ports` defines which ports are available on the container and the default level of access. Ports
 are defined with three different access modes: internal, expose, publish. Internal ports are only available
 to the containers within an Acorn. Expose(d) ports are available to services within the cluster. And
-publish ports are available publically outside the cluster. The access mode defined in the Acornfile is
+publish ports are available publicly outside the cluster. The access mode defined in the Acornfile is
 just the default behavior and can be changed at deploy time.
 ```acorn
 containers: web: {
@@ -450,7 +450,7 @@ containers: web: {
 ```
 
 ### memory
-`memory` allows you to specify how much memory the container should run with. It can be abreviated to `mem`. If left unspecified, it will be defaulted to the installation default (see the [reference documentation for memory](06-compute-resources.md#memory) for more information).
+`memory` allows you to specify how much memory the container should run with. It can be abbreviated to `mem`. If left unspecified, it will be defaulted to the installation default (see the [reference documentation for memory](06-compute-resources.md#memory) for more information).
 
 ```acorn
 containers: {
@@ -676,7 +676,7 @@ secrets: "my-token": {
 }
 ```
 ### data
-`data` defines the keys and non-senstive values that will be used by the secret.
+`data` defines the keys and non-sensitive values that will be used by the secret.
 Refer to [the secrets documentation](38-authoring/05-secrets.md) for
 descriptions of the different secret types and how to use data keys and values.
 
@@ -701,7 +701,7 @@ secrets: {
 
 ## args
 
-`args` defines arguements that can be modified at build or runtime by the user.
+`args` defines arguments that can be modified at build or runtime by the user.
 Arguments to an Acorn can be standard strings, ints, bools, and other complex types. To define an argument,
 specify a name and a default value. The type will be inferred from the default value.
 

docs/docs/100-reference/06-compute-resources.md

@@ -50,7 +50,7 @@ You can configure Acorn apps to have a set compute class upon startup.
 
 Setting a compute class allows you to define what the infrastructure providing your Acorn workloads should look like. Things that compute classes control include:
 
-- What OS/Architecure your workloads will run on
+- What OS/Architecture your workloads will run on
 - How much memory is minimal, maximal, default and allowed
 - How many vCPUs should be allocated
 
@@ -78,7 +78,7 @@ Breaking this down:
     1. `-` denotes a range and any value within it can be specified.
     2. `,` denotes specific values that are the only ones allowed.
 
-Specifying compute classes can be done in the Acornfile (using the [class property](03-acornfile.md#class) for containers) or at runtime (using the [--compute-class flag](50-running/55-compute-resources.md#compute-class)). If you do not specify a compute class, the default compute class for the project will be used. If there is no default for the project, the default for the cluster will be used. Finally, if there is no cluster default then no compute class will be used. Depending on the compute class that is used, the memory that you specify may be in contention with its requirements. Should that happen Acorn will provide a descriptive error message to ammend any issues.
+Specifying compute classes can be done in the Acornfile (using the [class property](03-acornfile.md#class) for containers) or at runtime (using the [--compute-class flag](50-running/55-compute-resources.md#compute-class)). If you do not specify a compute class, the default compute class for the project will be used. If there is no default for the project, the default for the cluster will be used. Finally, if there is no cluster default then no compute class will be used. Depending on the compute class that is used, the memory that you specify may be in contention with its requirements. Should that happen Acorn will provide a descriptive error message to amend any issues.
 
 :::note
 Looking to manage a compute class? This should only be done if you are (or are in communication with) an administrator of Acorn. You can read more information about managing compute classes [here](02-admin/03-computeclasses.md)

docs/docs/38-authoring/00-overview.md

@@ -113,7 +113,7 @@ localData: {
 
 Strings can be a single line or multiline.  A single line string is surrounded by `"` quotes.
 
-Multiline strings are enclosed in triple quotes `"""`. The opening `"""` must be followed by a newline. The closing `"""` must also be on it's own line. The whitespace directly preceding the closing quotles must match the preceding whitespace on all other lines and is not included in the value.  This allows you to indent the text to match current level without the indenting becoming part of the actual value.
+Multiline strings are enclosed in triple quotes `"""`. The opening `"""` must be followed by a newline. The closing `"""` must also be on it's own line. The whitespace directly preceding the closing quotes must match the preceding whitespace on all other lines and is not included in the value.  This allows you to indent the text to match current level without the indenting becoming part of the actual value.
 
 ```acorn
 singleLine: "Hi!"
@@ -278,10 +278,10 @@ All the basic math and comparison operators you'd find in a typical programming
 | :--------|:--------|:--------|:-------|
 | Addition | `+` | `1 + 1` | `2` |
 | Subtraction | `-` | `4 - 1` | `3` |
-| Muliplication | `*` | `4 * 2` | `8` |
+| Multiplication | `*` | `4 * 2` | `8` |
 | Division | `/` | `5 / 2` | `2.5`|
 | Greater than | `>` | `2 > 1` | `true` |
-| Grather than or equal | `>=` | `2 >= 2` | `true` |
+| Greater than or equal | `>=` | `2 >= 2` | `true` |
 | Less than | `<` | `1 < 1` | `false` |
 | Less than or equal | `<=` | `1 <= 1` | `true` |
 | Equals | `==` | `1 == 2` | `false` |
@@ -363,7 +363,7 @@ containers: {
 }
 ```
 
-See the [function libarary](../reference/functions#ifelse) for more information.
+See the [function library](../reference/functions#ifelse) for more information.
 
 ## For loops
 

docs/docs/38-authoring/03-containers.md

@@ -363,7 +363,7 @@ The `memory` property can be abbreviated to `mem` in the file.
 
 ## Compute Classes
 
-When you want to specify what infrastructure your Acorn's workload will run on, you use Compute Classes. You can set the class of a workload by defining by the `class` property defineable on all workloads (`containers` and `jobs`). Check out the [compute class documemtation](100-reference/06-compute-resources.md#compute-classes) for more information.
+When you want to specify what infrastructure your Acorn's workload will run on, you use Compute Classes. You can set the class of a workload by defining by the `class` property definable on all workloads (`containers` and `jobs`). Check out the [compute class documentation](100-reference/06-compute-resources.md#compute-classes) for more information.
 
 ```acorn
 containers: {

docs/docs/38-authoring/05-secrets.md

@@ -120,7 +120,7 @@ Acorn makes multiple types of secrets available to the Acorn author.
  1. **Template:** Used to store configuration files that contain sensitive information.
  1. **Token:** Used to generate and/or store long secret strings.
  1. **Generated:** Used to take the output of a `job` and pass along as a secret bit of info.
- 1. **Opaque:** A generic secret that can store defaults in the Acorn, or is meant to be overriden by the user to pass unknown/unstructured sensitive data.
+ 1. **Opaque:** A generic secret that can store defaults in the Acorn, or is meant to be overridden by the user to pass unknown/unstructured sensitive data.
 
 ### Basic secrets
 

docs/docs/38-authoring/09-permissions.md

@@ -65,7 +65,7 @@ Physically defining the permissions of your application, `rules` get converted i
 Similar to `rules`, `clusterRules` define permissions in the application's namespace but with the added benefit of working in other ones as well. Instead of creating a `Role` that gets attached to your application's `ServiceAccount`, you get a `ClusterRole`. If you would like to allow your application to perform the defined rules in any namespace on the cluster then `clusterRules` are the way to go.
 
 ## Verbs
-To define what actions your application can perform on a given resource, you define a `verb`. These `verbs` are words that allow you to declaritively define what actions your application can perform on given resources.
+To define what actions your application can perform on a given resource, you define a `verb`. These `verbs` are words that allow you to declaratively define what actions your application can perform on given resources.
 
 :::info
 Wondering what verbs are available? Take a look!

docs/docs/39-publishing.md

@@ -55,7 +55,7 @@ acorn login index.docker.io
 acorn login ghcr.io
 ```
 
-You will be prompted for your username and password to login. If your company has an internal registry you can login subtituting `ghcr.io` for your organizations registry domain.
+You will be prompted for your username and password to login. If your company has an internal registry you can login substituting `ghcr.io` for your organizations registry domain.
 
 ### Push the image
 

docs/docs/50-running/20-labels.md

@@ -2,7 +2,7 @@
 title: Labels and Annotations
 ---
 
-As mentioned in the [authoring section](38-authoring/20-labels.md), you can add labels and annotations to your Acorns that will then be propogated down to the core Kubernetes resources created by Acorn. Authors of Acorn images can add these directly to the Acornfile, but users can also add them at runtime.
+As mentioned in the [authoring section](38-authoring/20-labels.md), you can add labels and annotations to your Acorns that will then be propagated down to the core Kubernetes resources created by Acorn. Authors of Acorn images can add these directly to the Acornfile, but users can also add them at runtime.
 
 The flags for adding labels and annotations allow you to specify the resource type and name you are targeting. This is best explained through examples: