fix: node.js -> Node.js (nodejs#2657)

Manually reviewed since casing is intended for emails and some urls.

external/survey-2018/index.html

@@ -218,7 +218,7 @@ <h1>2018 Node.js User Survey Report</h1>
           <div class="section-content row">
             <ul>
               <li type="1">
-                As with last year, the typical node.js user is male, age 31 and college educated.
+                As with last year, the typical Node.js user is male, age 31 and college educated.
               </li>
               <li type="1">
                 A majority are developers (as opposed to dev managers), in small (&lt;100 employees) companies, with 5+ years of professional development experience.
@@ -425,7 +425,7 @@ <h4><i>(By Region)</i></h4>
                 Users are deploying to a variety of platforms, but AWS is most widely used for production and On-premise or AWS for development. Heroku seems to be growing in popularity in APAC and Latin America.
               </li>
               <li type="1">
-                More than 4 in 5 back-end and full stack developers are using node.js frameworks; Express is tops, but Graph QL is increasingly prevalent this wave.
+                More than 4 in 5 back-end and full stack developers are using Node.js frameworks; Express is tops, but Graph QL is increasingly prevalent this wave.
               </li>
               <li type="1">
                 Most are using a transpiler and module bundler (especially full stack and front-end developers). Babel is the preferred transpiler, but Typescript is growing. Webpack continues to dominate the module bundler space.
@@ -2036,7 +2036,7 @@ <h5><i>By Primary Development Focus</i></h5>
                 The impacts may not be immediately clear however: new users are less likely to report positive impacts in many areas.
               </li>
               <li>
-                While it’s not the most widely felt benefit, users in US/CA are more likely than others to say node.js has helped with recruiting.
+                While it’s not the most widely felt benefit, users in US/CA are more likely than others to say Node.js has helped with recruiting.
               </li>
               <li>
                 Despite their positive perceptions, few have been contributing to open source projects for Node.js.

layouts/partials/header.hbs

@@ -2,7 +2,7 @@
   <div class="container">
 
     <a href="/{{site.locale}}/" id="logo">
-      <img src="/static/images/logo.svg" alt="node.js" width="122" height="75">
+      <img src="/static/images/logo.svg" alt="Node.js" width="122" height="75">
     </a>
 
     <nav>

locale/en/blog/announcements/interactive-2015-programming.md

@@ -43,7 +43,7 @@ IoT Session Highlights:
 * Node.js Development for the Next Generation of IoT *with* Melissa Evers-Hood, Software Product Line Manager at Intel Corporation
 * Node.js While Crafting: Make Textile to Compute! *with* Mariko Kosaka, JavaScript Engineer at Scripto
 
-“Node.js has become pervasive within the last few years, with so many community accomplishments to highlight, including forming the new Node.js Foundation and the convergence of io.js and node.js,” said Mikeal Rogers, Community Manager, Node.js Foundation. “We created this conference to help showcase this growth, to accommodate the Node.js community’s many different needs, and to help accelerate adoption as it expands into enterprises.”
+“Node.js has become pervasive within the last few years, with so many community accomplishments to highlight, including forming the new Node.js Foundation and the convergence of io.js and Node.js,” said Mikeal Rogers, Community Manager, Node.js Foundation. “We created this conference to help showcase this growth, to accommodate the Node.js community’s many different needs, and to help accelerate adoption as it expands into enterprises.”
 
 Early bird registration ends October 23, 2015. Standard registration closes November 21, 2015, after which the conference price will increase from $425 to $525. Discounted hotel rates are also available until Wednesday, November 11, 2015. To register visit [https://www.regonline.com/Register/Checkin.aspx?EventID=1753707](https://www.regonline.com/Register/Checkin.aspx?EventID=1753707).
 

locale/en/blog/announcements/interactive-2015.md

@@ -9,12 +9,12 @@ layout: blog-post.hbs
 
 Are You Ready for Node.js Interactive?
 
-The Node.js Foundation is pleased to announce [Node.js Interactive](http://interactive.nodejs.org) happening from December 8-9, 2015 in Portland, OR. With node.js growing in all aspects of technology, the gathering will cover everything from streamlining development of fast websites and real-time applications to tips for managing node.js applications, and much more.
+The Node.js Foundation is pleased to announce [Node.js Interactive](http://interactive.nodejs.org) happening from December 8-9, 2015 in Portland, OR. With Node.js growing in all aspects of technology, the gathering will cover everything from streamlining development of fast websites and real-time applications to tips for managing Node.js applications, and much more.
 
-The event will be the first of its kind under the Node.js Foundation led in cooperation with The Linux Foundation. Vendor-neutral by design, it will focus on the continued ideals of open governance collaboration between the now joined node.js and io.js community. The conference welcomes experienced developers as well as those interested in how node.js might be of use to their business with tracks that focus on IoT, front-end and back-end technologies. To curate these tracks and create the best experience for attendees, track chairs include seasoned veterans:
+The event will be the first of its kind under the Node.js Foundation led in cooperation with The Linux Foundation. Vendor-neutral by design, it will focus on the continued ideals of open governance collaboration between the now joined Node.js and io.js community. The conference welcomes experienced developers as well as those interested in how Node.js might be of use to their business with tracks that focus on IoT, front-end and back-end technologies. To curate these tracks and create the best experience for attendees, track chairs include seasoned veterans:
 
 * [Kassandra Perch](https://github.com/nodebotanist) for IoT, a software developer / evangelist / advocate / educator / roboticist living in Austin, TX, who you can follow at: [@nodebotanist](https://twitter.com/nodebotanist).
-* [Jessica Lord](https://github.com/jlord/) for Front-End, a GitHub developer and designer who loves open source, JavaScript & node.js, and stories of Tudor England and is a Portland transplant.
+* [Jessica Lord](https://github.com/jlord/) for Front-End, a GitHub developer and designer who loves open source, JavaScript & Node.js, and stories of Tudor England and is a Portland transplant.
 * [C J Silverio](https://github.com/ceejbot) for Back-End, who is all node, all the time and works as VP of engineering at npm, Inc. in the Bay area.
 
 As the Node.js community continues to grow, the Node.js Foundation believes this event is the perfect place to continue to develop collaboration and better understand what’s next for this extremely popular technology. Interested in joining us? Register [here](http://events.linuxfoundation.org/events/node-interactive/attend/register). Timeline for discount rates are as follows:

locale/en/blog/module/service-logging-in-json-with-bunyan.md

@@ -26,7 +26,7 @@ These are what logs are good for. The current state of logging is barely adequat
 
 Let's log in JSON. Let's format log records with a filter _outside_ the app. Let's put more info in log records by not shoehorning into a printf-message. Debuggability can be improved. Monitoring and analysis can _definitely_ be improved. Let's _not_ write another regex-based parser, and use the time we've saved writing tools to collate logs from multiple nodes and services, to query structured logs (from all services, not just web servers), etc.
 
-At [Joyent](http://joyent.com) we use node.js for running many core services -- loosely coupled through HTTP REST APIs and/or AMQP. In this post I'll draw on experiences from my work on Joyent's [SmartDataCenter product](http://www.joyent.com/products/smartdatacenter/) and observations of [Joyent Cloud](http://www.joyentcloud.com/) operations to suggest some improvements to service logging. I'll show the (open source) **Bunyan logging library and tool** that we're developing to improve the logging toolchain.
+At [Joyent](http://joyent.com) we use Node.js for running many core services -- loosely coupled through HTTP REST APIs and/or AMQP. In this post I'll draw on experiences from my work on Joyent's [SmartDataCenter product](http://www.joyent.com/products/smartdatacenter/) and observations of [Joyent Cloud](http://www.joyentcloud.com/) operations to suggest some improvements to service logging. I'll show the (open source) **Bunyan logging library and tool** that we're developing to improve the logging toolchain.
 
 ## Current State of Log Formatting
 
@@ -69,7 +69,7 @@ Time to burn your log4j Layout classes and move formatting to the tools side. Cr
 
 ## Introducing Bunyan
 
-[Bunyan](https://github.com/trentm/node-bunyan) is **a node.js module for logging in JSON** and **a `bunyan` CLI tool** to view those logs.
+[Bunyan](https://github.com/trentm/node-bunyan) is **a Node.js module for logging in JSON** and **a `bunyan` CLI tool** to view those logs.
 
 Logging with Bunyan basically looks like this:
 
@@ -105,7 +105,7 @@ $ node hi.js | ./node_modules/.bin/bunyan -j    # indented JSON output
 }
 ```
 
-Bunyan is log4j-like: create a Logger with a name, call `log.info(...)`, etc. However it has no intention of reproducing much of the functionality of log4j. IMO, much of that is overkill for the types of services you'll tend to be writing with node.js.
+Bunyan is log4j-like: create a Logger with a name, call `log.info(...)`, etc. However it has no intention of reproducing much of the functionality of log4j. IMO, much of that is overkill for the types of services you'll tend to be writing with Node.js.
 
 ## Longer Bunyan Example
 
@@ -340,7 +340,7 @@ _This_ is logging you can use effectively.
 
 ## Other Tools
 
-Bunyan is just one of many options for logging in node.js-land. Others (that I know of) supporting JSON logging are [winston](https://github.com/flatiron/winston#readme) and [logmagic](https://github.com/pquerna/node-logmagic/). Paul Querna has [an excellent post on using JSON for logging](http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/), which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching.
+Bunyan is just one of many options for logging in Node.js-land. Others (that I know of) supporting JSON logging are [winston](https://github.com/flatiron/winston#readme) and [logmagic](https://github.com/pquerna/node-logmagic/). Paul Querna has [an excellent post on using JSON for logging](http://journal.paul.querna.org/articles/2011/12/26/log-for-machines-in-json/), which shows logmagic usage and also touches on topics like the GELF logging format, log transporting, indexing and searching.
 
 ## Final Thoughts
 
@@ -350,6 +350,6 @@ Separate log files for a single service is an anti-pattern. The typical Apache e
 
 JSON logs bring possibilities. Feeding to tools like Splunk becomes easy. Ad hoc fields allow for a lightly spec'd comm channel from apps to other services: records with a "metric" could feed to [statsd](http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/), records with a "loggly: true" could feed to loggly.com.
 
-Here I've described a very simple example of restify and bunyan usage for node.js-based API services with easy JSON logging. Restify provides a powerful framework for robust API services. Bunyan provides a light API for nice JSON logging and the beginnings of tooling to help consume Bunyan JSON logs.
+Here I've described a very simple example of restify and bunyan usage for Node.js-based API services with easy JSON logging. Restify provides a powerful framework for robust API services. Bunyan provides a light API for nice JSON logging and the beginnings of tooling to help consume Bunyan JSON logs.
 
 **Update (29-Mar-2012):** Fix styles somewhat for RSS readers.

locale/en/blog/uncategorized/ldapjs-a-reprise-of-ldap.md

@@ -82,7 +82,7 @@ For all the good parts of LDAP, those are really damned big failing points, and
 
 Well, in the last year, I went to work for [Joyent](http://www.joyent.com/ "Joyent"), and like everyone else, we have several use problems that are classic directory service problems. If you break down the list I outlined above:
 
-* **Connection-oriented and asynchronous:** Holy smokes batman, [node.js](https://nodejs.org/ "node.js") is a completely kick-ass event-driven asynchronous server platform that manages connections like a boss. Check!
+* **Connection-oriented and asynchronous:** Holy smokes batman, [Node.js](https://nodejs.org/ "Node.js") is a completely kick-ass event-driven asynchronous server platform that manages connections like a boss. Check!
 * **Lots of use cases:** Yeah, we've got some. Man, the [sinatra](http://www.sinatrarb.com/ "sinatra")/[express](http://expressjs.com/ "express") paradigm is so easy to slap over anything. How about we just do that and leave as many use cases open as we can. Check!
 * **Replication is hard. CAP is right:** There are a lot of distributed databases out vying to solve exactly this problem. At Joyent we went with [Riak](http://www.basho.com/ "Riak"). Check!
 * **Don't need all of the protocol:** I'm lazy. Let's just skip the stupid things most people don't need. Check!

locale/en/blog/uncategorized/some-new-node-projects.md

@@ -12,6 +12,6 @@ layout: blog-post.hbs
 
 * Joyent's Mark Cavage released [LDAP.js](http://ldapjs.org/). "_ldapjs is a pure JavaScript, from-scratch framework for implementing [LDAP](http://tools.ietf.org/html/rfc4510) clients and servers in [Node.js](https://nodejs.org/). It is intended for developers used to interacting with HTTP services in node and [express](http://expressjs.com)._
 
-* Microsoft's Tomasz Janczuk released [iisnode](http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html) "_The [iisnode](https://github.com/tjanczuk/iisnode) project provides a native IIS 7.x module that allows hosting of node.js applications in IIS._
+* Microsoft's Tomasz Janczuk released [iisnode](http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html) "_The [iisnode](https://github.com/tjanczuk/iisnode) project provides a native IIS 7.x module that allows hosting of Node.js applications in IIS._
 
   Scott Hanselman posted [a detailed walkthrough](http://www.hanselman.com/blog/InstallingAndRunningNodejsApplicationsWithinIISOnWindowsAreYouMad.aspx) of how to get started with iisnode

locale/en/blog/weekly-updates/weekly-update.2015-02-13.md

@@ -77,21 +77,21 @@ View the [original article](https://medium.com/@mikeal/how-io-js-built-a-146-per
 ## io.js and Node.js
 View the [original article](https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be) on Medium.
 
-* Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the node.js.
+* Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the Node.js.
 
 ### In only a few months io.js...
 
 * Has grown to 23 active core team members
 * Has several working groups
 * Has 29 language localization teams,
-* Has drawn more contributors to the project than we’ve ever had in the history of node.js, and
+* Has drawn more contributors to the project than we’ve ever had in the history of Node.js, and
 * Has been able to release quality software at a good pace with the support of an exceptional community.
 
 > We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.
 
 ### The Future
 
-* Talks with the node.js foundation are ongoing.
+* Talks with the Node.js foundation are ongoing.
 * Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join.
 
   * This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built.

locale/en/blog/weekly-updates/weekly-update.2015-02-27.md

@@ -51,6 +51,6 @@ The build team is in the process of being given access to the Linaro ARMv8 Serve
 
 * **[Wallaby.js](http://wallabyjs.com/)**, a while-you-write testing library for JavaScript, hit version 1.0 and [added support for io.js](http://dm.gl/2015/02/23/wallaby-version-one/)!
 * **[jsdom](https://github.com/tmpvar/jsdom)**, an implementation of the WHATWG DOM and HTML standards, just hit [version 4.0.0](https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400), which added a _requirement_ of io.js.
-* **[give](https://github.com/mmalecki/give)**'s creator [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that newer versions of give support io.js. Give is a git-based node.js/io.js version manager.
-* The **Firebase Realtime Client**, the official web/node.js JavaScript client for Firebase, [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) that they added support for io.js in [version 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client)
+* **[give](https://github.com/mmalecki/give)**'s creator [tweeted](https://twitter.com/maciejmalecki/status/569629100215816192) that newer versions of give support io.js. Give is a git-based Node.js/io.js version manager.
+* The **Firebase Realtime Client**, the official web/Node.js JavaScript client for Firebase, [tweeted](https://twitter.com/FirebaseRelease/status/570000737343647744) that they added support for io.js in [version 2.2.1](https://www.firebase.com/docs/web/changelog.html#section-realtime-client)
 * **Semaphore**, a hosted continuous integrations service, [tweeted](https://twitter.com/semaphoreapp/status/570987355005431809) about added io.js support in their [Platform update on February 24th, 2015](https://semaphoreapp.com/blog/2015/02/17/platform-update-on-february-24th.html?utm_source=twitter&utm_medium=social&utm_content=platform_update_launch&utm_campaign=platformupdate).