meta: Fix typos discovered by codespell (#6262)

Author: cclauss

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('/');

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('/');

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;

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

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

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
 

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