style: remove unnecessary 'just' occurences

Author: honzajavorek

sources/academy/glossary/tools/edit_this_cookie.md

@@ -25,7 +25,7 @@ Clicking this button will remove all cookies associated with the current domain.
 
 ### Reset
 
-Basically just a refresh button.
+A refresh button.
 
 ### Add a new cookie
 

sources/academy/glossary/tools/insomnia.md

@@ -66,4 +66,4 @@ This will bring up the **Manage cookies** window, where all cached cookies can b
 
 ## Postman or Insomnia {#postman-or-insomnia}
 
-The application you choose to use is completely up to your personal preference, and will not affect your development workflow. If viewing timelines of the requests you send is important to you, then you should go with Insomnia; however, if that doesn't matter, just choose the one that has the most intuitive interface for you.
+The application you choose to use is completely up to your personal preference, and will not affect your development workflow. If viewing timelines of the requests you send is important to you, then you should go with Insomnia; however, if that doesn't matter, choose the one that has the most intuitive interface for you.

sources/academy/glossary/tools/postman.md

@@ -43,7 +43,7 @@ In order to use a proxy, the proxy's server and configuration must be provided i
 
 ![Proxy configuration in Postman settings](./images/postman-proxy.png)
 
-After configuring a proxy, the next request sent will attempt to use it. To switch off the proxy, its details don't need to be deleted. The **Add a custom proxy configuration** option in settings just needs to be un-ticked to disable it.
+After configuring a proxy, the next request sent will attempt to use it. To switch off the proxy, its details don't need to be deleted. The **Add a custom proxy configuration** option in settings needs to be un-ticked to disable it.
 
 ## Managing the cookies cache {#managing-cookies}
 

sources/academy/platform/deploying_your_code/docker_file.md

@@ -16,15 +16,15 @@ import TabItem from '@theme/TabItem';
 
 The **Dockerfile** is a file which gives the Apify platform (or Docker, more specifically) instructions on how to create an environment for your code to run in. Every Actor must have a Dockerfile, as Actors run in Docker containers.
 
