Replace all instances of {{ site.data.product.title }} with {{ site.data.product.title_short }}

This has zero impact to upstream ManageIQ docs as both are defined as "ManageIQ".  Downstream this helps with client experience by replacing the long title name "IBM Cloud Pak for Multicloud Management - Infrastructure Management" with the shorter title name "Infrastructure Management".

Author: dehawkins512

_includes/appe-appliance-console-cli.md

@@ -1,6 +1,6 @@
 Currently, the `appliance_console_cli` feature is a subset of the full functionality of the `appliance_console` itself, and covers functions most likely to be scripted by using the command-line interface (CLI).
 
-1.  After starting the {{ site.data.product.title }} appliance, log in with a user name of `root` and the default password of `smartvm`. This displays the Bash prompt for the root user.
+1.  After starting the {{ site.data.product.title_short }} appliance, log in with a user name of `root` and the default password of `smartvm`. This displays the Bash prompt for the root user.
 
 2.  Enter the `appliance_console_cli` or `appliance_console_cli --help` command to see a list of options available with the command, or simply enter `appliance_console_cli --option <argument>` directly to use a specific option.
 

_includes/cap-util-assign-server-roles.md

@@ -18,4 +18,4 @@ begins 5 minutes after the server is started, and every 10 minutes after
 that. Therefore, the longest the collection takes after enabling the
 Capacity & Utilization Collector role is 10 minutes. The first
 collection from a particular provider may take a few minutes since
-{{ site.data.product.title }} is gathering data points going one month back in time.
+{{ site.data.product.title_short }} is gathering data points going one month back in time.

_includes/cap-util-note-metrics-collection.md

@@ -1,4 +1,4 @@
 For metrics collection to work properly, you also need to configure
-{{ site.data.product.title }} to allow for all three **Capacity & Utilization** server
+{{ site.data.product.title_short }} to allow for all three **Capacity & Utilization** server
 roles, which are available from the settings menu under
 menu:Configuration\[Server \> Server Control\].

_includes/configuration-advanced.md

@@ -75,19 +75,19 @@ configuration of the appliance:
 </tr>
 <tr class="even">
 <td><p><strong>Restart Appliance</strong></p></td>
-<td><p>Restart the {{ site.data.product.title }} appliance. You can either restart the appliance and clear the logs or just restart the appliance.</p></td>
+<td><p>Restart the {{ site.data.product.title_short }} appliance. You can either restart the appliance and clear the logs or just restart the appliance.</p></td>
 </tr>
 <tr class="odd">
 <td><p><strong>Shut Down Appliance</strong></p></td>
 <td><p>Power down the appliance and exit all processes.</p></td>
 </tr>
 <tr class="even">
 <td><p><strong>Summary Information</strong></p></td>
-<td><p>Go back to the network summary screen for the {{ site.data.product.title }} appliance.</p></td>
+<td><p>Go back to the network summary screen for the {{ site.data.product.title_short }} appliance.</p></td>
 </tr>
 <tr class="odd">
 <td><p><strong>Quit</strong></p></td>
-<td><p>Leave the {{ site.data.product.title }} appliance console.</p></td>
+<td><p>Leave the {{ site.data.product.title_short }} appliance console.</p></td>
 </tr>
 </tbody>
 </table>

_includes/configuration-db.md

@@ -5,14 +5,14 @@ hosting your appliance. See the documentation specific to your
 infrastructure for instructions for adding a disk. As a storage disk
 usually cannot be added while a virtual machine is running, Red Hat
 recommends adding the disk before starting the appliance.
-{{ site.data.product.title }} only supports installing of an internal VMDB on blank
+{{ site.data.product.title_short }} only supports installing of an internal VMDB on blank
 disks; installation will fail if the disks are not blank.
 
 </div>
 
 1.  Start the appliance and open a terminal console.
 
-2.  Enter the `appliance_console` command. The {{ site.data.product.title }} appliance
+2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
     summary screen displays.
 
 3.  Press **Enter** to manually configure settings.
@@ -21,10 +21,10 @@ disks; installation will fail if the disks are not blank.
 
 5.  You are prompted to create or fetch an encryption key.
 
-      - If this is the first {{ site.data.product.title }} appliance, choose **Create
+      - If this is the first {{ site.data.product.title_short }} appliance, choose **Create
         key**.
 
-      - If this is not the first {{ site.data.product.title }} appliance, choose
+      - If this is not the first {{ site.data.product.title_short }} appliance, choose
         **Fetch key from remote machine** to fetch the key from the
         first appliance. For worker and multi-region setups, use this
         option to copy key from another appliance.
