Cleanup, replace more default profile source constants

Author: melissamahoney-mongodb

source/configure/configuration-file.txt

@@ -26,7 +26,7 @@ the file. The {+mcli+} saves the configuration file to the folder where
 your system stores application configuration files, which is defined by
 the ``$XDG_CONFIG_HOME`` environment variable. By default, this location
 is the ``/.config`` folder of your home directory. If this folder
-doesn't exist, the {+mcli+} creates the folder and grants you read,
+doesn't exist, the {+mcli+} creates the folder and grants the user read,
 write, and execute permissions.
 
 .. _mcli-profiles:
@@ -38,9 +38,7 @@ The {+mcli+} configuration file stores related settings and
 |api| keys in groups called *profiles*. You can create or define multiple profiles so that you can use the {+mcli+} to access different MongoDB services or projects from the same terminal.
 
 The {+mcli+} uses the ``default`` profile by default. To run {+mcli+}
-commands without the ``--profile`` flag, you must use a profile named
-``default``. To use a profile with any other name, you must specify the
-``--profile`` flag for every command.
+commands without the ``--profile`` flag, you must configure a profile named ``default``. To use a profile with any other name, you must specify that profile with the ``--profile`` flag in every command.
 
 Example
 -------

source/includes/steps-configure-mcli-atlas.yaml

@@ -10,6 +10,7 @@ source:
   file: steps-configure-mcli.yaml
   ref: enter-api-key
 replacement:
+  apiKeys: ":atlas:`Programmatic API Key </configure-api-access>`"
   service: "|service|"
 ---
 stepnum: 3

source/includes/steps-configure-mcli-cm.yaml

@@ -10,6 +10,7 @@ source:
   file: steps-configure-mcli.yaml
   ref: enter-api-key
 replacement:
+  apiKeys: ":cloudmgr:`Cloud Manager API Access </tutorial/configure-public-api-access>`"
   service: "|cloud|"
 ---
 stepnum: 3

source/includes/steps-configure-mcli-om.yaml

@@ -15,6 +15,7 @@ source:
   file: steps-configure-mcli.yaml
   ref: enter-api-key
 replacement:
+  apiKeys: ":opsmgr:`Ops Manager API Acess </tutorial/configure-public-api-access>`"
   service: "|onprem|"
 ---
 stepnum: 4

source/includes/steps-configure-mcli.yaml

@@ -23,9 +23,8 @@ content: |
         :tabid: named-profile
 
         This command creates a profile with a custom name in the
-        :ref:`mcli-config-file`. To use this profile im subsequent
-        {+mcli+} commands, you must run the commands with the
-        ``--profile`` flag.
+        :ref:`mcli-config-file`. To use this profile, you must specify
+        it with the ``--profile`` flag in every command.
 
         Run the :ref:`mcli-config-command` command:
 
@@ -47,7 +46,7 @@ content: |
      ? Ops Manager Base URL: http://mms.example.com:8080
 
 ---
-title: "Enter your |svc-api-key| and Project ID."
+title: "Enter your {{apiKeys}} and Project ID."
 stepnum: 0
 level: 4
 ref: enter-api-key
@@ -73,7 +72,8 @@ level: 4
 ref: verify-profile
 content: |
 
-  View the ``mongocli.toml`` configuration file to verify your profile.
+  View the :ref:`configuration file <mcli-config-file>` to verify your
+  profile.
 
   .. include:: /includes/admonitions/secure-config-file.rst
 
@@ -86,7 +86,7 @@ content: |
         .. example::
 
            In this example, the configuration file is stored in the
-           ``/.config`` folder of your home directory. View the file
+           ``/.config`` folder of the home directory. View the file
            using the ``cat`` command:
 
            .. code-block:: sh

source/quick-start.txt

@@ -229,8 +229,9 @@ To learn more about generating the |svc-api-key|, see:
 
       .. include:: /includes/quick-start-summary.rst
 
-      You can use the |mongo| shell connect to your cluster with the
-      ``srvAddress`` and appropriate :manual:`connection string options
+      You can also use the |mongo| shell connect to your cluster with
+      the ``srvAddress`` and appropriate :manual:`connection string
+      options
       </reference/connection-string/#connection-string-options>`.
 
    .. tab:: Cloud Manager

source/reference/atlas/alerts-configs-create.txt

@@ -259,8 +259,7 @@ Options
    * - ``--profile``, ``-P``
      - string
      - Name of the profile where the public and private 
-       keys for the project are saved. If omitted, uses the ``default`` 
-       profile. To learn more about creating a 
+       keys for the project are saved. If omitted, uses the {+default-profile+}. To learn more about creating a 
        profile, see :ref:`mcli-configure`.
      - no
 

source/reference/atlas/alerts-configs-fields-type.txt

@@ -47,8 +47,7 @@ Options
    * - ``--profile``, ``-P``
      - string
      - Name of the profile where the public and private 
-       keys for the project are saved. If omitted, uses the ``default`` 
-       profile. To learn more about creating a 
+       keys for the project are saved. If omitted, uses the {+default-profile+}. To learn more about creating a 
        profile, see :ref:`mcli-configure`.
      - no
 

source/reference/atlas/alerts-configs-update.txt

@@ -264,8 +264,7 @@ Options
    * - ``--profile``, ``-P``
      - string
      - Name of the profile where the public and private 
-       keys for the project are saved. If omitted, uses the ``default`` 
-       profile. To learn more about creating a 
+       keys for the project are saved. If omitted, uses the {+default-profile+}. To learn more about creating a 
        profile, see :ref:`mcli-configure`.
      - no
 

source/reference/atlas/cluster-delete.txt

@@ -70,8 +70,7 @@ Options
    * - ``--profile``, ``-P``
      - string
      - Name of the profile to use for accessing the 
-       |service| project. If omitted, uses the ``default`` 
-       profile.
+       |service| project. If omitted, uses the {+default-profile+}.
      - no
 
    * - ``--projectId``