docs: correct typo in documentation

Author: doyoonkim12345

docs/docs/guide/1.gettingStarted/2.quickStart.mdx

@@ -79,7 +79,8 @@ You don't need to manually set `requestHeaders`. Instead, configure the channel
 > In this example, builds triggered with the `--profile preview` option will use the `beta` channel, while `--profile production` uses `stable`.
 
 </details>
-```
+
+
 
 ### 4️⃣ Provide environment variables
 

docs/docs/guide/3.expo/3.configs/index.mdx

@@ -64,7 +64,7 @@ interface AppConfig {
 			projectId: "12345aaa-bbbb-cccc-dddd-eeeeeeeeeeee",
 		},
 		cloudPush: {
-			checkUpdateStatusUrl: "https://yourdomain/api/udpates/status",
+			checkUpdateStatusUrl: "https://yourdomain/api/updates/status",
 		} as AppConfig,
 	},
 }
@@ -118,7 +118,7 @@ export default ({ config }: ConfigContext): ExpoConfig => ({
       projectId: "12345aaa-bbbb-cccc-dddd-eeeeeeeeeeee",
     },
     cloudPush: {
-      checkUpdateStatusUrl: "https://yourdomain/api/udpates/status",
+      checkUpdateStatusUrl: "https://yourdomain/api/updates/status",
     } as AppConfig,
   },
 });

docs/docs/guide/3.expo/4.env/index.mdx

@@ -13,7 +13,7 @@ As with expo, environments are limited to **production**, **development**, and *
 
 ## 1. `eas env`
 
-If you use `eas env`, environment variables are loaded from [expo.dev](https://expo.dev). To use this option, your project **must be set up so it can be found on [expo.dev](https://expo.dev)]**, and the environment variables you want to use must be properly set for each environment. Also, **the cloud-push execution environment must be set up so that eas can be used**.
+If you use `eas env`, environment variables are loaded from [expo.dev](https://expo.dev). To use this option, your project **must be set up so it can be found on [expo.dev](https://expo.dev)**, and the environment variables you want to use must be properly set for each environment. Also, **the cloud-push execution environment must be set up so that eas can be used**.
 
 ## 2. `.env`