@@ -84,6 +84,6 @@ disks; installation will fail if the disks are not blank.
 
 10. Create and confirm a password for the database.
 
-{{ site.data.product.title }} then configures the internal database. This takes a few
+{{ site.data.product.title_short }} then configures the internal database. This takes a few
 minutes. After the database is created and initialized, you can log in
 to {{ site.data.product.title_short }}.

_includes/configuration-gui.md

@@ -1,15 +1,15 @@
 The options under the ![Configuration](../images/config-gear.png)
 **Configuration** menu allow you to configure global options for your
-{{ site.data.product.title }} environment, view diagnostic information, and view
+{{ site.data.product.title_short }} environment, view diagnostic information, and view
 analytics on the servers in the environment. The menu displays the
-{{ site.data.product.title }} environment at the enterprise, zone, and server levels.
+{{ site.data.product.title_short }} environment at the enterprise, zone, and server levels.
 
 There are four main areas:
 
   - **Settings**
 
     This menu allows you to configure global settings for your
-    {{ site.data.product.title }} infrastructure. You can also create analysis
+    {{ site.data.product.title_short }} infrastructure. You can also create analysis
     profiles and schedules for these profiles.
 
   - **Access Control**

_includes/configuration-register-appliance.md

@@ -1,5 +1,5 @@
 Before you can access and apply package updates, you must register and
-subscribe the {{ site.data.product.title }} appliance to either Red Hat Content
+subscribe the {{ site.data.product.title_short }} appliance to either Red Hat Content
 Delivery Network (CDN) or to a Red Hat Satellite server.
 
 You need the following to register your appliance:
@@ -23,7 +23,7 @@ To configure registration for a region:
 
 4.  Click **Edit Registration**.
 
-5.  Configure registration details for the {{ site.data.product.title }} appliance
+5.  Configure registration details for the {{ site.data.product.title_short }} appliance
     using one of two available options:
 
     1.  To register with Red Hat Subscription Management:

_includes/configuration.md

@@ -1,4 +1,4 @@
-## Configuring {{ site.data.product.title }}
+## Configuring {{ site.data.product.title_short }}
 
 After installing {{ site.data.product.title_short }} and running it for the first
 time, you must perform some basic configuration. To configure
@@ -15,7 +15,7 @@ appliance console.
 
 1.  Start the appliance and open a terminal console.
 
-2.  Enter the `appliance_console` command. The {{ site.data.product.title }} appliance
+2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
     summary screen displays.
 
 3.  Press `Enter` to manually configure settings.
@@ -57,13 +57,13 @@ reporting zone, where each zone provides a specific function. The
 appliances in these zones must be configured to use an external
 database.
 
-The `postgresql.conf` file used with {{ site.data.product.title }} databases requires
+The `postgresql.conf` file used with {{ site.data.product.title_short }} databases requires
 specific settings for correct operation. For example, it must correctly
 reclaim table space, control session timeouts, and format the PostgreSQL
 server log for improved system support. Due to these requirements, Red
-Hat recommends that external {{ site.data.product.title }} databases use a
+Hat recommends that external {{ site.data.product.title_short }} databases use a
 `postgresql.conf` file based on the standard file used by the
-{{ site.data.product.title }} appliance.
+{{ site.data.product.title_short }} appliance.
 
 Ensure you configure the settings in the `postgresql.conf` to suit your
 system. For example, customize the `shared_buffers` setting according to
@@ -74,16 +74,16 @@ necessary to alter the `max_connections` setting.
 
 **Note:**
 
-  - {{ site.data.product.title }} requires PostgreSQL version 9.5.
+  - {{ site.data.product.title_short }} requires PostgreSQL version 9.5.
 
   - Because the `postgresql.conf` file controls the operation of all
     databases managed by a single instance of PostgreSQL, do not mix
-    {{ site.data.product.title }} databases with other types of databases in a single
+    {{ site.data.product.title_short }} databases with other types of databases in a single
     PostgreSQL instance.
 
 1.  Start the appliance and open a terminal console.
 
-2.  Enter the `appliance_console` command. The {{ site.data.product.title }} appliance
+2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
     summary screen displays.
 
 3.  Press **Enter** to manually configure settings.
@@ -92,10 +92,10 @@ necessary to alter the `max_connections` setting.
 
 5.  You are prompted to create or fetch a security key.
 
-      - If this is the first {{ site.data.product.title }} appliance, choose **Create
+      - If this is the first {{ site.data.product.title_short }} appliance, choose **Create
         key**.
 
-      - If this is not the first {{ site.data.product.title }} appliance, choose
+      - If this is not the first {{ site.data.product.title_short }} appliance, choose
         **Fetch key from remote machine** to fetch the key from the
         first appliance.
 
