Replace ' the the ' with ' the '

Change-Id: I706ab214f7710d96804a2859989632ba7285053a
Signed-off-by: Ivan Hrasko <ihrasko@cisco.com>

diff --git a/docs/developer-guide/controller.rst b/docs/developer-guide/controller.rst
index fd3d02900d1b3770a6ce0b6f22755b6afc63a235..58e3b0df680d34358e90636e2137cae56c1a9b01 100644 (file)
--- a/docs/developer-guide/controller.rst
+++ b/docs/developer-guide/controller.rst
@@ -684,7 +684,7 @@ MD-SAL RPC routing
 
 The MD-SAL provides a way to deliver Remote Procedure Calls (RPCs) to a
 particular implementation based on content in the input as it is modeled
-in YANG. This part of the the RPC input is referred to as a **context
+in YANG. This part of the RPC input is referred to as a **context
 reference**.
 
 The MD-SAL does not dictate the name of the leaf which is used for this

diff --git a/docs/developer-guide/neutron-service-developer-guide.rst b/docs/developer-guide/neutron-service-developer-guide.rst
index 6191e7c7c7fbc7a71c239d2506c2d13fab55570b..577d7ffb47bfa8c55fc2efe162a1c7b133328e08 100644 (file)
--- a/docs/developer-guide/neutron-service-developer-guide.rst
+++ b/docs/developer-guide/neutron-service-developer-guide.rst
@@ -66,7 +66,7 @@ referred as the above documentation doesn’t always cover the necessary
 details. There is nothing special to utilize those Neutron YANG models.
 The basic procedure will be:
 
-1. subscribe for changes made to the the model
+1. subscribe for changes made to the model
 
 2. respond on the data change notification for each models
 

diff --git a/docs/developer-guide/packetcable-developer-guide.rst b/docs/developer-guide/packetcable-developer-guide.rst
index e7255fc1ec843122650cbb69e45bd96629bbcb3f..d36b56d8cd0ee62c6a87ebb0506d03c0ffc6a899 100644 (file)
--- a/docs/developer-guide/packetcable-developer-guide.rst
+++ b/docs/developer-guide/packetcable-developer-guide.rst
@@ -34,8 +34,8 @@ The packetcable maven project is comprised of several modules.
 |                                      | connections to CCAPS/CMTSes.         |
 +--------------------------------------+--------------------------------------+
 | packetcable-emulator                 | A basic CCAP emulator to facilitate  |
-|                                      | testing the the plugin when no       |
-|                                      | physical CCAP is avaible.            |
+|                                      | testing the plugin when no physical  |
+|                                      | CCAP is avaible.                     |
 +--------------------------------------+--------------------------------------+
 | packetcable-policy-karaf             | Generates a Karaf distribution with  |
 |                                      | a config that loads all the          |

diff --git a/docs/getting-started-guide/concepts_and_tools.rst b/docs/getting-started-guide/concepts_and_tools.rst
index fa702a5e42e96c82322e5597969ddf46d62d3556..e5ccc15e78c9dbd84fa146b260a0c7fa33a1313b 100644 (file)
--- a/docs/getting-started-guide/concepts_and_tools.rst
+++ b/docs/getting-started-guide/concepts_and_tools.rst
@@ -41,5 +41,5 @@ below.
      drivers to notify and communicate with one another.
 
 * If you’re interacting with OpenDaylight through the REST APIs while
-  using the the OpenDaylight interfaces, the microservices architecture allows
+  using the OpenDaylight interfaces, the microservices architecture allows
   you to select available services, protocols, and REST APIs.

diff --git a/docs/user-guide/openflow-plugin-project-user-guide.rst b/docs/user-guide/openflow-plugin-project-user-guide.rst
index f72918d3ffe85bac0490060fbd2434829a30a36b..fa088fefdcef1853e874c1ba0bf7fc18e7b9feaf 100644 (file)
--- a/docs/user-guide/openflow-plugin-project-user-guide.rst
+++ b/docs/user-guide/openflow-plugin-project-user-guide.rst
@@ -274,7 +274,7 @@ this by:
 At this point you should have two interfaces one which gives you NATed
 access to the internet and another that gives you access between your
 mac and the VMs. At least for me, the NATed interface gets a 10.0.2.x
-address and the the host-only interface gets a 192.168.56.x address.
+address and the host-only interface gets a 192.168.56.x address.
 
 Your simplest choice: Use Vagrant
 '''''''''''''''''''''''''''''''''

diff --git a/docs/user-guide/unified-secure-channel.rst b/docs/user-guide/unified-secure-channel.rst
index aae6dbb1229344732d83910f732c2f783ce77f7a..ccb22eef7477fd4e9c5509ea4ed8438ff49da0ed 100644 (file)
--- a/docs/user-guide/unified-secure-channel.rst
+++ b/docs/user-guide/unified-secure-channel.rst
@@ -81,7 +81,7 @@ Administering or Managing USC Channel
 -------------------------------------
 
 After installing the odl-usc-channel-ui feature from the Karaf console,
-users can administer and manage USC channels from the the UI or APIDOCS
+users can administer and manage USC channels from the UI or APIDOCS
 explorer.
 
 Go to