File otp_src_24.1-doc-the-the.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File otp_src_24.1-doc-the-the.patch of Package erlang (Revision e1e1318bc8a36afe77940a6e4ed365bf)

Currently displaying revision e1e1318bc8a36afe77940a6e4ed365bf , Show latest

diff -Ndurp otp_src_24.1/erts/doc/src/erlang.xml otp_src_24.1-doc-the-the/erts/doc/src/erlang.xml
--- otp_src_24.1/erts/doc/src/erlang.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/erts/doc/src/erlang.xml	2021-09-22 11:37:46.915325328 +0300
@@ -7957,7 +7957,7 @@ true</pre>
 	 corresponds to scheduler number 1 and so on. If support for
 	 dirty schedulers exist, an element with the value for the
 	 dirty CPU run queue and its associated dirty CPU schedulers
-	 follow and then as last element the value for the the dirty
+	 follow and then as last element the value for the dirty
 	 IO run queue and its associated dirty IO schedulers follow.
 	 The information is not gathered atomically. That is,
 	 the result is not necessarily a consistent snapshot of the
diff -Ndurp otp_src_24.1/erts/doc/src/erl_dist_protocol.xml otp_src_24.1-doc-the-the/erts/doc/src/erl_dist_protocol.xml
--- otp_src_24.1/erts/doc/src/erl_dist_protocol.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/erts/doc/src/erl_dist_protocol.xml	2021-09-22 11:37:46.915325328 +0300
@@ -1485,7 +1485,7 @@ DiB == gen_digest(ChA, ICA)?
 	 <item>Process identifier of the group leader of the
 	 newly created process.</item>
 	 <tag><c>{Module :: atom(), Function :: atom(), Arity :: integer() >= 0}</c></tag>
-	 <item>Entry point for the the new process.</item>
+	 <item>Entry point for the new process.</item>
 	 <tag><c>OptList :: [term()]</c></tag>
 	 <item>A proper list of spawn options to use when spawning.</item>
 	 <tag><c>ArgList :: [term()]</c></tag>
diff -Ndurp otp_src_24.1/erts/doc/src/notes.xml otp_src_24.1-doc-the-the/erts/doc/src/notes.xml
--- otp_src_24.1/erts/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/erts/doc/src/notes.xml	2021-09-22 11:37:46.919325231 +0300
@@ -16172,7 +16172,7 @@
 
 	 The previous default of a maximum of 32768 simultaneous
 	 processes has been raised to 262144. This value can be
-	 changed using the the <seecom
+	 changed using the <seecom
 	 marker="erl#+P">+P</seecom> command line flag of
 	 <seecom marker="erl">erl(1)</seecom>. Note that the
 	 value passed now is considered as a hint, and that actual
diff -Ndurp otp_src_24.1/lib/asn1/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/asn1/doc/src/notes.xml
--- otp_src_24.1/lib/asn1/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/asn1/doc/src/notes.xml	2021-09-22 11:37:46.919325231 +0300
@@ -564,7 +564,7 @@
 <list>
 <item>
 
-	 Many bugs have been eliminated in the the ASN.1 compiler
+	 Many bugs have been eliminated in the ASN.1 compiler
 	 so that it can now successfully compile many more ASN.1
 	 specifications. Error messages have also been improved.
 
diff -Ndurp otp_src_24.1/lib/common_test/doc/src/ct_property_test.xml otp_src_24.1-doc-the-the/lib/common_test/doc/src/ct_property_test.xml
--- otp_src_24.1/lib/common_test/doc/src/ct_property_test.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/common_test/doc/src/ct_property_test.xml	2021-09-22 11:37:46.919325231 +0300
@@ -78,7 +78,7 @@
 ftp_simple_client_server:prop_ftp(),
 Config
 ).</code>
