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.

20 files changed, 34 insertions, 34 deletions

diff --git a/lib/appmon/doc/src/appmon_chapter.xml b/lib/appmon/doc/src/appmon_chapter.xml
index 9673a13078..6ab5c390d6 100644
--- a/lib/appmon/doc/src/appmon_chapter.xml
+++ b/lib/appmon/doc/src/appmon_chapter.xml
@@ -226,8 +226,8 @@
       <p>In the left frame it is possible to:</p>
       <list type="bulleted">
         <item>Select which node to supervise.</item>
-        <item>Select an application to view it's process tree.</item>
-        <item>Select an application to view it's specification.</item>
+        <item>Select an application to view its process tree.</item>
+        <item>Select an application to view its specification.</item>
       </list>
       <p>The right frame shows the selected information, either the application 
         specification or the process tree and process information.</p>
diff --git a/lib/erl_interface/doc/src/ei.xml b/lib/erl_interface/doc/src/ei.xml
index 2f65a8c375..5c13e15e36 100644
--- a/lib/erl_interface/doc/src/ei.xml
+++ b/lib/erl_interface/doc/src/ei.xml
@@ -333,7 +333,7 @@ ei_encode_tuple_header(buf, &amp;i, 0);
       <desc>
         <p>This function encodes a list header, with a specified
           arity. The next <c><![CDATA[arity+1]]></c> terms are the elements
-          (actually it's <c><![CDATA[arity]]></c> cons cells) and the tail of the
+          (actually its <c><![CDATA[arity]]></c> cons cells) and the tail of the
           list. Lists and tuples are encoded recursively, so that a
           list may contain another list or tuple.</p>
         <p>E.g. to encode the list <c><![CDATA[[c, d, [e | f]]]]></c>:</p>
diff --git a/lib/inets/doc/src/http_server.xml b/lib/inets/doc/src/http_server.xml
index 547617e2e3..01e0b47d37 100644
--- a/lib/inets/doc/src/http_server.xml
+++ b/lib/inets/doc/src/http_server.xml
@@ -357,7 +357,7 @@ UserName:Password
         <p>The mod_cgi module makes it possible to execute CGI scripts
           in the server.  A file that matches the definition of a
           ScriptAlias config directive is treated as a CGI script.  A CGI
-          script is executed by the server and it's output is returned to
+          script is executed by the server and its output is returned to
           the client. </p>
         <p>The CGI Script response comprises a message-header and a
           message-body, separated by a blank line.  The message-header
diff --git a/lib/inets/doc/src/httpd_util.xml b/lib/inets/doc/src/httpd_util.xml
index 642e5213b0..6ac2b13c72 100644
--- a/lib/inets/doc/src/httpd_util.xml
+++ b/lib/inets/doc/src/httpd_util.xml
@@ -63,7 +63,7 @@
         <v>Etag = string()</v>
       </type>
       <desc>
-        <p><c>create_etag/1</c> calculates the Etag for a file, from it's 
+        <p><c>create_etag/1</c> calculates the Etag for a file, from its
           size and time for last modification. fileinfo is a record defined 
           in <c>kernel/include/file.hrl</c></p>
 
@@ -78,7 +78,7 @@
         <v>HexValue = DecValue = string()</v>
       </type>
       <desc>
-        <p>Converts the hexadecimal value <c>HexValue</c> into it's
+        <p>Converts the hexadecimal value <c>HexValue</c> into its
           decimal equivalent (<c>DecValue</c>).</p>
 
 	<marker id="day"></marker>
diff --git a/lib/kernel/doc/src/erl_ddll.xml b/lib/kernel/doc/src/erl_ddll.xml
index 75dca8a85d..3b0e576e42 100644
--- a/lib/kernel/doc/src/erl_ddll.xml
+++ b/lib/kernel/doc/src/erl_ddll.xml
@@ -730,7 +730,7 @@
               extension suffix, i.e. <c>.so</c>). The name by which
               the driver identifies itself must also be consistent
               with this <c>Name</c> parameter, much as a beam-file's
-              module name much correspond to it's filename.</p>
+              module name much correspond to its filename.</p>
           </item>
           <tag><em>OptionList</em></tag>
           <item>
