[css-text-3] Editorial: punctuation

Consistant usage of curly quotes

Author: frivoal

css-text-3/Overview.bs

@@ -218,7 +218,7 @@ Languages and Typesetting</h3>
 	The [=content language=] an element is declared to be in
 	also identifies the specific written form of that language used in that element,
 	known as the <dfn export local-lt="writing system">content writing system</dfn>.
-	Depending on the [=document language=]'s facilities for identifying the [=content language=],
+	Depending on the [=document language=]’s facilities for identifying the [=content language=],
 	this information can be explicit or implied.
 	See the normative [[#script-tagging]].
 
@@ -764,7 +764,7 @@ Mapping Rules</h4>
 	then any appropriate language-specific rules must be applied as well.
 	These minimally include,
 	but are not limited to,
-	the language-specific rules in Unicode's
+	the language-specific rules in Unicode’s
 	<a href="http://www.unicode.org/Public/UNIDATA/SpecialCasing.txt">SpecialCasing.txt</a>.
 
 	<wpt>
@@ -803,7 +803,7 @@ Mapping Rules</h4>
 		(or another Turkic language that uses Turkish casing rules);
 		in other languages,
 		the usual mapping of &ldquo;I&rdquo; and &ldquo;i&rdquo; is required.
-		This rule is thus conditionally defined in Unicode's SpecialCasing.txt file.
+		This rule is thus conditionally defined in Unicode’s SpecialCasing.txt file.
     </div>
 
 	<wpt pathprefix="/css/CSS2/text/">
@@ -1573,7 +1573,7 @@ The White Space Processing Rules</h3>
 	(part of the CSS syntax)
 	are not necessarily identical.
 	However, since both include spaces (U+0020), tabs (U+0009), and line feeds (U+000A)
-	most authors won't notice any differences.
+	most authors won’t notice any differences.
 
 	Besides Space (U+0020)
 	and No-Break Space (U+00A0),
@@ -2173,7 +2173,7 @@ Phase II: Trimming and Positioning</h4>
 		they are not considered when placing the rest of the line during text alignment.
 		When aligning towards the end,
 		this means any such [=spaces=] will overflow,
-		and will not prevent the rest of the line's content from being flush with the edge of the line.
+		and will not prevent the rest of the line’s content from being flush with the edge of the line.
 		On the other hand,
 		preserved spaces at the end of a line <em>with</em> a forced break
 		[=conditionally hang=].
@@ -3326,7 +3326,7 @@ Breaking Rules for Letters: the 'word-break' property</h3>
 	are affected the same way as those letters.
 
 	<div class="example">
-		Here's a mixed-script sample text:
+		Here’s a mixed-script sample text:
 
 		<pre style="white-space: pre-wrap">
 			这是一些汉字 and some Latin <bdi dir=rtl>و کمی خط عربی</bdi> และตัวอย่างการเขียนภาษาไทย በጽሑፍ፡ማራዘሙን፡አንዳንድ፡
@@ -4507,7 +4507,7 @@ Text Alignment: the 'text-align' shorthand</h3>
 		<dt><dfn>match-parent</dfn>
 		<dd>
 			This value behaves the same as ''inherit''
-			(computes to its parent's computed value)
+			(computes to its parent’s computed value)
 			except that an [=inherited value=] of ''start'' or ''end''
 			is interpreted against the parent’s
 			(or the [=initial containing block=]’s,
@@ -4543,7 +4543,7 @@ Text Alignment: the 'text-align' shorthand</h3>
 	the UA may stretch or shrink any inline boxes
 	by [[#text-justify-property|adjusting]] their text.
 	(See 'text-justify'.)
-	If an element's [=white space=] is not [=collapsible=],
+	If an element’s [=white space=] is not [=collapsible=],
 	then the UA is not required to adjust its text
 	for the purpose of justification
 	and may instead treat the text
@@ -4563,8 +4563,8 @@ Text Alignment: the 'text-align' shorthand</h3>
 	If (after justification, if any)
 	the inline contents of a line box are too long to fit within it,
 	then the contents are <a spec=css-writing-modes-3>start</a>-aligned:
-	any content that doesn't fit
-	overflows the line box's <a spec=css-writing-modes-3>end</a> edge.
+	any content that doesn’t fit
+	overflows the line box’s <a spec=css-writing-modes-3>end</a> edge.
 
 	See [[#bidi-linebox]] for details on how to determine
 	the <a spec=css-writing-modes-3>start</a> and <a spec=css-writing-modes-3>end</a> edges
@@ -4674,7 +4674,7 @@ Justification Method: the 'text-justify' property</h3>
 	</wpt>
 
 	This property selects the justification method
-	used when a line's alignment is set to ''justify''
+	used when a line’s alignment is set to ''justify''
 	(see 'text-align').
 	The property applies to inlines,
 	but is inherited from block containers
@@ -4755,7 +4755,7 @@ Justification Method: the 'text-justify' property</h3>
 					expanding at spaces as well as between CJK and Southeast Asian letters.
 					This effectively uses inter-word + inter-ideograph spacing
 					for lines that have word-separators and/or CJK characters
-					and falls back to inter-cluster behavior for lines that don't
+					and falls back to inter-cluster behavior for lines that don’t
 					or for which the space stretches too far.
 				</figcaption>
 			</figure>
@@ -4861,7 +4861,7 @@ Expanding and Compressing Text</h4>
 
 	When justifying text,
 	the user agent takes the remaining space
-	between the ends of a line's contents and the edges of its line box,
+	between the ends of a line’s contents and the edges of its line box,
 	and distributes that space throughout its content
 	so that the contents exactly fill the line box.
 	The user agent may alternatively distribute negative space,
@@ -4929,7 +4929,7 @@ Handling Symbols and Punctuation</h4>
 	a [=typographic character unit=]
 	from the Unicode Symbols (S*) and Punctuation (P*) classes
 	is generally treated the same as a [=typographic letter unit=] of the same script
-	(or, if the character's script property is Common,
+	(or, if the character’s script property is Common,
 	then as a [=typographic letter unit=] of the dominant script).
 
 	However, by typographic tradition
@@ -5520,7 +5520,7 @@ Tracking: the 'letter-spacing' property</h3>
 
 		Since letter spacing is inserted <strong>after</strong> RTL reordering,
 		the letter spacing applied to the inner span below likewise has no effect,
-		since after reordering the "c" doesn't end up next to "&#x5d0;":
+		since after reordering the "c" doesn’t end up next to "&#x5d0;":
 
 		<pre highlight=css>
 			p    { letter-spacing: 1em; }
@@ -5594,7 +5594,7 @@ Cursive Scripts</h4>
 	if the UA cannot expand text from a [=cursive script=]
 	without breaking its cursive connections,
 	it <em>must not</em> apply spacing
-	between any pair of that script's [=typographic letter units=] at all
+	between any pair of that script’s [=typographic letter units=] at all
 	(effectively treating each word as a single [=typographic letter unit=]
 	for the purpose of letter-spacing).
 	Both cases will result in an effective spacing of zero between such letters;
@@ -5766,7 +5766,7 @@ Shaping Across Element Boundaries</h3>
 		in many systems this is performed by the font engine,
 		allowing the font to provide variant glyphs
 		with potentially very sophisticated contextual shaping.
-		It's not generally possible to rely on this system across a font change
+		It’s not generally possible to rely on this system across a font change
 		unless the font engine has an API to provide context,
 		but it is straightforward and therefore quite reasonable
 		for an engine to work around this limitation by, for example,
@@ -5792,7 +5792,7 @@ Shaping Across Element Boundaries</h3>
 		with an ampersand glyph (“&amp;”).
 
 		<!--
-			It's simply not possible for the UA
+			It’s simply not possible for the UA
 			to create the effect of a partway-bold single glyph.
 		-->
 	</div>
@@ -6044,7 +6044,7 @@ First Line Indentation: the 'text-indent' property</h3>
 		In the following example, 'text-indent'
 		is given a value of ''3em hanging each-line'',
 		giving the third line of the poem a hanging indent
-		where it soft-wraps at the block's right boundary:
+		where it soft-wraps at the block’s right boundary:
 
 		<pre class="output">
 			In a short line of text
@@ -6059,16 +6059,16 @@ First Line Indentation: the 'text-indent' property</h3>
 	Note: Since the 'text-indent' property inherits,
 	when specified on a block element, it will affect descendant
 	inline-block elements.
-	For this reason, it is often wise to specify 'text-indent: 0' on
-	elements that are specified 'display: inline-block'.</p>
+	For this reason, it is often wise to specify ''text-indent: 0'' on
+	elements that are specified ''display: inline-block''.</p>
 
 <h3 id="hanging">
 Hanging Glyphs</h3>
 
 	When a glyph at the start or end edge of a line <dfn lt="hang">hangs</dfn>,
 	it is not considered
-	when measuring the line's contents for fit, alignment, or justification.
-	Depending on the line's alignment/justification, this can
+	when measuring the line’s contents for fit, alignment, or justification.
+	Depending on the line’s alignment/justification, this can
 	result in the mark being placed outside the line box.
 	The [=hanging=] glyph is also not taken into account
 	when computing [=intrinsic sizes=] ([=min-content size=] and [=max-content size=]),
@@ -6085,7 +6085,7 @@ Hanging Glyphs</h3>
 	and still participates in text justification:
 	its character advance is just not measured when determining
 	how much content fits on the line,
-	how much the line's contents need to be expanded or compressed for justification,
+	how much the line’s contents need to be expanded or compressed for justification,
 	or how to position the content within the line box for text alignment.
 	Effectively, the [=hanging=] glyph character advance
 	is re-interpreted as an additional negative margin
@@ -6290,7 +6290,7 @@ Bidirectionality and Line Boxes</h3>
 	as applied by [[CSS-WRITING-MODES-3]]).
 
 	In most cases, a [=line box=]’s [=inline base direction=]
-	is given by its [=containing block=]'s computed 'direction'.
+	is given by its [=containing block=]’s computed 'direction'.
 	However,
 	if its [=containing block=] has ''unicode-bidi: plaintext''
 	[[!CSS-WRITING-MODES-3]]:
@@ -6300,7 +6300,7 @@ Bidirectionality and Line Boxes</h3>
 			If the [=bidi paragraph=] to which the [=line box=] belongs
 			(that is, the [=bidi paragraph=] for which the line box holds content)
 			has strong directionality,
-			the line box's [=inline base direction=] is that direction.
+			the line box’s [=inline base direction=] is that direction.
 
 		<li>
 			If the [=line box=] is empty
@@ -6508,7 +6508,7 @@ Scripts and Spacing</h2>
 			Arabic,
 			Mandaic,
 			Mongolian,
-			N'Ko,
+			N’Ko,
 			Phags Pa,
 			Syriac
 
@@ -6713,7 +6713,7 @@ Space-Discarding Unicode Characters</h2>
 		see [[#line-break-transform]].
 
 		In most cases, “unbreaking” a line of text requires joining them with a space,
-		but some writing systems don't use spaces
+		but some writing systems don’t use spaces
 		so such texts need to be joined without any space.
 		CSS uses the characters before and after to determine
 		whether to join lines with or without a space.
@@ -6740,7 +6740,7 @@ Space-Discarding Unicode Characters</h2>
 		* HTML/CSS
 		* Markdown
 		* TeX
-		* text editors' “unbreak lines” commands
+		* text editors’ “unbreak lines” commands
 	</details>
 CUT SEGMENT BREAK TRANSFORM -->
 
@@ -6771,7 +6771,7 @@ Identifying the Content Writing System</h2>
 	authors can disambiguate or indicate the use of an atypical writing system
 	with script subtags.
 	For example, to indicate use of the Latin writing system
-	for languages which don't natively use it,
+	for languages which don’t natively use it,
 	the <code>-Latn</code> script subtag can be added,
 	e.g. <code>ja-Latn</code> for Japanese romaji.
 	Other subtags exist for other writing systems,
@@ -7278,7 +7278,7 @@ Privacy and Security Considerations</h2>
 
 	This specification introduces no new security considerations.
 
-	This specification leaks the user's installed hyphenation and line-breaking dictionaries.
+	This specification leaks the user’s installed hyphenation and line-breaking dictionaries.
 
 <h2 class="no-num" id="acknowledgements">
 Acknowledgements</h2>