style: don't tell the reader something is 'easy'

Author: honzajavorek

sources/academy/platform/deploying_your_code/deploying.md

@@ -21,12 +21,10 @@ Before we deploy our project onto the Apify platform, let's ensure that we've pu
 
 ### Creating the Actor
 
-Before anything can be integrated, we've gotta create a new Actor. Luckily, this is super easy to do. Let's head over to our [Apify Console](https://console.apify.com?asrc=developers_portal) and click on the **New** button, then select the **Empty** template.
+Before anything can be integrated, we've gotta create a new Actor. Let's head over to our [Apify Console](https://console.apify.com?asrc=developers_portal) and click on the **New** button, then select the **Empty** template.
 
 ![Create new button](../getting_started/images/create-new-actor.png)
 
-Easy peasy!
-
 ### Changing source code location {#change-source-code}
 
 In the **Source** tab on the new Actor's page, we'll click the dropdown menu under **Source code** and select **Git repository**. By default, this is set to **Web IDE**.

sources/academy/platform/deploying_your_code/inputs_outputs.md

@@ -11,7 +11,7 @@ slug: /deploying-your-code/inputs-outputs
 
 ---
 
-Most of the time when you're creating a project, you are expecting some sort of input from which your software will run off. Oftentimes as well, you want to provide some sort of output once your software has completed running. With Apify, it is extremely easy to take in inputs and deliver outputs.
+Most of the time when you're creating a project, you are expecting some sort of input from which your software will run off. Oftentimes as well, you want to provide some sort of output once your software has completed running. Apify provides a convenient way to handle inputs and deliver outputs.
 
 An important thing to understand regarding inputs and outputs is that they are read/written differently depending on where the Actor is running:
 

sources/academy/platform/expert_scraping_with_apify/managing_source_code.md

@@ -31,8 +31,6 @@ Also, try to explore the **Multifile editor** in one of the Actors you developed
 
 ## Our task {#our-task}
 
-> This lesson's task is so quick and easy, we won't even be splitting this topic into two parts like the previous two topics!
-
 First, we must initialize a GitHub repository (you can use Gitlab if you like, but this lesson's examples will be using GitHub). Then, after pushing our main Amazon Actor's code to the repo, we must switch its source code to use the content of the GitHub repository instead.
 
 ## Integrating GitHub source code {#integrating-github}

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

@@ -232,7 +232,7 @@ router.addHandler(labels.OFFERS, async ({ $, request }) => {
 
 Don't forget to push your changes to GitHub using `git push origin MAIN_BRANCH_NAME` to see them on the Apify platform!
 
-## Creating a task (It's easy!) {#creating-task}
+## Creating a task {#creating-task}
 
 Back on the platform, on your Actor's page, you can see a button in the top right hand corner that says **Create new task**:
 

sources/academy/platform/get_most_of_actors/seo_and_promotion.md

@@ -23,7 +23,7 @@ On the other hand, if you precisely address a niche segment of users who will be
 
 ## Keywords
 
-Several freemium tools exist that make it easy to identify the right phrases and keywords:
+Several freemium tools exist that help with identifying the right phrases and keywords:
 
 - [wordstream.com/keywords](https://www.wordstream.com/keywords)
 - [neilpatel.com/ubersuggest](https://neilpatel.com/ubersuggest/)

sources/academy/platform/getting_started/apify_api.md

@@ -47,7 +47,7 @@ https://api.apify.com/v2/acts/YOUR_USERNAME~adding-actor/run-sync-get-dataset-it
 
 Additional parameters can be passed to this endpoint. You can learn about them [here](/api/v2#/reference/actors/run-actor-synchronously-and-get-dataset-items/run-actor-synchronously-with-input-and-get-dataset-items)
 
-> Note: It is safer to put your API token in the **Authorization** header like so: `Authorization: Bearer YOUR_TOKEN`. This is very easy to configure in popular HTTP clients, such as [Postman](../../glossary/tools/postman.md), [Insomnia](../../glossary/tools/insomnia.md).
+> Network components can record visited URLs, so it's more secure to send the token as a HTTP header, not as a parameter. The header should look like `Authorization: Bearer YOUR_TOKEN`. Popular HTTP clients, such as [Postman](../../glossary/tools/postman.md) or [Insomnia](../../glossary/tools/insomnia.md), provide a convenient way to configure the Authorization header for all your API requests.
 
 ## Sending the request {#sending-the-request}
 

sources/academy/platform/getting_started/inputs_outputs.md

@@ -11,7 +11,7 @@ slug: /getting-started/inputs-outputs
 
 ---
 
-Most of the time, when you are writing any sort of software, it will generally expect some sort of input and generate some sort of output. It is the same exact story when it comes to Actors, which is why we at Apify have made it so easy to accept input into an Actor and store its results somewhere.
+Actors, as any other programs, take inputs and generate outputs. The Apify platform has a way how to specify what inputs the Actor expects, and a way to temporarily or permanently store its results.
 
 In this lesson, we'll be demonstrating inputs and outputs by building an Actor which takes two numbers as input, adds them up, and then outputs the result.
 

sources/academy/tutorials/api/run_actor_and_retrieve_data_via_api.md

@@ -9,9 +9,9 @@ slug: /api/run-actor-and-retrieve-data-via-api
 
 ---
 
-The most popular way of [integrating](https://help.apify.com/en/collections/1669769-integrations) the Apify platform with an external project/application is by programmatically running an [Actor](/platform/actors) or [task](/platform/actors/running/tasks), waiting for it to complete its run, then collecting its data and using it within the project. Though this process sounds somewhat complicated, it's actually quite easy to do; however, due to the plethora of features offered on the Apify platform, new users may not be sure how exactly to implement this type of integration. Let's dive in and see how you can do it.
+The most popular way of [integrating](https://help.apify.com/en/collections/1669769-integrations) the Apify platform with an external project/application is by programmatically running an [Actor](/platform/actors) or [task](/platform/actors/running/tasks), waiting for it to complete its run, then collecting its data and using it within the project. Follow this tutorial to have an idea on how to approach this, it isn't as complicated as it sounds!
 
-> Remember to check out our [API documentation](/api/v2) with examples in different languages and a live API console. We also recommend testing the API with a nice desktop client like [Postman](https://www.getpostman.com/) or [Insomnia](https://insomnia.rest).
+> Remember to check out our [API documentation](/api/v2) with examples in different languages and a live API console. We also recommend testing the API with a desktop client like [Postman](https://www.getpostman.com/) or [Insomnia](https://insomnia.rest).
 
 
 Apify API offers two ways of interacting with it:

sources/academy/tutorials/apify_scrapers/puppeteer_scraper.md

@@ -374,7 +374,6 @@ JavaScript had the time to run.
 At first, you may think that the scraper is broken, but it just cannot wait for all the JavaScript in the page
 to finish executing. For a lot of pages, there's always some JavaScript executing or some network requests being made.
 It would never stop waiting. It is therefore up to you, the programmer, to wait for the elements you need.
-Fortunately, we have an easy solution.
 
 #### The `context.page.waitFor()` function
 
@@ -409,13 +408,13 @@ With those tools, you should be able to handle any dynamic content the website t
 
 ### [](#how-to-paginate)  How to paginate
 
-With the theory out of the way, this should be pretty easy. The algorithm is a loop:
+After going through the theory, let's design the algorithm:
 
-   1. Wait for the **Show more** button.
-   2. Click it.
-   3. Is there another **Show more** button?
-      - Yes? Repeat the above. (loop)
-      - No? We're done. We have all the Actors.
+1. Wait for the **Show more** button.
+2. Click it.
+3. Is there another **Show more** button?
+    - Yes? Repeat from 1. (loop)
+    - No? We're done. We have all the Actors.
 
 #### Waiting for the button
 

sources/academy/tutorials/apify_scrapers/web_scraper.md

@@ -272,7 +272,6 @@ JavaScript had the time to run.
 At first, you may think that the scraper is broken, but it just cannot wait for all the JavaScript in the page
 to finish executing. For a lot of pages, there's always some JavaScript executing or some network requests being made.
 It would never stop waiting. It is therefore up to you, the programmer, to wait for the elements you need.
-Fortunately, we have an easy solution.
 
 #### The `context.waitFor()` function
 
@@ -304,12 +303,12 @@ With those tools, you should be able to handle any dynamic content the website t
 
 ### [](#how-to-paginate) How to paginate
 
-With the theory out of the way, this should be pretty easy. The algorithm is a loop:
+After going through the theory, let's design the algorithm:
 
 1. Wait for the **Show more** button.
 2. Click it.
 3. Is there another **Show more** button?
-    - Yes? Repeat the above. (loop)
+    - Yes? Repeat from 1. (loop)
     - No? We're done. We have all the Actors.
 
 #### Waiting for the button