Fix some "Raw HTML omitted" warnings and formatting issues (part 3)

content/docs/latest/hcatalog/hcatalog-cli.md

@@ -143,11 +143,11 @@ Any command not listed above is NOT supported and throws an exception with the m
 
 ### Authentication
 
-If a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/`*<username>*`/hive.log`, then make sure you have run "`kinit` *<username>*`@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
+If a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/<username>/hive.log`, then make sure you have run "`kinit <username>@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
 
 ### Error Log
 
-If other errors occur while using the HCatalog CLI, more detailed messages are written to /tmp/*<username>*/hive.log.
+If other errors occur while using the HCatalog CLI, more detailed messages are written to `/tmp/<username>/hive.log`.
 
 
 

content/docs/latest/hcatalog/hcatalog-inputoutput.md

@@ -196,7 +196,7 @@ hdfs:///tmp/slf4j-api-1.6.1.jar
 
 ### Authentication
 
-If a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/`*<username>*`/hive.log`, then make sure you have run "`kinit` *<username>*`@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
+If a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/<username>/hive.log`, then make sure you have run "`kinit <username>@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
 
 ### Read Example
 

content/docs/latest/hcatalog/hcatalog-loadstore.md

@@ -164,7 +164,7 @@ The version number found in each filepath will be substituted for *. For example
 
 #### Authentication
 
-If you are using a secure cluster and a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/`*<username>*`/hive.log`, then make sure you have run "`kinit` *<username>*`@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
+If you are using a secure cluster and a failure results in a message like "2010-11-03 16:17:28,225 WARN hive.metastore ... - Unable to connect metastore with URI thrift://..." in `/tmp/<username>/hive.log`, then make sure you have run "`kinit <username>@FOO.COM`" to get a Kerberos ticket and to be able to authenticate to the HCatalog server.
 
 ### Load Examples
 

content/docs/latest/language/cast-format-with-sql2016-datetime-formats.md

@@ -137,7 +137,7 @@ e.g. input=2019-01-01 20:00, format=“AM”, output=“PM”.
 - Retains the exact format (capitalization and length) provided in the pattern string. If p.m.  
 is in the pattern, we expect a.m. or p.m. in the output; if AM is in the pattern, we expect  
 AM or PM in the output. If the case is mixed (Am or aM) then the output case will match the  
-case of the pattern's first character (Am => AM, aM => am).  
+case of the pattern's first character (Am => AM, aM => am).  
 - String to datetime conversion:  
 - Conflicts with HH24 and SSSSS.  
 - It doesn't matter which meridian indicator is in the pattern.  
@@ -221,21 +221,21 @@ MONTH|Month|month
 Name of month of year  
 - For datetime to string conversion, will include trailing spaces up to length 9 (length of  
 longest month of year name: "September"). Case is taken into account according to the  
-following example (pattern => output):  
-- MONTH => JANUARY  
-- Month => January  
-- month => january  
+following example (pattern => output):  
+- MONTH => JANUARY  
+- Month => January  
+- month => january  
 - For string to datetime conversion, neither the case of the pattern nor the case of the input  
 are taken into account.  
 - For string to datetime conversion, conflicts with MM and MON.
 
 MON|Mon|mon  
 Abbreviated name of month of year  
 - For datetime to string conversion, case is taken into account according to the following  
-example (pattern => output):  
-- MON => JAN  
-- Mon => Jan  
-- mon => jan  
+example (pattern => output):  
+- MON => JAN  
+- Mon => Jan  
+- mon => jan  
 - For string to datetime conversion, neither the case of the pattern nor the case of the input  
 are taken into account.  
 - For string to datetime conversion, conflicts with MM and MONTH.
@@ -244,7 +244,7 @@ DAY|Day|day
 Name of day of week  
 - For datetime to string conversion, will include trailing spaces until length is 9 (length of  
 longest day of week name: "Wednesday"). Case is taken into account according to the following  
-example (pattern => output):  
+example (pattern => output):  
 - DAY = SUNDAY  
 - Day = Sunday  
 - day = sunday  
@@ -255,7 +255,7 @@ are taken into account.
 DY|Dy|dy  
 Abbreviated name of day of week  
 - For datetime to string conversion, case is taken into account according to the following  
-example (pattern => output):  
+example (pattern => output):  
 - DY = SUN  
 - Dy = Sun  
 - dy = sun  
@@ -286,11 +286,11 @@ zone agnostic.
 
 ##### C. Separators
 
--|.|/|,|'|;|:|<space>  
+- |.|/|,|'|;|:|&lt;space&gt;\
 Separator  
 - Uses loose matching. Existence of a sequence of separators in the format should match the  
 existence of a sequence of separators in the input regardless of the types of the separator or  
-the length of the sequence where length > 1. E.g. input=“2019-. ;10/10”, pattern=“YYYY-MM-DD”  
+the length of the sequence where length &gt; 1. E.g. input=“2019-. ;10/10”, pattern=“YYYY-MM-DD”  
 is valid; input=“20191010”, pattern=“YYYY-MM-DD” is not valid.  
 - If the last separator character in the separator substring is "-" and is immediately followed  
 by a time zone hour (tzh) token, it's a negative sign and not counted as a separator, UNLESS