- and the the property test module (in this example <c>ftp_simple_client_server.erl</c>)
+ and the property test module (in this example <c>ftp_simple_client_server.erl</c>)
 as almost a usual property testing module
 (More examples are in <seeguide marker="ct_property_test_chapter">the User's Guide</seeguide>):
 <code>
diff -Ndurp otp_src_24.1/lib/common_test/doc/src/write_test_chapter.xml otp_src_24.1-doc-the-the/lib/common_test/doc/src/write_test_chapter.xml
--- otp_src_24.1/lib/common_test/doc/src/write_test_chapter.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/common_test/doc/src/write_test_chapter.xml	2021-09-22 11:37:46.919325231 +0300
@@ -812,7 +812,7 @@
 
 In the data directory, <c>data_dir</c>, the test module has
 its own files needed for the testing. The name of <c>data_dir</c>
- is the the name of the test suite followed by <c>"_data"</c>.
+ is the name of the test suite followed by <c>"_data"</c>.
 For example, <c>"some_path/foo_SUITE.beam"</c> has the data directory
 <c>"some_path/foo_SUITE_data/"</c>. Use this directory for portability,
 that is, to avoid hardcoding directory names in your suite. As the data
diff -Ndurp otp_src_24.1/lib/compiler/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/compiler/doc/src/notes.xml
--- otp_src_24.1/lib/compiler/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/compiler/doc/src/notes.xml	2021-09-22 11:37:46.919325231 +0300
@@ -3802,7 +3802,7 @@
 </item>
 <item>
 
-	 Code that (incorrectly) used the the value of nested
+	 Code that (incorrectly) used the value of nested
 	 applications of <c>setelement/3</c> in bit syntax
 	 construction could crash the compiler.
 
diff -Ndurp otp_src_24.1/lib/diameter/doc/src/diameter_app.xml otp_src_24.1-doc-the-the/lib/diameter/doc/src/diameter_app.xml
--- otp_src_24.1/lib/diameter/doc/src/diameter_app.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/diameter/doc/src/diameter_app.xml	2021-09-22 11:37:46.919325231 +0300
@@ -92,7 +92,7 @@ is called in response to an incoming Dia
 </list>
 
 
-The arities for the the callback functions here assume no extra arguments.
+The arities for the callback functions here assume no extra arguments.
 All functions will also be passed any extra arguments configured with
 the callback module itself when calling &mod_start_service;
 and, for the call-specific callbacks, any extra arguments passed to
diff -Ndurp otp_src_24.1/lib/diameter/doc/src/diameter_dict.xml otp_src_24.1-doc-the-the/lib/diameter/doc/src/diameter_dict.xml
--- otp_src_24.1/lib/diameter/doc/src/diameter_dict.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/diameter/doc/src/diameter_dict.xml	2021-09-22 11:37:46.919325231 +0300
@@ -109,7 +109,7 @@ defined.
 
 A dictionary file consists of distinct sections.
 Each section starts with a tag followed by zero or more arguments
-and ends at the the start of the next section or end of file.
+and ends at the start of the next section or end of file.
 Tags consist of an ampersand character followed by a keyword and are
 separated from their arguments by whitespace.
 Whitespace separates individual tokens but is otherwise insignificant.
@@ -196,7 +196,7 @@ Example:
 <marker id="vendor"/><c>@vendor Number Name</c></tag>
 <item>
 
-Defines the integer Number as the the default Vendor-Id of AVPs for
+Defines the integer Number as the default Vendor-Id of AVPs for
 which the V flag is set.
 Name documents the owner of the application
 but is otherwise unused.
diff -Ndurp otp_src_24.1/lib/diameter/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/diameter/doc/src/notes.xml
--- otp_src_24.1/lib/diameter/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/diameter/doc/src/notes.xml	2021-09-22 11:37:46.919325231 +0300
@@ -2050,7 +2050,7 @@ first.
 
 	 Fix #diameter_header{} handling broken by OTP-10445.
 
-	 The fault caused the the header of a [Header | Avps]
+	 The fault caused the header of a [Header | Avps]
 	 request to be ignored if both end_to_end_id and
 	 hop_by_hop_id were undefined.
 
diff -Ndurp otp_src_24.1/lib/erl_docgen/doc/src/doc-build.xml otp_src_24.1-doc-the-the/lib/erl_docgen/doc/src/doc-build.xml
--- otp_src_24.1/lib/erl_docgen/doc/src/doc-build.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/erl_docgen/doc/src/doc-build.xml	2021-09-22 11:37:46.919325231 +0300
@@ -67,7 +67,7 @@
 <title>Use xsltproc to generate different output formats</title>
 
 <section>
- <title>Parameters used in all the the XSL transformations</title>
+ <title>Parameters used in all the XSL transformations</title>
 
 	These parameters to <c>xsltproc</c> are used for all the supported output formats.
 
diff -Ndurp otp_src_24.1/lib/erl_interface/doc/src/ei_connect.xml otp_src_24.1-doc-the-the/lib/erl_interface/doc/src/ei_connect.xml
--- otp_src_24.1/lib/erl_interface/doc/src/ei_connect.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/erl_interface/doc/src/ei_connect.xml	2021-09-22 11:37:46.919325231 +0300
@@ -254,7 +254,7 @@
 	<c>tmo</c> contains timeout time in milliseconds.
 	
 	This callback is optional. Set the <c>writev</c> field
-	in the the <c>ei_socket_callbacks</c> structure to <c>NULL</c> if not
+	in the <c>ei_socket_callbacks</c> structure to <c>NULL</c> if not
 	implemented.
 </item>
 
diff -Ndurp otp_src_24.1/lib/erl_interface/doc/src/ei.xml otp_src_24.1-doc-the-the/lib/erl_interface/doc/src/ei.xml
--- otp_src_24.1/lib/erl_interface/doc/src/ei.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/erl_interface/doc/src/ei.xml	2021-09-22 11:37:46.919325231 +0300
@@ -429,7 +429,7 @@ typedef enum {
 	integer variable pointed to by the <c>size</c> argument. Both <c>size</c>
 	and <c>outbuf</c> can be set to <c>NULL</c>. The integer pointed to
 	by the <c>index</c> argument is updated to refer to the term
-	following after the <c>iodata()</c> term regardless of the the state
+	following after the <c>iodata()</c> term regardless of the state
 	of the <c>size</c> and the <c>outbuf</c> arguments.
 	
 	Note that the buffer pointed to by the <c>outbuf</c> argument
diff -Ndurp otp_src_24.1/lib/inets/doc/src/notes_history.xml otp_src_24.1-doc-the-the/lib/inets/doc/src/notes_history.xml
--- otp_src_24.1/lib/inets/doc/src/notes_history.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/inets/doc/src/notes_history.xml	2021-09-22 11:37:46.919325231 +0300
@@ -228,7 +228,7 @@
 <list type="bulleted">
 <item>
 	[httpd] - The server no longer produces error messages
-	 when the client resets the the connection. This is not an
+	 when the client resets the connection. This is not an
 	 error as far as the server is concerned.
 	Own Id: OTP-6484 Aux Id: seq10568 
 </item>
@@ -1016,7 +1016,7 @@
 	Own Id: OTP-5625 Aux Id: seq9872
 </item>
 <item>
-	When generating dynamic HTTP response bodies the the
+	When generating dynamic HTTP response bodies the
 	 default content-type is now set to "text/html" instead of
 	 "text/plain" which is more intuitive.
 	*** POTENTIAL INCOMPATIBILITY ***
diff -Ndurp otp_src_24.1/lib/inets/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/inets/doc/src/notes.xml
--- otp_src_24.1/lib/inets/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/inets/doc/src/notes.xml	2021-09-22 11:37:46.919325231 +0300
@@ -568,7 +568,7 @@
 <item>
 
 	 Fixed bug that causes a crash in http client when using
-	 hostnames (e.g. localhost) with the the option
+	 hostnames (e.g. localhost) with the option
 	 ipv6_host_with_brackets set to true.
 
 	 This change also fixes a regression: httpc:request fails
diff -Ndurp otp_src_24.1/lib/kernel/doc/src/erl_boot_server.xml otp_src_24.1-doc-the-the/lib/kernel/doc/src/erl_boot_server.xml
--- otp_src_24.1/lib/kernel/doc/src/erl_boot_server.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/kernel/doc/src/erl_boot_server.xml	2021-09-22 11:37:46.919325231 +0300
@@ -77,7 +77,7 @@
 </func>
 <func>
 <name name="start_link" arity="1" since=""/>
- <fsummary>Start the boot server and link to the the caller.</fsummary>
+ <fsummary>Start the boot server and link to the caller.</fsummary>
 <desc>
 Starts the boot server and links to the caller. This function
 is used to start the server if it is included in a supervision
diff -Ndurp otp_src_24.1/lib/kernel/doc/src/erpc.xml otp_src_24.1-doc-the-the/lib/kernel/doc/src/erpc.xml
--- otp_src_24.1/lib/kernel/doc/src/erpc.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/kernel/doc/src/erpc.xml	2021-09-22 11:37:46.919325231 +0300
@@ -393,7 +393,7 @@
 	 The <c>call</c> operation for this specific node
 	 raised an exception of class <c>Class</c> with
 	 exception reason <c>ExceptionReason</c>. These
-	 corresponds the the exceptions that
+	 corresponds the exceptions that
 	 <seemfa marker="#call/5"><c>erpc:call/5</c></seemfa>
 	 can raise.
 	 </item>
diff -Ndurp otp_src_24.1/lib/kernel/doc/src/socket.xml otp_src_24.1-doc-the-the/lib/kernel/doc/src/socket.xml
--- otp_src_24.1/lib/kernel/doc/src/socket.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/kernel/doc/src/socket.xml	2021-09-22 11:37:46.919325231 +0300
@@ -84,7 +84,7 @@
 	which enables a compiler optimization for receiving
 	a message containing a newly created <c>reference()</c>
 	(ignore the part of the message queue that had arrived
-	before the the <c>reference()</c> was created).
+	before the <c>reference()</c> was created).
 
 Another message the user must be prepared for (when making asynchronous
 calls) is the <c>abort</c> message:
diff -Ndurp otp_src_24.1/lib/megaco/doc/src/megaco_user.xml otp_src_24.1-doc-the-the/lib/megaco/doc/src/megaco_user.xml
--- otp_src_24.1/lib/megaco/doc/src/megaco_user.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/megaco/doc/src/megaco_user.xml	2021-09-22 11:37:46.919325231 +0300
@@ -354,7 +354,7 @@ protocol_version() = integer() ]]></c
 will take a long time and that the originator should get
 an immediate 'TransactionPending' reply as interim
 response. The actual processing of these action requests
