DOCSP-33529 -- incorporate feedback

Author: jvincent-mongodb

source/includes/steps-create-k8s-configmap.yaml

@@ -20,7 +20,7 @@ content: |
        name: my-project
        namespace: mongodb
      data:
-       projectName: myProjectName # optional; omit to create a project with the resource name
+       projectName: myProjectName # this is an optional parameter; when omitted, the Operator creates a project with the resource name
        orgId: 5b890e0feacf0b76ff3e7183 # this is a required parameter
        baseUrl: https://ops.example.com:8443
 

source/tutorial/create-project-using-configmap.txt

@@ -12,7 +12,7 @@ Create One Project using a ConfigMap
    :depth: 1
    :class: singlecol
 
-The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single, unique
+The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single and unique
 |onprem| :opsmgr:`Project </tutorial/manage-projects>`. If the 
 referenced project doesn't exist, the |k8s-op-short| creates it 
 according to the ``projectName`` that you provide in the ConfigMap.
@@ -31,15 +31,13 @@ which you can then apply to your Kubernetes environment.
 Considerations
 --------------
 
-You can deploy only one MongoDB resource per project. This limit 
-applies because |onprem| supports only one authentication method for 
-database user access per project. To learn more, see 
-:ref:`k8s-deploy-mdb-resources`.
+1. You can deploy only one MongoDB resource per project. This limit 
+   applies because |onprem| supports only one authentication method for 
+   database user access per project. To learn more, see 
+   :ref:`k8s-deploy-mdb-resources`.
 
-.. note:: 
-
-   Each |k8s-op-full| deployment requires a 1:1 pairing with
-   a unique |onprem| :opsmgr:`Project </tutorial/manage-projects>`. 
+2. You must pair a |k8s-op-full| deployment to a unique
+   |onprem| :opsmgr:`Project </tutorial/manage-projects>`. 
    You can either create a distinct ConfigMap for each |k8s-op-full| instance
    you deploy, or you can reuse the same ConfigMap for any number of deployments
    by omitting the ``data.projectName`` from your ConfigMap, so that