diff --git a/.octopus/deployment_process.ocl b/.octopus/deployment_process.ocl
index c7cc040c..f6207634 100644
--- a/.octopus/deployment_process.ocl
+++ b/.octopus/deployment_process.ocl
@@ -93,7 +93,7 @@ step "Queue and verify a test build" {
                 $tokenBytes = [System.Text.Encoding]::UTF8.GetBytes(":$AccessToken");
                 $base64Pat = [System.Convert]::ToBase64String($tokenBytes);
                 
-                $builParameters =  ConvertTo-Json @{
+                $buildParameters =  ConvertTo-Json @{
                   "system.debug" = "true"
                   "BuildConfiguration" = "debug"
                   "BuildPlatform" = "x64"
@@ -104,7 +104,7 @@ step "Queue and verify a test build" {
                         "id" = $TestProjectDefinitionId
                     }
                     "sourceBranch" = "refs/heads/master"
-                    "parameters" = $builParameters
+                    "parameters" = $buildParameters
                 } -Depth 100
                 
                 #$postData = '{"definition": {"id": ' + $TestProjectDefinitionId + ',"sourceBranch": "refs/heads/master", "parameters": "{\"system.debug\":\"true\",\"BuildConfiguration\":\"debug\",\"BuildPlatform\":\"x64\"}"}"}'
diff --git a/README.md b/README.md
index fc762937..5fada273 100644
--- a/README.md
+++ b/README.md
@@ -20,7 +20,7 @@ This extension provides a friendly interface to the [Octopus CLI](https://g.octo
 
 ## Dev
 
-Microsoft TFS/ADO web extensions are powered by Node.js under the hood. Simply open the repo with your favourite text editor like [Jetbrains WebStorm](https://jetbrains.com/webstorm) or [Visual Studio Code](https://code.visualstudio.com/) and you're good to go.
+Microsoft TFS/ADO web extensions are powered by Node.js under the hood. Simply open the repo with your favourite text editor like [JetBrains WebStorm](https://jetbrains.com/webstorm) or [Visual Studio Code](https://code.visualstudio.com/) and you're good to go.
 
 ## Building
 
diff --git a/source/tasks/Deploy/DeployV6/task.json b/source/tasks/Deploy/DeployV6/task.json
index 21643ec9..29a882a6 100644
--- a/source/tasks/Deploy/DeployV6/task.json
+++ b/source/tasks/Deploy/DeployV6/task.json
@@ -71,7 +71,7 @@
             "label": "Values for prompted variables",
             "defaultValue": "",
             "required": false,
-            "helpMarkDown": "Variable values to pass to the the deployment, use syntax `variable: value`"
+            "helpMarkDown": "Variable values to pass to the deployment, use syntax `variable: value`"
         },
         {
             "name": "UseGuidedFailure",
diff --git a/source/tasks/DeployTenant/TenantedDeployV6/task.json b/source/tasks/DeployTenant/TenantedDeployV6/task.json
index bbfdff08..3ce7ea41 100644
--- a/source/tasks/DeployTenant/TenantedDeployV6/task.json
+++ b/source/tasks/DeployTenant/TenantedDeployV6/task.json
@@ -87,7 +87,7 @@
             "label": "Values for prompted variables",
             "defaultValue": "",
             "required": false,
-            "helpMarkDown": "Variable values to pass to the the deployment, use syntax `variable: value`"
+            "helpMarkDown": "Variable values to pass to the deployment, use syntax `variable: value`"
         },
         {
             "name": "UseGuidedFailure",
diff --git a/source/vsts.md b/source/vsts.md
index 4400776a..07755ff6 100644
--- a/source/vsts.md
+++ b/source/vsts.md
@@ -222,7 +222,7 @@ Options include:
 
 ## Version 6 of Deploy Release step
 
-From version 6, the deploy release step is split into two seperate functions for normal deployments and tenanted deployments
+From version 6, the deploy release step is split into two separate functions for normal deployments and tenanted deployments
 
 ### <a name="deploy-octopus-release"></a>![Deploy Release Image](img/octopus_deploy-02.png) Deploy Octopus Release (v6 or later)
 
@@ -306,7 +306,7 @@ The `Step` input parameter needs to be set to the `name` of the deployment step
 
 | Name                               | Description                                                                                                                                                                                                      |
 | :--------------------------------- |:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `completed_successfully`           | True if all execution tasks completed succcessfully, false if any execution tasks failed.                                                                                                                        |
+| `completed_successfully`           | True if all execution tasks completed successfully, false if any execution tasks failed.                                                                                                                        |
 | `server_task_results`              | JSON representation of the tasks and their success. Schema: { "serverTaskId": <task id>, "tenantName": <tenant name>, "environmentName": <environment name>, "successful": <true/false> }                        |
 | `<context>.completed_successfully` | Contextual success flag for each task using the name of the environment or tenant, e.g `production.completed_successfully` or `uat_tenant.completed_successfully`. Spaces in names are replaced with underscores |