Fix more 404 links and a few redirects. (#2604)

Author: XhmikosR

locale/ar/about/working-groups.md

@@ -145,7 +145,8 @@ title:  مجموعات العمل
 * [nodejs-uk - Ukrainian (Українська)](https://github.com/nodejs/nodejs-uk)
 * [nodejs-vi - Vietnamese (Tiếng Việt)](https://github.com/nodejs/nodejs-vi)
 
-### <!--release-->[الإصدارات الطويلة الأمد](https://github.com/nodejs/LTS)
+### <!--release-->[الإصدارات الطويلة الأمد](https://github.com/nodejs/Release)
+
 تقوم هذه المجموعة بإدارة عمليات الأصدار للنسخ الجديدة من Node.js.
 
 تشمل مسؤولياتها:

locale/en/about/working-groups.md

@@ -171,7 +171,8 @@ Each language community maintains its own membership.
 * [nodejs-uk - Ukrainian (Українська)](https://github.com/nodejs/nodejs-uk)
 * [nodejs-vi - Vietnamese (Tiếng Việt)](https://github.com/nodejs/nodejs-vi)
 
-### [Release](https://github.com/nodejs/LTS)
+### [Release](https://github.com/nodejs/Release)
+
 The Release Working Group manages the release process for Node.js.
 
 Responsibilities include:

locale/en/knowledge/advanced/streams/what-are-streams.md

@@ -39,4 +39,4 @@ Run this script with arguments like `node cp.js src.txt dest.txt`. This would me
       console.log("ERROR", err);
     });
 
-This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/how-to-use-stream-pipe) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way.
+This sets up a readable stream from the source file and a writable stream to the destination file. Then whenever the readable stream gets data, it gets written to the writeable stream. Then finally it closes the writable stream when the readable stream is finished. NOTE: it would have been better to use [pipe](/en/knowledge/advanced/streams/how-to-use-stream-pipe/) like `readStream.pipe(writeStream);`, however, to show how streams work, we have done things the long way.

locale/en/knowledge/errors/what-is-the-error-object.md

@@ -39,4 +39,4 @@ If you want to add more information to the Error object, you can always add prop
     error.http_code = 404;
     console.log(error);
 
-For more details how to use the Error object, check out the [article on error conventions](/en/knowledge/errors/what-are-the-error-conventions)
+For more details how to use the Error object, check out the [article on error conventions](/en/knowledge/errors/what-are-the-error-conventions/)

locale/en/knowledge/errors/what-is-try-catch.md

@@ -46,4 +46,4 @@ Note that you can omit the `catch` or `finally` block, but one of them must be p
 
 ## But wait, isn't it Node.js convention to not use try-catch?
 
-In the core node.js libraries, the only place that one really *needs* to use a try-catch is around `JSON.parse()`. All of the other methods use either the standard Error object through the first parameter of the callback or emit an `error` event. Because of this, it is generally considered [standard](/what-are-the-error-conventions) to return errors through the callback rather than to use the `throw` statement.
+In the core node.js libraries, the only place that one really *needs* to use a try-catch is around `JSON.parse()`. All of the other methods use either the standard Error object through the first parameter of the callback or emit an `error` event. Because of this, it is generally considered [standard](/en/knowledge/errors/what-are-the-error-conventions/) to return errors through the callback rather than to use the `throw` statement.

locale/en/knowledge/file-system/how-to-read-files-in-nodejs.md

@@ -50,4 +50,4 @@ This is the output:
       code: 'ENOENT',
       path: '/doesnt/exist' }
 
-This is a basic Node.js [Error object](/what-is-the-error-object) - it can often be useful to log `err.stack` directly, since this contains a stack trace to the location in code at which the Error object was created.
+This is a basic Node.js [Error object](/en/knowledge/errors/what-is-the-error-object/) - it can often be useful to log `err.stack` directly, since this contains a stack trace to the location in code at which the Error object was created.

locale/en/knowledge/file-system/how-to-search-files-and-directories-in-nodejs.md

@@ -7,7 +7,7 @@ difficulty: 1
 layout: knowledge-post.hbs
 ---
 
-Suppose you want to list all the files in the current directory.  One approach is to use the builtin `fs.readdir` [method](/how-do-i-read-files-in-node-js). This will get you an array of all the files and directories on the specified path:
+Suppose you want to list all the files in the current directory.  One approach is to use the builtin `fs.readdir` [method](/en/knowledge/file-system/how-to-read-files-in-nodejs/). This will get you an array of all the files and directories on the specified path:
 
     fs = require('fs');
 

locale/en/knowledge/file-system/how-to-store-local-config-data.md

@@ -8,7 +8,7 @@ difficulty: 1
 layout: knowledge-post.hbs
 ---
 
-Storing your Node.js application's configuration data is quite simple - every object in JavaScript can be easily rendered as [JSON](/what-is-json), which in turn is just string data that can be sent or saved any way you'd like.  The simplest way to do this involves the built-in `JSON.parse()` and `JSON.stringify()` methods.
+Storing your Node.js application's configuration data is quite simple - every object in JavaScript can be easily rendered as [JSON](/en/knowledge/javascript-conventions/what-is-json/), which in turn is just string data that can be sent or saved any way you'd like.  The simplest way to do this involves the built-in `JSON.parse()` and `JSON.stringify()` methods.
 
 Let's take a look at a very simple (and contrived) example.  First, to save some very simple data:
 

locale/en/knowledge/file-system/how-to-use-the-path-module.md

@@ -57,7 +57,7 @@ Lastly, the `path` module provides methods to check whether or not a given path
 
 `existsSync`, on the other hand, checks the given path synchronously, returning the boolean directly.  In Node.js, you will typically want to use the asynchronous functions for most file system I/O - the synchronous versions will block your entire process until they finish.
 
-Blocking isn't always a bad thing.  Checking the existence of a vital configuration file synchronously makes sense, for example - it doesn't matter much if your process is blocking for something it can't run without!  Conversely, though, in a busy HTTP server, any per-request file I/O **MUST** be asynchronous, or else you'll be responding to requests one by one. See the article on [asynchronous operations](/how-to-write-asynchronous-code) for more details.
+Blocking isn't always a bad thing.  Checking the existence of a vital configuration file synchronously makes sense, for example - it doesn't matter much if your process is blocking for something it can't run without!  Conversely, though, in a busy HTTP server, any per-request file I/O **MUST** be asynchronous, or else you'll be responding to requests one by one. See the article on [asynchronous operations](/en/knowledge/getting-started/control-flow/how-to-write-asynchronous-code/) for more details.
 
         > var path = require('path')
         > path.exists('/etc', function(exists){console.log("Does the file exist?", exists)})

locale/en/knowledge/getting-started/control-flow/what-are-callbacks.md

@@ -50,4 +50,4 @@ The typical convention with asynchronous functions (which almost all of your fun
        //This code gets run after the async operation gets run
     });
 
-You will almost always want to follow the [error callback convention](/en/knowledge/errors/what-are-the-error-conventions), since most Node.js users will expect your project to follow them. The general idea is that the callback is the last parameter. The callback gets called after the function is done with all of its operations. Traditionally, the first parameter of the callback is the `error` value. If the function hits an error, then they typically call the callback with the first parameter being an Error object. If it cleanly exits, then they will call the callback with the first parameter being null and the rest being the return value(s).
+You will almost always want to follow the [error callback convention](/en/knowledge/errors/what-are-the-error-conventions/), since most Node.js users will expect your project to follow them. The general idea is that the callback is the last parameter. The callback gets called after the function is done with all of its operations. Traditionally, the first parameter of the callback is the `error` value. If the function hits an error, then they typically call the callback with the first parameter being an Error object. If it cleanly exits, then they will call the callback with the first parameter being null and the rest being the return value(s).