diff --git a/rules/have-a-definition-of-ready/rule.md b/rules/have-a-definition-of-ready/rule.md
index 8a273234429..0e3eeaaeacf 100644
--- a/rules/have-a-definition-of-ready/rule.md
+++ b/rules/have-a-definition-of-ready/rule.md
@@ -36,9 +36,11 @@ A recommended “Definition of Ready” would be:
 * Is in the Approved state
 
 ::: greybox
-**Notes:** 
-1.	PBIs can still be accepted into a Sprint even if they do not meet the DoR.  When that happens, there will be more risk and uncertainty around the PBI, but this should not stop the team from doing the work.  The recommendation is that PBI's are ready, but this is not mandatory.
+**Notes:**
+
+1. PBIs can still be accepted into a Sprint even if they do not meet the DoR.  When that happens, there will be more risk and uncertainty around the PBI, but this should not stop the team from doing the work.  The recommendation is that PBI's are ready, but this is not mandatory.
 2. User Stories should follow the INVEST Principle:
+
 * “I” ndependent (of all others)
 * “N” egotiable (not a specific contract for features)
 * “V” aluable (or vertical)
diff --git a/rules/the-standard-naming-conventions-for-tests/rule.md b/rules/the-standard-naming-conventions-for-tests/rule.md
index 2b4479972b0..8a2f9afa9ee 100644
--- a/rules/the-standard-naming-conventions-for-tests/rule.md
+++ b/rules/the-standard-naming-conventions-for-tests/rule.md
@@ -18,8 +18,9 @@ Ensuring a consistent and organized approach to testing is pivotal in any develo
 
 > As well as keeping your code tidy, using this naming convention also allows you to use TestDriven.Net's 'Go To Test/Code' command.
 > This navigates between your tests and code under test (and back). This is something that test-driven developers end up doing a lot.
-> Screen captures at https://weblogs.asp.net/nunitaddin/testdriven-net-3-0-all-systems-go
-> - Jamie Cansdale
+> Screen captures at <https://weblogs.asp.net/nunitaddin/testdriven-net-3-0-all-systems-go>
+>
+> * Jamie Cansdale
 
 <!--endintro-->
 
@@ -40,7 +41,6 @@ The main reason why we are categorizing tests is so that we can run different te
 * Integration tests after each check in on the build server
 * All tests including the functional tests in the nightly build
 
-
 #### Samples for Naming of test projects
 
 **Test.Unit.WebUI:** This test project, tests the WebUI project, and is independent of external resources.
@@ -57,7 +57,6 @@ That means if any external resource is unavailable, the tests will fail.
 
 #### Samples Naming of test methods
 
-
 ```cs
 [TestMethod]
  public void Test_Client()
@@ -67,7 +66,6 @@ That means if any external resource is unavailable, the tests will fail.
 Bad example: There is no way to guess what this test does; you have to read the source
 :::
 
-
 ```cs
 [TestMethod]
  public void PubSubServiceConnectTest_AuctionOk_AuctionInfoReturned()