Fix typos found on examples docs (vercel#20516)

This PR fixes some typos found on examples docs
juanmiguelbesada · Dec 27, 2020 · d96de6e · d96de6e
1 parent bad1448
commit d96de6e
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/examples/with-ant-design-mobile/README.md b/examples/with-ant-design-mobile/README.md
@@ -1,6 +1,6 @@
 # Ant Design Mobile example
 
-This example features how you use [antd-mobile](https://github.com/ant-design/ant-design-mobile) (Ant Design Mobile FrontEnd Framwork) with Next.js.
+This example features how you use [antd-mobile](https://github.com/ant-design/ant-design-mobile) (Ant Design Mobile FrontEnd Framework) with Next.js.
 
 ## Deploy your own
 

diff --git a/examples/with-deta-base/README.md b/examples/with-deta-base/README.md
@@ -36,10 +36,10 @@ Then set each variable on `.env.local`:
 
 - `DETA_PROJECT_KEY` should be the default _Project Key_ that you saved from step 1.
 
-The resulting `env.local` file shoule look like this:
+The resulting `env.local` file should look like this:
 
 ```bash
-DETA_PROEJECT_KEY=...
+DETA_PROJECT_KEY=...
 ```
 
 ### Step 3. Run Next.js in development mode

diff --git a/examples/with-electron-typescript/README.md b/examples/with-electron-typescript/README.md
@@ -29,7 +29,7 @@ Available commands:
 "build-electron": transpile electron layer
 "build": build both layers
 "dev": start dev version
-"dist": create production elctron build
+"dist": create production electron build
 "type-check": check TypeScript in project
 ```
 

diff --git a/examples/with-env-from-next-config-js/README.md b/examples/with-env-from-next-config-js/README.md
@@ -46,4 +46,4 @@ following behavior while you are doing development.
 - When you run `next build` then `next start`, assuming you set externally the environmental variable STAGING to anything but 1, you will get the results assuming `isProd` is true.
 - When your run `next build` or `npm run build` in production, if the environmental variable `STAGING` is set to `1`, `isStaging` will be set and you will get those values returned.
 
-You can read more about this feature in thie blog post <a href="https://vercel.com/blog/next5-1" target="_blank">Next.js 5.1: Faster Page Resolution, Environment Config and More</a> (under Environment Config).
+You can read more about this feature in this blog post <a href="https://vercel.com/blog/next5-1" target="_blank">Next.js 5.1: Faster Page Resolution, Environment Config and More</a> (under Environment Config).
diff --git a/examples/with-firebase-hosting/README.md b/examples/with-firebase-hosting/README.md
@@ -54,7 +54,7 @@ Then you can create components and pages in `.tsx` or `.ts`
 ## Good to know
 
 - [`firebase.json`](firebase.json:#L7) outlines the catchall rewrite rule for our Cloud Function.
-- The empty `public/.gitignore` file is to ensure `public/` dir exists as it is required for Firebase Hosting. It is [configured](firebase.json:#L4) (by [default](https://firebase.google.com/docs/hosting/full-config#ignore)) that dotfiles (`public/.*`) are ignored from bein publicly served.
+- The empty `public/.gitignore` file is to ensure `public/` dir exists as it is required for Firebase Hosting. It is [configured](firebase.json:#L4) (by [default](https://firebase.google.com/docs/hosting/full-config#ignore)) that dotfiles (`public/.*`) are ignored from being publicly served.
 - The Cloud Function is named `nextjsFunc` (changeable in [firebaseFunctions.js](firebaseFunctions.js#L16) and [firebase.json](firebase.json#L8)).
 - `public/*` files are statically served through [Firebase hosting](https://firebase.google.com/docs/hosting/full-config#public), not through [NextJs server](https://nextjs.org/docs/basic-features/static-file-serving).