Removes redundant spaces (part 1)

files/en-us/games/techniques/tilemaps/square_tilemaps_implementation_colon__scrolling_maps/index.md

@@ -46,7 +46,7 @@ To handle these issues, we need to slightly modify the rendering algorithm. Let'
     var endRow = startRow + (this.camera.height / map.tsize);
 ```
 
-Once we have the first tile, we need to calculate how much its rendering (and therefore the rendering of the other tiles) is offset by. Since the camera  is pointing at `(5, 10)`, we know that the first tile should be shifted by `(-5,-10)` pixels. In our demo the shifting amount is stored in the `offsetX` and `offsetY` variables.
+Once we have the first tile, we need to calculate how much its rendering (and therefore the rendering of the other tiles) is offset by. Since the camera is pointing at `(5, 10)`, we know that the first tile should be shifted by `(-5,-10)` pixels. In our demo the shifting amount is stored in the `offsetX` and `offsetY` variables.
 
 ```js
     var offsetX = -this.camera.x + startCol * map.tsize;

files/en-us/games/tutorials/2d_breakout_game_pure_javascript/build_the_brick_field/index.md

@@ -19,7 +19,7 @@ After modifying the gameplay mechanics, we are now able to lose — this is grea
 
 ## Setting up the brick variables
 
-The overall aim of this lesson is to render a few lines of code for the  bricks, using a nested loop that works through a two-dimensional array. First however we need to set up some variables to define information about the bricks such as their width and height, rows and columns, etc. Add the following lines to your code below the variables which you have previously declared in your program.
+The overall aim of this lesson is to render a few lines of code for the bricks, using a nested loop that works through a two-dimensional array. First however we need to set up some variables to define information about the bricks such as their width and height, rows and columns, etc. Add the following lines to your code below the variables which you have previously declared in your program.
 
 ```js
 var brickRowCount = 3;

files/en-us/games/tutorials/2d_breakout_game_pure_javascript/game_over/index.md

@@ -89,6 +89,6 @@ Here's the working code for you to compare yours against:
 
 ## Next steps
 
-We're doing quite well so far and our game is starting to feel a lot more worth playing now that you can lose! But it is still missing something. Let's move on  to the sixth chapter — [Build the brick field](/en-US/docs/Games/Tutorials/2D_Breakout_game_pure_JavaScript/Build_the_brick_field) — and create some bricks for the ball to destroy.
+We're doing quite well so far and our game is starting to feel a lot more worth playing now that you can lose! But it is still missing something. Let's move on to the sixth chapter — [Build the brick field](/en-US/docs/Games/Tutorials/2D_Breakout_game_pure_JavaScript/Build_the_brick_field) — and create some bricks for the ball to destroy.
 
 {{PreviousNext("Games/Workflows/2D_Breakout_game_pure_JavaScript/Paddle_and_keyboard_controls", "Games/Workflows/2D_Breakout_game_pure_JavaScript/Build_the_brick_field")}}

files/en-us/games/tutorials/2d_breakout_game_pure_javascript/paddle_and_keyboard_controls/index.md

@@ -47,7 +47,7 @@ We can draw the paddle wherever we want, but it should respond to the user's act
 
 - Two variables for storing information on whether the left or right control button is pressed.
 - Two event listeners for `keydown` and `keyup` events. We want to run some code to handle the paddle movement when the buttons are pressed.
-- Two functions handling the `keydown` and `keyup` events  the code that will be run when the buttons are pressed.
+- Two functions handling the `keydown` and `keyup` events the code that will be run when the buttons are pressed.
 - The ability to move the paddle left and right
 
 Pressed buttons can be defined and initialized with boolean variables like in the example. Add these lines somewhere near the rest of your variables:

files/en-us/glossary/certificate_authority/index.md

@@ -12,7 +12,7 @@ For a website digital certificate, this information minimally includes the name
 
 Certificate authorities are the part of the Internet [public key infrastructure](https://en.wikipedia.org/wiki/Public_key_infrastructure) that allows browsers to verify website identity and securely connect over SSL (and HTTPS).
 
-> **Note:** Web browsers come preloaded with a list of "root certificates". The browser can use these to reliably check that the website certificate was signed by a certificate authority  that "chains back" to the root certificate (i.e. was trusted by the owner of the root certificate or an intermediate CA). Ultimately this process relies on every CA performing adequate identity checks before signing a certificate!
+> **Note:** Web browsers come preloaded with a list of "root certificates". The browser can use these to reliably check that the website certificate was signed by a certificate authority that "chains back" to the root certificate (i.e. was trusted by the owner of the root certificate or an intermediate CA). Ultimately this process relies on every CA performing adequate identity checks before signing a certificate!
 
 ## See also
 

files/en-us/glossary/loop/index.md

@@ -60,7 +60,7 @@ while(i < 5){
     console.log(i)
     i++
 }
-//This loop  will print number 0-4, will stop when condition becomes false (i >=5)
+//This loop will print number 0-4, will stop when condition becomes false (i >=5)
 ```
 
 For the above example, the syntax is as follows:

