quotes

stacyspiva · stacyspiva · commit 0315618ae821 · 2018-11-01T14:33:56.000-07:00
diff --git a/docs/hackers/create-a-directory-page.md b/docs/hackers/create-a-directory-page.md
@@ -8,7 +8,8 @@ As the directory doesn’t contain every single organization, hackers with a rep
 
 In order to create a directory entry:
 1. Search the [directory](https://hackerone.com/directory) to see whether the organization already has an existing directory page.
-2. Click <b>Submit a program</b> if no matching entry exists. <i>Note: Only hackers with a reputation of at least 1000 will be able to see this button and create a page.</i>
+2. Click <b>Submit a program</b> if no matching entry exists.
+><i><b>Note:</b> Only hackers with a reputation of at least 1000 will be able to see this button and create a page.</i>
 
 ![create-a-directory-1](./images/create-a-directory-1.png)
 
@@ -18,4 +19,4 @@ In order to create a directory entry:
 
 4. Click <b>Submit Program</b>.
 
-Programs will be visible on the directory as soon as the directory is created.  When an employee of the organization chooses to own and manage the profile, they can [submit a claim](/programs/security-page.html). 
+Programs will be visible on the directory as soon as the directory is created.  When an employee of the organization chooses to own and manage the profile, they can [submit a claim](/programs/security-page.html).
diff --git a/docs/hackers/retesting.md b/docs/hackers/retesting.md
@@ -6,7 +6,7 @@ id: "hackers/retesting"
 
 As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of data. Programs can elect to invite you and other hackers to retest your vulnerabilities to verify fixes.  
 
-<i>This is a new feature that is currently in the beta phase and only select programs are testing this feature out. If you’re a part of those programs, you may be invited to retest the vulnerability fixes. There’s currently no effect to reputation for participating in the retest, and there’s also no time limit to complete it.</i>
+><i>This is a new feature that is currently in the beta phase and only select programs are testing this feature out. If you’re a part of those programs, you may be invited to retest the vulnerability fixes. There’s currently no effect to reputation for participating in the retest, and there’s also no time limit to complete it.</i>
 
 If you’re invited to retest a vulnerability, you’ll receive an invitation in your email to retest the report.
 
diff --git a/docs/programs/retesting.md b/docs/programs/retesting.md
@@ -6,7 +6,7 @@ id: "programs/retesting"
 
 As programs receive vulnerability reports and work on deploying fixes, they need proof that their vulnerabilities have actually been fixed. Asking hackers to verify whether a vulnerability has been fixed is a good way to secure the protection of your asset’s data. You can elect to invite hackers to retest your vulnerabilities to verify fixes. Each hacker that participates in the retest will receive a $100 bounty upon completion.
 
-<i>Inviting hackers to retest your vulnerabilities is a new feature that is currently in the beta phase. To be a part of the beta testing, please reach out to your program manager.</i>
+><i>Inviting hackers to retest your vulnerabilities is a new feature that is currently in the beta phase. To be a part of the beta testing, please reach out to your program manager.</i>
 
 ### Set Up
 There’s currently no set up on your end that’s needed to enable the feature. Your program manager will enable the feature for you.
