Merge pull request #285 from vbhavsar/patch-1

Update expo.md

Author: fecony

docs/integrations/expo.md

@@ -47,7 +47,7 @@ You can treat the Elysia server as if normal Expo API route.
 
 With this approach, you can have co-location of both frontend and backend in a single repository and have [End-to-end type safety with Eden](https://elysiajs.com/eden/overview.html) with both client-side and server action
 
-Please refers to [API route](https://docs.expo.dev/router/reference/api-routes/) for more information.
+Please refer to [API route](https://docs.expo.dev/router/reference/api-routes/) for more information.
 
 ## Prefix
 If you place an Elysia server not in the root directory of the app router, you need to annotate the prefix to the Elysia server.
@@ -76,7 +76,7 @@ You can either directly use API route using Elysia and deploy as normal Elysia a
 If you are using Expo server runtime, you may use `expo export` command to create optimized build for your expo app, this will include an Expo function which is using Elysia at **dist/server/_expo/functions/[...slugs\]+api.js**
 
 ::: tip
-Please note that Expo Function are treat as Edge function instead of normal server, so running the Edge function directly will not allocate anyport.
+Please note that Expo Function are treated as Edge function instead of normal server, so running the Edge function directly will not allocate any port.
 :::
 
 You may use the Expo function adapter provided by Expo to deploy your Edge Function.