files/en-us/glossary/transferable_objects/index.md

@@ -61,7 +61,7 @@ original[0] = 1;
 console.log(clone[0]);  // 0
 
 // Transferring the Uint8Array would throw an exception as it is not a transferrable object
-// const transferred = structuredClone(original, {transfer: [original]}); 
+// const transferred = structuredClone(original, {transfer: [original]});
 
 // We can transfer Uint8Array.buffer.
 const transferred = structuredClone(original, {transfer: [original.buffer]});

files/en-us/learn/css/building_blocks/selectors/combinators/index.md

@@ -97,7 +97,7 @@ In the example below we are selecting all `<p>` elements that come after the `<h
 You can combine any of the selectors that we discovered in previous lessons with combinators in order to pick out part of your document. For example, if we want to select list items with a class of "a", which are direct children of a `<ul>`, I could use the following.
 
 ```css
-ul > li[class="a"]  {  }
+ul > li[class="a"] {  }
 ```
 
 Take care, however, when creating big lists of selectors that select very specific parts of your document. It will be hard to reuse the CSS rules since you have made the selector very specific to the location of that element in the markup.

files/en-us/learn/css/css_layout/legacy_layout_methods/index.md

@@ -119,7 +119,7 @@ You'll notice here that we are using percentages for all the widths — this is
 
 The majority of legacy frameworks use the behavior of the {{cssxref("float")}} property to float one column up next to another in order to create something that looks like a grid. Working through the process of creating a grid with floats shows you how this works and also introduces some more advanced concepts to build on the things you learned in the lesson on [floats and clearing](/en-US/docs/Learn/CSS/CSS_layout/Floats).
 
-The easiest type of grid framework to create is a fixed width one — we just need to work out how much total width we want our design to be, how many columns we want, and how wide the gutters and columns should be. If we instead decided to lay out our design on a grid with columns that grow and shrink according to browser width, we would need to calculate percentage widths for the columns and  gutters between them.
+The easiest type of grid framework to create is a fixed width one — we just need to work out how much total width we want our design to be, how many columns we want, and how wide the gutters and columns should be. If we instead decided to lay out our design on a grid with columns that grow and shrink according to browser width, we would need to calculate percentage widths for the columns and gutters between them.
 
 In the next sections we will look at how to create both. We will create a 12 column grid — a very common choice that is seen to be very adaptable to different situations given that 12 is nicely divisible by 6, 4, 3, and 2.
 
@@ -370,7 +370,7 @@ These are not the only approach. You could instead decide on your grid and then
 
 ### Enabling offset containers in our grid
 
-The grid we have created works well as long as we want to start all of the containers flush with the left-hand side of the grid. If we wanted to leave an empty column space  before the first container — or between containers — we would need to create an offset class to add a left margin to our site to push it across the grid visually. More math!
+The grid we have created works well as long as we want to start all of the containers flush with the left-hand side of the grid. If we wanted to leave an empty column space before the first container — or between containers — we would need to create an offset class to add a left margin to our site to push it across the grid visually. More math!
 
 Let's try this out.
 

files/en-us/learn/css/howto/create_fancy_boxes/index.md

@@ -180,7 +180,7 @@ Let's have an example by turning our box into a cloud:
 }
 
 .fancy::before {
-  /* This is the  size of the clouds left ear */
+  /* This is the size of the clouds left ear */
   width  : 125px;
   height : 125px;
 

files/en-us/learn/forms/advanced_form_styling/index.md

@@ -257,7 +257,7 @@ If you view these checkboxes in a browser that doesn't support {{cssxref("appear
 
 ## What can be done about the "ugly" elements?
 
-Now let's turn our attention to the "ugly" controls — the ones that are really hard to thoroughly  style. In short, these are drop-down boxes, complex control types like [`color`](/en-US/docs/Web/HTML/Element/input/color) and [`datetime-local`](/en-US/docs/Web/HTML/Element/input/datetime-local), and feedback—oriented controls like {{HTMLElement("progress")}} and {{HTMLElement("meter")}}.
+Now let's turn our attention to the "ugly" controls — the ones that are really hard to thoroughly style. In short, these are drop-down boxes, complex control types like [`color`](/en-US/docs/Web/HTML/Element/input/color) and [`datetime-local`](/en-US/docs/Web/HTML/Element/input/datetime-local), and feedback—oriented controls like {{HTMLElement("progress")}} and {{HTMLElement("meter")}}.
 
 The problem is that these elements have very different default looks across browsers, and while you can style them in some ways, some parts of their internals are literally impossible to style.
 

files/en-us/learn/forms/basic_native_form_controls/index.md

@@ -62,7 +62,7 @@ All basic text controls share some common behaviors:
 
 ### Single line text fields
 
-A single line text field is created using an {{HTMLElement("input")}} element whose {{htmlattrxref("type","input")}} attribute value is set to `text`, or by omitting the  {{htmlattrxref("type","input")}} attribute altogether (`text` is the default value). The value `text` for this attribute is also the fallback value if the value you specify for the {{htmlattrxref("type","input")}} attribute is unknown by the browser (for example if you specify `type="color"` and the browser doesn't support native color pickers).
+A single line text field is created using an {{HTMLElement("input")}} element whose {{htmlattrxref("type","input")}} attribute value is set to `text`, or by omitting the {{htmlattrxref("type","input")}} attribute altogether (`text` is the default value). The value `text` for this attribute is also the fallback value if the value you specify for the {{htmlattrxref("type","input")}} attribute is unknown by the browser (for example if you specify `type="color"` and the browser doesn't support native color pickers).
 
 > **Note:** You can find examples of all the single line text field types on GitHub at [single-line-text-fields.html](https://github.com/mdn/learning-area/blob/main/html/forms/native-form-widgets/single-line-text-fields.html) ([see it live also](https://mdn.github.io/learning-area/html/forms/native-form-widgets/single-line-text-fields.html)).
 

files/en-us/learn/javascript/asynchronous/implementing_a_promise-based_api/index.md

@@ -201,7 +201,7 @@ button.addEventListener('click', async () => {
     output.textContent = message;
   }
   catch (error) {
-    output.textContent = `Couldn't set alarm: ${error}`;  
+    output.textContent = `Couldn't set alarm: ${error}`;
   }
 });
 ```

files/en-us/learn/javascript/first_steps/arrays/index.md

@@ -183,7 +183,7 @@ if (index !== -1) {
 console.log(cities);     // [ "Manchester", "Edinburgh", "Carlisle" ]
 ```
 
