docs(typo): fix typo javascript (#71175)

## 📚 Improving Documentation Hello, I've fixed the typo `JavaScript`. The `s` should be capitalized. `Javascript` -> `JavaScript` Co-authored-by: JJ Kasper <[email protected]>
vercel · Oct 12, 2024 · a987e2b · a987e2b
1 parent 07a32bc
commit a987e2b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/02-app/01-building-your-application/03-rendering/03-composition-patterns.mdx b/docs/02-app/01-building-your-application/03-rendering/03-composition-patterns.mdx
@@ -358,7 +358,7 @@ To reduce the Client JavaScript bundle size, we recommend moving Client Componen
 
 For example, you may have a Layout that has static elements (e.g. logo, links, etc) and an interactive search bar that uses state.
 
-Instead of making the whole layout a Client Component, move the interactive logic to a Client Component (e.g. `<SearchBar />`) and keep your layout as a Server Component. This means you don't have to send all the component Javascript of the layout to the client.
+Instead of making the whole layout a Client Component, move the interactive logic to a Client Component (e.g. `<SearchBar />`) and keep your layout as a Server Component. This means you don't have to send all the component JavaScript of the layout to the client.
 
 ```tsx filename="app/layout.tsx" switcher
 // SearchBar is a Client Component

diff --git a/docs/02-app/01-building-your-application/07-configuring/16-debugging.mdx b/docs/02-app/01-building-your-application/07-configuring/16-debugging.mdx
@@ -58,7 +58,7 @@ Now go to the Debug panel (`Ctrl+Shift+D` on Windows/Linux, `⇧+⌘+D` on macOS
 
 ## Using the Debugger in Jetbrains WebStorm
 
-Click the drop down menu listing the runtime configuration, and click `Edit Configurations...`. Create a `Javascript Debug` debug configuration with `http://localhost:3000` as the URL. Customize to your liking (e.g. Browser for debugging, store as project file), and click `OK`. Run this debug configuration, and the selected browser should automatically open. At this point, you should have 2 applications in debug mode: the NextJS node application, and the client/ browser application.
+Click the drop down menu listing the runtime configuration, and click `Edit Configurations...`. Create a `JavaScript Debug` debug configuration with `http://localhost:3000` as the URL. Customize to your liking (e.g. Browser for debugging, store as project file), and click `OK`. Run this debug configuration, and the selected browser should automatically open. At this point, you should have 2 applications in debug mode: the NextJS node application, and the client/ browser application.
 
 ## Debugging with Chrome DevTools