fix: forgot to run prettier

README.md

@@ -6,8 +6,8 @@
 flow, allowing developers to develop, share and collaborate on GraphQL-related plugins while filling
 the missing pieces in GraphQL implementations.
 
-`envelop` aims to extend the GraphQL execution flow by adding plugins that enrich the feature set
-of your application.
+`envelop` aims to extend the GraphQL execution flow by adding plugins that enrich the feature set of
+your application.
 
 <p align="center">
   <img height="150" src="./logo.png">
@@ -171,8 +171,8 @@ Feel free to open issues and pull requests. We're always welcome support from th
 ### Code of Conduct
 
 Help us keep Envelop open and inclusive. Please read and follow our
-[Code of Conduct](https://github.com/the-guild-org/Stack/blob/master/CODE_OF_CONDUCT.md) as adopted from
-[Contributor Covenant](https://www.contributor-covenant.org/)
+[Code of Conduct](https://github.com/the-guild-org/Stack/blob/master/CODE_OF_CONDUCT.md) as adopted
+from [Contributor Covenant](https://www.contributor-covenant.org/)
 
 ### License
 

packages/core/test/schema-change.spec.ts

@@ -16,7 +16,7 @@ describe('schemaChange', () => {
     expect(spiedPlugin.spies.onSchemaChange).toHaveBeenCalledTimes(0);
   });
 
-  it('Should trigger schema change only for plugins that don\'t trigger the change itself', async () => {
+  it("Should trigger schema change only for plugins that don't trigger the change itself", async () => {
     const pluginA = { onSchemaChange: jest.fn() };
     const pluginB = { onSchemaChange: jest.fn() };
 

website/src/pages/v3/guides/securing-your-graphql-api.mdx

@@ -101,8 +101,8 @@ const getEnveloped = envelop({
 
 ### Reject Malicious Operation Documents
 
-Parsing a GraphQL operation document is a very expensive and compute intensive operation that
-blocks the JavaScript event loop. If an attacker sends a very complex operation document with slight
+Parsing a GraphQL operation document is a very expensive and compute intensive operation that blocks
+the JavaScript event loop. If an attacker sends a very complex operation document with slight
 variations over and over again he can easily degrade the performance of the GraphQL server. Because
 of the variations simply having an LRU cache for parsed operation documents is not enough.
 

website/src/pages/v3/plugins/index.mdx

@@ -34,6 +34,7 @@ The plugin order specifies the order in which the handlers of each plugin will b
 `onExecute` hook of the plugin at the array index 0 will always be invoked before the plugin at the
 index 1.
 
-Plugins have the option to stop the execution completely and stop calling further plugins `onExecute`
-hooks. The `useResponseCache` plugin is such a plugin. Once a response is served from the cache all
-further `onExecute` are never called and all `onExecuteDone` hooks are never called at all.
+Plugins have the option to stop the execution completely and stop calling further plugins
+`onExecute` hooks. The `useResponseCache` plugin is such a plugin. Once a response is served from
+the cache all further `onExecute` are never called and all `onExecuteDone` hooks are never called at
+all.