From 06f46ca44dbaef036c1ceed1fc4fec2b11e56993 Mon Sep 17 00:00:00 2001 From: Christian Clauss Date: Tue, 23 Jan 2024 14:09:02 +0100 Subject: [PATCH] meta: Fix typos discovered by codespell --- layouts/BlogCategoryLayout.tsx | 2 +- layouts/New/Blog.tsx | 2 +- next.config.mjs | 2 +- next.constants.mjs | 2 +- next.dynamic.mjs | 2 +- pages/en/guides/diagnostics/memory/using-heap-profiler.md | 4 ++-- .../guides/diagnostics/poor-performance/using-linux-perf.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/layouts/BlogCategoryLayout.tsx b/layouts/BlogCategoryLayout.tsx index d1a64e52cb442..32e5303a852e6 100644 --- a/layouts/BlogCategoryLayout.tsx +++ b/layouts/BlogCategoryLayout.tsx @@ -10,7 +10,7 @@ import getBlogData from '@/next-data/blogData'; const getCategoryData = async (pathname: string) => { // pathname format can either be: /en/blog/{category} // or /en/blog/{category}/page/{page} - // hence we attempt to interpolate the full /en/blog/{categoy}/page/{page} + // hence we attempt to interpolate the full /en/blog/{category}/page/{page} // and in case of course no page argument is provided we define it to 1 // note that malformed routes can't happen as they are all statically generated const [, , category = 'all', , page = 1] = pathname.split('/'); diff --git a/layouts/New/Blog.tsx b/layouts/New/Blog.tsx index 576b50b766c1e..a972204cc0764 100644 --- a/layouts/New/Blog.tsx +++ b/layouts/New/Blog.tsx @@ -12,7 +12,7 @@ import styles from './layouts.module.css'; const getBlogCategory = async (pathname: string) => { // pathname format can either be: /en/blog/{category} // or /en/blog/{category}/page/{page} - // hence we attempt to interpolate the full /en/blog/{categoy}/page/{page} + // hence we attempt to interpolate the full /en/blog/{category}/page/{page} // and in case of course no page argument is provided we define it to 1 // note that malformed routes can't happen as they are all statically generated const [, , category = 'all', , page = 1] = pathname.split('/'); diff --git a/next.config.mjs b/next.config.mjs index df5225b93dfe6..f29a69eea3d3d 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -146,6 +146,6 @@ const nextWithSentry = withSentryConfig( sentryConfig ); -// Decides wheter enabling Sentry or not +// Decides whether enabling Sentry or not // By default we only want to enable Sentry within a Vercel Environment export default SENTRY_ENABLE ? nextWithSentry : nextWithIntl; diff --git a/next.constants.mjs b/next.constants.mjs index 1d75f8261c4ee..1a0c07f9af41a 100644 --- a/next.constants.mjs +++ b/next.constants.mjs @@ -91,7 +91,7 @@ export const BASE_PATH = process.env.NEXT_PUBLIC_BASE_PATH || ''; * Note this is assumes that the Node.js Website is either running within Vercel Environment * or running locally (either production or development) mode * - * Note this variable can be overrided via a manual Environment Variable defined by us if necessary. + * Note this variable can be overridden via a manual Environment Variable defined by us if necessary. */ export const NEXT_DATA_URL = process.env.NEXT_PUBLIC_DATA_URL ? process.env.NEXT_PUBLIC_DATA_URL diff --git a/next.dynamic.mjs b/next.dynamic.mjs index d212550c96b3e..f925e6da8dab9 100644 --- a/next.dynamic.mjs +++ b/next.dynamic.mjs @@ -22,7 +22,7 @@ import { compileMDX } from './next.mdx.compiler.mjs'; // This is the combination of the Application Base URL and Base PATH const baseUrlAndPath = `${BASE_URL}${BASE_PATH}`; -// This is a small utility that allows us to quickly separate locale from the remaning pathname +// This is a small utility that allows us to quickly separate locale from the remaining pathname const getPathname = (path = []) => path.join('/'); // This maps a pathname into an actual route object that can be used diff --git a/pages/en/guides/diagnostics/memory/using-heap-profiler.md b/pages/en/guides/diagnostics/memory/using-heap-profiler.md index ece31ec4a523a..40c8887e7dbfe 100644 --- a/pages/en/guides/diagnostics/memory/using-heap-profiler.md +++ b/pages/en/guides/diagnostics/memory/using-heap-profiler.md @@ -58,7 +58,7 @@ Finally, look at the snapshot data: ![heap profiler tutorial step 3][heap profiler tutorial 3] -Check the [useful links](#useful-links) section for futher information +Check the [useful links](#useful-links) section for further information about memory terminology. ## Sampling Heap Profiler @@ -68,7 +68,7 @@ over time. Since it is sampling based its overhead is low enough to use in production systems. > You can use the module [`heap-profiler`][] to start and stop the heap -> profiler programatically. +> profiler programmatically. ### How To diff --git a/pages/en/guides/diagnostics/poor-performance/using-linux-perf.md b/pages/en/guides/diagnostics/poor-performance/using-linux-perf.md index 62b3097fd3df4..ecf32a4d25d43 100644 --- a/pages/en/guides/diagnostics/poor-performance/using-linux-perf.md +++ b/pages/en/guides/diagnostics/poor-performance/using-linux-perf.md @@ -77,7 +77,7 @@ from step 6. Because `perf` output is not a Node.js specific tool, it might have issues with how JavaScript code is optimized in Node.js. See [perf output issues](/guides/diagnostics-flamegraph/#perf-output-issues) for a -futher reference. +further reference. ## Useful Links