[css-view-transitions-1] Fix spec text for suppressing rendering. (#8328)

* Fix spec text for suppressing rendering

* Update Overview.bs

* Whitespace tweak

Co-authored-by: Jake Archibald <jaffathecake@gmail.com>

Author: khushalsagar

css-view-transitions-1/Overview.bs

@@ -682,21 +682,12 @@ urlPrefix: https://html.spec.whatwg.org/multipage/rendering.html; type: dfn;
 	</div>
 
 	<div algorithm="suppress rendering">
-		1. For each {{Document}} in <var ignore>docs</var> with a [=document/transition suppressing rendering=] of true:
-
-			Issue: Move this to the html spec.
-				See [html/8368](https://github.com/whatwg/html/pull/8368/files).
-
-			Issue: How should input be handled when in this state?
-				The last frame presented to the user will not reflect the DOM state as it asynchronously switches to the new version.
-				See [issue 7797](https://github.com/w3c/csswg-drafts/issues/7797).
-
-			Note: The aim is to prevent unintended DOM updates from being presented to the user after a cached snapshot for the elements has been captured.
-				We wait for one [=rendering opportunity=] after prepare to present DOM mutations made by the author before prepare to be presented to the user.
-				This is also the content captured in snapshots.
+		In the definition for [=rendering opportunity=], add the following condition:
+		
+		A navigable has no rendering opportunities if active document has [=document/transition suppressing rendering=] set to true.
 
 		Note: These steps will be added to the [=update the rendering=] in the HTML spec.
-			As such, the prose style is written to match other steps in that algorithm.
+		      See <a href="https://github.com/w3c/csswg-drafts/issues/7784">#7884</a> for more context.
 	</div>
 
 ## [=Perform pending transition operations=] ## {#perform-pending-transition-operations-algorithm}