Fix case of JavaScript, Markdown and TypeScript

.gitignore

@@ -39,7 +39,7 @@ build/Release
 node_modules/
 jspm_packages/
 
-# Typescript v1 declaration files
+# TypeScript v1 declaration files
 typings/
 
 # Optional npm cache directory

src/components/mdx/code-block.js

@@ -62,7 +62,7 @@ const CodeBlock = props => {
   let codeFrontmatter = {}
 
   // For now, we don’t support code frontmatter
-  // in markdown code blocks because markdown
+  // in Markdown code blocks because Markdown
   // itself can contain frontmatter.
 
   // TODO: find workaround for this limitation

src/content/docs-engine/docs-flavored-markdown.md

@@ -133,7 +133,7 @@ If you need to take advantage of Gatsby’s routing but you want control over th
 
 ## Images
 
-Images are added by simply using the markdown syntax.
+Images are added by simply using the Markdown syntax.
 
 ```markdown
 ![Wall of entropy](./wall-of-entropy.jpg)
@@ -361,7 +361,7 @@ Use blockquotes when quoting someone. For example, here’s a translation of a q
 
 > If you want to get fancy with it you can use
 > [links](https://example.com) and `<code/>`, and
-> really just about any another inline markdown.
+> really just about any another inline Markdown.
 >
 > Multiple paragraphs can be added as well. And of
 > course you can use **bold** or _italics_. And
@@ -372,7 +372,7 @@ Use blockquotes when quoting someone. For example, here’s a translation of a q
 ```markdown
 > If you want to get fancy with it you can use
 > [links](https://example.com) and `<code/>`, and
-> really just about any another inline markdown.
+> really just about any another inline Markdown.
 >
 > Multiple paragraphs can be added as well. And of
 > course you can use **bold** or _italics_. And

src/content/docs-engine/site-configuration.md

@@ -33,7 +33,7 @@ module.exports = {
       // https://developers.cloudflare.com/docs/
       productLogoPathD: "M13.112 9.832c.164-.276.362-[...]",
 
-      // The GitHub repo where the markdown files live,
+      // The GitHub repo where the Markdown files live,
       // currently only used for "Edit on GitHub" links
       contentRepo: "cloudflare/workers-docs",
 

src/content/learning/how-the-cache-works.md

@@ -32,7 +32,7 @@ Conceptually, there are two ways to interact with Cloudflare’s Cache using a W
 
 The browser cache is controlled through the `Cache-Control` header sent in the response to the eyeball (the response passed or promised to `event.respondWith()`). Workers can customize browser cache behavior by setting this header on the response.
 
-We won’t discuss in this article, but other means to control Cloudflare’s cache include: Page rules and Cloudflare cache settings. I highly recommend the article [How to Control Cloudflare’s cache](https://support.cloudflare.com/hc/en-us/articles/202775670) if you wish to avoid writing Javascript with still some granularity of control.
+We won’t discuss in this article, but other means to control Cloudflare’s cache include: Page rules and Cloudflare cache settings. I highly recommend the article [How to Control Cloudflare’s cache](https://support.cloudflare.com/hc/en-us/articles/202775670) if you wish to avoid writing JavaScript with still some granularity of control.
 
 **What should I use: the Cache API or fetch for caching objects on Cloudflare?**