edits

Author: v-albemi

learn-pr/github/automate-github-using-github-script/includes/2-what-is-github-script.md

@@ -2,7 +2,7 @@ In this unit, you'll learn how GitHub Script enables you to automate common GitH
 
 ## What is GitHub Script?
 
-[GitHub Script](https://github.com/actions/github-script?azure-portal=true) is an action that provides an authenticated [Octokit](https://octokit.github.io/rest.js/?azure-portal=true) client and enables JavaScript to be written directly in a workflow file. It runs in [Node.js](https://nodejs.org/?azure-portal=true), so you have the power of that platform available when writing scripts.
+[GitHub Script](https://github.com/actions/github-script?azure-portal=true) is an action that provides an authenticated [Octokit](https://octokit.github.io/rest.js/?azure-portal=true) client and enables JavaScript to be written directly in a workflow file. It runs in [Node.js](https://nodejs.org/?azure-portal=true), so you have the power of that platform available when you write scripts.
 
 ## What is Octokit?
 
@@ -72,7 +72,7 @@ In this case, there's only one step: the GitHub Script action.
             })
 ```
 
-Using GitHub Actions can really help automate the events that take place in your repositories. Imagine that a repository visitor created a new issue containing information about a critical bug. You might want to thank them for bringing the bug to your attention, but this simple task can become overwhelming as your repository attracts more visitors. By automating an issue comment, you can automate the process of thanking visitors every time.
+Using GitHub Actions can really help automate the events that take place in your repositories. Imagine that a repository visitor opened a new issue containing information about a critical bug. You might want to thank them for bringing the bug to your attention, but this simple task can become overwhelming as your repository attracts more visitors. By automating an issue comment, you can automate the process of thanking visitors every time.
 
 ### Using actions/[email protected]
 
@@ -82,7 +82,7 @@ This action requires a `github-token` that's provided at runtime so that request
 
 The `script` parameter can be virtually any JavaScript that uses the octokit/rest/js client stored in `github`. In this case, it's just one line (split across multiple lines for readability) that creates a hardcoded comment.
 
-After the workflow runs, GitHub Script logs the code it ran for review on the **Actions** tab.
+After the workflow runs, GitHub Script logs the code it ran for review on the **Actions** tab:
 
 ![Screenshot of a completed GitHub Script workflow.](../media/2-completed-workflow.png)
 

learn-pr/github/automate-github-using-github-script/includes/3-use-github-script.md

@@ -40,7 +40,7 @@ One advantage of breaking the current workflow into multiple steps is that it en
 
 To separate the example workflow into steps:
 
-- Name each step so that you can track it from the Actions tab.
+- Name each step so that you can track it from the **Actions** tab.
 - Use expressions to determine whether a step should run (optional).
 
 In this example, the two tasks in the original workflow file are separated into individual steps:
@@ -78,15 +78,15 @@ jobs:
             });
 ```
 
-Each step includes a descriptive `name` element that also helps you track it from the Actions tab.
+Each step includes a descriptive `name` element that also helps you track it from the **Actions** tab.
 
 The `Add issue to project board` step also includes an `if` statement that specifies that the issue should be added to the project board only if it's labeled `bug`.
 
 ## Use the Node.js environment
 
 GitHub Script also grants you access to a full Node.js environment. Although we don't recommend using GitHub Script to write the logic for complex actions, you can use it to add more functionality to the octo/rest.js API.
 
-For example, you could use the Node.js to display a contribution guide whenever an issue is opened. You can use the Node.js file system to read a file and use it as the body of the issue comment. To access files within the repository, include the `actions/checkout` action as the first step in the workflow.
+For example, you could use Node.js to display a contribution guide whenever an issue is opened. You can use the Node.js file system to read a file and use it as the body of the issue comment. To access files within the repository, include the `actions/checkout` action as the first step in the workflow.
 
 The following example makes the following changes to the workflow file: