Update index.mdx

Author: jancurn

sources/platform/actors/index.mdx

@@ -33,19 +33,47 @@ import CardGrid from "@site/src/components/CardGrid";
 
 ## What is an Actor?
 
-Actors are serverless programs running in the cloud. They can perform anything from simple actions (such as filling out a web form or sending an email) to complex operations (such as crawling an entire website or removing duplicates from a large dataset). Actor runs can be as short or as long as necessary. They could last seconds, hours, or even infinitely.
-[Read whitepaper](https://whitepaper.actor/)
+> [Read Actor whitepaper](https://whitepaper.actor/)
 
-> **To get better idea of what Apify Actors are, visit [Apify Store](https://apify.com/store), and try out some of them!**
-> ![Apify Store](./running/images/store-google-maps-scraper.png)
+Actors are serverless programs that run in the cloud.
+They can perform anything from simple actions such as
+filling out a web form or sending an email,
+to complex operations such as crawling an entire website,
+or removing duplicates from a large dataset.
+Actors can persist their state and be restarted, and thus they can
+run as short or as long as necessary, from seconds to hours, even infinitely.
+
+Basically, Actors are programs packaged as Docker images,
+which accept a well-defined JSON input, perform
+an action, and optionally produce a well-defined JSON output.
+
+## What is an Actor made of?
+
+Actors have the following elements:
 
-You can use Actors [manually in Apify Console](https://console.apify.com/actors), by using the [API](/api/v2) or [scheduler](../schedules.md). You can easily [integrate them with other apps](../integrations/index.mdx) and share your Actors with other Apify users via [Apify Store](https://apify.com/store) or [access rights](./collaboration/access-rights) system.
+- **Dockerfile** which specifies where the Actor's source code is,
+  how to build it, and run it.
+- **Documentation** in a form of a README.md file.
+- **Input and output schemas** that describe what input the Actor requires,
+  and what results it produces.
+- Access to an out-of-the-box **storage system** for Actor data, results, and files.
+- **Metadata** such as the Actor name, description, author, and version.
 
-## Actors are containers
+The documentation and the input/output schemas make it possible for people to easily understand what the Actor does,
+enter the required inputs both in user interface or API,
+and integrate the results of the Actor into their other workflows.
+Actors can easily call and interact with each other, enabling the building of more complex
+systems on top of simple ones.
 
-A single isolated Actor consists of source code and various settings. You can think of an Actor as a cloud app or service that runs on the Apify platform. The run of an Actor is not limited to the lifetime of a single HTTP transaction. It can run for as long as necessary, even forever.
+![Apify Actor diagram](./images/apify-actor-drawing.png)
+
+## Running Actors
+
+You can run Actors manually in [Apify Console](https://console.apify.com/actors), using the [API](/api), [CLI](/cli), or [scheduler](../schedules). You can easily [integrate Actors](../integrations/index.mdx) with other apps, [share](./collaboration/access-rights) them with other people, [publish](./publishing) them in [Apify Store](https://apify.com/store), and even [monetize](./publishing/monetize).
+
+> **To get better idea of what Apify Actors are, visit [Apify Store](https://apify.com/store), and try out some of them!**
+> ![Apify Store](./running/images/store-google-maps-scraper.png)
 
-Basically, Actors are programs packaged as [Docker images](https://hub.docker.com/), which accept a well-defined JSON input, perform an action, and optionally produce an output.
 
 ## Public and private Actors