Skip to content

Commit c72ccde

Browse files
kathaylToriLindsay
andauthored
Update src/content/docs/browser-rendering/faq.mdx
Co-authored-by: ToriLindsay <[email protected]>
1 parent 2886b6c commit c72ccde

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/browser-rendering

1 file changed

+1
-1
lines changed

src/content/docs/browser-rendering/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,4 +96,4 @@ If you are still running into concurrency limits you can [request a higher limit
9696
No, there is not a fixed limit on the number of requests per browser session. A single browser can handle multiple requests as long as it stays within the available compute and memory limits.
9797

9898
### Do failed API calls, such as those that time out, add to billable browser hours?
99-
No. If a request to the Browser Rendering REST API fails with a waitForTimeout error, the browser session is not charged.
99+
No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.

0 commit comments

Comments
 (0)