@@ -117,7 +117,7 @@ necessary to alter the `max_connections` setting.
 
 11. Confirm the configuration if prompted.
 
-{{ site.data.product.title }} will then configure the external database.
+{{ site.data.product.title_short }} will then configure the external database.
 
 ### Configuring a Worker Appliance
 
@@ -131,15 +131,15 @@ has a region configured with a database.
 
 1.  Start the appliance and open a terminal console.
 
-2.  Enter the `appliance_console` command. The {{ site.data.product.title }} appliance
+2.  Enter the `appliance_console` command. The {{ site.data.product.title_short }} appliance
     summary screen displays.
 
 3.  Press **Enter** to manually configure settings.
 
 4.  Select **Configure Database** from the menu.
 
 5.  You are prompted to create or fetch a security key. Since this is
-    not the first {{ site.data.product.title }} appliance, choose **2) Fetch key from
+    not the first {{ site.data.product.title_short }} appliance, choose **2) Fetch key from
     remote machine**. For worker and multi-region setups, use this
     option to copy the security key from another appliance.
 

_includes/create-dynamic-resource-object.md

@@ -1,5 +1,5 @@
 Model a new resource by creating a generic object class and adding it to
-your {{ site.data.product.title }} inventory. Each generic object class can have
+your {{ site.data.product.title_short }} inventory. Each generic object class can have
 attributes, associations, and methods. Once created, generic object
 classes are visible to users of the Self Service user interface at the
 resource level.

_includes/create-generic-object.md

@@ -1,5 +1,5 @@
 Model a new resource by creating a generic object class and adding it to
-your {{ site.data.product.title }} inventory. Each generic object class can have
+your {{ site.data.product.title_short }} inventory. Each generic object class can have
 attributes, associations, and methods. Once created, generic objects
 classes are visible to users of the Service user interface at the
 resource level.

_includes/create-playbook-service-catalog-item.md

@@ -1,6 +1,6 @@
 **Note:**
 
-  - Before creating an Ansible service, at least one repository, one playbook, and one credential must exist in the {{ site.data.product.title }} inventory. Check your inventory and add the appropriate resources before creating an Ansible service. For more information, see [Automation Management Providers](../managing_providers/index.html#automation-management-providers) in *Managing Providers*.
+  - Before creating an Ansible service, at least one repository, one playbook, and one credential must exist in the {{ site.data.product.title_short }} inventory. Check your inventory and add the appropriate resources before creating an Ansible service. For more information, see [Automation Management Providers](../managing_providers/index.html#automation-management-providers) in *Managing Providers*.
 
   - Debugging verbosity is available for Ansible playbook catalog items.
     Selecting a higher verbosity value provides more detailed output as

_includes/create-tower-catalog-item.md

@@ -2,7 +2,7 @@
 
 You must first create the job or workflow template in Ansible Tower. The
 job or workflow templates are automatically discovered by
-{{ site.data.product.title }} when refreshing your Ansible Tower provider’s inventory.
+{{ site.data.product.title_short }} when refreshing your Ansible Tower provider’s inventory.
 
 </div>
 

_includes/import-export-custom-buttons.md

@@ -1,13 +1,13 @@
 ### Migrating Custom Buttons
 
 This workflow demonstrates how to export custom buttons from one
-{{ site.data.product.title }} appliance and import them in another
+{{ site.data.product.title_short }} appliance and import them in another
 {{ site.data.product.title_short }} appliance.
 
 1.  Export custom buttons from the source {{ site.data.product.title_short }}
     appliance:
 
-    1.  SSH into the {{ site.data.product.title }} appliance as `root`.
+    1.  SSH into the {{ site.data.product.title_short }} appliance as `root`.
 
     2.  Create a temporary directory:
 

_includes/initial-login-changepw.md

@@ -1,5 +1,5 @@
 Change your password to ensure more private and secure access to
-{{ site.data.product.title }}.
+{{ site.data.product.title_short }}.
 
 1.  Navigate to the URL for the login screen. (<https://xx.xx.xx.xx> on
     the virtual machine instance)

_includes/initial-login.md

@@ -1,7 +1,7 @@
-Once {{ site.data.product.title }} is installed, you can log in and perform
+Once {{ site.data.product.title_short }} is installed, you can log in and perform
 administration tasks.
 
-Log in to {{ site.data.product.title }} for the first time after installing by:
+Log in to {{ site.data.product.title_short }} for the first time after installing by:
 
 1.  Navigate to the URL for the login screen. (<https://xx.xx.xx.xx> on
     the virtual machine instance)