Update note about local development and testing

Author: stayallive

docs/platforms/php/guides/laravel/index.mdx

@@ -105,13 +105,13 @@ Performance data is transmitted using a new event type called "transactions", wh
 
 ## Local Development and Testing
 
-When Sentry is installed in your application, it will also be active when you are developing or running tests.
+When Sentry is installed in your application, it will also be active when you are developing or running tests. Because PHP is single-threaded, Sentry will send events synchronously, which can slow down your application or test suite.
 
-You most likely don't want errors to be sent to Sentry when you are developing or running tests. To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
+You most likely don't want errors to be sent to Sentry when you are developing or running tests so they don't use up [quota](/pricing/quotas/). To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
 
 You can also do this by not defining `SENTRY_LARAVEL_DSN` in your `.env` or by defining it as `SENTRY_LARAVEL_DSN=null`.
 
-If you do leave Sentry enabled when developing or running tests, it's possible for it to have a negative effect on the performance of your application or test suite.
+If you want to use Sentry in your local development environment, you can use [Spotlight](https://spotlightjs.com/) which runs locally on your machine.
 
 ## Set up Sentry through Forge
 

docs/platforms/php/guides/laravel/other-versions/laravel5.mdx

@@ -92,12 +92,10 @@ Visiting this route will trigger an exception that will be captured by Sentry.
 
 ## Local Development and Testing
 
-When Sentry is installed in your application, it will also be active when you are developing or running tests.
+When Sentry is installed in your application, it will also be active when you are developing or running tests. Because PHP is single-threaded, Sentry will send events synchronously, which can slow down your application or test suite.
 
-You most likely don't want errors to be sent to Sentry when you are developing or running tests. To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
+You most likely don't want errors to be sent to Sentry when you are developing or running tests so they don't use up [quota](/pricing/quotas/). To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
 
 You can also do this by not defining `SENTRY_LARAVEL_DSN` in your `.env` or by defining it as `SENTRY_LARAVEL_DSN=null`.
 
-If you do leave Sentry enabled when developing or running tests, it's possible for it to have a negative effect on the performance of your application or test suite.
-
 <PageGrid nextPages header="Next Steps" />

docs/platforms/php/guides/laravel/other-versions/laravel6-7.mdx

@@ -86,12 +86,10 @@ Visiting this route will trigger an exception that will be captured by Sentry.
 
 ## Local Development and Testing
 
-When Sentry is installed in your application, it will also be active when you are developing or running tests.
+When Sentry is installed in your application, it will also be active when you are developing or running tests. Because PHP is single-threaded, Sentry will send events synchronously, which can slow down your application or test suite.
 
-You most likely don't want errors to be sent to Sentry when you are developing or running tests. To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
+You most likely don't want errors to be sent to Sentry when you are developing or running tests so they don't use up [quota](/pricing/quotas/). To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
 
 You can also do this by not defining `SENTRY_LARAVEL_DSN` in your `.env` or by defining it as `SENTRY_LARAVEL_DSN=null`.
 
-If you do leave Sentry enabled when developing or running tests, it's possible for it to have a negative effect on the performance of your application or test suite.
-
 <PageGrid nextPages header="Next Steps" />

docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx

@@ -94,10 +94,8 @@ Performance data is transmitted using a new event type called "transactions", wh
 
 ## Local Development and Testing
 
-When Sentry is installed in your application, it will also be active when you are developing or running tests.
+When Sentry is installed in your application, it will also be active when you are developing or running tests. Because PHP is single-threaded, Sentry will send events synchronously, which can slow down your application or test suite.
 
-You most likely don't want errors to be sent to Sentry when you are developing or running tests. To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
+You most likely don't want errors to be sent to Sentry when you are developing or running tests so they don't use up [quota](/pricing/quotas/). To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
 
 You can also do this by not defining `SENTRY_LARAVEL_DSN` in your `.env` or by defining it as `SENTRY_LARAVEL_DSN=null`.
-
-If you do leave Sentry enabled when developing or running tests, it's possible for it to have a negative effect on the performance of your application or test suite.

docs/platforms/php/guides/laravel/other-versions/lumen.mdx

@@ -80,12 +80,10 @@ Visiting this route will trigger an exception that will be captured by Sentry.
 
 ## Local Development and Testing
 
-When Sentry is installed in your application, it will also be active when you are developing or running tests.
+When Sentry is installed in your application, it will also be active when you are developing or running tests. Because PHP is single-threaded, Sentry will send events synchronously, which can slow down your application or test suite.
 
-You most likely don't want errors to be sent to Sentry when you are developing or running tests. To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
+You most likely don't want errors to be sent to Sentry when you are developing or running tests so they don't use up [quota](/pricing/quotas/). To avoid this, set the DSN value to `null` to disable sending errors to Sentry.
 
 You can also do this by not defining `SENTRY_LARAVEL_DSN` in your `.env` or by defining it as `SENTRY_LARAVEL_DSN=null`.
 
-If you do leave Sentry enabled when developing or running tests, it's possible for it to have a negative effect on the performance of your application or test suite.
-
 <PageGrid nextPages header="Next Steps" />