anchor.diff:  
   .Procedure
   
  -To use the tool on the command line: 
  +To use the cluster capacity tool on the command line:
   
  -. Run the following command:
  +. From the terminal, log in to the Red Hat Registry:
   +
   [source,terminal]
   ----
  -$ ./cluster-capacity --kubeconfig <path-to-kubeconfig> \ <1>
  -    --podspec <path-to-pod-spec> <2>
  +$ podman login registry.redhat.io
   ----
  -<1> Specify the path to your Kubernetes configuration file.
  -<2> Specify the path to the sample `Pod` spec file
  -+
  -You can also add the `--verbose` option to output a detailed description of how
  -many pods can be scheduled on each node in the cluster:
  +
  +. Pull the cluster capacity tool image:
   +
   [source,terminal]
   ----
  -$ ./cluster-capacity --kubeconfig <path-to-kubeconfig> \
  -    --podspec <path-to-pod-spec> --verbose
  +$ podman pull registry.redhat.io/openshift4/ose-cluster-capacity
   ----
  +
  +. Run the cluster capacity tool:
  ++
  +[source,terminal]
  +----
  +$ podman run -v $HOME/.kube:/kube:Z -v $(pwd):/cc:Z  ose-cluster-capacity \
  +/bin/cluster-capacity --kubeconfig /kube/config --podspec /cc/pod-spec.yaml \
  +--verbose <1>
  +----
  +<1> You can also add the `--verbose` option to output a detailed description of how many pods can be scheduled on each node in the cluster.
   +
   .Example output
   [source,terminal]
  
positive.code: 	- CPU: 150m
  	- Memory: 100Mi
  
  The cluster can schedule 52 instance(s) of the pod small-pod.
  
  Termination reason: Unschedulable: No nodes are available that match all of the
  following predicates:: Insufficient cpu (2).
  
  Pod distribution among nodes:
  small-pod
  	- 192.168.124.214: 26 instance(s)
  	- 192.168.124.120: 26 instance(s)
  ----
  +
  In the above example, the number of estimated pods that can be scheduled onto
  the cluster is 52.
  
negative.code: 
  .Prerequisites
  
  * Run the link:https://catalog.redhat.com/software/containers/openshift4/ose-cluster-capacity/5cca0324d70cc57c44ae8eb6?container-tabs=overview[OpenShift Cluster Capacity Tool], which is available as a container image from the Red Hat Ecosystem Catalog.
  
  * Create a sample `Pod` spec file, which the tool uses for estimating resource usage. The `podspec` specifies its resource
  requirements as `limits` or `requests`. The cluster capacity tool takes the
  