@@ -742,8 +742,8 @@
               <tag><em>{driver_options, DriverOptionsList}</em></tag>
               <item>
                 <p>This option is to provide options that will change
-                  it's general behavior and will "stick" to the driver
-                  throughout it's lifespan.</p>
+                  its general behavior and will "stick" to the driver
+                  throughout its lifespan.</p>
                 <p>The driver options for a given driver name need
                   always to be consistent, <em>even when the driver is reloaded</em>, meaning that they are as much a part
                   of the driver as the actual name.</p>
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>
diff --git a/lib/runtime_tools/doc/src/erts_alloc_config.xml b/lib/runtime_tools/doc/src/erts_alloc_config.xml
index 5e7cbe4172..078271b5af 100644
--- a/lib/runtime_tools/doc/src/erts_alloc_config.xml
+++ b/lib/runtime_tools/doc/src/erts_alloc_config.xml
@@ -68,7 +68,7 @@
 	   command-line flag to the Erlang runtime system you are going
 	   to use for creation of the allocator configuration. It will
 	   disable features that prevent <c>erts_alloc_config</c> from
-	   doing it's job. Note, you should <em>not</em> use this flag
+	   doing its job. Note, you should <em>not</em> use this flag
 	   when using the created configuration. Also note that it is
 	   important that you use the same
 	   <seealso marker="erts:erl#+S">amount of schedulers</seealso>
diff --git a/lib/snmp/doc/src/notes_history.xml b/lib/snmp/doc/src/notes_history.xml
index 8739400773..cee671afc9 100644
--- a/lib/snmp/doc/src/notes_history.xml
+++ b/lib/snmp/doc/src/notes_history.xml
@@ -1732,7 +1732,7 @@
       version 4.1. </p>
     <p>When performing a downgrade, make sure the verbosity of the
       manager server process is silence, or else the process will crash
-      (due to a bug in version 4.0.4) and be restarted by it's 
+      (due to a bug in version 4.0.4) and be restarted by its
       supervisor.</p>
 
     <section>
@@ -1773,7 +1773,7 @@
       version 4.0.4. </p>
     <p>When performing a downgrade, make sure the verbosity of the
       manager server process is silence, or else the process will crash
-      (due to a bug in version 4.0.4) and be restarted by it's 
+      (due to a bug in version 4.0.4) and be restarted by its
       supervisor.</p>
 
     <section>
@@ -1827,8 +1827,8 @@
         </item>
         <item>
           <p>[manager] The server process contained a bug that caused it 
-            to crash, if it received an exit message from it's gct (GC timer) 
-            process and it's verbosity was <em>log</em> or higher. </p>
+            to crash, if it received an exit message from its gct (GC timer)
+            process and its verbosity was <em>log</em> or higher. </p>
 	  <p>This also effects the application downgrade. </p>
           <p>Own Id: OTP-5306</p>
         </item>
diff --git a/lib/snmp/doc/src/snmp_app.xml b/lib/snmp/doc/src/snmp_app.xml
index e5a725d720..57eb87a759 100644
--- a/lib/snmp/doc/src/snmp_app.xml
+++ b/lib/snmp/doc/src/snmp_app.xml
@@ -80,7 +80,7 @@
 
     <!-- The info below is also found in the snmp_config.xml file -->
 
-    <p>Each snmp component has it's own set of configuration parameters, 
+    <p>Each snmp component has its own set of configuration parameters,
       even though some of the types are common to both components. </p>
 
     <pre>
@@ -693,7 +693,7 @@
         <p>Specifies if and how the audit trail log shall be repaired
           when opened. Unless this parameter has the value <c>snmp_repair</c>
           it is sent to <c>disk_log</c>. If, on the other hand, the value is
-          <c>snmp_repair</c>, snmp attempts to handle certain faults on it's 
+          <c>snmp_repair</c>, snmp attempts to handle certain faults on its
           own. And even if it cannot repair the file, it does not truncate it 
           directly, but instead <em>moves it aside</em> for later off-line 
           analysis.</p>
