fix: address review comments on semantic line breaks PR

Co-authored-by: spawnia <12158000+spawnia@users.noreply.github.com>

Author: Copilot

docs/3/testing/phpunit.md

@@ -68,7 +68,7 @@ public function testCreatePost(): void
 
 Now that we know how to query our server in tests, we need to make sure the returned results match our expectations.
 
-The returned `TestResponse` conveniently offers assertions that work quite well quite with the JSON data returned by GraphQL.
+The returned `TestResponse` conveniently offers assertions that work quite well with the JSON data returned by GraphQL.
 
 The `assertJson` method asserts that the response is a superset of the given JSON.
 

docs/3/the-basics/directives.md

@@ -7,7 +7,7 @@ Those are called _directives_ and are the primary way to add functionality to yo
 
 ## Definition
 
-Directives always begin with an `@` symbol, followed by an unique name.
+Directives always begin with an `@` symbol, followed by a unique name.
 They may be used at specified parts of the GraphQL schema.
 
 This example directive `@upperCase` may be used on field definitions to UPPERCASE the result.

docs/4/subscriptions/client-implementations.md

@@ -1,6 +1,6 @@
 # Client Implementations
 
-To get you up and running quickly, the following sections show how to use subcriptions with common GraphQL client libraries.
+To get you up and running quickly, the following sections show how to use subscriptions with common GraphQL client libraries.
 
 ## Apollo
 

docs/5/performance/deferred.md

@@ -2,8 +2,10 @@
 
 **Experimental: not enabled by default, not guaranteed to be stable.**
 
-::: warning Currently the `@defer` directive requires Apollo Client in alpha.
-Track the state of the PR here: https://github.com/apollographql/apollo-client/pull/3686#issuecomment-555534519 :::
+::: warning
+Currently the `@defer` directive requires Apollo Client in alpha.
+Track the state of the PR here: https://github.com/apollographql/apollo-client/pull/3686#issuecomment-555534519
+:::
 
 Deferring fields allows you to prioritize fetching data needed to render the most important content as fast as possible,
 and then loading the rest of the page in the background.

docs/5/subscriptions/getting-started.md

@@ -2,7 +2,9 @@
 
 Subscriptions allow GraphQL clients to observe specific events and receive updates from the server when those events occur.
 
-::: tip NOTE Much of the credit should be given to the [Ruby implementation](https://github.com/rmosolgo/graphql-ruby/blob/master/guides/subscriptions/overview.md) as they provided a great overview of how the backend should work. :::
+::: tip NOTE
+Much of the credit should be given to the [Ruby implementation](https://github.com/rmosolgo/graphql-ruby/blob/master/guides/subscriptions/overview.md) as they provided a great overview of how the backend should work.
+:::
 
 ## Setup
 

docs/INDEX.md

@@ -1,6 +1,10 @@
 ---
-home: true title: Lighthouse - A framework for serving GraphQL from Laravel heroImage.
-/logo.svg actionText: Get Started → actionLink: /latest/getting-started/installation features:
+home: true
+title: Lighthouse - A framework for serving GraphQL from Laravel
+heroImage: /logo.svg
+actionText: Get Started →
+actionLink: /latest/getting-started/installation
+features:
   - title: 📜 SDL First
     details: Use the GraphQL Schema Definition Language to describe your data and add functionality through server-side directives.
   - title: ❤ Laravel Friendly

docs/master/digging-deeper/relay.md

@@ -2,7 +2,8 @@
 
 ## Cursor Connection
 
-Relay requires a particular kind of pagination which is the [Cursor Connection](https://facebook.github.io/relay/graphql/connections.htm) To get a relay-compatible connection on a root query field, use the [@paginate](../api-reference/directives.md#paginate) directive with the pagination type `CONNECTION`.
+Relay requires a particular kind of pagination which is the [Cursor Connection](https://facebook.github.io/relay/graphql/connections.htm).
+To get a relay-compatible connection on a root query field, use the [@paginate](../api-reference/directives.md#paginate) directive with the pagination type `CONNECTION`.
 
 > Lighthouse does not support actual cursor-based pagination as of now, see https://github.com/nuwave/lighthouse/issues/311 for details.
 > Under the hood, the "cursor" is decoded into a page offset.

docs/master/federation/entity-representations.md

@@ -30,7 +30,7 @@ type Comment @extends @key(fields: "id") {
 
 If entities don't have an Eloquent relationship within the subgraph, it's necessary to specify a separate resolver that will return the required information.
 The resolver should return data containing information about the `__typename` field.
-Corresponds to the entity's name and the primary key that can identify the entity.
+This corresponds to the entity's name and the primary key that can identify the entity.
 The `__typename` can either be provided as an explicit field or implicitly by returning an object with a matching class name.
 
 ### Example 1

docs/master/federation/getting-started.md

@@ -47,7 +47,7 @@ extend schema
 
 ## Federated tracing
 
-In order to use federated tracing, you need to enabled [tracing](../performance/tracing.md) and set the driver to `Nuwave\Lighthouse\Tracing\FederatedTracing\FederatedTracing::class` in your `config/lighthouse.php`:
+In order to use federated tracing, you need to enable [tracing](../performance/tracing.md) and set the driver to `Nuwave\Lighthouse\Tracing\FederatedTracing\FederatedTracing::class` in your `config/lighthouse.php`:
 
 ```php
 'tracing' => [

docs/master/performance/deferred.md

@@ -13,7 +13,7 @@ Register the service provider `Nuwave\Lighthouse\Defer\DeferServiceProvider`, se
 
 ## Configuration
 
-Consider the configuration options under `defer` in your `config/lighthouse.php` to prevent deferred queries from running to long.
+Consider the configuration options under `defer` in your `config/lighthouse.php` to prevent deferred queries from running too long.
 
 <br />