Removed RELP references; fixed formatting, capitalization, etcetera [#161488956]

Author: cshollingsworth

managing-cf/logging-config.html.md.erb

@@ -7,27 +7,28 @@ owner: Logging and Metrics
 
 This topic explains how to configure the Cloud Foundry [Loggregator system](../../loggregator/architecture.html).
 
-## <a id='scaling'></a> Scaling Loggregator ##
+
+## <a id='scaling'></a> Scaling Loggregator
 
 Cloud Foundry system components and apps constantly generate log and metrics data. The [Metron](../../loggregator/architecture.html#metron) agent running on each component or application VM collects and sends this data out to [Doppler](../../loggregator/architecture.html#doppler) components, which temporarily buffer the data before periodically forwarding it to the [Traffic Controller](../../loggregator/architecture.html#traffic-controller). The Traffic Controller then serves the aggregated data stream through the Firehose WebSocket endpoint.
 
 When the log and metrics data input to a Doppler exceeds its buffer size for a given interval, data can be lost. You can take several actions to minimize this loss.
 
-
-### Add additional Doppler server instances
+### <a id='add-doppler-server'></a> Add Additional Doppler Server Instances
 
 You can increase the number of Doppler servers by increasing the `instances` property for the `doppler_z1` and `doppler_z2` jobs in your Cloud Foundry BOSH deployment manifest.
 
-## <a id='syslog-forward'></a> Enabling System Log Forwarding ##
+
+## <a id='syslog-forward'></a> Enabling System Log Forwarding
 
 Cloud Foundry can forward syslog data to an external aggregator using the [syslog-release](https://github.com/cloudfoundry/syslog-release).
 
 
-## <a id='customizing'></a>Customizing Loggregator Components ##
+## <a id='customizing'></a> Customizing Loggregator Components
 
 You can customize each Loggregator component by changing its properties in the CF deployment manifest. The following details some of the most commonly used changes.
 
-### Doppler ###
+### <a id='doppler'></a> Doppler
 
 <table>
   <tr>
@@ -182,7 +183,7 @@ You can customize each Loggregator component by changing its properties in the C
   </tr>
 </table>
 
-### Traffic Controller ###
+### <a id='traffic-controller'></a> Traffic Controller
 
 <table>
   <tr>
@@ -286,7 +287,7 @@ You can customize each Loggregator component by changing its properties in the C
   </tr>
 </table>
 
-###  Metron Agent ###
+### <a id='metron-agent'></a> Metron Agent
 
 <table>
   <tr>
@@ -311,12 +312,12 @@ You can customize each Loggregator component by changing its properties in the C
   </tr>
   <tr>
     <td>syslog_daemon_config.transport</td>
-    <td>Transport to use when forwarding logs. Accepts the following values: <code>tcp</code>, <code>udp</code>, or <code>relp</code></td>
+    <td>Transport to use when forwarding logs. Accepts the following values: <code>tcp</code> or <code>udp</code></td>
     <td><code>tcp</code></td>
   </tr>
   <tr>
     <td>syslog_daemon_config.fallback_addresses</td>
-    <td>IP addresses of fallback servers to use if primary syslog server is unavailable. Only </code>tcp</code> and <code>relp</code> supported. Each list entry must consist of address, transport, and port keys.</td>
+    <td>IP addresses of fallback servers to use if primary syslog server is unavailable. Only </code>tcp</code> supported. Each list entry must consist of address, transport, and port keys.</td>
     <td><code>[]</code></td>
   </tr>
   <tr>
@@ -441,7 +442,7 @@ You can customize each Loggregator component by changing its properties in the C
   </tr>
 </table>
 
-### Syslog Drain Binder###
+### <a id='syslog-drain-binder'></a> Syslog Drain Binder
 
 See [Using Log Management Services](../../devguide/services/log-management.html).
 

managing-cf/logging.html.md.erb

@@ -7,7 +7,8 @@ owner: Logging and Metrics
 
 This section contains information for debugging Cloud Foundry system components.
 
-##Component Logging
+
+## <a id='component-logging'></a> Component Logging
 
 The Cloud Foundry components share a common interface for configuring logs. For more information, see the [Cloud
 Controller](http://github.com/cloudfoundry/cloud_controller_ng#logs), or for
@@ -19,18 +20,19 @@ In `cf-release`, the components are all configured in a similar way:
 * The job's main logs are written to a file named `<job-name>.log`.
 * Any output written directly to the job's stdout and stderr is written to `<job-name>.stdout.log` and `<job-name>.stderr.log`, respectively.
 
-### Database Migrations
+### <a id='db-migration'></a> Database Migrations
 
 For the Cloud Controller, database migration logs are written to `db_migrate.stdout.log` and `db_migrate.stderr.log`
 in the same directory.
 
-## Log Forwarding
+
+## <a id='log-forwarding'></a> Log Forwarding
 
 Each BOSH job in `cf-release` includes a job named `metron_agent`. Metron itself acts as a forwarding agent for Doppler within the Loggregator metric system, but it also includes a [template](https://github.com/cloudfoundry/loggregator/blob/develop/jobs/metron_agent/templates/syslog_forwarder.conf.erb) for configuring the `rsyslogd` daemon to forward logs to a remote machine. The [`syslog_daemon_config`](https://github.com/cloudfoundry/loggregator/blob/develop/jobs/metron_agent/spec) properties include:
 
 * `syslog_daemon_config.address`: the IP address (or DNS name) of a remote system that should receive component logs from this VM
 * `syslog_daemon_config.port`: the port on which the log recipient is listening
-* `syslog_daemon_config.transport`: the protocol over which logs should be sent (one of `tcp`, `udp` or `relp`); defaults to `tcp`
+* `syslog_daemon_config.transport`: the protocol over which logs should be sent (one of `tcp` or `udp`); defaults to `tcp`
 
 For example, to use UDP as the syslog transport, the manifest is similar to the following:
 ```yaml