Line edits

Author: lootle1

learn-pr/github/create-custom-github-actions/includes/create-custom-github-action.md

@@ -83,8 +83,8 @@ As you learned previously, your action needs to have a `runs` statement that def
 
 Docker container actions require the `runs` statement to configure the image the Docker action uses with the following arguments:
 
-- `using`: Needs to be set to `docker` to run a Docker container action
-- `image`: Docker image used as the container to run the action
+- `using`: Needs to be set to `docker` to run a Docker container action.
+- `image`: Docker image used as the container to run the action.
 
 ```yml
 runs:
@@ -96,8 +96,8 @@ runs:
 
 JavaScript actions require that the `runs` statement take the following two arguments:
 
-- `using`: Application used to execute the code as defined in `main`
-- `main`: File that contains the action code; the application defined in `using` executes this file
+- `using`: Application used to execute the code as defined in `main`.
+- `main`: File that contains the action code; the application defined in `using` executes this file.
 
 For example, here's a `runs` statement for a JavaScript action using Node.js:
 
@@ -111,9 +111,9 @@ runs:
 
 Composite run steps actions require that the `runs` statement take the following three arguments:
 
-- `using`: Needs to be set to `"composite"` to run a composite run step
-- `steps`: Run steps to run the action
-- `steps[*].run`: Command you want to run (can be inline or a script in your action repository)
+- `using`: Needs to be set to `"composite"` to run a composite run step.
+- `steps`: Run steps to run the action.
+- `steps[*].run`: Command you want to run (can be inline or a script in your action repository).
 
 For example, here's a `runs` statement for a composite run steps action that will run the script at filepath `/test/script/sh`:
 

learn-pr/github/create-custom-github-actions/includes/exercise-create-custom-action.md

@@ -13,9 +13,9 @@ When you select the _Start the exercise on GitHub_ button, you'll navigate to a
 When you've finished the exercise in GitHub, return here for:
 
 > [!div class="checklist"]
-> * A quick knowledge check 
-> * A summary of what you've learned
-> * To earn a badge for completing this module
+> - A quick knowledge check 
+> - A summary of what you've learned
+> - To earn a badge for completing this module
 
 >[!NOTE]
 > You don't need to modify any of the workflow files to complete this exercise. **Altering the contents in this workflow can break the exercise's ability to validate your actions, provide feedback, or grade the results**.

learn-pr/github/create-custom-github-actions/includes/introduction.md

@@ -1,6 +1,6 @@
 GitHub Actions allow you to create individual, custom actions by writing code that interacts with your repository in any way you'd like, including integrating with GitHub's APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
 
-You can write your own custom actions to use in your workflow or share the actions you build with the GitHub community. To share actions you've built with the community, your repository must be public. Actions can run directly on compute resources (such as virtual machines) or in Docker containers. You can also define an action's inputs, outputs, and environment variables.
+You can write your own custom actions to use in your workflow, or share the actions you build with the GitHub community. To share actions you've built with the community, your repository must be public. Actions can run directly on compute resources (such as virtual machines) or in Docker containers. You can also define an action's inputs, outputs, and environment variables.
 
 In this module, you'll learn the different ways to create a custom action, its necessary metadata and syntax, and how to publish a custom action to the GitHub Marketplace.
 
@@ -22,6 +22,6 @@ This module assumes you have basic familiarity with GitHub Actions and workflows
 - The ability to navigate and edit files in GitHub
   - For more information about GitHub, see [Introduction to GitHub](https://github.com/skills/introduction-to-github).
 - Basic familiarity with GitHub Actions and workflows
-  - If you aren't familiar with workflows, jobs and steps, check out the [Automate development tasks by using GitHub Actions](/training/modules/github-actions-automate-tasks/) module
+  - If you aren't familiar with workflows, jobs and steps, check out the [Automate development tasks by using GitHub Actions](/training/modules/github-actions-automate-tasks/) module.
 - Basic familiarity with continuous integration using GitHub Actions and workflows
-  - If you're unfamiliar with continuous integration using GitHub Actions and workflows, check out [Build continuous integration workflows by using GitHub Actions](/training/modules/github-actions-ci/)
+  - If you're unfamiliar with continuous integration using GitHub Actions and workflows, check out [Build continuous integration (CI) workflows by using GitHub Actions](/training/modules/github-actions-ci/).

learn-pr/github/create-custom-github-actions/includes/publish-custom-github-action.md

@@ -16,16 +16,16 @@ When an action is in a private repository, only workflows in the same repository
 
 ## Document your action
 
-It can be very frustrating to use a new tool or application when the documentation is vague or even missing. It's important to include good documentation with your action so that others can see how it works, whether you plan to make it public or private. The first thing to do is creating a good `README.md` file for your action.
+It can be very frustrating to use a new tool or application when the documentation is vague or even missing. It's important to include good documentation with your action so that others can see how it works, whether you plan to make it public or private. The first thing to do is create a good `README.md` file for your action.
 
 The `README.md` file is often the first place developers will look at to see how the action works. This is a great place to include all of the important information for the action. The following is a non-exhaustive list of things to include:
 
-- A detailed description of what the action does
-- Required input and output arguments
-- Optional input and output arguments
-- Secrets the action uses
-- Environment variables the action uses
-- An example of how to use your action in a workflow
+- A detailed description of what the action does.
+- Required input and output arguments.
+- Optional input and output arguments.
+- Secrets the action uses.
+- Environment variables the action uses.
+- An example of how to use your action in a workflow.
 
 As a general rule, the `README.md` file should include everything a user should know to use the action. If you think it could be useful information, include it in the `README.md`.
 
@@ -35,7 +35,7 @@ If you're developing an action for other people to use, whether it's public or p
 
 ### Good practices for release and version management
 
-A good release-management strategy should include versioning recommendations. Users should not be referencing an action's default branch with the action, because the default branch which is likely to contain the latest code (which might or might not be stable) and could result in your workflow breaking. Instead, we recommend that users specify a major version when using the action, and to only direct them to a more specific version if they encounter issues. They can do this by configuring their GitHub Actions workflow to target a tag, a commit's SHA, or a specific branch named for a release. Let's take a closer look at these release options.
+A good release-management strategy should include versioning recommendations. Users should not be referencing an action's default branch with the action. This is because the default branch that's likely to contain the latest code (which might or might not be stable) could result in your workflow breaking. Instead, we recommend that users specify a major version when using the action, and to only direct them to a more specific version if they encounter issues. They can do this by configuring their GitHub Actions workflow to target a tag, a commit's SHA, or a specific branch named for a release. Let's take a closer look at these release options.
 
 #### Tags
 

learn-pr/github/create-custom-github-actions/includes/summary.md

@@ -1,4 +1,4 @@
-Your goal in this module was to understand the different types of GitHub actions and then create your own custom GitHub action and use it in a workflow.
+Your goal in this module was to understand the different types of GitHub actions, and then create your own custom GitHub action and use it in a workflow.
 
 To accomplish this goal, you first learned about the necessary metadata and syntax to write custom GitHub actions. You learned about workflow commands to extend functionality to your action, how to choose a private or public location for your action, and establishing best practices for documenting and versioning your action. You also learned how to publish your action to the GitHub Marketplace.