diff --git a/specification/archSpec/technicalContent/dita-glossary-topic.dita b/specification/archSpec/technicalContent/dita-glossary-topic.dita
index 7f2cac09..2240d95e 100644
--- a/specification/archSpec/technicalContent/dita-glossary-topic.dita
+++ b/specification/archSpec/technicalContent/dita-glossary-topic.dita
@@ -15,9 +15,8 @@
       <ul>
         <li>They ensure that a team of writers can use the same
           terminology.</li>
-        <li>They make it possible to create glossaries that can be use to
-          provide readers with definitions of terms and explanations about
-          acronyms.</li>
+        <li>They make it possible to create glossaries that can be used to provide readers with
+          definitions of terms and explanations about acronyms.</li>
       </ul>
     </section>
     <!--<section><title>The purpose of the glossary entry topic</title><p>Defining terminology in a glossary ensures that a team of writers uses the same term for the same concept. A glossary added to a book or available online in conjunction with other subject matter provides the reader with definitions of unfamiliar terms and expands acronyms.</p></section>-->
@@ -39,12 +38,27 @@
       <p>The following code sample contains a simple glossentry topic:</p>
       <codeblock>&lt;glossentry id="ddl">
   &lt;glossterm>data definition language&lt;/glossterm>
-  &lt;glossdef>A language used for defining database schemas&lt;/glossdef>
+  &lt;glossdef>A language used for defining database schemas&lt;/glossdef><?oxy_insert_start author="dawnstevens" timestamp="20240507T073646-0600"?>
+  &lt;glossBody>
+     &lt;glossSurfaceForm>data definition language (DDL)&lt;/glossSurfaceForm>
+     &lt;glossAlt>
+        &lt;glossAcronym>DDL&lt;/glossAcronym>
+     &lt;/glossAlt>
+   &lt;glossBody>
+   &lt;related-links>
+      &lt;link href="data_control_language.dita"/>
+      &lt;link href="data_manipulation_language.dita"/>
+      &lt;link href="data_query_language.dita"/>
+      &lt;link href="sql.dita"/><?oxy_insert_end?>
 &lt;/glossentry></codeblock>
       <draft-comment author="Kristen J Eberlein" time="07 October 2022">
-        <p>This should have a glossbody that specifies an acronym and a
-          surface term. Also related links.</p>
+        <p>This should have a glossbody that specifies an acronym and a surface term. Also related
+          links.</p>
       </draft-comment>
+      <?oxy_insert_start author="dawnstevens" timestamp="20240507T073655-0600"?>
+      <draft-comment author="dawnstevens">Done</draft-comment>
+      <?oxy_insert_end?>
     </example>
   </conbody>
 </concept>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossAcronym.dita b/specification/langRef/technicalContent/glossAcronym.dita
index 93e5ec77..ce8d68e1 100644
--- a/specification/langRef/technicalContent/glossAcronym.dita
+++ b/specification/langRef/technicalContent/glossAcronym.dita
@@ -3,10 +3,13 @@
  "reference.dtd">
 <reference id="glossAcronym" xml:lang="en-us">
   <title><xmlelement>glossAcronym</xmlelement></title>
-  <shortdesc>The <xmlelement>glossAcronym</xmlelement> element defines an acronym for the term
-    specified in the topic's <xmlelement>glossterm</xmlelement> element. An acronym typically is
-    composed of the initial letters of the components of the full form or from the syllables of the
-    full form to create a pronounceable combination of letters. </shortdesc>
+  <shortdesc>The <xmlelement>glossAcronym</xmlelement> element defines
+    <?oxy_delete author="dawnstevens" timestamp="20240507T073807-0600" content="an acronym "?><?oxy_insert_start author="dawnstevens" timestamp="20240507T073807-0600"?>a
+    shortened form <?oxy_insert_end?>for the term specified in the topic's
+      <xmlelement>glossterm</xmlelement>
+    element<?oxy_insert_start author="dawnstevens" timestamp="20240507T073814-0600"?>, such as an
+    acronym, initialism, or abbreviation<?oxy_insert_end?>.
+    <?oxy_delete author="dawnstevens" timestamp="20240507T073834-0600" content="An acronym typically is composed of the initial letters of the components of the full form or from the syllables of the full form to create a pronounceable combination of letters. "?></shortdesc>
   <prolog>
     <metadata>
       <keywords>
