apply docs suggestions

Author: cristunaranjo

docs/source/api/apollo-server.mdx

@@ -505,9 +505,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

@@ -7,7 +7,7 @@ import TopLevelAwait from "../shared/top-level-await.mdx"
 
 > Apollo Server v4 introduced a regression where providing invalid variables yields a 200 status code instead of 400. To mitigate this regression, provide the `status400ForVariableCoercionErrors: true` option to your `ApolloServer` constructor. For more information, see the [migration guide](../migration/#known-regressions).
 
-You can also configure how many variable coercion errors are allowed before execution is terminated using the [`executionOptions`](../api/apollo-server#executionoptions) field.
+You can also configure how many variable coercion errors are allowed before execution terminates using the [<code>executionOptions</code>](../api/apollo-server#executionoptions) field.
 
 <!-- cSpell:ignore typenam -->