anchor.diff:  <2> Specify each image by a digest (SHA), not by an image tag.
   <3> Also reference the Operator container image by a digest (SHA), not by an image tag.
   
  -* Look for the `Disconnected` annotation, which indicates that the Operator works
  -in a disconnected environment:
  +. Add the `Disconnected` annotation, which indicates that the Operator works in a
  +disconnected environment:
   +
   [source,yaml]
   ----
  
positive.code: <2> Specify a unique identifier for the image.
  <3> Specify each image by a digest (SHA), not by an image tag.
  
  * in the `env` section of the Operators Deployments when declaring environment
  variables that inject the image that the Operator should use:
  +
  [source,yaml]
  
negative.code: [id="olm-enabling-operator-for-restricted-network_{context}"]
  = Enabling your Operator for restricted network environments
  
  As an Operator author, your Operator must meet  additional requirements to run
  properly in a restricted network, or disconnected, environment.
  
  .Operator requirements for supporting disconnected mode
  
  * In the ClusterServiceVersion (CSV) of your Operator:
  ** List any _related images_, or other container images that your Operator might
  require to perform their functions.
  ** Reference all specified images by a digest (SHA) and not by a tag.
  * All dependencies of your Operator must also support running in a disconnected
  mode.
  * Your Operator must not require any off-cluster resources.
  // TODO: Include more info w/ better steps on how to do this:
  //* You must understand the {product-title} proxy configuration.
  
  For the CSV requirements, you can make the following changes as the Operator
  author.
  
  .Prerequisites
  
  * An Operator project with a CSV.
  
  .Procedure
  
  . Use SHA references to related images in two places in the CSV for your Operator:
  
  .. Update `spec.relatedImages`:
  +
  [source,yaml]
  ----
  