- instead should be delegated to the the
+ instead should be delegated to the
 handle_trans_long_request/3 callback function with the
 req_data() as one of its arguments. 
 </item>
diff -Ndurp otp_src_24.1/lib/megaco/doc/src/megaco.xml otp_src_24.1-doc-the-the/lib/megaco/doc/src/megaco.xml
--- otp_src_24.1/lib/megaco/doc/src/megaco.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/megaco/doc/src/megaco.xml	2021-09-22 11:37:46.919325231 +0300
@@ -578,7 +578,7 @@ megaco_incr_timer() = #megaco_incr_timer
 
 <tag><c><![CDATA[user_mod]]></c></tag>
 <item>
- Name of the user callback module. See the the reference
+ Name of the user callback module. See the reference
 manual for megaco_user for more info.
 
 <marker id="ui_user_args"></marker>
@@ -587,7 +587,7 @@ megaco_incr_timer() = #megaco_incr_timer
 <tag><c><![CDATA[user_args]]></c></tag>
 <item>
 List of extra arguments to the user callback
- functions. See the the reference manual for megaco_user
+ functions. See the reference manual for megaco_user
 for more info.
 
 <marker id="ui_threaded"></marker>
diff -Ndurp otp_src_24.1/lib/mnesia/doc/src/mnesia.xml otp_src_24.1-doc-the-the/lib/mnesia/doc/src/mnesia.xml
--- otp_src_24.1/lib/mnesia/doc/src/mnesia.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/mnesia/doc/src/mnesia.xml	2021-09-22 11:37:46.923325134 +0300
@@ -2935,7 +2935,7 @@ raise(Name, Amount) ->
 <c>-mnesia dir Directory</c>. The name of the directory
 where all Mnesia data is stored. The directory name
 must be unique for the current node. Two nodes must never