@@ -21,17 +24,31 @@
     <section id="usage-information">
       <title>Usage information</title>
       <p>This element can be used with the <xmlelement>abbreviated-form</xmlelement> element to
-        display an expanded version of an acronym the first time that acronym appears in a set of
-        text. See <xref href="abbreviated-form.dita"
-          ><xmlelement>abbreviated-form</xmlelement></xref> for information on how the two elements
-        interact.</p>
-      <note>An acronym in one language might not have an equivalent in another language. When
-        acronyms are first displayed, some languages will display the expanded form first followed
-        by the acronym in parenthesis, while other languages do the reverse. For some acronyms, a
-        translation might need to render both the original and the translated version of the
-        acronym. For all of these reasons, DITA allows an author or translator to control what is
-        presented to a reader by using the <xmlelement>glossSurfaceForm</xmlelement> element, which
-        will often accompany the <xmlelement>glossAcronym</xmlelement>. The <xref
+        display <?oxy_insert_start author="dawnstevens" timestamp="20240507T073947-0600"?>either
+        <?oxy_insert_end?>an expanded version of
+        <?oxy_delete author="dawnstevens" timestamp="20240507T073903-0600" content="an acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T073903-0600"?>the
+        term<?oxy_insert_end?> the first time that
+        <?oxy_delete author="dawnstevens" timestamp="20240507T073907-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T073907-0600"?>term<?oxy_insert_end?>
+        appears in a set of
+        text<?oxy_insert_start author="dawnstevens" timestamp="20240507T073951-0600"?> or the
+        shortened version defined in this element on subsequent occurrences of the
+        term<?oxy_insert_end?>. See <xref href="abbreviated-form.dita"
+            ><xmlelement>abbreviated-form</xmlelement></xref> for information on how the two
+        elements interact.</p>
+      <note>A<?oxy_delete author="dawnstevens" timestamp="20240507T074049-0600" content="n acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074049-0600"?>
+        shortened form of a term<?oxy_insert_end?> in one language might not have an equivalent in
+        another language. When
+        <?oxy_delete author="dawnstevens" timestamp="20240507T074104-0600" content="acronyms"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074104-0600"?>shortened
+        terms<?oxy_insert_end?> are first displayed, some languages will display the expanded form
+        first followed by the
+        <?oxy_delete author="dawnstevens" timestamp="20240507T074112-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074112-0600"?>shortened
+        form<?oxy_insert_end?> in parenthesis, while other languages do the reverse. For some
+        <?oxy_delete author="dawnstevens" timestamp="20240507T074122-0600" content="acronyms"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074122-0600"?>terms<?oxy_insert_end?>,
+        a translation might need to render both the original and the translated version of the
+        <?oxy_delete author="dawnstevens" timestamp="20240507T074126-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074126-0600"?>shortened
+        form<?oxy_insert_end?>. For all of these reasons, DITA allows an author or translator to
+        control what is presented to a reader by using the <xmlelement>glossSurfaceForm</xmlelement>
+        element, which will often accompany the <xmlelement>glossAcronym</xmlelement>. The <xref
           href="abbreviated-form.dita"><xmlelement>abbreviated-form</xmlelement></xref> topic
         contains information on how the <xmlelement>glossSurfaceForm</xmlelement> and
           <xmlelement>glossAcronym</xmlelement> elements affect references to the term.</note>
@@ -63,3 +80,4 @@
     </example>
   </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossAlt.dita b/specification/langRef/technicalContent/glossAlt.dita
index ec85706b..26b21f32 100644
--- a/specification/langRef/technicalContent/glossAlt.dita
+++ b/specification/langRef/technicalContent/glossAlt.dita
@@ -66,7 +66,7 @@
       &lt;glossUsage>Do not use; the American continents include other countries.&lt;/glossUsage>
     <b>&lt;/glossAlt>
     &lt;glossAlt></b>
-      &lt;glossAbbreviation>the States&lt;/glossAbbreviation>
+      &lt;glossA<?oxy_delete author="dawnstevens" timestamp="20240507T074506-0600" content="bbreviation"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074506-0600"?>cronym<?oxy_insert_end?>>the States&lt;/glossA<?oxy_delete author="dawnstevens" timestamp="20240507T074511-0600" content="bbreviation"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074511-0600"?>cronym<?oxy_insert_end?>>
       &lt;glossUsage>Informal. Typically used by English speakers outside of the country.&lt;/glossUsage>
     <b>&lt;/glossAlt></b>
   &lt;/glossBody><b>
@@ -75,3 +75,4 @@
     </example>
   </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossBody.dita b/specification/langRef/technicalContent/glossBody.dita
index 27baaf81..0943310b 100644
--- a/specification/langRef/technicalContent/glossBody.dita
+++ b/specification/langRef/technicalContent/glossBody.dita
@@ -3,8 +3,9 @@
 <reference id="glossBody" xml:lang="en-us">
 <title><xmlelement>glossBody</xmlelement></title>
 <shortdesc>The <xmlelement>glossBody</xmlelement> element contains information about the term
-    specified in the topic's <xmlelement>glossterm</xmlelement> element, such as the part of speech
-    and variants for the term.</shortdesc>
+    specified in the topic's <xmlelement>glossterm</xmlelement> element, such as
+    <?oxy_delete author="dawnstevens" timestamp="20240507T074606-0600" content="the part of speech and "?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074606-0600"?>usage
+    and <?oxy_insert_end?>variants for the term.</shortdesc>
 <prolog><metadata>
 <keywords><indexterm><xmlelement>glossBody</xmlelement></indexterm>
             <indexterm>glossentry
@@ -23,23 +24,43 @@
          <p conkeyref="reuse-attributes/only-universal"/>
       </section>
       <example id="example" otherprops="examples">
-         <title>Example</title>
-      <p>The following code sample shows how the
-          <xmlelement>glossBody</xmlelement> element contains the part of
-        speech and variant forms for the term:</p>
-      <codeblock>&lt;glossentry id="sport-drink">
-    &lt;glossterm>Sport drink&lt;/glossterm>
-    &lt;glossdef>A soft drink designed or marketed for consumption in
+      <title>Example</title>
+      <p>The following code sample shows how the <xmlelement>glossBody</xmlelement> element
+        <?oxy_delete author="dawnstevens" timestamp="20240507T074641-0600" content="contains the part of speech"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T074641-0600"?>provides
+        guidance about the usage of the term<?oxy_insert_end?> and variant forms for the term:</p>
+      <?oxy_delete author="dawnstevens" timestamp="20240507T074807-0600" content="&lt;codeblock&gt;&amp;lt;glossentry id=&quot;sport-drink&quot;&gt;
+    &amp;lt;glossterm&gt;Sport drink&amp;lt;/glossterm&gt;
+    &amp;lt;glossdef&gt;A soft drink designed or marketed for consumption in
     conjunction with sporting activity or strenuous exercise, and which
     typically contains electrolytes such as sodium, potassium, and
