Manual fixes of false-positives. json, xml.

MightyPen · MightyPen · commit 6a9a0521d213 · 2020-04-17T00:51:04.000-07:00
diff --git a/docs/t-sql/functions/json-value-transact-sql.md b/docs/t-sql/functions/json-value-transact-sql.md
@@ -117,7 +117,7 @@ ORDER BY JSON_VALUE(jsonInfo,'$.info.address[0].town')
 ### Example 2
  The following example extracts the value of the JSON property `town` into a local variable.  
   
-```syntaxsql
+```sql
 DECLARE @jsonInfo NVARCHAR(MAX)
 DECLARE @town NVARCHAR(32)
 
diff --git a/docs/t-sql/functions/translate-transact-sql.md b/docs/t-sql/functions/translate-transact-sql.md
@@ -1,7 +1,7 @@
 ---
 title: "TRANSLATE (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: 02/01/2019
+ms.date: 04/16/2020
 ms.prod: sql
 ms.prod_service: "sql-database"
 ms.reviewer: ""
@@ -25,7 +25,7 @@ Returns the string provided as a first argument after some characters specified
 
 ## Syntax
 
-```sql
+```syntaxsql
 TRANSLATE ( inputString, characters, translations)
 ```
 
@@ -60,21 +60,21 @@ This is dissimilar to the behavior of multiple `REPLACE` functions, as each func
 
 The following query replaces square and curly braces in the input string with parentheses:
 
-```syntaxsql
+```sql
 SELECT TRANSLATE('2*[3+4]/{7-2}', '[]{}', '()()');
 ```
 
 [!INCLUDE[ssResult_md](../../includes/ssresult-md.md)]
 
-```plain_text
+```text
 2*(3+4)/(7-2)
 ```
 
 #### Equivalent calls to REPLACE
 
 In the following SELECT statement, there is a group of four nested calls to the REPLACE function. This group is equivalent to the one call made to the TRANSLATE function in the preceding SELECT:
 
-```syntaxsql
+```sql
 SELECT
 REPLACE
 (
@@ -103,7 +103,7 @@ REPLACE
 
 GeoJSON is a format for encoding a variety of geographic data structures. With the `TRANSLATE` function, developers can easily convert GeoJSON points to WKT format and vice versa. The following query replaces square and curly braces in input  with regular braces:
 
-```syntaxsql
+```sql
 SELECT TRANSLATE('[137.4, 72.3]' , '[,]', '( )') AS Point,
     TRANSLATE('(137.4 72.3)' , '( )', '[,]') AS Coordinates;
 ```
diff --git a/docs/t-sql/language-elements/else-if-else-transact-sql.md b/docs/t-sql/language-elements/else-if-else-transact-sql.md
@@ -52,14 +52,14 @@ IF Boolean_expression
 ### A. Using a simple Boolean expression  
  The following example has a simple Boolean expression (`1=1`) that is true and, therefore, prints the first statement.  
   
