Apply suggestions from code review

Co-authored-by: František Nesveda <[email protected]>

Author: TC-MO

sources/platform/actors/development/builds_and_runs/builds.md

@@ -11,11 +11,11 @@ slug: /actors/development/builds-and-runs/builds
 
 ## Understand Actor builds
 
-Before an Actor can be run, it needs to be built. The build process creates a snapshot of a specific version of the Actor's settings, including its [source code](../actor_definition/source_code.md) and [environment variables](../programming_interface/environment_variables.md). This snapshot is then used to create Docker image that containing everything the Actor needs for its run, such as NPM packages, web browsers, etc.
+Before an Actor can be run, it needs to be built. The build process creates a snapshot of a specific version of the Actor's settings, including its [source code](../actor_definition/source_code.md) and [environment variables](../programming_interface/environment_variables.md). This snapshot is then used to create a Docker image containing everything the Actor needs for its run, such as NPM packages, web browsers, etc.
 
 ### Build numbers
 
-Each build is assigned a unique build number if the format _MAJOR\.MINOR\.BUILD_ (e.g. _1\.2\.345_):
+Each build is assigned a unique build number in the format _MAJOR\.MINOR\.BUILD_ (e.g. _1\.2\.345_):
 
 - _MAJOR\.MINOR_ corresponds to the Actor version number
 - _BUILD_ is an automatically incremented number starting at **1**.
@@ -24,14 +24,14 @@ Each build is assigned a unique build number if the format _MAJOR\.MINOR\.BUILD_
 
 By default, builds have the following resource allocations:
 
-- Timeout of _1800_ seconds
+- Timeout: _1800_ seconds
 - Memory: `4096 MB`
 
-Check out [Resource limits](../../running/index.md) section for more details.
+Check out the [Resource limits](../../running/index.md) section for more details.
 
 ## Versioning
 
-To support active development, Actors can have multiple versions versions of source code and associated settings, such as the base image and environment. Each version is denoted by a version number of the form _MAJOR.MINOR_; following [Semantic Versioning](https://semver.org/) principles.
+To support active development, Actors can have multiple versions of source code and associated settings, such as the base image and environment. Each version is denoted by a version number of the form _MAJOR.MINOR_, following [Semantic Versioning](https://semver.org/) principles.
 
 For example, an Actor might have:
 
@@ -41,7 +41,7 @@ For example, an Actor might have:
 
 ## Tags
 
-Tags simplify the process of specifying which build to use when running an Actor Instead of using a version number, you can use a tag such as _latest_ or _beta_. Tags are unique, meaning only one build can be associated with a specific tag.
+Tags simplify the process of specifying which build to use when running an Actor. Instead of using a version number, you can use a tag such as _latest_ or _beta_. Tags are unique, meaning only one build can be associated with a specific tag.
 
 To set a tag for builds of a specific Actor version:
 
@@ -52,7 +52,7 @@ By default, the builds are set to the _latest_ tag.
 
 ## Cache
 
-To speed up builds triggered via API, you can use the `useCache=1` parameter. This instructs the build process to use cached Docker images and layers instead of pulling the latest copies and building each layer from scratch.
+To speed up builds triggered via API, you can use the `useCache=1` parameter. This instructs the build process to use cached Docker images and layers instead of pulling the latest copies and building each layer from scratch. Note that the cached images and layers might not always be available on the server building the image, the `useCache` parameter only functions on a best-effort basis.
 
 :::note Clean builds