- share the the same Mnesia directory. The results
+ share the same Mnesia directory. The results
 are unpredictable.
 </item>
 <item>
diff -Ndurp otp_src_24.1/lib/odbc/doc/src/getting_started.xml otp_src_24.1-doc-the-the/lib/odbc/doc/src/getting_started.xml
--- otp_src_24.1/lib/odbc/doc/src/getting_started.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/odbc/doc/src/getting_started.xml	2021-09-22 11:37:46.923325134 +0300
@@ -44,7 +44,7 @@
 have an ODBC driver installed for the database that you
 want to access. Both the client machine where you plan to
 run your erlang node and the server machine running the
- database needs the the ODBC driver. (In some cases the
+ database needs the ODBC driver. (In some cases the
 client and the server may be the same machine).</item>
 <item>Secondly you might need to set environment variables
 and paths to appropriate values. This may differ a lot
@@ -56,7 +56,7 @@
 precompiled executable for windows, solaris and linux (SLES10) in the commercial
 build. In the open source distribution it is built the
 same way as all other application using configure and make.
- You may want to provide the the path to your ODBC libraries
+ You may want to provide the path to your ODBC libraries
 using --with-odbc=PATH. </item>
 </list>
 <note>
diff -Ndurp otp_src_24.1/lib/public_key/doc/src/public_key.xml otp_src_24.1-doc-the-the/lib/public_key/doc/src/public_key.xml
--- otp_src_24.1/lib/public_key/doc/src/public_key.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/public_key/doc/src/public_key.xml	2021-09-22 11:37:46.923325134 +0300
@@ -870,7 +870,7 @@ end
 	<item>If a matching fails, there could be circumstances when the certificate should be accepted anyway. Think for
 	example of a web browser where you choose to accept an outdated certificate. This option enables implementation
 	of such a function. This <c>fun/1</c> is called when no <c>ReferenceID</c> matches. The return value of the fun
-	(a <c>boolean()</c>) decides the outcome. If <c>true</c> the the certificate is accepted otherwise
+	(a <c>boolean()</c>) decides the outcome. If <c>true</c> the certificate is accepted otherwise
 	it is rejected. See
 	<seeguide marker="using_public_key#-pinning--a-certificate">"Pinning" a Certificate</seeguide>
 	in the User's Guide.
diff -Ndurp otp_src_24.1/lib/snmp/doc/src/snmp_agent_funct_descr.xml otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_agent_funct_descr.xml
--- otp_src_24.1/lib/snmp/doc/src/snmp_agent_funct_descr.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_agent_funct_descr.xml	2021-09-22 11:37:46.923325134 +0300
@@ -578,7 +578,7 @@
 <section>
 <title>SNMP-VIEW-BASED-ACM-MIB</title>
 The SNMP-VIEW-BASED-ACM-MIB defines managed objects to
- control access to the the managed objects for the managers. 
+ control access to the managed objects for the managers. 
 The View Based Access Control Module (VACM) can be used with 
 any SNMP version. However, if it is used with SNMPv1 or SNMPv2c, 
 the SNMP-COMMUNITY-MIB defines additional objects to map 
diff -Ndurp otp_src_24.1/lib/snmp/doc/src/snmp_app.xml otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_app.xml
--- otp_src_24.1/lib/snmp/doc/src/snmp_app.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_app.xml	2021-09-22 11:37:46.923325134 +0300
@@ -982,7 +982,7 @@ in the snmp_config file!
 <c><![CDATA[atl_type() = read | write | read_write <optional>]]></c></tag>
 <item>
 Specifies what type of an audit trail log should be used. 
- The effect of the type is actually different for the the agent
+ The effect of the type is actually different for the agent
 and the manager. 
 For the agent:
 <list type="bulleted">
diff -Ndurp otp_src_24.1/lib/snmp/doc/src/snmp_config.xml otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_config.xml
--- otp_src_24.1/lib/snmp/doc/src/snmp_config.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmp_config.xml	2021-09-22 11:37:46.923325134 +0300
@@ -1003,7 +1003,7 @@ in so far as it will be converted to the
 <c><![CDATA[atl_type() = read | write | read_write <optional>]]></c></tag>
 <item>
 Specifies what type of an audit trail log should be used. 
- The effect of the type is actually different for the the agent
+ The effect of the type is actually different for the agent
 and the manager. 
 For the agent:
 <list type="bulleted">
diff -Ndurp otp_src_24.1/lib/snmp/doc/src/snmpm.xml otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmpm.xml
--- otp_src_24.1/lib/snmp/doc/src/snmpm.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/snmp/doc/src/snmpm.xml	2021-09-22 11:37:46.923325134 +0300
@@ -1454,7 +1454,7 @@ priv_key = [integer()] (length is 16 i
 
 <func>
 <name since="">oid_to_type(Oid) -> {ok, Type} | {error, Reason}</name>
- <fsummary>Get the type of the the oid</fsummary>
+ <fsummary>Get the type of the oid</fsummary>
 <type>
 <v>Oid = oid()</v>
 <v>Type = atom()</v>
diff -Ndurp otp_src_24.1/lib/ssh/doc/src/configurations.xml otp_src_24.1-doc-the-the/lib/ssh/doc/src/configurations.xml
--- otp_src_24.1/lib/ssh/doc/src/configurations.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssh/doc/src/configurations.xml	2021-09-22 11:37:46.923325134 +0300
@@ -330,7 +330,7 @@ ok
 	config-file without the need to change the actual call.
 	
 	For demonstration purposes we used <c>prepend</c> instead of <c>append</c>.
-	This forces the negotiation to select <c>ssh-dss</c> since the the full list
+	This forces the negotiation to select <c>ssh-dss</c> since the full list
 	of public key algorithms was
 	<c>['ssh-dss','ecdsa-sha2-nistp256']</c>.
 	Normally it is safer to append a non-default algorithm.
diff -Ndurp otp_src_24.1/lib/ssh/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/ssh/doc/src/notes.xml
--- otp_src_24.1/lib/ssh/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssh/doc/src/notes.xml	2021-09-22 11:37:46.923325134 +0300
@@ -728,7 +728,7 @@
 	 The ssh agent is now implemented in the ssh_agent key
 	 callback module. 
 
-	 Enable with the the option <c> {key_cb, {ssh_agent,
+	 Enable with the option <c> {key_cb, {ssh_agent,
 	 []}}</c> in for example ssh:connect/3.
 
 	 See the <seeerl marker="ssh:ssh_agent">ssh_agent
@@ -942,7 +942,7 @@
 	 If an OTP SSH server was serving an "exec" request and
 	 the executed code used Erlang <c>standard_io</c> for
 	 input/output, the I/O was erroneously handled by the
-	 *server's* group leader, so the I/O turned up in the the
+	 *server's* group leader, so the I/O turned up in the
 	 server's Erlang shell (if any). The user at the client
 	 side did therefor not see that I/O.
 
diff -Ndurp otp_src_24.1/lib/ssh/doc/src/ssh_protocol.xml otp_src_24.1-doc-the-the/lib/ssh/doc/src/ssh_protocol.xml
--- otp_src_24.1/lib/ssh/doc/src/ssh_protocol.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssh/doc/src/ssh_protocol.xml	2021-09-22 11:37:46.923325134 +0300
@@ -54,7 +54,7 @@
 software support on the client side. Instead, all authentication
 data should be entered via the keyboard. It is also possible
 to use a pure password based authentication scheme, note that in
- this case the the plain text password will be encrypted before sent
+ this case the plain text password will be encrypted before sent
 over the network. There are several configuration options for
 authentication handling available in
 <seemfa marker="ssh#connect/3">ssh:connect/[3,4]</seemfa>
diff -Ndurp otp_src_24.1/lib/ssh/doc/src/ssh.xml otp_src_24.1-doc-the-the/lib/ssh/doc/src/ssh.xml
--- otp_src_24.1/lib/ssh/doc/src/ssh.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssh/doc/src/ssh.xml	2021-09-22 11:37:46.923325134 +0300
@@ -865,7 +865,7 @@
 	virtualized environment, where there can be more that one
 	server that has the same <c>ip-address</c> and
 	<c>port</c>. If this property is not explicitly set, it is
-	assumed that the the <c>ip-address</c> and <c>port</c>
+	assumed that the <c>ip-address</c> and <c>port</c>
 	uniquely identifies the SSH daemon.
 	
 </desc>
diff -Ndurp otp_src_24.1/lib/ssl/doc/src/ssl_distribution.xml otp_src_24.1-doc-the-the/lib/ssl/doc/src/ssl_distribution.xml
--- otp_src_24.1/lib/ssl/doc/src/ssl_distribution.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssl/doc/src/ssl_distribution.xml	2021-09-22 11:37:46.923325134 +0300
@@ -243,7 +243,7 @@ $ erl -boot /home/me/ssl/start_ssl -prot
 <c>{verify, verify_peer}</c>,
 and the client will verify that the certificate matches
 the node name you are connecting to.
- This only works if the the server certificate is issued
+ This only works if the server certificate is issued
 to the name <c>atom_to_list(TargetNode)</c>.
 
 
diff -Ndurp otp_src_24.1/lib/ssl/doc/src/ssl.xml otp_src_24.1-doc-the-the/lib/ssl/doc/src/ssl.xml
--- otp_src_24.1/lib/ssl/doc/src/ssl.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssl/doc/src/ssl.xml	2021-09-22 11:39:40.808566963 +0300
@@ -442,7 +442,7 @@
 ]
 	 </code>
 
-	 Support for {md5, rsa} was removed from the the TLS-1.2 default in ssl-8.0 (OTP-22) 
+	 Support for {md5, rsa} was removed from the TLS-1.2 default in ssl-8.0 (OTP-22) 
 
 
 <c> TLS_13 _Legacy_Schemes =</c>
diff -Ndurp otp_src_24.1/lib/ssl/doc/src/using_ssl.xml otp_src_24.1-doc-the-the/lib/ssl/doc/src/using_ssl.xml
--- otp_src_24.1/lib/ssl/doc/src/using_ssl.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/ssl/doc/src/using_ssl.xml	2021-09-22 11:37:46.923325134 +0300
@@ -405,7 +405,7 @@ ok
 18,17,174,39,...&gt;&gt;}]}
 </code>
 
