fix a few things

Author: mchammer01

data/reusables/dependabot/supported-package-managers.md

@@ -1,5 +1,5 @@
 The following table shows, for each package manager:
-- The YAML value to use in the*dependabot.yml* file
+- The YAML value to use in the *dependabot.yml* file
 - The supported versions 
 - Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories are supported
 - Whether vendoring is supported for the package
@@ -19,7 +19,7 @@ Gradle | `gradle` | see (A) below | **✓** | |
 Maven | `maven` | see (B) below | **✓** | |
 Mix | `mix` | v1 | **✓** | |
 npm | `npm` | v6 | **✓** | |
-NuGet | `nuget` | <= 4.8. See (C) below | **✓** | |
+NuGet | `nuget` | <= 4.8.</br>See (C) below | **✓** | |
 pip | `pip` | v20 | | |
 pipenv | `pip` | <= 2018.11.26 | | |
 pip-compile | `pip` | TBD | | |
@@ -33,4 +33,4 @@ yarn | `nmp` | v1 | | |
 
 (C) {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8. Version 4.9 introduces lockfiles, which are unsupported.
 
-For package managers such as `pipenv` and `poetry`, you need to use the pip YAML value.For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file.
+For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file.