typos

Author: martrapp

src/content/docs/basics/levels.mdx

@@ -39,7 +39,7 @@ Part two indeed adds extensions for cross-document view transitions, but also fe
 ### Cross-Document
 * The `@view-transition{ navigation: auto }` at-rule to opt in to [cross-document view transitions](/basics/javascript/#cross-document-view-transitions). 
 * `pageswap` and `pagereveal` [events](/basics/javascript/#pageswap-and-pagereveal-events) that give access to the view transition object on the old and new page.
-* An [`activation`](/basics/javascript/#activation-object) property on `pageswap` holds a `NavigationActivation` object from the Navigation API. There are no equivalent on properties on `pagereveal`. Use `navigation.activation` from the Navigation API instead.
+* An [`activation`](/basics/javascript/#activation-object) property on `pageswap` holds a `NavigationActivation` object from the Navigation API. There are no equivalent properties on `pagereveal`. Use `navigation.activation` from the Navigation API instead.
 
 ### Extensions for Both, Same- and Cross-Document 
 * The [`view-transition-class`](/basics/styling/#with-classes) property and selector syntax to address multiple pseudo-elements with a single selector.

src/content/docs/tips/view-transition-fails-and-fixes.mdx

@@ -429,7 +429,7 @@ Typically, browsers suppress view transitions on navigation if they already have
 
 The `popstate` and `navigation` events have a `hasUAVisualTransition` property which you can use to skip your own view transitions when the browser has already started a native one.
 
-Sadly, `popstate` does not fire for cross-document navigation, and evn though it is now baseline not all browsers versions support the Navigation API.
+Sadly, `popstate` does not fire for cross-document navigation, and even though it is now baseline, not all browsers versions support the Navigation API.
 
 As a last resort, you could completely skip view transitions when the `activation.navigationType` of the `pageswap` event equals `'traverse'`.