diff options
author | Matthias Lang <[email protected]> | 2010-03-15 07:46:50 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2010-03-16 10:55:56 +0100 |
commit | bfd9a4f396d144199cb57376e6928701cf0dc931 (patch) | |
tree | 246a66e1bf48d1a2c9838390a68d87d4f155a74f /lib/megaco/doc/src/megaco_mib.xml | |
parent | 76ff26a3c209408c962a6115bf3426b2a55bd68a (diff) | |
download | otp-bfd9a4f396d144199cb57376e6928701cf0dc931.tar.gz otp-bfd9a4f396d144199cb57376e6928701cf0dc931.tar.bz2 otp-bfd9a4f396d144199cb57376e6928701cf0dc931.zip |
Change all incorrect occurrences of it's to its
The documentation (*.xml) in the otp tree has a common grammatical
problem, "it's" and "its" are often interchanged. That is annoying
for some readers.
This commit consists entirely of "it's" -> "its" changes. I went
through every .xml file in the tree. If there are any remaining
bugs of this type, it's because I missed them, not because I
didn't look.
Diffstat (limited to 'lib/megaco/doc/src/megaco_mib.xml')
-rw-r--r-- | lib/megaco/doc/src/megaco_mib.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/megaco/doc/src/megaco_mib.xml b/lib/megaco/doc/src/megaco_mib.xml index 3c0a549590..15f6a6334b 100644 --- a/lib/megaco/doc/src/megaco_mib.xml +++ b/lib/megaco/doc/src/megaco_mib.xml @@ -50,15 +50,15 @@ lightweight. I.e. the statistic counters are handled separately by different entities of the application. For instance our two transport module(s) (see <seealso marker="megaco_tcp#stats">megaco_tcp</seealso> and <seealso marker="megaco_udp#stats">megaco_udp</seealso>) maintain their - own counters and the application engine (see <seealso marker="megaco#stats">megaco</seealso>) maintain it's own + own counters and the application engine (see <seealso marker="megaco#stats">megaco</seealso>) maintain its own counters.</p> <p>This also means that if a user implement their own transport - service then it has to maintain it's own statistics.</p> + service then it has to maintain its own statistics.</p> </section> <section> <title>Distribution</title> - <p>Each megaco application maintains it's own set of counters. So + <p>Each megaco application maintains its own set of counters. So in a large (distributed) MG/MGC it could be necessary to collect the statistics from several nodes (each) running the megaco application (only one of them with the transport).</p> |