typo

Author: fantasai

css-display-3/issues-cr-2020.bsi

@@ -52,7 +52,7 @@ Resolved: https://www.w3.org/2020/09/17-css-minutes#item04
 Resolved: https://lists.w3.org/Archives/Public/www-style/2021Apr/0002.html
 ----
 Issue 6.
-Summary:  Sould  values be aliased at parse time?
+Summary:  Should  values be aliased at parse time?
 From:     Oriol Brufau
 Comment:  https://github.com/w3c/csswg-drafts/issues/5575
 Response: https://github.com/w3c/csswg-drafts/issues/5575#issuecomment-893899115

css-display-3/issues-cr-2020.html

@@ -92,7 +92,7 @@ CSS Display Module Level 3 Disposition of Comments for 2020-05-19 CR
 <span>Resolved: <a href='https://lists.w3.org/Archives/Public/www-style/2021Apr/0002.html'>https://lists.w3.org/Archives/Public/www-style/2021Apr/0002.htmla> <a href="https://www.w3.org/Mail/flatten/index?subject=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fwww-style/2021Apr/0002.html"><abbr title="Thread">∈abbr>a>span>pre>
 <pre class='open ' id='issue-6'>
 <span>Issue 6. <a href='#issue-6'>#a>span>
-<span>Summary:  Sould <display-legacy> values be aliased at parse time?span>
+<span>Summary:  Should <display-legacy> values be aliased at parse time?span>
 <span>From:     Oriol Brufauspan>
 <span>Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/5575'>https://github.com/w3c/csswg-drafts/issues/5575a>span>
 <span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/5575#issuecomment-893899115'>https://github.com/w3c/csswg-drafts/issues/5575#issuecomment-893899115a>span>