fix: standardize capitalization of "Level" in documentation

Author: martrapp

src/content/docs/basics/levels.mdx

@@ -9,18 +9,19 @@ head:
 ---
 The (preliminary) View Transition API's specification comes in two parts: 
 
-
 * Level 1: *CSS View Transitions Module Level 1* (Editor's Draft) [https://drafts.csswg.org/css-view-transitions-1/](https://drafts.csswg.org/css-view-transitions-1/)
 
 * Level 2: *CSS View Transitions Module Level 2* (Editor's Draft) [https://drafts.csswg.org/css-view-transitions-2/](https://drafts.csswg.org/css-view-transitions-2/)
 
-Splitting the specification into two parts allows browser vendors to roll out the API incrementally.
+Nowadays, the Level 1 document is frozen, while the Level 2 document is still in development. 
+
+Splitting the specification into two parts allowed browser vendors to roll out the API incrementally.
 
 You might often hear that 
 * Level 1 is _same-document_ view transitions and 
 * Level 2 defines _cross-document_ view transitions
 
-It is a neat, memorable way to explain it.  Half‑true, slightly wrong, but sticky enough to spread. Just do not forget: the real implications still hide in the details.
+It is a neat, memorable way to explain it.  Half-true, slightly wrong, but sticky enough to spread. Just do not forget: the real implications still hide in the details.
 
 I prefer to think of Level 1 as the core and Level 2 as the extensions.
 
@@ -57,7 +58,7 @@ Part two indeed adds extensions for cross-document view transitions, but also fe
 
 The new features defined in Level 2 of the view transition API are in deed written as extensions to the Level 1 spec. They can easily be merged into one specification. But the interesting part here is not the document structure but the implication from incremental releasing of the two parts.
 
-Up to now, all vendors have implemented and released Level 1 first before they went on to Level2. For Chrome and Edge there was a period of over 12 month before level 2 got released. For Safari, it had been 3 month. Firefox just released Level 1 of the API as it is part of Interop 2025. It's unclear when Level 2 will be released.
+Up to now, all vendors have implemented and released Level 1 first before they went on to Level 2. For Chrome and Edge there was a period of over 12 month before Level 2 got released. For Safari, it had been 3 month. Firefox released Level 1 of the API last year, as it was part of Interop 2025. It's unclear when Level 2 will be released.
 
 For the Chromium based browsers, this was not a problem as when they released Level 1 support there where no other browsers that understood Level 2. When Safari came out, this was different, but it did not take that lon for them to deliver Level 2 after that.
 

src/content/docs/basics/styling.mdx

@@ -12,7 +12,7 @@ import { Steps } from "@astrojs/starlight/components";
 
 The animations introduced by the View Transition API are controlled by CSS rules. The way to make the animations fit your expectations is to alter the [default animation](/basics/default-animations/) by overriding the styles for the [pseudo elements](/basics/pseudos/).
 
-To do this efficiently you should know what the View Transition API defines as defaults and how to easily change these styles if needed. To simplify styling, level 2 of the API introduced helpers in form of the `view-transition-class` property and the `:active-view-transition...` pseudo-classes.
+To do this efficiently you should know what the View Transition API defines as defaults and how to easily change these styles if needed. To simplify styling, Level 2 of the API introduced helpers in form of the `view-transition-class` property and the `:active-view-transition...` pseudo-classes.
 
 ## Styling Tasks for View Transitions
 

src/content/docs/vtbag.mdx

@@ -74,16 +74,16 @@ Remember a tech-demo, but not where it is buried on this site? Open the _All Tec
 
 @vtbag is all about the View Transition API. Find out [more about this browser API](/basics/api/).
 
-The content part of this site is build with [Starlight](https://starlight.astro.build/). The view transitions featured on this site and tech demos are independent of Astro. They only use the View Transition API and require browsers with native support for it. Cross document effects need a [level 2 compliant browser](https://events-3bg.pages.dev/jotter/api/test-page/).
+The content part of this site is build with [Starlight](https://starlight.astro.build/). The view transitions featured on this site and tech demos are independent of Astro. They only use the View Transition API and require browsers with native support for it. Cross document effects need a [Level 2 compliant browser](https://events-3bg.pages.dev/jotter/api/test-page/).
 
 ## Relation to astro-vtbot
 
-Some of you might be familiar with [astro-vtbot](https://events-3bg.pages.dev), the big sister, or at least the spiritual predecessor, of `@vtbag`: Even when the same-document (level 1) View Transition API in Chrome was only accessible behind a flag, the Astro project had already anticipated parts of the level 2 specification, enabling cross-document view transitions for MPAs. Of course, Astro's client-side router isn't technically comparable to level 2 view transitions and has its own challenges in handling scripts and state, but it allowed many users to experiment early and build expertise in view transitions.
+Some of you might be familiar with [astro-vtbot](https://events-3bg.pages.dev), the big sister, or at least the spiritual predecessor, of `@vtbag`: Even when the same-document (Level 1) View Transition API in Chrome was only accessible behind a flag, the Astro project had already anticipated parts of the Level 2 specification, enabling cross-document view transitions for MPAs. Of course, Astro's client-side router isn't technically comparable to Level 2 view transitions and has its own challenges in handling scripts and state, but it allowed many users to experiment early and build expertise in view transitions.
 
 Astro-vtbot, as a community project, built on that foundation by offering technical demos, reusable components, and a wealth of tips and tricks for using view transitions in Astro projects.
 
 ## Another Bag of Tricks
-With the wider adoption of the view transition API and the introduction of level 2, cross-document transitions can now be defined purely with CSS, without the need for an additional client-side router. `@vtbag` is your go-to resource for framework-agnostic support around view transitions.
+With the wider adoption of the view transition API and the introduction of Level 2, cross-document transitions can now be defined purely with CSS, without the need for an additional client-side router. `@vtbag` is your go-to resource for framework-agnostic support around view transitions.
 
 `@vtbag` inherits the concept of a Bag of Tricks from astro-vtbot: a diverse collection of tricks, tips, components, and tools. While astro-vtbot continues to focus on the specific needs of the Astro router, `@vtbag` aims at the view transition API in general, without being tied to any specific framework.