updates

Author: Nickomang

articles/aks/image-cleaner.md

@@ -74,9 +74,9 @@ ImageCleaner does not support the following:
 
 When enabled, an `eraser-controller-manager` pod is deployed on each agent node, which will use an `ImageList` CRD to determine unreferenced and vulnerable images. An `ImageList` can either be defined manually or automatically generated by ImageCleaner.
 
-In manual mode, the `ImageList` is created based off of a provided list of image names. In automatic mode, a time interval is set. ImageCleaner will continually run in this interval to generate an updated `ImageList`.
+In manual mode, the `ImageList` is created based off of a provided list of image names. In automatic mode, a time interval is set. ImageCleaner will repeatedly run in this interval to generate an updated `ImageList`.
 
-Once an `ImageList` is generated, ImageCleaner will delete all the images in the list from node VMs.
+Once an `ImageList` is generated, ImageCleaner will continuously delete all the images in the list from node VMs.
 
 ## Configuration options
 
@@ -90,8 +90,6 @@ In addition to choosing between manual and automatic mode, there are several opt
 
 ## Enable ImageCleaner on your AKS cluster
 
-### Enable ImageCleaner on your cluster
-
 To create a new AKS cluster using the default interval, use [az aks create][az-aks-create]:
 
 ```azurecli-interactive
@@ -110,7 +108,6 @@ The `--image-cleaner-interval-hours` parameter can be specified at creation time
 
 ```azurecli-interactive
 az aks update -g MyResourceGroup -n MyManagedCluster \
-  --enable-image-cleaner \
   --image-cleaner-interval-hours 48
 ```