-    chloride, and a high percentage of sugar to restore energy.&lt;/glossdef>
-  <b>&lt;glossBody></b>
-    &lt;glossPartOfSpeech value="noun"/>
-    &lt;glossAlt>
-      &lt;glossSynonym>energy drink&lt;/glossSynonym>
-    &lt;/glossAlt>
-  <b>&lt;/glossBody></b>
-&lt;/glossentry></codeblock>
-      </example>
+    chloride, and a high percentage of sugar to restore energy.&amp;lt;/glossdef&gt;
+  &lt;b&gt;&amp;lt;glossBody&gt;&lt;/b&gt;
+    &amp;lt;glossPartOfSpeech value=&quot;noun&quot;/&gt;
+    &amp;lt;glossAlt&gt;
+      &amp;lt;glossSynonym&gt;energy drink&amp;lt;/glossSynonym&gt;
+    &amp;lt;/glossAlt&gt;
+  &lt;b&gt;&amp;lt;/glossBody&gt;&lt;/b&gt;
+&amp;lt;/glossentry&gt;&lt;/codeblock&gt;"?>
+      <?oxy_insert_start author="dawnstevens" timestamp="20240507T074811-0600"?>
+      <codeblock>&lt;glossentry id="pin">
+    &lt;glossterm>personal identification number&lt;/glossterm>
+    &lt;glossdef>A numerical code issued with a payment card that is required 
+       to be entered to complete various finanancial transactions. The core
+       purpose of this code is to provide an additional layer of security 
+       to the electronic transaction process.&lt;/glossdef>
+ <b>&lt;glossBody></b>
+       &lt;glossSurfaceForm>personal identification number (PIN)&lt;/glossSurfaceForm>
+       &lt;glossUsage>Use in the context of banking and finanacial transactions. For
+          context of Indian addresses, see &lt;xref href="postal_index_number.dita">.
+       &lt;glossAlt>
+          &lt;glossAcronym>PIN&lt;/glossAcronym>
+          &lt;glossUsage>Do not use the acronym followed by the word "number." It is
+             redundant as the 'N' in the acronym stands for the word "number."
+          &lt;/glossUsage>
+       &lt;/glossAlt>
+ <b>&lt;/glossBody></b></codeblock>
+      <?oxy_insert_end?>
+    </example>
 </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossSurfaceForm.dita b/specification/langRef/technicalContent/glossSurfaceForm.dita
index 86391894..a13906d4 100644
--- a/specification/langRef/technicalContent/glossSurfaceForm.dita
+++ b/specification/langRef/technicalContent/glossSurfaceForm.dita
@@ -6,17 +6,7 @@
   <shortdesc>The <xmlelement>glossSurfaceForm</xmlelement> element specifies how the term specified
     by the topic's <xmlelement>glossterm</xmlelement> element should appear in the text. The surface
     form is suitable to introduce the term in new contexts or as the first occurrence in
-      text.<draft-comment author="dawnstevens">I learned a lot more than I really wanted to about
-      the surface form in linguistics to suggest this short description, as opposed to what was
-      there: "an unambiguous presentation of the term that might combine multiple forms." Surface
-      forms are " the way a linguistic unit (such as a word, phrase, or sentence) appears when it is
-      actually spoken or written, as opposed to its underlying or abstract form." Surface forms may
-      take into account phonology (to provide stress, intonation, and accent), test and plurals (the
-      surface form of "go" is "goes" in 3rd person singular), and derivational (to change roots of
-      words in various contexts), contextual (I'm might be a surface form of I am in informal
-      speech). Ultimately, in my experience the only thing this is really used for is first-use
-      occurrence of acronyms so they are spelled out. I wonder if we should use that use case only
-      in this definition, rather than a more comprehensive scope. </draft-comment></shortdesc>
+    text.<?oxy_delete author="dawnstevens" timestamp="20240507T080555-0600" content="&lt;draft-comment author=&quot;dawnstevens&quot;&gt;I learned a lot more than I really wanted to about the surface form in linguistics to suggest this short description, as opposed to what was there: &quot;an unambiguous presentation of the term that might combine multiple forms.&quot; Surface forms are &quot; the way a linguistic unit (such as a word, phrase, or sentence) appears when it is actually spoken or written, as opposed to its underlying or abstract form.&quot; Surface forms may take into account phonology (to provide stress, intonation, and accent), test and plurals (the surface form of &quot;go&quot; is &quot;goes&quot; in 3rd person singular), and derivational (to change roots of words in various contexts), contextual (I&apos;m might be a surface form of I am in informal speech). Ultimately, in my experience the only thing this is really used for is first-use occurrence of acronyms so they are spelled out. I wonder if we should use that use case only in this definition, rather than a more comprehensive scope. &lt;/draft-comment&gt;"?></shortdesc>
   <prolog>
     <metadata>
       <keywords>
