From 8174f6c4090de0c3aacc4c3029754bd1c67233e3 Mon Sep 17 00:00:00 2001
From: Mark Otto <markd.otto@gmail.com>
Date: Thu, 30 Apr 2015 11:40:54 -0700
Subject: [PATCH] update buttons role copy

/cc @cvrebert @patrickhlauke
---
 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 f84376c610..9b10ac2216 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
 
-As a best practice, **we highly recommend using the `<button>` element whenever possible** to ensure matching cross-browser rendering. However, you may also use button classes on `<a>`, `<button>`, or `<input>` elements.
+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.
 
-When using button classes on `<a>` elements, be sure to include the `role="button"` for improved accessibility.
+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.
 
 {% example html %}
 <a class="btn btn-secondary" href="#" role="button">Link</a>