Fix typo, s/hit/click, remove whitespacesautodevops-docs-update

1 files changed, 19 insertions, 20 deletions

diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index 12fa1f26338..4d4832184e2 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -2,8 +2,8 @@
 
 > [Introduced][ce-37115] in GitLab 10.0. Generally available on GitLab 11.0.
 
-Auto DevOps provides pre-defined CI/CD configuration which allows you to automatically detect, build, test, 
-deploy, and monitor your applications. Leveraging CI/CD best practices and tools, Auto DevOps aims 
+Auto DevOps provides pre-defined CI/CD configuration which allows you to automatically detect, build, test,
+deploy, and monitor your applications. Leveraging CI/CD best practices and tools, Auto DevOps aims
 to simplify the setup and execution of a mature & modern software development lifecycle.
 
 ## Overview
@@ -28,9 +28,9 @@ If you are using GitLab.com, see the [quick start guide](quick_start_guide.md)
 for how to use Auto DevOps with GitLab.com and a Kubernetes cluster on Google Kubernetes
 Engine (GKE).
 
-If you are using a self-hosted instance of GitLab, you will need to configure the 
-[Google OAuth2 OmniAuth Provider](https://docs.gitlab.com/ee/integration/google.html) before 
-you can configure a cluster on GKE. Once this is set up, you can follow the steps on the 
+If you are using a self-hosted instance of GitLab, you will need to configure the
+[Google OAuth2 OmniAuth Provider](../../integration/google.md) before
+you can configure a cluster on GKE. Once this is set up, you can follow the steps on the
 [quick start guide](quick_start_guide.md) to get started.
 
 ## Comparison to application platforms and PaaS
@@ -205,22 +205,22 @@ other environments.
 
 ## Enabling/Disabling Auto DevOps
 
-When first using Auto Devops, review the [requirements](#requirements) to ensure all necessary components to make 
+When first using Auto Devops, review the [requirements](#requirements) to ensure all necessary components to make
 full use of Auto DevOps are available. If this is your fist time, we recommend you follow the
 [quick start guide](quick_start_guide.md).
 
-GitLab.com users can enable/disable Auto DevOps at the project-level only. Self-managed users 
+GitLab.com users can enable/disable Auto DevOps at the project-level only. Self-managed users
 can enable/disable Auto DevOps at either the project-level or instance-level.
 
 ### Enabling/disabling Auto DevOps at the instance-level (Administrators only)
 
-1. Go to **Admin area > Settings > Continuous Integration and Deployment**
+1. Go to **Admin area > Settings > Continuous Integration and Deployment**.
 1. Toggle the checkbox labeled **Default to Auto DevOps pipeline for all projects**.
 1. If enabling, optionally set up the Auto DevOps [base domain](#auto-devops-base-domain) which will be used for Auto Deploy and Auto Review Apps.
 1. Click **Save changes** for the changes to take effect.
 
 NOTE: **Note:**
-Even when disabled at the instance level, project maintainers are still able to enable 
+Even when disabled at the instance level, project maintainers are still able to enable
 Auto DevOps at the project level.
 
 ### Enabling/disabling Auto DevOps at the project-level
@@ -230,8 +230,8 @@ Auto DevOps at the project level.
 1. Check the **Default to Auto DevOps pipeline** checkbox.
 1. Optionally, but recommended, add in the [base domain](#auto-devops-base-domain)
    that will be used by Auto DevOps to [deploy your application](#auto-deploy)
-   and choose the [deployment strategy](#deployment-strategy)
-1. Hit **Save changes** for the changes to take effect
+   and choose the [deployment strategy](#deployment-strategy).
+1. Click **Save changes** for the changes to take effect.
 
 When the feature has been enabled, an Auto DevOps pipeline is triggered on the default branch.
 
@@ -319,8 +319,7 @@ static analysis and other code checks on the current code. The report is
 created, and is uploaded as an artifact which you can later download and check
 out.
 
-In GitLab Starter, differences between the source and
-target branches are also
+Any differences between the source and target branches are also
 [shown in the merge request widget](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html).
 
 ### Auto SAST **[ULTIMATE]**
@@ -353,7 +352,7 @@ Any security warnings are also
 [shown in the merge request widget](https://docs.gitlab.com/ee//user/project/merge_requests/dependency_scanning.html).
 
 NOTE: **Note:**
-The Auto Dependency Sacnning stage will be skipped on licenses other than Ultimate.
+The Auto Dependency Scanning stage will be skipped on licenses other than Ultimate.
 
 ### Auto License Management **[ULTIMATE]**
 
@@ -381,7 +380,7 @@ Docker image and checks for potential security issues. Once the report is
 created, it's uploaded as an artifact which you can later download and
 check out.
 
-In GitLab Ultimate, any security warnings are also
+Any security warnings are also
 [shown in the merge request widget](https://docs.gitlab.com/ee//user/project/merge_requests/container_scanning.html).
 
 NOTE: **Note:**
@@ -406,7 +405,7 @@ branch's code so developers, designers, QA, product managers, and other
 reviewers can actually see and interact with code changes as part of the review
 process. Auto Review Apps create a Review App for each branch.
 
-Auto Review Apps will deploy your app to your Kubernetes cluster only. When no cluster 
+Auto Review Apps will deploy your app to your Kubernetes cluster only. When no cluster
 is available, no deployment will occur.
 
 The Review App will have a unique URL based on the project name, the branch
@@ -426,11 +425,11 @@ to perform an analysis on the current code and checks for potential security
 issues. Once the report is created, it's uploaded as an artifact which you can
 later download and check out.
 
-In GitLab Ultimate, any security warnings are also
+Any security warnings are also
 [shown in the merge request widget](https://docs.gitlab.com/ee//user/project/merge_requests/dast.html).
 
 NOTE: **Note:**
-*The Auto DAST stage will be skipped on licenses other than Ultimate.*
+The Auto DAST stage will be skipped on licenses other than Ultimate.
 
 ### Auto Browser Performance Testing **[PREMIUM]**
 
@@ -444,8 +443,8 @@ Auto Browser Performance Testing utilizes the [Sitespeed.io container](https://h
 /direction
 ```
 
-In GitLab Premium, performance differences between the source
-and target branches are [shown in the merge request widget](https://docs.gitlab.com/ee//user/project/merge_requests/browser_performance_testing.html).
+Any performance differences between the source and target branches are also
+[shown in the merge request widget](https://docs.gitlab.com/ee//user/project/merge_requests/browser_performance_testing.html).
 
 ### Auto Deploy