@@ -33,17 +23,28 @@
       <p>The <xmlelement>glossSurfaceForm</xmlelement> element is most often used for terms that
         also specify the <xmlelement>glossAcronym</xmlelement> element. In that context, the
           <xmlelement>glossSurfaceForm</xmlelement> element contains the term in a manner that
-        introduces both the term and the acronym, so that later references to the term can be
-        replaced with the acronym alone. <note id="note_nkh_yqp_c1c">In some languages, the surface
-          form that expands the acronym in its first use handles the formatting differently than in
-          English. For example, in Polish, the acronym precedes the expansion. In addition, some
-          languages may not have a corresponding acronym for a term, so the
-            <xmlelement>glossSurfaceForm</xmlelement> and <xmlelement>glossAcronym</xmlelement>
-          would be left blank in translated content.</note></p>
-      <p>See the <xref href="abbreviated-form.dita"
-            ><xmlelement>abbreviated-form</xmlelement></xref> element for a
-        full description of how the surface form is used together with
-        acronyms.</p>
+        introduces both the term and
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080628-0600" content="the acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080628-0600"?>its
+        shortened form<?oxy_insert_end?>, so that later references to the term can be replaced with
+        the
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080634-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080636-0600"?>shortened
+        form<?oxy_insert_end?> alone. <note id="note_nkh_yqp_c1c">In some languages, the surface
+          form that expands the
+          <?oxy_delete author="dawnstevens" timestamp="20240507T080645-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080645-0600"?>shortened
+          form<?oxy_insert_end?> in its first use handles the formatting differently than in
+          English. For example, in Polish,
+          <?oxy_delete author="dawnstevens" timestamp="20240507T080703-0600" content="the"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080703-0600"?>an<?oxy_insert_end?>
+          acronym precedes
+          <?oxy_delete author="dawnstevens" timestamp="20240507T080706-0600" content="the"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080706-0600"?>its<?oxy_insert_end?>
+          expansion. In addition, some languages may not have a corresponding
+          <?oxy_delete author="dawnstevens" timestamp="20240507T080709-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080709-0600"?>short
+          form<?oxy_insert_end?> for a term, so the <xmlelement>glossSurfaceForm</xmlelement> and
+            <xmlelement>glossAcronym</xmlelement> would be left blank in translated
+        content.</note></p>
+      <p>See the <xref href="abbreviated-form.dita"><xmlelement>abbreviated-form</xmlelement></xref>
+        element for a full description of how the surface form is used together with
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080718-0600" content="acronyms"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080718-0600"?>short
+        forms, such as acronyms<?oxy_insert_end?>.</p>
     </section>
     <section id="specialization-hierarchy">
       <title>Specialization hierarchy</title>
@@ -63,7 +64,9 @@
         the glossary entry topic is referenced from an <xmlelement>abbreviated-form</xmlelement>
         element.</p>
       <codeblock>&lt;glossentry id="abs">
-  &lt;glossterm>Anti-lock Braking System&lt;/glossterm>
+  &lt;glossterm>Anti-lock Braking System&lt;/glossterm><?oxy_insert_start author="dawnstevens" timestamp="20240507T080756-0600"?>
+  &lt;glossdef>A safety feature on vehicles used to prevent a wheel lock up and 
+    to help operators maintain control of the vehicle.&lt;/glossdef><?oxy_insert_end?>
   &lt;glossBody>
     <b>&lt;glossSurfaceForm>Anti-lock Braking System (ABS)&lt;/glossSurfaceForm></b>
     &lt;glossAlt>
