update all links

aar9nk · aar9nk · commit 216015bd8162 · 2024-11-24T11:55:03.000+11:00
diff --git a/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap b/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap
@@ -1363,7 +1363,7 @@ If you have explicitly defined a type for those fields, you can safely ignore th
 Otherwise, Gatsby will omit those fields from the GraphQL schema.
 
 If you know all field types in advance, the best strategy is to explicitly define them with the \`createTypes\` action, and skip inference with the \`@dontInfer\` directive.
-See https://www.gatsbyjs.com/docs/actions/#createTypes",
+See https://www.gatsbyjs.com/docs/reference/config-files/actions/#createTypes",
     ],
   ],
   "results": Array [
diff --git a/starters/gatsby-starter-wordpress-blog/gatsby-node.js b/starters/gatsby-starter-wordpress-blog/gatsby-node.js
@@ -97,7 +97,7 @@ async function createBlogPostArchive({ posts, gatsbyUtilities }) {
       }
 
       // createPage is an action passed to createPages
-      // See https://www.gatsbyjs.com/docs/actions#createPage for more info
+      // See https://www.gatsbyjs.com/reference/config-files/actions/#createPage for more info
       await gatsbyUtilities.actions.createPage({
         path: getPagePath(pageNumber),
 

Original file line number	Diff line number	Diff line change
`@@ -97,7 +97,7 @@ async function createBlogPostArchive({ posts, gatsbyUtilities }) {`
`97`	`97`	`}`
`98`	`98`
`99`	`99`	`// createPage is an action passed to createPages`
`100`		`- // See https://www.gatsbyjs.com/docs/actions#createPage for more info`
	`100`	`+ // See https://www.gatsbyjs.com/reference/config-files/actions/#createPage for more info`
`101`	`101`	`await gatsbyUtilities.actions.createPage({`
`102`	`102`	`path: getPagePath(pageNumber),`
`103`	`103`