Fix reviewdog highlights

Author: jesp209i

umbraco-cloud/set-up/project-settings/umbraco-cicd/ArtifactBestPractice.md

@@ -3,7 +3,7 @@ The zip package you are deploying needs to contain all things that normally is p
 
 Every new Umbraco Cloud project contains a readme.md file which explains the structure and how you can adapt it to suit your needs.
 
-The sample scripts on github includes a way to package the zip. As the scripts are samples they show a universal way to do this which works well for most people. But not all projects are alike, and you may not want to use that particular approach.
+The sample scripts on GitHub includes a way to package the zip. As the scripts are samples they show a universal way to do this which works well for most people. But not all projects are alike, and you may not want to use that particular approach.
 
 ## Do not include Dotnet Binaries
 Don’t include any binary build artifacts coming from the DotNet build/publish process. 
@@ -16,7 +16,7 @@ The folder will be ignored in the isolated instance, including the extra megabyt
 Also consider the artifact size limitation below. 
 
 ## Do include the finished frontend assets
-If you are using modern frontend build tools, ideally only include the finished frontend assets that are actually needed. No need to include javascript or typescript source files if you need to build the frontend. 
+If you are using modern frontend build tools, ideally only include the finished frontend assets that are needed. No need to include JavaScript or TypeScript source files if you need to build the frontend. 
 
 ## Keep the Artifact as small as possible
 It is good practice to keep the zipped artifact as small as possible. 

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-azure-devops.md

@@ -216,7 +216,7 @@ There are a couple of things here to be aware of:
 * We have a special `cloud.zipignore` file. This is a convenient way to tell the pipeline which files **not** to include when creating the zip package to send to cloud.
 
 {% hint style="info" %}
-If you have frontend assets that needs to be built (using tools like npm/yarn or others), you should add the needed steps before `Zip Source Code`. This is to ensure that the fresh frontend assets will be part of the package to be sent to Umbraco Cloud.
+If you have frontend assets that needs to be built (using npm/yarn or other tools), add the needed steps before `Zip Source Code`. This ensures that the fresh frontend assets will be part of the package to be sent to Umbraco Cloud.
 {% endhint %}
 
 ## Further information

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-github-actions.md

@@ -233,7 +233,7 @@ There are a couple of things here to be aware of:
 * We have a special `cloud.zipignore` file. This is a convenient way to tell the pipeline which files **not** to include when creating the zip package to send to cloud.
 
 {% hint style="info" %}
-If you have frontend assets that needs to be build (using tools like npm/yarn or others), you should add the needed steps before `Zip Source Code`. This is to ensure that the fresh frontend assets will be part of the package to be sent to cloud.
+If you have frontend assets that needs to be built (using npm/yarn or other tools), add the needed steps before `Zip Source Code`. This ensures that the fresh frontend assets will be part of the package to be sent to Umbraco Cloud.
 {% endhint %}
 
 ## Further information