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.

4 files changed, 7 insertions, 7 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>
diff --git a/lib/megaco/doc/src/megaco_run.xml b/lib/megaco/doc/src/megaco_run.xml
index 3afc638bcf..d998d30de4 100644
--- a/lib/megaco/doc/src/megaco_run.xml
+++ b/lib/megaco/doc/src/megaco_run.xml
@@ -365,7 +365,7 @@
           then the specified max message size (see the 
           <seealso marker="megaco#user_info">max_pdu_size</seealso> option).
           Finally, if segmentation is decided, then each action reply
-          will make up it's own (segment) message.</p>
+          will make up its own (segment) message.</p>
       </item>
     </list>
   </section>
diff --git a/lib/megaco/doc/src/megaco_user.xml b/lib/megaco/doc/src/megaco_user.xml
index 37942007bc..da4c961b51 100644
--- a/lib/megaco/doc/src/megaco_user.xml
+++ b/lib/megaco/doc/src/megaco_user.xml
@@ -669,7 +669,7 @@ protocol_version() = integer()    ]]></code>
         <p>Invoked when a unexpected message is received</p>
         <p>If a reply to a request is not received in time, the
           megaco stack removes all info about the request from
-          it's tables. If a reply should arrive after this has been
+          its tables. If a reply should arrive after this has been
           done the app has no way of knowing where to send this message.
           The message is delivered to the "user" by calling this
           function on the local node (the node which has the link).</p>
diff --git a/lib/megaco/doc/src/notes_history.xml b/lib/megaco/doc/src/notes_history.xml
index 97aa4c66a5..2256f7d60d 100644
--- a/lib/megaco/doc/src/notes_history.xml
+++ b/lib/megaco/doc/src/notes_history.xml
@@ -2764,7 +2764,7 @@
           <p>Added a new configuration parameter, threaded.
             This tells the megaco app, that all
             transaction requests in a message should be executed
-            in parallel (e.g. each in it's own process). 
+            in parallel (e.g. each in its own process).
             <br></br>See the 
             <seealso marker="megaco#user_info">threaded</seealso> parameter
             of the user_info function (also conn_info).</p>
@@ -2911,7 +2911,7 @@
       <title>Improvements and new features</title>
       <list type="bulleted">
         <item>
-          <p>This is just a code up-/downgrade cleanup release. I.e. It's the
+          <p>This is just a code up-/downgrade cleanup release. I.e. it's the
             same as version 1.2 minus the ugly stuff needed to handle up-/downgrade
             from/to version 1.1.2, 1.1.1 and 1.1.0.</p>
         </item>