diff --git a/docs/source/QA/makehosts.rst b/docs/source/QA/makehosts.rst
index ba9755033..2c34bb586 100644
--- a/docs/source/QA/makehosts.rst
+++ b/docs/source/QA/makehosts.rst
@@ -67,15 +67,15 @@ Q: How to configure aliases?
 There are 3 methods to configure aliases:
 
 #. Use ``hostnames`` in ``hosts`` table to configure aliases for the installnic.
-#. If you want to use script ``confignetwork`` to configure secondary NICs, suggest to use ``aliases`` in ``nics`` table to configure aliases.  Refer to :doc:`Configure Aliases <../guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_aliases>` 
-#. If you want to generate aliases records in ``/etc/hosts`` for secondary NICs and you don't want to use the script ``confignetwork`` to configure these NICs, suggest to use ``otherinterfaces`` in ``hosts`` table to configure aliases.  Refer to following example: 
-       
+#. If you want to use script ``confignetwork`` to configure secondary NICs, suggest to use ``aliases`` in ``nics`` table to configure aliases.  Refer to :doc:`Configure Aliases <../guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_aliases>`
+#. If you want to generate aliases records in ``/etc/hosts`` for secondary NICs and you don't want to use the script ``confignetwork`` to configure these NICs, suggest to use ``otherinterfaces`` in ``hosts`` table to configure aliases.  Refer to following example:
+
     * If you want to add ``node1-hd`` ``20.1.1.1`` in ``hosts`` table, and don't use ``confignetwork`` to configure it, you can add ``otherinterfaces`` like this: ::
 
-        chdef node1 otherinterfaces="node1-hd:20.1.1.1" 
+        chdef node1 otherinterfaces="node1-hd:20.1.1.1"
 
     * After executing ``makehosts -n``, you can get records in ``/etc/hosts`` like following: ::
-    
+
         20.1.1.1 node1-hd
 
 **Note**: If suffixes or aliases for the same IP are configured in both ``hosts`` table and ``nics`` table, will cause conflicts. ``makehosts`` will use values from ``nics`` table. The values from ``nics`` table will over-write that from ``hosts`` table to create ``/etc/hosts`` records.
@@ -90,7 +90,7 @@ You can follow the best practice example.
     * There are 2 networks in different domains: ``mgtnetwork`` and ``pubnetwork``
     * ``mgtnetwork`` is xCAT management network
     * Generate 2 records with the same hostname in ``/etc/hosts``, like: ::
-   
+
         10.5.106.101 node1.cluster.com
         192.168.20.101 node1.public.com
 
@@ -101,11 +101,11 @@ You can follow the best practice example.
     #. Add networks entry in ``networks`` table: ::
 
         chdef -t network mgtnetwork net=10.0.0.0 mask=255.0.0.0 domain=cluster.com
-        chdef -t network pubnetwork net=192.168.30.0 mask=255.255.255.0 domain=public.com 
-     
+        chdef -t network pubnetwork net=192.168.30.0 mask=255.255.255.0 domain=public.com
+
     #. Create ``node1`` with ``ip=10.5.106.101``, xCAT can manage and install this node: ::
-   
-        chdef node1 ip=10.5.106.101 groups=all 
+
+        chdef node1 ip=10.5.106.101 groups=all
 
     #. Create ``node1-pub`` with ``ip=192.168.30.101``, this node is only used to generate ``/etc/hosts`` records for public network, can use ``_unmanaged`` group name to label it: ::
 
@@ -114,9 +114,9 @@ You can follow the best practice example.
     #. Execute ``makehosts -n`` to generate ``/etc/hosts`` records: ::
 
         makehosts -n
-    
+
     #. Check results in ``/etc/hosts``: ::
-     
+
         10.5.106.101 node1 node1.cluster.com
         192.168.30.101 node1-pub node1.public.com