fix(gatsby-source-wordpress): remove hard tabs from Markdown (#29627)

gatsbyjs · Feb 22, 2021 · 0038683 · 0038683
1 parent 258e0f7
commit 0038683
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 15 deletions.
diff --git a/packages/gatsby-source-wordpress/docs/debugging-and-troubleshooting.md b/packages/gatsby-source-wordpress/docs/debugging-and-troubleshooting.md
@@ -39,7 +39,7 @@ Take that query and make the query directly to your WP instance GraphQL API like
 {
   pages {
     nodes {
-    	id
+      id
       title
     }
   }
@@ -54,10 +54,10 @@ Take that query and make the query directly to your WP instance GraphQL API like
    ```js
    {
      resolve: `gatsby-source-wordpress`,
-   	options: {
-   		debug: {
+     options: {
+       debug: {
          graphql: {
-         	writeQueriesToDisk: true,
+           writeQueriesToDisk: true,
          },
        },
      },
@@ -103,10 +103,10 @@ If your build is erroring on a GraphQL error returned in the response from a Gra
 ```js
 {
   resolve: `gatsby-source-wordpress`,
-	options: {
-		debug: {
+  options: {
+    debug: {
       graphql: {
-      	writeQueriesToDisk: true,
+        writeQueriesToDisk: true,
       },
     },
   },
@@ -136,8 +136,8 @@ To determine how many concurrent GraphQL requests your server can handle, enable
 ```js
 {
   resolve: `gatsby-source-wordpress`,
-	options: {
-		verbose: true,
+  options: {
+    verbose: true,
   },
 },
 ```

diff --git a/packages/gatsby-source-wordpress/docs/migrating-from-other-wp-source-plugins.md b/packages/gatsby-source-wordpress/docs/migrating-from-other-wp-source-plugins.md
@@ -34,7 +34,7 @@ For example, if you're querying for a list of pages:
 
 ```js
 {
-	wp {
+  wp {
     pages {
       nodes {
         title
@@ -50,11 +50,11 @@ So your query would change to look like this:
 
 ```
 {
-	allWpPage {
-		nodes {
-			title
-		}
-	}
+  allWpPage {
+    nodes {
+      title
+    }
+  }
 }
 ```