Fix typos (#8149)

Author: krsriq

billing.md

@@ -746,7 +746,7 @@ You may also create subscriptions from the Stripe dashboard itself. When doing s
 
 In addition, you may only create one type of subscription via the Stripe dashboard. If your application offers multiple subscriptions that use different names, only one type of subscription may be added through the Stripe dashboard.
 
-Finally, you should always make sure to only add one active subscription per type of subscription offered by your application. If customer has two `default` subscriptions, only the most recently added subscription will be used by Cashier even though both would be synced with your application's database.
+Finally, you should always make sure to only add one active subscription per type of subscription offered by your application. If a customer has two `default` subscriptions, only the most recently added subscription will be used by Cashier even though both would be synced with your application's database.
 
 <a name="checking-subscription-status"></a>
 ### Checking Subscription Status

cashier-paddle.md

@@ -739,7 +739,7 @@ If you would like to swap plans and immediately invoice the user instead of wait
 <a name="prorations"></a>
 #### Prorations
 
-By default, Paddle prorates charges when swapping between plans. The `noProrate` method may be used to update the subscription's without prorating the charges:
+By default, Paddle prorates charges when swapping between plans. The `noProrate` method may be used to update the subscriptions without prorating the charges:
 
     $user->subscription('default')->noProrate()->swap($premium = 34567);
 

database.md

@@ -420,7 +420,7 @@ To get started, you should schedule the `db:monitor` command to [run every minut
 php artisan db:monitor --databases=mysql,pgsql --max=100
 ```
 
-Scheduling this command alone is not enough to trigger a notification alerting you of the number of open connections. When the command encounters a database that has a open connection count that exceeds your threshold, a `DatabaseBusy` event will be dispatched. You should listen for this event within your application's `EventServiceProvider` in order to send a notification to you or your development team:
+Scheduling this command alone is not enough to trigger a notification alerting you of the number of open connections. When the command encounters a database that has an open connection count that exceeds your threshold, a `DatabaseBusy` event will be dispatched. You should listen for this event within your application's `EventServiceProvider` in order to send a notification to you or your development team:
 
 ```php
 use App\Notifications\DatabaseApproachingMaxConnections;

dusk.md

@@ -583,7 +583,7 @@ The `press` method may be used to click a button element on the page. The argume
 
     $browser->press('Login');
 
-When submitting forms, many application's disable the form's submission button after it is pressed and then re-enable the button when the form submission's HTTP request is complete. To press a button and wait for the button to be re-enabled, you may use the `pressAndWaitFor` method:
+When submitting forms, many applications disable the form's submission button after it is pressed and then re-enable the button when the form submission's HTTP request is complete. To press a button and wait for the button to be re-enabled, you may use the `pressAndWaitFor` method:
 
     // Press the button and wait a maximum of 5 seconds for it to be enabled...
     $browser->pressAndWaitFor('Save');
@@ -1884,7 +1884,7 @@ script:
 <a name="running-tests-on-github-actions"></a>
 ### GitHub Actions
 
-If you are using [Github Actions](https://github.com/features/actions) to run your Dusk tests, you may use the following configuration file as a starting point. Like TravisCI, we will use the `php artisan serve` command to launch PHP's built-in web server:
+If you are using [GitHub Actions](https://github.com/features/actions) to run your Dusk tests, you may use the following configuration file as a starting point. Like TravisCI, we will use the `php artisan serve` command to launch PHP's built-in web server:
 
 ```yaml
 name: CI

eloquent-mutators.md

@@ -172,7 +172,7 @@ The mutator closure will receive the value that is being set on the attribute, a
 
     $user->first_name = 'Sally';
 
-In this example, the `set` callback will be called with the value `Sally`. The mutator will then apply the `strtolower` function to the name and set its resulting value in model's the internal `$attributes` array.
+In this example, the `set` callback will be called with the value `Sally`. The mutator will then apply the `strtolower` function to the name and set its resulting value in the model's internal `$attributes` array.
 
 <a name="mutating-multiple-attributes"></a>
 #### Mutating Multiple Attributes

eloquent-resources.md

@@ -323,12 +323,12 @@ By default, your outermost resource is wrapped in a `data` key when the resource
         {
             "id": 1,
             "name": "Eladio Schroeder Sr.",
-            "email": "[email protected]",
+            "email": "[email protected]"
         },
         {
             "id": 2,
             "name": "Liliana Mayert",
-            "email": "[email protected]",
+            "email": "[email protected]"
         }
     ]
 }
@@ -425,12 +425,12 @@ When returning paginated collections via a resource response, Laravel will wrap
         {
             "id": 1,
             "name": "Eladio Schroeder Sr.",
-            "email": "[email protected]",
+            "email": "[email protected]"
         },
         {
             "id": 2,
             "name": "Liliana Mayert",
-            "email": "[email protected]",
+            "email": "[email protected]"
         }
     ],
     "links":{
@@ -471,12 +471,12 @@ Paginated responses always contain `meta` and `links` keys with information abou
         {
             "id": 1,
             "name": "Eladio Schroeder Sr.",
-            "email": "[email protected]",
+            "email": "[email protected]"
         },
         {
             "id": 2,
             "name": "Liliana Mayert",
-            "email": "[email protected]",
+            "email": "[email protected]"
         }
     ],
     "links":{
@@ -599,7 +599,7 @@ In addition to conditionally including relationships, you may conditionally incl
 
     new UserResource($user->loadCount('posts'));
 
-The `whenCounted` method may be used to conditionally include a relationship's count in your resource response. This method avoids unnecessarily including the attribute if the relationships's count is not present:
+The `whenCounted` method may be used to conditionally include a relationship's count in your resource response. This method avoids unnecessarily including the attribute if the relationships' count is not present:
 
     /**
      * Transform the resource into an array.

http-client.md

@@ -177,7 +177,7 @@ You may specify the maximum number of seconds to wait while trying to connect to
 <a name="retries"></a>
 ### Retries
 
-If you would like HTTP client to automatically retry the request if a client or server error occurs, you may use the `retry` method. The `retry` method accepts the maximum number of times the request should be attempted and the number of milliseconds that Laravel should wait in between attempts:
+If you would like the HTTP client to automatically retry the request if a client or server error occurs, you may use the `retry` method. The `retry` method accepts the maximum number of times the request should be attempted and the number of milliseconds that Laravel should wait in between attempts:
 
     $response = Http::retry(3, 100)->post(/* ... */);
 
@@ -187,7 +187,7 @@ If needed, you may pass a third argument to the `retry` method. The third argume
         return $exception instanceof ConnectionException;
     })->post(/* ... */);
 
-If a request attempt fails, you may wish to make a change to the request before a new attempt is made. You can achieve this by modifying request argument provided to the callable you provided to the `retry` method. For example, you might want to retry the request with a new authorization token if the first attempt returned an authentication error:
+If a request attempt fails, you may wish to make a change to the request before a new attempt is made. You can achieve this by modifying the request argument provided to the callable you provided to the `retry` method. For example, you might want to retry the request with a new authorization token if the first attempt returned an authentication error:
 
     $response = Http::withToken($this->getToken())->retry(2, 0, function ($exception, $request) {
         if (! $exception instanceof RequestException || $exception->response->status() !== 401) {

http-tests.md

@@ -698,7 +698,7 @@ Assert that the response contains the given cookie and it is not expired:
 <a name="assert-cookie-missing"></a>
 #### assertCookieMissing
 
-Assert that the response does not contains the given cookie:
+Assert that the response does not contain the given cookie:
 
     $response->assertCookieMissing($cookieName);
 
@@ -828,7 +828,7 @@ Assert that the response contains the given data at the specified path:
 
 For example, if the following JSON response is returned by your application:
 
-```js
+```json
 {
     "user": {
         "name": "Steve Schoger"
@@ -849,7 +849,7 @@ Assert that the response does not contain the given path:
 
 For example, if the following JSON response is returned by your application:
 
-```js
+```json
 {
     "user": {
         "name": "Steve Schoger"
@@ -870,7 +870,7 @@ Assert that the response has a given JSON structure:
 
 For example, if the JSON response returned by your application contains the following data:
 
-```js
+```json
 {
     "user": {
         "name": "Steve Schoger"
@@ -888,7 +888,7 @@ You may assert that the JSON structure matches your expectations like so:
 
 Sometimes, JSON responses returned by your application may contain arrays of objects:
 
-```js
+```json
 {
     "user": [
         {

localization.md

@@ -24,7 +24,7 @@ Laravel provides two ways to manage translation strings. First, language strings
         /es
             messages.php
 
-Or, translation strings may be defined within JSON files that are placed within the `lang` directory. When taking this approach, each language supported by your application would have a corresponding JSON file within this directory. This approach is recommended for application's that have a large number of translatable strings:
+Or, translation strings may be defined within JSON files that are placed within the `lang` directory. When taking this approach, each language supported by your application would have a corresponding JSON file within this directory. This approach is recommended for applications that have a large number of translatable strings:
 
     /lang
         en.json

mocking.md

@@ -178,7 +178,7 @@ You may use the `Bus` facade's `fake` method to prevent jobs from being dispatch
             // Assert that a job was dispatched synchronously...
             Bus::assertDispatchedSync(AnotherJob::class);
 
-            // Assert that a job was not dipatched synchronously...
+            // Assert that a job was not dispatched synchronously...
             Bus::assertNotDispatchedSync(AnotherJob::class);
 
             // Assert that a job was dispatched after the response was sent...

notifications.md

@@ -52,7 +52,7 @@
 <a name="introduction"></a>
 ## Introduction
 
-In addition to support for [sending email](/docs/{{version}}/mail), Laravel provides support for sending notifications across a variety of delivery channels, including email, SMS (via [Vonage](https://www.vonage.com/communications-apis/), formerly known as Nexmo), and [Slack](https://slack.com). In addition, a variety of [community built notification channels](https://laravel-notification-channels.com/about/#suggesting-a-new-channel) have been created to send notification over dozens of different channels! Notifications may also be stored in a database so they may be displayed in your web interface.
+In addition to support for [sending email](/docs/{{version}}/mail), Laravel provides support for sending notifications across a variety of delivery channels, including email, SMS (via [Vonage](https://www.vonage.com/communications-apis/), formerly known as Nexmo), and [Slack](https://slack.com). In addition, a variety of [community built notification channels](https://laravel-notification-channels.com/about/#suggesting-a-new-channel) have been created to send notifications over dozens of different channels! Notifications may also be stored in a database so they may be displayed in your web interface.
 
 Typically, notifications should be short, informational messages that notify users of something that occurred in your application. For example, if you are writing a billing application, you might send an "Invoice Paid" notification to your users via the email and SMS channels.
 

pagination.md

@@ -212,7 +212,7 @@ If you need to append a "hash fragment" to URLs generated by the paginator, you
 
 When calling the `paginate` method, you will receive an instance of `Illuminate\Pagination\LengthAwarePaginator`, while calling the `simplePaginate` method returns an instance of `Illuminate\Pagination\Paginator`. And, finally, calling the `cursorPaginate` method returns an instance of `Illuminate\Pagination\CursorPaginator`.
 
-These objects provide several methods that describe the result set. In addition to these helpers methods, the paginator instances are iterators and may be looped as an array. So, once you have retrieved the results, you may display the results and render the page links using [Blade](/docs/{{version}}/blade):
+These objects provide several methods that describe the result set. In addition to these helper methods, the paginator instances are iterators and may be looped as an array. So, once you have retrieved the results, you may display the results and render the page links using [Blade](/docs/{{version}}/blade):
 
 ```blade
 <div class="container">

queues.md

@@ -1465,7 +1465,7 @@ php artisan queue:work
 > **Note**  
 > To keep the `queue:work` process running permanently in the background, you should use a process monitor such as [Supervisor](#supervisor-configuration) to ensure that the queue worker does not stop running.
 
-Remember, queue workers, are long-lived processes and store the booted application state in memory. As a result, they will not notice changes in your code base after they have been started. So, during your deployment process, be sure to [restart your queue workers](#queue-workers-and-deployment). In addition, remember that any static state created or modified by your application will not be automatically reset between jobs.
+Remember, queue workers are long-lived processes and store the booted application state in memory. As a result, they will not notice changes in your code base after they have been started. So, during your deployment process, be sure to [restart your queue workers](#queue-workers-and-deployment). In addition, remember that any static state created or modified by your application will not be automatically reset between jobs.
 
 Alternatively, you may run the `queue:listen` command. When using the `queue:listen` command, you don't have to manually restart the worker when you want to reload your updated code or reset the application state; however, this command is significantly less efficient than the `queue:work` command:
 

redis.md

@@ -183,7 +183,7 @@ In addition to the default `scheme`, `host`, `port`, `database`, and `password`
 <a name="phpredis-serialization"></a>
 #### phpredis Serialization & Compression
 
-The phpredis extension may also be configured to use a variety serialization and compression algorithms. These algorithms can be configured via the `options` array of your Redis configuration:
+The phpredis extension may also be configured to use a variety of serialization and compression algorithms. These algorithms can be configured via the `options` array of your Redis configuration:
 
     'redis' => [
 

sail.md

@@ -271,7 +271,7 @@ The Sail `test` command is equivalent to running the `test` Artisan command:
 sail artisan test
 ```
 
-By default, Sail will create a dedicated `testing` database that your tests do not interfere with the current state of your database. In a default Laravel installation, Sail will also configure your `phpunit.xml` file to use this database when executing your tests:
+By default, Sail will create a dedicated `testing` database so that your tests do not interfere with the current state of your database. In a default Laravel installation, Sail will also configure your `phpunit.xml` file to use this database when executing your tests:
 
 ```xml
 <env name="DB_DATABASE" value="testing"/>

scout.md

@@ -184,7 +184,7 @@ By default, the entire `toArray` form of a given model will be persisted to its
 <a name="configuring-the-model-id"></a>
 ### Configuring The Model ID
 
-By default, Scout will use the primary key of the model as model's unique ID / key that is stored in the search index. If you need to customize this behavior, you may override the `getScoutKey` and the `getScoutKeyName` methods on the model:
+By default, Scout will use the primary key of the model as the model's unique ID / key that is stored in the search index. If you need to customize this behavior, you may override the `getScoutKey` and the `getScoutKeyName` methods on the model:
 
     <?php
 

starter-kits.md

@@ -20,7 +20,7 @@ While you are welcome to use these starter kits, they are not required. You are
 
 [Laravel Breeze](https://github.com/laravel/breeze) is a minimal, simple implementation of all of Laravel's [authentication features](/docs/{{version}}/authentication), including login, registration, password reset, email verification, and password confirmation. Laravel Breeze's default view layer is made up of simple [Blade templates](/docs/{{version}}/blade) styled with [Tailwind CSS](https://tailwindcss.com). Or, Breeze can scaffold your application using Vue or React and [Inertia](https://inertiajs.com).
 
-Breeze provides a wonderful starting point for beginning a fresh Laravel application and is also great choice for projects that plan to take their Blade templates to the next level with [Laravel Livewire](https://laravel-livewire.com).
+Breeze provides a wonderful starting point for beginning a fresh Laravel application and is also a great choice for projects that plan to take their Blade templates to the next level with [Laravel Livewire](https://laravel-livewire.com).
 
 <img src="https://laravel.com/img/docs/breeze-register.png">