Merge branch 'main' into fix-404-on-docs

checkly · Nov 23, 2023 · fbfbd0c · fbfbd0c
2 parents 3fb65e5 + db7a0b0
commit fbfbd0c
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 3 deletions.
diff --git a/site/content/docs/browser-checks/file-system.md b/site/content/docs/browser-checks/file-system.md
@@ -16,7 +16,7 @@ app.
 ## Testing uploads with the browser's File API
 
 To test any upload features with Playwright's `.setInputFiles()` method, you need to provide a file object. Currently,
-Checkly does have a dedicated storage layer where you could upload that file, so you need to host it yourself at a (publicly)
+Checkly does not have a dedicated storage layer where you could upload that file, so you need to host it yourself at a (publicly)
 accessible location like an AWS S3 bucket, Dropbox or any other file hosting service.
 
 In the example below, we do not need to interact with the file system. We can just:

diff --git a/site/content/docs/cli/using-environment-variables.md b/site/content/docs/cli/using-environment-variables.md
@@ -11,6 +11,10 @@ There are two types of environment variables (env vars) in the Checkly CLI conte
 - Local environment variables.
 - Remote environment variables.
 
+To get a quick overview of when to use which, checkout this video 👇
+
+{{< youtube nEIOBRSbjAk >}}
+
 ## Local Environment Variables
 
 Local environment variables exist on your local machine, your CI environment, or anywhere you run the Checkly CLI. They

diff --git a/site/content/docs/multistep-checks/upload-downloads-filesystem.md b/site/content/docs/multistep-checks/upload-downloads-filesystem.md
@@ -14,7 +14,7 @@ app.
 
 ## Testing uploads using HTTP POST requests
 
-To test any binary uploads, you need to provide a file object. Currently, Checkly does have a dedicated storage layer 
+To test any binary uploads, you need to provide a file object. Currently, Checkly does not have a dedicated storage layer 
 where you could upload that file, so you need to host it yourself at a (publicly) accessible location like an AWS S3 bucket, 
 Dropbox or any other file hosting service.
 

diff --git a/site/content/docs/private-locations/scaling-and-redundancy.md b/site/content/docs/private-locations/scaling-and-redundancy.md
@@ -10,7 +10,7 @@ cli: true
 At least two running Checkly Agents per Private Location are recommended for redundancy. Agents are stateless and can be scaled horizontally as needed. You can add additional agents to a location at any time and remove them
 as necessary.
 
-If one Checkly Agent fails, the other agents in the same Private Location will continue to run the checks assigned to that location. Even checks that are currently in progress on an agent that fails will be rerun by another agent after a timeout period of 140 seconds.
+If one Checkly Agent fails, the other agents in the same Private Location will continue to run the checks assigned to that location. Even checks that are currently in progress on an agent that fails will be rerun by another agent after a timeout period of 300 seconds.
 
 There are two cases where checks assigned to a location could fail to run: