fix: solve all outstanding Vale errors

Author: honzajavorek

sources/academy/glossary/concepts/index.md

@@ -12,8 +12,8 @@ slug: /concepts
 
 ---
 
-There are some terms and concepts you'll see frequently repeated throughout various courses in the academy. Many of these concepts are common, and even fundamental in the scraping world, which makes it necessary to explain them to our course-takers; however it would be inconvenient for our readers to explain these terms each time they appear in a lesson.
+You'll see some terms and concepts frequently repeated throughout various courses in the academy. Many of these concepts are common, and even fundamental in the scraping world, which makes it necessary to explain them to our course-takers; however it would be inconvenient for our readers to explain these terms each time they appear in a lesson.
 
-Because of this slight dilemma, and because there are no outside resources which compile all of these concepts into an educational and digestible form, we've decided to do just that. So, welcome to the **Concepts** section of the Apify Academy's **Glossary**!
+Because of this slight dilemma, and because there are no outside resources which compile all of these concepts into an educational and digestible form, we've decided to do just that. Welcome to the **Concepts** section of the Apify Academy's **Glossary**!
 
 > It's important to note that there is no specific order to these concepts. All of them range in their relevance and importance to your every day scraping endeavors.

sources/academy/platform/expert_scraping_with_apify/index.md

@@ -26,7 +26,7 @@ Before developing a pro-level Apify scraper, there are some important things you
 
 ### Crawlee, Apify SDK, and the Apify CLI {#crawlee-apify-sdk-and-cli}
 
-If you're feeling ambitious, you don't need to have any prior experience with Crawlee to get started with this course; however, at least 5-10 minutes of exposure is recommended. If you haven't yet tried out Crawlee, you can refer to [this lesson](../../webscraping/scraping_basics_javascript/crawling/pro_scraping.md) in the **Web scraping for beginners** course (and ideally follow along). To familiarize yourself with the Apify SDK, you can refer to the [Apify Platform](../apify_platform.md) category.
+If you're feeling ambitious, you don't need to have any prior experience with Crawlee to get started with this course; however, at least 5–10 minutes of exposure is recommended. If you haven't yet tried out Crawlee, you can refer to [this lesson](../../webscraping/web_scraping_for_beginners/crawling/pro_scraping.md) in the **Web scraping for beginners** course (and ideally follow along). To familiarize yourself with the Apify SDK, you can refer to the [Apify Platform](../apify_platform.md) category.
 
 The Apify CLI will play a core role in the running and testing of the Actor you will build, so if you haven't gotten it installed already, please refer to [this short lesson](../../glossary/tools/apify_cli.md).
 

sources/academy/platform/expert_scraping_with_apify/solutions/saving_stats.md

@@ -160,7 +160,7 @@ router.addHandler(labels.OFFERS, async ({ $, request }) => {
 
 **Q: Is storing these types of values necessary for every single Actor?**
 
-**A:** For small Actors, it might be a waste of time to do this. For large-scale Actors, it can be extremely helpful when debugging and most definitely worth the extra 10-20 minutes of development time. Usually though, the default statistics from the Crawlee and the SDK might be enough for simple run stats.
+**A:** For small Actors, it might be a waste of time to do this. For large-scale Actors, it can be extremely helpful when debugging and most definitely worth the extra 10–20 minutes of development time. Usually though, the default statistics from the Crawlee and the SDK might be enough for simple run stats.
 
 **Q: What is the difference between the `failedRequestHandler` and `errorHandler`?**
 

sources/academy/platform/get_most_of_actors/index.md

@@ -22,4 +22,4 @@ In this section, we will go over some of the practical steps you can take to ens
 
 ## Next up {#next}
 
-So, without further ado, let's jump [right into the next lesson](./naming_your_actor.md)!
+Without further ado, let's jump [right into the next lesson](./naming_your_actor.md)!

sources/academy/platform/get_most_of_actors/naming_your_actor.md

@@ -13,7 +13,7 @@ slug: /get-most-of-actors/naming-your-actor
 
 Naming your Actor can be tricky. Especially when you've spent a long time coding and are excited to show your brand-new creation to the world. To help users find your Actor, we've introduced naming standards. These standards improve your Actor's [search engine optimization (SEO)](https://en.wikipedia.org/wiki/Search_engine_optimization) and maintain consistency in the [Apify Store](https://apify.com/store).
 
-> Your Actor's name should be 3-63 characters long.
+> Your Actor's name should be 3–63 characters long.
 
 ## Scrapers {#scrapers}
 

sources/academy/tutorials/api/retry_failed_requests.md

@@ -9,9 +9,9 @@ slug: /api/retry-failed-requests
 
 ---
 
-There are many reasons why requests for a scraper could fail. The most common causes are different page layouts or proxy blocking issues ([check here on how to effectively analyze errors](https://docs.apify.com/academy/node-js/analyzing-pages-and-fixing-errors)). Both [Apify](https://apify.com) and [Crawlee](https://crawlee.dev/) allow you to restart your scraper run from the point where it ended, but there is no native functionality to re-scrape only failed requests. Usually, you also want to first analyze the problem, update the code, and build it before trying again.
+Requests of a scraper can fail for many reasons. The most common causes are different page layouts or proxy blocking issues ([check here on how to effectively analyze errors](https://docs.apify.com/academy/node-js/analyzing-pages-and-fixing-errors)). Both [Apify](https://apify.com) and [Crawlee](https://crawlee.dev/) allow you to restart your scraper run from the point where it ended, but there is no native functionality to re-scrape only failed requests. Usually, you also want to first analyze the problem, update the code, and build it before trying again.
 
-If you attempt to restart an already finished run, it will likely immediately finish because all the requests in the [request queue](https://crawlee.dev/docs/guides/request-storage) are marked as handled. So you need to update the failed requests in the queue to be marked as pending again.
+If you attempt to restart an already finished run, it will likely immediately finish because all the requests in the [request queue](https://crawlee.dev/docs/guides/request-storage) are marked as handled. You need to update the failed requests in the queue to be marked as pending again.
 
 The additional complication is that the [Request](https://crawlee.dev/api/core/class/Request) object doesn't have anything like the `isFailed` property. We have to approximate it using other fields. Fortunately, we can use the `errorMessages` and `retryCount` properties to identify failed requests. Unless the user explicitly has overridden these properties, we can identify failed requests with a larger amount of `errorMessages` than `retryCount`. That happens because the last error that doesn't cause a retry anymore is added to `errorMessages`.
 

sources/academy/tutorials/node_js/analyzing_pages_and_fixing_errors.md

@@ -77,14 +77,14 @@ Read more information about logging and error handling in our developer [best pr
 
 By snapshots, we mean **screenshots** if you use a [browser with Puppeteer/Playwright](../../webscraping/puppeteer_playwright/index.md) and HTML saved into a [key-value store](https://crawlee.dev/api/core/class/KeyValueStore) that you can easily display in your own browser. Snapshots are useful throughout your code but especially important in error handling.
 
-Note that an error can happen only in a few pages out of a thousand and look completely random. There is not much you can do other than save and analyze a snapshot.
+Note that an error can happen only in a few pages out of a thousand and look completely random. You cannot do much else than to save and analyze a snapshot.
 
 Snapshots can tell you if:
 
 - A website has changed its layout. This can also mean A/B testing or different content for different locations.
-- You have been blocked – you open a [CAPTCHA](https://en.wikipedia.org/wiki/CAPTCHA) or an **Access Denied** page.
-- Data load later dynamically – the page is empty.
-- The page was redirected – the content is different.
+- You have been blocked—you open a [CAPTCHA](https://en.wikipedia.org/wiki/CAPTCHA) or an **Access Denied** page.
+- Data load later dynamically—the page is empty.
+- The page was redirected—the content is different.
 
 You can learn how to take snapshots in Puppeteer or Playwright in [this short lesson](../../webscraping/puppeteer_playwright/page/page_methods.md)
 

sources/academy/tutorials/node_js/dealing_with_dynamic_pages.md

@@ -93,7 +93,7 @@ https://demo-webstore.apify.org/_next/image?url=https%3A%2F%2Fm.media-amazon.com
 
 The reason this is happening is because CheerioCrawler makes static HTTP requests, so it only manages to capture the content from the `DOMContentLoaded` event. Any elements or attributes generated dynamically thereafter using JavaScript (and usually XHR/Fetch requests) are not part of the downloaded HTML, and therefore are not accessible through the `$` object.
 
-So, what's the solution? We need to use something that is able to allow the page to follow through with the entire load process - a headless browser.
+What's the solution? We need to use something that is able to allow the page to follow through with the entire load process - a headless browser.
 
 ## Scraping dynamic content {#scraping-dynamic-content}
 
@@ -142,7 +142,7 @@ After running this one, we can see that our results look different from before.
 
 Well... Not quite. It seems that the only images which we got the full links to were the ones that were being displayed within the view of the browser. This means that the images are lazy-loaded. **Lazy-loading** is a common technique used across the web to improve performance. Lazy-loaded items allow the user to load content incrementally, as they perform some action. In most cases, including our current one, this action is scrolling.
 
-So, we've gotta scroll down the page to load these images. Luckily, because we're using Crawlee, we don't have to write the logic that will achieve that, because a utility function specifically for Puppeteer called [`infiniteScroll`](https://crawlee.dev/api/puppeteer-crawler/namespace/puppeteerUtils#infiniteScroll) already exists right in the library, and can be accessed through `utils.puppeteer`. Let's add it to our code now:
+We've gotta scroll down the page to load these images. Luckily, because we're using Crawlee, we don't have to write the logic that will achieve that, because a utility function specifically for Puppeteer called [`infiniteScroll`](https://crawlee.dev/api/puppeteer-crawler/namespace/puppeteerUtils#infiniteScroll) already exists right in the library, and can be accessed through `utils.puppeteer`. Let's add it to our code now:
 
 <RunnableCodeBlock className="language-js" type="puppeteer">
     {Example}

sources/academy/tutorials/node_js/js_in_html.md

@@ -29,7 +29,7 @@ These data objects will usually be attached to the window object (often prefixed
 
 ## Parsing {#parsing-objects}
 
-There are two ways to go about obtaining these objects to be used and manipulated in JavaScript code:
+You can obtain these objects to be used and manipulated in JavaScript in two ways:
 
 ### 1. Parsing them directly from the HTML
 

sources/academy/tutorials/node_js/processing_multiple_pages_web_scraper.md

@@ -5,7 +5,7 @@ sidebar_position: 15.6
 slug: /node-js/processing-multiple-pages-web-scraper
 ---
 
-There is a certain scraping scenario in which you need to process the same URL many times, but each time with a different setup (e.g. filling in a form with different data each time). This is easy to do with Apify, but how to go about it may not be obvious at first glance.
+Sometimes when scraping, you need to process the same URL many times, but each time with a different setup (e.g. filling in a form with different data each time). This is easy to do with Apify, but how to go about it may not be obvious at first glance.
 
 We'll show you how to do this with a simple example: starting a scraper with an array of keywords, inputting each of the keywords separately into Google, and retrieving the results on the last page. The tutorial will be split into these three main parts.