fix typos

Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/f4bd3ef5
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/f4bd3ef5
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/f4bd3ef5

Branch: refs/heads/develop
Commit: f4bd3ef5adafe09e818fcb9d7a77912cc536f875
Parents: d4d4283
Author: Lisa Owen <lo...@pivotal.io>
Authored: Fri Oct 14 15:20:35 2016 -0700
Committer: Lisa Owen <lo...@pivotal.io>
Committed: Fri Oct 14 15:20:35 2016 -0700

----------------------------------------------------------------------
 clientaccess/disable-kerberos.html.md.erb              | 2 +-
 reference/catalog/gp_configuration_history.html.md.erb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/f4bd3ef5/clientaccess/disable-kerberos.html.md.erb
----------------------------------------------------------------------
diff --git a/clientaccess/disable-kerberos.html.md.erb 
b/clientaccess/disable-kerberos.html.md.erb
index b5d7eeb..5646eec 100644
--- a/clientaccess/disable-kerberos.html.md.erb
+++ b/clientaccess/disable-kerberos.html.md.erb
@@ -4,7 +4,7 @@ title: Disabling Kerberos Security
 
 Follow these steps to disable Kerberos security for HAWQ and PXF for manual 
installations.
 
-**Note:** If you install or manager your cluster using Ambari, then the HAWQ 
Ambari plug-in automatically disables security for HAWQ and PXF when you 
disable security for Hadoop. The following instructions are only necessary for 
manual installations, or when Hadoop security is disabled outside of Ambari.
+**Note:** If you install or manage your cluster using Ambari, then the HAWQ 
Ambari plug-in automatically disables security for HAWQ and PXF when you 
disable security for Hadoop. The following instructions are only necessary for 
manual installations, or when Hadoop security is disabled outside of Ambari.
 
 1.  Disable Kerberos on the Hadoop cluster on which you use HAWQ.
 2.  Disable security for HAWQ:

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/f4bd3ef5/reference/catalog/gp_configuration_history.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/catalog/gp_configuration_history.html.md.erb 
b/reference/catalog/gp_configuration_history.html.md.erb
index bfc9425..e501d55 100644
--- a/reference/catalog/gp_configuration_history.html.md.erb
+++ b/reference/catalog/gp_configuration_history.html.md.erb
@@ -2,7 +2,7 @@
 title: gp_configuration_history
 ---
 
-The `gp_configuration_history` table contains information about system changes 
related to fault detection and recovery operations. The HAWQ [fault tolerance 
service](../../admin/FaultTolerance.html) logs data to this table, as do 
certain related management utilities such as `hawq init`. For example, when you 
add a new segment to the system, records for these events are logged to 
`gp_configuration_history`. If a segment is marked as down by the fault 
tolerance service in the 
[gp_segment_configuration](gp_segment_configuration.html) catalog table, then 
the reason for being marked as down is recorded in this table.
+The `gp_configuration_history` table contains information about system changes 
related to fault detection and recovery operations. The HAWQ [fault tolerance 
service](../../admin/FaultTolerance.html) logs data to this table, as do 
certain related management utilities such as `hawq init`. For example, when you 
add a new segment to the system, records for these events are logged to 
`gp_configuration_history`. If a segment is marked as down by the fault 
tolerance service in the 
[gp\_segment\_configuration](gp_segment_configuration.html) catalog table, then 
the reason for being marked as down is recorded in this table.
 
 The event descriptions stored in this table may be helpful for troubleshooting 
serious system issues in collaboration with HAWQ support technicians.
 

Reply via email to