diff --git a/Documentation/common-issues.md b/Documentation/common-issues.md
index 63525e1ef..6e524f8e1 100644
--- a/Documentation/common-issues.md
+++ b/Documentation/common-issues.md
@@ -47,7 +47,7 @@ Kubernetes status is the first line of investigating when something goes wrong w
 After you verify the basic health of the running pods, next you will want to run Ceph tools for status of the storage components. There are two ways to run the Ceph tools, either in the Rook toolbox or inside other Rook pods that are already running.
 
 ### Tools in the Rook Toolbox
- The [rook-ceph-tools pod](./toolbox.md) is a one-stop shop for both Ceph tools and other troubleshooting tools. Once the pod is up and running one connect to the pod to execute Ceph commands to evaluate that current state of the cluster.
+ The [rook-ceph-tools pod](./toolbox.md) provides a simple environment to run Ceph tools. Once the pod is up and running, connect to the pod to execute Ceph commands to evaluate that current state of the cluster.
  ```bash
  kubectl -n rook-ceph exec -it $(kubectl -n rook-ceph get pod -l "app=rook-ceph-tools" -o jsonpath='{.items[0].metadata.name}') bash
  ```
diff --git a/Documentation/object.md b/Documentation/object.md
index 6240226a7..cebb38ca2 100644
--- a/Documentation/object.md
+++ b/Documentation/object.md
@@ -70,7 +70,14 @@ The object store is now available by using the creds of `rook-user`. Take note o
 
 Use an S3 compatible client to create a bucket in the object store.
 
-This section will allow you to test connecting to the object store and uploading and downloading from it. The `s3cmd` tool is included in the [Rook toolbox](toolbox.md) pod to simplify your testing. Run the following commands after you have connected to the toolbox.
+This section will allow you to test connecting to the object store and uploading and downloading from it. Run the following commands after you have connected to the [Rook toolbox](toolbox.md).
+
+### Install s3cmd
+
+To test the object store we will install the `s3cmd` tool into the toobox pod.
+```bash
+yum --assumeyes install s3cmd
+```
 
 ### Connection Environment Variables
 
diff --git a/Documentation/toolbox.md b/Documentation/toolbox.md
index 5c8adc4a7..020e7d242 100644
--- a/Documentation/toolbox.md
+++ b/Documentation/toolbox.md
@@ -100,7 +100,7 @@ ceph df
 rados df
 ```
 
-When you are done with the toolbox, remove the pod:
+When you are done with the toolbox, you can remove the deployment:
 ```bash
 kubectl -n rook-ceph delete deployment rook-ceph-tools
 ```
diff --git a/PendingReleaseNotes.md b/PendingReleaseNotes.md
index 063df2d3d..648602830 100644
--- a/PendingReleaseNotes.md
+++ b/PendingReleaseNotes.md
@@ -12,6 +12,7 @@
 - The minimum version of Kubernetes supported by Rook changed from `1.7` to `1.8`.
 - `reclaimPolicy` parameter of `StorageClass` definition is now supported.
 - K8s client-go updated from version 1.8.2 to 1.11.3
+- The toolbox manifest now creates a deployment based on the `rook/ceph` image instead of creating a pod on a specialized `rook/ceph-toolbox` image.
 
 ## Breaking Changes
 - Ceph mons are [named consistently](https://github.com/rook/rook/issues/1751) with other daemons with the letters a, b, c, etc.