DOCSP-33529 -- Clarify 1:1 project to deployment relationship and related ConfigMap requirement

Author: jvincent-mongodb

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

@@ -20,7 +20,7 @@ content: |
        name: my-project
        namespace: mongodb
      data:
-       projectName: myProjectName # this is an optional parameter
+       projectName: myProjectName # optional; omit to generate a random project name
        orgId: 5b890e0feacf0b76ff3e7183 # this is a required parameter
        baseUrl: https://ops.example.com:8443
 

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

@@ -12,11 +12,20 @@ Create One Project using a ConfigMap
    :depth: 1
    :class: singlecol
 
-The |k8s-op-full| uses a |k8s| |k8s-configmap| to link your
+The |k8s-op-full| uses a |k8s| |k8s-configmap| to link to a single, 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.
 
+.. note:: 
+
+   As each |k8s-op-full| deployment requires a one to one pairing with
+   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
+   project names will be randomly generated as required.
+
 To create a |k8s-op-short| ConfigMap, you can edit a few lines of the
 :ref:`example ConfigMap <example-k8s-configmap>` |yaml| file and apply
 the ConfigMap. To view a full example, see the :github:`project.yaml