diff --git a/specification/archSpec/base/conref-attributes-specified-on-elements.dita b/specification/archSpec/base/conref-attributes-specified-on-elements.dita
index 4b0a21b4..312c5b45 100644
--- a/specification/archSpec/base/conref-attributes-specified-on-elements.dita
+++ b/specification/archSpec/base/conref-attributes-specified-on-elements.dita
@@ -52,7 +52,7 @@
    originating context, even if they are not valid in an intermediate context. </p>
   <p otherprops="examples">For example, if topic A and topic C allow highlighting, and topic B does
       not, then a content reference chain of topic A-to-topic B-to-topic C should preserve any
-      highlighting elements in the referenced content. The result, however it is achieved, must be
+      highlighting elements in the referenced content. The result, however it is achieved, is
       equivalent to the result of resolving the conref pairs recursively starting from the original
       referencing element in topic A.</p>
  </conbody>
diff --git a/specification/archSpec/base/conref-overview.dita b/specification/archSpec/base/conref-overview.dita
index 4eee8b61..32df80c9 100644
--- a/specification/archSpec/base/conref-overview.dita
+++ b/specification/archSpec/base/conref-overview.dita
@@ -35,19 +35,18 @@
         <dt>Pushing content from the referencing element</dt>
         <dd>
           <p>The <xmlatt>conaction</xmlatt> attribute reverses the direction of reuse from pull to
-            push. <ph >With a push, the referencing element is rendered before,
-              after, or in place of the referenced element. The location (before, after, or in place
-              of) is determined by the value of the <xmlatt>conaction</xmlatt> attribute.</ph>
-            Because the <xmlatt>conaction</xmlatt> and <xmlatt>conrefend</xmlatt> attributes cannot
-            both be used within the same referencing element, it is not possible to push a range of
-            elements.</p>
+            push. With a push, the referencing element is rendered before, after, or in place of the
+            referenced element. The location (before, after, or in place of) is determined by the
+            value of the <xmlatt>conaction</xmlatt> attribute. The <xmlatt>conaction</xmlatt> and
+              <xmlatt>conrefend</xmlatt> attributes cannot both be used within the same referencing
+            element, so it is not possible to push a range of elements.</p>
         </dd>
       </dlentry>
     </dl>
     <p>A fragment of DITA content, such as an XML document that contains only a single paragraph
-      without a topic ancestor, does not contain enough information for the conref processor to be
-      able to determine the validity of a reference to it. Consequently, the value of a conref must
-      specify one of the following items:</p>
+      without a topic ancestor, does not contain enough information for a conref processor to be
+      able to determine the validity of a reference to it. Consequently, the value of a
+        <xmlatt>conref</xmlatt> attribute must be one of the following items:</p>
     <ul>
       <li>A referenced element within a DITA map</li>
       <li>A referenced element within a DITA topic</li>
diff --git a/specification/archSpec/base/conref-processing.dita b/specification/archSpec/base/conref-processing.dita
index c5136f79..98c089c5 100644
--- a/specification/archSpec/base/conref-processing.dita
+++ b/specification/archSpec/base/conref-processing.dita
@@ -19,10 +19,10 @@
  </prolog>
  <conbody>
   <note>The DITA <xmlatt>conref</xmlatt> attribute is a transclusion mechanism similar to XInclude
-   and to HyTime value references. DITA differs from these mechanisms, however, in that conref
-   validity does not apply simply to the current content at the time of replacement, but to the
-   possible content given the restrictions of both the referencing document type and the referenced
-   document type.</note>
+      and to HyTime value references. DITA differs from these mechanisms, however, in that conref
+      validity does not apply simply to the current content at the time of replacement, but to the
+      possible resolved content given the restrictions of both the referencing document type and the
+      referenced document type.</note>
    <p>When content is reused between two documents with different domains or constraints, it is
       possible for the reused content to include domain extensions that are not defined for the new
       context, or to include elements that would be constrained out of the new context. When pulling
@@ -33,5 +33,59 @@
   <p>A conref processor <term outputclass="RFC-2119">SHOULD NOT</term> permit resolution of a reuse
       relationship that could be rendered invalid under the rules of either the reused or reusing
       content.</p>
+    <p>When resolving <xmlatt>conkeyref</xmlatt> attributes, processors <term outputclass="RFC-2119"
+        >SHOULD</term> issue a warning when a <xmlatt>conkeyref</xmlatt> reference cannot be
+      resolved and there is no <xmlatt>conref</xmlatt> attribute to use as a fallback. Processors
+        <term outputclass="RFC-2119">MAY</term> issue a warning when a <xmlatt>conkeyref</xmlatt>
+      cannot be resolved to an element and a specified <xmlatt>conref</xmlatt> is used as a
+      fallback.</p>
+    <section id="error-conditions" outputclass="errorcondition">
+      <title>Common error conditions related to conref ranges</title>
+      <p>When encountering the following error conditions, an implementation can optionally issue an
+        error message.</p>
+      <table id="table_pbn_czf_scc">
+        <tgroup cols="2">
+          <colspec colname="col1" colnum="1" colwidth="1*"/>
+          <colspec colname="col2" colnum="2" colwidth="1*"/>
+          <thead>
+            <row>
+              <entry colname="col1">Condition or Issue</entry>
+              <entry colname="col2">Result</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry colname="col1">The <xmlatt>conref</xmlatt> attribute cannot be resolved in the
+                target document (the target element might have been removed or its id has changed). </entry>
+              <entry colname="col2">The <xmlatt>conref</xmlatt> is ignored.</entry>
+            </row>
+            <row>
+              <entry colname="col1">The <xmlatt>conrefend</xmlatt> attribute cannot be resolved in
+                the target document (the target element might have been removed or its id has
+                changed).</entry>
+              <entry colname="col2">Range cannot be resolved, optional recovery processes the result
+                as a simple conref.</entry>
+            </row>
+            <row>
+              <entry colname="col1">Start and end elements are not siblings in the target
+                document.</entry>
+              <entry colname="col2">If the start element exists, optional recovery processes the
+                result as a simple conref. </entry>
+            </row>
+            <row>
+              <entry colname="col1">End element occurs before the start element in the target
+                document.</entry>
+              <entry colname="col2">If the start element exists, optional recovery processes the
+                result as a simple conref.</entry>
+            </row>
+            <row>
+              <entry colname="col1">An element has a <xmlatt>conrefend</xmlatt> attribute but is
+                missing the <xmlatt>conref</xmlatt> attribute.</entry>
+              <entry colname="col2">No result.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
  </conbody>
 </concept>
diff --git a/specification/archSpec/base/conref.dita b/specification/archSpec/base/conref.dita
index e510740b..f11d3ae8 100644
--- a/specification/archSpec/base/conref.dita
+++ b/specification/archSpec/base/conref.dita
@@ -2,10 +2,10 @@
 <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
 <concept id="conref" xml:lang="en-us">
  <title>Content <ph >reference</ph> (conref)</title>
- <shortdesc >The DITA conref attributes provide mechanisms for reusing content.
-  DITA content references support reuse scenarios that are difficult or impossible to implement
-  using other XML-based inclusion mechanisms like XInclude and entities. Additionally, DITA content
-  references have rules that help ensure that the results of content inclusion remain valid after
+ <shortdesc>The DITA conref attributes provide mechanisms for reusing content. DITA content
+  references support reuse scenarios that are difficult or impossible to implement using many
+  XML-based inclusion mechanisms like XInclude and entities. Additionally, DITA content references
+  have rules that help ensure that the results of content inclusion remain valid after
   resolution</shortdesc>
  <prolog>
   <metadata>
diff --git a/specification/archSpec/base/conref.ditamap b/specification/archSpec/base/conref.ditamap
index 3ace888e..0c1bfef3 100644
--- a/specification/archSpec/base/conref.ditamap
+++ b/specification/archSpec/base/conref.ditamap
@@ -4,14 +4,26 @@
  <title>Content reference (conref)</title>
  <topicref href="conref.dita" keys="conref">
     <topicref href="conref-overview.dita"/>
+  <topicref keyref="attributes-conref"/>
+  <topicref keyref="attributes-conkeyref"/>
+  <topicref keyref="attributes-conrefend"/>
     <topicref keyref="attributes-conaction"/>
-    <topicref keyref="attributes-conrefend"/>
-    <topicref keyref="attributes-conkeyref"/>
-    <topicref keyref="attributes-conref"/>
     <topicref keyref="attributes-useconreftarget"/>
     <topicref href="conref-processing.dita"/>
     <topicref href="conref-attributes-specified-on-elements.dita"/>
     <topicref href="handling-xref-and-conref-within-topics.dita"/>
+  <topicref href="examples-conref.dita">
+   <topicref href="example-conref-simple.dita"/>
+   <topicref href="example-conref-conkeyref.dita"/>
+   <topicref href="example-conref-range-list.dita"/>
+   <topicref href="example-conref-range-blocks.dita"/>
+   <topicref href="example-conref-range-conkeyref.dita"/>
+   <topicref href="example-conref-conaction-replace.dita"/>
+   <topicref href="example-conref-conaction-pushbefore.dita"/>
+   <topicref href="example-conref-conaction-pushafter.dita"/>
+   <topicref href="example-conref-includes-xref.dita"/>
+   <topicref href="example-conref-includes-xref-and-keyscope.dita"/>
+  </topicref>
   </topicref>
  <reltable title="Source&lt;-->Target">
   <relheader>
diff --git a/specification/archSpec/base/handling-xref-and-conref-within-topics.dita b/specification/archSpec/base/handling-xref-and-conref-within-topics.dita
index 744270fd..39f3a787 100644
--- a/specification/archSpec/base/handling-xref-and-conref-within-topics.dita
+++ b/specification/archSpec/base/handling-xref-and-conref-within-topics.dita
@@ -62,109 +62,8 @@
       same-topic fragment identifier is resolved in the context of the topic that contains the
       content reference, and a key reference is resolved in the context of the key scope that is in
       effect for each use of the topic that contains the content reference. </p>