- On the server side the the <c>{reuse_sessions, boolean()}</c> option
+ On the server side the <c>{reuse_sessions, boolean()}</c> option
 determines if the server will save session data and allow session
 reuse or not. This can be further customized by the option
 <c>{reuse_session, fun()}</c> that may introduce a local policy for
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/c.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/c.xml
--- otp_src_24.1/lib/stdlib/doc/src/c.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/c.xml	2021-09-22 11:39:02.313499270 +0300
@@ -85,7 +85,7 @@
 is used to search for it relative to the directory of the
 object file.
 
- The source file is compiled with the the original
+ The source file is compiled with the original
 options appended to the given <c><anno>Options</anno></c>, the
 output replacing the old object file if and only if compilation
 succeeds.
@@ -112,7 +112,7 @@
 is used to search for it relative to the directory of the
 object file.
 
- The source file is compiled with the the original
+ The source file is compiled with the original
 options appended to the given <c><anno>Options</anno></c>, the
 output replacing the old object file if and only if compilation
 succeeds. The function <c><anno>Filter</anno></c> specifies
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/gen_event.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/gen_event.xml
--- otp_src_24.1/lib/stdlib/doc/src/gen_event.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/gen_event.xml	2021-09-22 11:37:46.923325134 +0300
@@ -677,7 +677,7 @@ gen_event:stop -----> Modul
 the return value of <c>Module1:terminate/2</c>. This makes it
 possible to transfer information from <c>Handler1</c> to
 <c>Handler2</c>.
