fix(docs): improve wording in problem oultine section (#6931)

packages/docs/src/routes/docs/(qwik)/concepts/think-qwik/index.mdx

@@ -46,9 +46,9 @@ Modern websites require vast amounts of JavaScript to become interactive. Too mu
 1. **Network bandwidth**: A large amount of code is shipped to the client, which may take a long time on slow networks.
 2. **Startup time**: Once on the client, the code needs to be executed (as part of hydration) to get the site interactive.
 
-As Qwik applications get more complex with a higher fidelity of interactivity, the amount of code has steadily increased over the years, with no sign of stopping. Simply put, Qwik sites are getting more complex. An increase in site complexity, in turn, requires more code. All of this code negatively impacts site startup performance.
+As applications get more complex with a higher fidelity of interactivity, the amount of code being shipped has steadily increased over the years, with no sign of stopping. Simply put, websites are getting more complicated. An increase in site complexity, in turn, requires more code. All of this code negatively impacts site startup performance.
 
-To make matters worse, JavaScript is single-threaded; therefore, Qwik’s complex sites can't take advantage of modern multi-core CPUs.
+To make matters worse, JavaScript is single-threaded; therefore, complex sites can't take advantage of modern multi-core CPUs.
 
 ### How did we get here?