repo sync

Author: Octomerger

content/actions/learn-github-actions/finding-and-customizing-actions.md

@@ -79,7 +79,7 @@ steps:
 
 #### Using branches
 
-Referring to a specific branch means that the action will always use the latest updates on the target branch, but can create problems if those updates include breaking changes. This example targets a branch named `@main`:
+Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`:
 
 ```yaml
 steps:

content/packages/guides/connecting-a-repository-to-a-container-image.md

@@ -33,11 +33,11 @@ https://github.com/monalisa/hello_docker
 1. In your Dockerfile, add this line, replacing `OWNER` and `REPO` with your details:
 
  ```shell
- LABEL org.opencontainers.image.source https://github.com/<em>OWNER</em>/<em>REPO</em>
+ LABEL org.opencontainers.image.source=https://github.com/<em>OWNER</em>/<em>REPO</em>
  ```
  For example, if you're the user `monalisa` and own `my-repo`, you would add this line to your Dockerfile:
  ```shell
- LABEL org.opencontainers.image.source https://github.com/monalisa/my-repo
+ LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo
  ```
  For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository.
 

data/reusables/organizations/can-require-ssh-cert.md

@@ -1 +1 @@
-You can require that members use SSH certificates to access organization resources,, unless SSH is disabled in your repository.
+You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository.