JavaScript case sensitive typos

book/forms.rst

@@ -1691,7 +1691,7 @@ There's still much more to learn about the powerful world of forms, such as
 how to handle
 :doc:`file uploads with Doctrine </cookbook/doctrine/file_uploads>` or how
 to create a form where a dynamic number of sub-forms can be added (e.g. a
-todo list where you can keep adding more fields via Javascript before submitting).
+todo list where you can keep adding more fields via JavaScript before submitting).
 See the cookbook for these topics. Also, be sure to lean on the
 :doc:`field type reference documentation </reference/forms/types>`, which
 includes examples of how to use each field type and its options.

book/page_creation.rst

@@ -95,7 +95,7 @@ inside a bundle.
 
 A bundle is nothing more than a directory that houses everything related
 to a specific feature, including PHP classes, configuration, and even stylesheets
-and Javascript files (see :ref:`page-creation-bundles`).
+and JavaScript files (see :ref:`page-creation-bundles`).
 
 To create a bundle called ``AcmeHelloBundle`` (a play bundle that you'll
 build in this chapter), run the following command and follow the on-screen

book/templating.rst

@@ -679,7 +679,7 @@ Asynchronous Content with hinclude.js
 .. versionadded:: 2.1
     hinclude.js support was added in Symfony 2.1
 
-Controllers can be embedded asynchronously using the hinclude.js_ javascript library.
+Controllers can be embedded asynchronously using the hinclude.js_ JavaScript library.
 As the embedded content comes from another page (or controller for that matter),
 Symfony2 uses a version of the standard ``render`` function to configure ``hinclude``
 tags:
@@ -744,7 +744,7 @@ tags:
                 'fragments' => array('path' => '/_fragment'),
             ));
 
-Default content (while loading or if javascript is disabled) can be set globally
+Default content (while loading or if JavaScript is disabled) can be set globally
 in your application configuration:
 
 .. configuration-block::
@@ -974,7 +974,7 @@ correctly:
 Linking to Assets
 ~~~~~~~~~~~~~~~~~
 
-Templates also commonly refer to images, Javascript, stylesheets and other
+Templates also commonly refer to images, JavaScript, stylesheets and other
 assets. Of course you could hard-code the path to these assets (e.g. ``/images/logo.png``),
 but Symfony2 provides a more dynamic option via the ``asset`` Twig function:
 
@@ -1007,29 +1007,29 @@ look like ``/images/logo.png?v2``. For more information, see the :ref:`ref-frame
 configuration option.
 
 .. index::
-   single: Templating; Including stylesheets and Javascripts
+   single: Templating; Including stylesheets and JavaScripts
    single: Stylesheets; Including stylesheets
-   single: Javascript; Including Javascripts
+   single: JavaScript; Including JavaScripts
 
-Including Stylesheets and Javascripts in Twig
+Including Stylesheets and JavaScripts in Twig
 ---------------------------------------------
 
-No site would be complete without including Javascript files and stylesheets.
+No site would be complete without including JavaScript files and stylesheets.
 In Symfony, the inclusion of these assets is handled elegantly by taking
 advantage of Symfony's template inheritance.
 
 .. tip::
 
     This section will teach you the philosophy behind including stylesheet
-    and Javascript assets in Symfony. Symfony also packages another library,
+    and JavaScript assets in Symfony. Symfony also packages another library,
     called Assetic, which follows this philosophy but allows you to do much
     more interesting things with those assets. For more information on
     using Assetic see :doc:`/cookbook/assetic/asset_management`.
 
 Start by adding two blocks to your base template that will hold your assets:
 one called ``stylesheets`` inside the ``head`` tag and another called ``javascripts``
 just above the closing ``body`` tag. These blocks will contain all of the
-stylesheets and Javascripts that you'll need throughout your site:
+stylesheets and JavaScripts that you'll need throughout your site:
 
 .. code-block:: html+jinja
 
@@ -1052,7 +1052,7 @@ stylesheets and Javascripts that you'll need throughout your site:
     </html>
 
 That's easy enough! But what if you need to include an extra stylesheet or
-Javascript from a child template? For example, suppose you have a contact
+JavaScript from a child template? For example, suppose you have a contact
 page and you need to include a ``contact.css`` stylesheet *just* on that
 page. From inside that contact page's template, do the following:
 

components/css_selector.rst

@@ -32,8 +32,8 @@ long and unwieldy expressions.
 
 Many developers -- particularly web developers -- are more comfortable
 using CSS selectors to find elements. As well as working in stylesheets,
-CSS selectors are used in Javascript with the ``querySelectorAll`` function
-and in popular Javascript libraries such as jQuery, Prototype and MooTools.
+CSS selectors are used in JavaScript with the ``querySelectorAll`` function
+and in popular JavaScript libraries such as jQuery, Prototype and MooTools.
 
 CSS selectors are less powerful than XPath, but far easier to write, read
 and understand. Since they are less powerful, almost all CSS selectors can

cookbook/assetic/apply_to_option.rst

@@ -7,7 +7,7 @@ How to Apply an Assetic Filter to a Specific File Extension
 Assetic filters can be applied to individual files, groups of files or even,
 as you'll see here, files that have a specific extension. To show you how
 to handle each option, let's suppose that you want to use Assetic's CoffeeScript
-filter, which compiles CoffeeScript files into Javascript.
+filter, which compiles CoffeeScript files into JavaScript.
 
 The main configuration is just the paths to coffee, node and node_modules.
 An example configuration might look like this:

cookbook/assetic/uglifyjs.rst

@@ -4,8 +4,8 @@
 How to Minify CSS/JS Files (using UglifyJs and UglifyCss)
 =========================================================
 
-`UglifyJs`_ is a javascript parser/compressor/beautifier toolkit. It can be used
-to combine and minify javascript assets so that they require less HTTP requests
+`UglifyJs`_ is a JavaScript parser/compressor/beautifier toolkit. It can be used
+to combine and minify JavaScript assets so that they require less HTTP requests
 and make your site load faster. `UglifyCss`_ is a css compressor/beautifier
 that is very similar to UglifyJs.
 

cookbook/assetic/yuicompressor.rst

@@ -103,7 +103,7 @@ the view layer, this work is done in your templates:
 
     The above example assumes that you have a bundle called ``AcmeFooBundle``
     and your JavaScript files are in the ``Resources/public/js`` directory under
-    your bundle. This isn't important however - you can include your Javascript
+    your bundle. This isn't important however - you can include your JavaScript
     files no matter where they are.
 
 With the addition of the ``yui_js`` filter to the asset tags above, you should

cookbook/controller/error_pages.rst

@@ -68,7 +68,7 @@ end-user, create a new template located at
 
 In addition to the standard HTML error page, Symfony provides a default error
 page for many of the most common response formats, including JSON
-(``error.json.twig``), XML (``error.xml.twig``) and even Javascript
+(``error.json.twig``), XML (``error.xml.twig``) and even JavaScript
 (``error.js.twig``), to name a few. To override any of these templates, just
 create a new file with the same name in the
 ``app/Resources/TwigBundle/views/Exception`` directory. This is the standard