Comment NNI port speed runtime config
Change-Id: I7730886677bb5d874b22ef9f42934a1d66d83fa2
diff --git a/VERSION b/VERSION
index 26aaba0..6085e94 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-1.2.0
+1.2.1
diff --git a/docs/ManagingDevice.md b/docs/ManagingDevice.md
index f80ee5b..b5a1c01 100644
--- a/docs/ManagingDevice.md
+++ b/docs/ManagingDevice.md
@@ -73,4 +73,14 @@
```
This RPC is used to administratively reboot the device. The server side implementations should reboot the device only after successfully returning this RPC.
+## Port Speed configuration
+The Device Management Interface does not support runtime NNI (network to network interface) port speed configuration on the OLT device.
+The speed of the NNI ports is configured, for each port, at startup time through the startup configuration file that can be provided via the
+`UpdateStartupConfiguration` API. If a change to the NNI port speed is needed a new startup configuration will be sent
+to the DM implementation for that OLT via the `UpdateStartupConfiguration` API.
+The new configuration will then be applied by the DM to the OLT. This may include a reboot of the OLT.
+
+Operators currently do not require runtime configuration of the NNI because it's not an element that is expected to change
+at all once initial deployment is performed.
+
diff --git a/docs/RpcGuidelines.md b/docs/RpcGuidelines.md
index 7cd781e..1ff819c 100644
--- a/docs/RpcGuidelines.md
+++ b/docs/RpcGuidelines.md
@@ -22,7 +22,7 @@
need to be taken into account, such as how to generate events and handle different states of operations.
Please refer to each of those files.
-## Errors returned in the response messages
+## Errors returned in response messages
Each of the response messages of the RPCs have a field called `status` which says if there is an application level error in execution of the RPC or not.