Tile Dev inclusive lang, etc

Double check

Author: bobbygeeze

concourse.html.md.erb

@@ -1,5 +1,5 @@
 ---
-title: How to perform continuous integration testing on your service title
+title: Continuous integration testing on your service tile
 owner: Services
 ---
 
@@ -139,7 +139,7 @@ To configure install properties for your tile using the **Properties** tab:
 3. When you remove all of the red text box, click **Save** or **Save and Run**.
 
 
-### <a id="config-with-advanced-tab"></a> Configure your tile using the advanced - JSON properties Tab
+### <a id="config-with-advanced-tab"></a> Configure your tile using the advanced - JSON properties tab
 
 In the **Advanced - JSON Properties** tab, you configure install properties, specifying them in JSON,
 in the format used by the om tool.
@@ -265,7 +265,7 @@ You define this pipeline in the `pipeline.yml` file that is uploaded to the
 Concourse server. The [Tile Generator](tile-generator.html) contains a sample
 pipeline that you can clone for your own tile.
 
-### <a id="pool"></a> Set up <%= vars.platform_name %> for your CI Pipeline
+### <a id="pool"></a> Set up <%= vars.platform_name %> for your CI pipeline
 
 <%= vars.company_name %> partners who have VMware host their pipeline have access to a pool of <%= vars.platform_name %>
 instances that are managed and are regularly updated with the latest

credhub.html.md.erb

@@ -2,7 +2,7 @@
 title: How to use CredHub with your service tile
 owner: Services
 ---
-You can configure service tiles to store internal credentials in BOSH CredHub, instead of
+You can configure service tiles to store internal credentials in BOSH CredHub instead of
 encoding them in product template and job template files.
 
 BOSH CredHub is a secure credential management component that runs on the BOSH VM to minimize the surface area where

environments.html.md.erb

@@ -3,14 +3,14 @@ title: Development environments for your tile service
 owner: Services
 ---
 
-Learn how to set up a tile development environment, from simple standalone tools to a full Ops Manager
+Learn how to set up a tile development environment from simple standalone tools to a full Ops Manager
 development environment.
 As you progress through the [stages](stages.html) of
 tile development, you might progress through this environment.
 
 ## <a id='pcf'></a> <%= vars.app_runtime_abbr %> with Ops Manager
 
-### <a id='shared'></a> Shared <%= vars.app_runtime_abbr %> Development Environments for VMware Tanzu Partners
+### <a id='shared'></a> Shared <%= vars.app_runtime_abbr %> Development environments for VMware Tanzu Partners
 
 <%= vars.company_name %> operates and manages a number of shared <%= vars.app_runtime_abbr %> development environments,
 called Pivotal Integration Environments (PIEs),
