Basic configuration to add
* '{@code Expires}' and '{@code Cache-Control: max-age=}'
- * headers to images, css and javascript
+ * headers to images, css and JavaScript
*
*
* {@code
diff --git a/webapps/docs/config/filter.xml b/webapps/docs/config/filter.xml
index e6bb2cfd26ee..eef71dfb0120 100644
--- a/webapps/docs/config/filter.xml
+++ b/webapps/docs/config/filter.xml
@@ -508,7 +508,7 @@ HTTP/1.1 200 OK
Basic configuration to add 'Expires' and 'Cache-Control: max-age='
- headers to images, css and javascript.
+ headers to images, css and JavaScript.
diff --git a/webapps/docs/ssi-howto.xml b/webapps/docs/ssi-howto.xml
index f697ac6d1eb4..464a97ec30f7 100644
--- a/webapps/docs/ssi-howto.xml
+++ b/webapps/docs/ssi-howto.xml
@@ -61,7 +61,7 @@ is mapped to the URL pattern "*.shtml".
is mapped to the URL pattern "*.shtml", though it can be mapped to "*" as
it will selectively enable/disable SSI processing based on mime types. The
contentType init param allows you to apply SSI processing to JSP pages,
-javascript, or any other content you wish.
+JavaScript, or any other content you wish.
By default SSI support is disabled in Tomcat.
diff --git a/webapps/docs/ssl-howto.xml b/webapps/docs/ssl-howto.xml
index 4262c4ca1e4b..65708b424aa2 100644
--- a/webapps/docs/ssl-howto.xml
+++ b/webapps/docs/ssl-howto.xml
@@ -155,7 +155,7 @@ scenarios, they are not suitable for any form of production use.
When securing a website with SSL it's important to make sure that all assets
that the site uses are served over SSL, so that an attacker can't bypass
-the security by injecting malicious content in a javascript file or similar. To
+the security by injecting malicious content in a JavaScript file or similar. To
further enhance the security of your website, you should evaluate to use the
HSTS header. It allows you to communicate to the browser that your site should
always be accessed over https.