From 1b588fa76d7abbfca4bb9e69b4b698cb6980a416 Mon Sep 17 00:00:00 2001 From: Jim Hoskins Date: Tue, 22 Feb 2011 07:33:26 +0800 Subject: [PATCH] Updated grammatical errors in docs Changed "an" to "a" where appropriate --- docs/content/content-themes.html | 10 +++++----- docs/pages/docs-link-scenarios.html | 2 +- docs/pages/docs-navmodel.html | 2 +- docs/toolbars/docs-headers.html | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/content/content-themes.html b/docs/content/content-themes.html index a95be15f..0e076d33 100755 --- a/docs/content/content-themes.html +++ b/docs/content/content-themes.html @@ -40,7 +40,7 @@

H1 Heading

This is a paragraph that contains strong, emphasized and linked text. Here is more text so you can see how HTML markup works in content. Here is more text so you can see how HTML markup works in content.

-

I'm an themed collapsible

+

I'm a themed collapsible

I have data-theme attribute set manually on my container to set the color to match the content block I'm in.

@@ -50,7 +50,7 @@

H1 Heading

This is a paragraph that contains strong, emphasized and linked text. Here is more text so you can see how HTML markup works in content. Here is more text so you can see how HTML markup works in content.

-

I'm an themed collapsible

+

I'm a themed collapsible

I have data-theme attribute set manually on my container to set the color to match the content block I'm in.

@@ -60,7 +60,7 @@

H1 Heading

This is a paragraph that contains strong, emphasized and linked text. Here is more text so you can see how HTML markup works in content. Here is more text so you can see how HTML markup works in content.

-

I'm an themed collapsible

+

I'm a themed collapsible

I have data-theme attribute set manually on my container to set the color to match the content block I'm in.

@@ -70,7 +70,7 @@

H1 Heading

This is a paragraph that contains strong, emphasized and linked text. Here is more text so you can see how HTML markup works in content. Here is more text so you can see how HTML markup works in content.

-

I'm an themed collapsible

+

I'm a themed collapsible

I have data-theme attribute set manually on my container to set the color to match the content block I'm in.

@@ -80,7 +80,7 @@

H1 Heading

This is a paragraph that contains strong, emphasized and linked text. Here is more text so you can see how HTML markup works in content. Here is more text so you can see how HTML markup works in content.

-

I'm an themed collapsible

+

I'm a themed collapsible

I have data-theme attribute set manually on my container to set the color to match the content block I'm in.

diff --git a/docs/pages/docs-link-scenarios.html b/docs/pages/docs-link-scenarios.html index 4171a7e4..ffa4904c 100755 --- a/docs/pages/docs-link-scenarios.html +++ b/docs/pages/docs-link-scenarios.html @@ -26,7 +26,7 @@
  • [href="docs/pages/index.html"]
  • [href="/docs/toolbars/index.html"]
  • [href="#somelocalID"]
    • -
  • Note: an full URL to the same-domain will also work
    • +
  • Note: a full URL to the same-domain will also work
  • Examples of links that trigger a refresh
  • [data-ajax="false"]
  • [rel="external"]
    • diff --git a/docs/pages/docs-navmodel.html b/docs/pages/docs-navmodel.html index 45807f9a..f83e60c2 100644 --- a/docs/pages/docs-navmodel.html +++ b/docs/pages/docs-navmodel.html @@ -61,7 +61,7 @@

    Some plugins may choose to dynamically break a page's content into separate navigable pages, which can then be reached via deep links. One example of this would be the Listview plugin, which will break a nested UL (or OL) into separate pages, which are each given a data-url attribute so they can be linked to like any normal "page" in jQuery Mobile. However, in order to link to these pages, the page that generates them must first be requested from the server. To make this work, pages that are auto-generated by plugins use the following special data-url structure: <div data-url="page.html&subpageidentifier">

    -

    So, for example, a page generated by the listview plugin may have an data-url attribute like this: data-url="artists.html&ui-page=listview-1"

    +

    So, for example, a page generated by the listview plugin may have a data-url attribute like this: data-url="artists.html&ui-page=listview-1"

    When a page is requested, jQuery Mobile knows to split the URL at "&ui-page" and make an HTTP request to the portion of the URL before that key. In the case of the listview example mentioned above, the URL would look like this: http://example.com/artists.html&ui-page=listview-1 ...and jQuery Mobile would request artists.html, which would then generate its sub-pages, creating the div with data-url="artists.html&ui-page=listview-1", which it will then display as the active page.

    diff --git a/docs/toolbars/docs-headers.html b/docs/toolbars/docs-headers.html index 0590bf3e..32484b8d 100755 --- a/docs/toolbars/docs-headers.html +++ b/docs/toolbars/docs-headers.html @@ -20,7 +20,7 @@

    Header structure

    -

    The header is an toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the the left and/or right of the title for navigation or actions.

    +

    The header is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the the left and/or right of the title for navigation or actions.

    The title text is normally an H1 heading element but it's possible to use any heading level (H1-H6) to allow for semantic flexibility. For example, a page containing multiple mobile 'pages' may use a H1 element on the home 'page' and a H2 element on the secondary pages. All heading levels are styled identically by default to maintain visual consistency.