Apply suggestions from code review

Co-authored-by: James Opstad <[email protected]>

Author: emily-shen

src/content/docs/workers/frameworks/framework-guides/hono.mdx

@@ -63,7 +63,7 @@ With Workers Assets, you can easily combine a Hono API running on Workers with a
         					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your SPA do not go to the Worker, and are thus free.
         					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in Cloudflare's `workerd` runtime, ensuring your local development environment is as close to production as possible.
+    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
     						`src/worker/index.ts` is your Hono app, which contains a single endpoint to begin with, `/api`.
     						At `src/react-app/src/App.tsx`, your React app calls this endpoint to get a message back and displays this in your SPA.
@@ -74,8 +74,8 @@ With Workers Assets, you can easily combine a Hono API running on Workers with a
         After creating your project, run the following command in your project directory to start a local development server.
         <PackageManagers type="run" args="dev" />
         		<Details header="What's happening in local development?">
-        			This project uses Vite for local development and build, and thus comes with all of Vite's features like hot module replacement (HMR).
-        			In addition, `vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your application in Cloudflare's `workerd` runtime, just like in production, as well as access to local emulators of bindings.
+        			This project uses Vite for local development and build, and thus comes with all of Vite's features, including hot module replacement (HMR).
+        			In addition, `vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your application in the Cloudflare Workers runtime, just like in production, and enables access to local emulations of bindings.
         		</Details>
 
 3.  **Deploy your project**

src/content/docs/workers/frameworks/framework-guides/react.mdx

@@ -62,9 +62,9 @@ import {
         					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your React SPA do not go to the Worker, and are thus free.
         					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in Cloudflare's `workerd` runtime, ensuring your local development environment is as close to production as possible.
+    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-    						`worker/index.ts` is your backend API, which contains a single endpoint `/api` that returns a text response.
+    						`worker/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
     						At `src/App.tsx`, your React app calls this endpoint to get a message back and displays this.
         		</Details>
 
@@ -73,8 +73,8 @@ import {
         After creating your project, run the following command in your project directory to start a local development server.
         <PackageManagers type="run" args="dev" />
         		<Details header="What's happening in local development?">
-        			This project uses Vite for local development and build, and thus comes with all of Vite's features like hot module replacement (HMR).
-        			In addition, `vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your application in Cloudflare's `workerd` runtime, just like in production, as well as access to local emulators of bindings.
+        			This project uses Vite for local development and build, and thus comes with all of Vite's features, including hot module replacement (HMR).
+        			In addition, `vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your application in the Cloudflare Workers runtime, just like in production, and enables access to local emulations of bindings.
         		</Details>
 
 3.  **Deploy your project**

src/content/docs/workers/frameworks/framework-guides/vue.mdx

@@ -49,9 +49,9 @@ To use `create-cloudflare` to create a new Vue project with <InlineBadge preset=
         					- `assets.not_found_handling` is set to `single-page-application`, which means that routes that are handled by your Vue SPA do not go to the Worker, and are thus free.
         					- If you want to add bindings to resources on Cloudflare's developer platform, you configure them here. Read more about [bindings](/workers/runtime-apis/bindings/).
 
-    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in Cloudflare's `workerd` runtime, ensuring your local development environment is as close to production as possible.
+    						`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your Worker in the Cloudflare Workers runtime, ensuring your local development environment is as close to production as possible.
 
-    						`server/index.ts` is your backend API, which contains a single endpoint `/api` that returns a text response.
+    						`server/index.ts` is your backend API, which contains a single endpoint, `/api/`, that returns a text response.
     						At `src/App.vue`, your Vue app calls this endpoint to get a message back and displays this.
         		</Details>
 
@@ -62,10 +62,9 @@ After you have created your project, run the following command in the project di
 <PackageManagers type="run" args={"dev"} />
 <Details header="What's happening in local development?">
 	This project uses Vite for local development and build, and thus comes with
-	all of Vite's features like hot module replacement (HMR). In addition,
-	`vite.config.ts` is set up to use the Cloudflare Vite plugin. This runs your
-	application in Cloudflare's `workerd` runtime, just like in production, as
-	well as access to local emulators of bindings.
+	all of Vite's features, including hot module replacement (HMR). In addition,
+	`vite.config.ts` is set up to use the Cloudflare Vite plugin.
+	 This runs your application in the Cloudflare Workers runtime, just like in production, and enables access to local emulations of bindings.
 </Details>
 
 ## 3. Deploy your project