anchor.diff:        name: hab-bastion
       spec:
         accessModes: [ "ReadWriteOnce" ]
  -      # uncomment if you don't have a default storageclass
  +      # uncomment if you don't have a default StorageClass
         # storageClassName: "standard"
         resources:
           requests:
             storage: 10Gi
   ```
   
  -All of the Habitat supervisor's state data is stored under `/hab/sup` - we mount this on a persistent volume so it gets re-attached if the pod is ever relaunched. The data persists!
  +All of the Habitat Supervisor's state data is stored under `/hab/sup` - we mount this on a persistent volume so it gets re-attached if the pod is ever rescheduled. The data persists!
   
   ### Create a Kubernetes Deployment that works with the Bastion
   
  
positive.code: 
  ## Bare Kubernetes
  
  If your packages don't require communication with the Chef Habitat supervisor ring, such as binds, secrets, etc., then you can execute your packages directly on the cluster. You can deploy Chef Habitat packages exported as containers to Kubernetes with the [`kubectl` command](http://kubernetes.io/docs/user-guide/pods/single-container/). Using the [Docker exporter](/docs/developing-packages#pkg-exports) to create a containerized application, you can launch the container like this example:
  
  ```shell
  $ kubectl run mytutorial --image=myorigin/mytutorial --port=8080
  
negative.code:         - '--permanent-peer'
  ```
  
  The `image:` line defines the source of the docker container. In this case, the instructions create an image from a Chef Habitat plan using the `hab pkg export docker` command. It only runs the Chef Habitat Supervisor (hab-sup) service.
  The argument `--permanent-peer` instructs the Supervisor to act as a permanent peer.
  
  ```yaml
          resources:
  