chore: fix typos (#496)

noritaka1166 · web-flow · commit 2af8294ed475 · 2025-08-30T19:16:08.000+02:00
diff --git a/websites/mswjs.io/src/content/blog/enter-websockets.mdx b/websites/mswjs.io/src/content/blog/enter-websockets.mdx
@@ -79,7 +79,7 @@ The next iteration didn't lead anywhere either. Or, rather, it led back to the s
 
 **I should've based the interceptor off of the WHATWG WebSocket standard all along.**
 
-No custom transports, no unofficial message protocols. Bet. On. The. Standard. Allways bet on the standard. And it is only through betting on the standard that you can enjoy the WebSocket mocking today.
+No custom transports, no unofficial message protocols. Bet. On. The. Standard. Always bet on the standard. And it is only through betting on the standard that you can enjoy the WebSocket mocking today.
 
 ## The final iteration
 
diff --git a/websites/mswjs.io/src/content/blog/introducing-server-boundary.mdx b/websites/mswjs.io/src/content/blog/introducing-server-boundary.mdx
@@ -41,7 +41,7 @@ Internally, MSW keeps the list of current request handlers in-memory, and resolv
 
 ```js {8}
 class SetupServerApi {
-  construtor(...initialHandlers) {
+  constructor(...initialHandlers) {
     this.initialHandlers = initialHandlers
     this.currentHandlers = [...this.initialHandlers]
   }
diff --git a/websites/mswjs.io/src/content/blog/why-use-mock-service-worker.mdx b/websites/mswjs.io/src/content/blog/why-use-mock-service-worker.mdx
@@ -56,7 +56,7 @@ You would be mistaken to assume you can throw that logic away without any reperc
 fetch('/resource', { body: 'Hello world' })
 ```
 
-**If this was a real reques**t, it would throw an exception:
+**If this was a real request**, it would throw an exception:
 
 ```
 Request with GET/HEAD method cannot have body.
diff --git a/websites/mswjs.io/src/content/docs/api/ws.mdx b/websites/mswjs.io/src/content/docs/api/ws.mdx
@@ -236,7 +236,7 @@ api.addEventListener('connection', ({ server }) => {
 
 ## `WebSocketConnectionInfo`
 
-The `info` argument on the `connection` event listener contains additional WebSocket connection infromation.
+The `info` argument on the `connection` event listener contains additional WebSocket connection information.
 
 | Property name | Type                              | Description                                                             |
 | ------------- | --------------------------------- | ----------------------------------------------------------------------- |
diff --git a/websites/mswjs.io/src/content/docs/graphql/intercepting-operations/index.mdx b/websites/mswjs.io/src/content/docs/graphql/intercepting-operations/index.mdx
@@ -126,7 +126,7 @@ The following properties are available on the response resolver object argument
 
 | Property        | Type                     | Description                                                                                  |
 | --------------- | ------------------------ | -------------------------------------------------------------------------------------------- |
-| `cookies`       | `Record<string, string>` | Parsed requets cookies.                                                                      |
+| `cookies`       | `Record<string, string>` | Parsed request cookies.                                                                      |
 | `query`         | `string`                 | Raw GraphQL [query string](/docs/graphql/intercepting-operations/queries#reading-raw-query). |
 | `variables`     | `Record<string, any>`    | Parsed [variables](/docs/graphql/intercepting-operations/variables) of this operation.       |
 | `operationName` | `string`                 | Operation name (e.g. `'GetUser'`).                                                           |
diff --git a/websites/mswjs.io/src/content/docs/graphql/mocking-responses/index.mdx b/websites/mswjs.io/src/content/docs/graphql/mocking-responses/index.mdx
@@ -62,7 +62,7 @@ api.query<User>('GetUser', () => {
 })
 ```
 
-> Above is an example of including the `__typename` key in the mocked response reqiured by Apollo.
+> Above is an example of including the `__typename` key in the mocked response required by Apollo.
 
 ## Next steps
 
diff --git a/websites/mswjs.io/src/content/docs/http/handling-requests.mdx b/websites/mswjs.io/src/content/docs/http/handling-requests.mdx
@@ -58,7 +58,7 @@ http.get('https://api.example.com/resource', async ({ request }) => {
 
 ### Return nothing
 
-You can also return nothing from the response resolver, either explicitly or implicitly. If that happens, MSW will continue to look for other request handlers that might match ths request. You can utilize this for network introspection or any other side effects that do not involve responding to the request.
+You can also return nothing from the response resolver, either explicitly or implicitly. If that happens, MSW will continue to look for other request handlers that might match this request. You can utilize this for network introspection or any other side effects that do not involve responding to the request.
 
 ```ts {3}
 export const handlers = [
@@ -71,4 +71,4 @@ export const handlers = [
 ]
 ```
 
-> In this example, the first request handler will match, log the message to the console, and, since it returns nothing, finish. The second request hander will then match the same request and handle it with a mocked response, as an example.
+> In this example, the first request handler will match, log the message to the console, and, since it returns nothing, finish. The second request handler will then match the same request and handle it with a mocked response, as an example.
diff --git a/websites/mswjs.io/src/content/docs/http/mocking-responses/polling.mdx b/websites/mswjs.io/src/content/docs/http/mocking-responses/polling.mdx
@@ -27,7 +27,7 @@ http.get<{ city: string }, never, { degree: number }>(
 )
 ```
 
-This `GET /wheather/:city` request handler increments the `degree` on each response until it reaches 28 degrees:
+This `GET /weather/:city` request handler increments the `degree` on each response until it reaches 28 degrees:
 
 ```json
 GET /weather/london // { "degree": 26 }
diff --git a/websites/mswjs.io/src/content/docs/philosophy.mdx b/websites/mswjs.io/src/content/docs/philosophy.mdx
@@ -43,4 +43,4 @@ http.get('/old', () => {
 
 ## Server's perspective
 
-When working with MSW, you will be writing [request handlers](/docs/http/intercepting-requests/) to intercept and respond to requests. It's important to approach those handlers from the _server's_ perspective since, effectively, you are describing how the server should behave in a particlar scenario.
+When working with MSW, you will be writing [request handlers](/docs/http/intercepting-requests/) to intercept and respond to requests. It's important to approach those handlers from the _server's_ perspective since, effectively, you are describing how the server should behave in a particular scenario.
diff --git a/websites/mswjs.io/src/content/docs/recipes/using-local-https.mdx b/websites/mswjs.io/src/content/docs/recipes/using-local-https.mdx
@@ -7,7 +7,7 @@ keywords:
   - self-signed
 ---
 
-Due to security considerations, Service Workers can only be registered over a secure connection (exception being the local development on `localhost`). In some project setups, you may require to run your local application over HTTPS and will shortly encouter the following error when starting MSW's worker:
+Due to security considerations, Service Workers can only be registered over a secure connection (exception being the local development on `localhost`). In some project setups, you may require to run your local application over HTTPS and will shortly encounter the following error when starting MSW's worker:
 
 ```txt
 SecurityError: Failed to register a ServiceWorker:
diff --git a/websites/mswjs.io/src/content/docs/websocket/client-events/client-to-server-forwarding.mdx b/websites/mswjs.io/src/content/docs/websocket/client-events/client-to-server-forwarding.mdx
@@ -3,7 +3,7 @@ title: Client-to-server forwarding
 description: Manage the client event forwarding.
 ---
 
-By default, none of the events you send from your WebSocket client are forwarded to the original server because the original server connection is not established. You can choose to [establish the server connection](/docs/websocket/server-events/establishing-server-connection) by calling `server.connect()` in your event handler. Once you do, all the client events will be forwaded to that original server.
+By default, none of the events you send from your WebSocket client are forwarded to the original server because the original server connection is not established. You can choose to [establish the server connection](/docs/websocket/server-events/establishing-server-connection) by calling `server.connect()` in your event handler. Once you do, all the client events will be forwarded to that original server.
 
 You can manage that event forwarding in multiple ways:
 
diff --git a/websites/mswjs.io/src/content/docs/websocket/type-safety.mdx b/websites/mswjs.io/src/content/docs/websocket/type-safety.mdx
@@ -12,7 +12,7 @@ ws.link<Arg1, Arg2>(url)
 //     ^^^^^^^^^^^^ Type error!
 ```
 
-The reasoning behing this decision is twofold:
+The reasoning behind this decision is twofold:
 
 1. Narrowing down the data type doesn't guarantee that a different data type wouldn't be sent over the network (the classic types vs runtime debate);
 1. The `event.data` value you receive in the message event listener will always be of type `string | Blob | ArrayBuffer` because MSW provides no message parsing.
diff --git a/websites/mswjs.io/src/pages/index.astro b/websites/mswjs.io/src/pages/index.astro
@@ -408,7 +408,7 @@ import PromoBanner from '@mswjs/shared/components/PromoBanner.astro'
   >
     <span class="text-white">Mock Service Worker</span> is the best
     way to integrate API mocking across your entire stack. Test,
-    prototype, and debug withouth sacrificing your application's
+    prototype, and debug without sacrificing your application's
     integrity. Give it a try, it's open-source and free!
   </GettingStarted>
 </BaseLayout>
diff --git a/websites/source.mswjs.io/src/content/docs/integrations/har.mdx b/websites/source.mswjs.io/src/content/docs/integrations/har.mdx
@@ -136,7 +136,7 @@ fromTraffic(har, (entry) => {
 })
 ```
 
-In this example, we are locating requests to `example.com` and rewriting their hostname to point to the `BASE_URL` we use in tests. This is handy if the recorded traffic was on production while we want to run tests aginst staging or local.
+In this example, we are locating requests to `example.com` and rewriting their hostname to point to the `BASE_URL` we use in tests. This is handy if the recorded traffic was on production while we want to run tests against staging or local.
 
 Using the map function also allows you to repurpose a single network archive by transforming its entries based on the test cases or debugging scenarios.
 

Original file line number	Diff line number	Diff line change
`@@ -41,7 +41,7 @@ Internally, MSW keeps the list of current request handlers in-memory, and resolv`
`41`	`41`
`42`	`42`	```js {8}
`43`	`43`	`class SetupServerApi {`
`44`		`- construtor(...initialHandlers) {`
	`44`	`+ constructor(...initialHandlers) {`
`45`	`45`	`this.initialHandlers = initialHandlers`
`46`	`46`	`this.currentHandlers = [...this.initialHandlers]`
`47`	`47`	`}`
Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,7 @@ http.get<{ city: string }, never, { degree: number }>(`
`27`	`27`	`)`
`28`	`28`	```
`29`	`29`
`30`		-This `GET /wheather/:city` request handler increments the `degree` on each response until it reaches 28 degrees:
	`30`	+This `GET /weather/:city` request handler increments the `degree` on each response until it reaches 28 degrees:
`31`	`31`
`32`	`32`	```json
`33`	`33`	`GET /weather/london // { "degree": 26 }`
Original file line number	Diff line number	Diff line change
`@@ -43,4 +43,4 @@ http.get('/old', () => {`
`43`	`43`
`44`	`44`	`## Server's perspective`
`45`	`45`
`46`		`-When working with MSW, you will be writing [request handlers](/docs/http/intercepting-requests/) to intercept and respond to requests. It's important to approach those handlers from the _server's_ perspective since, effectively, you are describing how the server should behave in a particlar scenario.`
	`46`	`+When working with MSW, you will be writing [request handlers](/docs/http/intercepting-requests/) to intercept and respond to requests. It's important to approach those handlers from the _server's_ perspective since, effectively, you are describing how the server should behave in a particular scenario.`