anchor.diff:          fsGroup: 42
   ```
   
  -This section sets the group ownership for the persistent volume mount point so the Habitat supervisor can write to it.  The Habitat user (`hab`) by default has the uid `42` and the gid `42`.
  +This section sets the group ownership for the persistent volume mount point so the Habitat Supervisor can write to it.  The Habitat user (`hab`) by default has the uid `42` and the gid `42`.
   
   ```yaml
         containers:
  
positive.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:
  
negative.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
  