From d5d78f46e1195599b3c4dcb4eef1d75ab9668a1b Mon Sep 17 00:00:00 2001
From: toddparker <todd@filamentgroup.com>
Date: Thu, 17 Nov 2011 11:42:49 -0500
Subject: [PATCH] Tweaks to custom select menu pages

---
 docs/forms/selects/custom.html | 1 +
 docs/forms/selects/index.html  | 6 +++++-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/forms/selects/custom.html b/docs/forms/selects/custom.html
index ce7f4266..5f220645 100644
--- a/docs/forms/selects/custom.html
+++ b/docs/forms/selects/custom.html
@@ -32,6 +32,7 @@
 	<li><a href="events.html" data-role="button" data-transition="fade">Events</a></li>
 </ul>
 
+<h2>Custom select menus</h2>
 <p>The framework is capable of building a custom menu based on the <code>select</code> element's list of options.  We recommend using a custom menu when multiple selections are required, or when the menu itself must be styled with CSS.</p>
 
 <p>You can optionally use custom-styled select menus instead of the native OS menu. The custom menu supports disabled options and multiple selection (whereas native mobile OS support for both is inconsistent), adds an elegant way to handle placeholder values, and restores missing functionality on certain platforms such as <code>optgroup</code> support on Android (all explained below).  In addition, the framework applies the custom button's theme to the menu to better match the look and feel and provide visual consistency across platforms. Lastly, custom menus often look better on desktop browsers because native desktop menus are smaller than their mobile counterparts and tend to look disproportionate.</p>
diff --git a/docs/forms/selects/index.html b/docs/forms/selects/index.html
index a613b649..446c3944 100644
--- a/docs/forms/selects/index.html
+++ b/docs/forms/selects/index.html
@@ -403,7 +403,11 @@ $('select').selectmenu();
 		</select>
 	</div>
 	
-	<p>For the sake of advanced styling, the framework also offers a method of generating <a href="custom.html">custom menus</a> from existing select menu markup. You can optionally use custom-styled select menus instead of the native OS menu. The custom menu supports disabled options and multiple selection (whereas native mobile OS support for both is inconsistent), adds an elegant way to handle placeholder values, and restores missing functionality on certain platforms such as <code>optgroup</code> support on Android.</p>
+	<h2>Custom select menus</h2>
+	<p>For the sake of advanced styling, the framework also offers a method of generating <a href="custom.html">custom menus</a> from existing select menu markup  instead of the native OS menu. The custom menu supports disabled options and multiple selection (whereas native mobile OS support for both is inconsistent), adds an elegant way to handle placeholder values, and restores missing functionality on certain platforms such as <code>optgroup</code> support on Android.
+		
+	<a href="custom.html" data-role="button">Custom select menu docs</a>
+		</p>
 	
 	</div><!--/content-primary -->