From bfd9a4f396d144199cb57376e6928701cf0dc931 Mon Sep 17 00:00:00 2001 From: Matthias Lang Date: Mon, 15 Mar 2010 07:46:50 +0100 Subject: 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. --- erts/doc/src/alt_dist.xml | 8 ++++---- erts/doc/src/driver.xml | 2 +- erts/doc/src/erl_driver.xml | 2 +- erts/doc/src/erlang.xml | 4 ++-- erts/doc/src/notes.xml | 2 +- lib/appmon/doc/src/appmon_chapter.xml | 4 ++-- lib/erl_interface/doc/src/ei.xml | 2 +- lib/inets/doc/src/http_server.xml | 2 +- lib/inets/doc/src/httpd_util.xml | 4 ++-- lib/kernel/doc/src/erl_ddll.xml | 6 +++--- lib/megaco/doc/src/megaco_mib.xml | 6 +++--- lib/megaco/doc/src/megaco_run.xml | 2 +- lib/megaco/doc/src/megaco_user.xml | 2 +- lib/megaco/doc/src/notes_history.xml | 4 ++-- lib/runtime_tools/doc/src/erts_alloc_config.xml | 2 +- lib/snmp/doc/src/notes_history.xml | 8 ++++---- lib/snmp/doc/src/snmp_app.xml | 4 ++-- lib/snmp/doc/src/snmp_config.xml | 2 +- lib/snmp/doc/src/snmpa_network_interface_filter.xml | 2 +- lib/snmp/doc/src/snmpm.xml | 4 ++-- lib/stdlib/doc/src/io_protocol.xml | 4 ++-- lib/stdlib/doc/src/ms_transform.xml | 2 +- lib/stdlib/doc/src/unicode_usage.xml | 4 ++-- lib/test_server/doc/src/test_server_ctrl.xml | 2 +- lib/xmerl/doc/src/notes.xml | 2 +- 25 files changed, 43 insertions(+), 43 deletions(-) diff --git a/erts/doc/src/alt_dist.xml b/erts/doc/src/alt_dist.xml index a929aec97f..36d83a685b 100644 --- a/erts/doc/src/alt_dist.xml +++ b/erts/doc/src/alt_dist.xml @@ -434,7 +434,7 @@ (13) Word received; /* Bytes received */ (14) struct uds_data *partner; /* The partner in an accept/listen pair */ (15) struct uds_data *next; /* Next structure in list */ -(16) /* The input buffer and it's data */ +(16) /* The input buffer and its data */ (17) int buffer_size; /* The allocated size of the input buffer */ (18) int buffer_pos; /* Current position in input buffer */ (19) int header_pos; /* Where the current header is in the @@ -825,7 +825,7 @@ I/O vector itself. One can use this to allocate the binaries for the queue "manually" in the driver, but we'll just fill the binary array with NULL values (line 7) , which will make - the runtime system allocate it's own buffers when we call + the runtime system allocate its own buffers when we call (line 37).

The routine builds an I/O vector containing the header bytes @@ -942,7 +942,7 @@ between invocations of Erlang nodes with the same name.

The control interface gets a buffer to return its value in, - but is free to allocate it's own buffer is the provided one is + but is free to allocate its own buffer is the provided one is to small. Here is the code for :

function, which is useful as it starts the distribution on a running system, where tracing/debugging can be performed. The routine takes a - list as it's single argument. The lists first element should be + list as its single argument. The lists first element should be the node name (without the "@hostname") as an atom, and the second (and last) element should be one of the atoms or . In the example case is diff --git a/erts/doc/src/driver.xml b/erts/doc/src/driver.xml index 12c79aee90..006a6160de 100644 --- a/erts/doc/src/driver.xml +++ b/erts/doc/src/driver.xml @@ -413,7 +413,7 @@ select(Port, Query) -> Sample asynchronous driver

Sometimes database queries can take long time to complete, in our driver, the emulator - halts while the driver is doing it's job. This is + halts while the driver is doing its job. This is often not acceptable, since no other Erlang processes gets a chance to do anything. To improve on our postgres driver, we reimplement it using the asynchronous diff --git a/erts/doc/src/erl_driver.xml b/erts/doc/src/erl_driver.xml index 5061230a33..497a2fa01d 100644 --- a/erts/doc/src/erl_driver.xml +++ b/erts/doc/src/erl_driver.xml @@ -781,7 +781,7 @@ typedef struct ErlIOVec {

This function reads a timestamp into the memory pointed to by the parameter now. See the description of ErlDrvNowData for - specification of it's fields.

+ specification of its fields.

The return value is 0 unless the now pointer is not valid, in which case it is < 0.

diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 46f8df4683..c4751d7463 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -2749,7 +2749,7 @@ os_prompt%

Works like {spawn, Command}, but only runs - external executables. The Command in it's whole + external executables. The Command in its whole is used as the name of the executable, including any spaces. If arguments are to be passed, the args and arg0 PortSettings can be used.

@@ -2926,7 +2926,7 @@ os_prompt% The standard input and standard output handles of the port program will, if this option is supplied, be opened with the flag FILE_FLAG_OVERLAPPED, so that the port program can (and has to) do - overlapped I/O on it's standard handles. This is not normally + overlapped I/O on its standard handles. This is not normally the case for simple port programs, but an option of value for the experienced Windows programmer. On all other platforms, this option is silently discarded.

diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml index 65b836fc45..c11509131c 100644 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -4681,7 +4681,7 @@

The runtime system with SMP support did not slowly adjust - it's view of time when the system time suddenly changed.

+ its view of time when the system time suddenly changed.

Timeouts could sometimes timeout too early on the runtime system with SMP support.

Own Id: OTP-6202

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 @@

In the left frame it is possible to:

Select which node to supervise. - Select an application to view it's process tree. - Select an application to view it's specification. + Select an application to view its process tree. + Select an application to view its specification.

The right frame shows the selected information, either the application specification or the process tree and process information.

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, &i, 0);

This function encodes a list header, with a specified arity. The next terms are the elements - (actually it's cons cells) and the tail of the + (actually its cons cells) and the tail of the list. Lists and tuples are encoded recursively, so that a list may contain another list or tuple.

E.g. to encode the list :

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

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.

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 @@ Etag = string() -

create_etag/1 calculates the Etag for a file, from it's +

create_etag/1 calculates the Etag for a file, from its size and time for last modification. fileinfo is a record defined in kernel/include/file.hrl

@@ -78,7 +78,7 @@ HexValue = DecValue = string() -

Converts the hexadecimal value HexValue into it's +

Converts the hexadecimal value HexValue into its decimal equivalent (DecValue).

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. .so). The name by which the driver identifies itself must also be consistent with this Name parameter, much as a beam-file's - module name much correspond to it's filename.

+ module name much correspond to its filename.

 OptionList @@ -742,8 +742,8 @@ {driver_options, DriverOptionsList}

This option is to provide options that will change - it's general behavior and will "stick" to the driver - throughout it's lifespan.

+ its general behavior and will "stick" to the driver + throughout its lifespan.

The driver options for a given driver name need always to be consistent, even when the driver is reloaded, meaning that they are as much a part of the driver as the actual name.

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 megaco_tcp and megaco_udp) maintain their - own counters and the application engine (see megaco) maintain it's own + own counters and the application engine (see megaco) maintain its own counters.

This also means that if a user implement their own transport - service then it has to maintain it's own statistics.

+ service then it has to maintain its own statistics.

Distribution -

Each megaco application maintains it's own set of counters. So +

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).

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 max_pdu_size option). Finally, if segmentation is decided, then each action reply - will make up it's own (segment) message.

+ will make up its own (segment) message.

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() ]]>

Invoked when a unexpected message is received

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).

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 @@

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).

See the threaded parameter of the user_info function (also conn_info).

@@ -2911,7 +2911,7 @@ Improvements and new features -

This is just a code up-/downgrade cleanup release. I.e. It's the +

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.

 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 erts_alloc_config from - doing it's job. Note, you should not use this flag + doing its job. Note, you should not use this flag when using the created configuration. Also note that it is important that you use the same amount of schedulers 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.

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.

@@ -1773,7 +1773,7 @@ version 4.0.4.

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.

@@ -1827,8 +1827,8 @@

[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 log or higher.

+ to crash, if it received an exit message from its gct (GC timer) + process and its verbosity was log or higher.

This also effects the application downgrade.

Own Id: OTP-5306

 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 @@ -

Each snmp component has it's own set of configuration parameters, +

Each snmp component has its own set of configuration parameters, even though some of the types are common to both components. 

@@ -693,7 +693,7 @@
         
Specifies if and how the audit trail log shall be repaired
           when opened. Unless this parameter has the value snmp_repair
           it is sent to disk_log. If, on the other hand, the value is
-          snmp_repair, snmp attempts to handle certain faults on it's 
+          snmp_repair, 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 moves it aside for later off-line 
           analysis.

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 @@
         
Specifies if and how the audit trail log shall be repaired
           when opened. Unless this parameter has the value snmp_repair
           it is sent to disk_log. If, on the other hand, the value is
-          snmp_repair, snmp attempts to handle certain faults on it's 
+          snmp_repair, 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 moves it aside for later off-line 
           analysis.

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'
         
For the message to be discarded all together, the function 
           must return false. 

         
Note that it is possible for this function to filter out targets
-          (but not add it's own) by returning an updated 
+          (but not add its own) by returning an updated
           Targets list (NewTargets). 

       
     
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
         Oids = [oid()]
       
       
-        
Transform a alias-name to it's oid.

+        
Transform a alias-name to its oid.

         
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.

@@ -938,7 +938,7 @@ priv_key = [integer()]   (length is 16 if priv = usmDESPrivProtocol | usmAesCfb1
         Reason = term()
       
       
-        
Transform a oid to it's aliasname.

+        
Transform a oid to its aliasname.

 
         
       
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. 

   below).

 
   
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 if possible
 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)).    
-    
As a matter of fact, this query hit's the feature of partially bound
+    
As a matter of fact, this query hits the feature of partially bound
       keys in the table type ordered_set, so that not the whole
       table need be searched, only the part of the table containing keys
       beginning with 0 is in fact looked into. 

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
 $ echo $LC_CTYPE
 en_US.UTF-8
-

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.

+

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.

To investigate what Erlang thinks about the terminal, the io:getopts() call can be used when the shell is started:

 $ LC_CTYPE=en_US.ISO-8859-1 erl
@@ -185,7 +185,7 @@ Eshell V5.7  (abort with ^G)
 file, group and user
 
 
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 shell has support for Unicode terminals and the  file module allows for translation to and from various Unicode formats on disk.

-
The actual reading and writing of files with Unicode data is however not best done with the file 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 io module.

+
The actual reading and writing of files with Unicode data is however not best done with the file 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 io module.

 
 re
 
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
           NAME name
           Names the test suite to something else than the
            default name. This does not apply to SPEC which keeps
-           it's names.
+           its names.
           
           PARAMETERS parameterfile
           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 @@
         
           

             A continuation clause of parse_reference/3 had
-            it's parameters in wrong order.

+            its parameters in wrong order.

           

             Own Id: OTP-8251 Aux Id: seq11429 

         
-- 
cgit v1.2.3