-    <note>In the case of same-topic fragment identifiers, it is the responsibility of the author of
-      the content reference to ensure that any element IDs that are specified in same-topic fragment
-      identifiers in the referenced content will also be available in the referencing topic at
-      resolution time.</note>
-  <example id="example" otherprops="examples">
-      <title>Example: Resolving conrefs to elements that contain cross references</title>
-      <p>Consider the following paragraphs in <filepath>paras-01.dita</filepath> that are intended
-        to be used by reference from other topics:</p>
-      <codeblock>&lt;topic id="paras-01">&lt;title>Reusable paragraphs&lt;/title>
-    &lt;body>
-        &lt;p id="p1">See &lt;xref href="#paras-01/p5"/>.&lt;/p>
-        &lt;p id="p2">See &lt;xref href="topic-02.dita#topic02/fig-01"/>.&lt;/p>
-        &lt;p id="p3">See &lt;xref href="#./p5"/>.&lt;/p>
-        &lt;p id="p4">See &lt;xref keyref="task-remove-cover"/>.&lt;/p>
-        &lt;p id="p5">Paragraph 5 in paras-01.&lt;/p>
-    &lt;/body>
-&lt;/topic></codeblock>
-      <p>The paragraphs are used by content reference from other topics, including the
-          <filepath>using-topic-01.dita</filepath> topic:</p>
-      <codeblock>&lt;topic id="using-topic-01">&lt;title>Using topic one&lt;/title>
-    &lt;body>
-        &lt;p id="A" conref="paras-01.dita#paras-01/p1"/> 
-        &lt;p id="B" conref="paras-01.dita#paras-01/p2"/> 
-        &lt;p id="C" conref="paras-01.dita#paras-01/p3"/>
-        &lt;p id="D" conref="paras-01.dita#paras-01/p4"/>
-        &lt;p id="p5">Paragraph 5 in using-topic-01&lt;/p>  
-    &lt;/body>
-&lt;/topic></codeblock>
-      <p>Following resolution of the content references and processing of the
-          <xmlelement>xref</xmlelement> elements in the referenced paragraphs, the rendered cross
-        references in <filepath>using-topic-01.dita</filepath> are <ph >shown
-          in the following table</ph>.</p>
-      <simpletable frame="all" relcolwidth="1.0* 1.0* 2.0* 3.0*">
-        <sthead>
-          <stentry>Paragraph</stentry>
-          <stentry>Value of <xmlatt>id</xmlatt> attribute on conrefed paragraph</stentry>
-          <stentry><xmlelement>xref</xmlelement> within conrefed paragraph</stentry>
-          <stentry>Resolution</stentry>
-        </sthead>
-        <strow>
-          <stentry>A</stentry>
-          <stentry>p1</stentry>
-          <stentry><codeph>&lt;xref href="#paras-01/p5"/></codeph></stentry>
-          <stentry>The cross reference in paragraph p1 is a direct URI reference that does not
-            contain a same-topic fragment identifier. It can be resolved only to paragraph p5 in
-              <filepath>paras-01.dita</filepath>, which contains the content "Paragraph 5 in
-            paras-01".</stentry>
-        </strow>
-        <strow>
-          <stentry>B</stentry>
-          <stentry>p2</stentry>
-          <stentry><codeph>&lt;xref href="topic-02.dita#topic02/fig-01"/></codeph></stentry>
-          <stentry>The cross reference in paragraph p2 is a direct URI reference. It can be resolved
-            only to the element with <codeph>id="fig-01"</codeph> in
-              <filepath>topic-02.dita</filepath>.</stentry>
-        </strow>
-        <strow>
-          <stentry>C</stentry>
-          <stentry>p3</stentry>
-          <stentry><codeph>&lt;xref href="#./p5"/></codeph></stentry>
-          <stentry>
-            <p>The cross reference in paragraph p3  is a direct URI reference that contains a
-              same-topic fragment identifier.  Because the URI reference contains a same-topic
-              fragment identifier, the reference is resolved in the context of the referencing topic
-                (<filepath>using-topic-01.dita</filepath>). </p>
-            <p>If <filepath>using-topic-01.dita</filepath> did not contain an element with
-                <codeph>id="p5"</codeph>, then the conref to paragraph p3 would result in a link
-              resolution failure.</p>
-          </stentry>
-        </strow>
-        <strow>
-          <stentry>D</stentry>
-          <stentry>p4</stentry>
-          <stentry><codeph>&lt;xref keyref="task-remove-cover"/></codeph></stentry>
-          <stentry>The cross reference in paragraph p4 is a key reference. It is resolved to
-            whatever resource is bound to the key name "task-remove-cover" in the applicable map
-            context.</stentry>
-        </strow>
-      </simpletable>
-    </example>
-    <example id="example-w-scoped-keys" otherprops="examples">
-      <title>Example: Resolving conrefs to elements that contain key-based cross references </title>
-      <p >Consider the following map, which uses the topics from the previous
-        example:</p>
-      <codeblock>&lt;map>
-  &lt;topicgroup keyscope="product-1">
-    &lt;topicref keys="task-remove-cover" href="prod-1-task-remove-cover.dita"/>
-    &lt;topicref href="using-topic-01.dita"/>
-  &lt;/topicgroup>
-  &lt;topicgroup keyscope="product-2">
-    &lt;topicref keys="task-remove-cover" href="prod-2-task-remove-cover.dita"/>
-    &lt;topicref href="using-topic-01.dita"/>
-  &lt;/topicgroup>
-&lt;/map></codeblock>
-      <p>The map establishes two key scopes: "product-1" and "product-2". Within the map branches,
-        the key name "task-remove-cover" is bound to a different topic. The topic
-          <filepath>using-topic-01.dita</filepath>, which includes a conref to a paragraph that
-        includes a cross reference to the key name "task-remove-cover", is also referenced in each
-        branch. When each branch is rendered, the target of the cross reference is different.</p>
-      <p>In the first branch with the key scope set to "product-1", the cross reference from
-        paragraph p4 is resolved to <filepath>prod-1-task-remove-cover.dita</filepath>. In the
-        second branch with the key scope set to "product-2", the cross reference from paragraph p4
-        is resolved to <filepath>prod-2-task-remove-cover.dita</filepath>.</p>
-    </example>
+    <note>In the case of same-topic fragment identifiers, the author of the content reference needs
+      to ensure that any element IDs that are specified in same-topic fragment identifiers in the
+      referenced content will also be available in the referencing topic at resolution time.</note>
  </conbody>
 </concept>
diff --git a/specification/archSpec/base/theconactionattribute.dita b/specification/archSpec/base/theconactionattribute.dita
index 216319fb..0b11ef69 100644
--- a/specification/archSpec/base/theconactionattribute.dita
+++ b/specification/archSpec/base/theconactionattribute.dita
@@ -3,12 +3,10 @@
  "reference.dtd">
 <reference id="theconactionattribute" xml:lang="en-us">
 <title>The <xmlatt>conaction</xmlatt> attribute</title>
-<shortdesc>The <xmlatt>conaction</xmlatt> attribute allows users to push
-    content from one topic into another. It causes the
-      <xmlatt>conref</xmlatt> attribute to work in reverse, so that the
-    content is pushed from the current topic into another, rather than
-    pulled from another topic into the current
-    one.<!-- Allowable values for <xmlatt>conaction</xmlatt> are: <keyword>pushafter</keyword>, <keyword>pushbefore</keyword>, <keyword>pushreplace</keyword>, mark<keyword/>, and <keyword>-dita-use-conref-target</keyword>.--></shortdesc>
+<shortdesc>The <xmlatt>conaction</xmlatt> attribute allows users to push content from one location
+    into another. It causes the <xmlatt>conref</xmlatt> attribute to work in reverse, so that
+    content is pushed from the referencing element into another location, rather than pulled from
+    another location to replace the referencing element.</shortdesc>
   <prolog>
     <metadata>
       <keywords>
@@ -17,12 +15,6 @@
     </metadata>
   </prolog>
 <refbody>
-    <section>
-      <draft-comment author="robander" time="19 May 2021">This topic is moving into the arch spec,
-        but needs further editing to split overview / conceptual info from processing info; this and
-        other conref-attribute topics currently have a bunch of processing info that is missing from
-        the actual "Processing conref" arch spec topics.</draft-comment>
-    </section>
 <section id="section-1"><note>In the descriptions below, the word <i>target</i> always refers to the element referenced by a
           <xmlatt>conref</xmlatt> attribute.</note><p>There are three possible functions using the <xmlatt>conaction</xmlatt> attribute: replacing an
         element, pushing content before an element, and pushing content after an element. The
@@ -48,45 +40,9 @@
 <section id="replacing-content">
       <title>Replacing content in another topic</title>
       <p>When the <xmlatt>conaction</xmlatt> attribute is set to <keyword>pushreplace</keyword>, the
