Convert invalid html content to jsx

Author: lukekarrys

content/packages-and-modules/contributing-packages-to-the-registry/about-semantic-versioning.mdx

@@ -6,11 +6,11 @@ redirect_from:
 
 To keep the JavaScript ecosystem healthy, reliable, and secure, every time you make significant updates to an npm package you own, we recommend publishing a new version of the package with an updated version number in the [`package.json` file][pkg-json] that follows the [semantic versioning spec][semver-org]. Following the semantic versioning spec helps other developers who depend on your code understand the extent of changes in a given version, and adjust their own code if necessary.
 
-<div class="note">
+<Note>
 
-<span class="bold">Note:</span> If you introduce a change that breaks a package dependency, we strongly recommend incrementing the version <span class="bold">major number</span>; see below for details.
+**Note:** If you introduce a change that breaks a package dependency, we strongly recommend incrementing the version **major number**; see below for details.
 
-</div>
+</Note>
 
 ## Incrementing semantic versions in published packages
 

content/packages-and-modules/introduction-to-packages-and-modules/about-private-packages.mdx

@@ -2,16 +2,15 @@
 title: About private packages
 ---
 
-<div class="note">
+<Note>
 
 To use private packages, you must
 
-<ul>
-<li> be using npm version 2.7.0 or greater. To upgrade, on the command line, run <code class="highlighter-rouge">npm install npm@latest -g</code></li>
-<li>have a <a href="https://www.npmjs.com/pricing">paid user or organization account</a></li>
-</ul>
 
-</div>
+- be using npm version 2.7.0 or greater. To upgrade, on the command line, run `npm install npm@latest -g`
+- have a [paid user or organization account](https://www.npmjs.com/pricing)
+
+</Note>
 
 With npm private packages, you can use the npm registry to host code that is only visible to you and chosen collaborators, allowing you to manage and use private code alongside public code in your projects.
 

content/packages-and-modules/introduction-to-packages-and-modules/about-scopes.mdx

@@ -4,11 +4,11 @@ redirect_from:
   - /getting-started/scoped-packages
 ---
 
-<div class="note">
+<Note>
 
-<span class="bold">Note:</span> You must be using npm version 2 or greater to use scopes. To upgrade to the latest version of npm, on the command line, run <code class="highlighter-rouge">npm install npm@latest -g</code>
+**Note:** You must be using npm version 2 or greater to use scopes. To upgrade to the latest version of npm, on the command line, run `npm install npm@latest -g`
 
-</div>
+</Note>
 
 When you sign up for an npm user account or create an organization, you are granted a scope that matches your user or organization name. You can use this scope as a namespace for related packages.
 

content/packages-and-modules/introduction-to-packages-and-modules/package-scope-access-level-and-visibility.mdx

@@ -4,11 +4,11 @@ title: npm package scope, access level, and visibility
 
 Visibility of npm packages depends on the scope (namespace) in which the package is contained, and the access level (private or public) set for the package.
 
-<div class="note">
+<Note>
 
-<span class="bold">Note:</span> To create organization-scoped packages, you must first create an organization. For more information, see "<a href="https://docs.npmjs.com/creating-an-organization">Creating an organization</a>".
+**Note:** To create organization-scoped packages, you must first create an organization. For more information, see "<a href="https://docs.npmjs.com/creating-an-organization">Creating an organization</a>".
 
-</div>
+</Note>
 
 ## Public registry
 
@@ -20,8 +20,8 @@ Visibility of npm packages depends on the scope (namespace) in which the package
 | User     | Public       | Everyone  | The package owner and users who have been granted read and write access to the package |
 | Unscoped | Public | Everyone | The package owner and users who have been granted read and write access to the package |
 
-<div class="note">
+<Note>
 
-<span class="bold">Note:</span> Only user accounts can create and manage unscoped packages. Organizations can only manage scoped packages.
+**Note:** Only user accounts can create and manage unscoped packages. Organizations can only manage scoped packages.
 
-</div>
+</Note>