Remove redundant 'the'

Change-Id: I10ed9148af1144b9010ab6d8bb8dd0539f1bc34b

specs/newton/implemented/compute-node-inventory-newton.rst

@@ -237,7 +237,7 @@ and `NUMA_MEMORY`), create an inventory record for each compute node that
 exposes NUMA topology resources.
 
 For example, let us assume we have a compute node that exposes 2 NUMA nodes
-(cells), each with 4 cores and 8 threads. We would set the the min_unit and
+(cells), each with 4 cores and 8 threads. We would set the min_unit and
 max_unit values of the inventory records to the single-NUMA-cell
 constraints and the total value to the combined number of the resource. So,
 for instance, for the `NUMA_CORES`, we'd set total to 8 (2 sockets having 4

specs/newton/implemented/deprecate-api-proxies.rst

@@ -113,7 +113,7 @@ Networking API
 Nova Network is deprecated, as such the APIs around that networking
 will also be marked as deprecated, as is their use in talking to the
 proxy. A preamble will be written for this section to clarify the
-deprecation of the network API as well as the the proxy to Neutron
+deprecation of the network API as well as the proxy to Neutron
 functionality.
 
 Users who wish to continue to use the Network API in Nova must just

specs/newton/implemented/os-vif-library.rst

@@ -260,7 +260,7 @@ in the "VIFConfig" class shown earlier. This object corresponds to the
 data that can be provided in the <portprofile>...</portprofile> XML
 block. This is required data when a VIF is connected to OpenVSwitch,
 or when using one of the two VEPA modes. This could have been provided
-inline in the the VIFConfig subclasses, but there are a few cases
+inline in the VIFConfig subclasses, but there are a few cases
 where the same data is needed by different VIF types, so breaking it
 out into a separate object allows better reuse, without increasing
 the number of VIF types.