diff --git a/lib/snmp/doc/src/snmp_config.xml b/lib/snmp/doc/src/snmp_config.xml
index 6fc9cc49f2..5bd36305fc 100644
--- a/lib/snmp/doc/src/snmp_config.xml
+++ b/lib/snmp/doc/src/snmp_config.xml
@@ -704,7 +704,7 @@
         <p>Specifies if and how the audit trail log shall be repaired
           when opened. Unless this parameter has the value <c>snmp_repair</c>
           it is sent to <c>disk_log</c>. If, on the other hand, the value is
-          <c>snmp_repair</c>, snmp attempts to handle certain faults on it's 
+          <c>snmp_repair</c>, snmp attempts to handle certain faults on its
           own. And even if it cannot repair the file, it does not truncate it 
           directly, but instead <em>moves it aside</em> for later off-line 
           analysis.</p>
diff --git a/lib/snmp/doc/src/snmpa_network_interface_filter.xml b/lib/snmp/doc/src/snmpa_network_interface_filter.xml
index d625fd3e4a..d2520def12 100644
--- a/lib/snmp/doc/src/snmpa_network_interface_filter.xml
+++ b/lib/snmp/doc/src/snmpa_network_interface_filter.xml
@@ -153,7 +153,7 @@ pdu_type() = 'get-request' | 'get-next-request' | 'get-response' | 'set-request'
         <p>For the message to be discarded all together, the function 
           <em>must</em> return <em>false</em>. </p>
         <p>Note that it is possible for this function to filter out targets
