Fix minor typos

docs/basic-features/typescript.md

@@ -53,7 +53,7 @@ npm run dev
 # ...
 ```
 
-You're now ready to start converting files from `.js` to `.tsx` and leveraging the benefits of TypeScript!.
+You're now ready to start converting files from `.js` to `.tsx` and leveraging the benefits of TypeScript!
 
 > A file named `next-env.d.ts` will be created in the root of your project. This file ensures Next.js types are picked up by the TypeScript compiler. **You cannot remove it or edit it** as it can change at any time.
 

docs/testing.md

@@ -136,7 +136,7 @@ You can learn more about Cypress and Continuous Integration from these resources
 
 - [Cypress Continuous Integration Docs](https://docs.cypress.io/guides/continuous-integration/introduction)
 - [Cypress GitHub Actions Guide](https://on.cypress.io/github-actions)
-- [Official Cypress Github Action](https://github.com/cypress-io/github-action)
+- [Official Cypress GitHub Action](https://github.com/cypress-io/github-action)
 
 ## Playwright
 

examples/with-chakra-ui-typescript/src/pages/index.tsx

@@ -21,7 +21,7 @@ const Index = () => (
     <Main>
       <Text>
         Example repository of <Code>Next.js</Code> + <Code>chakra-ui</Code> +{' '}
-        <Code>typescript</Code>.
+        <Code>TypeScript</Code>.
       </Text>
 
       <List spacing={3} my={0}>

examples/with-firebase-hosting/README.md

@@ -41,9 +41,9 @@ npm run deploy
 yarn deploy
 ```
 
-## Typescript
+## TypeScript
 
-To use Typescript, simply follow [Typescript setup](https://nextjs.org/learn/excel/typescript/setup) as normal (package.json scripts are already set).
+To use TypeScript, simply follow [TypeScript setup](https://nextjs.org/learn/excel/typescript/setup) as normal (package.json scripts are already set).
 
 i.e: `npm install --save-dev typescript @types/react @types/node`
 

examples/with-mobx-state-tree-typescript/README.md

@@ -1,4 +1,4 @@
-# MobX State Tree with Typescript example
+# MobX State Tree with TypeScript example
 
 Usually splitting your app state into `pages` feels natural but sometimes you'll want to have global state for your app. This is an example on how you can use mobx that also works with our universal rendering approach.
 

examples/with-mobx-state-tree-typescript/store.ts

@@ -20,7 +20,7 @@ const Store = types
       timer = setInterval(() => {
         // mobx-state-tree doesn't allow anonymous callbacks changing data.
         // Pass off to another action instead (need to cast self as any
-        // because typescript doesn't yet know about the actions we're
+        // because TypeScript doesn't yet know about the actions we're
         // adding to self here)
         ;(self as any).update()
       }, 1000)