Skip to content

[12.x] Use straight quotation marks for consistency #10794

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

taylorotwell merged 3 commits into laravel:12.x from AhmedAlaa4611:straight-quotation-marks

Sep 3, 2025

Merged

[12.x] Use straight quotation marks for consistency #10794

Changes from all commits

Commits

Show all changes

Select commit Hold shift + click to select a range

Update cache.md

AhmedAlaa4611 Sep 3, 2025

Update horizon.md

AhmedAlaa4611 Sep 3, 2025

AhmedAlaa4611 Sep 3, 2025

File filter

Filter by extension

Conversations

Jump to

Jump to file

Failed to load files.

Loading

Diff view

Diff view

2 changes: 1 addition & 1 deletion cache.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -237,7 +237,7 @@ $value = Cache::rememberForever('users', function () {

		When using the `Cache::remember` method, some users may experience slow response times if the cached value has expired. For certain types of data, it can be useful to allow partially stale data to be served while the cached value is recalculated in the background, preventing some users from experiencing slow response times while cached values are calculated. This is often referred to as the "stale-while-revalidate" pattern, and the `Cache::flexible` method provides an implementation of this pattern.

	The flexible method accepts an array that specifies how long the cached value is considered "fresh" and when it becomes "stale." The first value in the array represents the number of seconds the cache is considered fresh, while the second value defines how long it can be served as stale data before recalculation is necessary.
	The flexible method accepts an array that specifies how long the cached value is considered "fresh" and when it becomes "stale". The first value in the array represents the number of seconds the cache is considered fresh, while the second value defines how long it can be served as stale data before recalculation is necessary.

		If a request is made within the fresh period (before the first value), the cache is returned immediately without recalculation. If a request is made during the stale period (between the two values), the stale value is served to the user, and a [deferred function](/docs/{{version}}/helpers#deferred-functions) is registered to refresh the cached value after the response is sent to the user. If a request is made after the second value, the cache is considered expired, and the value is recalculated immediately, which may result in a slower response for the user:

Expand Down

2 changes: 1 addition & 1 deletion dusk.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -2392,7 +2392,7 @@ $browser->visit(new Dashboard)
		<a name="components"></a>
		## Components

	Components are similar to Dusk's "page objects", but are intended for pieces of UI and functionality that are re-used throughout your application, such as a navigation bar or notification window. As such, components are not bound to specific URLs.
	Components are similar to Dusk's "page objects", but are intended for pieces of UI and functionality that are re-used throughout your application, such as a navigation bar or notification window. As such, components are not bound to specific URLs.

		<a name="generating-components"></a>
		### Generating Components
Expand Down

4 changes: 2 additions & 2 deletions horizon.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -200,7 +200,7 @@ Similarly, you can set a `timeout` value at the supervisor level, which specifie
		```

		> [!WARNING]
	> When using the `auto` balancing strategy, Horizon will consider in-progress workers as "hanging" and force-kill them after the Horizon timeout during scale down. Always ensure the Horizon timeout is greater than any job-level timeout, otherwise jobs may be terminated mid-execution. In addition, the `timeout` value should always be at least a few seconds shorter than the `retry_after` value defined in your `config/queue.php` configuration file. Otherwise, your jobs may be processed twice.
	> When using the `auto` balancing strategy, Horizon will consider in-progress workers as "hanging" and force-kill them after the Horizon timeout during scale down. Always ensure the Horizon timeout is greater than any job-level timeout, otherwise jobs may be terminated mid-execution. In addition, the `timeout` value should always be at least a few seconds shorter than the `retry_after` value defined in your `config/queue.php` configuration file. Otherwise, your jobs may be processed twice.

		<a name="job-backoff"></a>
		### Job Backoff
Expand Down Expand Up		@@ -535,7 +535,7 @@ sudo supervisorctl start horizon
		<a name="tags"></a>
		## Tags

	Horizon allows you to assign "tags" to jobs, including mailables, broadcast events, notifications, and queued event listeners. In fact, Horizon will intelligently and automatically tag most jobs depending on the Eloquent models that are attached to the job. For example, take a look at the following job:
	Horizon allows you to assign "tags" to jobs, including mailables, broadcast events, notifications, and queued event listeners. In fact, Horizon will intelligently and automatically tag most jobs depending on the Eloquent models that are attached to the job. For example, take a look at the following job:

		```php
		<?php
Expand Down