diff --git a/docs/design/security.md b/docs/design/security.md
index 6ea611b7957..1f43772e058 100644
--- a/docs/design/security.md
+++ b/docs/design/security.md
@@ -54,7 +54,7 @@ Automated process users fall into the following categories:
   * are less focused on application security. Focused on operating system security.
   * protect the node from bad actors in containers, and properly-configured innocent containers from bad actors in other containers.
   * comfortable reasoning about the security properties of a system at the level of detail of Linux Capabilities, SELinux, AppArmor, etc.
-  * decides who can use which Linux Capabilities, run privileged containers, use hostDir, etc.
+  * decides who can use which Linux Capabilities, run privileged containers, use hostPath, etc.
     * e.g. a team that manages Ceph or a mysql server might be trusted to have raw access to storage devices in some organizations, but teams that develop the applications at higher layers would not.
 
 
diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md
index 2f23f76b710..7adf5f038e2 100644
--- a/docs/getting-started-guides/scratch.md
+++ b/docs/getting-started-guides/scratch.md
@@ -484,7 +484,7 @@ To run the apiserver:
 
 Here are some apiserver flags you may need to set:
   - `--cloud-provider=`
-  - `--cloud-config=` if cloud provider requires a config file (GCE, AWS). If so, need to put config file into apiserver image or mount through hostDir.
+  - `--cloud-config=` if cloud provider requires a config file (GCE, AWS). If so, need to put config file into apiserver image or mount through hostPath.
   - `--address=${MASTER_IP}`.  
    - or `--bind-address=127.0.0.1` and `--address=127.0.0.1` if you want to run a proxy on the master node.
   - `--cluster-name=$CLUSTER_NAME`
diff --git a/examples/walkthrough/README.md b/examples/walkthrough/README.md
index 59a1ab0950b..c315c72e4ca 100644
--- a/examples/walkthrough/README.md
+++ b/examples/walkthrough/README.md
@@ -64,7 +64,7 @@ And we added a reference to that volume to our container:
 
 In Kubernetes, ```emptyDir``` Volumes live for the lifespan of the Pod, which is longer than the lifespan of any one container, so if the container fails and is restarted, our persistent storage will live on.
 
-If you want to mount a directory that already exists in the file system (e.g. ```/var/logs```) you can use the ```hostDir``` directive.
+If you want to mount a directory that already exists in the file system (e.g. ```/var/logs```) you can use the ```hostPath``` directive.
 
 See [volumes](../../docs/volumes.md) for more details.