From 1bde860c016b75ca0df7b684fa8a7e3ca07e18b6 Mon Sep 17 00:00:00 2001
From: Mike Jacobson <michaeljjacobson1@gmail.com>
Date: Sun, 1 Oct 2017 15:26:37 -0700
Subject: [PATCH] Clarify ScrollSpy 'activate' event element

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

diff --git a/docs/4.0/components/scrollspy.md b/docs/4.0/components/scrollspy.md
index 32a86d839f..b7f9e994fd 100644
--- a/docs/4.0/components/scrollspy.md
+++ b/docs/4.0/components/scrollspy.md
@@ -316,13 +316,13 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap
   <tbody>
     <tr>
       <td>activate.bs.scrollspy</td>
-      <td>This event fires whenever a new item becomes activated by the scrollspy.</td>
+      <td>This event fires on the scroll element whenever a new item becomes activated by the scrollspy.</td>
     </tr>
   </tbody>
 </table>
 
 {% highlight js %}
-$('#myScrollspy').on('activate.bs.scrollspy', function () {
+$('[data-spy="scroll"]').on('activate.bs.scrollspy', function () {
   // do something…
 })
 {% endhighlight %}
-- 
2.47.2