README.md in docker-spoon-0.7.0 vs README.md in docker-spoon-0.8.0

@@ -93,10 +93,15 @@
   environment variable `DOCKER_HOST` if this argument is not specified
   and that env var exists.
 - `--image`, The image name to use when starting a spoon container.
 - `--prefix`, The prefix to use for creating, listing & destroying
   containers.
+- `--portforwards`, This is a space separated list of ports to forward
+  over ssh. The format is either `sourceport:destport` or  just `sourceport`
+  in which case the same port will be used for source & destination.
+	Multiple port forwards may be separated by spaces, for exampe
+	`--portforwards '8080 8081:9090'`
 
 ### List
 
 The `--list` argument will list any containers on the destination Docker
 host which have the same prefix as specified by `--prefix` (default
@@ -118,14 +123,20 @@
 
 The `--destroy NAME` option will destroy the specified spoon container.
 
 ```shell
 $ spoon -d fortesting
+Are you sure you want to destroy spoon-fortesting? (y/n) y
 Destroying spoon-fortesting
 Done!
 ```
 
+To skip any confirmations:
+
+  * add `-f` or `--force` to the command-line
+  * add `options[:force] = true` to your `.spoonrc`.
+
 ### Network
 
 The `--network NAME` option will show the forwarded ports for a spoon
 instance. Any ports listed via `EXPOSE` in your Dockerfile should be
 exposed when a spoon container is started. If you are working with
@@ -194,9 +205,22 @@
   upon container creation.
 
 Example:
 ```
 options[:add_authorized_keys] = "id_rsa.pub"
+```
+
+  `run_on_create` - This is a list of commands to run on a spoon container
+  once it has been started. This allows you to quickly and automatically
+  modify a spoon environment upon creation to meet any needs you have
+  which aren't baked into the Docker image. This is a config-only
+	option, there is no command line for this. Commands are run one at a
+	time over ssh - enabling :add_authorized_keys makes this option more
+	tolerable.
+
+Example:
+```
+options[:run_on_create] = [ "sudo apt-get -y install emacs" ]
 ```
 
 #### Container expectations
 
 When building an image for use with docker-spoon you must build an