stop linking to 1.x specific Gradle page

topics/appendix/resources/explore_api.md

@@ -91,7 +91,7 @@ source code, as well as other basic features of IntelliJ IDEA.
 Many developers keep the
 [IntelliJ Community source code](https://github.com/JetBrains/intellij-community)
 open in a separate IDE project while working on their plugin.
-Others search the source code of the IntelliJ Platform that is attached by default when using a [Gradle](configuring_plugin_project.md)-based project.
+Others search the source code of the IntelliJ Platform that is attached by default when using a [Gradle](creating_plugin_project.md)-based project.
 While both methods work, it should be noted that developing plugins without inspecting the IntelliJ Platform code is nearly impossible,
 and all the tips below assume having the sources available.
 

topics/appendix/verifying_plugin_compatibility.md

@@ -14,7 +14,7 @@ See also [](build_number_ranges.md#multipleIDEVersions).
 
 ### Using with Gradle
 
-Integration in [Gradle build](configuring_plugin_project.md) is available out-of-the box via dedicated Gradle tasks.
+Integration in [Gradle build](creating_plugin_project.md) is available out-of-the box via dedicated Gradle tasks.
 
 <tabs>
 <tab title="IntelliJ Platform Gradle Plugin (2.x)">

topics/basics/getting_started/plugin/developing_plugins.md

@@ -45,7 +45,9 @@ A dedicated [SBT plugin](https://github.com/JetBrains/sbt-idea-plugin) is availa
 
 ## Plugin Development Workflow
 
-* [Creating a Gradle-based Plugin Project](creating_plugin_project.md)
-* [Configuring the Gradle IntelliJ Plugin](configuring_plugin_project.md)
-  * [Adding Kotlin Support](using_kotlin.md)
-* [Publishing a Plugin](publishing_plugin.md)
+* [](creating_plugin_project.md)
+  * [](plugin_github_template.md)
+* [](configuring_plugin_project.md)
+* [](using_kotlin.md)
+* [](plugin_signing.md)
+* [](publishing_plugin.md)

topics/basics/getting_started/publishing_plugin.md

@@ -58,7 +58,7 @@ See [](#deploying-a-plugin-with-gradle) on how to publish new versions using Gra
 
 ## Publishing Plugin With Gradle
 
-Once [Gradle support](configuring_plugin_project.md) has been configured, and the plugin has been [uploaded manually](#uploading-a-plugin-to-jetbrains-marketplace) to the plugin repository at least once,
+Once [Gradle support](creating_plugin_project.md) has been configured, and the plugin has been [uploaded manually](#uploading-a-plugin-to-jetbrains-marketplace) to the plugin repository at least once,
 it can be built and deployed to the [JetBrains Marketplace](https://plugins.jetbrains.com) automatically using dedicated Gradle tasks.
 
 > **2.x** refers to [](tools_intellij_platform_gradle_plugin.md) and **1.x** to [](tools_gradle_intellij_plugin.md) in the following sections.

topics/basics/plugin_structure/dynamic_plugins.md

@@ -106,7 +106,7 @@ If a plugin fails to reload, the log will contain a cause as to why.
 
 <procedure title="Finding leaks preventing unload">
 
-1. Verify that the IDE is running with the VM parameter `-XX:+UnlockDiagnosticVMOptions`. When using [Gradle](configuring_plugin_project.md), specify `runIde.jvmArgs += "-XX:+UnlockDiagnosticVMOptions"` otherwise [Configure JVM Options](https://www.jetbrains.com/help/idea/tuning-the-ide.html#procedure-jvm-options).
+1. Verify that the IDE is running with the VM parameter `-XX:+UnlockDiagnosticVMOptions`. When using [Gradle](creating_plugin_project.md), specify `runIde.jvmArgs += "-XX:+UnlockDiagnosticVMOptions"` otherwise [Configure JVM Options](https://www.jetbrains.com/help/idea/tuning-the-ide.html#procedure-jvm-options).
 2. Set Registry key `ide.plugins.snapshot.on.unload.fail` to `true` (Go to <ui-path>Navigate | Search Everywhere</ui-path> and type `Registry`).
 3. Trigger the plugin reload.
 4. Open the <path>.hprof</path> memory snapshot generated in the user home directory on plugin unloading, look for the plugin ID string. [IntelliJ Ultimate](https://www.jetbrains.com/help/idea/analyze-hprof-memory-snapshots.html) can open memory snapshots directly.

topics/products/idea/spring_api.md

@@ -16,7 +16,7 @@ To develop plugins, you will need to use _IntelliJ IDEA Ultimate Edition_ versio
 
 ## Setting up Project
 
-Setup [Gradle build script](configuring_plugin_project.md#intellij-platform-configuration) to target IntelliJ IDEA Ultimate, then [add dependency](plugin_dependencies.md) to bundled Spring plugin with ID `com.intellij.spring`.
+Setup [Gradle](creating_plugin_project.md) to target IntelliJ IDEA Ultimate, then [add dependency](plugin_dependencies.md) to bundled Spring plugin with ID `com.intellij.spring`.
 
 Please use only Spring-related functionality exposed in <path>spring-api.jar</path> (sources are provided in <path>\$IDEA_HOME\$/lib/src/src_spring-boot-openapi.zip</path>) in your plugin.
 Using any other "internal" (implementation) classes from Spring plugin itself (<path>spring.jar</path>) is _not_ supported.

topics/products/rider/rider.md

@@ -17,7 +17,7 @@ Rider uses the IntelliJ Platform to provide the user interface for a C# and .NET
 ## IntelliJ IDEA Configuration for Rider Plugin Development
 
 Although there is no dedicated Rider SDK, the [ReSharper DevGuide](https://www.jetbrains.com/help/resharper/sdk/getting_started.html) addresses the subject of plugins for Rider.
-The documentation describes the [configuration](https://www.jetbrains.com/help/resharper/sdk/creating_plugin.html) of the Gradle build script and <path>settings.gradle</path> file to build a Rider plugin using the [Gradle project system](configuring_plugin_project.md) in IntelliJ IDEA.
+The documentation describes the [configuration](https://www.jetbrains.com/help/resharper/sdk/creating_plugin.html) of the Gradle build script and <path>settings.gradle</path> file to build a Rider plugin using the [Gradle build system](creating_plugin_project.md) in IntelliJ IDEA.
 
 > See [](rider_extension_point_list.md) for the complete list.
 >