Update index.adoc

Author: franz1981

content/post/method-data-scalability/index.adoc

@@ -165,7 +165,7 @@ Nowadays modern CPUs can have multiple https://en.wikipedia.org/wiki/Non-uniform
 
 image::numa.png[NUMA lstopo output]
 
-We can now verify that binding the application to run in 2 physical cores in the same NUMA node would produce a different effect than running over the same.
+We can now verify that binding the application to run in 2 physical cores in the same NUMA node would produce a different effect than running on different ones.
 
 Running on the same node (in node 0):
 
@@ -198,4 +198,4 @@ What we’ve shown so far is pretty scary:
 
 So, what about containers?
 
-In containers, users usually set the cpu quotas (e.g. in the form of request/limit, in https://docs.openshift.com/container-platform/3.11/dev_guide/compute_resources.html[Openshift]) without binding a container to run on a specific NUMA node, which can expose their application to the worse possible version of this issue: in the next part we will focus on this use case with a more realistic example.
+In containers, users usually set the cpu quotas (e.g. in the form of request/limit, in https://docs.openshift.com/container-platform/3.11/dev_guide/compute_resources.html[Openshift]) without binding a container to run on a specific NUMA node, which can expose their application to the worse possible version of this issue: in the next part we will focus on this use case with a more realistic example.