Skip to content

Fix a few typos (its, incompatibilities) #1164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xatapult merged 1 commit into from
Jan 12, 2026
Merged

Fix a few typos (its, incompatibilities) #1164

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions xproc/src/main/xml/specification.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,7 @@ document has no base URI.</para>
</term>
<listitem>
<para>The value of the (optional) “<code>serialization</code>” property holds serialization
properties for the document. If present, it’s value <rfc2119>must</rfc2119> be of type
properties for the document. If present, its value <rfc2119>must</rfc2119> be of type
<type>map(xs:QName, item()*)</type>. <error code="D0070">It is a <glossterm>dynamic
error</glossterm> if a value is assigned to the <code>serialization</code>
document property that cannot be converted into <type>map(xs:QName, item()*)</type> according
Expand Down Expand Up @@ -1134,7 +1134,7 @@ or in either order.
<listitem>
<para>Step5 is connected to Step3 because it reads from the output of Step3. It is also
transitively connected to Step2 and the connections that Step2 has. Step5 is also connected
to Step4 because it’s option “<literal>option1</literal>” is connected to “<literal>someVar</literal>”
to Step4 because its option “<literal>option1</literal>” is connected to “<literal>someVar</literal>”
which is connected to “<literal>ecount</literal>” which reads its context from Step4.
</para>
</listitem>
Expand Down Expand Up @@ -3426,7 +3426,7 @@ is “3.1”.</para>
<title>A pragmatic approach to 3.0 and 3.1</title>
<para>In practice, implementations are expected to treat version “3.0”
as a synonym for version “3.1”. Although there are technically a few
backwards incompatiblities between 3.1 and 3.0, all known processors
backwards incompatibilities between 3.1 and 3.0, all known processors
<emphasis>have always</emphasis> implemented the behavior now defined
in 3.1, so it is of no consequence.</para>
<para>Requiring processors to reject pipelines labeled “3.0” would be
Expand Down Expand Up @@ -4126,7 +4126,7 @@ execution time of a step is measured.</impl>
<title>Status and debugging output</title>

<para xml:id="p.message">The <tag class="attribute">[p:]message</tag>
attribute can appear on any step invocation. It’s value is treated
attribute can appear on any step invocation. Its value is treated
as an attribute value template (irrespective of any enclosing
<tag class="attribute">[p:]expand-text</tag> setting) and the
computed value is made available.</para>
Expand Down
Loading