Skip to content

Commit 1bce01b

Browse files
authored
docs: clarify wording (#6990)
clarify wording The original text wrongly implied that Qwik's tools increase JavaScript, which goes against what Qwik is all about. I reworded it to clarify that the issue applies to general tools, not Qwik's.
1 parent 94ee2b4 commit 1bce01b

File tree

1 file changed

+1
-1
lines changed
  • packages/docs/src/routes/docs/(qwik)/concepts/think-qwik

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ The solution to the above problem is both obvious and hard: Ship less JavaScript
5656

5757
The obvious part is that sites with less JavaScript will perform better.
5858

59-
The hard part is our tools don't help us to get there. The majority of Qwik's tools solve problems in a way that makes shipping less JavaScript hard. These tools are designed to solve a specific problem without thinking about the amount of JavaScript they generate.
59+
The hard part is that our tools don't help us achieve this. Most of them solve problems in a way that makes shipping less JavaScript hard. These tools are designed to address specific issues without considering how much JavaScript they produce.
6060

6161
Do you need to solve rendering, styling, animation, A/B testing, analytics, etc.? There is a tool for that. Just import or add a `<script>` tag, and these tools will solve your problems, but at the expense of making the initial bundle bigger.
6262

0 commit comments

Comments
 (0)