Remove CJS from docs (#4400)

Author: JoviDeCroock

website/pages/api-v16/error.mdx

@@ -10,8 +10,7 @@ The `graphql/error` module is responsible for creating and formatting
 GraphQL errors. You can import either from the `graphql/error` module, or from the root `graphql` module. For example:
 
 ```js
-import { GraphQLError } from 'graphql'; // ES6
-const { GraphQLError } = require('graphql'); // CommonJS
+import { GraphQLError } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/execution.mdx

@@ -10,8 +10,7 @@ The `graphql/execution` module is responsible for the execution phase of
 fulfilling a GraphQL request. You can import either from the `graphql/execution` module, or from the root `graphql` module. For example:
 
 ```js
-import { execute } from 'graphql'; // ES6
-const { execute } = require('graphql'); // CommonJS
+import { execute } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/graphql-http.mdx

@@ -11,8 +11,7 @@ The [official `graphql-http` package](https://github.com/graphql/graphql-http) p
 ## Express
 
 ```js
-import { createHandler } from 'graphql-http/lib/use/express'; // ES6
-const { createHandler } = require('graphql-http/lib/use/express'); // CommonJS
+import { createHandler } from 'graphql-http/lib/use/express';
 ```
 
 ### createHandler

website/pages/api-v16/graphql.mdx

@@ -10,8 +10,7 @@ The `graphql` module exports a core subset of GraphQL functionality for creation
 of GraphQL type systems and servers.
 
 ```js
-import { graphql } from 'graphql'; // ES6
-const { graphql } = require('graphql'); // CommonJS
+import { graphql } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/language.mdx

@@ -9,8 +9,7 @@ title: graphql/language
 The `graphql/language` module is responsible for parsing and operating on the GraphQL language. You can import either from the `graphql/language` module, or from the root `graphql` module. For example:
 
 ```js
-import { Source } from 'graphql'; // ES6
-const { Source } = require('graphql'); // CommonJS
+import { Source } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/type.mdx

@@ -9,8 +9,7 @@ title: graphql/type
 The `graphql/type` module is responsible for defining GraphQL types and schema. You can import either from the `graphql/type` module, or from the root `graphql` module. For example:
 
 ```js
-import { GraphQLSchema } from 'graphql'; // ES6
-const { GraphQLSchema } = require('graphql'); // CommonJS
+import { GraphQLSchema } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/utilities.mdx

@@ -10,8 +10,7 @@ The `graphql/utilities` module contains common useful computations to use with
 the GraphQL language and type objects. You can import either from the `graphql/utilities` module, or from the root `graphql` module. For example:
 
 ```js
-import { introspectionQuery } from 'graphql'; // ES6
-const { introspectionQuery } = require('graphql'); // CommonJS
+import { introspectionQuery } from 'graphql';
 ```
 
 ## Overview

website/pages/api-v16/validation.mdx

@@ -10,8 +10,7 @@ The `graphql/validation` module fulfills the Validation phase of fulfilling a
 GraphQL result. You can import either from the `graphql/validation` module, or from the root `graphql` module. For example:
 
 ```js
-import { validate } from 'graphql/validation'; // ES6
-const { validate } = require('graphql/validation'); // CommonJS
+import { validate } from 'graphql/validation';
 ```
 
 ## Overview

website/pages/docs/abstract-types.mdx

@@ -36,7 +36,7 @@ concrete type a given value corresponds to.
 The following example defines a `ContentItem` interface for a publishing platform:
 
 ```js
-const { GraphQLInterfaceType, GraphQLString, GraphQLNonNull } = require('graphql');
+import { GraphQLInterfaceType, GraphQLString, GraphQLNonNull } from 'graphql';
 
 const ContentItemInterface = new GraphQLInterfaceType({
   name: 'ContentItem',
@@ -69,7 +69,7 @@ The following example implements the `Article` and `PodcastEpisode` types that
 conform to the `ContentItem` interface:
 
 ```js
-const { GraphQLObjectType, GraphQLString, GraphQLNonNull } = require('graphql');
+import { GraphQLObjectType, GraphQLString, GraphQLNonNull } from 'graphql';
 
 const ArticleType = new GraphQLObjectType({
   name: 'Article',
@@ -114,7 +114,7 @@ A union requires:
 The following example defines a `SearchResult` union:
 
 ```js
-const { GraphQLUnionType } = require('graphql');
+import { GraphQLUnionType } from 'graphql';
 
 const SearchResultType = new GraphQLUnionType({
   name: 'SearchResult',
@@ -134,7 +134,7 @@ const SearchResultType = new GraphQLUnionType({
 });
 ```
 
-Unlike interfaces, unions don’t declare any fields of their own. Clients use inline fragments 
+Unlike interfaces, unions don't declare any fields of their own. Clients use inline fragments 
 to query fields from the concrete types.
 
 ## Resolving abstract types at runtime

website/pages/docs/advanced-custom-scalars.mdx

@@ -9,7 +9,7 @@ schema, follow these best practices.
 
 ### Document expected formats and validation
 
-Provide a clear description of the scalar’s accepted input and output formats. For example, a 
+Provide a clear description of the scalar's accepted input and output formats. For example, a 
 `DateTime` scalar should explain that it expects [ISO-8601](https://www.iso.org/iso-8601-date-and-time-format.html) strings ending with `Z`.
 
 Clear descriptions help clients understand valid input and reduce mistakes.
@@ -100,8 +100,8 @@ describe('DateTime scalar', () => {
 Integrate the scalar into a schema and run real GraphQL queries to validate end-to-end behavior.
 
 ```js
-const { graphql, GraphQLSchema, GraphQLObjectType } = require('graphql');
-const { DateTimeResolver as DateTime } = require('graphql-scalars');
+import { graphql, GraphQLSchema, GraphQLObjectType } from 'graphql';
+import { DateTimeResolver as DateTime } from 'graphql-scalars';
 
 const Query = new GraphQLObjectType({
   name: 'Query',
@@ -184,13 +184,13 @@ scalars for DateTime, EmailAddress, URL, UUID, and many others.
 ### Example: Handling email validation
 
 Handling email validation correctly requires dealing with Unicode, quoted local parts, and 
-domain validation. Rather than writing your own regex, it’s better to use a library scalar 
+domain validation. Rather than writing your own regex, it's better to use a library scalar 
 that's already validated against standards.
 
 If you need domain-specific behavior, you can wrap an existing scalar with custom rules:
 
 ```js
-const { EmailAddressResolver } = require('graphql-scalars');
+import { EmailAddressResolver } from 'graphql-scalars';
 
 const StrictEmailAddress = new GraphQLScalarType({
   ...EmailAddressResolver,