[css-text-3] corrections from publishing

Author: svgeesus

css-text-3/Overview.bs

@@ -7,6 +7,8 @@ Work Status: Refining
 Group: csswg
 ED: https://drafts.csswg.org/css-text-3/
 TR: https://www.w3.org/TR/css-text-3/
+Previous version: https://www.w3.org/TR/2020/CR-css-text-3-20201222/
+Previous version: https://www.w3.org/TR/2020/WD-css-text-3-20201119/
 Previous version: https://www.w3.org/TR/2020/WD-css-text-3-20200429/
 Previous version: https://www.w3.org/TR/2019/WD-css-text-3-20191113/
 Previous Version: https://www.w3.org/TR/2018/WD-css-text-3-20181212/
@@ -16,6 +18,7 @@ Previous Version: https://www.w3.org/TR/2017/WD-css-text-3-20170822/
 Previous Version: https://www.w3.org/TR/2013/WD-css-text-3-20131010/
 Test Suite: http://test.csswg.org/suites/css3-text/nightly-unstable/
 !Test Coverage Analysis: <a href="https://drafts.csswg.org/css-text-3/test-coverage">https://drafts.csswg.org/css-text-3/test-coverage</a>
+Implementation Report: https://test.csswg.org/harness/results/css-text-3_dev/grouped/
 Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
 Editor: Koji Ishii, Invited Expert, kojiishi@gluesoft.co.jp, w3cid 45369
 Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net, w3cid 43241
@@ -1276,7 +1279,7 @@ Order of Operations</h4>
 
     The source text of a document often contains formatting
     that is not relevant to the final rendering: for example,
-    <a href="http://rhodesmill.org/brandon/2012/one-sentence-per-line/">breaking the source into segments</a>
+    <a href="https://rhodesmill.org/brandon/2012/one-sentence-per-line/">breaking the source into segments</a>
     (lines) for ease of editing
     or adding [=white space characters=] such as [=tabs=] and [=spaces=] to indent the source code.
     CSS white space processing allows the author to control interpretation of such formatting:
@@ -3975,7 +3978,7 @@ Shaping Across Intra-word Breaks</h3>
     Inherited: yes
     Canonical order: n/a
     Animation type: discrete
-    </pre> 
+    </pre>
 
     <wpt>
       inheritance.html
@@ -4340,7 +4343,7 @@ Shaping Across Intra-word Breaks</h3>
                  title="Swash forms elongate the first line while a compressed contextual ligature shortens the second, allowing both to end precisely together."
                  src="images/text-justify-cursive.png"></p>
           <p class="caption">An example of cursively-justified Arabic text,
-          rendered by <a href="http://www.decotype.com/">Tasmeem</a>.
+          rendered by <a href="https://www.decotype.com/">Tasmeem</a>.
           Like English, Arabic can be justified by adjusting the spacing between words,
           but in most styles it can also be justified by calligraphically elongating or compressing the letterforms themselves.
           In this example, the upper text is extended to fill the line by the use of elongated (kashida) forms and swash forms,
@@ -5174,7 +5177,7 @@ Cursive Scripts</h4>
   Text shaping <em>must not</em> be broken across inline box boundaries
   when there is no effective change in formatting,
   or if the only formatting changes do not affect the glyphs
-  (as in applying <a href="https://www.w3.org/TR/css-text-decoration/">text decoration</a>).
+  (as in applying <a href="https://www.w3.org/TR/css-text-decor-3/">text decoration</a>).
 
   <wpt>
     text-transform/text-transform-shaping-001.html