Rename operator to admin in examples to be consistent with user stories

docs/proposals/20201020-management-cluster-operator.md

@@ -440,7 +440,7 @@ type ProviderStatus struct {
 
 #### Example API Usage
 
-1. As an operator, I want to install the aws infrastructure provider with
+1. As an admin, I want to install the aws infrastructure provider with
    specific controller flags.
 
 ```yaml
@@ -481,7 +481,7 @@ spec:
          awsmachine-concurrency: 11
 ```
 
-2. As an operator, I want to install aws infrastructure provider but override
+2. As an admin, I want to install aws infrastructure provider but override
    the container image of the CAPA deployment.
 
 ```yaml
@@ -500,7 +500,7 @@ spec:
      image: gcr.io/myregistry/capa-controller:v0.6.0-foo
 ```
 
-3. As an operator, I want to change the resource limits for the manager pod in
+3. As an admin, I want to change the resource limits for the manager pod in
    my control plane provider deployment.
 
 ```yaml
@@ -525,7 +525,7 @@ spec:
          memory: 20Mi
 ```
 
-4. As an operator, I would like to fetch my azure provider components from a
+4. As an admin, I would like to fetch my azure provider components from a
    specific repository which is not the default.
 
 ```yaml
@@ -543,7 +543,7 @@ spec:
 
 ```
 
-5. As an operator, I would like to use the default fetch configurations by
+5. As an admin, I would like to use the default fetch configurations by
    simply specifying the expected Cluster API provider names such as 'aws',
    'vsphere', 'azure', 'kubeadm', 'talos', or 'cluster-api' instead of having
    to explicitly specify the fetch configuration.
@@ -770,7 +770,7 @@ the operator, it is required to address the following issues.
 
 **Example Usage**
 
-As an operator, I would like to fetch my azure provider components from within
+As an admin, I would like to fetch my azure provider components from within
 the cluster because I’m working within an air-gapped environment.
 
 In this example, we have two config maps that define the components and