[#185473625]

Author: VMWare-JasonAndrew

dev-workflow.html.md.erb

@@ -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)<!--฿ 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.
+* [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.

managed.html.md.erb

@@ -24,7 +24,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 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
+worry too much about high availability of this instance. This integration level is mostly about getting the BOSH packaging, deployment, and monitoring working
 correctly.
 
 ### <a id="managed-ha"></a> High availability

migrating-syslog-configuration.html.md.erb

@@ -46,7 +46,7 @@ By enabling the Ops Manager syslog feature, Ops Manager:
     <td><code>transport_protocol</code></td>
     <td>string</td>
     <td>No</td>
-    <td>The transport protocol used to send syslog messages to the server.
+    <td>The transport protocol used to send syslog entriess to the server.
       <br>Valid values are <code>tcp</code> and <code>udp</code>. Defaults to <code>tcp</code></td>
   </tr>
   <tr>

nozzle.html.md.erb

@@ -135,25 +135,25 @@ The events channel receives the following six types of events.
 * _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
+For the full details about events, see
 [dropsonde protocol](https://github.com/cloudfoundry/dropsonde-protocol/tree/master/events)
 in GitHub.
 
-The above events show how this data targets two different personae:
+These events show how this data targets two different personae:
 platform operators and app developers. Keep this in mind when designing an integration.
 
-The `doppler.firehose` scope gets nozzle data for *every* app and the platform.
+The `doppler.firehose` scope recieves nozzle data for *every* app and the platform.
 Any filtering based on the event payload is the nozzle implementor's responsibility.
 An advanced integration can combine a
 [service broker](service-brokers.html) with a nozzle to:
 
 * App developers can opt in to logging (implementing filtering in the nozzle)
-* Establish [SSO](https://docs.cloudfoundry.org/services/dashboard-sso.html) exchange for authentication so that developers only can access logs for their space's apps
+* Establish [Cloud Foundry documentation](https://docs.cloudfoundry.org/services/dashboard-sso.html) exchange for authentication so that developers only can access logs for their space's apps
 
 For a full working example (suitable as an integration starting point),
 see [firehose-nozzle](https://github.com/cf-platform-eng/firehose-nozzle).
 
-### <a id="deploy"></a> Deploy a Nozzle
+### <a id="deploy"></a> Deploy a nozzle
 
 After you have built a nozzle, you can deploy it as a managed service or as an app.
 
@@ -164,7 +164,7 @@ You can also deploy the nozzle as an app on <%= vars.app_runtime_abbr %>. Visit
 [section on pushed apps](tile-generator.html#pushed-applications)
 for more details.
 
-### <a id="examples"></a> Example Nozzles
+### <a id="examples"></a> Example nozzles
 
 There are several open source examples you can use
 as a reference for building your nozzle.
@@ -196,19 +196,19 @@ another real world implementation.
 
 ## <a id="syslog-format-pcf"></a> Log Format for <%= vars.app_runtime_abbr %> Components
 
-The standard log format for <%= vars.app_runtime_abbr %> adheres to the [RFC-5424 syslog protocol](https://tools.ietf.org/html/rfc5424), with log messages formatted as follows:
+The standard log format for <%= vars.app_runtime_abbr %> adheres to the [RFC-5424 syslog protocol](https://tools.ietf.org/html/rfc5424), with log entriess formatted as follows:
 
 `<${PRI}>${VERSION} ${TIMESTAMP} ${HOST_IP} ${APP_NAME} ${PROD_ID} ${MSG_ID} ${SD-ELEMENT-instance} ${MESSAGE}`
 
-The [Syslog Message Elements table](#syslog-elements) immediately below describes each element of the log, and the [Structured Instance Data Format](#sd-element) table describes the contents of the structured data element that carries Cloud Foundry VM instance information.
+The [Syslog entries Elements table](#syslog-elements) describes each element of the log, and the [Structured Instance Data Format](#sd-element) table describes the contents of the structured data element that carries Cloud Foundry VM instance information.
 
-### <a id="syslog-elements"></a> Syslog Message Elements
+### <a id="syslog-elements"></a> Syslog entries Elements
 
-This table describes each element of a standard <%= vars.app_runtime_abbr %> syslog message.
+This table describes each element of a standard <%= vars.app_runtime_abbr %> syslog entries.
 
 <table id='syslog-elements-table' border="1" class="nice" >
   <tr>
-    <th>Syslog Message Element</th>
+    <th>Syslog entries Element</th>
     <th>Meaning or Value</th>
   </tr><tr>
     <td><code>${PRI}</code></td>
@@ -221,7 +221,7 @@ This table describes each element of a standard <%= vars.app_runtime_abbr %> sys
     <td><a href="https://tools.ietf.org/html/rfc5424#section-9.1"><code>1</code></a></td>
   </tr><tr>
     <td><code>${TIMESTAMP}</code></td>
-    <td><p>The <a href="https://tools.ietf.org/html/rfc5424#section-9.1">timestamp</a> of when the log message is forwarded; typically slightly after it was generated. Example: <code>2017-07-24T05:14:15.000003Z</code></p></td>
+    <td><p>The <a href="https://tools.ietf.org/html/rfc5424#section-9.1">timestamp</a> of when the log entry is forwarded (typically slightly after it was generated). Example: <code>2017-07-24T05:14:15.000003Z</code></p></td>
   </tr><tr>
     <td><code>${HOST_IP}</code></td>
     <td><a href="https://tools.ietf.org/html/rfc5424#section-6.2.4">Internal IP address</a> of origin server</td>
@@ -238,19 +238,19 @@ This table describes each element of a standard <%= vars.app_runtime_abbr %> sys
     <td>The <a href="https://tools.ietf.org/html/rfc5424#section-6.2.6">Process ID</a> of the syslog process doing the forwarding. If this is not easily available, default to <code>-</code> (hyphen) to indicate unknown.</td>
   </tr><tr>
     <td><code>${MSG_ID}</code></td>
-    <td>The <a href="https://tools.ietf.org/html/rfc5424#section-6.2.7">type</a> of log message. If this is not easily available, default to <code>-</code> (hyphen) to indicate unknown.</td>
+    <td>The <a href="https://tools.ietf.org/html/rfc5424#section-6.2.7">type</a> of log entries. If this is not easily available, default to <code>-</code> (hyphen) to indicate unknown.</td>
   </tr><tr>
     <td><code>${SD-ELEMENT-instance}</code></td>
-    <td>Structured data (SD) relevant to <%= vars.app_runtime_abbr %> about the <a href="https://tools.ietf.org/html/rfc5424#section-6.3.1">source instance (VM)</a> that originates the log message. See the <a href="#sd-element">Structured Instance Data Format table</a> below for content and format.</td>
+    <td>Structured data (SD) relevant to <%= vars.app_runtime_abbr %> about the <a href="https://tools.ietf.org/html/rfc5424#section-6.3.1">source instance (VM)</a> that originates the log entries. See the <a href="#sd-element">Structured Instance Data Format table</a> below for content and format.</td>
   </tr><tr>
     <td><code>${MESSAGE}</code></td>
-    <td>The log message itself, ideally in JSON</td>
+    <td>The log entries itself, ideally in JSON</td>
   </tr>
 </table>
 
 ### <a id="severity"></a> RFC-5424 Severity Codes
 
-<%= vars.app_runtime_abbr %> components generate log messages with the following severity levels. The most common severity level is `13`.
+<%= vars.app_runtime_abbr %> components generate log entries with the following severity levels. The most common severity level is `13`.
 
 <table id='severity-table' border="1" class="nice" >
   <tr>

property-template-references.html.md.erb

@@ -165,10 +165,10 @@ The table that follows describes the accessors you can use to retrieve informati
 | Accessor | Description |
 | -------- | ----------- |
 | `ca_certificate` | Provides the root CA certificate that signs the Director VM |
-| `trusted_certificates` | Provides a list of certificates that the Director applies to all VMs. |
+| `trusted_certificates` | Provides a list of certificates that the Director applies to all VMs |
 | `http_proxy` | Provides the comma-separated values (CSV) that are entered when Ops Manager traffic is directed to an HTTP Proxy |
 | `https_proxy` | Provides the CSVs that are entered when Ops Manager traffic is directed to an HTTPS Proxy |
-| `no_proxy` | Provides the CSVs that should not go through a proxy |
+| `no_proxy` | Provides the CSVs that must not go through a proxy |
 | `instance_types_catalog` | Provides a list of all available VM types. Includes custom VM types |
 | `restricted_view_api_access_credentials` | Provides a payload for a UAA client to make read-only non-credential requests against Ops Manager. The payload includes `uaa_client_name`, `uaa_client_secret`, `hostname`, and `port`. |
 | `iaas_type` | Provides the type of the infrastructure: `google`, `aws`, `azure`, `vsphere`, or `openstack` |
@@ -185,7 +185,7 @@ The table that describes the accessors you can use to retrieve information about
 | `password` | Provides the password for the BOSH Director VM |
 | `ntp_servers` | Provides a list of Network Time Protocol (NTP) servers that the BOSH Director deploys |
 | `ca_public_key` | Provides the public key that is used to sign the BOSH Director VM |
-| `hostname` | Provides the hostname for the BOSH Director VM |
+| `hostname` | Provides the host name for the BOSH Director VM |
 | `tld` | Returns the string `bosh` as the top-level domain (TLD) of the BOSH Director |
 | `metrics_server_enabled` | Returns `true` if the `system-metrics-server` job is included in the manifest.<br>For information about the job, see <a href="https://bosh.io/jobs/system-metrics-server?source=github.com/cloudfoundry/bosh-system-metrics-server-release">system-metrics-server job</a> in the BOSH documentation. |
 | `bosh_metrics_forwarder_client_name` | Provides the BOSH Metrics Forwarder client name |