diff --git a/docs/controlkube_scenario.md b/docs/controlkube_scenario.md
index c7108c4..7f5d206 100644
--- a/docs/controlkube_scenario.md
+++ b/docs/controlkube_scenario.md
@@ -23,7 +23,7 @@
 You should run the following commands on a clean Linux machine in the
 home directory to install this scenario:
 
-```
+```shell
 # Pull down cord-bootstrap.sh script and start a tmux session
 curl -o ~/cord-bootstrap.sh \
 https://raw.githubusercontent.com/opencord/cord/{{ book.branch }}/scripts/cord-bootstrap.sh
@@ -31,7 +31,7 @@
 tmux
 ```
 
-```
+```shell
 # Install CORD with kubernetes and XOS Helm chart (this is a single command wordwrapped)
 time bash ./cord-bootstrap.sh -v -x -t "PODCONFIG=rcord-controlkube.yml config" \
 -t "build" |& tee -a ~/setup.log
diff --git a/docs/getting_the_code.md b/docs/getting_the_code.md
index e391f40..8f26861 100644
--- a/docs/getting_the_code.md
+++ b/docs/getting_the_code.md
@@ -68,3 +68,18 @@
 project, see [Contributing to
 CORD](https://wiki.opencord.org/display/CORD/Contributing+to+CORD).
 
+## Downloading testing and QA repositories
+
+Whie not useful for deploying a CORD POD, the repo manifests files and the
+infrastructure code used to configure our test and QA systems, including
+Jenkins jobs created with [Jenkins Job
+Builder](https://docs.openstack.org/infra/jenkins-job-builder/) can be
+downloaded with repo:
+
+```shell
+mkdir cordqa
+cd cordqa
+repo init -u https://gerrit.opencord.org/qa-manifest -b master
+repo sync
+```
+
diff --git a/docs/release-notes/satisfying-cactus.md b/docs/release-notes/satisfying-cactus.md
index f5cb0e3..de0102b 100644
--- a/docs/release-notes/satisfying-cactus.md
+++ b/docs/release-notes/satisfying-cactus.md
@@ -8,33 +8,32 @@
 ## Platform and Build System
 
 * Added support for dynamically loading new services and service profiles into
-a running system. R-CORD and E-CORD services converted to use new
-dynamic loading mechanism, but M-CORD still uses `corebuilder`.
+  a running system. R-CORD and E-CORD services converted to use new dynamic
+  loading mechanism, but M-CORD still uses `corebuilder`.
 
-* Refactored build to isolate profile-specific information (e.g., models,
-TOSCA templates). R-CORD, M-CORD, and E-CORD converted to use
-refactoring.
+* Refactored build to isolate profile-specific information (e.g., models, TOSCA
+  templates). R-CORD, M-CORD, and E-CORD converted to use refactoring.
 
-* Added support for logging and diagnostics. See the
-[Logging and Diagnostics](../operate/elk_stack.md) section of the
-guide for more information.
+* Added support for logging and diagnostics. See the [Logging and
+  Diagnostics](../operate/elk_stack.md) section of the guide for more
+  information.
 
 * Added new scenarios to build:
 
-  * `preppedpod`: Installs a CORD POD without MaaS on pre-prepared systems,
-  which can run the R-CORD test suite.
+    * `preppedpod`: Installs a CORD POD without MaaS on pre-prepared systems,
+      which can run the R-CORD test suite.
 
-  * `controlpod`: Installs XOS and ONOS without VNF support. Runs on Ubuntu
-16.04 in preparation for updating the entire CORD platform.
+    * `controlpod`: Installs XOS and ONOS without VNF support. Runs on Ubuntu
+      16.04 in preparation for updating the entire CORD platform.
 
-  * `controlkube`: Preliminary support for running XOS on Kubernetes, in preparation
-  for greater functionality in the next release.
+    * `controlkube`: Preliminary support for running XOS on Kubernetes, in
+      preparation for greater functionality in the next release.
 
 * Preliminary integration of Kubernetes into CORD (pre-alpha):
 
-  * Manages XOS containers
+    * Manages XOS containers
 
-  * Works with `controlkube` Scenario
+    * Works with `controlkube` Scenario
 
 * Removed old TOSCA Engine.
 
@@ -57,3 +56,4 @@
 ## E-CORD
 
 * Automated Monitoring at EVC creation
+
diff --git a/docs/scripts/descriptions.md b/docs/scripts/descriptions.md
index 3401793..193b813 100644
--- a/docs/scripts/descriptions.md
+++ b/docs/scripts/descriptions.md
@@ -663,6 +663,7 @@
 
 ## vtn_net_management_host_interface
 
+Interface name for the MANAGEMENT_HOST VTN network.
 
 ## vtn_net_management_host_range_xos_high