-        source element will replace the target specified on the <xmlatt>conref</xmlatt> attribute.
-        The pushed content remains in the source topic where it was originally authored.</p>
-      <p>For example, assume that a task in <filepath>example.dita</filepath> has the
-          <xmlatt>id</xmlatt> set to example<keyword/>, and it contains a
-          <xmlelement>step</xmlelement> element with the <xmlatt>id</xmlatt> set to
-          <keyword>b</keyword>:</p>
-      <codeblock id="codeblock_scr_wqh_psb">&lt;task id="example" xml:lang="en">
-  &lt;title>Example topic&lt;/title>
-  &lt;taskbody>
-    &lt;steps>
-      &lt;step id="a">&lt;cmd>A&lt;/cmd>&lt;/step>
-      &lt;step id="b">&lt;cmd>B&lt;/cmd>&lt;/step>
-      &lt;step id="c">&lt;cmd>C&lt;/cmd>&lt;/step>
-    &lt;/steps>
-  &lt;/taskbody>
-&lt;/task></codeblock>
-      <p>In order to replace the step with <codeph>id="b"</codeph>, another topic must combine a
-          <xmlatt>conaction</xmlatt> value of <keyword>pushreplace</keyword> with a
-          <xmlatt>conref</xmlatt> attribute that references this
-        <xmlelement>step</xmlelement>:<codeblock>&lt;!-- Steps element within another task -->
-&lt;steps>
-  &lt;step conaction="pushreplace" 
-        conref="example.dita#example/b">
-    &lt;cmd>Updated B&lt;/cmd>
-  &lt;/step>
-&lt;/steps>
-&lt;/task></codeblock></p>
-      <p>The result will be an updated version of <filepath>example.dita</filepath> which contains
-        the pushed
-        <xmlelement>step</xmlelement>:<codeblock>&lt;task id="example" xml:lang="en">
-  &lt;title>Example topic&lt;/title>
-  &lt;taskbody>
-    &lt;steps>
-      &lt;step id="a">&lt;cmd>A&lt;/cmd>&lt;/step>
-      &lt;step id="b">&lt;cmd>Updated B&lt;/cmd>&lt;/step>
-      &lt;step id="c">&lt;cmd>C&lt;/cmd>&lt;/step>
-    &lt;/steps>
-  &lt;/taskbody>
-&lt;/task></codeblock></p>
+        referencing element will replace the referenced element specified by the
+          <xmlatt>conref</xmlatt> attribute. The pushed content remains in the source topic where it
+        was originally authored.</p>
       <p>When resolving a conref push action, attributes are resolved using the same precedence as
         for normal <xmlatt>conref</xmlatt>, with one exception. Attributes on the element with the
           <xmlatt>conref</xmlatt> attribute (in this case, the source doing the push) will take
@@ -103,97 +59,50 @@
         element to be pushed before the element referenced by the <xmlatt>conref</xmlatt> attribute.
         Likewise, setting the <xmlatt>conaction</xmlatt> attribute to <keyword>pushafter</keyword>
         allows an element to be pushed after the element referenced by the <xmlatt>conref</xmlatt>
-        attribute. Multiple sources can push content before or after the same target; the order in
-        which that content is pushed is undefined.</p>
-      <p>When an element is pushed before or after a target, the resulting document will have at
-        least two of that element. Because this is not always valid, a document attempting to push
-        content before or after a target must take an extra step to ensure that the result will be
-        valid. The extra step makes use of the <codeph>conaction="mark"</codeph> value.</p>
+        attribute. Multiple sources can push content before or after the same referenced element;
+        the order in which that content is pushed is undefined.</p>
+      <p>When an element is pushed before or after a referenced element, the resulting document will
+        have at least two of that element. Because this is not always valid, a document attempting
+        to push content before or after a target must take an extra step to ensure that the result
+        will be valid. The extra step makes use of the <codeph>conaction="mark"</codeph> value. For
+        example, this restriction prevents a topic from trying to push a
+          <xmlelement>body</xmlelement> element before or after another
+          <xmlelement>body</xmlelement> element, because it is not valid to have two body elements
+        in sequence.</p>
       <p>When pushing before, the <xmlatt>conref</xmlatt> attribute itself looks just as it did when
-        replacing, but the <xmlatt>conaction</xmlatt> attribute is set to mark<keyword/> because it
-        is marking the target element. This element remains empty; its purpose is to ensure that it
-        is legal to have more than one of the current element. Immediately before the element which
-        marks the target, you will place the content that you actually want to push. This element
-        will set the <xmlatt>conaction</xmlatt> attribute to <keyword>pushbefore</keyword>.</p>
+        replacing, but the <xmlatt>conaction</xmlatt> attribute is set to <keyword>mark</keyword>
+        because it is marking the referenced element. This element remains empty; its purpose is to
+        ensure that it is legal to have more than one of the current element. The element
+        immediately before the marking element is the content that will actually be pushed. This
+        element will set the <xmlatt>conaction</xmlatt> attribute to
+        <keyword>pushbefore</keyword>.</p>
       <p>When pushing after, the procedure is the same, except that the order of the elements is
         reversed. The element with <codeph>conaction="pushafter"</codeph> comes immediately after
         the element which marks the target.</p>
       <p>Attributes on the element which is pushed (the one with
-          <codeph>conaction="pushbefore"</codeph>) must be retained on the target, apart from the
-          <xmlatt>conaction</xmlatt> attribute itself. If this causes the result document to end up
-        with duplicate IDs, an application can recover by dropping the duplicate ID, modifying it to
-        ensure uniqueness, or warning the user.</p>
+          <codeph>conaction="pushbefore"</codeph> or <codeph>conaction="pushafter"</codeph>) must be
+        retained on the target, apart from the <xmlatt>conaction</xmlatt> attribute itself. If this
+        causes the result document to end up with duplicate IDs, an application can recover by
+        changing the <xmlatt>id</xmlatt>, warning the user, or implementing another strategy.</p>
       <p>The following restrictions apply when pushing content before or after an element: <ul>
           <li>The elements that use <codeph>conaction="mark"</codeph> and
               <codeph>conaction="pushbefore"</codeph> are the same type as each other and appear in
-            sequence. This restriction prevents a topic from trying to push a
-              <xmlelement>body</xmlelement> element before or after another
-              <xmlelement>body</xmlelement> element, because it is not valid to have two body
-            elements in sequence.</li>
+            sequence.</li>
           <li>Either the container elements of the source and target match, or the container of the
-            source element is be a specialization of the target's container. This is also to ensure
+            source element is a specialization of the target's container. This is also to ensure
             validity of the target; for example, while it is possible to include multiple titles in
             a <xmlelement>section</xmlelement>, it is not possible to do so in a figure. Comparing
             the parents prevents a second <xmlelement>section</xmlelement> title from being pushed
