File otp_src_19.3.6.13-doc-the-the.patch of Package erlang
diff -Ndurp otp_src_19.3.6.13/erts/doc/src/notes.xml otp_src_19.3.6.13-doc-the-the/erts/doc/src/notes.xml
--- otp_src_19.3.6.13/erts/doc/src/notes.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/erts/doc/src/notes.xml 2021-03-04 12:00:54.573908005 +0200
@@ -6509,7 +6509,7 @@
<p>
The previous default of a maximum of 32768 simultaneous
processes has been raised to 262144. This value can be
- changed using the the <seealso
+ changed using the <seealso
marker="erl#+P">+P</seealso> command line flag of
<seealso marker="erl">erl(1)</seealso>. Note that the
value passed now is considered as a hint, and that actual
diff -Ndurp otp_src_19.3.6.13/lib/asn1/doc/src/notes.xml otp_src_19.3.6.13-doc-the-the/lib/asn1/doc/src/notes.xml
--- otp_src_19.3.6.13/lib/asn1/doc/src/notes.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/asn1/doc/src/notes.xml 2021-03-04 12:00:54.573908005 +0200
@@ -113,7 +113,7 @@
<list>
<item>
<p>
- 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.</p>
<p>
diff -Ndurp otp_src_19.3.6.13/lib/common_test/doc/src/write_test_chapter.xml otp_src_19.3.6.13-doc-the-the/lib/common_test/doc/src/write_test_chapter.xml
--- otp_src_19.3.6.13/lib/common_test/doc/src/write_test_chapter.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/common_test/doc/src/write_test_chapter.xml 2021-03-04 12:00:54.573908005 +0200
@@ -807,7 +807,7 @@
<p>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_19.3.6.13/lib/compiler/doc/src/notes.xml otp_src_19.3.6.13-doc-the-the/lib/compiler/doc/src/notes.xml
--- otp_src_19.3.6.13/lib/compiler/doc/src/notes.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/compiler/doc/src/notes.xml 2021-03-04 12:00:54.573908005 +0200
@@ -1775,7 +1775,7 @@
</item>
<item>
<p>
- 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.</p>
<p>
diff -Ndurp otp_src_19.3.6.13/lib/cosNotification/doc/src/CosNotifyFilter_Filter.xml otp_src_19.3.6.13-doc-the-the/lib/cosNotification/doc/src/CosNotifyFilter_Filter.xml
--- otp_src_19.3.6.13/lib/cosNotification/doc/src/CosNotifyFilter_Filter.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/cosNotification/doc/src/CosNotifyFilter_Filter.xml 2021-03-04 12:00:54.573908005 +0200
@@ -135,7 +135,7 @@
</type>
<desc>
<p>All constraints associated with the target object are removed by this operation and, since
- the the target object no longer contain any constraints, true will always be the result of
+ the target object no longer contain any constraints, true will always be the result of
any match operation.</p>
</desc>
</func>
diff -Ndurp otp_src_19.3.6.13/lib/diameter/doc/src/diameter_app.xml otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/diameter_app.xml
--- otp_src_19.3.6.13/lib/diameter/doc/src/diameter_app.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/diameter_app.xml 2021-03-04 12:00:54.573908005 +0200
@@ -91,7 +91,7 @@ is called in response to an incoming Dia
</list>
<p>
-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_19.3.6.13/lib/diameter/doc/src/diameter_dict.xml otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/diameter_dict.xml
--- otp_src_19.3.6.13/lib/diameter/doc/src/diameter_dict.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/diameter_dict.xml 2021-03-04 12:00:54.573908005 +0200
@@ -108,7 +108,7 @@ defined.</p>
<p>
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.</p>
@@ -195,7 +195,7 @@ Example:</p>
<marker id="vendor"/><c>@vendor Number Name</c></tag>
<item>
<p>
-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_19.3.6.13/lib/diameter/doc/src/notes.xml otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/notes.xml
--- otp_src_19.3.6.13/lib/diameter/doc/src/notes.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/diameter/doc/src/notes.xml 2021-03-04 12:00:54.573908005 +0200
@@ -1506,7 +1506,7 @@ first.</p>
<p>
Fix #diameter_header{} handling broken by OTP-10445.</p>
<p>
- 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.</p>
<p>
diff -Ndurp otp_src_19.3.6.13/lib/erl_docgen/doc/src/doc-build.xml otp_src_19.3.6.13-doc-the-the/lib/erl_docgen/doc/src/doc-build.xml
--- otp_src_19.3.6.13/lib/erl_docgen/doc/src/doc-build.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/erl_docgen/doc/src/doc-build.xml 2021-03-04 12:00:54.573908005 +0200
@@ -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>
<p>
These parameters to <c>xsltproc</c> are used for all the supported output formats.
</p>
diff -Ndurp otp_src_19.3.6.13/lib/ic/doc/src/ch_c_mapping.xml otp_src_19.3.6.13-doc-the-the/lib/ic/doc/src/ch_c_mapping.xml
--- otp_src_19.3.6.13/lib/ic/doc/src/ch_c_mapping.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/ic/doc/src/ch_c_mapping.xml 2021-03-04 12:00:54.573908005 +0200
@@ -125,7 +125,7 @@ module m1 {
<c>i1</c>. The typedef will produce <c>oe_code_m1_lseq.c</c>.</p>
<p>The header file contains type definitions for all
<c>struct</c> types and sequences and constants in the IDL file. The
- c file contains all operation stubs if the the scope is an interface.</p>
+ c file contains all operation stubs if the scope is an interface.</p>
<p>In addition to the scope-related files a C source file will
be generated for encoding operations of all <c>struct</c> and
sequence types.</p>
@@ -308,7 +308,7 @@ module M1 {
<em>interface object</em> type, and a last parameter of
<em>environment</em> type.</p>
<p></p>
- <p>In a C operation function the the <c>in</c> and <c>out</c>
+ <p>In a C operation function the <c>in</c> and <c>out</c>
parameters are located between the first and last parameters
described above, and they appear in the same order as in the IDL
operation declaration.</p>
diff -Ndurp otp_src_19.3.6.13/lib/inets/doc/src/notes_history.xml otp_src_19.3.6.13-doc-the-the/lib/inets/doc/src/notes_history.xml
--- otp_src_19.3.6.13/lib/inets/doc/src/notes_history.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/inets/doc/src/notes_history.xml 2021-03-04 12:00:54.573908005 +0200
@@ -228,7 +228,7 @@
<list type="bulleted">
<item>
<p>[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.</p>
<p>Own Id: OTP-6484 Aux Id: seq10568 </p>
</item>
@@ -1016,7 +1016,7 @@
<p>Own Id: OTP-5625 Aux Id: seq9872</p>
</item>
<item>
- <p>When generating dynamic HTTP response bodies the the
+ <p>When generating dynamic HTTP response bodies the
default content-type is now set to "text/html" instead of
"text/plain" which is more intuitive.</p>
<p>*** POTENTIAL INCOMPATIBILITY ***</p>
diff -Ndurp otp_src_19.3.6.13/lib/kernel/doc/src/erl_boot_server.xml otp_src_19.3.6.13-doc-the-the/lib/kernel/doc/src/erl_boot_server.xml
--- otp_src_19.3.6.13/lib/kernel/doc/src/erl_boot_server.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/kernel/doc/src/erl_boot_server.xml 2021-03-04 12:00:54.573908005 +0200
@@ -77,7 +77,7 @@
</func>
<func>
<name name="start_link" arity="1"/>
- <fsummary>Start the boot server and link to the the caller.</fsummary>
+ <fsummary>Start the boot server and link to the caller.</fsummary>
<desc>
<p>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_19.3.6.13/lib/megaco/doc/src/megaco_user.xml otp_src_19.3.6.13-doc-the-the/lib/megaco/doc/src/megaco_user.xml
--- otp_src_19.3.6.13/lib/megaco/doc/src/megaco_user.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/megaco/doc/src/megaco_user.xml 2021-03-04 12:00:54.573908005 +0200
@@ -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. </p>
</item>
diff -Ndurp otp_src_19.3.6.13/lib/megaco/doc/src/megaco.xml otp_src_19.3.6.13-doc-the-the/lib/megaco/doc/src/megaco.xml
--- otp_src_19.3.6.13/lib/megaco/doc/src/megaco.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/megaco/doc/src/megaco.xml 2021-03-04 12:00:54.573908005 +0200
@@ -578,7 +578,7 @@ megaco_incr_timer() = #megaco_incr_timer
<tag><c><![CDATA[user_mod]]></c></tag>
<item>
- <p>Name of the user callback module. See the the reference
+ <p>Name of the user callback module. See the reference
manual for megaco_user for more info.</p>
<marker id="ui_user_args"></marker>
@@ -587,7 +587,7 @@ megaco_incr_timer() = #megaco_incr_timer
<tag><c><![CDATA[user_args]]></c></tag>
<item>
<p>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.</p>
<marker id="ui_threaded"></marker>
diff -Ndurp otp_src_19.3.6.13/lib/mnesia/doc/src/mnesia.xml otp_src_19.3.6.13-doc-the-the/lib/mnesia/doc/src/mnesia.xml
--- otp_src_19.3.6.13/lib/mnesia/doc/src/mnesia.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/mnesia/doc/src/mnesia.xml 2021-03-04 12:00:54.573908005 +0200
@@ -2872,7 +2872,7 @@ raise(Name, Amount) ->
<p><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.</p>
</item>
<item>
diff -Ndurp otp_src_19.3.6.13/lib/odbc/doc/src/getting_started.xml otp_src_19.3.6.13-doc-the-the/lib/odbc/doc/src/getting_started.xml
--- otp_src_19.3.6.13/lib/odbc/doc/src/getting_started.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/odbc/doc/src/getting_started.xml 2021-03-04 12:00:54.573908005 +0200
@@ -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_19.3.6.13/lib/snmp/doc/src/snmp_agent_funct_descr.xml otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_agent_funct_descr.xml
--- otp_src_19.3.6.13/lib/snmp/doc/src/snmp_agent_funct_descr.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_agent_funct_descr.xml 2021-03-04 12:00:54.573908005 +0200
@@ -578,7 +578,7 @@
<section>
<title>SNMP-VIEW-BASED-ACM-MIB</title>
<p>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_19.3.6.13/lib/snmp/doc/src/snmp_app.xml otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_app.xml
--- otp_src_19.3.6.13/lib/snmp/doc/src/snmp_app.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_app.xml 2021-03-04 12:00:54.573908005 +0200
@@ -867,7 +867,7 @@
<c><![CDATA[atl_type() = read | write | read_write <optional>]]></c></tag>
<item>
<p>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. </p>
<p>For the agent:</p>
<list type="bulleted">
diff -Ndurp otp_src_19.3.6.13/lib/snmp/doc/src/snmp_config.xml otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_config.xml
--- otp_src_19.3.6.13/lib/snmp/doc/src/snmp_config.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmp_config.xml 2021-03-04 12:00:54.573908005 +0200
@@ -895,7 +895,7 @@ in so far as it will be converted to the
<c><![CDATA[atl_type() = read | write | read_write <optional>]]></c></tag>
<item>
<p>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. </p>
<p>For the agent:</p>
<list type="bulleted">
diff -Ndurp otp_src_19.3.6.13/lib/snmp/doc/src/snmpm.xml otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmpm.xml
--- otp_src_19.3.6.13/lib/snmp/doc/src/snmpm.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/snmp/doc/src/snmpm.xml 2021-03-04 12:00:54.573908005 +0200
@@ -1424,7 +1424,7 @@ priv_key = [integer()] (length is 16 i
<func>
<name>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_19.3.6.13/lib/ssh/doc/src/ssh_protocol.xml otp_src_19.3.6.13-doc-the-the/lib/ssh/doc/src/ssh_protocol.xml
--- otp_src_19.3.6.13/lib/ssh/doc/src/ssh_protocol.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/ssh/doc/src/ssh_protocol.xml 2021-03-04 12:00:54.573908005 +0200
@@ -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
<seealso marker="ssh#connect-3">ssh:connect/[3,4]</seealso>
diff -Ndurp otp_src_19.3.6.13/lib/ssh/doc/src/ssh.xml otp_src_19.3.6.13-doc-the-the/lib/ssh/doc/src/ssh.xml
--- otp_src_19.3.6.13/lib/ssh/doc/src/ssh.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/ssh/doc/src/ssh.xml 2021-03-04 12:00:54.573908005 +0200
@@ -682,7 +682,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.
</p>
</item>
diff -Ndurp otp_src_19.3.6.13/lib/ssl/doc/src/pkix_certs.xml otp_src_19.3.6.13-doc-the-the/lib/ssl/doc/src/pkix_certs.xml
--- otp_src_19.3.6.13/lib/ssl/doc/src/pkix_certs.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/ssl/doc/src/pkix_certs.xml 2021-03-04 12:01:17.277416165 +0200
@@ -37,7 +37,7 @@
are (as always) not working.
</p>
<p>Working certificate definitions for the Internet Community are found
- in the the PKIX RFCs <cite id="rfc3279"></cite> and <cite id="rfc3280"></cite>.
+ in the PKIX RFCs <cite id="rfc3279"></cite> and <cite id="rfc3280"></cite>.
The parsing of certificates in the Erlang/OTP SSL application is
based on those RFCS.
</p>
diff -Ndurp otp_src_19.3.6.13/lib/stdlib/doc/src/gen_event.xml otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/gen_event.xml
--- otp_src_19.3.6.13/lib/stdlib/doc/src/gen_event.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/gen_event.xml 2021-03-04 12:00:54.573908005 +0200
@@ -489,7 +489,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>.</p>
- <p>The new handler is added even if the the specified old event
+ <p>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_19.3.6.13/lib/stdlib/doc/src/notes.xml otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/notes.xml
--- otp_src_19.3.6.13/lib/stdlib/doc/src/notes.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/notes.xml 2021-03-04 12:00:54.577907919 +0200
@@ -5142,7 +5142,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_19.3.6.13/lib/stdlib/doc/src/slave.xml otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/slave.xml
--- otp_src_19.3.6.13/lib/stdlib/doc/src/slave.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/stdlib/doc/src/slave.xml 2021-03-04 12:00:54.577907919 +0200
@@ -160,7 +160,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_19.3.6.13/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml otp_src_19.3.6.13-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml
--- otp_src_19.3.6.13/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CelloMOM.xml 2021-03-04 12:00:54.577907919 +0200
@@ -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 -> 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 < rtoBetaIndex < 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_19.3.6.13/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml otp_src_19.3.6.13-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml
--- otp_src_19.3.6.13/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/lib/xmerl/test/xmerl_SUITE_data/eventp/CMOM.xml 2021-03-04 12:00:54.581907832 +0200
@@ -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 -> 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 < rtoBetaIndex < 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_19.3.6.13/system/doc/getting_started/seq_prog.xml otp_src_19.3.6.13-doc-the-the/system/doc/getting_started/seq_prog.xml
--- otp_src_19.3.6.13/system/doc/getting_started/seq_prog.xml 2019-01-08 15:39:47.000000000 +0200
+++ otp_src_19.3.6.13-doc-the-the/system/doc/getting_started/seq_prog.xml 2021-03-04 12:00:54.581907832 +0200
@@ -844,7 +844,7 @@ reverse([], Reversed_List) ->
[3,2,1]</pre>
<p>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:</p>
<code type="none">
reverse([1|2,3], []) =>
