apply docs suggestions

Author: cristunaranjo

docs/source/api/apollo-server.mdx

@@ -525,9 +525,9 @@ const server = new ApolloServer({
 });
 ```
 
-When variable coercion encounters more errors than the specified limit, GraphQL execution will be terminated with an error message indicating that the error limit was reached. This is useful for preventing potentially expensive operations when many input variables are malformed.
+When variable coercion encounters more errors than the specified limit, GraphQL execution terminates with an error message indicating that the error limit was reached. This is useful for preventing potentially expensive operations when many input variables are malformed.
 
-**Note:** This option works in conjunction with [`status400ForVariableCoercionErrors`](#status400forvariablecoercionerrors) to provide appropriate HTTP status codes for variable coercion errors.
+Note: This option works in conjunction with [<code>status400ForVariableCoercionErrors</code>](#status400forvariablecoercionerrors) to provide appropriate HTTP status codes for variable coercion errors.
 
 </td>
 </tr>

docs/source/data/errors.mdx

@@ -5,6 +5,8 @@ description: Making errors actionable on the client and server
 
 import TopLevelAwait from "../shared/top-level-await.mdx"
 
+You can configure how many variable coercion errors are allowed before execution terminates using the [<code>executionOptions</code>](../api/apollo-server#executionoptions) field.
+
 <!-- cSpell:ignore typenam -->
 
 Whenever Apollo Server encounters errors while processing a GraphQL operation, its response to the client includes an `errors` array containing each error that occurred. Each error in the array has an `extensions` field that provides additional useful information, including an error `code` and (while in development mode) a `stacktrace`.