[install-guide] Add glossterm markup

Change-Id: I03a34bd376023fcb2df9442ca8860525aa62dc9d

doc/install-guide-rst/source/basics-queue.rst

@@ -1,10 +1,10 @@
 Message queue
 ~~~~~~~~~~~~~
 
-OpenStack uses a message queue to coordinate operations and status
-information among services. The message queue service typically runs on
-the controller node. OpenStack supports several message queue services
-including `RabbitMQ <http://www.rabbitmq.com>`__,
+OpenStack uses a :term:`message queue` to coordinate operations and
+status information among services. The message queue service typically
+runs on the controller node. OpenStack supports several message queue
+services including `RabbitMQ <http://www.rabbitmq.com>`__,
 `Qpid <http://qpid.apache.org>`__, and `ZeroMQ <http://zeromq.org>`__.
 However, most distributions that package OpenStack support a particular
 message queue service. This guide implements the RabbitMQ message queue

doc/install-guide-rst/source/glance-verify.rst

@@ -41,10 +41,8 @@ For information about how to manage images, see the
       $ wget -P /tmp/images http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
 
 #. Upload the image to the Image service using the
-   QCOW2 disk format, bare container format, and
-   public visibility so all projects can access it:
-
-   .. TODO(katomo): add link to glossterm QCOW2
+   :term:`QCOW2 <QEMU Copy On Write 2 (QCOW2)>` disk format, :term:`bare`
+   container format, and public visibility so all projects can access it:
 
    .. code-block:: console
 

doc/install-guide-rst/source/glance.rst

@@ -9,14 +9,12 @@ Add the Image service
    glance-verify.rst
 
 The OpenStack Image service (glance) enables users to discover,
-register, and retrieve virtual machine images. It offers a REST
-API that enables you to query virtual machine image metadata and
-retrieve an actual image. You can store virtual machine images
-made available through the Image service in a variety of locations,
-from simple file systems to object-storage systems like OpenStack
-Object Storage.
-
-.. TODO(katomo): add link to glossterm REST.
+register, and retrieve virtual machine images. It offers a
+:term:`REST <RESTful>` API that enables you to query virtual
+machine image metadata and retrieve an actual image.
+You can store virtual machine images made available through
+the Image service in a variety of locations, from simple file
+systems to object-storage systems like OpenStack Object Storage.
 
 .. important::
 

doc/install-guide-rst/source/heat-install.rst

@@ -119,8 +119,8 @@ database, service credentials, and API endpoints.
         The Orchestration service automatically assigns the
         ``heat_stack_user`` role to users that it creates
         during stack deployment. By default, this role restricts
-        API operations. To avoid conflicts, do not add this role
-        to users with the ``heat_stack_owner`` role.
+        :term:`API` operations. To avoid conflicts, do not add
+        this role to users with the ``heat_stack_owner`` role.
 
    * Create the ``heat`` and ``heat-cfn`` service entities:
 

doc/install-guide-rst/source/nova-compute-install.rst

@@ -3,8 +3,10 @@ Install and configure a compute node
 
 This section describes how to install and configure the Compute
 service on a compute node. The service supports several
-hypervisors to deploy instances or VMs. For simplicity,
-this configuration uses the QEMU hypervisor with the KVM extension
+:term:`hypervisors <hypervisor>` to deploy :term:`instances <instance>`
+or :term:`VMs <virtual machine (VM)>`. For simplicity, this configuration
+uses the :term:`QEMU <Quick EMUlator (QEMU)>` hypervisor with the
+:term:`KVM <kernel-based VM (KVM)>` extension
 on compute nodes that support hardware acceleration for virtual machines.
 On legacy hardware, this configuration uses the generic QEMU hypervisor.
 You can follow these instructions with minor modifications to horizontally