reword URI path interop note to be more neutral

zenomt · Jul 20, 2023 · ad94625 · ad94625
1 parent 3cc912c
commit ad94625
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
diff --git a/rtmp-errata-addenda.html b/rtmp-errata-addenda.html
@@ -1222,7 +1222,7 @@
 <dl id="identifiers">
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-07-16" class="published">16 July 2023</time>
+<time datetime="2023-07-19" class="published">19 July 2023</time>
     </dd>
 <dt class="label-authors">Author:</dt>
 <dd class="authors">
@@ -1862,10 +1862,10 @@ <h4 id="name-tcurl-2">
 namespace.<a href="#section-7.1.2-1" class="pilcrow">¶</a></p>
 <p id="section-7.1.2-2">The meaning of "target resource" is implementation specific and is reserved
 for the server.<a href="#section-7.1.2-2" class="pilcrow">¶</a></p>
-<p id="section-7.1.2-3">Interoperability Note: Some legacy client implementations improperly presume
+<p id="section-7.1.2-3">Interoperability Note: Some legacy client implementations incorrectly presume
 the server's interpretation of the <code>path</code> component of the URI,
 specifically by presuming the number of path segments that identify the target
-resource and setting <code>tcUrl</code> accordingly.  They then improperly interpret
+resource and setting <code>tcUrl</code> accordingly.  They then incorrectly interpret
 the remaining path segments of the original URI as identifying a secondary
 resource (such the name of a stream to play or publish via the connection to
 the target resource).  This behavior is not in keeping with the spirit of

diff --git a/rtmp-errata-addenda.txt b/rtmp-errata-addenda.txt
@@ -3,7 +3,7 @@
 
 
                                                            M. Thornburgh
-                                                            16 July 2023
+                                                            19 July 2023
 
 
                         RTMP Errata and Addenda
@@ -630,11 +630,11 @@ Thornburgh                    Informational                    [Page 11]
    The meaning of "target resource" is implementation specific and is
    reserved for the server.
 
-   Interoperability Note: Some legacy client implementations improperly
+   Interoperability Note: Some legacy client implementations incorrectly
    presume the server's interpretation of the path component of the URI,
    specifically by presuming the number of path segments that identify
    the target resource and setting tcUrl accordingly.  They then
-   improperly interpret the remaining path segments of the original URI
+   incorrectly interpret the remaining path segments of the original URI
    as identifying a secondary resource (such the name of a stream to
    play or publish via the connection to the target resource).  This
    behavior is not in keeping with the spirit of generic URIs

diff --git a/rtmp-errata-addenda.xml b/rtmp-errata-addenda.xml
@@ -577,10 +577,10 @@ namespace.</t>
 <t>The meaning of "target resource" is implementation specific and is reserved
 for the server.</t>
 
-<t>Interoperability Note: Some legacy client implementations improperly presume
+<t>Interoperability Note: Some legacy client implementations incorrectly presume
 the server's interpretation of the <tt>path</tt> component of the URI,
 specifically by presuming the number of path segments that identify the target
-resource and setting <tt>tcUrl</tt> accordingly.  They then improperly interpret
+resource and setting <tt>tcUrl</tt> accordingly.  They then incorrectly interpret
 the remaining path segments of the original URI as identifying a secondary
 resource (such the name of a stream to play or publish via the connection to
 the target resource).  This behavior is not in keeping with the spirit of

diff --git a/rtmp-uris.md b/rtmp-uris.md
@@ -141,10 +141,10 @@ The `path-abempty` and `query` components identify the abstract
 _target resource_ within the origin server’s namespace. The meaning of "target
 resource" is implementation-specific and is reserved for the origin server.
 
-Interoperability Note: Some legacy client implementations improperly presume
+Interoperability Note: Some legacy client implementations incorrectly presume
 the server’s interpretation of the `path-abempty` component of the URI,
 specifically by presuming the number of path segments that identify the target
-resource. They then improperly interpret the remaining path segments of the
+resource. They then incorrectly interpret the remaining path segments of the
 original URI as identifying a secondary resource (such the name of a stream
 to play or publish via the connection to the target resource).  This behavior
 is not in keeping with the spirit of generic URIs (particularly that the