-            before a figure title (the resulting figure would not be valid DITA). This restriction
-            only applies to the <keyword>pushbefore</keyword> or<keyword> pushafter</keyword>
-            actions, not to the <keyword>pushreplace</keyword> action.</li>
+            before a figure title. This restriction only applies to the
+              <keyword>pushbefore</keyword> or<keyword> pushafter</keyword> actions, not to the
+              <keyword>pushreplace</keyword> action.</li>
         </ul></p>
       <p>When content is pushed from one topic to another, it is still rendered in the original
-        context. Processors might delete the empty element that has the
+        context. Processors might choose not to render the empty element that has the
           <codeph>conaction="mark"</codeph> attribute. In order to push content from a topic without
         actually rendering that topic on its own, the topic should be referenced from the map with
         the <xmlatt>processing-role</xmlatt> attribute set to "resource-only".</p>
     </section>
-<example id="example-pushbefore" otherprops="examples">
-      <title>Example: pushing an element before the target</title>
-      <p>The following example pushes a <xmlelement>step</xmlelement> before "b" in the
-          <filepath>example.dita</filepath> file shown above. <codeblock>&lt;steps>
-  &lt;step conaction="pushbefore">
-    &lt;cmd>Do this before B&lt;/cmd>
-  &lt;/step>
-  &lt;step conaction="mark" conref="example.dita#example/b">
-    &lt;cmd/>
-  &lt;/step>
-&lt;/steps></codeblock></p>
-      <p>The result contains the pushed <xmlelement>step</xmlelement> element before
-        "b".<codeblock>&lt;task id="example" xml:lang="en">
-  &lt;title>Example topic&lt;/title>
-  &lt;taskbody>
-    &lt;steps>
-      &lt;step id="a">&lt;cmd>A&lt;/cmd>&lt;/step>
-      &lt;step>&lt;cmd>Do this before B&lt;/cmd>&lt;/step>
-      &lt;step id="b">&lt;cmd>B&lt;/cmd>&lt;/step>
-      &lt;step id="c">&lt;cmd>C&lt;/cmd>&lt;/step>
-    &lt;/steps>
-  &lt;/taskbody>
-&lt;/task></codeblock></p>
-    </example>
-<example id="example-pushafter" otherprops="examples">
-      <title>Example: pushing an element after the target</title>
-      <p>Pushing an element after a target is exactly the same as pushing before, except that the
-        order of the "mark" element and the pushed element are reversed.<codeblock>&lt;steps>
-  &lt;step conaction="mark" conref="example.dita#example/b">
-    &lt;cmd/>
-  &lt;/step>
-  &lt;step conaction="pushafter">
-    &lt;cmd>Do this AFTER B&lt;/cmd>
-  &lt;/step>
-&lt;/steps></codeblock></p>
-      <p>In this case the resulting document has the pushed content after
-          <xmlelement>step</xmlelement>
-        b:<codeblock>&lt;task id="example" xml:lang="en">
-  &lt;title>Example topic&lt;/title>
-  &lt;taskbody>
-    &lt;steps>
-      &lt;step id="a">&lt;cmd>A&lt;/cmd>&lt;/step>
-      &lt;step id="b">&lt;cmd>B&lt;/cmd>&lt;/step>
-      &lt;step>&lt;cmd>Do this AFTER B&lt;/cmd>&lt;/step>
-      &lt;step id="c">&lt;cmd>C&lt;/cmd>&lt;/step>
-    &lt;/steps>
-  &lt;/taskbody>
-&lt;/task></codeblock></p>
-    </example>
 <section id="combining-conref-actions">
       <title>Combining <xmlatt>conaction</xmlatt> with <xmlatt>conkeyref</xmlatt> or
           <xmlatt>conrefend</xmlatt></title>
diff --git a/specification/archSpec/base/theconkeyrefattribute.dita b/specification/archSpec/base/theconkeyrefattribute.dita
index 7ecd3698..20768d37 100644
--- a/specification/archSpec/base/theconkeyrefattribute.dita
+++ b/specification/archSpec/base/theconkeyrefattribute.dita
@@ -4,8 +4,8 @@
 <reference id="theconkeyrefattribute" xml:lang="en-us">
 <title>The <xmlatt>conkeyref</xmlatt> attribute</title>
   <shortdesc>The <xmlatt>conkeyref</xmlatt> attribute provides an indirect content reference to
-    topic elements, map elements, or elements within maps or topics. When the DITA content is
-    processed, the key references are resolved using key definitions from DITA maps.</shortdesc>
+    topic elements, map elements, or elements within maps or topics. It allows the referencing
+    element to use a key in place of a file name when referencing another topic or map.</shortdesc>
   <prolog>
     <metadata>
       <keywords>
@@ -14,29 +14,18 @@
     </metadata>
   </prolog>
 <refbody>
-    <section id="section_nsw_5xy_qpb">
-      <draft-comment author="robander" time="19 May 2021">This topic is moving into the arch spec,
-        but needs further editing to split overview / conceptual info from processing info; this and
-        other conref-attribute topics currently have a bunch of processing info that is missing from
-        the actual "Processing conref" arch spec topics.</draft-comment>
-    </section>
     <section id="section-1">
-      <p>For content references from map elements to map elements or topic elements to topic
-        elements, the value of the <xmlatt>conkeyref</xmlatt> attribute is a key name, where the key
-        must be bound to a map element (for references from map elements) or a topic element (for
-        references from topic elements). For all other elements, the value of the
-          <xmlatt>conkeyref</xmlatt> attribute is a key name, an optional <ph 
-          >slash</ph> ("/"), and the ID of the target element, where the key name must be bound to
-        the map or topic that contains the topic element. </p>
+      <p>When the target of a content reference is an element within a topic or map, the value of
+        the <xmlatt>conkeyref</xmlatt> attribute is a key name, followed by a slash ("/"), followed
+        by the ID of the referenced element. The key name must be bound to the topic or map that
+        contains the referenced element.</p>
+      <p>When the target of a content reference is a topic or map, the value of the
+          <xmlatt>conkeyref</xmlatt> attribute is a key name that directly resolves to that topic or
+        map.</p>
       <p>When the key name specified by the <xmlatt>conkeyref</xmlatt> attribute is not defined and
         the element also specifies a <xmlatt>conref</xmlatt> attribute, the <xmlatt>conref</xmlatt>
