From ca8530ffc86af399e15cc82fb45b5d19c43b2db9 Mon Sep 17 00:00:00 2001 From: Hassan El Mghari Date: Sat, 12 Feb 2022 19:22:52 -0500 Subject: [PATCH] Changed all occurrences of etc to match (#34280) The [correct](https://www.grammarly.com/blog/et-cetera-etc/) way to use et cetera is to put a period right after and a comma behind it if it's being used as a list. I updated the occurrences in the docs and examples that didn't match these rules. --- docs/advanced-features/measuring-performance.md | 2 +- docs/basic-features/layouts.md | 2 +- docs/guides/building-forms.md | 2 +- docs/migrating/from-gatsby.md | 2 +- errors/css-npm.md | 2 +- examples/custom-server-actionhero/README.md | 2 +- examples/layout-component/pages/about.js | 2 +- examples/layout-component/pages/contact.js | 2 +- examples/with-stencil/packages/test-component/readme.md | 6 +++--- packages/next/cli/next-dev.ts | 2 +- 10 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/advanced-features/measuring-performance.md b/docs/advanced-features/measuring-performance.md index 0a861b416473d..a9c20215e0b7e 100644 --- a/docs/advanced-features/measuring-performance.md +++ b/docs/advanced-features/measuring-performance.md @@ -159,7 +159,7 @@ export function reportWebVitals(metric) { > **Note**: If you use [Google Analytics](https://analytics.google.com/analytics/web/), using the > `id` value can allow you to construct metric distributions manually (to calculate percentiles, -> etc...). +> etc.) > > ```js > export function reportWebVitals({ id, name, label, value }) { diff --git a/docs/basic-features/layouts.md b/docs/basic-features/layouts.md index ea9bfd6f1424e..1bc5c1aa92509 100644 --- a/docs/basic-features/layouts.md +++ b/docs/basic-features/layouts.md @@ -86,7 +86,7 @@ export default function MyApp({ Component, pageProps }) { } ``` -When navigating between pages, we want to *persist* page state (input values, scroll position, etc) for a Single-Page Application (SPA) experience. +When navigating between pages, we want to *persist* page state (input values, scroll position, etc.) for a Single-Page Application (SPA) experience. This layout pattern enables state persistence because the React component tree is maintained between page transitions. With the component tree, React can understand which elements have changed to preserve state. diff --git a/docs/guides/building-forms.md b/docs/guides/building-forms.md index 705b73aebe8b0..c2b163d4fac1e 100644 --- a/docs/guides/building-forms.md +++ b/docs/guides/building-forms.md @@ -49,7 +49,7 @@ Though both of these types are equally important, this guide will focus on clien Client-side validation is further categorized as: -- **Built-in**: Uses HTML-based attributes like `required`, `type`, `minLength`, `maxLength`, `pattern` etc. +- **Built-in**: Uses HTML-based attributes like `required`, `type`, `minLength`, `maxLength`, `pattern`, etc. - **JavaScript-based**: Validation that's coded with JavaScript. ### Built-in Form Validation Using `required`, `type`, `minLength`, `maxLength` diff --git a/docs/migrating/from-gatsby.md b/docs/migrating/from-gatsby.md index 36d27b38a8b1e..d8388b283c75f 100644 --- a/docs/migrating/from-gatsby.md +++ b/docs/migrating/from-gatsby.md @@ -217,7 +217,7 @@ export default function Home() { ## Site Configuration -With Gatsby, your site's metadata (name, description, etc) is located inside `gatsby-config.js`. This is then exposed through the GraphQL API and consumed through a `pageQuery` or a static query inside a component. +With Gatsby, your site's metadata (name, description, etc.) is located inside `gatsby-config.js`. This is then exposed through the GraphQL API and consumed through a `pageQuery` or a static query inside a component. With Next.js, we recommend creating a config file similar to below. You can then import this file anywhere without having to use GraphQL to access your site's metadata. diff --git a/errors/css-npm.md b/errors/css-npm.md index 3e4e81f834a79..2a2a89d395a1a 100644 --- a/errors/css-npm.md +++ b/errors/css-npm.md @@ -24,4 +24,4 @@ know the correct behavior: - Should the file be consumed as Global CSS or CSS Modules? - If Global, in what order does the file need to be injected? - If Modules, what are the emitted class names? As-is, camel-case, snake case? -- Etc... +- Etc. diff --git a/examples/custom-server-actionhero/README.md b/examples/custom-server-actionhero/README.md index c1c4e1c37a3da..62dcb0675609c 100644 --- a/examples/custom-server-actionhero/README.md +++ b/examples/custom-server-actionhero/README.md @@ -80,7 +80,7 @@ module.exports = class CreateChatRoom extends Action { } ``` -3. Tell ActionHero to use the api rather than the file server as the top-level route in `api.config.servers.web.rootEndpointType = 'api'`. This will allows "/" to listen to API requests. Also update `api.config.general.paths.public = [ path.join(__dirname, '/../static') ]`. In this configuration, the next 'static' renderer will take priority over the ActionHero 'public file' api. Note that any static assets (CSS, fonts, etc) will need to be in "./static" rather than "./public". +3. Tell ActionHero to use the api rather than the file server as the top-level route in `api.config.servers.web.rootEndpointType = 'api'`. This will allows "/" to listen to API requests. Also update `api.config.general.paths.public = [ path.join(__dirname, '/../static') ]`. In this configuration, the next 'static' renderer will take priority over the ActionHero 'public file' api. Note that any static assets (CSS, fonts, etc.) will need to be in "./static" rather than "./public". Note that this is where the websocket server, if you enable it, will place the `ActionheroWebsocketClient` library.
diff --git a/examples/layout-component/pages/about.js b/examples/layout-component/pages/about.js index 59f76166cad82..feb320214f270 100644 --- a/examples/layout-component/pages/about.js +++ b/examples/layout-component/pages/about.js @@ -13,7 +13,7 @@ export default function About() {

When navigating between pages, we want to persist page state (input - values, scroll position, etc) for a Single-Page Application (SPA) + values, scroll position, etc.) for a Single-Page Application (SPA) experience.

diff --git a/examples/layout-component/pages/contact.js b/examples/layout-component/pages/contact.js index d2888593ec9fd..50167f2bec144 100644 --- a/examples/layout-component/pages/contact.js +++ b/examples/layout-component/pages/contact.js @@ -13,7 +13,7 @@ export default function Contact() {

When navigating between pages, we want to persist page state (input - values, scroll position, etc) for a Single-Page Application (SPA) + values, scroll position, etc.) for a Single-Page Application (SPA) experience.

diff --git a/examples/with-stencil/packages/test-component/readme.md b/examples/with-stencil/packages/test-component/readme.md index d6812363edd4e..d01839ddf56e4 100644 --- a/examples/with-stencil/packages/test-component/readme.md +++ b/examples/with-stencil/packages/test-component/readme.md @@ -57,16 +57,16 @@ Instead, use a prefix that fits your company or any name for a group of related - [Publish to NPM](https://docs.npmjs.com/getting-started/publishing-npm-packages) - Put a script tag similar to this `` in the head of your index.html -- Then you can use the element anywhere in your template, JSX, html etc +- Then you can use the element anywhere in your template, JSX, html, etc. ### Node Modules - Run `npm install my-component` - Put a script tag similar to this `` in the head of your index.html -- Then you can use the element anywhere in your template, JSX, html etc +- Then you can use the element anywhere in your template, JSX, html, etc. ### In a stencil-starter app - Run `npm install my-component` - Add an import to the npm packages `import my-component;` -- Then you can use the element anywhere in your template, JSX, html etc +- Then you can use the element anywhere in your template, JSX, html, etc. diff --git a/packages/next/cli/next-dev.ts b/packages/next/cli/next-dev.ts index 6441831ffbe08..7fe541b68fb26 100755 --- a/packages/next/cli/next-dev.ts +++ b/packages/next/cli/next-dev.ts @@ -34,7 +34,7 @@ const nextDev: cliCommand = (argv) => { console.log(` Description Starts the application in development mode (hot-code reloading, error - reporting, etc) + reporting, etc.) Usage $ next dev

-p