not yet ready for publishing

Author: martrapp

src/content/docs/tips/concurrent.mdx

@@ -7,7 +7,7 @@ head:
       property: "og:image"
       content: "/concurrent-og.png"
 ---
-
+{/* 
 When a view transition starts while another view transition is still active, the former gets canceled.
 
 What does that mean and how can we improve this situation?
@@ -22,3 +22,4 @@ When a call is made to `startViewTransition` while the active view transition's
 former update callbacks.
 
 On the other hand, if the active view transition was `ready` and animations have been started, the active `::view-transition` pseudo-element tree is removed. This will stop all animations associated with the pseudo-elements and finally stop the active view transition. This looks like all animations abruptly skip to their end before the new view transition starts from there.
+*/}

src/content/docs/tips/scoped.mdx

@@ -2,6 +2,7 @@
 title: Isolated View Transitions
 description: "Keeping multiple view transitions separate and independent."
 ---
+{/* 
 When you use view transitions today, they always operate on the whole document. In the future, [_Scoped_ view transitions](/basics/javascript/#scoped-view-transitions) will allow you to confine them to a subtree of the DOM. While this is a planned extensions for the View Transition API, we are not there yet. Currently they are available in Chrome behind a flag.
 
 Scoped View Transitions will bring a lot of benefits:
@@ -63,3 +64,4 @@ The most reliable solution would be if each use case would only temporarily add
 this would only add the lightbox view transition name to the element with class
 
 
+*/}