diff --git a/publishing/docs/html/iframes.html b/publishing/docs/html/iframes.html
index 3f88d201..42c331b2 100644
--- a/publishing/docs/html/iframes.html
+++ b/publishing/docs/html/iframes.html
@@ -30,7 +30,7 @@ <h3>Techniques</h3>
 					<li>Ensure that the frame has a meaningful label (<code>aria-label</code>, <code>aria-labelledby</code> or <code>title</code>). [[WCAG-2.4.1]] and [[WCAG-4.1.2]]</li>
 					<li>Identify frames not intended for users in their label.</li>
 					<li>Use relative units to size the <code>iframe</code>.</li>
-					<li>Set scrolling to <code>auto</code>.</li>
+					<li>Ensure users can scroll the <code>iframe</code>.</li>
 				</ul>
 			</section>
 			
@@ -39,7 +39,7 @@ <h3>Example</h3>
 				<figure id="ex-01">
 					<figcaption><span class="label">Example 1 &#8212; A basic <code>iframe</code></span></figcaption>
 					<p>The <code>iframe</code> identifies that it contains a quiz in its <code>title</code> attribute.
-						It includes fallback content to reach the file for reading systems that don't support frames.</p>
+						It includes fallback content to reach the file for reading systems that do not support frames.</p>
 					<pre id="ex-01-src" class="prettyprint linenums"><code>&lt;iframe
       href="quiz01.xhtml"
       title="Quiz 1"
@@ -77,8 +77,11 @@ <h3>Explanation</h3>
 						embedded content (in a <code>title</code> attribute on the <code>iframe</code> element).</li>
 					<li>When setting the height and width of the <code>iframe</code>, a relative unit such as percentage or
 						ems should be used to facilitate resizing.</li>
-					<li>Scrolling should be set to <code>auto</code> so that if the user resizes the content in the frame
-						it can still be accessed if it becomes bigger than the available space.</li>
+					<li>Scrolling should not be disabled so that users can access content even if they resize it such that
+						it no longer fits within the visible space of the <code>iframe</code>. For example, do not set the
+						CSS <a 
+							href="https://drafts.csswg.org/css-overflow/#overflow-properties">overflow properties</a> on
+						the <code>iframe</code> to <code>clip</code> or <code>hidden</code>.</li>
 					<li>The <code>iframe</code> element should provide embedded fallback content for user agents that do
 						not support inline frames (e.g., a direct link to the content file).</li>
 					<li>If the frame does not contain content for the user, indicate as much in the <code>title</code>, set
diff --git a/publishing/docs/html/links.html b/publishing/docs/html/links.html
index ff5d74a1..15b0a3c9 100644
--- a/publishing/docs/html/links.html
+++ b/publishing/docs/html/links.html
@@ -96,9 +96,9 @@ <h3>Explanation</h3>
 					after reading a section. Without meaningful labels, the result can be a confusing mess of "see here" and
 					"read more" link text being offered with no indication of where those links go.</p>
 				
-				<p>To avoid this problem, always ensure that the text you hyperlink is meaningful on its own. If you can read
-					the link out of the context of its surrounding prose, and it clearly indicates where links to, you will
-					improve the experience for users using ATs.</p>
+				<p>To avoid this problem, always ensure that the text of the hyperlink is meaningful on its own. If you can
+					read the link out of the context of its surrounding prose, and it clearly indicates where links to, you
+					will improve the experience for users using ATs.</p>
 				
 				<p class="bridgehead">Overuse</p>
 				
diff --git a/publishing/docs/html/maps.html b/publishing/docs/html/maps.html
index 7db14fea..4533be1d 100644
--- a/publishing/docs/html/maps.html
+++ b/publishing/docs/html/maps.html
@@ -20,7 +20,7 @@
 			<section id="summary">
 				<h3>Summary</h3>
 				
-				<p>Ensure the areas of an image map are labelled so that the map is accessible to users who cannot cannot 
+				<p>Ensure the areas of an image map are labelled so that the map is accessible to users who cannot
 					see it or easily activate the regions.</p>
 			</section>