-          (but <em>not</em> add it's own) by returning an updated 
+          (but <em>not</em> add its own) by returning an updated
           <c>Targets</c> list (<c>NewTargets</c>). </p>
       </desc>
     </func>
diff --git a/lib/snmp/doc/src/snmpm.xml b/lib/snmp/doc/src/snmpm.xml
index 9e7ac75daf..87776555d1 100644
--- a/lib/snmp/doc/src/snmpm.xml
+++ b/lib/snmp/doc/src/snmpm.xml
@@ -920,7 +920,7 @@ priv_key = [integer()]   (length is 16 if priv = usmDESPrivProtocol | usmAesCfb1
         <v>Oids = [oid()]</v>
       </type>
       <desc>
-        <p>Transform a alias-name to it's oid.</p>
+        <p>Transform a alias-name to its oid.</p>
         <p>Note that an alias-name is only unique within the mib, so
           when loading several mib's into a manager, there might be
           several instances of the same aliasname.</p>
@@ -938,7 +938,7 @@ priv_key = [integer()]   (length is 16 if priv = usmDESPrivProtocol | usmAesCfb1
         <v>Reason = term()</v>
       </type>
       <desc>
-        <p>Transform a oid to it's aliasname.</p>
+        <p>Transform a oid to its aliasname.</p>
 
         <marker id="oid_to_type"></marker>
       </desc>
diff --git a/lib/stdlib/doc/src/io_protocol.xml b/lib/stdlib/doc/src/io_protocol.xml
index 201787f7b5..b52e862a5c 100644
--- a/lib/stdlib/doc/src/io_protocol.xml
+++ b/lib/stdlib/doc/src/io_protocol.xml
@@ -195,7 +195,7 @@ latin1, Module, Function, Args} respectively. </p>
   below).</p>
 
   <p>The function will be called with the data the io_server finds on
-  it's device, returning {done, Result, RestChars} when enough data is
+  its device, returning {done, Result, RestChars} when enough data is
   read (in which case Result is sent to the client and RestChars are
   kept in the io_server as a buffer for subsequent input) or {more,
   Continuation}, indicating that more characters are needed to
@@ -741,7 +741,7 @@ optimize anything however. It is important though that the returned
 data is of the right type depending on the options set, so we convert
 the lists to binaries in the correct encoding <em>if possible</em>
 before returning. The function supplied in the get_until request may,
-as it's final result return anything, so only functions actually
+as its final result return anything, so only functions actually
 returning lists can get them converted to binaries. If the request
 contained the encoding tag unicode, the lists can contain all unicode
 codepoints and the binaries should be in UTF-8, if the encoding tag
diff --git a/lib/stdlib/doc/src/ms_transform.xml b/lib/stdlib/doc/src/ms_transform.xml
index 9f178b426c..6c484c5119 100644
--- a/lib/stdlib/doc/src/ms_transform.xml
+++ b/lib/stdlib/doc/src/ms_transform.xml
@@ -245,7 +245,7 @@ ets:select(emp_tab, ets:fun2ms(
                       fun(#emp{empno = [$0 | Rest] }) ->
                               {[$0|Rest],[$1|Rest]}
                       end)).    </code>
-    <p>As a matter of fact, this query hit's the feature of partially bound
+    <p>As a matter of fact, this query hits the feature of partially bound
       keys in the table type <c>ordered_set</c>, so that not the whole
       table need be searched, only the part of the table containing keys
       beginning with <c>0</c> is in fact looked into. </p>
diff --git a/lib/stdlib/doc/src/unicode_usage.xml b/lib/stdlib/doc/src/unicode_usage.xml
index c5bf10b63d..f1b0659ea2 100644
--- a/lib/stdlib/doc/src/unicode_usage.xml
+++ b/lib/stdlib/doc/src/unicode_usage.xml
@@ -143,7 +143,7 @@ en_US.UTF-8</pre>
 <pre>
 $ echo <input>$LC_CTYPE</input>
 en_US.UTF-8</pre>
-<p>The LANG or LC_CTYPE setting should be consistent with what the terminal is capable of, there is no portable way for Erlang to ask the actual terminal about it's UTF-8 capacity, we have to rely on the language and character type settings.</p>
+<p>The LANG or LC_CTYPE setting should be consistent with what the terminal is capable of, there is no portable way for Erlang to ask the actual terminal about its UTF-8 capacity, we have to rely on the language and character type settings.</p>
 <p>To investigate what Erlang thinks about the terminal, the <c>io:getopts()</c> call can be used when the shell is started:</p>
 <pre>
 $ <input>LC_CTYPE=en_US.ISO-8859-1 erl</input>
@@ -185,7 +185,7 @@ Eshell V5.7  (abort with ^G)
 <tag><c>file</c>, <c>group</c> and <c>user</c></tag>
 <item>
 <p>I/O-servers throughout the system are able both to handle Unicode data and has options for converting data upon actual output or input to/from the device. As shown earlier, the <seealso marker="stdlib:shell">shell</seealso> has support for Unicode terminals and the  <seealso marker="kernel:file">file</seealso> module allows for translation to and from various Unicode formats on disk.</p>
-<p>The actual reading and writing of files with Unicode data is however not best done with the <c>file</c> module as it's interface is byte oriented. A file opened with a Unicode encoding (like UTF-8), is then best read or written using the <seealso marker="stdlib:io">io</seealso> module.</p>
+<p>The actual reading and writing of files with Unicode data is however not best done with the <c>file</c> module as its interface is byte oriented. A file opened with a Unicode encoding (like UTF-8), is then best read or written using the <seealso marker="stdlib:io">io</seealso> module.</p>
 </item>
 <tag><c>re</c></tag>
 <item>
diff --git a/lib/test_server/doc/src/test_server_ctrl.xml b/lib/test_server/doc/src/test_server_ctrl.xml
index 0ed5f88544..4a778bcaf7 100644
--- a/lib/test_server/doc/src/test_server_ctrl.xml
+++ b/lib/test_server/doc/src/test_server_ctrl.xml
@@ -610,7 +610,7 @@ Optional, if not given the test server controller node
           <tag><c>NAME name</c></tag>
           <item>Names the test suite to something else than the
            default name. This does not apply to <c>SPEC</c> which keeps
-           it's names.
+           its names.
           </item>
           <tag><c>PARAMETERS parameterfile</c></tag>
           <item>Specifies the parameter file to use when starting
diff --git a/lib/xmerl/doc/src/notes.xml b/lib/xmerl/doc/src/notes.xml
index 0f30ae9eca..3106c72bd8 100644
--- a/lib/xmerl/doc/src/notes.xml
+++ b/lib/xmerl/doc/src/notes.xml
@@ -54,7 +54,7 @@
         <item>
           <p>
             A continuation clause of <c>parse_reference/3</c> had
-            it's parameters in wrong order.</p>
+            its parameters in wrong order.</p>
           <p>
             Own Id: OTP-8251 Aux Id: seq11429 </p>
         </item>