Fix weird highlighting.

Signed-off-by: Matthew Marchese <maffblaster@gentoo.org>

1 files changed, 22 insertions, 28 deletions

diff --git a/get-involved/become-developer/index.md b/get-involved/become-developer/index.md
index 7bc243f..33fa070 100644
--- a/get-involved/become-developer/index.md
+++ b/get-involved/become-developer/index.md
@@ -1,5 +1,5 @@
 ---
-title: Become a Developer
+title: Become a developer
 
 nav1: get-involved
 nav2: become-dev
@@ -7,36 +7,35 @@ nav2-show: true
 nav2-weight: 50
 ---
 <div class="alert alert-info">
-  <strong>Getting Guidance:</strong>
+  <strong>Getting guidance:</strong>
   Your central point of contact for all questions about becoming a developer
-  is the <a href="mailto:recruiters@gentoo.org" class="alert-link">Gentoo Recruiters</a> team.
+  is the <a href="mailto:recruiters@gentoo.org" class="alert-link">Gentoo recruiters</a> team.
   Please do not hesitate to contact them!
 </div>
 
 ## Becoming a developer
 
 There are two interwoven paths for becoming a Gentoo developer. If you would
-like to focus your work on ebuilds, then you are probably interested in <span
-class="bg-danger">becoming a developer with commit access to ::gentoo</span>. If
-you are interested primarily in other areas of contribution, you may prefer to
-<span class="bg-info">become a developer without commit access</span>.
+like to focus your work on ebuilds, then you are probably interested in 
+becoming a developer with commit access to ::gentoo. If you are interested 
+primarily in other areas of contribution, you may prefer to become a developer
+without commit access.
 
 ### Step 1. Contribute
 
 If you would like to help Gentoo, first find yourself something to do. You may
 want to look at our [contribution guide](/get-involved/contribute/), and
 subsequently look through the [Gentoo
-projects](https://wiki.gentoo.org/wiki/Project:Gentoo). <span
-class="bg-danger">For ebuild work, you can try helping out one of the projects
+projects](https://wiki.gentoo.org/wiki/Project:Gentoo). 
+For ebuild work, you can try helping out one of the projects
 that focus on maintaining packages, such as the
 [GNOME](https://wiki.gentoo.org/wiki/Project:GNOME) or
 [KDE](https://wiki.gentoo.org/wiki/Project:KDE) projects. Alternatively, you can
 maintain your own packages or co-maintain other Gentoo packages via the [Proxy
 Maintainers](https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers)
-project.</span> <span class="bg-info">For non-ebuild work, you may want to look
-at other projects, such as [Bug
+project. For non-ebuild work, you may want to look at other projects, such as [Bug
 Wranglers](https://wiki.gentoo.org/wiki/Project:Bug-wranglers) or [Gentoo
-Forums](https://wiki.gentoo.org/wiki/Project:Forums).</span>
+forums](https://wiki.gentoo.org/wiki/Project:Forums).
 
 ### Step 2. Participate
 
@@ -44,7 +43,7 @@ If you enjoy working on Gentoo and would like to stay longer, you should
 consider starting to participate in the community. You should consider joining
 some of [our IRC channels](/get-involved/irc-channels/), subscribing to some of
 [the mailing lists](/get-involved/mailing-lists/) and/or using [Gentoo
-Forums](https://forums.gentoo.org/). This way you get to know more of the Gentoo
+forums](https://forums.gentoo.org/). This way you get to know more of the Gentoo
 developers and users, and they get to know you!
 
 ### Step 3. Find a mentor
@@ -58,21 +57,16 @@ project](https://wiki.gentoo.org/wiki/Project:Mentors).
 ### Step 4. Take quizzes
 
 Before you become an officially recognized Gentoo developer, you are expected to
-learn a few basics on how Gentoo is structured and how it operates. <span
-class="bg-danger">To get commit access, you will also need to know a fair bit
-about ebuilds</span>. To help you get yourself knowledgeable, we have prepared
-<span class="bg-info">one</span> or <span class="bg-danger">two</span> quizzes
-for you to take.
-
-<span class="bg-danger">The prospective developers aiming to obtain commit
-access should take the [ebuild
+learn a few basics on how Gentoo is structured and how it operates. To get commit
+access, you will also need to know a fair bit about ebuilds. To help you get 
+yourself knowledgeable, we have prepared one or two quizzes for you to take.
+
+The prospective developers aiming to obtain commit access should take the [ebuild
 quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/ebuild-quiz.txt),
-followed by the [end
-quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/end-quiz.txt).</span>
-<span class="bg-info">For candidates for developers without commit access, we
-have prepared a less technical [developer
-quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/developer-quiz.txt)
-instead.</span>
+followed by the [end quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/end-quiz.txt).
+For candidates for developers without commit access, we have prepared a less 
+technical [developer quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/developer-quiz.txt)
+instead.
 
 ### Step 5. Get recruited!
 
@@ -88,5 +82,5 @@ developer.
 
 Besides the warm feeling of contributing to Free and Open Source Software you ask?
 
-Okay, there are indeed a few perks: You get an <tt>@gentoo.org</tt> email address, matching IRC cloak,
+Okay, there are indeed a few perks: You get an **@gentoo.org** email address, matching IRC cloak,
 special access flags on our Wiki and Bugzilla, and a few other things to facilitate your development efforts.