@@ -29,7 +29,7 @@ using the credentials that you use for [Partners Slack](https://pivotalpartners.
 
 If you are not in the PTPP or cannot access the Partners Slack, email [email protected].
 
-### <a id='diy'></a> Install Your Own <%= vars.app_runtime_abbr %> Environment
+### <a id='diy'></a> Install your own <%= vars.app_runtime_abbr %> environment
 
 If you need an isolated or dedicated <%= vars.app_runtime_abbr %> development environment, or you must work offline, you can install your own environment that includes Ops Manager:
 

get-credhub-vars.html.md.erb

@@ -1,5 +1,5 @@
 ---
-title: Fetching variable names and values with CredHub for your services
+title: Fetching variable names and values with CredHub
 owner: CredHub
 ---
 

integrations-index.html.md.erb

@@ -19,6 +19,6 @@ Here is information about service integrations with <%= vars.app_runtime_full %>
     *   [Creating new variables in CredHub](/docs-tiledev/create-credhub-vars.html)
     *   [Migrating existing credentials to CredHub](/docs-tiledev/migrating-credhub-credentials.html)
     *   [Fetching variable names and values](/docs-tiledev/get-credhub-vars.html)
-    *   [Securing service credentials with Rrntime CredHub](/docs-tiledev/ssi-creds-tiledev.html)
+    *   [Securing service credentials with Runtime CredHub](/docs-tiledev/ssi-creds-tiledev.html)
 *   [How to integrate services with Cloud Foundry's logging system](/docs-tiledev/nozzle.html)
 *   [Syslog: migrating existing configuration](/docs-tiledev/migrating-syslog-configuration.html)

migrating-credhub-credentials.html.md.erb

@@ -40,10 +40,7 @@ corresponding CredHub credential types:
   </tr>
 </table>
 
-<p class="note">
-<span class="note__title">Note</span>
-CredHub does not retain the salt when migrating <code>salted_credentials.
-</p>
+<p> CredHub does not retain the salt when you migrate <code>salted_credentials</code>.</p>
 
 See [Property and template references](./property-template-references.html#secret) for more information about credential types.
 
@@ -102,7 +99,7 @@ following the naming conventions in the [Update Values or Property Names using J
 <p class="note">
 <span class="note__title">Note</span>
 While the property blueprint refers to the type as <code>secret</code>, BOSH refers to the
-type as <code>password</code>. See the <a href="#cred-types">CredHub Credential Types</a> table at the beginning of this topic for more information about credential types.
+type as <code>password</code>. See the <a href="#cred-types">CredHub credential types</a> table at the beginning of this topic for more information about credential types.
 </p>
 
 1. In your manifest snippet, replace the existing secret value with the new triple-parenthesis syntax.
@@ -122,4 +119,4 @@ type as <code>password</code>. See the <a href="#cred-types">CredHub Credential
 
 3. Use an API endpoint to confirm that the credential is stored in the variable.
 
-   For more information about the endpoint, see [Fetching Variable Names and Values](./get-credhub-vars.html).
+   For more information about the endpoint, see [Fetching variable names and values](./get-credhub-vars.html).

migrating-syslog-configuration.html.md.erb

@@ -3,7 +3,8 @@ title: Migrating existing syslog configuration to Ops Manager
 owner: Ops Manager
 ---
 
-You can migrate existing syslog properties that are defined by a tile into a syslog form that is provided in Ops Manager v2.9 and later.
+You can migrate existing syslog properties that are defined by a tile into a syslog form that
+is provided in Ops Manager v2.9 and later.
 
 When you enable the Ops Manager syslog feature, Ops Manager:
 

nozzle.html.md.erb

@@ -5,8 +5,7 @@ owner: Services
 You can integrate services with Cloud Foundry's logging system, _Loggregator_, by writing to and
 reading from its _Firehose_ endpoint.
 
-
-Cloud Foundry's Loggregator logging system collects your logs and metrics from apps and platform components
+The Loggregator logging system collects your logs and metrics from apps and platform components
 and streams them to a single endpoint, Firehose.
 
 Your tile can integrate its service with Loggregator in following ways:
@@ -337,7 +336,7 @@ element to carry VM instance information as follows:
 
 ## <a id="metrics"></a> Metrics
 
-The [Monitoring <%= vars.platform_name %>](https://docs.pivotal.io/pivotalcf/monitoring/index.html) topic has a
+The [Logging and metrics in Cloud Foundry](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/data-sources.html) topic has a
 rundown of the
 various metrics and how to make them useful.
 

odb-resource-defaults.html.md.erb

@@ -6,10 +6,10 @@ owner: Ops Manager
 You can configure the drop-down menu items for VM types and persistent disk types in your tile.
 
 On-Demand service tiles have a configuration pane for each service plan.
-You can use the drop-down menus on the configuration pane to set the VM type and persistent disk type for
+You can use the drop-down menu on the configuration pane to set the VM type and persistent disk type for
 each instance of that plan.
 
-Ops Manager populates the menus with options that are based on the VM and disk options available
+Ops Manager populates the menu with options that are based on the VM and disk options available
 on the current IaaS.
 When you set default values for VMs and disk types, it helps you to select the right
 resources for on-demand service

on-demand.html.md.erb

@@ -1,9 +1,9 @@
 ---
-title: How to integrate your software as an on-demand service
+title: How to integrate your software as an On-Demand service
 owner: Services
 ---
 
-You can integrate your software as an on-demand service and service tile for <%= vars.platform_name %>.
+You can integrate your software as an On-Demand service and service tile for <%= vars.platform_name %>.
 
 Brokered service and managed service integrations assume that you have a single VM instance
 deployed for your software, or a limited number of VMs.
@@ -15,29 +15,29 @@ On-Demand (dynamic) services activates this flexibility in a scalable way. When
     not pre-allocate VM resources for service instances. Instead, define an allowable range of VM memory and
     CPU sizes and create a dedicated network on the IaaS to host any required number of service instance VMs.
 
-When a developer creates an instance of an on-demand service, they provision the resources within the
+When a developer creates an instance of an On-Demand service, they provision the resources within the
 allowed range, and BOSH dynamically creates a new, dedicated VM for the instance.
 
-## <a id="create"></a> Create an on-demand service
+## <a id="create"></a> Create an On-Demand service
 
 The best way to create an on-demand service is to use the
 [On-Demand Services SDK](https://docs.vmware.com/en/On-Demand-Services-SDK-for-VMware-Tanzu/0.43/on-demand-services-sdk/GUID-about.html).
 
-The on-demand services SDK provides a generic on-demand service broker (ODB) that
+The On-Demand services SDK provides a generic On-Demand service broker (ODB) that
 the Tile Generator can consume like any other service broker.
 
-The on-demand service author does not write a service broker. Instead, it writes a service adapter
+The On-Demand service author does not write a service broker. Instead, it writes a service adapter
 component that takes requests from the ODB and interfaces with the service software to fulfill requests
 from the ODB.
 
 To create the tile, you need to feed the service adapter and the BOSH release of the ODB to
 [Tile Generator](./tile-generator.html):
 
-* [On-demand services SDK](https://docs.vmware.com/en/On-Demand-Services-SDK-for-VMware-Tanzu/0.43/on-demand-services-sdk/GUID-index.html) documentation explains how to write a service
+* [On-Demand services SDK](https://docs.vmware.com/en/On-Demand-Services-SDK-for-VMware-Tanzu/0.43/on-demand-services-sdk/GUID-index.html) documentation explains how to write a service
 adapter for an on-demand service that uses the ODB.
 
 * After you have the individual components for your brokered service integration, you can work
-through [Building Your First Tile](./index.html#tile-steps) to create your tile.
+through [Building your first tile](./index.html#tile-steps) to create your tile.
 
 At any level of integration, you must use [Concourse](./concourse.html) for continuous integration
 during development.

property-template-references.html.md.erb

@@ -7,7 +7,6 @@ Use these instructions to describe your product template for your tile and learn
 
 The `metadata` subdirectory of a tile contains a product template file in `.yml` file format. The product template file specifies how the tile interface collects configurable properties from the user, and how Ops Manager incorporates these properties into the deployment manifest.
 
-
 ## <a id="product-template"></a> Product template contents
 
 The product template, a `.yml` file in the tile's `metadata` subdirectory, includes or points to:
@@ -30,7 +29,7 @@ a functional tile that is provided by the Ops Manager engineering team that depl
 
 For more information about product template configuration, see [Top-Level Properties](#top-level).
 
-To learn how to configure your tile's forms, see [Form Properties](#form-properties).
+To learn how to configure your tile's forms, see [Form properties](#form-properties).
 
 
 ## <a id='property-values'></a> Editing the product template
@@ -85,7 +84,7 @@ Some property values in a product template, such as CredHub credentials, must be
 
 Ops Manager gets rid of the outer parentheses from these expressions and includes the resulting double-parens expressions in the manifest it generates, for BOSH to evaluate at deploy time.
 
-For more information about tile properties, see [Referencing Properties](#property-refs).
+For more information about tile properties, see [Referencing properties](#property-refs).
 
 ### <a id='property-refs'></a> Referencing properties
 
@@ -107,7 +106,8 @@ Where:
 
 #### <a id="property-location"></a> Referencing a location
 
-The method of referencing the location of the property varies. The following table describes the different methods of referencing a property:
+The method of referencing the location of the property varies.
+The following table describes the different methods of referencing a property:
 
 | Method Name | Description |
 | ----------- | ----------- |
@@ -119,7 +119,8 @@ The method of referencing the location of the property varies. The following tab
 
 #### <a id="accessor-location"></a> Referencing an accessor
 
-Accessors vary between property blueprint types. The following example uses the property blueprint type `string` with its one accessor, `value`:
+Accessors vary between property blueprint types.
+The following example uses the property blueprint type `string` with its one accessor, `value`:
 
 ```console
 (( .properties.example-string.value ))
@@ -133,7 +134,7 @@ For example:
 (( .properties.example-string.value || [] ))
 ```
 
-For more information about the available properties and their accessors, see [Property Blueprint Reference](#property-blueprints).
+For more information about the available properties and their accessors, see [Property Blueprint reference](#property-blueprints).
 
 ### <a id='product'></a> Product context
 

publish.html.md.erb

@@ -7,7 +7,7 @@ You can publish and update your service tile for <%= vars.platform_name %>.
 
 ## <a id="publish"></a> Publish your service tile
 
-The [Partner Software Product Release Cycle](./releases.html) explains how <%= vars.company_name %> works with partners to release VMware Tanzu products,
+The [Partner software product release cycle](./releases.html) explains how <%= vars.company_name %> works with partners to release VMware Tanzu products,
 from the private alpha and closed beta phases, to general availability and publication on [VMware Tanzu Network](http://network.pivotal.io).
 
 After you package your product's BOSH releases, stemcell, metadata, and other tile components into a single zipped download file, post it to VMware Tanzu Network in one of two ways:

publishing-index.html.md.erb

@@ -7,5 +7,5 @@ Learn about how to publish and update your service tile.
 
 *   [Publish and update](/docs-tiledev/publish.html)
 *   [Creating tile documentation](/docs-tiledev/tile-documentation.html)
-*   [Partner software product release Cycle](/docs-tiledev/releases.html)
+*   [Partner software product release cycle](/docs-tiledev/releases.html)
 *   [Upgrading tiles](/docs-tiledev/tile-upgrades.html)

reference.html.md.erb

@@ -11,8 +11,8 @@ building your <%= vars.platform_name %> tiles.
 Use these resources to troubleshoot more complex issues:
 
 - [Troubleshooting <%= vars.platform_name %>](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/troubleshooting.html)
-- [Troubleshooting Applications](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/deploy-apps-troubleshoot-app-health.html)
-- [Advanced Troubleshooting with BOSH CLI](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/3.0/vmware-tanzu-ops-manager/install-trouble-advanced.html)
+- [Troubleshooting applications](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/deploy-apps-troubleshoot-app-health.html)
+- [Advanced troubleshooting with BOSH CLI](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/3.0/vmware-tanzu-ops-manager/install-trouble-advanced.html)
 
 ## <a id="api"></a>API
 
@@ -25,9 +25,9 @@ create listings in the Services Marketplace.
 
 ## <a id="properties"></a>Configuration properties
 
-* [Property and Template References](./property-template-references.html) catalogs how top-level properties, form properties, property blueprints, configurable properties, and job types are defined in tile installer `.yml` files, such as those generated by the Tile Installer or hand-coded legacy tiles. It also explains how to specify the locations of tile configuration properties in a tile installer `.yml` file.
+* [Property and template references](./property-template-references.html) catalogs how top-level properties, form properties, property blueprints, configurable properties, and job types are defined in tile installer `.yml` files, such as those generated by the Tile Installer or hand-coded legacy tiles. It also explains how to specify the locations of tile configuration properties in a tile installer `.yml` file.
 
-* [Property Blueprint Reference](./property-template-references.html#property-blueprints) compiles a list of accessors and values for configuration properties in the `property_blueprints` section of a tile installer `.yml` file.
+* [Property Blueprint reference](./property-template-references.html#property-blueprints) compiles a list of accessors and values for configuration properties in the `property_blueprints` section of a tile installer `.yml` file.
 
 ## <a id="cli"></a>Command Line Tools