[Browser Rendering] Small limits footnote fix

Author: ToriLindsay

src/content/docs/browser-rendering/platform/limits.mdx

@@ -23,7 +23,7 @@ To increase this limit, you will need to [upgrade to a Workers Paid plan](/worke
 | Browser timeout                        | 60 seconds |
 | Total requests per min (REST API only) | 6 per minute    |
 
-By default, a browser instance gets killed if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the `keep_alive` [option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
+By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the `keep_alive` [option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
 
 ## Workers Paid
 
@@ -38,7 +38,7 @@ By default, a browser instance gets killed if it does not get any [devtools](htt
 
 [^1]: Contact our team to request increases to this limit.
 
-By default, a browser instance gets killed if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the `keep_alive` [option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
+By default, a browser will time out if it does not get any [devtools](https://chromedevtools.github.io/devtools-protocol/) command for 60 seconds, freeing one instance. Users can optionally increase this by using the `keep_alive` [option](/browser-rendering/platform/puppeteer/#keep-alive). `browser.close()` releases the browser instance.
 
 ## Note on concurrency