anchor.diff:  
   <p class="note"><strong>Note</strong>: This feature is currently experimental.</p>
   
  -Developers can map a route to their app that is only available internally to the platform. Once a route is mapped, that route will be available to all other apps on the platform.
  -
  -To create a `foo.apps.internal` internal route for `myapp`:
  +You can map an internal route to any app. This internal route allows your app to communicate with other apps without leaving the platform. Once mapped, this route becomes available to all other apps on the platform.
  +
  +This example creates a `foo.apps.internal` internal route for `myapp`:
   
   <pre class="terminal">
   $ cf map-route myapp apps.internal --hostname foo
  
positive.code: 
  <p class="note"><strong>Note</strong>: This feature is currently experimental.</p>
  
  Applications can communicate without leaving the platform on the container network using internal routes. An internal route can be created using the [map-route](#map-internal-route) command with an [internal domain](#internal-domains).
  
  By default, apps cannot communicate with each other on the container network. In order for an app to talk to another app a [network policy](https://cli.cloudfoundry.org/en-US/cf/add-network-policy.html) must be created.
  
  ### <a id='create-route'></a>Create a Route ###
  
  
negative.code: $ cf delete-shared-domain example.com
  </pre>
  
  #### <a id='internal-domains'></a>Internal Domain ####
  
  <p class="note"><strong>Note</strong>: This feature is currently experimental.</p>
  
  The internal domain is a special type of shared domain used for app communication internal to the platform. When you enable service discovery, the internal domain `apps.internal` becomes provided for your use.
  
  <p class="note"><strong>Note</strong>: The internal domain <em>apps.internal</em> cannot be deleted. At this time, no other internal domains can be created.</p>
  
  ### <a id='private-domains'></a>Private Domains ###
  
  