Branch was updated using the 'autoupdate branch' Actions workflow.

Author: Octomerger

content/actions/guides/caching-dependencies-to-speed-up-workflows.md

@@ -184,8 +184,8 @@ For example, if a pull request contains a `feature` branch (the current scope) a
 1. Key `npm-feature-` in the `feature` branch scope
 2. Key `npm-` in the `feature` branch scope
 1. Key `npm-feature-d5ea0750` in the `main` branch scope
-3. Key `npm-d5ea0750` in the `main` branch scope
-4. Key `npm` in the `main` branch scope
+3. Key `npm-feature-` in the `main` branch scope
+4. Key `npm-` in the `main` branch scope
 
 ### Usage limits and eviction policy
 

content/actions/reference/workflow-commands-for-github-actions.md

@@ -254,12 +254,12 @@ echo "action_state=yellow" >> $GITHUB_ENV
 Running `$action_state` in a future step will now return `yellow`
 
 #### Multline strings
-For multiline strings, you may use a delimeter with the following syntax. 
+For multiline strings, you may use a delimiter with the following syntax. 
 
 ```
-{name}<<{delimeter}
+{name}<<{delimiter}
 {value}
-{delimeter}
+{delimiter}
 ```
 
 #### Example

content/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images.md

@@ -20,7 +20,7 @@ To push and pull container images owned by an organization, an organization admi
 
 This example pushes the latest version of `IMAGE-NAME`.
   ```shell
-  $ docker push ghcr.io/OWNER/IMAGE_NAME.latest
+  $ docker push ghcr.io/OWNER/IMAGE_NAME:latest
   ```
 
 This example pushes the `2.5` version of the image.
@@ -42,7 +42,7 @@ To ensure you're always using the same image, you can specify the exact containe
   ```
 2. Remove image locally as needed.
   ```shell
-  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME.latest
+  $ docker rmi  ghcr.io/OWNER/IMAGE_NAME:latest
   ```
 
 3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.