style: don't use 'simply', let the reader decide what is simple

Author: honzajavorek

sources/academy/glossary/concepts/http_headers.md

@@ -23,7 +23,7 @@ For some websites, you won't need to worry about modifying headers at all, as th
 
 Some websites will require certain default browser headers to work properly, such as **User-Agent** (though, this header is becoming more obsolete, as there are more sophisticated ways to detect and block a suspicious user).
 
-Another example of such a "default" header is **Referer**. Some e-commerce websites might share the same platform, and data is loaded through XMLHttpRequests to that platform, which simply would not know which data to return without knowing which exact website is requesting it.
+Another example of such a "default" header is **Referer**. Some e-commerce websites might share the same platform, and data is loaded through XMLHttpRequests to that platform, which would not know which data to return without knowing which exact website is requesting it.
 
 ## Custom headers required {#needs-custom-headers}
 
@@ -44,7 +44,7 @@ You could use Chrome DevTools to inspect request headers, and [Insomnia](../tool
 HTTP/1.1 and HTTP/2 headers have several differences. Here are the three key differences that you should be aware of:
 
 1. HTTP/2 headers do not include status messages. They only contain status codes.
-2. Certain headers are no longer used in HTTP/2 (such as **Connection** along with a few others related to it like **Keep-Alive**). In HTTP/2, connection-specific headers are prohibited. While some browsers will simply ignore them, Safari and other Webkit-based browsers will outright reject any response that contains them. Easy to do by accident, and a big problem.
+2. Certain headers are no longer used in HTTP/2 (such as **Connection** along with a few others related to it like **Keep-Alive**). In HTTP/2, connection-specific headers are prohibited. While some browsers will ignore them, Safari and other Webkit-based browsers will outright reject any response that contains them. Easy to do by accident, and a big problem.
 3. While HTTP/1.1 headers are case-insensitive and could be sent by the browsers with capitalized letters (e.g. **Accept-Encoding**, **Cache-Control**, **User-Agent**), HTTP/2 headers must be lower-cased (e.g. **accept-encoding**, **cache-control**, **user-agent**).
 
 > To learn more about the difference between HTTP/1.1 and HTTP/2 headers, check out [this](https://httptoolkit.tech/blog/translating-http-2-into-http-1/) article

sources/academy/glossary/tools/edit_this_cookie.md

@@ -21,7 +21,7 @@ At the top of the popup, there is a row of buttons. From left to right, here is
 
 ### Delete all cookies
 
-Clicking this button will simply remove all cookies associated with the current domain. For example, if you're logged into your Apify account and delete all the cookies, the website will ask you to log in again.
+Clicking this button will remove all cookies associated with the current domain. For example, if you're logged into your Apify account and delete all the cookies, the website will ask you to log in again.
 
 ### Reset
 

sources/academy/platform/deploying_your_code/input_schema.md

@@ -28,7 +28,7 @@ In the root of our project, we'll create a file named **INPUT_SCHEMA.json** and
 }
 ```
 
-The **title** and **description** simply describe what the input schema is for, and a bit about what the Actor itself does.
+The **title** and **description** describe what the input schema is for, and a bit about what the Actor itself does.
 
 ## Properties {#properties}
 

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

@@ -106,7 +106,7 @@ const proxyConfiguration = await Actor.createProxyConfiguration({
 
 **Q: What do you need to do to rotate a proxy (one proxy usually has one IP)? How does this differ for CheerioCrawler and PuppeteerCrawler?**
 
-**A:** Simply making a new request with the proxy endpoint above will automatically rotate it. Sessions can also be used to automatically do this. While proxy rotation is fairly straightforward for Cheerio, it's more complex in Puppeteer, as you have to retire the browser each time a new proxy is rotated in. The SessionPool will automatically retire a browser when a session is retired. Sessions can be manually retired with `session.retire()`.
+**A:** Making a new request with the proxy endpoint above will automatically rotate it. Sessions can also be used to automatically do this. While proxy rotation is fairly straightforward for Cheerio, it's more complex in Puppeteer, as you have to retire the browser each time a new proxy is rotated in. The SessionPool will automatically retire a browser when a session is retired. Sessions can be manually retired with `session.retire()`.
 
 **Q: Name a few different ways how a website can prevent you from scraping it.**
 

sources/academy/platform/get_most_of_actors/actor_readme.md

@@ -57,7 +57,7 @@ Aim for sections 1–6 below and try to include at least 300 words. You can move
 
     - Add a video tutorial or GIF from an ideal Actor run.
 
-    > Tip: For better user experience, Apify Console automatically renders every YouTube URL as an embedded video player. Simply add a separate line with the URL of your YouTube video.
+    > Tip: For better user experience, Apify Console automatically renders every YouTube URL as an embedded video player. Add a separate line with the URL of your YouTube video.
 
     - Consider adding a short numbered tutorial as Google will sometimes pick these up as rich snippets. Remember that this might be in search results, so you can repeat the name of the Actor and give a link, e.g.
 

sources/academy/platform/getting_started/actors.md

@@ -15,7 +15,7 @@ After you've followed the **Getting started** lesson, you're almost ready to sta
 
 ## What's an Actor? {#what-is-an-actor}
 
-When you deploy your script to the Apify platform, it is then called an **Actor**, which is simply a [serverless microservice](https://www.datadoghq.com/knowledge-center/serverless-architecture/serverless-microservices/#:~:text=Serverless%20microservices%20are%20cloud-based,suited%20for%20microservice-based%20architectures.) that accepts an input and produces an output. Actors can run for a few seconds, hours or even infinitely. An Actor can perform anything from a simple action such as filling out a web form or sending an email, to complex operations such as crawling an entire website and removing duplicates from a large dataset.
+When you deploy your script to the Apify platform, it is then called an **Actor**, which is a [serverless microservice](https://www.datadoghq.com/knowledge-center/serverless-architecture/serverless-microservices/#:~:text=Serverless%20microservices%20are%20cloud-based,suited%20for%20microservice-based%20architectures.) that accepts an input and produces an output. Actors can run for a few seconds, hours or even infinitely. An Actor can perform anything from a simple action such as filling out a web form or sending an email, to complex operations such as crawling an entire website and removing duplicates from a large dataset.
 
 Once an Actor has been pushed to the Apify platform, they can be shared to the world through the [Apify Store](https://apify.com/store), and even monetized after going public.
 

sources/academy/platform/getting_started/apify_api.md

@@ -39,7 +39,7 @@ Our **adding-actor** takes in two input values (`num1` and `num2`). When using t
 
 ## Parameters {#parameters}
 
-Let's say we want to run our **adding-actor** via API and view its results in CSV format at the end. We'll achieve this by simply passing the **format** parameter with a value of **csv** to change the output format:
+Let's say we want to run our **adding-actor** via API and view its results in CSV format at the end. We'll achieve this by passing the **format** parameter with a value of **csv** to change the output format:
 
 ```text
 https://api.apify.com/v2/acts/YOUR_USERNAME~adding-actor/run-sync-get-dataset-items?token=YOUR_TOKEN_HERE&format=csv

sources/academy/platform/getting_started/creating_actors.md

@@ -68,7 +68,7 @@ If you want to use the template locally, you can again use our [Apify CLI](/cli)
 
 When you click on the **Use locally** button, you'll be presented with instructions on how to create an Actor from this template in your local environment.
 
-With the Apify CLI installed, you can simply run the following commands in your terminal:
+With the Apify CLI installed, you can run the following commands in your terminal:
 
 ```shell
 apify create my-actor -t getting_started_node
@@ -153,7 +153,7 @@ And now we are ready to run the Actor. But before we do that, let's give the Act
 
 The input tab is where you can provide the Actor with some meaningful input. In this case, we'll be providing the Actor with a URL to scrape. For now, we'll use the prefilled value of [Apify website](https://apify.com/) (`https://apify.com/`).
 
-You can change the website you want to extract the data from by simply changing the URL in the input field.
+You can change the website you want to extract the data from by changing the URL in the input field.
 
 ![Input tab](./images/actor-input-tab.png)
 
@@ -163,7 +163,7 @@ Once you have provided the Actor with some URL you want to extract the data from
 
 ![Actor run logs](./images/actor-run.png)
 
-After the Actor finishes, you can preview or download the extracted data simply by clicking on the **Export X results** button.
+After the Actor finishes, you can preview or download the extracted data by clicking on the **Export X results** button.
 
 ![Export results](./images/actor-run-dataset.png)
 

sources/academy/platform/running_a_web_server.md

@@ -61,7 +61,7 @@ Now we need to read the following environment variables:
 
 - **APIFY_CONTAINER_PORT** contains a port number where we must start the server.
 - **APIFY_CONTAINER_URL** contains a URL under which we can access the container.
-- **APIFY_DEFAULT_KEY_VALUE_STORE_ID** is simply the ID of the default key-value store of this Actor where we can store screenshots.
+- **APIFY_DEFAULT_KEY_VALUE_STORE_ID** is the ID of the default key-value store of this Actor where we can store screenshots.
 
 ```js
 const {

sources/academy/tutorials/api/run_actor_and_retrieve_data_via_api.md

@@ -56,7 +56,7 @@ If we send a correct POST request to one of these endpoints, the actor/actor-tas
 
 ### Additional settings {#additional-settings}
 
-We can also add settings for the Actor (which will override the default settings) as additional query parameters. For example, if we wanted to change how much memory the Actor's run should be allocated and which build to run, we could simply add the `memory` and `build` parameters separated by `&`.
+We can also add settings for the Actor (which will override the default settings) as additional query parameters. For example, if we wanted to change how much memory the Actor's run should be allocated and which build to run, we could add the `memory` and `build` parameters separated by `&`.
 
 ```cURL
 https://api.apify.com/v2/acts/ACTOR_NAME_OR_ID/runs?token=YOUR_TOKEN&memory=8192&build=beta
@@ -201,7 +201,7 @@ For runs longer than 5 minutes, the process consists of three steps:
 
 ### Wait for the run to finish {#wait-for-the-run-to-finish}
 
-There may be cases where we need to simply run the Actor and go away. But in any kind of integration, we are usually interested in its output. We have three basic options for how to wait for the actor/task to finish.
+There may be cases where we need to run the Actor and go away. But in any kind of integration, we are usually interested in its output. We have three basic options for how to wait for the actor/task to finish.
 
 - [`waitForFinish` parameter](#waitforfinish-parameter)
 - [Webhooks](#webhooks)
@@ -221,7 +221,7 @@ Once again, the final response will be the **run info object**; however, now its
 
 #### Webhooks {#webhooks}
 
-If you have a server, [webhooks](/platform/integrations/webhooks) are the most elegant and flexible solution for integrations with Apify. You can simply set up a webhook for any Actor or task, and that webhook will send a POST request to your server after an [event](/platform/integrations/webhooks/events) has occurred.
+If you have a server, [webhooks](/platform/integrations/webhooks) are the most elegant and flexible solution for integrations with Apify. You can set up a webhook for any Actor or task, and that webhook will send a POST request to your server after an [event](/platform/integrations/webhooks/events) has occurred.
 
 Usually, this event is a successfully finished run, but you can also set a different webhook for failed runs, etc.
 
@@ -239,7 +239,7 @@ What if you don't have a server, and the run you'd like to do is much too long t
 
 When we run the Actor with the [usual API call](#run-an-actor-or-task) shown above, we will back a response with the **run info** object. From this JSON object, we can then extract the ID of the Actor run that we just started from the `id` field. Then, we can set an interval that will poll the Apify API (let's say every 5 seconds) by calling the [**Get run**](https://apify.com/docs/api/v2#/reference/actors/run-object/get-run) endpoint to retrieve the run's status.
 
-Simply replace the `RUN_ID` in the following URL with the ID you extracted earlier:
+Replace the `RUN_ID` in the following URL with the ID you extracted earlier:
 
 ```cURL
 https://api.apify.com/v2/acts/ACTOR_NAME_OR_ID/runs/RUN_ID