-```syntaxsql
+```sql
 IF 1 = 1 PRINT 'Boolean_expression is true.'  
 ELSE PRINT 'Boolean_expression is false.' ;  
 ```  
   
  The following example has a simple Boolean expression (`1=2`) that is false, and therefore prints the second statement.  
   
-```syntaxsql
+```sql
 IF 1 = 2 PRINT 'Boolean_expression is true.'  
 ELSE PRINT 'Boolean_expression is false.' ;  
 GO  
@@ -68,7 +68,7 @@ GO
 ### B. Using a query as part of a Boolean expression  
  The following example executes a query as part of the Boolean expression. Because there are 10 bikes in the `Product` table that meet the `WHERE` clause, the first print statement will execute. Change `> 5` to `> 15` to see how the second part of the statement could execute.  
   
-```  
+```sql
 USE AdventureWorks2012;  
 GO  
 IF   
@@ -81,7 +81,7 @@ GO
 ### C. Using a statement block  
  The following example executes a query as part of the Boolean expression and then executes slightly different statement blocks based on the result of the Boolean expression. Each statement block starts with `BEGIN` and completes with `END`.  
   
-```  
+```sql
 USE AdventureWorks2012;  
 GO  
 DECLARE @AvgWeight decimal(8,2), @BikeCount int  
@@ -113,7 +113,7 @@ GO
 ### D. Using nested IF...ELSE statements  
  The following example shows how an IF ... ELSE statement can be nested inside another. Set the `@Number` variable to `5`, `50`, and `500` to test each statement.  
   
-```  
+```sql
 DECLARE @Number int;  
 SET @Number = 50;  
 IF @Number > 100  
@@ -133,7 +133,7 @@ GO
 ### E: Using a query as part of a Boolean expression  
  The following example uses `IF...ELSE` to determine which of two responses to show the user, based on the weight of an item in the `DimProduct` table.  
   
-```  
+```sql
 -- Uses AdventureWorks  
   
 DECLARE @maxWeight float, @productKey integer  
diff --git a/docs/t-sql/statements/create-view-transact-sql.md b/docs/t-sql/statements/create-view-transact-sql.md
@@ -1,7 +1,7 @@
 ---
 title: "CREATE VIEW (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "10/10/2018"
+ms.date: 04/16/2020
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
 ms.reviewer: ""
@@ -204,7 +204,7 @@ OR ALTER
   
  A partitioned view on `Server1` is defined in the following way:  
   
-```  
+```sql
 --Partitioned view as defined on Server1  
 CREATE VIEW Customers  
 AS  
@@ -223,7 +223,7 @@ FROM Server3.CompanyData.dbo.Customers_99;
   
  Generally, a view is said to be a partitioned view if it is of the following form:  
   
-```  
+```syntaxsql
 SELECT <select_list1>  
 FROM T1  
 UNION ALL  
@@ -247,21 +247,21 @@ FROM Tn;
   
          Constraint `C1` defined on table `T1` must be of the following form:  
   
-   syntaxsql
+        ```syntaxsql
         C1 ::= < simple_interval > [ OR < simple_interval > OR ...]  
         < simple_interval > :: =   
         < col > { < | > | \<= | >= | = < value >}   
         | < col > BETWEEN < value1 > AND < value2 >  
         | < col > IN ( value_list )  
         | < col > { > | >= } < value1 > AND  
         < col > { < | <= } < value2 >  
