spelling

docs/rseries_inside_the_tenant.rst

@@ -31,7 +31,7 @@ Interface Behavior
 
 There are some architectural differences between the r5000/r10000 appliances and the r2000/r4000 appliances that manifest slightly different behavior inside an F5OS tenant. In general, F5OS tenants on the r5000/r10000 platforms have no visibility into the underlying physical interfaces or LAGs that are configured at the F5OS layer. The tenant will be connected to specific interfaces or LAGs based on its VLAN membership. The only exception to this is the HA Group functionality inside the tenant, which has visibility into LAG state and membership to facilitate proper redundancy/failover.
 
-Generally, the r2000/r4000 appliances follow these same principles, but due to some architectural differences these platforms have more visibility into the lower layer interfaces and LAGs that are configured at the F5OS layer. As an example, an F5OS tenant on an r5000/r10000 appliance has no visibility into the physical interfaces at the F5OS layer. Instead, the tenant will see virtual interfaces and the number of interfaces within a tenant will be based upon the number of vCPUs assigned to the tenant. The r5000 and higher platforms will have one virtual interface per TMM since there is one TMM per physical core. This interface is not an Ethernet interface it is an interval virtual NIC interface that is capable of high speeds. The screenshot below shows the interfaces inside the tenant lining up with the number of physical CPU cores per tenant. In the example there are 36 vCPUs assigned to a single F5OS tenant, this will equate to 18 physical CPUs due to hyperthreading. Since TMOS runs HT-Split, there is one TMM per physical core as TMM's run on the even numbered hyperthreads. As seen in the output below, the tenant has 36 total vCPUs assigned. 
+Generally, the r2000/r4000 appliances follow these same principles, but due to some architectural differences these platforms have more visibility into the lower layer interfaces and LAGs that are configured at the F5OS layer. As an example, an F5OS tenant on an r5000/r10000 appliance has no visibility into the physical interfaces at the F5OS layer. Instead, the tenant will see virtual interfaces and the number of interfaces within a tenant will be based upon the number of vCPUs assigned to the tenant. The r5000 and higher platforms will have one virtual interface per TMM since there is one TMM per physical core. This interface is not an Ethernet interface it is an internal virtual NIC interface that is capable of high speeds. The screenshot below shows the interfaces inside the tenant lining up with the number of physical CPU cores per tenant. In the example there are 36 vCPUs assigned to a single F5OS tenant, this will equate to 18 physical CPUs due to hyperthreading. Since TMOS runs HT-Split, there is one TMM per physical core as TMM's run on the even numbered hyperthreads. As seen in the output below, the tenant has 36 total vCPUs assigned. 
 
 
 .. image:: images/rseries_inside_the_tenant/image4.png