-> Actors on the platform are always run in Docker containers; however, they can also be run in local Docker containers. This is not common practice though, as it requires more setup and a deeper understanding of Docker. For testing, it's best to just run the Actor on the local OS (this requires you to have the underlying runtime installed, such as Node.js, Python, Rust, GO, etc).
+> Actors on the platform are always run in Docker containers; however, they can also be run in local Docker containers. This is not common practice though, as it requires more setup and a deeper understanding of Docker. For testing, it's best to run the Actor on the local OS (this requires you to have the underlying runtime installed, such as Node.js, Python, Rust, GO, etc).
 
 ## Base images {#base-images}
 
 If your project doesn’t already contain a Dockerfile, don’t worry! Apify offers [many base images](/sdk/js/docs/guides/docker-images) that are optimized for building and running Actors on the platform, which can be found [here](https://hub.docker.com/u/apify). When using a language for which Apify doesn't provide a base image, [Docker Hub](https://hub.docker.com/) provides a ton of free Docker images for most use-cases, upon which you can create your own images.
 
 > Tip: You can see all of Apify's Docker images [on DockerHub](https://hub.docker.com/r/apify/).
 
-At the base level, each Docker image contains a base operating system and usually also a programming language runtime (such as Node.js or Python). You can also find images with preinstalled libraries or just install them yourself during the build step.
+At the base level, each Docker image contains a base operating system and usually also a programming language runtime (such as Node.js or Python). You can also find images with preinstalled libraries or install them yourself during the build step.
 
 Once you find the base image you need, you can add it as the initial `FROM` statement:
 
@@ -111,7 +111,7 @@ CMD python3 main.py
 
 ## Examples {#examples}
 
-The examples we just showed were for Node.js and Python, however, to drive home the fact that Actors can be written in any language, here are some examples of some Dockerfiles for Actors written in different programming languages:
+The examples above show how to deploy Actors written in Node.js or Python, but you can use any language. As an inspiration, here are a few examples for other languages: Go, Rust, Julia.
 
 <Tabs groupId="main">
 <TabItem value="GO Actor Dockerfile" label="GO Actor Dockerfile">

sources/academy/platform/deploying_your_code/index.md

@@ -1,6 +1,6 @@
 ---
 title: Deploying your code
-description: In this course learn how to take an existing project of yours and deploy it to the Apify platform as an Actor in just a few minutes!
+description: In this course learn how to take an existing project of yours and deploy it to the Apify platform as an actor.
 sidebar_position: 9
 category: apify platform
 slug: /deploying-your-code
@@ -11,25 +11,24 @@ import TabItem from '@theme/TabItem';
 
 # Deploying your code to Apify {#deploying}
 
-**In this course learn how to take an existing project of yours and deploy it to the Apify platform as an Actor in just a few minutes!**
+**In this course learn how to take an existing project of yours and deploy it to the Apify platform as an Actor.**
 
 ---
 
 This section will discuss how to use your newfound knowledge of the Apify platform and Actors from the [**Getting started**](../getting_started/index.md) section to deploy your existing project's code to the Apify platform as an Actor.
-
-Because Actors are basically just chunks of code running in Docker containers, you're able to **_Actorify_** just about anything!
+Any program running in a Docker container can become an Apify Actor.
 
 ![The deployment workflow](../../images/deployment-workflow.png)
 
-Actors are language agnostic, which means that the language your project is written in does not affect your ability to actorify it.
+Apify provides detailed guidance on how to deploy Node.js and Python programs as Actors, but apart from that you're not limited in what programming language you choose for your scraper.
 
 ![Supported languages](../../images/supported-languages.jpg)
 
-Though the majority of Actors currently on the platform were written in Node.js, and despite the fact our current preferred languages are JavaScript and Python, there are a few examples of Actors in other languages:
+Here are a few examples of Actors in other languages:
 
-- [Actor written in Rust](https://apify.com/lukaskrivka/rust-actor-example)
-- [GO Actor](https://apify.com/jirimoravcik/go-actor-example)
-- [Actor written with Julia](https://apify.com/jirimoravcik/julia-actor-example)
+- [Rust actor](https://apify.com/lukaskrivka/rust-actor-example)
+- [Go actor](https://apify.com/jirimoravcik/go-actor-example)
+- [Julia actor](https://apify.com/jirimoravcik/julia-actor-example)
 
 ## The "actorification" workflow {#workflow}
 

sources/academy/platform/expert_scraping_with_apify/actors_webhooks.md

@@ -17,7 +17,7 @@ Thus far, you've run Actors on the platform and written an Actor of your own, wh
 
 In this course, we'll be working out of the Amazon scraper project from the **Web scraping for beginners** course. If you haven't already built that project, you can do it in three short lessons [here](../../webscraping/web_scraping_for_beginners/challenge/index.md). We've made a few small modifications to the project with the Apify SDK, but 99% of the code is still the same.
 
-Take another look at the files within your Amazon scraper project. You'll notice that there is a **Dockerfile**. Every single Actor has a Dockerfile (the Actor's **Image**) which tells Docker how to spin up a container on the Apify platform which can successfully run the Actor's code. "Apify Actors" is basically just a serverless platform that runs multiple Docker containers. For a deeper understanding of Actor Dockerfiles, refer to the [Apify Actor Dockerfile docs](/sdk/js/docs/guides/docker-images#example-dockerfile).
+Take another look at the files within your Amazon scraper project. You'll notice that there is a **Dockerfile**. Every single Actor has a Dockerfile (the Actor's **Image**) which tells Docker how to spin up a container on the Apify platform which can successfully run the Actor's code. "Apify Actors" is a serverless platform that runs multiple Docker containers. For a deeper understanding of Actor Dockerfiles, refer to the [Apify Actor Dockerfile docs](/sdk/js/docs/guides/docker-images#example-dockerfile).
 
 ## Webhooks {#webhooks}
 

sources/academy/platform/expert_scraping_with_apify/migrations_maintaining_state.md

@@ -11,7 +11,7 @@ slug: /expert-scraping-with-apify/migrations-maintaining-state
 
 ---
 
-We already know that Actors are basically just Docker containers that can be run on any server. This means that they can be allocated anywhere there is space available, making them very efficient. Unfortunately, there is one big caveat: Actors move - a lot. When an Actor moves, it is called a **migration**.
+We already know that Actors are Docker containers that can be run on any server. This means that they can be allocated anywhere there is space available, making them very efficient. Unfortunately, there is one big caveat: Actors move - a lot. When an Actor moves, it is called a **migration**.
 
 On migration, the process inside of an Actor is completely restarted and everything in its memory is lost, meaning that any values stored within variables or classes are lost.
 

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

@@ -68,7 +68,7 @@ const filtered = items.reduce((acc, curr) => {
 }, {});
 ```
 
-The results should be an array, so finally, we can take the map we just created and push an array of all of its values to the Actor's default dataset:
+The results should be an array, so we can take the map we just created and push an array of its values to the Actor's default dataset:
 
 ```js
 await Actor.pushData(Object.values(filtered));

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

@@ -73,7 +73,7 @@ And that's it! We've successfully configured the session pool to match the task'
 
 ## Limiting proxy location {#limiting-proxy-location}
 
-The final requirement was to only use proxies from the US. Back in our **ProxyConfiguration**, we just need to add the **countryCode** key and set it to **US**:
+The final requirement was to use proxies only from the US. Back in our **ProxyConfiguration**, we need to add the **countryCode** key and set it to **US**:
 
 ```js
 const proxyConfiguration = await Actor.createProxyConfiguration({

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

@@ -88,7 +88,7 @@ const crawler = new CheerioCrawler({
 
 ## Tracking total saved {#tracking-total-saved}
 
-Now, we'll just increment our **totalSaved** count for every offer added to the dataset.
+Now, we'll increment our **totalSaved** count for every offer added to the dataset.
 
 ```js
 router.addHandler(labels.OFFERS, async ({ $, request }) => {