- The new handler is added even if the the specified old event
+ The new handler is added even if the specified old event
 handler is not installed, in which case <c>Term=error</c>, or if
 <c>Module1:terminate/2</c> fails with <c>Reason</c>,
 in which case <c>Term={'EXIT',Reason}</c>.
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/gen_statem.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/gen_statem.xml
--- otp_src_24.1/lib/stdlib/doc/src/gen_statem.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/gen_statem.xml	2021-09-22 11:37:46.923325134 +0300
@@ -1049,7 +1049,7 @@ handle_event(_, _, State, Data) ->
 	
 	 If <c>Time</c> is relative and <c>0</c>
 	 no timer is actually started,
-	 instead the the time-out event is enqueued to ensure
+	 instead the time-out event is enqueued to ensure
 	 that it gets processed before any not yet
 	 received external event, but after already queued events.
 	
@@ -1083,7 +1083,7 @@ handle_event(_, _, State, Data) ->
 	
 	 If <c>Time</c> is relative and <c>0</c>
 	 no timer is actually started,
-	 instead the the time-out event is enqueued to ensure
+	 instead the time-out event is enqueued to ensure
 	 that it gets processed before any not yet
 	 received external event.
 	
@@ -1119,7 +1119,7 @@ handle_event(_, _, State, Data) ->
 	
 	 If <c>Time</c> is relative and <c>0</c>
 	 no timer is actually started,
