diff options
Diffstat (limited to 'lib')
27 files changed, 122 insertions, 130 deletions
diff --git a/lib/common_test/doc/src/cover_chapter.xml b/lib/common_test/doc/src/cover_chapter.xml index 0d56d4824c..12db7226c4 100644 --- a/lib/common_test/doc/src/cover_chapter.xml +++ b/lib/common_test/doc/src/cover_chapter.xml @@ -85,7 +85,7 @@ <p>To activate the code coverage support, specify the name of the cover specification file as you start <c>Common Test</c>. Do this by using flag <c>-cover</c> with - <seeerl marker="ct_run"><c>ct_run</c></seeerl>, + <seecom marker="ct_run"><c>ct_run</c></seecom>, for example:</p> <pre> $ ct_run -dir $TESTOBJS/db -cover $TESTOBJS/db/config/db.coverspec</pre> diff --git a/lib/common_test/doc/src/ct.xml b/lib/common_test/doc/src/ct.xml index 79420ec8a4..c3bb257f22 100644 --- a/lib/common_test/doc/src/ct.xml +++ b/lib/common_test/doc/src/ct.xml @@ -1339,8 +1339,8 @@ <desc><marker id="run_test-1"/> <p>Runs tests as specified by the combination of options in <c>Opts</c>. The options are the same as those used with program - <c>ct_run</c>, see <seeerl marker="ct_run#ct_run">Run Tests from - Command Line</seeerl> in the <c>ct_run</c> manual page.</p> + <c>ct_run</c>, see <seecom marker="ct_run#ct_run">Run Tests from + Command Line</seecom> in the <c>ct_run</c> manual page.</p> <p>Here a <c>TestDir</c> can be used to point out the path to a <c>Suite</c>. Option <c>testcase</c> corresponds to option <c>-case</c> in program <c>ct_run</c>. Configuration files diff --git a/lib/common_test/doc/src/event_handler_chapter.xml b/lib/common_test/doc/src/event_handler_chapter.xml index 3ee1ea785a..ee758c3199 100644 --- a/lib/common_test/doc/src/event_handler_chapter.xml +++ b/lib/common_test/doc/src/event_handler_chapter.xml @@ -81,7 +81,7 @@ <marker id="usage"></marker> <title>Use</title> <p>Event handlers can be installed by an <c>event_handler</c> start flag - (<seeerl marker="ct_run"><c>ct_run</c></seeerl>) or option + (<seecom marker="ct_run"><c>ct_run</c></seecom>) or option <seemfa marker="ct#run_test/1"><c>ct:run_test/1</c></seemfa>, where the argument specifies the names of one or more event handler modules.</p> diff --git a/lib/common_test/doc/src/install_chapter.xml b/lib/common_test/doc/src/install_chapter.xml index 2cc7da98f2..17ef6c8dc1 100644 --- a/lib/common_test/doc/src/install_chapter.xml +++ b/lib/common_test/doc/src/install_chapter.xml @@ -36,7 +36,7 @@ <p>The two main interfaces for running tests with <c>Common Test</c> are an executable program named - <seeerl marker="ct_run"><c>ct_run</c></seeerl> and the + <seecom marker="ct_run"><c>ct_run</c></seecom> and the Erlang module <seeerl marker="ct"><c>ct</c></seeerl>. <c>ct_run</c> is compiled for the underlying operating system (for example, Unix/Linux or Windows) during the build of the Erlang/OTP system, @@ -51,11 +51,3 @@ and/or the interface functions in the <c>ct</c> module.</p> </section> </chapter> - - - - - - - - diff --git a/lib/common_test/doc/src/run_test_chapter.xml b/lib/common_test/doc/src/run_test_chapter.xml index f83858cbc0..0b8657ced3 100644 --- a/lib/common_test/doc/src/run_test_chapter.xml +++ b/lib/common_test/doc/src/run_test_chapter.xml @@ -80,7 +80,7 @@ <p>If test suites or help modules include header files stored in other locations than the test directory, these include directories can be specified by using flag <c><![CDATA[-include]]></c> with - <seeerl marker="ct_run"><c>ct_run</c></seeerl>, + <seecom marker="ct_run"><c>ct_run</c></seecom>, or option <c><![CDATA[include]]></c> with <c><![CDATA[ct:run_test/1]]></c>. Also, an include path can be specified with an OS environment variable, <c><![CDATA[CT_INCLUDE_PATH]]></c>.</p> @@ -119,7 +119,7 @@ <marker id="ct_run"></marker> <title>Running Tests from the OS Command Line</title> - <p>The <seeerl marker="ct_run"><c>ct_run</c></seeerl> program can be used + <p>The <seecom marker="ct_run"><c>ct_run</c></seecom> program can be used for running tests from the OS command line, for example, as follows: </p> <list type="bulleted"> @@ -153,7 +153,7 @@ <seeguide marker="run_test_chapter#group_execution">Test Case Group Execution</seeguide>.</p> <p>The following flags can also be used with - <seeerl marker="ct_run"><c>ct_run</c></seeerl>:</p> + <seecom marker="ct_run"><c>ct_run</c></seecom>:</p> <taglist> <tag><c><![CDATA[-help]]></c></tag> <item><p>Lists all available start flags.</p></item> @@ -303,7 +303,7 @@ <c>ct_run -dir ./</c></p></note> <p>For more information about the <c>ct_run</c> program, see module - <seeerl marker="ct_run"><c>ct_run</c></seeerl> and section + <seecom marker="ct_run"><c>ct_run</c></seecom> and section <seeguide marker="install_chapter#general">Installation</seeguide>. </p> </section> diff --git a/lib/common_test/doc/src/write_test_chapter.xml b/lib/common_test/doc/src/write_test_chapter.xml index cfc5b4dd6d..3c3790cfc5 100644 --- a/lib/common_test/doc/src/write_test_chapter.xml +++ b/lib/common_test/doc/src/write_test_chapter.xml @@ -833,7 +833,7 @@ configured to create one dedicated private directory per test case and execution instead. This is accomplished with the flag/option <c>create_priv_dir</c> (to be used with the - <seeerl marker="ct_run"><c>ct_run</c></seeerl> program, the + <seecom marker="ct_run"><c>ct_run</c></seecom> program, the <seemfa marker="ct#run_test/1"><c>ct:run_test/1</c></seemfa> function, or as test specification term). There are three possible values for this option as follows: diff --git a/lib/crypto/doc/src/new_api.xml b/lib/crypto/doc/src/new_api.xml index 08b9a658a2..54097dbfee 100644 --- a/lib/crypto/doc/src/new_api.xml +++ b/lib/crypto/doc/src/new_api.xml @@ -226,7 +226,7 @@ <section> <title>Example of crypto_one_time/5</title> <p>The same example as in the - <seemfa marker="#examples-of-crypto_init-4-and-crypto_update/2">previous section</seemfa>, + <seeguide marker="#examples-of-crypto_init-4-and-crypto_update-2">previous section</seeguide>, but now with one call to <seemfa marker="crypto#crypto_one_time/5">crypto_one_time/5</seemfa>: </p> <code> @@ -249,7 +249,7 @@ <section> <title>Example of crypto_one_time_aead/6</title> <p>The same example as in the - <seemfa marker="#example-of-crypto_one_time/5">previous section</seemfa>, + <seeguide marker="#example-of-crypto_one_time-5">previous section</seeguide>, but now with one call to <seemfa marker="crypto#crypto_one_time_aead/6">crypto_one_time_aead/6</seemfa>: </p> <code> diff --git a/lib/diameter/doc/src/seealso.ent b/lib/diameter/doc/src/seealso.ent index 3deb093834..13395f4d44 100644 --- a/lib/diameter/doc/src/seealso.ent +++ b/lib/diameter/doc/src/seealso.ent @@ -103,22 +103,22 @@ significant. <!-- diameter_dict --> -<!ENTITY dict_data_types '<seeerl marker="diameter_dict#DATA_TYPES">diameter_dict(4)</seeerl>'> - -<!ENTITY dict_Address '<seeerl marker="diameter_dict#DATA_TYPES">Address()</seeerl>'> -<!ENTITY dict_DiameterIdentity '<seeerl marker="diameter_dict#DATA_TYPES">DiameterIdentity()</seeerl>'> -<!ENTITY dict_DiameterURI '<seeerl marker="diameter_dict#DATA_TYPES">DiameterURI()</seeerl>'> -<!ENTITY dict_IPFilterRule '<seeerl marker="diameter_dict#DATA_TYPES">IPFilterRule()</seeerl>'> -<!ENTITY dict_QoSFilterRule '<seeerl marker="diameter_dict#DATA_TYPES">QoSFilterRule()</seeerl>'> -<!ENTITY dict_Grouped '<seeerl marker="diameter_dict#DATA_TYPES">Grouped()</seeerl>'> -<!ENTITY dict_OctetString '<seeerl marker="diameter_dict#DATA_TYPES">OctetString()</seeerl>'> -<!ENTITY dict_Time '<seeerl marker="diameter_dict#DATA_TYPES">Time()</seeerl>'> -<!ENTITY dict_UTF8String '<seeerl marker="diameter_dict#DATA_TYPES">UTF8String()</seeerl>'> -<!ENTITY dict_Unsigned32 '<seeerl marker="diameter_dict#DATA_TYPES">Unsigned32()</seeerl>'> - -<!ENTITY dict_name '<seeerl marker="diameter_dict#name">@name</seeerl>'> -<!ENTITY dict_prefix '<seeerl marker="diameter_dict#prefix">@prefix</seeerl>'> -<!ENTITY dict_inherits '<seeerl marker="diameter_dict#inherits">@inherits</seeerl>'> +<!ENTITY dict_data_types '<seefile marker="diameter_dict#DATA_TYPES">diameter_dict(4)</seefile>'> + +<!ENTITY dict_Address '<seefile marker="diameter_dict#DATA_TYPES">Address()</seefile>'> +<!ENTITY dict_DiameterIdentity '<seefile marker="diameter_dict#DATA_TYPES">DiameterIdentity()</seefile>'> +<!ENTITY dict_DiameterURI '<seefile marker="diameter_dict#DATA_TYPES">DiameterURI()</seefile>'> +<!ENTITY dict_IPFilterRule '<seefile marker="diameter_dict#DATA_TYPES">IPFilterRule()</seefile>'> +<!ENTITY dict_QoSFilterRule '<seefile marker="diameter_dict#DATA_TYPES">QoSFilterRule()</seefile>'> +<!ENTITY dict_Grouped '<seefile marker="diameter_dict#DATA_TYPES">Grouped()</seefile>'> +<!ENTITY dict_OctetString '<seefile marker="diameter_dict#DATA_TYPES">OctetString()</seefile>'> +<!ENTITY dict_Time '<seefile marker="diameter_dict#DATA_TYPES">Time()</seefile>'> +<!ENTITY dict_UTF8String '<seefile marker="diameter_dict#DATA_TYPES">UTF8String()</seefile>'> +<!ENTITY dict_Unsigned32 '<seefile marker="diameter_dict#DATA_TYPES">Unsigned32()</seefile>'> + +<!ENTITY dict_name '<seefile marker="diameter_dict#name">@name</seefile>'> +<!ENTITY dict_prefix '<seefile marker="diameter_dict#prefix">@prefix</seefile>'> +<!ENTITY dict_inherits '<seefile marker="diameter_dict#inherits">@inherits</seefile>'> <!-- diameter_make --> @@ -134,12 +134,12 @@ significant. <!-- reference pages --> -<!ENTITY man_compile '<seemfa marker="diameterc">diameterc(1)</seemfa>'> -<!ENTITY man_main '<seemfa marker="diameter">diameter(3)</seemfa>'> -<!ENTITY man_app '<seemfa marker="diameter_app">diameter_app(3)</seemfa>'> -<!ENTITY man_codec '<seemfa marker="diameter_codec">diameter_codec(3)</seemfa>'> +<!ENTITY man_compile '<seecom marker="diameterc">diameterc(1)</seecom>'> +<!ENTITY man_main '<seeerl marker="diameter">diameter(3)</seeerl>'> +<!ENTITY man_app '<seeerl marker="diameter_app">diameter_app(3)</seeerl>'> +<!ENTITY man_codec '<seeerl marker="diameter_codec">diameter_codec(3)</seeerl>'> <!ENTITY man_dict '<seefile marker="diameter_dict">diameter_dict(4)</seefile>'> -<!ENTITY man_make '<seemfa marker="diameter_make">diameter_make(3)</seemfa>'> -<!ENTITY man_transport '<seemfa marker="diameter_transport">diameter_transport(3)</seemfa>'> -<!ENTITY man_sctp '<seemfa marker="diameter_sctp">diameter_sctp(3)</seemfa>'> -<!ENTITY man_tcp '<seemfa marker="diameter_tcp">diameter_tcp(3)</seemfa>'> +<!ENTITY man_make '<seeerl marker="diameter_make">diameter_make(3)</seeerl>'> +<!ENTITY man_transport '<seeerl marker="diameter_transport">diameter_transport(3)</seeerl>'> +<!ENTITY man_sctp '<seeerl marker="diameter_sctp">diameter_sctp(3)</seeerl>'> +<!ENTITY man_tcp '<seeerl marker="diameter_tcp">diameter_tcp(3)</seeerl>'> diff --git a/lib/erl_docgen/doc/src/overview.xml b/lib/erl_docgen/doc/src/overview.xml index 24eaf3a0e6..ef6986024a 100644 --- a/lib/erl_docgen/doc/src/overview.xml +++ b/lib/erl_docgen/doc/src/overview.xml @@ -48,17 +48,17 @@ <tag><em>Reference Manual</em></tag> <item> <p>(DTD: - <seecref marker="refman_dtds#applicationDTD">application</seecref> + <seeguide marker="refman_dtds#applicationDTD">application</seeguide> A collection of manual pages for modules - (<seecref marker="refman_dtds#erlrefDTD">erlref</seecref>), + (<seeguide marker="refman_dtds#erlrefDTD">erlref</seeguide>), applications - (<seecref marker="refman_dtds#apprefDTD">appref</seecref>), + (<seeguide marker="refman_dtds#apprefDTD">appref</seeguide>), commands - (<seecref marker="refman_dtds#comrefDTD">comref</seecref>), + (<seeguide marker="refman_dtds#comrefDTD">comref</seeguide>), C libraries - (<seecref marker="refman_dtds#crefDTD">cref</seecref>) and + (<seeguide marker="refman_dtds#crefDTD">cref</seeguide>) and files - (<seecref marker="refman_dtds#filerefDTD">fileref</seecref>). + (<seeguide marker="refman_dtds#filerefDTD">fileref</seeguide>). </p> </item> diff --git a/lib/erl_docgen/doc/src/refman_dtds.xml b/lib/erl_docgen/doc/src/refman_dtds.xml index 886031db71..322e9c7442 100644 --- a/lib/erl_docgen/doc/src/refman_dtds.xml +++ b/lib/erl_docgen/doc/src/refman_dtds.xml @@ -55,11 +55,11 @@ groups a set of manual pages into one unit. The structure is similar to the part DTD: first an introduction and then the manual pages, written in separate files with the - <seecref marker="#apprefDTD">appref</seecref>, - <seecref marker="#comrefDTD">comref</seecref>, - <seecref marker="#crefDTD">cref</seecref>, - <seecref marker="#erlrefDTD">erlref</seecref>, or - <seecref marker="#filerefDTD">fileref</seecref> DTD.</p> + <seeguide marker="#apprefDTD">appref</seeguide>, + <seeguide marker="#comrefDTD">comref</seeguide>, + <seeguide marker="#crefDTD">cref</seeguide>, + <seeguide marker="#erlrefDTD">erlref</seeguide>, or + <seeguide marker="#filerefDTD">fileref</seeguide> DTD.</p> <p>Example:</p> <pre> @@ -149,14 +149,14 @@ <p>Contains <seeguide marker="header_tags#headerTAG"><header></seeguide>, - <seecref marker="#appTAG"><app></seecref>, - <seecref marker="#appsummaryTAG"><appsummary></seecref>, - <seecref marker="#descriptionTAG"><description></seecref>, + <seeguide marker="#appTAG"><app></seeguide>, + <seeguide marker="#appsummaryTAG"><appsummary></seeguide>, + <seeguide marker="#descriptionTAG"><description></seeguide>, zero or more - <seecref marker="#sectionTAG"><section></seecref> and - <seecref marker="#funcsTAG"><funcs></seecref>, + <seeguide marker="#sectionTAG"><section></seeguide> and + <seeguide marker="#funcsTAG"><funcs></seeguide>, followed by zero or more - <seecref marker="#authorsTAG"><authors></seecref>.</p> + <seeguide marker="#authorsTAG"><authors></seeguide>.</p> </section> <section> @@ -233,14 +233,14 @@ <p>Contains <seeguide marker="header_tags#headerTAG"><header></seeguide>, - <seecref marker="#comTAG"><com></seecref>, - <seecref marker="#comsummaryTAG"><comsummary></seecref>, - <seecref marker="#descriptionTAG"><description></seecref>, + <seeguide marker="#comTAG"><com></seeguide>, + <seeguide marker="#comsummaryTAG"><comsummary></seeguide>, + <seeguide marker="#descriptionTAG"><description></seeguide>, zero or more - <seecref marker="#sectionTAG"><section></seecref> and - <seecref marker="#funcsTAG"><funcs></seecref>, + <seeguide marker="#sectionTAG"><section></seeguide> and + <seeguide marker="#funcsTAG"><funcs></seeguide>, followed by zero or more - <seecref marker="#authorsTAG"><authors></seecref>.</p> + <seeguide marker="#authorsTAG"><authors></seeguide>.</p> </section> <section> @@ -321,14 +321,14 @@ <p>Contains <seeguide marker="header_tags#headerTAG"><header></seeguide>, - <seecref marker="#libTAG"><lib></seecref>, - <seecref marker="#libsummaryTAG"><libsummary></seecref>, - <seecref marker="#descriptionTAG"><description></seecref>, + <seeguide marker="#libTAG"><lib></seeguide>, + <seeguide marker="#libsummaryTAG"><libsummary></seeguide>, + <seeguide marker="#descriptionTAG"><description></seeguide>, zero or more - <seecref marker="#sectionTAG"><section></seecref> and - <seecref marker="#funcsTAG"><funcs></seecref>, followed by + <seeguide marker="#sectionTAG"><section></seeguide> and + <seeguide marker="#funcsTAG"><funcs></seeguide>, followed by zero or more - <seecref marker="#authorsTAG"><authors></seecref>.</p> + <seeguide marker="#authorsTAG"><authors></seeguide>.</p> </section> <section> @@ -413,14 +413,14 @@ <p>Contains <seeguide marker="header_tags#headerTAG"><header></seeguide>, - <seecref marker="#moduleTAG"><module></seecref>, - <seecref marker="#modulesummaryTAG"><modulesummary></seecref>, - <seecref marker="#descriptionTAG"><description></seecref>, + <seeguide marker="#moduleTAG"><module></seeguide>, + <seeguide marker="#modulesummaryTAG"><modulesummary></seeguide>, + <seeguide marker="#descriptionTAG"><description></seeguide>, zero or more - <seecref marker="#sectionTAG"><section></seecref> and - <seecref marker="#funcsTAG"><funcs></seecref>, + <seeguide marker="#sectionTAG"><section></seeguide> and + <seeguide marker="#funcsTAG"><funcs></seeguide>, followed by zero or more - <seecref marker="#authorsTAG"><authors></seecref>.</p> + <seeguide marker="#authorsTAG"><authors></seeguide>.</p> </section> <section> @@ -491,14 +491,14 @@ <p>Contains <seeguide marker="header_tags#headerTAG"><header></seeguide>, - <seecref marker="#fileTAG"><file></seecref>, - <seecref marker="#filesummaryTAG"><filesummary></seecref>, - <seecref marker="#descriptionTAG"><description></seecref>, + <seeguide marker="#fileTAG"><file></seeguide>, + <seeguide marker="#filesummaryTAG"><filesummary></seeguide>, + <seeguide marker="#descriptionTAG"><description></seeguide>, zero or more - <seecref marker="#sectionTAG"><section></seecref> and - <seecref marker="#funcsTAG"><funcs></seecref>, + <seeguide marker="#sectionTAG"><section></seeguide> and + <seeguide marker="#funcsTAG"><funcs></seeguide>, followed by zero or more - <seecref marker="#authorsTAG"><authors></seecref>.</p> + <seeguide marker="#authorsTAG"><authors></seeguide>.</p> </section> <section> @@ -548,7 +548,7 @@ <p>A group of "formal" function definitions.</p> <p>Contains one or more - <seecref marker="#funcTAG"><func></seecref>.</p> + <seeguide marker="#funcTAG"><func></seeguide>.</p> </section> <section> @@ -558,10 +558,10 @@ <p>A "formal" function definition.</p> <p>Contains one or more - <seecref marker="#nameTAG"><name></seecref>, followed by - <seecref marker="#fsummaryTAG"><fsummary></seecref>, - <seecref marker="#typeTAG"><type></seecref> (optional) and - <seecref marker="#descTAG"><desc></seecref> (optional).</p> + <seeguide marker="#nameTAG"><name></seeguide>, followed by + <seeguide marker="#fsummaryTAG"><fsummary></seeguide>, + <seeguide marker="#typeTAG"><type></seeguide> (optional) and + <seeguide marker="#descTAG"><desc></seeguide> (optional).</p> </section> <section> @@ -610,8 +610,8 @@ <p>Type declarations for the function/command.</p> <p>Contains one or more pairs of - <seecref marker="#vTAG"><v></seecref> and - <seecref marker="#dTAG"><d></seecref> (optional).</p> + <seeguide marker="#vTAG"><v></seeguide> and + <seeguide marker="#dTAG"><d></seeguide> (optional).</p> </section> <section> @@ -647,8 +647,8 @@ <p>Authors of the manual page. The <c>authors</c> element is optional.</p> <p>Contains one or more pairs of - <seecref marker="#anameTAG"><aname></seecref> and - <seecref marker="#emailTAG"><email></seecref>.</p> + <seeguide marker="#anameTAG"><aname></seeguide> and + <seeguide marker="#emailTAG"><email></seeguide>.</p> </section> <section> diff --git a/lib/kernel/doc/src/code.xml b/lib/kernel/doc/src/code.xml index 9db0839f02..421c1ca254 100644 --- a/lib/kernel/doc/src/code.xml +++ b/lib/kernel/doc/src/code.xml @@ -197,7 +197,7 @@ zip:create("mnesia-4.4.7.ez", level in the archive. At startup, the top directory in the embedded archive and all (second level) <c>ebin</c> directories in the embedded archive are added to the code path. - See <seeerl marker="erts:escript"><c>erts:escript(1)</c></seeerl>.</p> + See <seecom marker="erts:escript"><c>erts:escript(1)</c></seecom>.</p> <p>When the choice of directories in the code path is <c>strict</c>, the directory that ends up in the code path is diff --git a/lib/snmp/doc/src/notes.xml b/lib/snmp/doc/src/notes.xml index 707687a616..d4d5dd2f35 100644 --- a/lib/snmp/doc/src/notes.xml +++ b/lib/snmp/doc/src/notes.xml @@ -813,11 +813,11 @@ <item> <p>[agent] Enable SNMP to create missing database directories. </p> <p>Add - <seeerl marker="snmp_config#db_init_error"> - {db_init_error, create_db_and_dir}</seeerl> option to SNMP - <seeerl marker="snmp_config#manager_opts_and_types">manager</seeerl> + <seeguide marker="snmp_config#db_init_error"> + {db_init_error, create_db_and_dir}</seeguide> option to SNMP + <seeguide marker="snmp_config#manager_opts_and_types">manager</seeguide> and - <seeerl marker="snmp_config#agent_opts_and_types">agent</seeerl>. + <seeguide marker="snmp_config#agent_opts_and_types">agent</seeguide>. This allows them to create any missing parent directories for <c>db_dir</c>, rather than treating any missing directories as a fatal error. @@ -1087,9 +1087,9 @@ At present only the default module (<c>snmpa_mib_data_tttn</c>) is provided. </p> <p>A config option for the (agent) - <seeerl marker="snmp_config#agent_mib_server">mib-servers</seeerl> + <seeguide marker="snmp_config#agent_mib_server">mib-servers</seeguide> mib-data backend module has been added to the agent config options, - <seeerl marker="snmp_config#agent_ms_data_module">data_module</seeerl>. </p> + <seeguide marker="snmp_config#agent_ms_data_module">data_module</seeguide>. </p> <p>Own Id: OTP-11101</p> </item> @@ -1101,7 +1101,7 @@ <c>snmpa_mib_storage_mnesia</c>) implementing this behaviour, provided with the app. </p> <p>A config option for the (agent) - <seeerl marker="snmp_config#agent_mib_storage">mib storage</seeerl> + <seeguide marker="snmp_config#agent_mib_storage">mib storage</seeguide> has been added to the agent config options. </p> <p>Own Id: OTP-11107</p> </item> @@ -1549,7 +1549,7 @@ limit the number of varbinds that can be included in a Get-BULK response message. This is specified by the new config option, - <seeerl marker="snmp_config#agent_gb_max_vbs">gb_max_vbs</seeerl>. + <seeguide marker="snmp_config#agent_gb_max_vbs">gb_max_vbs</seeguide>. </p> <p>Own Id: OTP-9700</p> </item> diff --git a/lib/snmp/doc/src/snmp_agent_funct_descr.xml b/lib/snmp/doc/src/snmp_agent_funct_descr.xml index 88f715554b..4fe0ae87ca 100644 --- a/lib/snmp/doc/src/snmp_agent_funct_descr.xml +++ b/lib/snmp/doc/src/snmp_agent_funct_descr.xml @@ -205,12 +205,12 @@ <icaption>MIB Compiler Principles</icaption> </image> <p>The compiler parses the SMI file and associates each table or - variable with an instrumentation function (see the figure <seemfa marker="#image/1">MIB Compiler Principles</seemfa>). The actual - instrumentation functions are not needed at MIB compile time, only + variable with an instrumentation function (see the figure <seeguide marker="#image-1">MIB Compiler Principles</seeguide>). + The actual instrumentation functions are not needed at MIB compile time, only their names. </p> <p>The binary output file produced by the compiler is read by the - agent at MIB load time (see the figure <seemfa marker="#image/2">Starting the Agent</seemfa>). The instrumentation is ordinary Erlang code which + agent at MIB load time (see the figure <seeguide marker="#image-2">Starting the Agent</seeguide>). The instrumentation is ordinary Erlang code which is loaded explicitly or automatically the first time it is called.</p> <marker id="image-2"></marker> <image file="snmp-um-1-image-2.gif"> @@ -457,7 +457,7 @@ </code> <p>The initial values for the managed objects defined in these tables, are read at start-up from a set of configuration files. - These are described in <seeerl marker="snmp_config">Configuration Files</seeerl>. + These are described in <seeguide marker="snmp_config">Configuration Files</seeguide>. </p> <section> @@ -478,7 +478,7 @@ The new compiled MIB must have the same name as the original MIB (i.e. STANDARD-MIB or SNMPv2-MIB), and be located in the SNMP configuration - directory (see <seeerl marker="snmp_config">Configuration Files</seeerl>.) + directory (see <seeguide marker="snmp_config">Configuration Files</seeguide>.) </p> <p>One of these MIBs is always loaded. If only SNMPv1 is used, STANDARD-MIB is loaded, otherwise SNMPv2-MIB is loaded. diff --git a/lib/snmp/doc/src/snmp_manager_funct_descr.xml b/lib/snmp/doc/src/snmp_manager_funct_descr.xml index 8033570c7e..aa1cf8cc77 100644 --- a/lib/snmp/doc/src/snmp_manager_funct_descr.xml +++ b/lib/snmp/doc/src/snmp_manager_funct_descr.xml @@ -56,7 +56,7 @@ <c>snmpm_user_default</c> module, which simply sends an info message to the error_logger. It is however highly recommended that this module be replaced by another that does something useful - (see <seeerl marker="snmp_config#configuration_params">configuration params</seeerl> for more info).</p> + (see <seeguide marker="snmp_config#configuration_params">configuration params</seeguide> for more info).</p> <p>When using version 3, then (at least one) <em>usm user</em> has to be registered.</p> <p>Requests can be issued in two different ways. Synchronous (see diff --git a/lib/snmp/doc/src/snmp_manager_netif.xml b/lib/snmp/doc/src/snmp_manager_netif.xml index 987e1d13ea..f6c9e642cf 100644 --- a/lib/snmp/doc/src/snmp_manager_netif.xml +++ b/lib/snmp/doc/src/snmp_manager_netif.xml @@ -58,7 +58,7 @@ is created that processes the message/request and then exits. </p> <p>There is a <c>server</c> config option, - <seeerl marker="snmp_config#manager_server_nis">netif_sup</seeerl> + <seeguide marker="snmp_config#manager_server_nis">netif_sup</seeguide> that enables "active" Net If supervision. This is very simple mechanism. The (supervising) process simply sends a <seeguide marker="#im_ping">ping</seeguide> message and expects a @@ -142,7 +142,7 @@ Server ! {snmp_inform, Ref, Pdu, PduMS, Domain, Addr} will not make the call to the <seeerl marker="snmpm_network_interface#inform_response">inform_response</seeerl> function). See the - <seeerl marker="snmp_config#manager_irb">inform request behaviour</seeerl> + <seeguide marker="snmp_config#manager_irb">inform request behaviour</seeguide> configuration option for more info.</p> </item> <item> diff --git a/lib/snmp/doc/src/snmpa.xml b/lib/snmp/doc/src/snmpa.xml index ce56c21b1a..178f25ccb0 100644 --- a/lib/snmp/doc/src/snmpa.xml +++ b/lib/snmp/doc/src/snmpa.xml @@ -1396,7 +1396,7 @@ snmp_agent:register_subagent(SA1,[1,2,3], SA2). see the OTP R9C documentation.</p> <p>For information about the current agent config (<c>AgentConfig</c>), see the - <seeerl marker="snmp_config#configuration_params">Configuring the application</seeerl> + <seeguide marker="snmp_config#configuration_params">Configuring the application</seeguide> chapter of the SNMP user's guide.</p> <marker id="restart_worker"></marker> diff --git a/lib/snmp/doc/src/snmpa_error.xml b/lib/snmp/doc/src/snmpa_error.xml index 1a4273d7c8..cbbbf39cc9 100644 --- a/lib/snmp/doc/src/snmpa_error.xml +++ b/lib/snmp/doc/src/snmpa_error.xml @@ -50,7 +50,7 @@ </p> <p>The error report module is configured using the directive <c>error_report_mod</c>, see - <seeerl marker="snmp_config#configuration_params">configuration parameters</seeerl>. + <seeguide marker="snmp_config#configuration_params">configuration parameters</seeguide>. </p> <marker id="config_err"></marker> diff --git a/lib/snmp/doc/src/snmpa_error_io.xml b/lib/snmp/doc/src/snmpa_error_io.xml index 77e1fb9d20..608cf46172 100644 --- a/lib/snmp/doc/src/snmpa_error_io.xml +++ b/lib/snmp/doc/src/snmpa_error_io.xml @@ -47,7 +47,7 @@ </p> <p>This module needs to be explicitly configured, see <seeerl marker="snmpa_error#desc">snmpa_error</seeerl> and - <seeerl marker="snmp_config#configuration_params">configuration parameters</seeerl>. + <seeguide marker="snmp_config#configuration_params">configuration parameters</seeguide>. </p> </description> <funcs> diff --git a/lib/snmp/doc/src/snmpa_error_logger.xml b/lib/snmp/doc/src/snmpa_error_logger.xml index 42cca89fcf..e6554ca49e 100644 --- a/lib/snmp/doc/src/snmpa_error_logger.xml +++ b/lib/snmp/doc/src/snmpa_error_logger.xml @@ -49,7 +49,7 @@ <p>This module is the default error report module, but can be explicitly configured, see <seeerl marker="snmpa_error#desc">snmpa_error</seeerl> and - <seeerl marker="snmp_config#configuration_params">configuration parameters</seeerl>. + <seeguide marker="snmp_config#configuration_params">configuration parameters</seeguide>. </p> </description> <funcs> diff --git a/lib/snmp/doc/src/snmpa_network_interface_filter.xml b/lib/snmp/doc/src/snmpa_network_interface_filter.xml index 35cd547583..f5556ddfd6 100644 --- a/lib/snmp/doc/src/snmpa_network_interface_filter.xml +++ b/lib/snmp/doc/src/snmpa_network_interface_filter.xml @@ -76,7 +76,7 @@ (<c>snmpa_net_if</c>). The default filter accepts all messages.</p> <p>A network interface filter can e.g. be used during testing or for load regulation. If the intended use is load regulation, see also - <seeerl marker="snmp_config#agent_ni_req_limit">req_limit</seeerl> and + <seeguide marker="snmp_config#agent_ni_req_limit">req_limit</seeguide> and the function <seeerl marker="snmpa#register_notification_filter">register_notification_filter</seeerl>. </p> <p>Legacy network interface filter modules used arguments on the form diff --git a/lib/snmp/doc/src/snmpa_supervisor.xml b/lib/snmp/doc/src/snmpa_supervisor.xml index 849b47c58d..f11d669996 100644 --- a/lib/snmp/doc/src/snmpa_supervisor.xml +++ b/lib/snmp/doc/src/snmpa_supervisor.xml @@ -55,7 +55,7 @@ started by calling <c>start_sub_agent/3</c>. </p> <p><c>db_dir</c> is mandatory.</p> - <p>See <seeerl marker="snmp_config#configuration_params">configuration parameters</seeerl> for + <p>See <seeguide marker="snmp_config#configuration_params">configuration parameters</seeguide> for a description of the options.</p> </desc> </func> @@ -77,7 +77,7 @@ </p> <p><c>db_dir</c> is mandatory.</p> <p><c>dir</c> in config is mandatory.</p> - <p>See <seeerl marker="snmp_config">snmp config</seeerl> for + <p>See <seeguide marker="snmp_config">snmp config</seeguide> for a description of the options.</p> </desc> </func> diff --git a/lib/snmp/doc/src/snmpm_user.xml b/lib/snmp/doc/src/snmpm_user.xml index f2290b14b6..bea3cd88cd 100644 --- a/lib/snmp/doc/src/snmpm_user.xml +++ b/lib/snmp/doc/src/snmpm_user.xml @@ -247,7 +247,7 @@ snmp_v1_trap_info() :: {Enteprise :: snmp:oid(), <c>{register, UserId, TargetName2, AgentConfig}</c> is the <em>default user</em>.</p> <p>If the - <seeerl marker="snmp_config#manager_irb">inform request behaviour</seeerl> + <seeguide marker="snmp_config#manager_irb">inform request behaviour</seeguide> configuration option is set to <c>user</c> or <c>{user, integer()}</c>, the response (acknowledgment) to this inform-request will be sent when this function returns.</p> diff --git a/lib/ssl/doc/src/ssl.xml b/lib/ssl/doc/src/ssl.xml index e30bd06e40..4b626ebdec 100644 --- a/lib/ssl/doc/src/ssl.xml +++ b/lib/ssl/doc/src/ssl.xml @@ -34,7 +34,7 @@ <p> This module contains interface functions for the TLS/DTLS protocol. For detailed information about the supported standards see - <seeerl marker="ssl_app">ssl(6)</seeerl>. + <seeapp marker="ssl_app">ssl(6)</seeapp>. </p> </description> @@ -648,7 +648,7 @@ fun(Chain::[public_key:der_encoded()]) -> This option overrides the application environment option <c>protocol_version</c> and <c>dtls_protocol_version</c>. If the environment option is not set, it defaults to all versions, supported by the SSL application. - See also <seeerl marker="ssl:ssl_app">ssl(6).</seeerl></p> + See also <seeapp marker="ssl:ssl_app">ssl(6).</seeapp></p> </desc> </datatype> @@ -700,7 +700,7 @@ fun(srp, Username :: string(), UserState :: term()) -> <desc><p>Specifies the log level for a TLS/DTLS connection. Alerts are logged on <c>notice</c> level, which is the default level. The level <c>debug</c> triggers verbose - logging of TLS/DTLS protocol messages. See also <seeerl marker="ssl_app">ssl(6)</seeerl> + logging of TLS/DTLS protocol messages. See also <seeapp marker="ssl_app">ssl(6)</seeapp> </p> </desc> </datatype> @@ -1254,7 +1254,7 @@ fun(srp, Username :: string(), UserState :: term()) -> <note><p>This option is supported by TLS 1.3 and above and only with stateless session tickets. Ticket lifetime, the number of tickets sent by the server and the maximum number of tickets stored by the server in stateful mode are configured by - <seeerl marker="ssl:ssl_app#configuration">application variables</seeerl>. See also + <seeapp marker="ssl:ssl_app#configuration">application variables</seeapp>. See also <seeguide marker="ssl:using_ssl#anti-replay-protection-in-tls-1.3"> SSL's Users Guide, Anti-Replay Protection in TLS 1.3</seeguide> </p></note> diff --git a/lib/ssl/doc/src/ssl_session_cache_api.xml b/lib/ssl/doc/src/ssl_session_cache_api.xml index 373ee5a3d6..86fdc34fd8 100644 --- a/lib/ssl/doc/src/ssl_session_cache_api.xml +++ b/lib/ssl/doc/src/ssl_session_cache_api.xml @@ -120,7 +120,7 @@ Currently this is the only predefined property, there can also be user-defined properties. See also application environment variable - <seeerl marker="ssl_app">session_cb_init_args</seeerl>. + <seeapp marker="ssl_app">session_cb_init_args</seeapp>. </p> <p>Performs possible initializations of the cache and returns a reference to it that is used as parameter to the other diff --git a/lib/ssl/doc/src/using_ssl.xml b/lib/ssl/doc/src/using_ssl.xml index cf966dde01..5b57a58073 100644 --- a/lib/ssl/doc/src/using_ssl.xml +++ b/lib/ssl/doc/src/using_ssl.xml @@ -254,7 +254,7 @@ ssl:connect("localhost", 9999, </p> <p>Session tickets are sent by servers on newly estalished TLS connections. The number of tickets sent and their lifetime are configurable by application variables. See also - <seeerl marker="ssl:ssl_app#configuration"> SSL's configuration</seeerl>.</p> + <seeapp marker="ssl:ssl_app#configuration"> SSL's configuration</seeapp>.</p> <p>Session tickets are protected by application traffic keys, and in stateless tickets, the opaque data structure itself is self-encrypted.</p> diff --git a/lib/stdlib/doc/src/ets.xml b/lib/stdlib/doc/src/ets.xml index 4eb820092d..5f10818273 100644 --- a/lib/stdlib/doc/src/ets.xml +++ b/lib/stdlib/doc/src/ets.xml @@ -146,8 +146,8 @@ If a match specification passed as argument has excessive nesting which causes scheduler stack exhaustion for the scheduler that the calling process is executing on. - <seeerl marker="erts:erl#sched_thread_stack_size">Scheduler - stack size</seeerl> can be configured when starting the + <seecom marker="erts:erl#sched_thread_stack_size">Scheduler + stack size</seecom> can be configured when starting the runtime system. </p></item> </taglist> @@ -264,8 +264,8 @@ true <p>Some of the functions use a <em>match specification</em>, <c>match_spec</c>. For a brief explanation, see <seemfa marker="#select/2"><c>select/2</c></seemfa>. For a detailed - description, see section <seeerl marker="erts:match_spec"> - Match Specifications in Erlang</seeerl> in ERTS User's Guide.</p> + description, see section <seeguide marker="erts:match_spec"> + Match Specifications in Erlang</seeguide> in ERTS User's Guide.</p> <p>A match specifications with excessive nesting will cause a <seeerl marker="#ets_failures"><c>system_limit</c></seeerl> error exception to be raised.</p> diff --git a/lib/stdlib/doc/src/io_protocol.xml b/lib/stdlib/doc/src/io_protocol.xml index c2292d7d49..847ac63357 100644 --- a/lib/stdlib/doc/src/io_protocol.xml +++ b/lib/stdlib/doc/src/io_protocol.xml @@ -340,7 +340,7 @@ eof <p>Notice that the <c>get_until</c> request allows for a function with the data specified as always being a list. Also, the return value data from such a function can be of any type (as is indeed the case when an - <seemfa marker="stdlib:io#fread/2"><c>io:fread/2,3</c></seemfa> + <seemfa marker="stdlib:io#fread/1"><c>io:fread/2,3</c></seemfa> request is sent to an I/O server). The client must be prepared for data received as answers to those requests to be in various forms. However, the I/O |