From 48fca0c614add538e95f1075b2777fc396023d31 Mon Sep 17 00:00:00 2001 From: Dominique Hazael-Massieux Date: Tue, 16 Mar 2021 08:50:01 +0100 Subject: [PATCH] Use datatracker URLs for IETF documents rather than tools.ietf.org (#3174) tools.ietf.org are being deprecated per https://mailarchive.ietf.org/arch/msg/tools-discuss/oYrAxb3KayPzZ4SNB1DVZTDPPNo/ changes generated with rg -l https://tools.ietf.org/html --- files/en-us/glossary/base64/index.html | 2 +- files/en-us/glossary/cacheable/index.html | 2 +- files/en-us/glossary/caldav/index.html | 4 ++-- files/en-us/glossary/carddav/index.html | 2 +- files/en-us/glossary/client_hints/index.html | 2 +- files/en-us/glossary/dtls/index.html | 2 +- files/en-us/glossary/entity_header/index.html | 2 +- files/en-us/glossary/hpkp/index.html | 2 +- files/en-us/glossary/http_header/index.html | 2 +- files/en-us/glossary/idempotent/index.html | 2 +- files/en-us/glossary/nntp/index.html | 2 +- files/en-us/glossary/payload_body/index.html | 2 +- files/en-us/glossary/pop/index.html | 6 +++--- files/en-us/glossary/quic/index.html | 2 +- files/en-us/glossary/request_header/index.html | 2 +- files/en-us/glossary/robots.txt/index.html | 2 +- files/en-us/glossary/rtsp/index.html | 2 +- files/en-us/glossary/safe/index.html | 2 +- files/en-us/glossary/stun/index.html | 2 +- files/en-us/glossary/tls/index.html | 2 +- files/en-us/glossary/ttl/index.html | 4 ++-- files/en-us/glossary/udp/index.html | 2 +- files/en-us/glossary/uri/index.html | 2 +- .../apache_configuration_htaccess/index.html | 4 ++-- .../webextensions/api/dns/resolve/index.html | 2 +- .../add-ons/webextensions/api/identity/index.html | 2 +- .../api/webrequest/certificateinfo/index.html | 6 +++--- .../api/webrequest/onauthrequired/index.html | 2 +- .../api/webrequest/securityinfo/index.html | 2 +- files/en-us/mozilla/firefox/releases/14/index.html | 2 +- .../firefox/releases/2/security_changes/index.html | 2 +- files/en-us/mozilla/firefox/releases/52/index.html | 4 ++-- files/en-us/mozilla/firefox/releases/59/index.html | 2 +- files/en-us/mozilla/firefox/releases/7/index.html | 6 +++--- .../certificate_download_specification/index.html | 2 +- .../nss/nss_3.12.6_release_notes/index.html | 2 +- .../nss/nss_3.15.1_release_notes/index.html | 2 +- .../nss/nss_3.15.5_release_notes/index.html | 2 +- .../projects/nss/nss_3.15_release_notes/index.html | 2 +- .../nss/nss_3.16.2.3_release_notes/index.html | 2 +- .../projects/nss/nss_3.16_release_notes/index.html | 2 +- .../nss/nss_3.17.1_release_notes/index.html | 2 +- .../projects/nss/nss_3.20_release_notes/index.html | 2 +- .../projects/nss/nss_3.21_release_notes/index.html | 4 ++-- .../projects/nss/nss_3.24_release_notes/index.html | 2 +- .../projects/nss/nss_3.28_release_notes/index.html | 4 ++-- .../projects/nss/nss_3.39_release_notes/index.html | 2 +- .../projects/nss/nss_3.46_release_notes/index.html | 4 ++-- .../projects/nss/nss_3.47_release_notes/index.html | 4 ++-- .../projects/nss/nss_3.48_release_notes/index.html | 4 ++-- .../projects/nss/nss_api_guidelines/index.html | 2 +- .../en-us/mozilla/projects/nss/overview/index.html | 4 ++-- .../nss_tools__colon__certutil/index.html | 6 +++--- .../mozilla/projects/nss/tools/certutil/index.html | 6 +++--- .../guide/plug-in_development_overview/index.html | 6 +++--- files/en-us/plugins/guide/urls/index.html | 2 +- .../network_monitor/request_details/index.html | 2 +- .../web/api/addresserrors/languagecode/index.html | 2 +- .../authenticatordata/index.html | 2 +- .../attestationobject/index.html | 4 ++-- .../clientdatajson/index.html | 2 +- files/en-us/web/api/document/cookie/index.html | 2 +- files/en-us/web/api/hkdfparams/index.html | 2 +- .../web/api/navigatorlanguage/languages/index.html | 2 +- .../web/api/paymentaddress/languagecode/index.html | 4 ++-- .../web/api/performanceresourcetiming/index.html | 2 +- .../nexthopprotocol/index.html | 4 ++-- .../en-us/web/api/pushmanager/subscribe/index.html | 2 +- .../web/api/pushsubscription/getkey/index.html | 2 +- files/en-us/web/api/rsapssparams/index.html | 4 ++-- .../api/rtcconfiguration/bundlepolicy/index.html | 4 ++-- .../web/api/rtcdatachannel/error_event/index.html | 2 +- files/en-us/web/api/rtcicecandidate/index.html | 2 +- .../cantrickleicecandidates/index.html | 2 +- .../icecandidate_event/index.html | 2 +- files/en-us/web/api/rtcrtpcapabilities/index.html | 2 +- .../en-us/web/api/rtcrtpcodecparameters/index.html | 2 +- .../shownotification/index.html | 2 +- .../en-us/web/api/subtlecrypto/decrypt/index.html | 2 +- .../web/api/subtlecrypto/derivebits/index.html | 2 +- .../web/api/subtlecrypto/derivekey/index.html | 8 ++++---- .../en-us/web/api/subtlecrypto/encrypt/index.html | 4 ++-- .../web/api/subtlecrypto/exportkey/index.html | 6 +++--- .../web/api/subtlecrypto/importkey/index.html | 12 ++++++------ files/en-us/web/api/subtlecrypto/index.html | 2 +- files/en-us/web/api/subtlecrypto/sign/index.html | 10 +++++----- .../web/api/subtlecrypto/unwrapkey/index.html | 8 ++++---- files/en-us/web/api/subtlecrypto/verify/index.html | 4 ++-- .../en-us/web/api/subtlecrypto/wrapkey/index.html | 10 +++++----- files/en-us/web/api/texttrack/index.html | 2 +- .../web/api/web_authentication_api/index.html | 4 ++-- files/en-us/web/api/webrtc_api/index.html | 10 +++++----- .../signaling_and_video_calling/index.html | 2 +- .../api/webrtc_api/using_data_channels/index.html | 2 +- files/en-us/web/api/websockets_api/index.html | 2 +- .../writing_a_websocket_server_in_java/index.html | 4 ++-- .../index.html | 2 +- .../writing_websocket_server/index.html | 4 ++-- .../writing_websocket_servers/index.html | 6 +++--- files/en-us/web/css/_colon_lang/index.html | 2 +- .../live_streaming_web_audio_and_video/index.html | 2 +- files/en-us/web/html/element/blockquote/index.html | 2 +- files/en-us/web/html/element/img/index.html | 2 +- files/en-us/web/html/element/nextid/index.html | 2 +- .../web/http/basics_of_http/data_uris/index.html | 2 +- .../mime_types/common_types/index.html | 4 ++-- files/en-us/web/http/caching/index.html | 4 ++-- .../en-us/web/http/content_negotiation/index.html | 2 +- files/en-us/web/http/cookies/index.html | 2 +- .../web/http/headers/accept-language/index.html | 2 +- .../web/http/headers/clear-site-data/index.html | 2 +- files/en-us/web/http/headers/connection/index.html | 2 +- .../http/headers/content-disposition/index.html | 2 +- .../web/http/headers/content-encoding/index.html | 2 +- .../web/http/headers/content-language/index.html | 2 +- files/en-us/web/http/headers/digest/index.html | 8 ++++---- files/en-us/web/http/headers/expect-ct/index.html | 2 +- files/en-us/web/http/headers/index.html | 14 +++++++------- files/en-us/web/http/headers/keep-alive/index.html | 6 +++--- files/en-us/web/http/headers/save-data/index.html | 2 +- files/en-us/web/http/headers/set-cookie/index.html | 4 ++-- .../http/headers/set-cookie/samesite/index.html | 2 +- files/en-us/web/http/headers/te/index.html | 2 +- .../web/http/headers/transfer-encoding/index.html | 4 ++-- .../en-us/web/http/headers/want-digest/index.html | 6 +++--- .../web/http/headers/x-frame-options/index.html | 2 +- files/en-us/web/http/index.html | 4 ++-- .../en-us/web/http/link_prefetching_faq/index.html | 2 +- files/en-us/web/http/methods/patch/index.html | 2 +- .../web/http/network_error_logging/index.html | 2 +- .../http/resources_and_specifications/index.html | 8 ++++---- files/en-us/web/http/status/506/index.html | 2 +- files/en-us/web/http/status/507/index.html | 2 +- files/en-us/web/http/status/510/index.html | 2 +- files/en-us/web/http/status/index.html | 4 ++-- .../errors/cyclic_object_value/index.html | 2 +- .../reference/global_objects/date/date/index.html | 4 ++-- .../global_objects/date/toutcstring/index.html | 2 +- .../reference/global_objects/encodeuri/index.html | 2 +- .../global_objects/encodeuricomponent/index.html | 2 +- .../reference/global_objects/intl/index.html | 2 +- .../global_objects/json/stringify/index.html | 2 +- .../web/media/formats/webrtc_codecs/index.html | 6 +++--- .../security/certificate_transparency/index.html | 2 +- files/en-us/web/svg/attribute/lang/index.html | 4 ++-- .../web/svg/attribute/systemlanguage/index.html | 2 +- .../web/svg/attribute/xml_colon_lang/index.html | 4 ++-- 147 files changed, 233 insertions(+), 233 deletions(-) diff --git a/files/en-us/glossary/base64/index.html b/files/en-us/glossary/base64/index.html index 0d48a1988989b13..e8ee6992dd25306 100644 --- a/files/en-us/glossary/base64/index.html +++ b/files/en-us/glossary/base64/index.html @@ -25,7 +25,7 @@
  • atob(): decodes a base64 encoded string("atob" should be read as "ASCII to binary").
    • -

    The algorithm used by atob() and btoa() is specified in RFC 4648, section 4.

    +

    The algorithm used by atob() and btoa() is specified in RFC 4648, section 4.

    Note that btoa() expects to be passed binary data, and will throw an exception if the given string contains any characters whose UTF-16 representation occupies more than one byte. For more details, see the documentation for btoa().

    diff --git a/files/en-us/glossary/cacheable/index.html b/files/en-us/glossary/cacheable/index.html index 3ea15cbfcfbe95d..fe5ac7b9933bce2 100644 --- a/files/en-us/glossary/cacheable/index.html +++ b/files/en-us/glossary/cacheable/index.html @@ -46,7 +46,7 @@
    1. General knowledge
        -
      1. Definition of cacheable in the HTTP specification.
        2. +
      2. Definition of cacheable in the HTTP specification.
    2. Technical knowledge diff --git a/files/en-us/glossary/caldav/index.html b/files/en-us/glossary/caldav/index.html index 6e6d62462107d2d..3e08d8633d66915 100644 --- a/files/en-us/glossary/caldav/index.html +++ b/files/en-us/glossary/caldav/index.html @@ -19,6 +19,6 @@

      General knowledge

      Technical reference

      diff --git a/files/en-us/glossary/carddav/index.html b/files/en-us/glossary/carddav/index.html index 6083c04ff30fa4f..b5f2c16265994b4 100644 --- a/files/en-us/glossary/carddav/index.html +++ b/files/en-us/glossary/carddav/index.html @@ -19,5 +19,5 @@

      General knowledge

      Technical reference

      diff --git a/files/en-us/glossary/client_hints/index.html b/files/en-us/glossary/client_hints/index.html index 3ced801b8cc5f92..c537e2970e791fc 100644 --- a/files/en-us/glossary/client_hints/index.html +++ b/files/en-us/glossary/client_hints/index.html @@ -10,7 +10,7 @@ ---

      Client Hints are a set of HTTP request header fields for proactive content negotiation allowing clients to indicate a list of device and agent specific preferences.

      -

      Use of client hints isn't automatic: rather, servers must announce that they support client hints. Servers announce support for Client Hints using the Accept-CH (accept client hints) header or an equivalent HTML meta element with the http-equiv attribute.

      +

      Use of client hints isn't automatic: rather, servers must announce that they support client hints. Servers announce support for Client Hints using the Accept-CH (accept client hints) header or an equivalent HTML meta element with the http-equiv attribute.

      Accept-CH: Width, Viewport-Width, Downlink

      diff --git a/files/en-us/glossary/dtls/index.html b/files/en-us/glossary/dtls/index.html index fb89bcb41cedae2..f704ac6e6d3c7d6 100644 --- a/files/en-us/glossary/dtls/index.html +++ b/files/en-us/glossary/dtls/index.html @@ -21,7 +21,7 @@

      Specifications

      diff --git a/files/en-us/glossary/entity_header/index.html b/files/en-us/glossary/entity_header/index.html index f4dfebbfa5318b7..fd8b09bd0ad1425 100644 --- a/files/en-us/glossary/entity_header/index.html +++ b/files/en-us/glossary/entity_header/index.html @@ -6,7 +6,7 @@ - WebMechanics ---
      -

      The current HTTP/1.1 specification no longer refers to entities, entity headers or entity-body. Some of the fields are now referred to as representation header fields (RFC 7231, section 3: Representations).

      +

      The current HTTP/1.1 specification no longer refers to entities, entity headers or entity-body. Some of the fields are now referred to as representation header fields (RFC 7231, section 3: Representations).

      An entity header is an {{glossary("header", "HTTP header")}} that describes the payload of an HTTP message (i.e. metadata about the message body). Entity headers include: {{HTTPHeader("Content-Length")}}, {{HTTPHeader("Content-Language")}}, {{HTTPHeader("Content-Encoding")}}, {{HTTPHeader("Content-Type")}}, {{HTTPHeader("Expires")}}, etc. Entity headers may be present in both HTTP request and response messages.

      diff --git a/files/en-us/glossary/hpkp/index.html b/files/en-us/glossary/hpkp/index.html index 1db568bda936cd6..4af22b9e5c6b645 100644 --- a/files/en-us/glossary/hpkp/index.html +++ b/files/en-us/glossary/hpkp/index.html @@ -12,6 +12,6 @@

      Learn more

      diff --git a/files/en-us/glossary/http_header/index.html b/files/en-us/glossary/http_header/index.html index 48690aa9aed39b0..7e397ca6d542236 100644 --- a/files/en-us/glossary/http_header/index.html +++ b/files/en-us/glossary/http_header/index.html @@ -58,7 +58,7 @@
      1. Specifications
          -
        1. Syntax of headers in the HTTP specification.
          2. +
        2. Syntax of headers in the HTTP specification.
      2. Technical Reference diff --git a/files/en-us/glossary/idempotent/index.html b/files/en-us/glossary/idempotent/index.html index d98dd2af4e844df..8dc98df27b593c8 100644 --- a/files/en-us/glossary/idempotent/index.html +++ b/files/en-us/glossary/idempotent/index.html @@ -37,7 +37,7 @@

        Learn more

        General knowledge

          -
        • Definition of idempotent in the HTTP specification.
          • +
        • Definition of idempotent in the HTTP specification.

        Technical knowledge

        diff --git a/files/en-us/glossary/nntp/index.html b/files/en-us/glossary/nntp/index.html index b3c32202f3081f9..80119d3e960bce6 100644 --- a/files/en-us/glossary/nntp/index.html +++ b/files/en-us/glossary/nntp/index.html @@ -18,5 +18,5 @@

        General knowledge

        Technical reference

        diff --git a/files/en-us/glossary/payload_body/index.html b/files/en-us/glossary/payload_body/index.html index bb332d683ba4ee9..685033cc4b20761 100644 --- a/files/en-us/glossary/payload_body/index.html +++ b/files/en-us/glossary/payload_body/index.html @@ -30,4 +30,4 @@ \r\n -

        For more information see RFC 7230, section 3.3: Message Body and RFC 7230, section 3.3.1: Transfer-Encoding.

        +

        For more information see RFC 7230, section 3.3: Message Body and RFC 7230, section 3.3.1: Transfer-Encoding.

        diff --git a/files/en-us/glossary/pop/index.html b/files/en-us/glossary/pop/index.html index d4c16e38a68924a..1386560b32e111a 100644 --- a/files/en-us/glossary/pop/index.html +++ b/files/en-us/glossary/pop/index.html @@ -13,9 +13,9 @@
      -

      The below status codes are defined by section 10 of RFC 2616. You can find an updated specification in RFC 7231.

      +

      The below status codes are defined by section 10 of RFC 2616. You can find an updated specification in RFC 7231.

      If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server's software.

      @@ -68,7 +68,7 @@

      Successful responses

      Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
      {{HTTPStatus(208, "208 Already Reported")}} ({{Glossary("WebDAV")}})
      Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
      -
      {{HTTPStatus(226, "226 IM Used")}} (HTTP Delta encoding)
      +
      {{HTTPStatus(226, "226 IM Used")}} (HTTP Delta encoding)
      The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
      diff --git a/files/en-us/web/javascript/reference/errors/cyclic_object_value/index.html b/files/en-us/web/javascript/reference/errors/cyclic_object_value/index.html index bf653efb9c602fd..a0738cdc68d8599 100644 --- a/files/en-us/web/javascript/reference/errors/cyclic_object_value/index.html +++ b/files/en-us/web/javascript/reference/errors/cyclic_object_value/index.html @@ -28,7 +28,7 @@

      What went wrong?

      The JSON format per se doesn't support object references (although an IETF draft + href="https://datatracker.ietf.org/doc/html/draft-pbryan-zyp-json-ref-03">IETF draft exists), hence {{jsxref("JSON.stringify()")}} doesn't try to solve them and fails accordingly.

      diff --git a/files/en-us/web/javascript/reference/global_objects/date/date/index.html b/files/en-us/web/javascript/reference/global_objects/date/date/index.html index 265e72e421f7289..50ef1ed229a31a1 100644 --- a/files/en-us/web/javascript/reference/global_objects/date/date/index.html +++ b/files/en-us/web/javascript/reference/global_objects/date/date/index.html @@ -67,7 +67,7 @@

      Timestamp string

      dateString
      A string value representing a date, specified in a format recognized by the {{jsxref("Date.parse()")}} method. (These formats are IETF-compliant RFC 2822 + href="https://datatracker.ietf.org/doc/html/rfc2822#page-14">IETF-compliant RFC 2822 timestamps, and also strings in a version of ISO8601.) @@ -78,7 +78,7 @@

      Timestamp string

        -
      • Support for RFC 2822 +
      • Support for RFC 2822 format strings is by convention only.
      • Support for ISO 8601 formats differs in that date-only strings (e.g. "1970-01-01") are treated as UTC, not local.
        • diff --git a/files/en-us/web/javascript/reference/global_objects/date/toutcstring/index.html b/files/en-us/web/javascript/reference/global_objects/date/toutcstring/index.html index 56f51d5c18bf479..3f42c337cdf28a1 100644 --- a/files/en-us/web/javascript/reference/global_objects/date/toutcstring/index.html +++ b/files/en-us/web/javascript/reference/global_objects/date/toutcstring/index.html @@ -13,7 +13,7 @@

        The toUTCString() method converts a date to a string, using the UTC time zone.

        -

        Based on rfc7231 and +

        Based on rfc7231 and modified according to ecma-262 toUTCString, it can have negative values in the Encoding a lone high surrogate th

        Encoding for IPv6

        If one wishes to follow the more recent RFC3986 for URLs, which makes square + href="https://datatracker.ietf.org/doc/html/rfc3986">RFC3986 for URLs, which makes square brackets reserved (for {{glossary("IPv6")}}) and thus not encoded when forming something which could be part of a URL (such as a host), the following code snippet may help:

        diff --git a/files/en-us/web/javascript/reference/global_objects/encodeuricomponent/index.html b/files/en-us/web/javascript/reference/global_objects/encodeuricomponent/index.html index 06ae744664cd1ac..7ff8c5eceabdd27 100644 --- a/files/en-us/web/javascript/reference/global_objects/encodeuricomponent/index.html +++ b/files/en-us/web/javascript/reference/global_objects/encodeuricomponent/index.html @@ -94,7 +94,7 @@

        Description

        For application/x-www-form-urlencoded, spaces are to be replaced by +, so one may wish to follow a encodeURIComponent() replacement with an additional replacement of %20 with +.

        -

        To be more stringent in adhering to RFC 3986 (which reserves !, ', (, ), +

        To be more stringent in adhering to RFC 3986 (which reserves !, ', (, ), and *), even though these characters have no formalized URI delimiting uses, the following can be safely used:

        diff --git a/files/en-us/web/javascript/reference/global_objects/intl/index.html b/files/en-us/web/javascript/reference/global_objects/intl/index.html index 35198ee0b7c7ed1..7652aaec8fcb6ab 100644 --- a/files/en-us/web/javascript/reference/global_objects/intl/index.html +++ b/files/en-us/web/javascript/reference/global_objects/intl/index.html @@ -96,7 +96,7 @@

        locales argument

        Locale negotiation

        -

        The list of locales specified by the locales argument, after Unicode extensions have been removed from them, is interpreted as a prioritized request from the application. The runtime compares it against the locales it has available and picks the best one available. Two matching algorithms exist: the "lookup" matcher follows the Lookup algorithm specified in BCP 47; the "best fit" matcher lets the runtime provide a locale that's at least, but possibly more, suited for the request than the result of the Lookup algorithm. If the application doesn't provide a locales argument, or the runtime doesn't have a locale that matches the request, then the runtime's default locale is used. The matcher can be selected using a property of the options argument (see below).

        +

        The list of locales specified by the locales argument, after Unicode extensions have been removed from them, is interpreted as a prioritized request from the application. The runtime compares it against the locales it has available and picks the best one available. Two matching algorithms exist: the "lookup" matcher follows the Lookup algorithm specified in BCP 47; the "best fit" matcher lets the runtime provide a locale that's at least, but possibly more, suited for the request than the result of the Lookup algorithm. If the application doesn't provide a locales argument, or the runtime doesn't have a locale that matches the request, then the runtime's default locale is used. The matcher can be selected using a property of the options argument (see below).

        If the selected locale identifier had a Unicode extension sequence, that extension is now used to customize the constructed object or the behavior of the function. Each constructor or function supports only a subset of the keys defined for the Unicode extension, and the supported values often depend on the locale identifier. For example, the "co" key (collation) is only supported by {{jsxref("Collator")}}, and its "phonebk" value is only supported for German.

        diff --git a/files/en-us/web/javascript/reference/global_objects/json/stringify/index.html b/files/en-us/web/javascript/reference/global_objects/json/stringify/index.html index 95c9662c803aa8a..ef0f9fd0a370a1d 100644 --- a/files/en-us/web/javascript/reference/global_objects/json/stringify/index.html +++ b/files/en-us/web/javascript/reference/global_objects/json/stringify/index.html @@ -289,7 +289,7 @@

        Issue wi

        Note that since the JSON format doesn't support object references (although an IETF draft + href="https://datatracker.ietf.org/doc/html/draft-pbryan-zyp-json-ref-03">IETF draft exists), a {{JSxRef("TypeError")}} will be thrown if one attempts to encode an object with circular references.

        diff --git a/files/en-us/web/media/formats/webrtc_codecs/index.html b/files/en-us/web/media/formats/webrtc_codecs/index.html index c86b3bad68a3975..7c3874a35294b7e 100644 --- a/files/en-us/web/media/formats/webrtc_codecs/index.html +++ b/files/en-us/web/media/formats/webrtc_codecs/index.html @@ -116,11 +116,11 @@

        Parameters which are usefu
        max-br
        -
        If specified and supported by the software, the max-br parameter specifies the maximum video bit rate in units of 1,000 bps for VCL and 1,200 bps for NAL. You'll find details about this on page 47 of RFC 6184.
        +
        If specified and supported by the software, the max-br parameter specifies the maximum video bit rate in units of 1,000 bps for VCL and 1,200 bps for NAL. You'll find details about this on page 47 of RFC 6184.
        max-cpb
        -
        If specified and supported by the software, max-cpb specifies the maximum coded picture buffer size. This is a fairly complicated parameter whose unit size can vary. See page 45 of RFC 6184 for details.
        +
        If specified and supported by the software, max-cpb specifies the maximum coded picture buffer size. This is a fairly complicated parameter whose unit size can vary. See page 45 of RFC 6184 for details.
        max-dpb
        -
        If specified and supported, max-dpb indicates the maximum decoded picture buffer size, given in units of 8/3 macroblocks. See RFC 6184, page 46 for further details.
        +
        If specified and supported, max-dpb indicates the maximum decoded picture buffer size, given in units of 8/3 macroblocks. See RFC 6184, page 46 for further details.
        max-fs
        If specified and supported by the software, max-fs specifies the maximum size of a single video frame, given as a number of macroblocks.
        max-mbps
        diff --git a/files/en-us/web/security/certificate_transparency/index.html b/files/en-us/web/security/certificate_transparency/index.html index a4e49b3eac4ae8a..c545fd5651ef64f 100644 --- a/files/en-us/web/security/certificate_transparency/index.html +++ b/files/en-us/web/security/certificate_transparency/index.html @@ -53,7 +53,7 @@

        Specifications

        Comment - Certificate Transparency + Certificate Transparency IETF RFC diff --git a/files/en-us/web/svg/attribute/lang/index.html b/files/en-us/web/svg/attribute/lang/index.html index f737d8d9b408b61..305713d23892c18 100644 --- a/files/en-us/web/svg/attribute/lang/index.html +++ b/files/en-us/web/svg/attribute/lang/index.html @@ -43,7 +43,7 @@

        Usage notes

        <language-tag>
        -

        This value specifies the language used for the element. The syntax of this value is defined in the BCP 47 specification.

        +

        This value specifies the language used for the element. The syntax of this value is defined in the BCP 47 specification.

        The most common syntax is a value formed by a lowercase two-character part for the language and an uppercase two-character part for the region or country, separated by a minus sign, e.g. en-US for US English or de-AT for Austrian German.

        @@ -80,5 +80,5 @@

        Browser compatibility

        See also

        diff --git a/files/en-us/web/svg/attribute/systemlanguage/index.html b/files/en-us/web/svg/attribute/systemlanguage/index.html index 45c7179e2d2f9d6..3e8add64e55085b 100644 --- a/files/en-us/web/svg/attribute/systemlanguage/index.html +++ b/files/en-us/web/svg/attribute/systemlanguage/index.html @@ -32,7 +32,7 @@

        Usage notes

        <language-tags>
        -
        The value is a set of comma-separated tokens, each of which must be a Language-Tag value, as defined in BCP 47.
        +
        The value is a set of comma-separated tokens, each of which must be a Language-Tag value, as defined in BCP 47.

        systemLanguage is often used in conjunction with the {{SVGElement("switch")}} element. If the attribute is used in other situations, then it represents a simple switch on the given element whether to render the element or not.

        diff --git a/files/en-us/web/svg/attribute/xml_colon_lang/index.html b/files/en-us/web/svg/attribute/xml_colon_lang/index.html index b9193f0e4726536..e8e7f2943a2598d 100644 --- a/files/en-us/web/svg/attribute/xml_colon_lang/index.html +++ b/files/en-us/web/svg/attribute/xml_colon_lang/index.html @@ -43,7 +43,7 @@

        Usage notes

        <language-tag>
        -

        This value specifies the language used for the element. The syntax of this value is defined in the BCP 47 specification.

        +

        This value specifies the language used for the element. The syntax of this value is defined in the BCP 47 specification.

        The most common syntax is a value formed by a lowercase two-character part for the language and an uppercase two-character part for the region or country, separated by a minus sign, e.g. en-US for US English or de-AT for Austrian German.

        @@ -81,5 +81,5 @@

        See also