-	 instead the the time-out event is enqueued to ensure
+	 instead the time-out event is enqueued to ensure
 	 that it gets processed before any not yet
 	 received external event.
 	
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/notes.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/notes.xml
--- otp_src_24.1/lib/stdlib/doc/src/notes.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/notes.xml	2021-09-22 11:39:55.432212795 +0300
@@ -70,7 +70,7 @@
 </item>
 <item>
 	 Calling <c>c:ls/1</c> with an atom whose contents is
-	 the the name of a file (as opposed to a directory) would
+	 the name of a file (as opposed to a directory) would
 	 crash.
 
 	 Own Id: OTP-17463 Aux Id: GH-4916 
@@ -8257,7 +8257,7 @@
 	 cause a crash.</item> <item>If a QLC restricted some
 	 column of a table in such a way that a traversal using a
 	 match specification was possible and the QLC also
-	 compared the key column or some indexed column of the the
+	 compared the key column or some indexed column of the
 	 table with a column of some other table, <c>qlc</c>
 	 always chose to traverse the table first, never
 	 considering lookup join. This has been changed so that
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/re.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/re.xml
--- otp_src_24.1/lib/stdlib/doc/src/re.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/re.xml	2021-09-22 11:37:46.927325038 +0300
@@ -1640,7 +1640,7 @@ Pattern PCRE matches Perl m
 subject string, all fail, as there is no character to match.
 
 For compatibility with Perl, \s did not used to match the VT character (code
- 11), which made it different from the the POSIX "space" class. However, Perl
+ 11), which made it different from the POSIX "space" class. However, Perl
 added VT at release 5.18, and PCRE followed suit at release 8.34. The default
 \s characters are now HT (9), LF (10), VT (11), FF (12), CR (13), and space
 (32), which are defined as white space in the "C" locale. This list may vary if
diff -Ndurp otp_src_24.1/lib/stdlib/doc/src/slave.xml otp_src_24.1-doc-the-the/lib/stdlib/doc/src/slave.xml
--- otp_src_24.1/lib/stdlib/doc/src/slave.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/stdlib/doc/src/slave.xml	2021-09-22 11:37:46.927325038 +0300
@@ -167,7 +167,7 @@ slave:start(H, Name, Arg).</code>
 <list type="bulleted">
 <item>Erlang/OTP is not installed on the remote host.</item>
 <item>The file system on the other host has a different
- structure to the the master.</item>
+ structure to the master.</item>
 <item>The Erlang nodes have different cookies.</item>
 </list>
 </item>
diff -Ndurp otp_src_24.1/lib/wx/doc/src/wxListCtrl.xml otp_src_24.1-doc-the-the/lib/wx/doc/src/wxListCtrl.xml
--- otp_src_24.1/lib/wx/doc/src/wxListCtrl.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/wx/doc/src/wxListCtrl.xml	2021-09-22 11:37:46.927325038 +0300
@@ -592,7 +592,7 @@
 <fsummary>Sort the items in the list control. </fsummary>
 <desc>Sort the items in the list control. 
 Sorts the items with supplied <c>SortCallBack</c> fun. 
- SortCallBack receives the client data associated with two items to compare (<c>NOT</c> the the index), and should return 0 if the items are equal, a negative value if the first item is less than the second one and a positive value if the first item is greater than the second one.
+ SortCallBack receives the client data associated with two items to compare (<c>NOT</c> the index), and should return 0 if the items are equal, a negative value if the first item is less than the second one and a positive value if the first item is greater than the second one.
 Remark: Notice that the control may only be sorted on client data associated with the items, so you must use SetItemData if you want to be able to sort the items in the control.
 The callback may not call other (wx) processes. 
 </desc>
diff -Ndurp otp_src_24.1/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml otp_src_24.1-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml
--- otp_src_24.1/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml	2021-09-22 11:37:46.931324940 +0300
@@ -14736,7 +14736,7 @@ SILI -switch internal link interface.
 </dataType>
 </attribute>
 <attribute name="operationalStateSil">
- <description>Operational state indicates the the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test.</description>
+ <description>Operational state indicates the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test.</description>
 <noNotification/>
 <nonPersistent/>
 <readOnly/>
@@ -25394,7 +25394,7 @@ rtoAlphaIndex = 4 -&gt; RTO-Alpha = 1/16
 </dataType>
 </attribute>
 <attribute name="rtoBetaIndex">
- <description>This parameter is used for computing the the value of RTTVar (Round Trip Time Variation) of a destination
+ <description>This parameter is used for computing the value of RTTVar (Round Trip Time Variation) of a destination
 address. 
 It's value must be between 0 and 1 (0 &lt; rtoBetaIndex &lt; 1). A value close to 1 gives more importance to the
 last observed variation.
@@ -25467,7 +25467,7 @@ Unit is seconds.</description>
 
 The value of this attribute should be greater than, or equal to the value of the attribute 'pathMaxRtx'.
 
