From 68bcb8929174d232b301c9fb20525b50d19df92e Mon Sep 17 00:00:00 2001
From: Mark Otto <markd.otto@gmail.com>
Date: Thu, 30 Apr 2015 14:39:57 -0700
Subject: [PATCH] Update buttons.md

---
 docs/components/buttons.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/components/buttons.md b/docs/components/buttons.md
index 9b10ac2216..62727fba49 100644
--- a/docs/components/buttons.md
+++ b/docs/components/buttons.md
@@ -37,9 +37,9 @@ Using color to add meaning to a button only provides a visual indication, which
 
 ## Button tags
 
-In most cases, the `<button>` element should be used with our `.btn` classes as some browsers render the following elements slightly differently. However, you may also use button classes on `<a>`, `<button>`, or `<input>` elements.
+The `.btn` classes are designed to be used with the `<button>` element. However, you can also use these classes on `<a>` or `<input>` elements (though some browsers may apply a slightly different rendering).
 
-When using button classes on `<a>` elements, sometimes you'll want to include `role="button"` for improved accessibility. This only applies to buttons that trigger in-page functionality (like collapsing content), and not linking to new pages or sections within the current page.
+When using button classes on `<a>` elements that are used to trigger in-page functionality (like collapsing content), rather than linking to new pages or sections within the current page, these links should be given a `role="button"` to appropriately convey their purpose to assistive technologies such as screen readers.
 
 {% example html %}
 <a class="btn btn-secondary" href="#" role="button">Link</a>
-- 
2.47.2