Use `h5` for callouts so that they are not included in ToC.

Callouts are already excluded from ToC, but due to a limitation in jekyll-toc they are still being included.

We should revisit this if the bug is fixed later.

diff --git a/site/_includes/callout-danger-async-methods.md b/site/_includes/callout-danger-async-methods.md
index 083f28f238902809412cf5ec8278038d5d7121bd..951ba76ccf3afd76adffbb682eb32cdd2ab3a755 100644 (file)
--- a/site/_includes/callout-danger-async-methods.md
+++ b/site/_includes/callout-danger-async-methods.md
@@ -1,5 +1,5 @@
 {% capture callout %}
-#### Asynchronous methods and transitions
+##### Asynchronous methods and transitions
 
 All API methods are **asynchronous** and start a **transition**. They return to the caller as soon as the transition is started but **before it ends**. In addition, a method call on a **transitioning component will be ignored**.
 

diff --git a/site/docs/4.1/components/forms.md b/site/docs/4.1/components/forms.md
index 29f7fc10bc59d1dea29977398aeae4810fe87e73..1ea3e1a4d3a7e36f81265119145ba39e3c397d4d 100644 (file)
--- a/site/docs/4.1/components/forms.md
+++ b/site/docs/4.1/components/forms.md
@@ -737,7 +737,7 @@ By default, browsers will treat all native form controls (`<input>`, `<select>`
 {% include callout.html content=callout type="warning" %}
 
 {% capture callout %}
-#### Cross-browser compatibility
+##### Cross-browser compatibility
 
 While Bootstrap will apply these styles in all browsers, Internet Explorer 11 and below don't fully support the `disabled` attribute on a `<fieldset>`. Use custom JavaScript to disable the fieldset in these browsers.
 {% endcapture %}

diff --git a/site/docs/4.1/components/popovers.md b/site/docs/4.1/components/popovers.md
index f55826d7cae4392c6e54a1a855e14a2fea44fa8d..d26cb278a6b2dc90bdbbbc112b0b32f8ce30cbe3 100644 (file)
--- a/site/docs/4.1/components/popovers.md
+++ b/site/docs/4.1/components/popovers.md
@@ -99,7 +99,7 @@ sagittis lacus vel augue laoreet rutrum faucibus.">
 Use the `focus` trigger to dismiss popovers on the user's next click of a different element than the toggle element.
 
 {% capture callout %}
-#### Specific markup required for dismiss-on-next-click
+##### Specific markup required for dismiss-on-next-click
 
 For proper cross-browser and cross-platform behavior, you must use the `<a>` tag, _not_ the `<button>` tag, and you also must include a [`tabindex`](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex) attribute.
 {% endcapture %}
@@ -253,7 +253,7 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap
 </table>
 
 {% capture callout %}
-#### Data attributes for individual popovers
+##### Data attributes for individual popovers
 
 Options for individual popovers can alternatively be specified through the use of data attributes, as explained above.
 {% endcapture %}

diff --git a/site/docs/4.1/components/scrollspy.md b/site/docs/4.1/components/scrollspy.md
index 3c52f82510c6a32f8569b0c014dfa585558a0567..015e0ca42d1ab1f22b6c4d756c1000af2cf759f1 100644 (file)
--- a/site/docs/4.1/components/scrollspy.md
+++ b/site/docs/4.1/components/scrollspy.md
@@ -257,14 +257,14 @@ $('body').scrollspy({ target: '#navbar-example' })
 {% endhighlight %}
 
 {% capture callout %}
-#### Resolvable ID targets required
+##### Resolvable ID targets required
 
 Navbar links must have resolvable id targets. For example, a `<a href="#home">home</a>` must correspond to something in the DOM like `<div id="home"></div>`.
 {% endcapture %}
 {% include callout.html content=callout type="danger" %}
 
 {% capture callout %}
-#### Non-`:visible` target elements ignored
+##### Non-`:visible` target elements ignored
 
 Target elements that are not [`:visible` according to jQuery](https://api.jquery.com/visible-selector/) will be ignored and their corresponding nav items will never be highlighted.
 {% endcapture %}

diff --git a/site/docs/4.1/components/tooltips.md b/site/docs/4.1/components/tooltips.md
index aa3ebe077cf26606ffc523278c3887ccf6a645df..fffa795fd1cb102594b2c5c34f798d2c29b2a63c 100644 (file)
--- a/site/docs/4.1/components/tooltips.md
+++ b/site/docs/4.1/components/tooltips.md
@@ -254,7 +254,7 @@ Options can be passed via data attributes or JavaScript. For data attributes, ap
 </table>
 
 {% capture callout %}
-#### Data attributes for individual tooltips
+##### Data attributes for individual tooltips
 
 Options for individual tooltips can alternatively be specified through the use of data attributes, as explained above.
 {% endcapture %}

diff --git a/site/docs/4.1/getting-started/javascript.md b/site/docs/4.1/getting-started/javascript.md
index 7f59ac213a982bda15532b0bb03ca0b38114d1bd..534e2fd42056e17a14c34e345163cacbd943aa61 100644 (file)
--- a/site/docs/4.1/getting-started/javascript.md
+++ b/site/docs/4.1/getting-started/javascript.md
@@ -35,7 +35,7 @@ $(document).off('.alert.data-api')
 {% endhighlight %}
 
 {% capture callout %}
-## Selectors
+##### Selectors
 
 Currently to query DOM elements we use the native methods `querySelector` and `querySelectorAll` for performance reasons, so you have to use [valid selectors](https://www.w3.org/TR/CSS21/syndata.html#value-def-identifier).
 If you use special selectors, for example: `collapse:Example` be sure to escape them.

diff --git a/site/docs/4.1/utilities/colors.md b/site/docs/4.1/utilities/colors.md
index 55699adb8c72c20838ae058d1204cb0358b2dcdb..a1b1a9816fb65b55123d06066ee4f2aae74b696f 100644 (file)
--- a/site/docs/4.1/utilities/colors.md
+++ b/site/docs/4.1/utilities/colors.md
@@ -49,7 +49,7 @@ When `$enable-gradients` is set to `true` (default is `false`), you can use `.bg
 - `.bg-gradient-{{ color.name }}`{% endfor %}
 
 {% capture callout %}
-#### Dealing with specificity
+##### Dealing with specificity
 
 Sometimes contextual classes cannot be applied due to the specificity of another selector. In some cases, a sufficient workaround is to wrap your element's content in a `<div>` with the class.
 {% endcapture %}