Merge pull request #1 from stevjohnson/pull-requests_10-6-14

Pull requests from 10-6-14

Author: Steve Johnson

guides/m2devgde/v1.0.0.0/integration/integration-auth.md

@@ -7,6 +7,8 @@ title: Understanding Integration Authorization
 
 <p><a href="{{ site.githuburl }}guides/m2devgde/v1.0.0.0/integration/integration-auth.md" target="_blank"><em>Help us improve this page</em></a>&nbsp;<img src="{{ site.baseurl }}common/images/newWindow.gif"/></p>
 
+Hello
+
 There are two ways to authenticate the third-party system with Magento:
 
 *  (Preferred) Using a secure, cloud-based OAuth workflow

guides/m2devgde/v1.0.0.0/rest/rest-overview.md

@@ -9,13 +9,13 @@ title: Accessing Magento Objects Using REST
 
 <h2 id="rest-call">How to Make a REST Call</h2>
 
-All REST calls for the Customer service are contained in ~webapi.xml~; however, inputs and return values are defined in their respective interfaces.
+All REST calls for the Customer service are contained in `webapi.xml`; however, inputs and return values are defined in their respective service interfaces.
 
 To make a REST call for the Customer service:
 
 <h3 id="rest-call-step1">Step 1: Look up the call in webapi.xml:</h3>
 
-This section discusses how to make an HTTP GET call to the getCustomer method.
+This section uses as an example how to make an HTTP GET call to the getCustomer method.
 
 1.	Open `webapi.xml`.
 
@@ -32,7 +32,7 @@ In this example, `GET /V1/customerAccounts/:customerId/customer`
 
 *Note*: Any value prefixed by a colon character is a required input. In the preceding example, `:customerId` indicates you must provide the customer ID.
 
-*Note*: Some REST calls have no route; for these cases, use the Base URL only.
+*Note*: Some REST calls have no route; for these calls, use the Base URL only.
 
 <h3 id="rest-call-step2">Step 2: Find the response object</h3>
 

guides/m2devgde/v1.0.0.0/svcs-framework/compare_mage1_mage2.md

@@ -3,7 +3,7 @@ layout: howtom2devgde_chapters
 title: Services Use Case—Magento 1 and Magento 2 Side By Side 
 ---
 
-# Services Use Case—Magento 1 and Magento 2 Side By Side
+<h1 id="svcs-use-case-mage1">Services Use Case&mdash;Magento 1 and Magento 2 Side By Side</h1>
 
 <p><a href="{{ site.githuburl }}guides/m2devgde/v1.0.0.0/svcs-framework/compare_mage1_mage2.md" target="_blank"><em>Help us improve this page</em></a>&nbsp;<img src="{{ site.baseurl }}common/images/newWindow.gif"/></p>
 
@@ -34,7 +34,7 @@ Magento 2 implementation:
 
 Both implementations:
 
-*	Use a template and two blocks
+*	Use one template and two blocks
 *	Return the address object as HTML
 
 However, the similarities end there. The following table shows the key differences between the implementations:
@@ -74,7 +74,7 @@ Magento 2 implementation:
 
 <p><img src="{{ site.baseurl }}common/images/services_service-interaction_checkout-reg_mage2.png"/></p>
 
-### Discussion of Register During Checkout Example
+### Discussion of the Register During Checkout Example
 
 These two implementations both start with the controller calling the <tt>saveOrder</tt> method on the Onepage class, then Onepage calling <tt>submitOrder</tt> on the Quote class.