Merge pull request #294 from penguhyang/correct_doc

correct doc for word and syntax

docs/source/guides/admin-guides/basic_concepts/index.rst

@@ -7,7 +7,7 @@ xCAT is not hard to use but you still need to learn some basic concepts of xCAT
 
   The unit which can be managed in the xCAT is defined as an object. xCAT abstracts several types of objects from the cluster information to represent the physical or logical entities in the cluster. Each xCAT object has a set of attributes, each attribute is mapped from a specified field of a xCAT database table. The xCAT users can get cluster information and perform cluster management work through operations against the objects.
 
-* **XCAT Database**
+* **xCAT Database**
 
   All the data for the xCAT Objects (node, group, network, osimage, policy ... and global configuration) are stored in xCAT Database. Tens of tables are created as the back-end of xCAT Objects. Generally the data in the database is used by user through **xCAT Objects**. But xCAT also offers a bunch of commands to handle the database directly.
 

docs/source/guides/admin-guides/basic_concepts/xcat_db/index.rst

@@ -1,7 +1,7 @@
 xCAT Database
 =============
 
-All of the xCAT Objects and Configuration data are stored in xCAT database. By default, xCAT uses **SQLite** - an OS contained simple database engine. The powerful open source dtabase engines like MySQL, MariaDB, PostgreSQL are also supported for a large cluster.
+All of the xCAT Objects and Configuration data are stored in xCAT database. By default, xCAT uses **SQLite** - an OS contained simple database engine. The powerful open source database engines like MySQL, MariaDB, PostgreSQL are also supported for a large cluster.
 
 xCAT defines about 70 tables to store different data. You can get the xCAT database definition from file ``/opt/xcat/lib/perl/xCAT/Schema.pm``.
 

docs/source/guides/admin-guides/index.rst

@@ -7,7 +7,7 @@ Now you can start to learn how to manage a cluster by xCAT. This chapter include
 
 * **Basic Concepts**
 
-  This Section will give you the introduction of some basic concepts in xCAT like the **Object Concept**, **Database**, **Global Configuration**, **Network** and **NOde Type**.
+  This Section will give you the introduction of some basic concepts in xCAT like the **Object Concept**, **Database**, **Global Configuration**, **Network** and **Node Type**.
 
 * **Manage Cluster**
 

docs/source/guides/admin-guides/large_clusters/index.rst

@@ -10,12 +10,12 @@ The following configurations are supported:
     * Having a pool of service nodes, any of which can respond to an installation request from a compute node (*Requires service nodes to be aligned with networks broadcast domains, compute node chooses service nodes based on who responds to DHCP request first.*)
     * A hybrid of the above, where each specific set of compute nodes have 2 or more service nodes in a pool
 
-The following documentation assumes an xCAT cluster has already been configured and covers the additional steps needed to suport xCAT Hierarchy via Service Nodes.
+The following documentation assumes an xCAT cluster has already been configured and covers the additional steps needed to support xCAT Hierarchy via Service Nodes.
 
 .. toctree::
    :maxdepth: 2
 
-   service_nodes/service_nodes101.rst
+   service_nodes/service_nodes.rst
    databases/index.rst
    service_nodes/define_service_nodes.rst
    service_nodes/provision_service_nodes.rst

docs/source/guides/admin-guides/large_clusters/service_nodes/service_nodes.rst

@@ -1,5 +1,5 @@
-Service Nodes 101
-=================
+Service Nodes
+=============
 
 Service Nodes are similar to the xCAT Management Node in that each service Nodes runs an instance of the xCAT daemon: ``xcatd``.  ``xcatd``'s communicate with each other using the same XML/SSL protocol that the xCAT client uses to communicate with ``xcatd`` on the Management Node. 
 

docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst

@@ -62,6 +62,7 @@ Following are the brief characters and adaptability of each method, you can sele
 * **Sequential-based Discovery**
 
   **Step1**: **Pre-define** the **Node Object** for all the nodes in the cluster.
+
   **Step2**: Manually power on the node one by one. The booted node will be discovered, each new discovered node will be assigned to one of the **Pre-defined** node in **Sequential**.
 
   * pros

docs/source/guides/admin-guides/manage_clusters/ppc64le/management.rst

@@ -14,7 +14,7 @@ With xCAT, the end user can turn the beacon light on or off with the commands sh
     rbeacon cn1 on
     rbeacon cn1 off
 
-Please notice, the current state of the beacon light can not be inquery remotely. As a workaround, one can always use the ``rbeacon`` command to trun all the beacon lights in one frame off, and then turn a particular beancon light on. ::
+Please notice, the current state of the beacon light can not be inquery remotely. As a workaround, one can always use the ``rbeacon`` command to turn all the beacon lights in one frame off, and then turn a particular beancon light on. ::
 
     rbeacon a_group_of_cn off
     rbeacon cn5 on
@@ -104,7 +104,7 @@ Firmware Updating
 Configures Nodes' Service Processors
 ````````````````````````````````````
 
-Here comes the command, ``rspconfig``. It is used to configure the service processor of a phyisical machine. On a OpenPower system, the service processor is the BMC, BAse Motherboard Controller. Various variables can be set through the command. But, please also notice, the actual configuration may change among difference machine model type.
+Here comes the command, ``rspconfig``. It is used to configure the service processor of a phyisical machine. On a OpenPower system, the service processor is the BMC, Base Motherboard Controller. Various variables can be set through the command. But, please also notice, the actual configuration may change among difference machine model type.
 
 Examples
 

docs/source/guides/install-guides/zypper/prepare_mgmt_node.rst

@@ -45,5 +45,5 @@ Set up Network
 
 The management node IP address should be set to a **static** ip address.  
 
-Modify the ifcfg-<nic> file under ``/etc/sysconfig/network-scripts`` and configure a static IP address.
+Modify the ifcfg-<nic> file under ``/etc/sysconfig/network`` and configure a static IP address.