Merge pull request #9140 from damabe/1429836-Part4

TsqlAcrolinxScores: User Story 1429836, Part 4

Author: ktoliver

docs/t-sql/data-types/binary-and-varbinary-transact-sql.md

@@ -29,14 +29,14 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 Binary data types of either fixed length or variable length.
 
 ## Arguments  
-**binary** [ ( *n* ) ]
-Fixed-length binary data with a length of *n* bytes, where *n* is a value from 1 through 8,000. The storage size is *n* bytes.
+**binary** [ ( _n_ ) ]
+Fixed-length binary data with a length of _n_ bytes, where _n_ is a value from 1 through 8,000. The storage size is _n_ bytes.
 
-**varbinary** [ ( *n* | **max**) ]
-Variable-length binary data. *n* can be a value from 1 through 8,000. **max** indicates that the maximum storage size is 2^31-1 bytes. The storage size is the actual length of the data entered + 2 bytes. The data that is entered can be 0 bytes in length. The ANSI SQL synonym for **varbinary** is **binary varying**.
+**varbinary** [ ( _n_ | **max**) ]
+Variable-length binary data. _n_ can be a value from 1 through 8,000. **max** indicates that the maximum storage size is 2^31-1 bytes. The storage size is the actual length of the data entered + 2 bytes. The data that is entered can be 0 bytes in length. The ANSI SQL synonym for **varbinary** is **binary varying**.
 
 ## Remarks  
-When *n* is not specified in a data definition or variable declaration statement, the default length is 1. When *n* is not specified with the CAST function, the default length is 30.
+The default length is 1 when _n_ isn't specified in a data definition or variable declaration statement. When _n_ isn't specified with the CAST function, the default length is 30.
 
 | Data type | Use when ... |
 | --- | --- |
@@ -46,11 +46,23 @@ When *n* is not specified in a data definition or variable declaration statement
 
 
 ## Converting binary and varbinary data
-When data is converted from a string data type (**char**, **varchar**, **nchar**, **nvarchar**, **binary**, **varbinary**, **text**, **ntext**, or **image**) to a **binary** or **varbinary** data type of unequal length, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] pads or truncates the data on the right. When other data types are converted to **binary** or **varbinary**, the data is padded or truncated on the left. Padding is achieved by using hexadecimal zeros.
+When converting data from a string data type to a **binary** or **varbinary** data type of unequal length, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] pads or truncates the data on the right. These string data types are:
+
+* **char** 
+* **varchar**
+* **nchar**
+* **nvarchar**
+* **binary**
+* **varbinary**
+* **text**
+* **ntext**
+* **image**
+
+When other data types are converted to **binary** or **varbinary**, the data is padded or truncated on the left. Padding is achieved by using hexadecimal zeros.
 
-Converting data to the **binary** and **varbinary** data types is useful if **binary** data is the easiest way to move around data. Converting any value of any type to a binary value of large enough size and then back to the type, always results in the same value if both conversions are taking place on the same version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. The binary representation of a value might change from version to version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
+Converting data to the **binary** and **varbinary** data types is useful if **binary** data is the easiest way to move around data. At some point, you might convert a value type to a binary value of large enough size and then convert it back. This conversion always results in the same value if both conversions are taking place on the same version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. The binary representation of a value might change from version to version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
-You can convert **int**, **smallint**, and **tinyint** to **binary** or **varbinary**, but if you convert the **binary** value back to an integer value, this value will be different from the original integer value if truncation has occurred. For example, the following SELECT statement shows that the integer value `123456` is usually stored as a binary `0x0001e240`:
+You can convert **int**, **smallint**, and **tinyint** to **binary** or **varbinary**. If you convert the **binary** value back to an integer value, this value will be different from the original integer value if truncation has occurred. For example, the following SELECT statement shows that the integer value `123456` is stored as a binary `0x0001e240`:
 
 ```sql
 SELECT CAST( 123456 AS BINARY(4) );  

docs/t-sql/data-types/getreparentedvalue-database-engine.md

@@ -22,7 +22,7 @@ manager: craigg
 # GetReparentedValue (Database Engine)
 [!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-asdb-xxxx-xxx-md.md)]
 
-Returns a node whose path from the root is the path to *newRoot*, followed by the path from *oldRoot* to *this*.
+Returns a node whose path from the root is the path to _newRoot_, followed by the path from _oldRoot_.
 
 ## Syntax  
 
@@ -37,24 +37,24 @@ SqlHierarchyId GetReparentedValue ( SqlHierarchyId oldRoot , SqlHierarchyId newR
 ```  
 
 ## Arguments  
-*oldRoot*  
+_oldRoot_  
 A **hierarchyid** that is the node that represents the level of the hierarchy that is to be modified.
 
-*newRoot*  
-A **hierarchyid** that represents the node that will replace the *oldRoot* section of the current node in order to move the node.
+_newRoot_  
+A **hierarchyid** that represents the node. Replace the _oldRoot_ section of the current node to move the node.
 
 ## Return Types  
 **SQL Server return type:hierarchyid**
 
 **CLR return type:SqlHierarchyId**
 
 ## Remarks  
-Can be used to modify the tree by moving nodes from *oldRoot* to *newRoot*. GetReparentedValue can be used to move a node of a hierarchy to a new location in the hierarchy. The **hierarchyid** data type represents but does not enforce the hierarchical structure. Users must ensure that the hierarchyid is appropriately structured for the new location. A unique index on the **hierarchyid** data type can help prevent duplicate entries. For an example of moving an entire subtree, see [Hierarchical Data (SQL Server)](../../relational-databases/hierarchical-data-sql-server.md).
+Used to modify the tree by moving nodes from _oldRoot_ to _newRoot_. GetReparentedValue is used to move a hierarchy node to a new location in the hierarchy. The **hierarchyid** data type represents but doesn't enforce the hierarchical structure. Users must ensure that the hierarchyid is appropriately structured for the new location. A unique index on the **hierarchyid** data type can help prevent duplicate entries. For an example of moving an entire subtree, see [Hierarchical Data (SQL Server)](../../relational-databases/hierarchical-data-sql-server.md).
 
 ## Examples  
 
 ### A. Comparing two node locations  
-The following example shows the current hierarchyid of a node. It also shows what the **hierarchyid** of the node would be if the node were moved to become a descendant of the **@NewParent** node. It uses the `ToString()` method to show the hierarchical relationships.
+The following example shows the current hierarchyid of a node. It also shows what the **hierarchyid** of the node would be if you move the node to become a descendant of the **@NewParent** node. It uses the `ToString()` method to show the hierarchical relationships.
 
 ```sql
 DECLARE @SubjectEmployee hierarchyid , @OldParent hierarchyid, @NewParent hierarchyid