-        attribute is used to determine the content reference relationship. If no
-          <xmlatt>conref</xmlatt> attribute is specified there is no content reference relationship. </p>
-      <p>Processors <term outputclass="RFC-2119">SHOULD</term> issue a warning when a
-          <xmlatt>conkeyref</xmlatt> reference cannot be resolved and there is no
-          <xmlatt>conref</xmlatt> attribute to use as a fallback. Processors <term
-          outputclass="RFC-2119">MAY</term> issue a warning when a <xmlatt>conkeyref</xmlatt> cannot
-        be resolved to an element and a specified <xmlatt>conref</xmlatt> is used as a fallback.</p>
+        attribute is used to determine the referenced element. If no <xmlatt>conref</xmlatt>
+        attribute is specified there is no content reference relationship. </p>
       <p>The <xmlatt>conrefend</xmlatt> attribute, which defines the end of a conref range, cannot
         include a key. Instead the map or topic element addressed by the key name component of the
           <xmlatt>conkeyref</xmlatt> is used in place of whatever map or topic element is addressed
diff --git a/specification/archSpec/base/theconrefattribute.dita b/specification/archSpec/base/theconrefattribute.dita
index 82523b56..721c3573 100644
--- a/specification/archSpec/base/theconrefattribute.dita
+++ b/specification/archSpec/base/theconrefattribute.dita
@@ -13,17 +13,11 @@
     </metadata>
   </prolog>
 <refbody>
-    <section id="section_pdh_wxy_qpb">
-      <draft-comment author="robander" time="19 May 2021">This topic is moving into the arch spec,
-        but needs further editing to split overview / conceptual info from processing info; this and
-        other conref-attribute topics currently have a bunch of processing info that is missing from
-        the actual "Processing conref" arch spec topics.</draft-comment>
-    </section>
-<section id="section-1"><p>The value of the <xmlatt>conref</xmlatt> attribute must be a URI reference to a DITA element. See
+<section id="section-1"><p>The value of the <xmlatt>conref</xmlatt> attribute is a URI reference to a DITA element. See
           <xref href="../../archSpec/base/uri-based-addressing.dita"/> for details on specifying URI
-        references to DITA elements. <ph>As with other DITA references, a <xmlatt>conref</xmlatt>
-          attribute that references a resource without an ID is treated as a reference to the first
-          topic or map in the document.</ph></p><note>When using the <xmlatt>conref</xmlatt> attribute on an element, the content of that element is
+        references to DITA elements. As with other DITA references, a <xmlatt>conref</xmlatt>
+        attribute that references a resource without an ID is treated as a reference to the first
+        topic or map in the document.</p><note>When using the <xmlatt>conref</xmlatt> attribute on an element, the content of that element is
         ignored. For example, if a phrase is marked up like
         this:<codeblock>&lt;ph conref="#topic/ph">Something&lt;/ph></codeblock> the
         word "Something" will be replaced by the content of the referenced
diff --git a/specification/archSpec/base/theconrefendattribute.dita b/specification/archSpec/base/theconrefendattribute.dita
index 2ec8db16..476b3130 100644
--- a/specification/archSpec/base/theconrefendattribute.dita
+++ b/specification/archSpec/base/theconrefendattribute.dita
@@ -14,12 +14,6 @@
     </metadata>
   </prolog>
   <refbody>
-    <section id="section_v1f_5xy_qpb">
-      <draft-comment author="robander" time="19 May 2021">This topic is moving into the arch spec,
-        but needs further editing to split overview / conceptual info from processing info; this and
-        other conref-attribute topics currently have a bunch of processing info that is missing from
-        the actual "Processing conref" arch spec topics.</draft-comment>
-    </section>
     <section id="section-1"><title>Using <xmlatt>conref</xmlatt> together with
           <xmlatt>conrefend</xmlatt></title>
       <p>The following markup rules apply when using or implementing <xmlatt>conrefend</xmlatt>:<ul>
@@ -34,25 +28,25 @@
             referencing element.
             <!--For example, it is possible to pull a range from <xmlelement>conbody</xmlelement> into <xmlelement>body</xmlelement>, because <xmlelement>conbody</xmlelement> is generalizable to <xmlelement>body</xmlelement>. It is not possible to pull a range from <xmlelement>body</xmlelement> into <xmlelement>conbody</xmlelement>, because the result <ph>might</ph> not be valid in <xmlelement>conbody</xmlelement>.--></li>
         </ul></p><p>In addition, several other items must be taken into account:</p><ul>
-        <li>Processors will resolve the range by pulling in the start target and following sibling
-          XML nodes across to and including the end target.</li>
+        <li>Processors will resolve the range by pulling in the starting referenced element and
+          following sibling XML nodes across to and including the ending referenced element.</li>
         <li>As with <xmlatt>conref</xmlatt>, if the <xmlatt>conrefend</xmlatt> references a more
           specialized version of the referencing element, applications should generalize the target
-          when resolving. </li>
-        <li>It is not valid to use <xmlatt>conrefend</xmlatt> to reference a more general version of
-          an element (such as using <xmlelement>step</xmlelement> to reference an
-            <xmlelement>li</xmlelement> element).</li>
+          when resolving.</li>
+        <li>As with <xmlatt>conref</xmlatt>, it is not valid to use <xmlatt>conrefend</xmlatt> to
+          reference a more general version of an element (such as using
+            <xmlelement>step</xmlelement> to reference an <xmlelement>li</xmlelement> element).</li>
         <li>Other nodes (such as elements or text) between the start and end of a range do not have
           to match the referencing element.</li>
         <li>With single conref, an <xmlatt>id</xmlatt> attribute from the referenced element will
           not be preserved on the resolved content. With a range, an <xmlatt>id</xmlatt> on both the
           start and the end elements will not be preserved. <xmlatt>id</xmlatt> attributes on
           intermediate or child nodes should be preserved; if this results in duplicate
-            <xmlatt>id</xmlatt> values, an application <ph>can recover by changing the
-              <xmlatt>id</xmlatt>, warning the user, or implementing another strategy.</ph></li>
-        <li>With a single conref, attributes specified on the referencing element<ph>can</ph> be
-          used to override attributes on the referenced element. With a conref range, the same is
-          true, with the following clarifications: <ul>
+            <xmlatt>id</xmlatt> values, an application can recover by changing the
+            <xmlatt>id</xmlatt>, warning the user, or implementing another strategy.</li>
+        <li>With a single conref, attributes specified on the referencing element can be used to
+          override attributes on the referenced element. With a conref range, the same is true, with
+          the following clarifications: <ul>
             <li>When an <xmlatt>id</xmlatt> attribute is specified on the referencing element, it
               will only be preserved on the first element of the resolved range.</li>
             <li>When other attributes are specified, they will only apply to referenced elements of
