<center>![](https://cdn.steemitimages.com/DQmQPWKpofUTSNs5ZZCw7m6etqsLShgShoNAJ6peVvxhgTy/node.png)</center>

<center>[Source](https://en.wikipedia.org/wiki/File:Node.js_logo.svg)</center>

#### Repository

https://github.com/nodejs/i18n

#### Project Details

> Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code outside of a browser... Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of "modules" that handle various core functionality... Node.js represents a "JavaScript everywhere" paradigm, unifying web application development around a single programming language, rather than different languages for server side and client side scripts. | [Source](https://en.wikipedia.org/wiki/Node.js)

In simple words, this project brings value to the open source community because it facilitates the creation of all sort of applications using JavaScript, and provides a lot of help and versatility to developers, so much so that well-known companies like Netflix, Paypal, and Uber (among many others) use Node for their online services.

Since Node.js is very easy to learn and it provides a lot of benefits for developers, there is a huge community of people involved with it, which is one of the reasons why this project is available to be translated into several languages (in crowdin, one of the best translation platforms in the web, this project is available to be translated into 33 different languages, Spanish is the one corresponding to this contribution), the ultimate goal of translating Node.js is to make it easier for developers from any country to start learning about this project in their own native language. 

 If you want to know more about Node.js feel free to visit its [website.](https://nodejs.org/en/)

#### Contribution Specifications

- Translation Overview

This is my 57# contribution to Node.js. As of this moment, this project is 59% translated for the Spanish language and the team is advancing nicely towards the completion of this project. 

The translation for this contribution consisted mainly in brief instructions regarding changes that were applied to Node.js in the past, sometimes these changes are extremely simply such as fixing a typo in a document, and other times there can be more complex instructions such as fixing some technical issues or bugs. 

The content in most of the translated strings always follow the same structure, which is explained below:

* The first thing we encounter in the commits is a link to the original commit in Github. This is where the developer informs the community about a particular issue, and propose a solution to said issue.
* Then we will see an individual word indicating the area related to this particular instruction. Some common areas are “doc”, “tools”, “test”.
* After that, we will see the most important part of the string, the instructions. These are always written in short forms, using imperative verbs and giving clear cut indications.
* The next piece of information we will see is the name of the person who proposed this change. This is a way or recognizing this person for his work done.
* Finally, we will see another link to Github, this time it will take us to the merged pull request.

Some examples of the instructions I translated can be seen below:

English

> update writable.write return value

Spanish

> actualizar valor de devolución de writable.write

There was a little misunderstanding regarding an explanation. The problem was that the document indicated write() would return false  when highWatermark was exceeded, but that was a wrong indication. The correct information was that it would return false once said highWatermark was reached, not exceeded. In short words, the return value used in the documentation was incorrect. We can find the discussion on Github [here](https://github.com/nodejs/node/issues/9247 ) and the commit here.](https://github.com/nodejs/node/commit/6d726c07aa )

The reaction of the developer responsible for that mistake must have been something like this:

<center><i><a href="https://giphy.com/gifs/uTCIuoDirt7PismsHv "><sup>         Fuente</sup></a></i></center>

<center>![crap.gif](https://cdn.steemitimages.com/DQmdUb4c5ZSGuy7m27qZyhoAzgGe4RProeoBTnXdjzn2QpW/crap.gif)</center>

***

English 

> fix broken internal link in process.md

Spanish

> reparar enlace interno roto en process.md

When redacting documentation or guidelines, especially if it is with a lot of technical information, it is very likely to make mistakes from time to time. Usually, these mistakes are simple types that anyone can easily notice so it doesn’t really affect the reader, but other times, it can be more serious mistakes.

In this case, there was a broken link in process.md which could disturb the experience of any developer using that file. Luckily this mistake was reported through Github and eventually it was fixed.

***

English

> remove Chris Dickinson from active releasers

Spanish

> remover a Chris Dickinson de actualizadores activos

A software with such an active development like Node.js, will always have an updated list of every developer that contributes to the project. On this occassion, there was a developer that stopped being active and it was decided that he should be removed from the group of active releasers.

In the previous contributions, I included the definition of these terms: deprecation, I/O - input/output, callback, asynchrony, POSIX, parsing, path, wildcard, wrapper function, stack trace, floating point value, error-first callbacks, transpilation tool, root certificate, little-endian,  DNS rebinding,  same-origin-policy, keep-alive behavior, stringification, arrow function, salt (cryptography), semver, lint, fixtures modules, newline, backporting, shell command, ES6 Classes , code refactoring, tarball, benchmark, type-check, deflate, char, aix, spawn, rehash, noop, rebasing, continuous integration, linkify, segfaults, IPC, libuv, toolchain, punycode, symlink, base64, interprocess communication (IPC), application binary interface (ABI), read–Eval–Print Loop (REPL), advanced Interactive eXecutive (AIX), GYP, Opaque binary blob (obb), symbolic link, destructuring, dotfiles, transport layer security (tls), realpath function, watchdog, continuous integration, smoke test, hotfix, data execution prevention,  (DEP), try/catch blocks, off-by-one error, carriage return, ESLint, hard code, hook, Resource Acquisition Is Initialization or RAII, Coverity, nit, backtick, hashes, big endian, nop, redux, shorthand, TPR records, rest parameters, javaScript Object Notation (JSON), N-API, primitives, and CVE.

***

- Languages

Source language: English

Translated language: Spanish

I have made several contributions in the past, and I published a series of articles in both languages. I am also part of the Utopian + DaVinci Spanish team.

- Word Count

The word count of this contribution is the number of words translated after subtracting words that aren’t changed, such as names, links, functions.

Part 56: 1211 words

The total numbers of words include every word in the final translated strings, including those that aren’t actually translated, such as names, links, functions.

Total: 71012 words

<center>![](https://cdn.steemitimages.com/DQmdnZhGp9EjdnnC62hZ4N4jJjWjt91eE1qsB8yfh8HKKCU/image.png)</center>

### Proof of Authorship

[My activity on Crowdin](https://crowdin.com/profile/dedicatedguy/activity)