[#185085318]

Author: VMWare-JasonAndrew

README.md

@@ -33,7 +33,7 @@ If you are using the Provide instructions in your PRs to indicate which branches
 
 List of terms that VMware wants to use consistently in the doc:
 
-+ The Tile Dashboard–for the UI/product as a whole. For example, "Log on to the Tile Dashboard. [MB 2018.07.11]
++ The Tile Dashboard–for the UI/product as a whole. For example, "Log in to the Tile Dashboard. [MB 2018.07.11]
 + Tile Dashboard CI–for the subsystem of the Tile Dashboard that does the automated testing. For example, "Tile Dashboard CI runs any post-deploy errands that your tile has defined." [MB 2018.07.11]
 
 ## Releasing a New Minor Version

concourse.html.md.erb

@@ -181,7 +181,7 @@ A description of these placeholder values appears on the **Tile Configuration**
 
 To specify the UAA users:
 
-1. [Log on to the Tile Dashboard and Locate the Configuration Page](#navigate-to-tile).
+1. [Log in to the Tile Dashboard and Locate the Configuration Page](#navigate-to-tile).
 
 1. At the bottom of the configuration page, click **+** to expand the box and view the text boxs.
 
@@ -192,7 +192,7 @@ To specify the UAA users:
 
 ###<a id="save-and-run"></a> Save and run
 
-1. [Log on to the Tile Dashboard and Locate the Configuration Page](#navigate-to-tile).
+1. [Log in to the Tile Dashboard and Locate the Configuration Page](#navigate-to-tile).
 
 1. Click **Save and Run**.
 

dev-workflow.html.md.erb

@@ -1,9 +1,9 @@
 ---
 title: Development workflow for your tile
-owner: OpsMan
+owner: Ops Manager
 ---
 
-This document references topics that follow <%= vars.company_name %>'s tile development workflow in [Building Your First Tile](./index.html#tile-steps).
+This page references topics that follow <%= vars.company_name %>'s tile development workflow in [Building Your First Tile](./index.html#tile-steps).
 
 ## <a id="contents"></a> Development workflow
 

embedded-agents.html.md.erb

@@ -5,7 +5,7 @@ owner: Services
 
 Here's how to configuring services that use software agents embedded in application containers.
 
-Some service integrations depend on the ability to inject code into application containers. Examples include:
+Some service integrations can inject code into application containers. Examples include:
 
 - Application Performance Monitoring (APM) agents for monitoring services
 - Container-embedded API gateways

environments.html.md.erb

@@ -3,7 +3,7 @@ title: Development environments for your tile service
 owner: Services
 ---
 
-Here's how to set up tile development environments, from simple standalone tools to a full <%= vars.platform_name %> development environment. As you progress through the [stages](stages.html) of tile development, you might progress through these environments.
+Here's how to set up tile development environments.  As you progress through the [stages](stages.html) of tile development, you might progress through these environments.
 
 
 ## <a id='pcfdev'></a> <%= vars.product_dev_local %> and BOSH-Lite
@@ -47,14 +47,14 @@ for Pivotal Technical Partnership Program (PTPP) program members to develop thei
 
 To use your assigned PIE environment:
 
-1. Log on to the <%= vars.company_name %> [Tile Dashboard](https://tile-dashboard.cfapps.io/)
+1. Log in to the <%= vars.company_name %> [Tile Dashboard](https://tile-dashboard.cfapps.io/)
 using the credentials that you use for [Partners Slack](https://pivotalpartners.slack.com/).
 
 1. Click the `pie-xx` environment assigned to you.
 
-1. Log on to Ops Manager with the given Ops Manager URL and credentials.
+1. Log in to Ops Manager with the given Ops Manager URL and credentials.
 
-1. Log on to Apps Manager or the cf CLI with the Cloud Foundry information provided on the same page.
+1. Log in to Apps Manager or the cf CLI with the Cloud Foundry information provided on the same page.
 
 If you are not in the PTPP or cannot access the Partners Slack, email [email protected].
 

get-credhub-vars.html.md.erb

@@ -18,10 +18,10 @@ Use these endpoints to view variables for any product in Ops Manager, except the
 
 ## <a id="fetch-variables"></a> Fetching variables
 
-This endpoint returns the list of variables associated with a product that are stored in CredHub. Not all variables are stored in CredHub. If you call a variable that is not stored in CredHub, the call returns an empty value.
+This endpoint returns the list of variables associated with a product that are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. Not all variables are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. If you call a variable that is not stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, the call returns an empty value.
 
 <pre class="terminal">
-$ curl "http<span>s</span>://OPS-MAN-FQDN/api/v0/deployed/products/product-guid/variables" \
+$ curl "http<span>s</span>://OPS-MAN-FQDN/api<!--฿ |API| is preferred. ฿-->/v0/deployed/products/product-guid<!--฿ |GUID| is preferred. ฿-->/variables" \
     -X GET \
     -H "Authorization: Bearer EXAMPLE_UAA_ACCESS_TOKEN"
 </pre>
@@ -39,22 +39,22 @@ HTTP/1.1 200 OK
 ### <a id="query-params"></a> Query parameters
 
 <table class="nice">
-	<th>Parameter</th>
-	<th>Description</th>
-	<tr>
-		<td>product_guid</td>
-		<td>The unique product identifier, formatted as a text string</td>
-	</tr>
+  <th>Parameter</th>
+  <th>Description</th>
+  <tr>
+    <td>product_guid</td>
+    <td>The unique product identifier, formatted as a text string</td>
+  </tr>
 </table>
 
 This endpoint returns a variable's name. Use the name in the next endpoint to return the variable's value.
 
 ## <a id="fetch-var-values"></a> Fetching variable values
 
-This endpoint returns the value of a variable stored in CredHub. Not all variables are stored in CredHub, so if you call a variable that isn't in CredHub, the call returns an empty value.
+This endpoint returns the value of a variable stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. Not all variables are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, so if you call a variable that isn't in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, the call returns an empty value.
 
 <pre class="terminal">
-$ curl "http<span>s</span>://OPS-MAN-FQDN/api/v0/deployed/products/product-guid/variables?name=EXAMPLE-VARIABLE-NAME" \
+$ curl "http<span>s</span>://OPS-MAN-FQDN/api<!--฿ |API| is preferred. ฿-->/v0/deployed/products/product-guid<!--฿ |GUID| is preferred. ฿-->/variables?name=EXAMPLE-VARIABLE-NAME" \
     -X GET \
     -H "Authorization: Bearer UAA_ACCESS_TOKEN"
 </pre>
@@ -65,20 +65,20 @@ $ curl "http<span>s</span>://OPS-MAN-FQDN/api/v0/deployed/products/product-guid/
 HTTP/1.1 200 OK
 
 {
-  "credhub-password": "EXAMPLE-PASSWORD"
+  "credhub<!--฿ The CF component is named |CredHub| ฿-->-password": "EXAMPLE-PASSWORD"
 }
 </pre>
 
 ### <a id="query-params-values"></a> Query parameters
 <table>
-	<th>Parameter</th>
-	<th>Description</th>
-	<tr>
-		<td>variable_name</td>
-		<td>The name of the variable, formatted as a text string</td>
-	</tr>
-	<tr>
-		<td>product_guid</td>
-		<td>The unique product identifier, formatted as a text string</td>
-	</tr>
+  <th>Parameter</th>
+  <th>Description</th>
+  <tr>
+    <td>variable_name</td>
+    <td>The name of the variable, formatted as a text string</td>
+  </tr>
+  <tr>
+    <td>product_guid</td>
+    <td>The unique product identifier, formatted as a text string</td>
+  </tr>
 </table>

index.html.md.erb

@@ -79,7 +79,7 @@ Before you publish your tile, you can test it manually using a Partner Integrati
 
 To gain access to your PIE, reach out to your contact at <%= vars.company_name %> or [register as a partner](https://partners.pivotal.io/).
 
-If you already have access to your PIE, for information information about how to log on, see [Development Environments](./environments.html).
+If you already have access to your PIE, for information information about how to log in, see [Development Environments](./environments.html).
 
 #### <a id="document"></a> Step 4: Document your tile
 

integrations-index.html.md.erb

@@ -3,7 +3,7 @@ title: Integrations reference for your services
 owner: Services
 ---
 
-Here's information about service integrations with <%= vars.app_runtime_full %>.
+Here is information about service integrations with <%= vars.app_runtime_full %>.
 
 *   [Types of integration](/docs-tiledev/stages.html)
 *   [User-provided service](/docs-tiledev/user-provided.html)

releases.html.md.erb

@@ -45,7 +45,7 @@ Aa Closed Beta product should include an easy way for users to provide feedback
 ### Steps to Release
 To create a new Closed Beta release for your product:
 
-1. Log on to [VMware Tanzu Network](http://network.pivotal.io).
+1. Log in to [VMware Tanzu Network](http://network.pivotal.io).
 
 1. Create a new release for your product and populate all of the required text boxes.
 
@@ -90,7 +90,7 @@ For more information about the security policy, see [<%= vars.platform_name %> S
 
 ### Steps to Release
 
-1. Log on to [VMware Tanzu Network](http://network.pivotal.io).
+1. Log in to [VMware Tanzu Network](http://network.pivotal.io).
 
 1. Create a new release for your product and populate all of the required text boxes.
 
@@ -130,7 +130,7 @@ Products must meet the following requirements for **General Availability**:
 * Product installation does not require an internet connection, after initial product download.
 
 ### Steps to release
-1. Log on to [VMware Tanzu network](http://network.pivotal.io).
+1. Log in to [VMware Tanzu network](http://network.pivotal.io).
 
 1. Create a new release for your product and populate all of the required text boxes.
 1. Email your <%= vars.company_name %>  contact to request product validation and General Availability release. Provide basic instructions on how to validate the new feature set. <%= vars.company_name %> validates the upgrade scenario and data persistence.

tile-documentation.html.md.erb

@@ -91,7 +91,7 @@ If there are any specific instructions for upgrading the tile, you can include t
 
 Add snapshots for each step when possible or add details as required.
 
-- Log on to Ops Manager.
+- Log in to Ops Manager.
 - Click **Import a Product** and import the Partner Tile.
 - Select the Partner option.
 - Click **Add** on the Partner Tile.