[css-view-transitions-1] curly quotes

Author: fantasai

css-view-transitions-1/Overview.bs

@@ -155,7 +155,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 	1. Developer calls <code>document.{{Document/startViewTransition}}({{UpdateCallback|updateCallback}})</code>,
 		which returns <code>viewTransition</code>, a {{ViewTransition}}.
 
-	1. Current state captured as the "old" state.
+	1. Current state captured as the “old” state.
 
 	1. Rendering paused.
 
@@ -164,7 +164,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 
 	1. <code>viewTransition.{{ViewTransition/updateCallbackDone}}</code> fulfills.
 
-	1. Current state captured as the "new" state.
+	1. Current state captured as the “new” state.
 
 	1. Transition pseudo-elements created.
 		See [[#view-transition-pseudos]] for an overview of this structure.
@@ -337,7 +337,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 		}
 		```
 
-		By default, these groups will transition size and position from their "old" to "new" state,
+		By default, these groups will transition size and position from their “old” to “new” state,
 		while their visual states cross-fade:
 
 		<figure>
@@ -352,7 +352,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 			<video src="diagrams/videos/bad-sidebar.mp4" style="aspect-ratio: 1404/738" class="main-example-video" controls muted loop playsinline></video>
 		</figure>
 
-		In this case, things would look better if the sidebar was static if it was in both the "old" and "new" states.
+		In this case, things would look better if the sidebar was static if it was in both the “old” and “new” states.
 		Otherwise, it should animate in or out.
 
 		The '':only-child'' pseudo-class can be used to create animations specifically for these states:
@@ -379,7 +379,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 		}
 		```
 
-		For cases where the sidebar has both an "old" and "new" state, the default animation is correct.
+		For cases where the sidebar has both an “old” and “new” state, the default animation is correct.
 
 		<figure>
 			<video src="diagrams/videos/good-sidebar.mp4" style="aspect-ratio: 1404/738" class="main-example-video" controls muted loop playsinline></video>
@@ -391,7 +391,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 		let's say we wanted to create a circular reveal from the user's cursor.
 		This can't be done with CSS alone.
 
-		Firstly, in the CSS, allow the "old" and "new" states to layer on top of one another without the default blending,
+		Firstly, in the CSS, allow the “old” and “new” states to layer on top of one another without the default blending,
 		and prevent the default cross-fade animation:
 
 		```css
@@ -491,7 +491,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 	</dl>
 
 	Note: This property causes the user-agent to both capture separate snapshots from the elements,
-	as well as create separate pseudo-element sub-trees representing this element's "old" and "new" states.
+	as well as create separate pseudo-element sub-trees representing this element's “old” and “new” states.
 	For the purposes of this API,
 	if one element has a transition-name "foo" in the old state, and another element has a transition-name "foo" in the new state,
 	they are treated as representing different visual state of the same element.
@@ -595,7 +595,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 ## View transition pseudo-elements ## {#view-transition-pseudos}
 
 	<div class=note>
-		Once the user-agent has captured both the "old" and "new" states of the document,
+		Once the user-agent has captured both the “old” and “new” states of the document,
 		it creates a structure of pseudo-elements like the following:
 
 		```
@@ -612,7 +612,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 
 		For convenience, the [=document element=] is given the 'view-transition-name' "root" in the [[#ua-styles|user-agent style sheet]].
 
-		Either ''::view-transition-old()'' or ''::view-transition-new()'' are absent in cases where the capture does not have an "old" or "new" state.
+		Either ''::view-transition-old()'' or ''::view-transition-new()'' are absent in cases where the capture does not have an “old” or “new” state.
 
 		Each of the pseudo-elements generated can be targeted by CSS in order to customize its appearance,
 		behavior and/or add animations.
@@ -646,11 +646,11 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 ### <dfn>::view-transition-group( <<pt-name-selector>> )</dfn> ### {#::view-transition-group}
 
 	<div class=note>
-		This element initially mirrors the size and position of the "old" element,
-		or the "new" element if there isn't an "old" element.
+		This element initially mirrors the size and position of the “old” element,
+		or the “new” element if there isn't an “old” element.
 		It is always a [=tree/child=] of a ''::view-transition''.
 
-		If there's both an "old" and "new" state,
+		If there's both an “old” and “new” state,
 		styles in the [=document/view transition style sheet=] animate this pseudo-element's 'width' and 'height'
 		from the size of the old element's [=border box=] to that of the new element's [=border box=].
 
@@ -709,11 +709,11 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
 
 	<div class=note>
 
-		This element is a replaced element that produced the visual representation of the "old" state taken from user-agent provided snapshots.
+		This element is a replaced element that produced the visual representation of the “old” state taken from user-agent provided snapshots.
 
 		This is only ever a [=tree/child=] of a ''::view-transition-image-pair()'',
 		never has any [=tree/children=],
-		and is omitted if there's no "old" state to represent.
+		and is omitted if there's no “old” state to represent.
 
 		'':only-child'' can be used to match cases where this element is the only element in the ''::view-transition-image-pair()''.