a57481c · cryptotaxi247/documentation-1

content/getting-started/setting-up-your-npm-user-account/accessing-npm-using-2fa.mdx

+1 -1

@@ -35,7 +35,7 @@ import shared from '../../../src/shared.js'

35

36 ## Sign in from the command line using `--auth-type=web`

37

38 -npm 8.14.0 and higher support login flow through the browers. This will become the default behavior for the npm public registry in npm 9.

38 +npm 8.14.0 and higher support login flow through the browsers. This will become the default behavior for the npm public registry in npm 9.

39

40 ### With an existing browser session

41

content/organizations/creating-and-managing-organizations/renaming-an-organization.mdx

+1 -1

@@ -11,7 +11,7 @@ To rename an organization, as an organization owner, you must manually migrate y

11 1. [Create a new organization][org-create] with the name you want. If your old organization is on a paid plan, you must choose a paid plan for the new organization.

12 2. [Add the members][add-org-members] of your old organization to your new organization.

13 3. In your new organization, [create teams][create-teams] to match teams in your old organization.

14 -4. Republish packages to the new organization by updating the package scope in its `package.json` file to match the new organizationanization name and running `npm publish`.

14 +4. Republish packages to the new organization by updating the package scope in its `package.json` file to match the new organization name and running `npm publish`.

15 5. In the new organization teams, [configure package access][pkg-access] to match team package access in your old organization.

16 6. [Contact npm Support][contact-support] to have the outdated packages unpublished and the previous organization deleted.

17

content/organizations/managing-teams/about-developers-team.mdx

+1 -1

@@ -11,7 +11,7 @@ is automatically populated with the members of the current **developers** team

11 If you create a new package under your organization's scope and you do not

12 want members of the **developers** team to have read/write access to that

13 package, an owner or admin can remove the **developers** team's access to that

14 -package. For more informations, see "[Managing team access to organization packages][pkg-access]".

14 +package. For more information, see "[Managing team access to organization packages][pkg-access]".

15

16 If an owner adds a new member to an organization and **does not** want

17 that member to be on the **developers** team, an owner can remove them.

content/policies/logos-and-usage.mdx

+1 -1

@@ -38,7 +38,7 @@ If you need to use "npm" to indicate compatibility, you should use "npm" after y

38

39 * Pink Unicorn Consulting Ltd. services for npm

40 * Purple Unicorn Inc. private registry server compatible with the npm client

41 -* Kappa, a hirearchical proxy of the npm registry

41 +* Kappa, a hierarchical proxy of the npm registry

42

43 You need to ask for permission for any uses not described. When in doubt about your use of the npm name or logo, please contact [npm, Inc.](https://www.npmjs.com/contact) for clarification.

44

Fixed several typos (#271)