Merge pull request #1100 from Nordix/fix-typo-in-cloud-provider-az

📖 Fix few typos in docs under /topics folder

Author: k8s-ci-robot

docs/book/src/topics/cloud-provider-config.md

@@ -2,6 +2,6 @@
 
 The [Azure cloud provider](https://github.com/kubernetes-sigs/cloud-provider-azure) has a number of configuration options driven by a file on cluster nodes. This file canonically lives on a node at /etc/kubernetes/azure.json. The Azure cloud provider documentation details the [configuration options exposed](https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/docs/cloud-provider-config.md#cloud-provider-config) by this file.
 
-CAPZ automatically generates this file based on user-provided values in AzureMachineTemplate and AzureMachine. All AzureMachines in the same MachineDeployment or control plane will all share a single cloud provider secret, while AzureMachines created inidividially will have their own secret.
+CAPZ automatically generates this file based on user-provided values in AzureMachineTemplate and AzureMachine. All AzureMachines in the same MachineDeployment or control plane will all share a single cloud provider secret, while AzureMachines created inidividually will have their own secret.
 
 For AzureMachineTemplate and standalone AzureMachines, the generated secret will have the name "${RESOURCE}-azure-json", where "${RESOURCE}" is the name of either the AzureMachineTemplate or AzureMachine. The secret will have one data field, `azure.json`, with the raw content for that file. When the secret `${RESOURCE}-azure-json` already exists in the same namespace as an AzureCluster and does not have the label `"${CLUSTER_NAME}": "owned"`, CAPZ will not generate the default described above. Instead it will directly use whatever the user provides in that secret.

docs/book/src/topics/ephemeral-os.md

@@ -30,14 +30,14 @@ When `diffDiskSettings.option` is set to `Local`, ephemeral OS will be enabled.
 
 ## Known Limitations
 
-Not all SKU sizes support ephemeral os. CAPZ will query Azure's resource
+Not all SKU sizes support ephemeral OS. CAPZ will query Azure's resource
 SKUs API to check if the requested VM size supports ephemeral OS. If
 not, the azuremachine controller will log an event with the
 corresponding error on the AzureMachine object.
 
 ## Example
 
-The below example shows how to enable ephemeral OS for a machine template. For control plane nodes, we strongly recommend using [etcd data disks](data-disks.md)to avoid data loss.
+The below example shows how to enable ephemeral OS for a machine template. For control plane nodes, we strongly recommend using [etcd data disks](data-disks.md) to avoid data loss.
 
 ````yaml
 apiVersion: infrastructure.cluster.x-k8s.io/v1alpha3

docs/book/src/topics/gpu.md

@@ -48,7 +48,7 @@ azuremachinetemplate.infrastructure.cluster.x-k8s.io/azure-gpu-md-0 created
 kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/azure-gpu-md-0 created
 ```
 
-Wait until the cluster and nodes are finished provisioning. The GPU nodes make take several minutes
+Wait until the cluster and nodes are finished provisioning. The GPU nodes may take several minutes
 to provision, since each one must install drivers and supporting software.
 
 ```bash

docs/book/src/topics/machinepools.md

@@ -32,7 +32,7 @@
 *Source: [MachinePool API Proposal](https://github.com/kubernetes-sigs/cluster-api/blob/bf51a2502f9007b531f6a9a2c1a4eae1586fb8ca/docs/proposals/20190919-machinepool-api.md)*
 
 ## AzureMachinePool
-Cluster API Provider Azure (CAPZ) has experimental support for `MachinePool` though the infrastructure
+Cluster API Provider Azure (CAPZ) has experimental support for `MachinePool` through the infrastructure
 type `AzureMachinePool`. An `AzureMachinePool` corresponds to an [Azure Virtual Machine Scale Set](https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview),
 which provides the cloud provider specific resource for orchestrating a group of Virtual Machines.
 

docs/book/src/topics/managedcluster.md

@@ -154,7 +154,7 @@ should be fairly clear from context.
 
 AKS clusters deployed from CAPZ currently only support a limited,
 "blessed" configuration. This was primarily to keep the initial
-implementation simple. If you'd like to managed AKS cluster with CAPZ
+implementation simple. If you'd like to run managed AKS cluster with CAPZ
 and need an additional feature, please open a pull request or issue with
 details. We're happy to help!
 

docs/book/src/topics/multitenancy.md

@@ -23,7 +23,7 @@ spec:
   - <cluster-namespace>
 
 ```
-The password will need to be added in a secret similar to the following example
+The password will need to be added in a secret similar to the following example:
 
 ```yaml
 apiVersion: v1
@@ -35,7 +35,7 @@ data:
   clientSecret: <client-secret-of-SP-identity>
 ```
 
-OR the password can also as a Certificate 
+OR the password can also be added as a Certificate:
 
 ```yaml
 apiVersion: v1
@@ -78,6 +78,6 @@ spec:
 
 For more details on how aad-pod-identity works, please check the guide [here](https://azure.github.io/aad-pod-identity/docs/).
 
-## User Assiged Identity
+## User Assigned Identity
 
 _will be supported in a future release_