From 6a459aae51381e6e8b0ba30b72eec87aede9c032 Mon Sep 17 00:00:00 2001 From: Philipp Parzer <74797907+philparzer@users.noreply.github.com> Date: Wed, 13 Apr 2022 21:35:56 +0200 Subject: [PATCH] docs: fix typo 'reboostrap' to 'rebootstrap' --- docs/pages/guide/mental-model.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/guide/mental-model.mdx b/docs/pages/guide/mental-model.mdx index 844dc3e3ff3..45edbf3011b 100644 --- a/docs/pages/guide/mental-model.mdx +++ b/docs/pages/guide/mental-model.mdx @@ -32,9 +32,9 @@ All applications have a main entry point to get the application going. We call t On hydration, the bootstrap again takes a root component and calls a framework method to resume the current HTML (meaning re-attach the listeners as well as rebuild the framework internal state about the application component tree.) -Qwik does not need to do hydration. Qwik still has a bootstrap method, but that typically executes on the server to render the initial application. There is no reboostrap on the client. Instead, Qwik serializes not only the application state into HTML but also the framework state as well. The serialized state allows the Qwik framework to continue execution where the server left off. Not requiring a reboostrap is what makes Qwik resumable. +Qwik does not need to do hydration. Qwik still has a bootstrap method, but that typically executes on the server to render the initial application. There is no rebootstrap on the client. Instead, Qwik serializes not only the application state into HTML but also the framework state as well. The serialized state allows the Qwik framework to continue execution where the server left off. Not requiring a rebootstrap is what makes Qwik resumable. -If the Qwik application required a reboostrap in the browser, they would require pulling the root component and, with it, all child components. This would require an early download of the application code, the exact thing that Qwik aims to avoid. +If the Qwik application required a rebootstrap in the browser, they would require pulling the root component and, with it, all child components. This would require an early download of the application code, the exact thing that Qwik aims to avoid. ## 4. State