anchor.diff:      name: docker-registry
   status: {}
   ----
  -. Verify that the route has been created successfully: 
  +. Verify that the route has been created successfully:
   +
   ----
   # oc get route
   NAME              HOST/PORT                    PATH      SERVICE           LABELS                    INSECURE POLICY   TLS TERMINATION
   docker-registry   registry.example.com            docker-registry   docker-registry=default
   ----
  -. Check the health of the registry in your web browser: \http://registry.example.com/healthz 
  -
  +. Check the health of the registry:
  ++
  +----
  +$ curl -v http://registry.example.com/healthz
  +----
  ++
  +Expect an HTTP 200/OK message.
  ++
   After exposing the registry, update your *_/etc/sysconfig/docker_* file by
   adding the port number to the `OPTIONS` entry. For example:
  -
  -----
  -OPTIONS='--selinux-enabled --insecure-registry=172.30.0.0/16 --insecure-registry registry.ose-node.openshift.com:443'
  -----
  -
  -When 
  ++
  +----
  +OPTIONS='--selinux-enabled --insecure-registry=172.30.0.0/16 --insecure-registry registry.example.com:80'
  +----
  ++
  +[IMPORTANT]
  +====
  +The above options should be added on the client from which you are trying to log in.
  +
  +Also, ensure that Docker is running on the client.
  +====
  +
  +When
   xref:access-logging-in-to-the-registry[logging in] to the non-secured and
   exposed registry, make sure you specify the registry in the login command. For
   example:
   
   ----
  -docker login -e user@company.com -u f83j5h6 -p Ju1PeM47R0B92Lk3AZp-bWJSck2F7aGCiZ66aFGZrs2 registry.ose-node.openshift.com:443
  -----+docker login -e user@company.com -u f83j5h6 -p Ju1PeM47R0B92Lk3AZp-bWJSck2F7aGCiZ66aFGZrs2 registry.example.com:80
  +----
  
positive.code: . Expose the registry:
  +
  ----
  # oc expose service docker-registry --hostname=<hostname> -n default 
  ----
  +
  This creates the following JSON file:
  
negative.code: xref:securing-the-registry[securing the registry] and then
  xref:exposing-the-registry[exposing the registry].
  This allows you to log in to the registry from outside the cluster using the
  route address, and to tag and push images using the route host.
  
  When
  xref:access-logging-in-to-the-registry[logging in] to the secured and exposed
  registry, make sure you specify the registry in the login command. For example:
  
  ----
  docker login -e user@company.com -u f83j5h6 -p Ju1PeM47R0B92Lk3AZp-bWJSck2F7aGCiZ66aFGZrs2 registry.example.com:80
  ----
  
  [[access-insecure-registry-by-exposing-route]]
  