[Metrics chapter] adding trivial word fixes and exceptions

Author: spier

.github/vale/Vocab/Base/accept.txt

@@ -11,4 +11,6 @@ Fogel
 
 # Orgs
 Mattermost
-Atlasian
+Atlasian
+Universidad
+Rey

measuring/areas.md

@@ -82,4 +82,4 @@ organization.
     we have when measuring this type of metrics is that we can control
     where our InnerSource method is leading those metrics. Increases in
     the code complexity or less test coverage may indicate unexpected
-    behaviours that should be fixed and controlled.
+    behaviors that should be fixed and controlled.

measuring/authors.md

@@ -11,4 +11,3 @@ Chronological order:
 * Gregorio Robles. [Universidad Rey Juan Carlos](https://www.urjc.es/).
 * José Manrique López. [Bitergia](http://bitergia.com).
 * Kate Stewart. [The Linux Foundation](https://www.linuxfoundation.org/).
-

measuring/introduction.md

@@ -10,7 +10,7 @@ This report aims to formalize a strategy and a method to identify,
 acquire and understand metrics, and how to apply those to the inner
 source world. Part of the information found in this document is built on
 top of previous literature and talks about InnerSource. However, none
-of the former seems to focus especifically on the metrics needed to
+of the former seems to focus specifically on the metrics needed to
 understand if a process is working as expected, or if substantial
 changes are required.
 
@@ -35,7 +35,7 @@ Rewarding systems on top of the metrics are also recommended, but always
 with a specific focus on fostering some actions such as pushing
 developers to commit their first pull request[^1]. The point about
 having metrics is that people can cheat on them, so when fostering
-specific behaviours, those should be use in short periods of time to
+specific behaviors, those should be use in short periods of time to
 help developers to get used to some way of developing. The most
 recommended use of metrics is to track the performance of the whole
 community and how to avoid bottlenecks and actions that may delay their

measuring/metrics.md

@@ -18,7 +18,7 @@ process, but this also helps to be more metrics-friendly as there is a
 clear workflow followed by any developer within the organization.
 
 On the other hand, if the workflow is not well defined or if the
-development infrastructure allows to have work arounds, this may lead to
+development infrastructure allows to have work-arounds, this may lead to
 situations where shortcuts are usual, and developers and managers may get
 frustrated at some point.
 
@@ -265,7 +265,7 @@ Scalability
 And this leads to pure scalability. When allowing D2D relationships from
 any place within the organization, middle management roles tend to
 re-convert themselves to community managers that foster that type of
-behaviours, bring hackathons at home and invite third parties to
+behaviors, bring hackathons at home and invite third parties to
 participate in their projects as they participate in others.
 
 Keep Great Developers in House