diff --git a/docs/how-to-use.md b/docs/how-to-use.md
index 5a36e23cf..84d4f550a 100644
--- a/docs/how-to-use.md
+++ b/docs/how-to-use.md
@@ -604,7 +604,7 @@ The `--multus-master-cni-file-name` can be used to select the cni file as the ma
     --multus-log-level=
     --multus-log-file=
 
-Used only with `--multus-conf-file=auto`. See the documentation for logging for which values are permitted.
+Used only with `--multus-conf-file=auto`. See the [documentation for logging](https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/docs/configuration.md#logging) for which values are permitted.
 
 Used only with `--multus-conf-file=auto`. Allows you to specify CNI spec version. Please set if you need to specify CNI spec version.
 
diff --git a/images/README.md b/images/README.md
index b03b2f4e1..fc31762b8 100644
--- a/images/README.md
+++ b/images/README.md
@@ -15,7 +15,7 @@ $ docker build -t dougbtv/multus -f images/Dockerfile .
 You may wish to deploy Multus as a daemonset, you can do so by starting with the example Daemonset shown here:
 
 ```
-$ kubectl create -f ./images/multus-daemonset.yml
+$ kubectl create -f ./deployments/multus-daemonset.yml
 ```
 
 Note: The likely best practice here is to build your own image given the Dockerfile, and then push it to your preferred registry, and change the `image` fields in the Daemonset YAML to reference that image.