diff --git a/locale/ar/about/index.md b/locale/ar/about/index.md
index 8750858cd0a98..6549cd184c682 100644
--- a/locale/ar/about/index.md
+++ b/locale/ar/about/index.md
@@ -4,7 +4,7 @@ title: عن النود جي اس
trademark: العلامة التجارية
---
-# عن الـ Node.js ®
+# عن الـ Node.js ®
كونه بيئة تشغيل جافاسكريبت غير متزامنة و مدفوعة بالاحداث، فإن Node.js صمم لبناء تطبيقات للشبكات قابلة للتطوير. في المثال الأتي، يمكن التحكم في عدة اتصالات معا في وقت واحد و مع كل اتصال يتم تشغيل دالة مستدعاة، وعندما لن يكون هناك عمل لاتمامه، سيقف النود جي اس عن العمل مؤقتا.
```javascript
diff --git a/locale/ar/about/resources.md b/locale/ar/about/resources.md
index e521097cff298..b15e0c6e2ea7e 100644
--- a/locale/ar/about/resources.md
+++ b/locale/ar/about/resources.md
@@ -7,7 +7,7 @@ title: الشعارات والرسومات
## تحميل الشعار
-للحصول على معلومات حول الاستخدام المسموح به لشعارات وعلامات Node.js® يرجى مراجعة [سياسة العلامات التجارية](/ar/about/trademark/).
+للحصول على معلومات حول الاستخدام المسموح به لشعارات وعلامات Node.js® يرجى مراجعة [سياسة العلامات التجارية](/ar/about/trademark/).
الإرشادات من أجل العرض المرئي لعلامة Node.js موضحة في [القواعد العرض الإرشادية](/static/documents/foundation-visual-guidelines.pdf).
diff --git a/locale/ar/get-involved/node-meetups.md b/locale/ar/get-involved/node-meetups.md
index 2b7df124defac..795e1b6f5f326 100644
--- a/locale/ar/get-involved/node-meetups.md
+++ b/locale/ar/get-involved/node-meetups.md
@@ -16,7 +16,7 @@ layout: contribute.hbs
الصيغة
- [اللقاء](https://www.meetup.com/pdxnode/)
- تردد اللقاء
-- كيف يتم تقديم طلب المحاضرة? <<اذكر هنا>>
+- كيف يتم تقديم طلب المحاضرة? «اذكر هنا»
- إسم المنظم أو المنظمين (إذا اردت الإدلاء به)
- معلومات الإتصال بالمنظمين (إذا اردت الإدلاء به)
diff --git a/locale/ca/about/index.md b/locale/ca/about/index.md
index 5fdf44cc923ec..2447c9577e811 100644
--- a/locale/ca/about/index.md
+++ b/locale/ca/about/index.md
@@ -4,7 +4,7 @@ title: Sobre nosaltres
trademark: Trademark
---
-# Sobre Node.js®
+# Sobre Node.js®
Nascut com a un entorn d'execució de JavaScript orientat a esdeveniments asíncrons, Node.js està
dissenyat per a crear aplicacions en xarxa de manera escalable. En la següent aplicació d'exemple
diff --git a/locale/de/about/index.md b/locale/de/about/index.md
index d1ce4781fb49d..62600c0f05b92 100644
--- a/locale/de/about/index.md
+++ b/locale/de/about/index.md
@@ -4,7 +4,7 @@ title: Über Node.js
trademark: Trademark
---
-# Über Node.js®
+# Über Node.js®
Als asynchrone, Event-basierte Laufzeitumgebung wurde Node speziell für die
Entwicklung von skalierbaren Netzwerkanwendungen entworfen. Im nachfolgenden
diff --git a/locale/en/about/index.md b/locale/en/about/index.md
index 08ea261f02e98..188a160f95cde 100644
--- a/locale/en/about/index.md
+++ b/locale/en/about/index.md
@@ -4,7 +4,7 @@ title: About
trademark: Trademark
---
-# About Node.js®
+# About Node.js®
As an asynchronous event-driven JavaScript runtime, Node.js is designed to build
scalable network applications. In the following "hello world" example, many
diff --git a/locale/en/about/resources.md b/locale/en/about/resources.md
index 7b51438206396..a6c69f87d7949 100644
--- a/locale/en/about/resources.md
+++ b/locale/en/about/resources.md
@@ -7,7 +7,7 @@ title: Logos and Graphics
## Logo Downloads
-Please review the [trademark policy](/en/about/trademark/) for information about permissible use of Node.js® logos and marks.
+Please review the [trademark policy](/en/about/trademark/) for information about permissible use of Node.js® logos and marks.
Guidelines for the visual display of the Node.js mark are described in
the [Visual Guidelines](/static/documents/foundation-visual-guidelines.pdf).
diff --git a/locale/en/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md b/locale/en/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md
index 3ac28a844424e..18a3a46165200 100644
--- a/locale/en/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md
+++ b/locale/en/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17.md
@@ -16,11 +16,11 @@ layout: blog-post.hbs
## Details
-A few weeks ago, Matthew Daley found a security vulnerability in Node's HTTP implementation, and thankfully did the responsible thing and reported it to us via email. He explained it quite well, so I'll quote him here:
+A few weeks ago, Matthew Daley found a security vulnerability in Node's HTTP implementation, and thankfully did the responsible thing and reported it to us via email. He explained it quite well, so I'll quote him here:
-> There is a vulnerability in node's `http_parser` binding which allows information disclosure to a remote attacker:
+> There is a vulnerability in node's `http_parser` binding which allows information disclosure to a remote attacker:
>
-> In node::StringPtr::Update, an attempt is made at an optimization on certain inputs (`node_http_parser.cc`, line 151). The intent is that if the current string pointer plus the current string size is equal to the incoming string pointer, the current string size is just increased to match, as the incoming string lies just beyond the current string pointer. However, the check to see whether or not this can be done is incorrect; "size" is used whereas "size_" should be used. Therefore, an attacker can call Update with a string of certain length and cause the current string to have other data appended to it. In the case of HTTP being parsed out of incoming socket data, this can be incoming data from other sockets.
+> In node::StringPtr::Update, an attempt is made at an optimization on certain inputs (`node_http_parser.cc`, line 151). The intent is that if the current string pointer plus the current string size is equal to the incoming string pointer, the current string size is just increased to match, as the incoming string lies just beyond the current string pointer. However, the check to see whether or not this can be done is incorrect; "size" is used whereas "size_" should be used. Therefore, an attacker can call Update with a string of certain length and cause the current string to have other data appended to it. In the case of HTTP being parsed out of incoming socket data, this can be incoming data from other sockets.
>
> Normally node::StringPtr::Save, which is called after each execution of `http_parser`, would stop this from being exploitable as it converts strings to non-optimizable heap-based strings. However, this is not done to 0-length strings. An attacker can therefore exploit the mistake by making Update set a 0-length string, and then Update past its boundary, so long as it is done in one `http_parser` execution. This can be done with an HTTP header with empty value, followed by a continuation with a value of certain length.
>
@@ -46,6 +46,6 @@ The fix landed on [7b3fb22](https://github.com/joyent/node/commit/7b3fb22) and [
The first releases with the fix are v0.7.8 and 0.6.17. So now is a good time to make a big deal about it.
-If you are using node version 0.6 in production, please upgrade to at least [v0.6.17](http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/), or at least apply the fix in [c9a231d](https://github.com/joyent/node/commit/c9a231d) to your system. (Version 0.6.17 also fixes some other important bugs, and is without doubt the most stable release of Node 0.6 to date, so it's a good idea to upgrade anyway.)
+If you are using node version 0.6 in production, please upgrade to at least [v0.6.17](http://blog.nodejs.org/2012/05/04/version-0-6-17-stable/), or at least apply the fix in [c9a231d](https://github.com/joyent/node/commit/c9a231d) to your system. (Version 0.6.17 also fixes some other important bugs, and is without doubt the most stable release of Node 0.6 to date, so it's a good idea to upgrade anyway.)
-I'm extremely grateful that Matthew took the time to report the problem to us with such an elegant explanation, and in such a way that we had a reasonable amount of time to fix the issue before making it public.
+I'm extremely grateful that Matthew took the time to report the problem to us with such an elegant explanation, and in such a way that we had a reasonable amount of time to fix the issue before making it public.
diff --git a/locale/en/download/releases.md b/locale/en/download/releases.md
index f3ea453d53031..41fe89648e179 100644
--- a/locale/en/download/releases.md
+++ b/locale/en/download/releases.md
@@ -4,7 +4,7 @@ title: Previous Releases
modules: "NODE_MODULE_VERSION
refers to the ABI (application binary interface) version number of Node.js, used to determine which versions of Node.js compiled C++ add-on binaries can be loaded in to without needing to be re-compiled. It used to be stored as hex value in earlier versions, but is now represented as an integer."
---
-### io.js & Node.js
+### io.js & Node.js
Releases 1.x through 3.x were called "io.js" as they were part of the io.js fork. As of Node.js 4.0.0 the former release lines of io.js converged with Node.js 0.12.x into unified Node.js releases.
NODE_MODULE_VERSION
se refiere al número de versión ABI (application binary interface) de Node.js, usado para determinar que versiones de los binarios de los complementos en C++ pueden ser cargados sin necesidad de ser re-compilados. Este solía ser almacenado como un valor hexadecimal en versiones anteriores, pero ahora es representado como un entero."
---
-### io.js & Node.js
+### io.js & Node.js
Las versiones desde la 1.x hasta la 3.x fueron llamadas "io.js" ya que fueron parte del _fork_ io.js . Desde Node.js 4.0.0 las líneas de versiones de io.js convergieron con las de Node.js 0.12.x en una unificación de versiones de Node.js.