-In this call to `splice()`, the first argument says where to start removing items, and the second argument says  how many items should be removed. So you can remove more than one item:
+In this call to `splice()`, the first argument says where to start removing items, and the second argument says how many items should be removed. So you can remove more than one item:
 
 ```js
 const cities = ['Manchester', 'Liverpool', 'Edinburgh', 'Carlisle'];

files/en-us/learn/javascript/objects/json/index.md

@@ -221,7 +221,7 @@ In our function, the first four lines use the Fetch API to fetch the JSON from t
 - we make the network request using the {{domxref("fetch", "fetch()")}} function, and this returns a {{domxref("Response")}} object
 - we retrieve the response as JSON using the {{domxref("Response/json", "json()")}} function of the `Response` object.
 
-> **Note:** The `fetch()` API is **asynchronous**. We'll learn a lot about asynchronous functions in [the next module](/en-US/docs/Learn/JavaScript/Asynchronous), but for now we'll just say that we need to add the keyword {{jsxref("Statements/async_function", "async")}} before the name of the function that uses the fetch API, and  add the keyword {{jsxref("Operators/await", "await")}} before the calls to any asynchronous functions.
+> **Note:** The `fetch()` API is **asynchronous**. We'll learn a lot about asynchronous functions in [the next module](/en-US/docs/Learn/JavaScript/Asynchronous), but for now we'll just say that we need to add the keyword {{jsxref("Statements/async_function", "async")}} before the name of the function that uses the fetch API, and add the keyword {{jsxref("Operators/await", "await")}} before the calls to any asynchronous functions.
 
 After all that, the `superHeroes` variable will contain the JavaScript object based on the JSON. We are then passing that object to two function calls — the first one fills the `<header>` with the correct data, while the second one creates an information card for each hero on the team, and inserts it into the `<section>`.
 

files/en-us/learn/javascript/objects/object_prototypes/index.md

@@ -216,7 +216,7 @@ The objects we create using the `Person` constructor above have two properties:
 
 It's common to see this pattern, in which methods are defined on the prototype, but data properties are defined in the constructor. That's because methods are usually the same for every object we create, while we often want each object to have its own value for its data properties (just as here where every person has a different name).
 
-Properties that are defined directly in the object, like `name` here, are called **own properties**, and you can check whether a property is an own property using the static  {{jsxref("Object/hasOwn", "Object.hasOwn()")}} method:
+Properties that are defined directly in the object, like `name` here, are called **own properties**, and you can check whether a property is an own property using the static {{jsxref("Object/hasOwn", "Object.hasOwn()")}} method:
 
 ```js
 const irma = new Person('Irma');

