some details on paint order

src/components/starlight/Head.astro

@@ -12,8 +12,6 @@ import MarkTitle from '../bot/MarkTitle.astro';
 import SilentCatch from '../bot/SilentCatch.astro';
 import SwapSound from '../bot/SwapSound.astro';
 import PagefindToTextFragments from './PagefindToTextFragments.astro';
-import 'astro-vtbot/components/ReplacementSwap.astro';
-import 'astro-vtbot/components/starlight/StarlightConnector.astro';
 import SidebarSelect from './SidebarSelect.astro';
 
 import '../../styles/vt.css';

src/content/docs/jotter/api/details.mdx

@@ -145,6 +145,8 @@ This is a more elaborated description of what the `startViewTransitions()` funct
 <Steps>
 
 1. In the capture phase, the browser saves a bitmap of the current state for each HTML element that has a `view-transition-name` CSS property. This can later be addressed using the `::view-transition-old(<name>)` pseudo element. Together with the image data, further CSS properties are recorded[^1]. \
+	 \
+	 For the captures, elements are ordered from bottom to top starting at the lowest `z-index`. While capturing an image, other elements of "higher" images are not painted and thus the capture shows the element's background in these areas. \
    \
    All `view-transition-name` values used in the document must be unique. Otherwise the view transition is aborted (after calling the _update callback_, see next step).
 

src/content/docs/jotter/snippets/things-to-write-about.mdx

@@ -29,3 +29,4 @@ title: Things to write about when I find the time to do so and there are no othe
 
 * how to have the view transition move **behind** some elements in the front?
 
+* how to set break points to investigate the pseudo elements