[1.8.x] Updated capitalization in the word "JavaScript" for consistency

Backport of 08c980d752 from master

docs/topics/forms/media.txt

@@ -207,7 +207,7 @@ be prepended with the value of the appropriate prefix.
 
 As part of the introduction of the
 :doc:`staticfiles app </ref/contrib/staticfiles>` two new settings were added
-to refer to "static files" (images, CSS, Javascript, etc.) that are needed
+to refer to "static files" (images, CSS, JavaScript, etc.) that are needed
 to render a complete web page: :setting:`STATIC_URL` and :setting:`STATIC_ROOT`.
 
 To find the appropriate prefix to use, Django will check if the

docs/topics/i18n/formatting.txt

@@ -64,7 +64,7 @@ will try to use a locale specific format whenever it outputs a value
 in a template.
 
 However, it may not always be appropriate to use localized values --
-for example, if you're outputting Javascript or XML that is designed
+for example, if you're outputting JavaScript or XML that is designed
 to be machine-readable, you will always want unlocalized values. You
 may also want to use localization in selected templates, rather than
 using localization everywhere.

docs/topics/i18n/translation.txt

@@ -1167,7 +1167,7 @@ whenever you restart your application server.
     def cached_javascript_catalog(request, domain='djangojs', packages=None):
         return javascript_catalog(request, domain, packages)
 
-You can even pre-generate the javascript catalog as part of your deployment
+You can even pre-generate the JavaScript catalog as part of your deployment
 procedure and serve it as a static file. This radical technique is implemented
 in django-statici18n_.