@@ -74,3 +77,4 @@
     </example>
   </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossUsage.dita b/specification/langRef/technicalContent/glossUsage.dita
index 6bfa5391..5c561b54 100644
--- a/specification/langRef/technicalContent/glossUsage.dita
+++ b/specification/langRef/technicalContent/glossUsage.dita
@@ -21,10 +21,7 @@
       <title>Specialization hierarchy</title>
       <p>The <xmlelement>glossUsage</xmlelement> element is specialized from
           <xmlelement>note</xmlelement>. It is defined in the glossary entry module.</p>
-      <draft-comment author="dawnstevens">Although I realize the element is specialized from Note, I
-        question the need to point out the type and othertype attributes; they don't seem to me to
-        have any meaning in the content of a usage note. A usage note is type usage note, in my
-        mind. Why would anyone specify any type or othertype?</draft-comment>
+      <?oxy_delete author="dawnstevens" timestamp="20240507T081126-0600" content="&lt;draft-comment author=&quot;dawnstevens&quot;&gt;Although I realize the element is specialized from Note, I question the need to point out the type and othertype attributes; they don&apos;t seem to me to have any meaning in the content of a usage note. A usage note is type usage note, in my mind. Why would anyone specify any type or othertype?&lt;/draft-comment&gt;"?>
     </section>
     <section conkeyref="reuse-note/attributes" id="attributes"/>
     <example id="example" otherprops="examples">
@@ -53,3 +50,4 @@
     </example>
   </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file
diff --git a/specification/langRef/technicalContent/glossentry.dita b/specification/langRef/technicalContent/glossentry.dita
index 62ff513d..f194b511 100644
--- a/specification/langRef/technicalContent/glossentry.dita
+++ b/specification/langRef/technicalContent/glossentry.dita
@@ -39,10 +39,16 @@
       <p>One possible implementation of a glossary in online processing is to associate a hotspot
         for mentions of terms in <xmlelement>term</xmlelement> elements and display the definition
         on hover or click. A possible implementation in PDF processing is to define a first-use
-        occurrence form of the term with its acronym and use it in conjunction with
-          <xmlelement>abbreviated-form</xmlelement> to render a spell-out version of the term with
-        its acronym on first use within an output, while rendering the acronym in all subsequent
-        locations.</p>
+        occurrence form of the term with its
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080031-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080031-0600"?>shortened
+        form<?oxy_insert_end?> and use it in conjunction with
+          <xmlelement>abbreviated-form</xmlelement> to render a
+        spell<?oxy_insert_start author="dawnstevens" timestamp="20240507T080017-0600"?>ed<?oxy_insert_end?>-out
+        version of the term with its
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080039-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080039-0600"?>short
+        form<?oxy_insert_end?> on first use within an output, while rendering the
+        <?oxy_delete author="dawnstevens" timestamp="20240507T080043-0600" content="acronym"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080043-0600"?>short
+        form<?oxy_insert_end?> in all subsequent locations.</p>
     </section>
     <section id="specialization-hierarchy">
       <title>Specialization hierarchy</title>
@@ -61,27 +67,28 @@
   &lt;glossterm>USB flash drive&lt;/glossterm>
   &lt;glossdef>A small portable drive.&lt;/glossdef>
   &lt;glossBody>
-    &lt;glossPartOfSpeech value="noun"/>
+    <?oxy_delete author="dawnstevens" timestamp="20240507T080216-0600" content="&amp;lt;glossPartOfSpeech value=&quot;noun&quot;/&gt;"?>
     &lt;glossUsage>Do not use this term in upper case (for example,  in "USB Flash Drive")
       because that suggests a trademark.&lt;/glossUsage>
     &lt;glossAlt>
       &lt;glossAcronym>UFD&lt;/glossAcronym>