files/en-us/learn/performance/measuring_performance/index.md

@@ -58,7 +58,7 @@ The [PerformanceEntry](/en-US/docs/Web/API/PerformanceEntry) object is part of t
 
 The [PerformanceObserver API](/en-US/docs/Web/API/PerformanceObserver) can be used to observe performance measurement events and it can notify you of new [performance entries](/en-US/docs/Web/API/PerformanceEntry) as they are recorded in the browser's performance timeline.
 
-While this article does not dive into using these APIs, it is useful to know they exist. You can also refer to  the [Navigation and timings](/en-US/docs/Web/Performance/Navigation_and_resource_timings)  article for further examples on using performance Web APIs.
+While this article does not dive into using these APIs, it is useful to know they exist. You can also refer to the [Navigation and timings](/en-US/docs/Web/Performance/Navigation_and_resource_timings) article for further examples on using performance Web APIs.
 
 ## Tools and metrics
 

files/en-us/learn/server-side/django/home_page/index.md

@@ -102,7 +102,7 @@ The `path()` function defines the following:
 - A URL pattern, which is an empty string: `''`. We'll discuss URL patterns in detail when working on the other views.
 - A view function that will be called if the URL pattern is detected: `views.index`, which is the function named `index()` in the **views.py** file.
 
-The `path()` function also specifies a `name` parameter, which is a unique identifier for *this* particular URL mapping. You can use the name to "reverse" the mapper, i.e. to dynamically create a URL that  points to the resource that the mapper is designed to handle.
+The `path()` function also specifies a `name` parameter, which is a unique identifier for *this* particular URL mapping. You can use the name to "reverse" the mapper, i.e. to dynamically create a URL that points to the resource that the mapper is designed to handle.
 For example, we can use the name parameter to link to our home page from any other page by adding the following link in a template:
 
 ```html

files/en-us/learn/server-side/express_nodejs/introduction/index.md

@@ -447,7 +447,7 @@ $ npm install mongodb
 The database itself can be installed locally or on a cloud server. In your Express code you require the driver, connect to the database, and then perform create, read, update, and delete (CRUD) operations. The example below (from the Express documentation) shows how you can find "mammal" records using MongoDB.
 
 ```js
-//this works with older versions of  mongodb version ~ 2.2.33
+//this works with older versions of mongodb version ~ 2.2.33
 const MongoClient = require('mongodb').MongoClient;
 
 MongoClient.connect('mongodb://localhost:27017/animals', function(err, db) {

files/en-us/learn/server-side/express_nodejs/routes/index.md

@@ -118,7 +118,7 @@ The callback takes three arguments (usually named as shown: `req`, `res`, `next`
 
 > **Note:** Router functions are [Express middleware](/en-US/docs/Learn/Server-side/Express_Nodejs/Introduction#using_middleware), which means that they must either complete (respond to) the request or call the `next` function in the chain. In the case above we complete the request using `send()`, so the `next` argument is not used (and we choose not to specify it).
 >
-> The  router function above takes a single callback, but you can specify as many callback arguments as you want, or an array of callback functions. Each function is part of the middleware chain, and will be called in the order it is added to the chain (unless a preceding function completes the request).
+> The router function above takes a single callback, but you can specify as many callback arguments as you want, or an array of callback functions. Each function is part of the middleware chain, and will be called in the order it is added to the chain (unless a preceding function completes the request).
 
 The callback function here calls [`send()`](https://expressjs.com/en/4x/api.html#res.send) on the response to return the string "About this wiki" when we receive a GET request with the path ('`/about'`). There are a [number of other response methods](https://expressjs.com/en/guide/routing.html#response-methods) for ending the request/response cycle. For example, you could call [`res.json()`](https://expressjs.com/en/4x/api.html#res.json) to send a JSON response or [`res.sendFile()`](https://expressjs.com/en/4x/api.html#res.sendFile) to send a file. The response method that we'll be using most often as we build up the library is [render()](https://expressjs.com/en/4x/api.html#res.render), which creates and returns HTML files using templates and data—we'll talk a lot more about that in a later article!
 

files/en-us/learn/tools_and_testing/client-side_javascript_frameworks/ember_resources/index.md

@@ -85,7 +85,7 @@ Not at all. While `ember-data` solves _the most common problems_ that any app de
 data will run in to, it is possible to roll your own front-end data client. A common
 alternative is to any fully-featured front-end data client is [The Fetch API](/en-US/docs/Web/API/Fetch_API/Using_Fetch).
 
-Using the design patterns provided by the framework, a `Route` using `fetch()` would look something  like this:
+Using the design patterns provided by the framework, a `Route` using `fetch()` would look something like this:
 
 ```js
 import Route from '@ember/routing/route';