[css-display-3] Fix indentation. Whitespace-only change.

Author: fantasai

css-display-3/Overview.bs

@@ -1169,69 +1169,66 @@ SVG Elements {#unbox-svg}
 ---------------------------
 
 	: An <{svg}> element that has CSS box layout
-      (this includes all <{svg}> whose parent is an HTML element,
-       as well as document root elements)
+		(this includes all <{svg}> whose parent is an HTML element,
+		as well as document root elements)
 	::
 		''display: contents'' behaves as ''display: none''.
 
 	: All other SVG [=container elements=] that are also [=renderable elements=]
-    : SVG [=text content child elements=]
-    : <{use}>
+	: SVG [=text content child elements=]
+	: <{use}>
 	::
 		''display: contents'' strips the element from the formatting tree,
 		and hoists its contents up to display in its place.
-        These contents include the shadow-DOM content for <{use}>.
+		These contents include the shadow-DOM content for <{use}>.
 
 	: any other SVG elements
 	::
 		''display: contents'' behaves as ''display: none''.
-        
-  When an element is stripped from the formatting tree,
-  then any SVG attributes on that element
-  that control the layout and formatting of its child content
-  (or shadow DOM content)
-  are ignored when rendering the contents.
-  However, SVG [=presentation attributes=]
-  continue to affect CSS property inheritance,
-  the same as CSS styles set in any other way.
-  
-  Issue(w3c/csswg-drafts#2502):
-  Is this description clear enough to identify
-  the SVG attributes affected by ''display: contents''?
-  
-
-  <div class="note">
-  
-	The intention here is that 
-    the ''display: none'' behavior applies
-    whenever the "rendering context" inside the element
-    is different than the context outside of it.
-    If the element's child elements would not be valid children
-    of the element's parent,
-    you cannot simply hoist them up the formatting tree.
-    
-    For example, text content and text formatting elements in SVG
-    require a <{text}> element context;
-    if you remove a <{text}>,
-    its child text content and elements are no longer valid.
-    For that reason, ''display: contents'' on <{text}>
-    prevents the entire text element from being rendered.
-    In contrast, any content inside a <{tspan}> or <{textPath}>
-    is also valid content inside the parent text formatting context,
-    so the hoisting behavior applies for these elements.
-    
-    Similarly, if hoisting would convert the children from
-    [=non-rendered elements=]
-    (e.g., a shape inside a <{pattern}> or <{symbol}>)
-    to [=rendered elements=]
-    (e.g., a shape that is a direct child of the <{svg}>),
-    that is an invalid change of rendering context.
-    Never-rendered container elements therefore cannot be "un-boxed"
-    by ''display: contents''.
-    (Also, authors cannot override the 'display' property on these elements:
-    it is forced to ''none'' by an ''!important'' user agent style rule.)
-    
- </div>
+
+	When an element is stripped from the formatting tree,
+	then any SVG attributes on that element
+	that control the layout and formatting of its child content
+	(or shadow DOM content)
+	are ignored when rendering the contents.
+	However, SVG [=presentation attributes=]
+	continue to affect CSS property inheritance,
+	the same as CSS styles set in any other way.
+
+	Issue(w3c/csswg-drafts#2502):
+	Is this description clear enough to identify
+	the SVG attributes affected by ''display: contents''?
+
+	<div class="note">
+		The intention here is that
+		the ''display: none'' behavior applies
+		whenever the "rendering context" inside the element
+		is different than the context outside of it.
+		If the element's child elements would not be valid children
+		of the element's parent,
+		you cannot simply hoist them up the formatting tree.
+
+		For example, text content and text formatting elements in SVG
+		require a <{text}> element context;
+		if you remove a <{text}>,
+		its child text content and elements are no longer valid.
+		For that reason, ''display: contents'' on <{text}>
+		prevents the entire text element from being rendered.
+		In contrast, any content inside a <{tspan}> or <{textPath}>
+		is also valid content inside the parent text formatting context,
+		so the hoisting behavior applies for these elements.
+
+		Similarly, if hoisting would convert the children from
+		[=non-rendered elements=]
+		(e.g., a shape inside a <{pattern}> or <{symbol}>)
+		to [=rendered elements=]
+		(e.g., a shape that is a direct child of the <{svg}>),
+		that is an invalid change of rendering context.
+		Never-rendered container elements therefore cannot be "un-boxed"
+		by ''display: contents''.
+		(Also, authors cannot override the 'display' property on these elements:
+		it is forced to ''none'' by an ''!important'' user agent style rule.)
+	</div>
 
 
 MathML Elements {#unbox-mathml}