diff --git a/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/content/actions/creating-actions/dockerfile-support-for-github-actions.md
index 1488948e86..ef78f50fe4 100644
--- a/content/actions/creating-actions/dockerfile-support-for-github-actions.md
+++ b/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -79,7 +79,7 @@ ENTRYPOINT ["/entrypoint.sh"]
 
 Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
 
-``` sh
+```shell
 #!/bin/sh
 
 # `$#` expands to the number of arguments and `$@` expands to the supplied `args`
@@ -90,13 +90,13 @@ printf '\n'
 
 Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
 
-``` sh
+```shell
 chmod +x entrypoint.sh
 ```
 
 When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
 
-``` sh
+```shell
 Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
 ```
 
diff --git a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
index 7bae83b411..95f283b635 100644
--- a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
+++ b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -43,12 +43,16 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
    For example, using [the AWS CLI](https://aws.amazon.com/cli/):
 
-   {% raw %}```bash copy
+   {% raw %}
+
+   ```bash copy
    aws ecr create-repository \
        --repository-name MY_ECR_REPOSITORY \
        --region MY_AWS_REGION
 
-   ```{% endraw %}
+   ```
+
+   {% endraw %}
 
    Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
 
@@ -64,10 +68,15 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
    The format of the file should be the same as the output generated by:
 
-   {% raw %}```bash copy
+   {% raw %}
+
+   ```bash copy
+   
    aws ecs register-task-definition --generate-cli-skeleton
 
-   ```{% endraw %}
+   ```
+
+   {% endraw %}
 
    Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
 
diff --git a/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md b/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md
index 262feaec03..bb8e217d9b 100644
--- a/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md
+++ b/content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md
@@ -300,7 +300,7 @@ gh actions-importer audit circle-ci --output-dir ./output/ --include-from reposi
 
 The file supplied for this parameter must be a a line-delimited list of repositories, for example:
 
-```txt
+```text
 repository_one
 repository_two
 repository_three