@@ -64,98 +58,6 @@
                 <xmlelement>ol</xmlelement> elements in that range.</li>
           </ul></li>
       </ul></section>
-    <example id="example-reuse-li" otherprops="examples">
-      <title>Example: reusing a set of list items</title>
-      <fig>
-        <title>List example: Source <filepath>topic.dita</filepath> with ids</title>
-        <codeblock>&lt;topic id="x">
-  &lt;title>Sample file topic.dita&lt;/title>
-  &lt;body>
-    &lt;ol>
-      &lt;li id="apple">A&lt;/li>
-      &lt;li id="bear">B&lt;/li>
-      &lt;li id="cat">C&lt;/li>
-      &lt;li id="dog">D&lt;/li>
-      &lt;li id="eel">E&lt;/li>
-    &lt;/ol>
-  &lt;/body>
-&lt;/topic></codeblock>
-      </fig>
-      <fig id="fig_C0AF6F23F1E74AF98540F736113DFFAB">
-        <title>List example: Reusing topic with conrefs</title>
-        <codeblock>&lt;topic id="y">
-  &lt;title>Sample file reusing content&lt;/title>
-  &lt;body>
-    &lt;ol>
-      &lt;li>My own first item&lt;/li>
-      &lt;li conref="topic.dita#x/bear" conrefend="topic.dita#x/dog"/>
-      &lt;li>And a different final item&lt;/li>
-    &lt;/ol>
-  &lt;/body>
-&lt;/topic></codeblock>
-      </fig>
-      <fig id="fig_A79BE8A6869B4DFDAAFA2F55BC113AA1">
-        <title>List example: Processed result of reusing topic</title>
-        <codeblock>&lt;topic id="y">
-  &lt;title>Sample file reusing content&lt;/title>
-  &lt;body>
-    &lt;ol>
-      &lt;li>My own first item&lt;/li>
-      &lt;li>B&lt;/li>
-      &lt;li id="cat">C&lt;/li>
-      &lt;li>D&lt;/li>
-      &lt;li>And a different final item&lt;/li>
-    &lt;/ol>
-  &lt;/body>
-&lt;/topic></codeblock>
-      </fig>
-    </example>
-    <example id="example-reuse-blocks" otherprops="examples">
-      <title>Example: Reusing a set of blocks</title>
-      <fig id="fig_7BB281DFE28F474BB9197BAE691B927C">
-        <title>Block level example: Source <filepath>topic.dita</filepath> with ids</title>
-        <codeblock>&lt;topic id="x">
-  &lt;title>Sample file topic.dita&lt;/title>
-  &lt;body>
-    &lt;p id="p1"&gt;First para&lt;/p&gt;
-    &lt;ol id="mylist"&gt;
-      &lt;li id="apple"&gt;A&lt;/li&gt;
-      &lt;li id="bear"&gt;B&lt;/li&gt;
-      &lt;li id="cat"&gt;C&lt;/li&gt;
-      &lt;li id="dog"&gt;D&lt;/li&gt;
-      &lt;li id="eel"&gt;E&lt;/li&gt;
-    &lt;/ol&gt;
-    &lt;p id="p2"&gt;Second para&lt;/p&gt;
-  &lt;/body&gt;
-&lt;/topic&gt;</codeblock>
-      </fig>
-      <fig id="fig_BF890E35527C41FBA93878660EFC1636">
-        <title>Block level example: Reusing topic with conrefs</title>
-        <codeblock>&lt;topic id="y"&gt;
-  &lt;title>Sample file reusing content&lt;/title>
-  &lt;body>
-    &lt;p conref="topic.dita#x/p1" conrefend="topic.dita#x/p2"/&gt;
-  &lt;/body>
-&lt;/topic&gt;</codeblock>
-      </fig>
-      <fig id="fig_D257C3B1EE2B49DA85457B1753A8C79D">
-        <title>Block level example: Processed result of reusing topic</title>
-        <codeblock>&lt;topic id="y"&gt;
-  &lt;title>Sample file reusing content&lt;/title>
-  &lt;body>
-    &lt;p&gt;First para&lt;/p&gt;
-    &lt;ol id="mylist"&gt;
-      &lt;li id="apple"&gt;A&lt;/li&gt;
-      &lt;li id="bear"&gt;B&lt;/li&gt;
-      &lt;li id="cat"&gt;C&lt;/li&gt;
-      &lt;li id="dog"&gt;D&lt;/li&gt;
-      &lt;li id="eel"&gt;E&lt;/li&gt;
-    &lt;/ol&gt;
-    &lt;p&gt;Second para&lt;/p&gt;
-  &lt;/body&gt;
-&lt;/topic&gt;</codeblock>
-      </fig>
-    </example>
     <section id="conkeyref">
       <title>Using <xmlatt>conrefend</xmlatt> together with <xmlatt>conkeyref</xmlatt></title>
       <p>When the <xmlatt>conkeyref</xmlatt> attribute is used in place of <xmlatt>conref</xmlatt>,
@@ -172,114 +74,5 @@
         the <xmlatt>conref</xmlatt> attribute itself is not present for fallback, the
           <xmlatt>conrefend</xmlatt> attribute is ignored.</p>
     </section>
