Merge pull request #39 from Microsoft/jodebrui

minor readme fixes

samples/databases/wide-world-importers/sample-scripts/always-encrypted/README.md

@@ -1,4 +1,4 @@
-# Sample for use of Always Encrypted in WideWorldImportersDW
+# Sample for use of Always Encrypted in WideWorldImporters
 
 This script demonstrates the use of Always Encrypted to encrypt sensitive data in the database.
 
@@ -17,7 +17,6 @@ This script demonstrates the use of Always Encrypted to encrypt sensitive data i
 
 ## About this sample
 
-<!-- Delete the ones that don't apply -->
 1. **Applies to:** SQL Server 2016 (or higher), Azure SQL Database
 1. **Key features:** Always Encrypted
 1. **Workload:** OLTP
@@ -33,7 +32,6 @@ To run this sample, you need the following prerequisites.
 
 **Software prerequisites:**
 
-<!-- Examples -->
 1. SQL Server 2016 (or higher) or Azure SQL Database.
 2. SQL Server Management Studio
 3. Visual Studio 2015
@@ -63,7 +61,7 @@ The code included in this sample is not intended to be used for production purpo
 <a name=related-links></a>
 
 ## Related Links
-<!-- Links to more articles. Remember to delete "en-us" from the link path. -->
+
 For more information, see these articles:
 - [Always Encrypted documentation](https://msdn.microsoft.com/library/mt163865.aspx)
 - [Keep Sensitive Data Secure with Always Encrypted](https://channel9.msdn.com/Events/DataDriven/SQLServer2016/AlwaysEncrypted)

samples/databases/wide-world-importers/workload-drivers/vehicle-location-insert/README.md

@@ -18,7 +18,6 @@ The main purpose is to compare the performance of data insertion into traditiona
 
 ## About this sample
 
-<!-- Delete the ones that don't apply -->
 1. **Applies to:** SQL Server 2016 (or higher), Azure SQL Database
 1. **Key features:** Core database features
 1. **Workload:** OLTP
@@ -34,7 +33,6 @@ To run this sample, you need the following prerequisites.
 
 **Software prerequisites:**
 
-<!-- Examples -->
 1. SQL Server 2016 (or higher) or Azure SQL Database.
 2. Visual Studio 2015.
 3. The WideWorldImporters database (Full version).
@@ -47,7 +45,7 @@ To run this sample, you need the following prerequisites.
 
 2. Build the solution.
 
-3. Connect to the database and
+3. Connect to the database and run the script VehicleLocation.sql to create the memory-optimized and disk-based tables used for the comparison.
 
 4. Run the app and follow the instructions on-screen. Compare the time taken for On Disk and In Memory insertion.
 
@@ -77,5 +75,5 @@ The code included in this sample is not intended to be used for production purpo
 <a name=related-links></a>
 
 ## Related Links
-<!-- Links to more articles. Remember to delete "en-us" from the link path. -->
+
 - [in-memory/ticket-reservations](/samples/features/in-memory/ticket-reservations)

samples/databases/wide-world-importers/wwi-integration-etl/README.md

@@ -32,7 +32,6 @@ To run this sample, you need the following prerequisites.
 
 **Software prerequisites:**
 
-<!-- Examples -->
 1. SQL Server 2016 (or higher) with the databases WideWorldImporters and WideWorldImportersDW. These can be on different instances.
 2. Visual Studio 2015.
 3. SQL Server 2016 Integration Services.
@@ -91,6 +90,5 @@ The code included in this sample is not intended to be used for production purpo
 <a name=related-links></a>
 
 ## Related Links
-<!-- Links to more articles. Remember to delete "en-us" from the link path. -->
 For more information, see these articles:
 - [SQL Server Integration Services documentation](https://msdn.microsoft.com/library/ms141026.aspx)