summaryrefslogtreecommitdiff
path: root/Documentation/faq
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/faq')
-rw-r--r--Documentation/faq/openflow.rst2
-rw-r--r--Documentation/faq/qos.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/faq/openflow.rst b/Documentation/faq/openflow.rst
index 8c9489170..0111de78a 100644
--- a/Documentation/faq/openflow.rst
+++ b/Documentation/faq/openflow.rst
@@ -385,7 +385,7 @@ but OVS drops the packets instead.
$ ovs-ofctl add-flow br0 actions=load:0->NXM_OF_IN_PORT[],2,3,4,5,6
If the input port is important, then one may save and restore it on the
- stack:
+ stack::
$ ovs-ofctl add-flow br0 actions=push:NXM_OF_IN_PORT[],\
load:0->NXM_OF_IN_PORT[],\
diff --git a/Documentation/faq/qos.rst b/Documentation/faq/qos.rst
index 53ad89809..33c319166 100644
--- a/Documentation/faq/qos.rst
+++ b/Documentation/faq/qos.rst
@@ -102,7 +102,7 @@ Q: How do I configure ingress policing?
A: A policing policy can be configured on an interface to drop packets that
arrive at a higher rate than the configured value. For example, the
following commands will rate-limit traffic that vif1.0 may generate to
- 10Mbps:
+ 10Mbps::
$ ovs-vsctl set interface vif1.0 ingress_policing_rate=10000
$ ovs-vsctl set interface vif1.0 ingress_policing_burst=8000