Add notes about remote files and adaptive scaling.

Author: tobiasraabe

docs/source/coiled.md

@@ -66,6 +66,14 @@ configure the hardware and software environment.
 ```{literalinclude} ../../docs_src/coiled/coiled_functions_task.py
 ```
 
+By default, {func}`@coiled.function <coiled.function>`
+[scales adaptively](https://docs.coiled.io/user_guide/usage/functions/index.html#adaptive-scaling)
+to the workload. It means that coiled infers from the number of submitted tasks and
+previous runtimes, how many additional remote workers it should deploy to handle the
+workload. It provides a convenient mechanism to scale without intervention. Also,
+workers launched by {func}`@coiled.function <coiled.function>` will shutdown quicker
+than a cluster.
+
 ```{seealso}
 Serverless functions are more thoroughly explained in
 [coiled's guide](https://docs.coiled.io/user_guide/usage/functions/index.html).

docs/source/remote_backends.md

@@ -3,7 +3,7 @@
 There are a couple of things you need to know when using backends that launch workers
 remotely, meaning not on your machine.
 
-## Cross-Platform
+## Cross-platform support
 
 Issue: {issue}`102`.
 
@@ -19,7 +19,13 @@ Windows users on the other hand should use the
 [WSL (Windows Subsystem for Linux)](https://learn.microsoft.com/en-us/windows/wsl/about)
 to run their projects.
 
-## Local Paths
+## Local files
+
+Avoid using local files with remote backends and use storages like S3 for dependencies
+and products. The reason is that every local file needs to be send to the remote workers
+and when your internet connection is slow you will face a hefty penalty on runtime.
+
+## Local paths
 
 In most projects you are using local paths to refer to dependencies and products of your
 tasks. This becomes an interesting problem with remote workers since your local files