[various][editorial] Remove a handful of unnecessary/incorrect genderings.

Author: tabatkins

css-color-4/Overview.bs

@@ -1694,7 +1694,7 @@ For historical reasons, this is also referred to as the X11 color set.
 
 Note: The history of the X11 color system is interesting,
 	and was excellently summarized by
-	<a href="https://www.youtube.com/watch?v=HmStJQzclHc">Alex Sexton in his talk “Peachpuffs and Lemonchiffons”</a>.
+	<a href="https://www.youtube.com/watch?v=HmStJQzclHc">Alex Sexton in their talk “Peachpuffs and Lemonchiffons”</a>.
 
 <wpt>
 named-001.html

css-images-3/issues-cr-2012.yaml

@@ -91,8 +91,8 @@ issue:
     openness: closed
     resolved: editorial
     notes: >-
-      Despite what Tab seems to be implying in the comment there, what he
-      actually did was restrict color stops to two colors. Either way, he
+      Despite what Tab seems to be implying in the comment there, what they
+      actually did was restrict color stops to two colors. Either way, they
       resolved the issue.
     tag: []
     filtered: []

css-text-3/Overview.bs

@@ -7140,7 +7140,7 @@ Bidirectionality and Line Boxes</h3>
 
 		<xmp highlight=html>
 			<para style="display: block; direction: rtl; unicode-bidi:plaintext">
-			“<quote style="unicode-bidi:plaintext">שלום!</quote>”, he said.
+			“<quote style="unicode-bidi:plaintext">שלום!</quote>”, they said.
 			</para>
 		</xmp>
 	</div>

css-text-4/Overview.bs

@@ -6653,7 +6653,7 @@ Character-based Alignment in a Table Column</h3>
 	is consistent with the cell's?
 	(Consistent in the alignment character, or fully consistent?)
 
-	<p class="issue">This behavior of aligning as though he alignment character
+	<p class="issue">This behavior of aligning as though the alignment character
 	had been inserted at the end of the contents of the cell,
 	combined with center-of-character alignment,
 	will produce gaps on the end-side of lines
@@ -9351,7 +9351,7 @@ Bidirectionality and Line Boxes</h3>
 
 		<xmp highlight=html>
 			<para style="display: block; direction: rtl; unicode-bidi:plaintext">
-			“<quote style="unicode-bidi:plaintext">שלום!</quote>”, he said.
+			“<quote style="unicode-bidi:plaintext">שלום!</quote>”, they said.
 			</para>
 		</xmp>
 	</div>

css-transforms-1/ChangeLog

@@ -57,7 +57,7 @@
 2014-01-25 Simon Fraser <simon.fraser@apple.com>
     Change to note that transforms do affect getClientRects() and 
     getBoundingClientRect(), and add a paragraph to the Module Interactions
-    section about his.
+    section about this.
 
     Also change wording of the note on transforms not affecting layout,
     to note that they do affect overflow.

css-transforms-2/Overview.bs

@@ -595,7 +595,7 @@ The box will be rotated toward the viewer, with the left edge staying fixed whil
 
 Mathematically, the top right vertex of the box was originally (100, &minus;50), relative to the transform-origin. It is first expanded to (100, &minus;50, 0, 1).  After applying the transform specified, this will get mapped to about (70.71, &minus;50, 70.71, &minus;0.4142). This has <var>w</var> = &minus;0.4142 &lt; 0, so we need to slice away the part of the box with <var>w</var> &lt; 0.  This results in the new top-right vertex being (50, &minus;50, 50, 0).  This is then mapped to some faraway point in the same direction, such as (5000, &minus;5000, 5000), which is up and to the right from the transform-origin.  Something similar is done to the lower right corner, which gets mapped far down and to the right. The resulting box stretches far past the edge of the screen.
 
-Again, the rendered box is still finite, so the user can scroll to see the whole thing if he or she chooses. However, the right part has been chopped off.  No matter how far the user scrolls, the rightmost ''30px'' or so of the original box will not be visible.  The blue border was only ''25px'' wide, so it will be visible on the left, top, and bottom, but not the right.
+Again, the rendered box is still finite, so the user can scroll to see the whole thing if they choose. However, the right part has been chopped off.  No matter how far the user scrolls, the rightmost ''30px'' or so of the original box will not be visible.  The blue border was only ''25px'' wide, so it will be visible on the left, top, and bottom, but not the right.
 
 The same basic procedure would apply if one or three vertices had <var>w</var> &lt; 0.  However, in that case the result of truncating the <var>w</var> &lt; 0 part would be a triangle or pentagon instead of a quadrilateral.
 

css2/Overview.bs

@@ -3675,7 +3675,7 @@ than <samp>[id=p123]</samp> in terms of the <a href="#assigning">cascade</a>.
 attribute contains an element's IDs is contained in a DTD. When
 parsing XML, UAs do not always read the DTD, and thus may not know
 what the ID of an element is. If a style sheet designer knows or
-suspects that this will be the case, he should use normal attribute
+suspects that this will be the case, they should use normal attribute
 selectors instead: <code>[name=p371]</code> instead of
 <code>#p371</code>. However, the cascading order of normal attribute
 selectors is different from ID selectors. It may be necessary to add
@@ -10221,7 +10221,7 @@ and lists</h2>
 <p>In some cases, authors may want user agents to render content
 that does not come from the <a href="#doctree">document
 tree</a>. One familiar example of this is a numbered list; the author
-does not want to list the numbers explicitly, he or she wants the
+does not want to list the numbers explicitly, they want the
 user agent to generate them automatically. Similarly, authors
 may want the user agent to insert the word
 "Figure" before the caption of a figure, or "Chapter 7" before the