Apply suggestions from code review

Commit changes from @Chukslord1

Co-authored-by: Chukslord <[email protected]>

Author: ktoliver

learn-pr/github/github-actions-ci/includes/2-github-actions-workflows-ci.md

@@ -77,8 +77,6 @@ To learn more about npm, check out the npm documentation:
 
 A team of developers can benefit from using reusable workflows to streamline and standardize repeated automation steps. By using reusable workflows, you can reduce redundancy, improve maintainability, and ensure consistency across your continuous integration/continuous deployment (CI/CD) pipelines.
 
-<!-- InfoMagnus Starts -->
-<!-- INFOMAGNUS UPDATES for sub OD 1.5.9. Source Material: https://docs.github.com/en/actions/sharing-automations/reusing-workflows -->
 
 ## Avoid duplication by using reusable workflows
 
@@ -137,8 +135,6 @@ By understanding how reusable workflows function and their benefits, you can ado
 
 Reusable workflows are a powerful way to enforce consistency, reduce duplication, and scale DevOps practices in any engineering team. Whether you're managing a single repository, microservices, or open-source libraries, reusable workflows can simplify automation, so your CI/CD is faster, cleaner, and easier for you to manage.
 
-<!-- INFOMAGNUS UPDATES for sub OD 2.1.1, 2.1.2, 2.1.3, and 2.1.4 go here. Source Material: Infomagnus team to find source material and cite it.
-https://docs.github.com/en/actions/writing-workflows/about-workflows , https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs , https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/triggering-a-workflow , https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/viewing-workflow-run-history , https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/troubleshooting-workflows/about-troubleshooting-workflows -->
 
 ## Identify the event that triggered a workflow
 
@@ -406,12 +402,7 @@ test:
       CI: true
 ```
 
-<!-- INFOMAGNUS UPDATES for sub OD 2.2.1 go here. Source Material: Infomagnus team to find source material and cite sources when they update material 
-https://docs.github.com/en/actions/writing-workflows/about-workflows -->
 
-<!-- ## Locate a workflow in a repository -->
-
-<!-- InfoMagnus END -->
 
 ## Work with artifacts
 

learn-pr/github/github-actions-ci/includes/2b-github-actions-essential-features.md

@@ -26,7 +26,6 @@ jobs:
 
 This example is using the `github.ref` context to check the branch that triggered the workflow. If the branch is `main`, the runner is executed and prints "Deploying to production server on branch $GITHUB_REF." The default environment variable `$GITHUB_REF` is used in the runner to refer to the branch. Notice that default environment variables are all uppercase where context variables are all lowercase.
 
-<!-- INFOMAGNUS UPDATES for sub OD 1.4.2 go here. Source Material: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs -->
 
 ## Contextual information available in a workflow
 
@@ -90,7 +89,6 @@ The following table lists restrictions for each context and special function in
 |`on.workflow_call.inputs.<inputs_id>.default` | `github`, `inputs`, `vars` | None |
 |`on.workflow_call.outputs.<output_id>.value` | `github`, jobs, `vars`, `inputs` | None |
 
-<!-- INFOMAGNUS 1.4.2 END
 
 ## Custom environment variables
 
@@ -109,7 +107,6 @@ jobs:
           First_Name: Mona
 ```
 
-<!-- INFOMAGNUS UPDATES for sub OD 1.4.3, 1.4.6, and 1.4.7 go here. Source Material: Infomagnus team to find source material and cite sources when they update material , https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables , https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#setting-an-environment-variable -->
 ## Set custom environment variables in a workflow
 
 You can define environment variables that are scoped to the entire workflow by using `env` at the top level of the workflow file. Scope the contents of a job within a workflow by using `jobs.<job_id>.env`. You can scope an environment variable at a specific step within a job by using `jobs.<job_id>.steps[*].env`.
@@ -350,7 +347,6 @@ For example, a `GET` request to view a specific workflow run log follows this pa
 GET /repos/{owner}/{repo}/actions/runs/{run_id}/logs
 ```
 
-<!-- INFOMAGNUS UPDATES for sub OD 1.4.4 go here. Source Material: Infomagnus team to find source material and cite sources when they update material   https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-an-installation-access-token-for-a-github-app  ,  https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation -->
 
 ## Identify when to use an installation token from a GitHub app