Edit pass on 4 Solution guidance sections (SharePoint#1788)

* Edit pass

* Updated TOC and overview page and titles

* Updated Note text

* Edit pass

* Edit pass

* Fixes

* Edit pass

* Edit pass

* Edit pass

* Updated home page and descriptions; fixes

* Fixes

* Fixed bookmark

* Fixes

* Composite business apps initial edit

* Edit pass

* Edit pass

* Edit pass

* Fixes

* Edit pass

* Fixes

* Updated links

* Updated loc link

* Edit pass

* Edit pass

* Edit pass

* Edit pass

* Final fixes

* Fixes

Author: Linda-Editor

docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md

@@ -404,7 +404,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
     Note the name of the **Outcome** variable: _outcome_0_ (or similar). We use this variable to check the outcome of the task - that is, whether the approver has approved or rejected the document.
 
     > [!NOTE]
-    > The **Outcome** out-argument returns an **Int32** value corresponding to the index of the outcome - that is, **0** for "Approved" and **1** for "Rejected". These integers are the default values provided in the out-of-box SharePoint site column named "Task Outcome."
+    > The **Outcome** out-argument returns an **Int32** value corresponding to the index of the outcome - that is, **0** for "Approved" and **1** for "Rejected". These integers are the default values provided in the out-of-the-box SharePoint site column named "Task Outcome."
 8. Now, in order for the workflow to check the outcome of the task, we need to add another **If** activity and place it following the **SingleTask** activity, but inside the **Then** area, as shown in Figure 17. Setting the **If** condition to " `outcome_0 == 0`" tells us whether the document was approved.
 
    **Figure 17. Adding the IF activity to check the task status.**

docs/general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md

@@ -22,7 +22,7 @@ One of the more significant changes to the workflow architecture is that now all
 For those customers who have created workflows using SharePoint Designer in the past, this is nothing new. Workflows authored using SharePoint Designer have always been fully declarative. This change does benefit customers who create workflows using SharePoint Designer 2013, however, because SharePoint Designer 2013 workflows now support calling and consuming web services.
 ## Why are web services important for SharePoint workflows
 
-Let's start by understanding scenarios in which using web services makes sense. In the days of SharePoint 2007 or SharePoint 2010, writing custom code was common when using Visual Studio to author workflows because that was the best way to perform calculations or implement custom business logic. Any time you encountered a situation in which the out-of-box actions and activities didn't meet your needs, you could fall back on custom code in a managed assembly.
+Let's start by understanding scenarios in which using web services makes sense. In the days of SharePoint 2007 or SharePoint 2010, writing custom code was common when using Visual Studio to author workflows because that was the best way to perform calculations or implement custom business logic. Any time you encountered a situation in which the out-of-the-box actions and activities didn't meet your needs, you could fall back on custom code in a managed assembly.
 
 
 

docs/scenario-guidance/Branding.md

@@ -202,7 +202,7 @@ Cascading style sheet (CSS) plays a large role in SharePoint branding. To succes
 
 - [CSS injection pattern](https://dev.office.com/patterns-and-practices-detail/1852)
 - [AlternateCssUrl & SiteLogoUrl properties in web object](https://dev.office.com/patterns-and-practices-detail/1849)
-- [Making out of the box Seattle master responsive](https://dev.office.com/patterns-and-practices-detail/5823)
+- [Making out-of-the-box Seattle master responsive](https://dev.office.com/patterns-and-practices-detail/5823)
 
 ## Script Embedding and DOM manipulation
 

docs/scenario-guidance/Transformation.md

@@ -116,7 +116,7 @@ When you deactivate your existing sandbox solution from your sites, any assets o
 
 _**Applies to:** Office 365 and SharePoint Server_
 
-Client-side rendering or JSLink is a concept introduced with SharePoint 2013.  With the help of this concept, you can customize the look and feel of SharePoint Out of the box VIEW/ADD/EDIT FORM.
+Client-side rendering or JSLink is a concept introduced with SharePoint 2013.  With the help of this concept, you can customize the look and feel of SharePoint out-of-the-box VIEW/ADD/EDIT FORM.
 
 JSLink is a JavaScript file which will override the default view of your list with the help of logically defined in your custom JSLink file. You can include the JSLink JavaScript file under the Miscellaneous section of your list view web part.
 

docs/solution-guidance/Autotagging-sample-app-for-SharePoint.md

@@ -1,60 +1,49 @@
 ---
-title: Bulk upload documents sample add-in for SharePoint
-ms.date: 11/03/2017
+title: Bulk upload documents sample SharePoint Add-in
+description: As part of your Enterprise Content Management (ECM) strategy, you can bulk upload documents to document libraries, including OneDrive for Business.
+ms.date: 5/2/2018
 ---
-# Bulk upload documents sample add-in for SharePoint
 
-As part of your Enterprise Content Management (ECM) strategy, you can bulk upload documents to document libraries, including OneDrive for Business.
-    
-_**Applies to:** Office 365 | SharePoint 2013 | SharePoint Online_
+# Bulk upload documents sample SharePoint Add-in
 
 > [!NOTE] 
 > The sample uploads one file to a document library. To upload multiple files, you'll need to extend the sample.
 
-This add-in uses a console application to upload files by using REST API calls. Configuration settings are specified in an XML and a CSV file. Use this solution if you want to:
+The Core.BulkDocumentUploader sample add-in uses a console application to upload files by using REST API calls. Configuration settings are specified in an XML and a CSV file. 
 
-- Upload files to SharePoint Online.
-    
+Use this solution if you want to:
+
+- Upload files to SharePoint Online. 
 - Migrate to Office 365 and use a custom migration tool to move your files.
 
 ## Before you begin
-<a name="sectionSection0"> </a>
 
-To get started, download the  [Core.BulkDocumentUploader](https://github.com/SharePoint/PnP/tree/master/Samples/Core.BulkDocumentUploader) sample add-in from the [Office 365 Developer patterns and practices](https://github.com/SharePoint/PnP/tree/dev) project on GitHub.
+To get started, download the [Core.BulkDocumentUploader](https://github.com/SharePoint/PnP/tree/master/Samples/Core.BulkDocumentUploader) sample add-in from the Office 365 Developer Patterns and Practices project on GitHub.
 
-Before you run the code sample, do the following:
+> [!NOTE] 
+> The code in this article is provided as-is, without warranty of any kind, either express or implied, including any implied warranties of fitness for a particular purpose, merchantability, or non-infringement.
 
+Before you run the code sample, do the following:
 
 1. Edit the OneDriveUploader.xml file with the following information:
 
 	- The ___location where you want to save your text and CSV log files.
-    
 	- The file path to your CSV mapping file (for example, C:\PnP\Samples\Core.BulkDocumentUploader\Input\SharePointSites.csv).
-    
 	- The ___location of the company policy files to upload (for example, C:\PnP\Samples\Core.BulkDocumentUploader\Input\OneDriveFiles).
-    
 	- Your SharePoint Online credentials.
-    
 	- The document action to perform (either upload or delete).
-    
 	- The new file name to apply to the file after the file is uploaded to the document library (for example, COMPANY POLICY DOCUMENT.xlsx).
 
 2. In the SharePointSites.csv mapping file, list the document library URL to upload files to, and the name of the company policy file to upload. 
 
-3. Add the file path of the OneDriveUploader.xml file as a command-line argument. To do this, open the Core.BulkDocumentUploader project properties in Solution Explorer, and then choose  **Properties** > **Debug**, as shown in Figure 1.
-    
-    **Figure 1. Setting OneDriveUploader.xml as a command-line argument in the project properties**
+3. Add the file path of the OneDriveUploader.xml file as a command-line argument. To do this, open the Core.BulkDocumentUploader project properties in Solution Explorer, and then choose **Properties** > **Debug**.
 
     ![Screenshot of the Core.BulkDocumentUploader properties pane with Debug highlighted.](media/f1d950b4-82be-4800-9ccc-07fa2c739fad.png)
 
 
-## Using the Core.BulkDocumentUploader sample app
-<a name="sectionSection1"> </a>
+## Using the Core.BulkDocumentUploader sample add-in
 
-From the  **Main** method in Program.cs, the **RecurseActions** method calls the **Run** method in OneDriveMapper.cs. The **Run** method gets the ___location of the file to upload from SharePointSites.csv, and then calls the **IterateCollection** method.
-
-> [!NOTE] 
-> The code in this article is provided as-is, without warranty of any kind, either express or implied, including any implied warranties of fitness for a particular purpose, merchantability, or non-infringement.
+From the **Main** method in Program.cs, the **RecurseActions** method calls the **Run** method in OneDriveMapper.cs. The **Run** method gets the ___location of the file to upload from SharePointSites.csv, and then calls the **IterateCollection** method.
 
 ```csharp
 public override void Run(BaseAction parentAction, DateTime CurrentTime, LogHelper logger)
@@ -71,18 +60,20 @@ public override void Run(BaseAction parentAction, DateTime CurrentTime, LogHelpe
 
 ```
 
+<br/>
+
 The SharePointSite.csv file lists a file to upload and the document library to upload that file to. The  **IterateCollection** method then does the following to upload the file to the document library:
 
 1. Gets the file to upload. 
 
 2. Ensures that the user has permissions to add items.
 
-3. Creates the  **HttpWebRequest** object with the authentication cookie, the REST string request to upload the document, and the HTTP request action method.
+3. Creates the **HttpWebRequest** object with the authentication cookie, the REST string request to upload the document, and the HTTP request action method.
 
 4. Performs the file upload.
 
 > [!NOTE] 
-> The file name is overwritten with the value of  **FileUploadName** specified in OneDriveUploader.xml.
+> The file name is overwritten with the value of **FileUploadName** specified in OneDriveUploader.xml.
 
 ```csharp
 public override void IterateCollection(Collection<string> entries, LogHelper logger)
@@ -212,8 +203,6 @@ public override void IterateCollection(Collection<string> entries, LogHelper log
 ```
 
 ## See also
-<a name="bk_addresources"> </a>
-
--  [Enterprise Content Management solutions for SharePoint 2013 and SharePoint Online](Enterprise-Content-Management-solutions-for-SharePoint-2013-and-SharePoint-Online.md)   
--  [Core.LargeFileUpload sample](https://github.com/SharePoint/PnP/tree/master/Samples/Core.LargeFileUpload)
-    
+  
+- [Core.LargeFileUpload sample](https://github.com/SharePoint/PnP/tree/master/Samples/Core.LargeFileUpload)  
+- [Enterprise Content Management solutions for SharePoint](enterprise-content-management-solutions-for-sharepoint.md)

docs/solution-guidance/Bulk-upload-documents-sample-app-for-SharePoint.md

@@ -20,8 +20,8 @@ Many enterprises need to replicate custom attributes to the SharePoint user prof
 2. A standardized set of attributes are replicated from Azure Active Directory to the SharePoint Online User Profile Store within Office 365. Unlke on-premises SharePoint, these attributes cannot be customized.
 3. A custom synchronization tool taking advantage of the new bulk update APIs. This tool uploads a JSON file to the Office 365 tenant and queues the import process. This tool can be implemented using managed code (.NET) or as a PowerShell script using the new CSOM APIs.
 4. A Line of Business (LOB) system, or any external system, which is the source of the information in the JSON file. This could also be a combination of data from Active Directory and any external system. Notice that from an API perspective, the LOB system could even be an on-premises SharePoint 2013 or 2016 farm.
-5. An out of the box server side timer job running in SharePoint online which checks for queued import requests and will perform the actual import operation based on the API calls and the information within the provided JSON file.
-6. Extended user profile information is available within user profiles and can be used for any out of the box or custom functionality in SharePoint online.
+5. An out-of-the-box server side timer job running in SharePoint online which checks for queued import requests and will perform the actual import operation based on the API calls and the information within the provided JSON file.
+6. Extended user profile information is available within user profiles and can be used for any out-of-the-box or custom functionality in SharePoint online.
 
 > [!NOTE] 
 > The import only works for user profile properties which have **not** been set to be editable by end users. This is to prevent the user profile import process from overriding any information which an end user has already updated. Additionally, the import only allows custom properties that are not active directory core properties. These must be synchronized to Azure Active Directory. For the list of these core directory properties, see the table listed in the FAQ section below.