Acrolinx

BYHAM · web-flow · commit ce0c5bf4c94e · 2017-07-06T10:15:15.000-07:00
diff --git a/docs/t-sql/functions/scope-identity-transact-sql.md b/docs/t-sql/functions/scope-identity-transact-sql.md
@@ -28,7 +28,7 @@ manager: "jhubbard"
 # SCOPE_IDENTITY (Transact-SQL)
 [!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx_md](../../includes/tsql-appliesto-ss2008-asdb-xxxx-xxx-md.md)]
 
-  Returns the last identity value inserted into an identity column in the same scope. A scope is a module: a stored procedure, trigger, function, or batch. Therefore, two statements are in the same scope if they are in the same stored procedure, function, or batch.  
+  Returns the last identity value inserted into an identity column in the same scope. A scope is a module: a stored procedure, trigger, function, or batch. Therefore, if two statements are in the same stored procedure, function, or batch, they are in the same scope.  
   
  ![Topic link icon](../../database-engine/configure-windows/media/topic-link.gif "Topic link icon") [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
   
@@ -50,7 +50,7 @@ SCOPE_IDENTITY()
   
  For example, there are two tables, T1 and T2, and an INSERT trigger is defined on T1. When a row is inserted to T1, the trigger fires and inserts a row in T2. This scenario illustrates two scopes: the insert on T1, and the insert on T2 by the trigger.  
   
- Assuming that both T1 and T2 have identity columns, @@IDENTITY and SCOPE_IDENTITY will return different values at the end of an INSERT statement on T1. @@IDENTITY will return the last identity column value inserted across any scope in the current session. This is the value inserted in T2. SCOPE_IDENTITY() will return the IDENTITY value inserted in T1. This was the last insert that occurred in the same scope. The SCOPE_IDENTITY() function will return the null value if the function is invoked before any INSERT statements into an identity column occur in the scope.  
+ Assuming that both T1 and T2 have identity columns, @@IDENTITY and SCOPE_IDENTITY return different values at the end of an INSERT statement on T1. @@IDENTITY returns the last identity column value inserted across any scope in the current session. This is the value inserted in T2. SCOPE_IDENTITY() returns the IDENTITY value inserted in T1. This was the last insert that occurred in the same scope. The SCOPE_IDENTITY() function returns the null value if the function is invoked before any INSERT statements into an identity column occur in the scope.  
   
  Failed statements and transactions can change the current identity for a table and create gaps in the identity column values. The identity value is never rolled back even though the transaction that tried to insert the value into the table is not committed. For example, if an INSERT statement fails because of an IGNORE_DUP_KEY violation, the current identity value for the table is still incremented.  
   
@@ -120,13 +120,14 @@ GO
   
  [!INCLUDE[ssResult](../../includes/ssresult-md.md)]  
 ```
+/*SCOPE_IDENTITY returns the last identity value in the same scope. This was the insert on table TZ.*/`  
 SCOPE_IDENTITY  
 4  
-/*SCOPE_IDENTITY returned the last identity value in the same scope. This was the insert on table TZ.*/`  
 
+/*@@IDENTITY returns the last identity value inserted to TY by the trigger. 
+  This fired because of an earlier insert on TZ.*/
 @@IDENTITY  
 115  
-/*@@IDENTITY returned the last identity value inserted to TY by the trigger. This fired because of an earlier insert on TZ.*/
 ```  
   
 ### B. Using @@IDENTITY and SCOPE_IDENTITY() with replication  
