Fix typos and grammar

[ci skip]

doc/ci/autodeploy/index.md

@@ -102,7 +102,7 @@ kubernetes deploy:
     - kubectl create -f nginx-deployment.yaml || kubectl replace -f nginx-deployment.yaml
 ```
 
-Notice that we use a couple of environment Kubernetes variables to configure
+Notice that we use a couple of Kubernetes environment variables to configure
 the Kubernetes cluster. These are exposed from the
 [Kubernetes service](../../user/project/integrations/kubernetes.md#deployment-variables).
 The most important one is the `$KUBE_NAMESPACE` which should be unique for

doc/user/project/deploy_boards.md

@@ -87,10 +87,11 @@ reverted.
 
 To start using canary deployments, in addition to the
 [requirements of Deploy Boards](#requirements), you also need to label your
-deployments and pods with `track: canary`. This allows GitLab to discover
-whether deployment is stable or canary (temporary).
+deployments and pods with the `canary` label (`track: canary`).
 
-To quickly start, you can use the [Autodeploy] template for canary deployments
+In the end, depending on the deploy, the label should be either `stable` or `canary`.
+This allows GitLab to discover whether deployment is stable or canary (temporary).
+To get started quickly, you can use the [Autodeploy] template for canary deployments
 that GitLab provides.
 
 Canary deployments are marked with a yellow dot in the Deploy Board so that you