[docs] Update 2FA requirements for npm publish documentation

Author: shmam

content/cli/v10/commands/npm-publish.mdx

@@ -29,11 +29,15 @@ npm publish <package-spec>
 
 Publishes a package to the registry so that it can be installed by name.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v10/using-npm/scope) in the name, combined with a scope-configured registry (see [`package.json`](/cli/v10/configuring-npm/package-json)).
 

content/cli/v11/commands/npm-publish.mdx

@@ -45,11 +45,15 @@ npm publish <package-spec>
 
 Publishes a package to the registry so that it can be installed by name.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v11/using-npm/scope) in the name, combined with a scope-configured registry (see [`package.json`](/cli/v11/configuring-npm/package-json)).
 

content/cli/v6/commands/npm-publish.mdx

@@ -32,11 +32,15 @@ Sets tag 'latest' if no --tag specified
 
 Publishes a package to the registry so that it can be installed by name. All files in the package directory are included if no local `.gitignore` or `.npmignore` file exists. If both files exist and a file is ignored by `.gitignore` but not by `.npmignore` then it will be included. See [`developers`](/cli/v6/using-npm/developers) for full details on what's included in the published package, as well as details on how the package is built.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v6/using-npm/scope) in the name (see [`package.json`](/cli/v6/configuring-npm/package-json)).
 

content/cli/v7/commands/npm-publish.mdx

@@ -32,11 +32,15 @@ Sets tag 'latest' if no --tag specified
 
 Publishes a package to the registry so that it can be installed by name.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v7/using-npm/scope) in the name (see [`package.json`](/cli/v7/configuring-npm/package-json)).
 

content/cli/v8/commands/npm-publish.mdx

@@ -29,11 +29,15 @@ npm publish <package-spec>
 
 Publishes a package to the registry so that it can be installed by name.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v8/using-npm/scope) in the name, combined with a scope-configured registry (see [`package.json`](/cli/v8/configuring-npm/package-json)).
 

content/cli/v9/commands/npm-publish.mdx

@@ -29,11 +29,15 @@ npm publish <package-spec>
 
 Publishes a package to the registry so that it can be installed by name.
 
+<Note>
+
 **Important:** Publishing to npm requires either:
 - Two-factor authentication (2FA) enabled on your account, OR
 - A granular access token with bypass 2FA enabled (for CI/CD workflows)
 
-For more information, see the npm documentation on [requiring 2FA for package publishing](https://docs.npmjs.com/requiring-2fa-for-package-publishing-and-settings-modification).
+For more information, see the npm documentation on [requiring 2FA for package publishing](/requiring-2fa-for-package-publishing-and-settings-modification).
+
+</Note>
 
 By default npm will publish to the public registry. This can be overridden by specifying a different default registry or using a [`scope`](/cli/v9/using-npm/scope) in the name, combined with a scope-configured registry (see [`package.json`](/cli/v9/configuring-npm/package-json)).