[#185473625]

Author: VMWare-JasonAndrew

dev-workflow.html.md.erb

@@ -14,10 +14,10 @@ The following topics can help you learn the necessary background information to
 * [Tile basics](./tile-basics.html) describes how <%= vars.platform_name %>, service brokers, and tiles work together, and how tiles are structured.
 
 * [Types of integrations](./stages.html) gives a high-level view of a staged tile development process that iterates through increasing levels of integration:
-	- [User-provided service](./user-provided.html)
-	- [Brokered service](./brokered.html)
-	- [Managed service](./managed.html)
-	- [On-demand service](./on-demand.html)
+  - [User-provided service](./user-provided.html)
+  - [Brokered service](./brokered.html)
+  - [Managed service](./managed.html)
+  - [On-demand service](./on-demand.html)
 
 * [Development environments](./environments.html) describes how to set up development environments for different stages and levels in the tile development process.
 
@@ -29,4 +29,4 @@ The following topics can help you learn the necessary background information to
 
 * [Reference](./reference.html) provides language references for tile elements such as the Service Broker API and the Properties list for tile configuration.
 
-* [Tanzu ISV partner program contact information](./contacts.html) lists contacts to learn more about the VMware Tanzu ISV Partner Program or request our help with your integration project, and explains where you can contribute to this documentation.
+* [Tanzu ISV partner program contact information](./contacts.html)<!--฿ If this file is a partial, do not use relative links. ฿--> lists contacts to learn more about the VMware Tanzu ISV Partner Program or request our help with your integration project, and explains where you can contribute to this documentation.

managed.html.md.erb

@@ -23,7 +23,7 @@ To integrate your service at this level, you configure to learn about stemcells,
 
 ### <a id="managed-mvp"></a> Minimal viable product
 
-Minimal Viable Product (MVP) version of a managed service should aim for a single, shared service instance, and don't yet
+Minimal Viable Product (MVP) version of a managed service be a single, shared service instance, and don't yet
 worry too much about High Availability of this instance. This integration level is mostly about getting the BOSH packaging, deployment, and monitoring working
 correctly.
 
@@ -43,7 +43,7 @@ your persistent storage across those as well.
 * For BOSH to manage your service, you must create a BOSH release for it.
 [BOSH releases](./bosh-release.html) explains how to do this, and how to use your already-existing Docker image as a shortcut.
 
-* After you have created a BOSH release for your managed service integration, you can work through [Building your first tile](./index.html#tile-steps) to create your tile.
+* After you created a BOSH release for your managed service integration, you can work through [Building your first tile](./index.html#tile-steps) to create your tile.
 
 * The [Tile generator](./tile-generator.html) tool automatically creates the life cycle errands that can run after a <%= vars.platform_name %> tile is deployed or before it is removed. Operators control which errands run the next time they click **Apply Changes** to redeploy. See the [Errands](./tile-errands.html) topic for how <%= vars.platform_name %> operators control when errands run, and how to set default errand run rules in the tile.
 

migrating-syslog-configuration.html.md.erb

@@ -141,7 +141,7 @@ longer used to configure the syslog.
 1. Run a test deploy of your tile by doing the procedures in [Testing Tiles](./testing.html).
 
 1. To verify that your syslog properties were migrated into the Ops Manager syslog
-configuration, do one of the following:
+configuration, you can:
 
     * View the configurations in the **Syslog** pane in Ops Manager **Settings** page.
     * View your syslog properties using the `syslog_configuration` Ops Manager API endpoint.

nozzle.html.md.erb

@@ -132,7 +132,7 @@ The events channel receives the following six types of events.
 * _CounterEvent_ represents an incrementing counter, emitted by platform components. For example, a Diego cell's remaining memory capacity.
 * _Error_ represents an error in the originating process.
 * _HttpStartStop_ represents HTTP request details, including both app and platform requests.
-* _LogMessage_ represents a log message for an individual app.
+* _LogMessage_ represents a log entry for an individual app.
 * _ContainerMetric_ represents application container information. For example, memory used.
 
 For the full details on events, see
@@ -296,7 +296,7 @@ The RFC-5424 syslog protocol includes a [structured data element](https://tools.
     <td>Your Enterprise Number, as <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">listed</a> by the Internet Assigned Numbers Authority (IANA) </td>
   </tr><tr>
     <td><code>${DIRECTOR}</code></td>
-    <td>The BOSH director managing the deployment. </td>
+    <td>The BOSH irector managing the deployment. </td>
   </tr><tr>
     <td><code>${DEPLOYMENT}</code></td>
     <td>BOSH <code>spec.deployment</code> value</td>
@@ -319,7 +319,7 @@ various metrics and how to make them useful.
 
 ## <a id="resources"></a> Other Resources
 
-* CF Summit Video [Monitoring Cloud Foundry: Learning about the Firehose](https://youtu.be/skJKvQfpKD4)
+* Cloud Foundry Summit Video [Monitoring Cloud Foundry: Learning about the Firehose](https://youtu.be/skJKvQfpKD4)
 
 * [Loggregator GitHub repository](https://github.com/cloudfoundry/loggregator/)
 

tile-basics.html.md.erb

@@ -17,5 +17,5 @@ Cloud operators make software services available to developers by finding them o
 
 See the following:
 
-* [How <%= vars.app_runtime_abbr %> and <%= vars.platform_name %> Services Work](cf-concepts.html)
+* [How <%= vars.app_runtime_abbr %> and <%= vars.platform_name %> Services work](cf-concepts.html)
 * [How tiles work](tile-structure.html)

tile-index.html.md.erb

@@ -6,7 +6,7 @@ owner: Services
 Here is some references that provide basic information about tiles.
 
 *   [Tile basics](/docs-tiledev/tile-basics.html)
-*   [How <%= vars.app_runtime_abbr %> and <%= vars.ops_manager %> Services Work](/docs-tiledev/cf-concepts.html)
+*   [How <%= vars.app_runtime_abbr %> and <%= vars.ops_manager %> services work](/docs-tiledev/cf-concepts.html)
 *   [How tiles work](/docs-tiledev/tile-structure.html)
 *   [Configuring disk and VM type defaults for on-demand service tiles](/docs-tiledev/odb-resource-defaults.html)
 *   [Managing runtime configs](/docs-tiledev/runtime-config.html)