rename classes from .bs-docs and .bs to .bd

3 files changed, 3 insertions, 3 deletions

diff --git a/docs/getting-started/accessibility.md b/docs/getting-started/accessibility.md
index c20085ff8..25bc36acc 100644
--- a/docs/getting-started/accessibility.md
+++ b/docs/getting-started/accessibility.md
@@ -9,7 +9,7 @@ Bootstrap follows common web standards and—with minimal extra effort—can be
 
 If your navigation contains many links and comes before the main content in the DOM, add a `Skip to main content` link before the navigation (for a simple explanation, see this [A11Y Project article on skip navigation links](http://a11yproject.com/posts/skip-nav-links/)). Using the `.sr-only` class will visually hide the skip link, and the <code>.sr-only-focusable</code> class will ensure that the link becomes visible once focused (for sighted keyboard users).
 
-<div class="bs-callout bs-callout-danger" id="callout-skiplinks">
+<div class="bd-callout bd-callout-danger" id="callout-skiplinks">
   <p>Due to long-standing shortcomings/bugs in Chrome (see <a href="https://code.google.com/p/chromium/issues/detail?id=262171" title="Chromium bug tracker - Issue 262171: Focus should cycle from named anchor">issue 262171 in the Chromium bug tracker</a>) and Internet Explorer (see this article on <a href="http://accessibleculture.org/articles/2010/05/in-page-links/">in-page links and focus order</a>), you will need to make sure that the target of your skip link is at least programmatically focusable by adding <code>tabindex="-1"</code>.</p>
   <p>In addition, you may want to explicitly suppress a visible focus indication on the target (particularly as Chrome currently also sets focus on elements with <code>tabindex="-1"</code> when they are clicked with the mouse) with <code>#content:focus { outline: none; }</code>.</p>
   <p>Note that this bug will also affect any other in-page links your site may be using, rendering them useless for keyboard users. You may consider adding a similar stop-gap fix to all other named anchors / fragment identifiers that act as link targets.</p>
diff --git a/docs/getting-started/contents.md b/docs/getting-started/contents.md
index 15de28618..811c60f44 100644
--- a/docs/getting-started/contents.md
+++ b/docs/getting-started/contents.md
@@ -5,7 +5,7 @@ title: Contents
 
 Bootstrap can come in one of two forms, as precompiled or source code. Learn more about each form's contents and structure below.
 
-<div class="bs-callout bs-callout-warning" id="jquery-required">
+<div class="bd-callout bd-callout-warning" id="jquery-required">
   <h4>jQuery required</h4>
   <p>Please note that <strong>all JavaScript plugins require jQuery</strong> to be included, as shown in the <a href="../quick-start">starter template</a>. <a href="{{ site.repo }}/blob/v{{ site.current_version }}/bower.json">Consult our <code>bower.json</code></a> to see which versions of jQuery are supported.</p>
 </div>
diff --git a/docs/getting-started/javascript.md b/docs/getting-started/javascript.md
index 08576cdf7..eafa473d5 100644
--- a/docs/getting-started/javascript.md
+++ b/docs/getting-started/javascript.md
@@ -87,7 +87,7 @@ $.fn.tooltip.Constructor.VERSION // => "{{ site.current_version }}"
 
 Bootstrap's plugins don't fall back particularly gracefully when JavaScript is disabled. If you care about the user experience in this case, use [`<noscript>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/noscript) to explain the situation (and how to re-enable JavaScript) to your users, and/or add your own custom fallbacks.
 
-<div class="bs-callout bs-callout-warning" id="callout-third-party-libs">
+<div class="bd-callout bd-callout-warning" id="callout-third-party-libs">
   <h4>Third-party libraries</h4>
   <p><strong>Bootstrap does not officially support third-party JavaScript libraries</strong> like Prototype or jQuery UI. Despite <code>.noConflict</code> and namespaced events, there may be compatibility problems that you need to fix on your own.</p>
 </div>