anchor.diff:  (NAT boxes are systems responsible for Network Address Translation, not to be confused with the NATS messaging protocol.)
   
   You also need to obtain the special URL, called a syslog URL, that the service makes available as an endpoint for incoming log data.
  -The URL is special because its protocol is `syslog`.
  -It also includes a port number.
  +This URL has a protocol of `syslog` and includes a port number.
   For example:
   
    `syslog://logs.example.com:1234`
  
positive.code: 	</tbody>
  </table>
  
  ## <a id='format'></a> About Log File Formats and Third-Party Log Management Software  ##
  
  Loggregator formats logging data that it sends to third-party services according to [RFC 5424](http://tools.ietf.org/html/rfc5424), titled *The Syslog Protocol*.
  Logs viewed in the CLI are not in syslog format.
  
negative.code: In this case, you create a user-provided service instance using the `cups` command with the `-l` option and the syslog URL you obtained earlier.
  See [User-Provided Services] (./user-provided.html#user-cups).
  
  Now that the service instance and the syslog drain exist, you are ready to bind the service instance to the app.
  
  ### <a id='bind'></a>Bind the service instance to the application ###
  
  Use the `cf bind-service` command as described in [Binding User-Provided Service Instances to Applications](user-provided.html#cups-example).
  
  ## <a id='verify'></a>Verifying that Logs are Draining to a Service ##
  
  _Let's provide a few clues about what to do once we've completed the procedure above._
  
  ## <a id='types'></a> Types of Logs ##
  
  