Fix broken links in contributors readme files (#32272)

gutenberg.php

@@ -39,7 +39,7 @@ function gutenberg_wordpress_version_notice() {
  */
 function gutenberg_build_files_notice() {
 	echo '<div class="error"><p>';
-	_e( 'Gutenberg development mode requires files to be built. Run <code>npm install</code> to install dependencies, <code>npm run build</code> to build the files or <code>npm run dev</code> to build the files and watch for changes. Read the <a href="https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/getting-started.md">contributing</a> file for more information.', 'gutenberg' );
+	_e( 'Gutenberg development mode requires files to be built. Run <code>npm install</code> to install dependencies, <code>npm run build</code> to build the files or <code>npm run dev</code> to build the files and watch for changes. Read the <a href="https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/getting-started-with-code-contribution.md">contributing</a> file for more information.', 'gutenberg' );
 	echo '</p></div>';
 }
 

packages/eslint-plugin/docs/rules/dependency-group.md

@@ -1,6 +1,6 @@
 # Enforce dependencies docblocks formatting (dependency-group)
 
-Ensures that all top-level package imports adhere to the dependencies grouping conventions as outlined in the [Coding Guidelines](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/coding-guidelines.md#imports).
+Ensures that all top-level package imports adhere to the dependencies grouping conventions as outlined in the [Coding Guidelines](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/coding-guidelines.md#imports).
 
 Specifically, this ensures that:
 

packages/eslint-plugin/docs/rules/no-unsafe-wp-apis.md

@@ -3,7 +3,7 @@
 Prevent unsafe APIs from `@wordpress/*` packages from being imported.
 
 This includes experimental and unstable APIs which are expected to change and likely to cause issues in application code.
-See the [documentation](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/coding-guidelines.md#experimental-and-unstable-apis).
+See the [documentation](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/coding-guidelines.md#experimental-and-unstable-apis).
 
 > **There is no support commitment for experimental and unstable APIs.** They can and will be removed or changed without advance warning, including as part of a minor or patch release. As an external consumer, you should avoid these APIs.
 > …

packages/project-management-automation/lib/tasks/add-milestone/README.md

@@ -8,4 +8,4 @@ Creates the milestone if it does not yet exist.
 
 If a pull request is merged, it can be difficult to know which upcoming or past plugin version that change would be included within. This is useful for debugging if a change should be expected to be available for testing, and to know if a change should be anticipated to be released within an upcoming release of the plugin.
 
-It is also used in automation associated with [release changelogs](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/release.md#writing-the-release-post-and-changelog), which aggregate pull requests based on the assigned milestone.
+It is also used in automation associated with [release changelogs](https://github.com/WordPress/gutenberg/blob/HEAD/docs/contributors/code/release.md#writing-the-release-notes-and-post), which aggregate pull requests based on the assigned milestone.