diff --git a/source/server/index.md b/source/server/index.md
index 027773f..34038cb 100644
--- a/source/server/index.md
+++ b/source/server/index.md
@@ -132,6 +132,19 @@ ENTRYPOINT [ "/sbin/init" ]
 CMD [ "start" ]
 ```
 
+### Set your container timezone (optional)
+
+If you want your running container to be in your timezone, then add this to your Dockerfile
+
+```Dockerfile
+# Set out local time
+RUN ln -sf /usr/share/zoneinfo/Australia/Melbourne /etc/localtime
+
+```
+<small>**NOTE**: This will set your timezone to Melbourne, Australia - naturally, choose the appropriate Country/City for your timezone.
+
+## Build your Image 
+
 A complete Dockerfile is available [here](http://dev.leenooks.net/deon/spdocker/blob/master/Dockerfile) if you need one as a starting point. Once you have your images loaded on a web server, and the supporting build files run `docker build -t ibm/spectrumprotect:8.1.x .`
 
 If your final build is successful, you should see a Docker Image that is about 3GB.
diff --git a/source/server/upgrade.md b/source/server/upgrade.md
index 77d49a1..70a925b 100644
--- a/source/server/upgrade.md
+++ b/source/server/upgrade.md
@@ -84,7 +84,7 @@ ANS8002I Highest return code was 0.
  While you can control the timeout between the SIGTERM and SIGKILL signal and you can even control which kill signal is sent, I haven't explored what signals SP will act on. So as a recommendation, always use SP `halt` command to stop an SP server.</small>
 
 ## If you can, snapshot your persistent storage.
-If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restoredb" if something goes pair shaped.
+If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restore db" if something goes pair shaped.
 
 ```bash Using LVM Snapshot
 [root@host]# df /srv/sp