-    <example id="conrefend-with-conkeyref" otherprops="examples">
-      <title>Example: Combining <xmlatt>conrefend</xmlatt> with <xmlatt>conkeyref</xmlatt></title>
-      <fig>
-        <title>Defining and referencing a key with <xmlatt>conkeyref</xmlatt></title>
-        <p>In this example the key <keyword>xmp</keyword> is defined as the first topic in the file
-            <filepath>examples.dita.</filepath></p>
-        <codeblock id="codeblock_hwy_krh_psb">&lt;map>
-  &lt;!-- ... -->
-  &lt;keydef keys="xmp" href="examples.dita"/>
-  &lt;!-- ... -->
-&lt;/map></codeblock>
-        <codeblock id="codeblock_iwy_krh_psb">&lt;!-- examples.dita: -->
-&lt;topic id="examples">
-  &lt;title>These are examples&lt;/title>
-  &lt;body>
-    &lt;ul>
-      &lt;li id="first">A first example&lt;/li>
-      &lt;li>Another trivial example&lt;/li>
-      &lt;li id="last">Final example&lt;/li>
-    &lt;/ul>
-  &lt;/body>
-&lt;/topic></codeblock>
-        <p>To reuse these list items by using the key, the <xmlatt>conkeyref</xmlatt> attribute
-          combines the key itself with the sub-topic id (first) to define the start of the range.
-          The <xmlatt>conrefend</xmlatt> attribute defines a default high-level object along with
-          the sub-topic id (last) that ends the
-          range:<codeblock>  &lt;li conkeyref="xmp/first" 
-      conrefend="default.dita#default/last"/></codeblock></p>
-        <p>The <xmlatt>conkeyref</xmlatt> attribute uses a key to reference the first topic in
-            <filepath>examples.dita</filepath>, so the range begins with the object
-            <codeph>examples.dita#examples/first</codeph>. The high-level object in the
-            <xmlatt>conrefend</xmlatt> attribute (<codeph>default.dita#default</codeph>) is replaced
-          with the object represented by the key (the first topic in
-            <filepath>examples.dita</filepath>), resulting in a range that ends with the object
-            <codeph>examples.dita#examples/last</codeph>.</p>
-      </fig>
-      <fig>
-        <title>Combining <xmlatt>conref</xmlatt>, <xmlatt>conkeyref</xmlatt>, and
-            <xmlatt>conrefend</xmlatt></title>
-        <p>When <xmlatt>conref</xmlatt>, <xmlatt>conkeyref</xmlatt>, and <xmlatt>conrefend</xmlatt>
-          are all specified, the key value takes priority.</p>
-        <codeblock>  &lt;li conkeyref="thisconfig/start"
-      conref="standardconfig.dita#config/start"
-      conrefend="standardconfig.dita#config/end"/></codeblock>
-        <ul>
-          <li>If the key <keyword>thisconfig</keyword> is defined as
-              <codeph>mySpecialConfig.dita#myconfig</codeph>, then the range will go from the list
-            item with <codeph>id="start"</codeph> to the list item with<codeph>id="end"</codeph> in
-            the topic <codeph>mySpecialConfig.dita#myconfig</codeph>.</li>
-          <li>If the key <keyword>thisconfig</keyword> is defined as <codeph>myConfig.dita</codeph>,
-            then the range will go from the list item with <codeph>id="start"</codeph> to the list
-            item with <codeph>id="end"</codeph> within the first topic in
-              <codeph>myConfig.dita</codeph>.</li>
-          <li>If the key <keyword>thisconfig</keyword> is not defined, then the unchanged
-              <xmlatt>conref</xmlatt> and <xmlatt>conrefend</xmlatt> attributes are used as
-            fallback. In that case, the range will go from the list item with
-              <codeph>id="start"</codeph> to the list item with <codeph>id="end"</codeph> within the
-            topic <codeph>standardconfig.dita#config</codeph>.</li>
-        </ul>
-      </fig>
-    </example>
-    <section id="error-conditions" outputclass="errorcondition">
-      <title>Error conditions</title>
-      <p>When encountering an error condition, an implementation can issue an error message.</p>
-      <table>
-        <tgroup cols="2">
-          <colspec colname="col1" colnum="1" colwidth="1*"/>
-          <colspec colname="col2" colnum="2" colwidth="1*"/>
-          <thead>
-            <row>
-              <entry colname="col1">Condition or Issue</entry>
-              <entry colname="col2">Result</entry>
-            </row>
-          </thead>
-          <tbody>
-            <row>
-              <entry colname="col1">The <xmlatt>conref</xmlatt> attribute cannot be resolved in the
-                target document (the target element <ph>might</ph> have been removed or its id has
-                changed). </entry>
-              <entry colname="col2">The <xmlatt>conref</xmlatt> is ignored.</entry>
-            </row>
-            <row>
-              <entry colname="col1">The <xmlatt>conrefend</xmlatt> attribute cannot be resolved in
-                the target document (the target element <ph>might</ph> have been removed or its id
-                has changed).</entry>
-              <entry colname="col2">Range cannot be resolved, optional recovery processes the result
-                as a simple conref.</entry>
-            </row>
-            <row>
-              <entry colname="col1">Start and end elements are not siblings in the target
-                document.</entry>
-              <entry colname="col2">If the start element exists, optional recovery processes the
-                result as a simple conref. </entry>
-            </row>
-            <row>
-              <entry colname="col1">End element occurs before the start element in the target
-                document.</entry>
-              <entry colname="col2">If the start element exists, optional recovery processes the
-                result as a simple conref.</entry>
-            </row>
-            <row>
-              <entry colname="col1">An element has a <xmlatt>conrefend</xmlatt> attribute but is
-                missing the <xmlatt>conref</xmlatt> attribute.</entry>
-              <entry colname="col2">No result.</entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-    </section>
   </refbody>
 </reference>
diff --git a/specification/common/conref-file.dita b/specification/common/conref-file.dita
index dc6b3737..a7930298 100644
--- a/specification/common/conref-file.dita
+++ b/specification/common/conref-file.dita
@@ -17,8 +17,8 @@
             <xmlelement>reference</xmlelement></ph></p>
                         <p><ph id="maps-shortdesc">DITA maps are documents that organize topics and
           other resources into structured collections of information. DITA maps specify hierarchy
-          and the relationships among the topics; they also provide the <ph>contexts</ph> in which
-          keys are defined and resolved.</ph></p>
+          and the relationships among the topics; they also provide the contexts in which keys are
+          defined and resolved.</ph></p>
                         <p><ph id="information-typing-shortdesc">Information typing is the practice
           of identifying types of topics, such as concept, reference, and task, to clearly
           distinguish between different types of information. Topics that answer different reader
@@ -42,10 +42,9 @@
           an abbreviated fragment-identifier syntax that can be used when addressing non-topic
           elements from within the same topic.</ph></p>
                         <p><ph id="conref-shortdesc">The DITA <xmlatt>conref</xmlatt>,
-            <xmlatt>conkeyref</xmlatt>, <xmlatt>conrefend</xmlatt>, and <xmlatt 
-            >conaction</xmlatt> attributes provide mechanisms for reusing content within DITA topics
-          or maps. <ph >These mechanisms can be used both to <ph 
-              >pull and push</ph> content.</ph></ph></p>
+            <xmlatt>conkeyref</xmlatt>, <xmlatt>conrefend</xmlatt>, and <xmlatt>conaction</xmlatt>
+          attributes provide mechanisms for reusing content within DITA topics or maps. These
+          mechanisms can be used both to pull and push content.</ph></p>
                         <p><ph id="conditional-processing-shortdesc"
           >Conditional processing is the filtering or flagging of
           information based on processing-time