-      &lt;glossStatus value="prohibited"/>
+      &lt;gloss<?oxy_delete author="dawnstevens" timestamp="20240507T080110-0600" content="Status"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080112-0600"?>Usage<?oxy_insert_end?><?oxy_delete author="dawnstevens" timestamp="20240507T080115-0600" content=" value=&quot;prohibited&quot;/"?>><?oxy_insert_start author="dawnstevens" timestamp="20240507T080118-0600"?>Do not use. This acronym is commonly used
+         to stand for "unique factorization domain."&lt;/glossStatus><?oxy_insert_end?>
     &lt;/glossAlt>
     &lt;glossAlt id="memoryStick">
       &lt;glossSynonym>memory stick&lt;/glossSynonym>
-      &lt;glossUsage>This is a colloquial term.&lt;/glossUsage>
+      &lt;glossUsage><?oxy_insert_start author="dawnstevens" timestamp="20240507T080421-0600"?>Do not use. <?oxy_insert_end?>This <?oxy_insert_start author="dawnstevens" timestamp="20240507T080444-0600"?>synonym <?oxy_insert_end?>is a colloquial term.&lt;/glossUsage>
     &lt;/glossAlt>
     &lt;glossAlt>
-      &lt;glossAbbreviation>stick&lt;/glossAbbreviation>
-      &lt;glossStatus value="prohibited"/>
-      &lt;glossUsage>This is too colloquial.&lt;/glossUsage>
-      &lt;glossAlternateFor href="#usbfd/memoryStick"/>
+      &lt;gloss<?oxy_delete author="dawnstevens" timestamp="20240507T080501-0600" content="Abbreviatio"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080501-0600"?>Acronym<?oxy_insert_end?>n>stick&lt;/glossA<?oxy_delete author="dawnstevens" timestamp="20240507T080506-0600" content="bbreviation"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080506-0600"?>cronym<?oxy_insert_end?>>
+      <?oxy_delete author="dawnstevens" timestamp="20240507T080136-0600" content="&amp;lt;glossStatus value=&quot;prohibited&quot;/&gt;
+      "?>&lt;glossUsage><?oxy_insert_start author="dawnstevens" timestamp="20240507T080426-0600"?>Do not use. <?oxy_insert_end?>This <?oxy_insert_start author="dawnstevens" timestamp="20240507T080512-0600"?>short form <?oxy_insert_end?>is too <?oxy_delete author="dawnstevens" timestamp="20240507T080450-0600" content="colloquial"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080450-0600"?>vague<?oxy_insert_end?>.&lt;/glossUsage>
+      <?oxy_delete author="dawnstevens" timestamp="20240507T080144-0600" content="&amp;lt;glossAlternateFor href=&quot;#usbfd/memoryStick&quot;/&gt;"?>
     &lt;/glossAlt>
     &lt;glossAlt>
-      &lt;glossAbbreviation>flash&lt;/glossAbbreviation>
-      &lt;glossStatus value="prohibited"/>
-      &lt;glossUsage>This short form is ambiguous.&lt;/glossUsage>
+      &lt;glossA<?oxy_delete author="dawnstevens" timestamp="20240507T080152-0600" content="bbreviation"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080152-0600"?>cronym<?oxy_insert_end?>>flash&lt;/glossA<?oxy_delete author="dawnstevens" timestamp="20240507T080155-0600" content="bbreviation"?><?oxy_insert_start author="dawnstevens" timestamp="20240507T080155-0600"?>cronym<?oxy_insert_end?>>
+      <?oxy_delete author="dawnstevens" timestamp="20240507T080201-0600" content="&amp;lt;glossStatus value=&quot;prohibited&quot;/&gt;"?>
+      &lt;glossUsage><?oxy_insert_start author="dawnstevens" timestamp="20240507T080433-0600"?>Do not use. <?oxy_insert_end?>This short form is ambiguous.&lt;/glossUsage>
     &lt;/glossAlt>
   &lt;/glossBody><b>
 &lt;/glossentry>
@@ -89,3 +96,4 @@
     </example>
   </refbody>
 </reference>
+<?oxy_options track_changes="on"?>
\ No newline at end of file