-Note that for a specific association, it might happen that all the remote addresses (if the the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down.
+Note that for a specific association, it might happen that all the remote addresses (if the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down.
 
 Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network.</description>
 <dataType>
@@ -27609,7 +27609,7 @@ The local distinguished name of this MO
 <attribute name="emergencyStateInfo">
 <description>This attribute holds information about the emergency status and the time remaining in the current state.
 
-Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the the value of'time' is insignificant.</description>
+Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the value of'time' is insignificant.</description>
 <noNotification/>
 <readOnly/>
 <dataType>
diff -Ndurp otp_src_24.1/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml otp_src_24.1-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml
--- otp_src_24.1/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml	2021-09-22 11:37:46.931324940 +0300
@@ -14736,7 +14736,7 @@ SILI -switch internal link interface.
 </dataType>
 </attribute>
 <attribute name="operationalStateSil">
- <description>Operational state indicates the the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test.</description>
+ <description>Operational state indicates the traffic handling capability of all ports as a group on the board, i.e it is enabled if one or more of the eight ports is enabled. The purpose of this attribute is only for test.</description>
 <noNotification/>
 <nonPersistent/>
 <readOnly/>
@@ -25394,7 +25394,7 @@ rtoAlphaIndex = 4 -&gt; RTO-Alpha = 1/16
 </dataType>
 </attribute>
 <attribute name="rtoBetaIndex">
- <description>This parameter is used for computing the the value of RTTVar (Round Trip Time Variation) of a destination
+ <description>This parameter is used for computing the value of RTTVar (Round Trip Time Variation) of a destination
 address. 
 It's value must be between 0 and 1 (0 &lt; rtoBetaIndex &lt; 1). A value close to 1 gives more importance to the
 last observed variation.
@@ -25467,7 +25467,7 @@ Unit is seconds.</description>
 
 The value of this attribute should be greater than, or equal to the value of the attribute 'pathMaxRtx'.
 
-Note that for a specific association, it might happen that all the remote addresses (if the the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down.
+Note that for a specific association, it might happen that all the remote addresses (if the remote end is multi homed) becomes unreachable without exceeding the 'associationMaxRtx'. In such a case the association will be closed down.
 
 Note! The value need to be increased to avoid frequent CommLost's in case of an unstable network.</description>
 <dataType>
@@ -27609,7 +27609,7 @@ The local distinguished name of this MO
 <attribute name="emergencyStateInfo">
 <description>This attribute holds information about the emergency status and the time remaining in the current state.
 
-Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the the value of'time' is insignificant.</description>
+Note! If the node is in emergency state USE_DEGRADED, or the emergency state is USE_DISABLED, the value of'time' is insignificant.</description>
 <noNotification/>
 <readOnly/>
 <dataType>
diff -Ndurp otp_src_24.1/system/doc/getting_started/seq_prog.xml otp_src_24.1-doc-the-the/system/doc/getting_started/seq_prog.xml
--- otp_src_24.1/system/doc/getting_started/seq_prog.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/system/doc/getting_started/seq_prog.xml	2021-09-22 11:37:46.935324843 +0300
@@ -845,7 +845,7 @@ reverse([], Reversed_List) ->
 [3,2,1]</pre>
 Consider how <c>Reversed_List</c> is built. It starts as [],
 then successively the heads are taken off of the list to be reversed
- and added to the the <c>Reversed_List</c>, as shown in
+ and added to the <c>Reversed_List</c>, as shown in
 the following:
 <code type="none">
 reverse([1|2,3], []) =>
diff -Ndurp otp_src_24.1/system/doc/programming_examples/bit_syntax.xml otp_src_24.1-doc-the-the/system/doc/programming_examples/bit_syntax.xml
--- otp_src_24.1/system/doc/programming_examples/bit_syntax.xml	2021-09-17 11:20:27.000000000 +0300
+++ otp_src_24.1-doc-the-the/system/doc/programming_examples/bit_syntax.xml	2021-09-22 11:37:46.935324843 +0300
@@ -206,7 +206,7 @@ X:4/little-signed-integer-unit:8</code>
 matching, this default value is only valid for the last
 element. All other binary elements in matching must have a size
 specification.
- The default unit depends on the the type. For <c>integer</c>,
+ The default unit depends on the type. For <c>integer</c>,
 <c>float</c>, and <c>bitstring</c> it is 1. For binary it is 8.
 The default signedness is <c>unsigned</c>.
 The default endianness is <c>big</c>.
@@ -312,7 +312,7 @@ foo(N, Bin) ->
 <title>Binding and Using a Size Variable</title>
 There is one exception to the rule that a variable that is
 as size must be previously bound. It is possible to match and
- bind a variable, and use it as a size within the the same
+ bind a variable, and use it as a size within the same
 binary pattern. For example:
 
 <code type="none"><![CDATA[

Places

File otp_src_24.1-doc-the-the.patch of Package erlang (Revision e1e1318bc8a36afe77940a6e4ed365bf)

Places