-   syntaxsql
+        ```
   
     -   The constraints must be in such a way that any specified value of `<col>` can satisfy, at most, one of the constraints `C1, ..., Cn` so that the constraints form a set of disjointed or nonoverlapping intervals. The column `<col>` on which the disjointed constraints are defined is called the partitioning column. Note that the partitioning column may have different names in the underlying tables. The constraints must be in an enabled and trusted state for them to meet the previously mentioned conditions of the partitioning column. If the constraints are disabled, re-enable constraint checking by using the CHECK CONSTRAINT *constraint_name* option of ALTER TABLE, and using the WITH CHECK option to validate them.  
   
          The following examples show valid sets of constraints:  
   
-   syntaxsql
+        ```syntaxsql
         { [col < 10], [col between 11 and 20] , [col > 20] }  
         { [col between 11 and 20], [col between 21 and 30], [col between 31 and 100] }  
         ```  
@@ -350,7 +350,7 @@ The following examples use the AdventureWorks 2012 or AdventureWorksDW database.
 ### A. Using a simple CREATE VIEW  
  The following example creates a view by using a simple `SELECT` statement. A simple view is helpful when a combination of columns is queried frequently. The data from this view comes from the `HumanResources.Employee` and `Person.Person` tables of the [!INCLUDE[ssSampleDBnormal](../../includes/sssampledbnormal-md.md)] database. The data provides name and hire date information for the employees of [!INCLUDE[ssSampleDBCoFull](../../includes/sssampledbcofull-md.md)]. The view could be created for the person in charge of tracking work anniversaries but without giving this person access to all the data in these tables.  
   
-```  
+```sql
 CREATE VIEW hiredate_view  
 AS   
 SELECT p.FirstName, p.LastName, e.BusinessEntityID, e.HireDate  
@@ -365,7 +365,7 @@ GO
   
 **Applies to**: [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)] and later and [!INCLUDE[ssSDS](../../includes/sssds-md.md)].  
   
-```  
+```sql
 CREATE VIEW Purchasing.PurchaseOrderReject  
 WITH ENCRYPTION  
 AS  
@@ -381,7 +381,7 @@ GO
 ### C. Using WITH CHECK OPTION  
  The following example shows a view named `SeattleOnly` that references five tables and allows for data modifications to apply only to employees who live in Seattle.  
   
-```  
+```sql
 CREATE VIEW dbo.SeattleOnly  
 AS  
 SELECT p.LastName, p.FirstName, e.JobTitle, a.City, sp.StateProvinceCode  
@@ -402,7 +402,7 @@ GO
 ### D. Using built-in functions within a view  
  The following example shows a view definition that includes a built-in function. When you use functions, you must specify a column name for the derived column.  
   
-```  
+```sql
 CREATE VIEW Sales.SalesPersonPerform  
 AS  
 SELECT TOP (100) SalesPersonID, SUM(TotalDue) AS TotalSales  
@@ -416,7 +416,7 @@ GO
 ### E. Using partitioned data  
  The following example uses tables named `SUPPLY1`, `SUPPLY2`, `SUPPLY3`, and `SUPPLY4`. These tables correspond to the supplier tables from four offices, located in different countries/regions.  
   
-```  
+```sql
 --Create the tables and insert the values.  
 CREATE TABLE dbo.SUPPLY1 (  
 supplyID INT PRIMARY KEY CHECK (supplyID BETWEEN 1 and 150),  
@@ -463,7 +463,7 @@ GO
 ### F. Creating a simple view  
  The following example creates a view by selecting only some of the columns from the source table.  
   
-```  
+```sql
 CREATE VIEW DimEmployeeBirthDates AS  
 SELECT FirstName, LastName, BirthDate   
 FROM DimEmployee;  
@@ -472,7 +472,7 @@ FROM DimEmployee;
 ### G. Create a view by joining two tables  
  The following example creates a view by using a `SELECT` statement with an `OUTER JOIN`. The results of the join query populate the view.  
   
-```  
+```sql
 CREATE VIEW view1  
 AS 
 SELECT fis.CustomerKey, fis.ProductKey, fis.OrderDateKey, 
diff --git a/docs/t-sql/xml/query-method-xml-data-type.md b/docs/t-sql/xml/query-method-xml-data-type.md
@@ -1,7 +1,7 @@
 ---
 title: "query() Method (xml Data Type) | Microsoft Docs"
 ms.custom: ""
-ms.date: "07/26/2017"
+ms.date: 04/16/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: t-sql
@@ -22,7 +22,7 @@ Specifies an XQuery against an instance of the **xml** data type. The result is
   
 ## Syntax  
   
-```  
+```syntaxsql
   
 query ('XQuery')  
 ```  
@@ -39,7 +39,7 @@ The following example declares a variable **\@myDoc** of **xml** type and assign
   
 The query retrieves the <`Features`> child element of the <`ProductDescription`> element:  
   
-```  
+```sql
 declare @myDoc xml  
 set @myDoc = '<Root>  
 <ProductDescription ProductID="1" ProductName="Road Bike">  
@@ -64,7 +64,7 @@ The following output shows the result:
 ### B. Using the query() method against an XML type column  
 In the following example, the **query()** method is used to specify an XQuery against the **CatalogDescription** column of **xml** type in the **AdventureWorks** database:  
   
-```syntaxsql
+```sql
 SELECT CatalogDescription.query('  
 declare namespace PD="https://schemas.microsoft.com/sqlserver/2004/07/adventure-works/ProductModelDescription";  
 <Product ProductModelID="{ /PD:ProductDescription[1]/@ProductModelID }" />  
@@ -94,7 +94,7 @@ The following output shows the partial result:
   
 Note the query() and exist() methods both declare the PD prefix. In these cases, you can use WITH XMLNAMESPACES to first define the prefixes and use it in the query.  
   
-```syntaxsql
+```sql
 WITH XMLNAMESPACES 
 (  
    'https://schemas.microsoft.com/sqlserver/2004/07/adventure-works/ProductModelDescription' AS PD,  
