use "JetBrains Marketplace" everywhere

reference_guide/api_changes_list.md

@@ -67,7 +67,7 @@ IntelliJ API may be occasionally changed between releases, leading to existing p
 ## Verifying Compatibility
 
 ### Plugin Verifier
-Compatibility with newer IDEs can easily be verified for plugins hosted on the [JetBrains Plugins Repository](https://plugins.jetbrains.com) using the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/).
+Compatibility with newer IDEs can easily be verified for plugins hosted on the [JetBrains Marketplace](https://plugins.jetbrains.com) using the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/).
 
 For local verification or non-public plugins, [intellij-plugin-verifier](https://github.com/JetBrains/intellij-plugin-verifier) can be used standalone as well.
 

topics/appendix/api_notable/api_notable_list_2019.md

@@ -28,7 +28,7 @@ User-customizable date/time formatting
 
 Unbundled plugins
 : Several plugins (Heroku integration, RubyMotion support, Java Applets Support) for no longer actively maintained technology have been moved to a [separate repository](https://github.com/JetBrains/intellij-obsolete-plugins/).
-If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).
 
 ## 2019.2
 
@@ -79,7 +79,7 @@ Java functionality extracted as a plugin
 : If your plugin depends on Java, it must be specified now; please see [blog post](https://blog.jetbrains.com/platform/2019/06/java-functionality-extracted-as-a-plugin/) for details.
 
 Unbundled plugins
-: Several plugins (J2ME, JsTestDriver, Struts 1.x) for no longer actively maintained technology have been moved to a [separate repository](https://github.com/JetBrains/intellij-obsolete-plugins/). If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+: Several plugins (J2ME, JsTestDriver, Struts 1.x) for no longer actively maintained technology have been moved to a [separate repository](https://github.com/JetBrains/intellij-obsolete-plugins/). If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).
 
 ## 2019.1
 

topics/appendix/api_notable/api_notable_list_2020.md

@@ -96,7 +96,7 @@ Validating Lexer for editor highlighting
 ### IntelliJ IDEA 2020.2
 
 Unbundled plugins
-: Several plugins (ASP, CFML, Flash/Flex, GWT, JBoss Seam Pageflow, JBoss Seam, JBoss jBPM, OSGi, Play Framework, Resin, Seam Navigation, Tapestry, Virgo/dmServer) for no longer actively maintained technology have been unbundled. If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+: Several plugins (ASP, CFML, Flash/Flex, GWT, JBoss Seam Pageflow, JBoss Seam, JBoss jBPM, OSGi, Play Framework, Resin, Seam Navigation, Tapestry, Virgo/dmServer) for no longer actively maintained technology have been unbundled. If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).
 
 ## 2020.1
 
@@ -136,4 +136,4 @@ EOL for JetBrains TFS Plugin
 : Please use [Azure DevOps](https://plugins.jetbrains.com/plugin/7981-azure-devops) plugin instead, see [blog post](https://blog.jetbrains.com/idea/2020/01/end-of-support-for-tfs-2014-and-older/) for more details.
 
 Unbundled plugins
-: Several plugins (Cloud Foundry, Google App Engine) for no longer actively maintained technology have been unbundled. If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+: Several plugins (Cloud Foundry, Google App Engine) for no longer actively maintained technology have been unbundled. If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).

topics/appendix/api_notable/api_notable_list_2021.md

@@ -33,7 +33,7 @@ Language Injection
 ### IntelliJ IDEA 2021.2
 
 Unbundled plugins
-: Several plugins (Arquillian, AspectJ, CoffeeScript, Debugger Support for JSP (JSR45), Drools, Guice, Helidon, Java EE: Enterprise Java Beans (EJB), Spring OSGi, Spring Web Flow) have been unbundled. The IDE will suggest installation if the project contains related framework dependency. If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+: Several plugins (Arquillian, AspectJ, CoffeeScript, Debugger Support for JSP (JSR45), Drools, Guice, Helidon, Java EE: Enterprise Java Beans (EJB), Spring OSGi, Spring Web Flow) have been unbundled. The IDE will suggest installation if the project contains related framework dependency. If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).
 
 ## 2021.1
 

topics/appendix/api_notable/api_notable_list_2022.md

@@ -14,7 +14,7 @@ External System Test Framework
 ### IntelliJ IDEA 2021.2
 
 Unbundled plugins
-: Several plugins (Grails, Jakarta EE: Batch Applications, Jakarta EE: Server Faces (JSF), Jakarta EE: Web Services (JAX-WS), Smali Support, Spring Batch, Spring Integration Patterns, Spring Web Services) have been unbundled. The IDE will suggest installation if the project contains related framework dependency. If your plugin depends on them, users will need to install them from the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+: Several plugins (Grails, Jakarta EE: Batch Applications, Jakarta EE: Server Faces (JSF), Jakarta EE: Web Services (JAX-WS), Smali Support, Spring Batch, Spring Integration Patterns, Spring Web Services) have been unbundled. The IDE will suggest installation if the project contains related framework dependency. If your plugin depends on them, users will need to install them from the [JetBrains Marketplace](https://plugins.jetbrains.com).
 
 ### Maven Plugin 2022.1
 

topics/basics/getting_started/build_number_ranges.md

@@ -7,7 +7,7 @@ Setting the actual values in <path>plugin.xml</path> is usually managed by `patc
 
  > Compatibility with the specified version range (and compatible products) must always be verified using [Plugin Verifier](api_changes_list.md#verifying-compatibility) to ensure binary compatibility.
  >
- > Plugins hosted on [JetBrains Plugins Repository](https://plugins.jetbrains.com) are checked automatically. According to [Approval Guidelines](https://plugins.jetbrains.com/legal/approval-guidelines), incompatible plugin versions will be restricted by JetBrains if necessary.
+ > Plugins hosted on [JetBrains Marketplace](https://plugins.jetbrains.com) are checked automatically. According to [Approval Guidelines](https://plugins.jetbrains.com/legal/approval-guidelines), incompatible plugin versions will be restricted by JetBrains if necessary.
  >
  {type="warning"}
 

topics/basics/plugin_structure/dynamic_plugins.md

@@ -18,7 +18,7 @@ Please note that any unloading problems in a production environment will simply
 For a plugin to support this, all restrictions listed below must be met.
 To verify a plugin locally, invoke <menupath>Code | Analyze Code | Run Inspection by Name...</menupath> and run <control>Plugin DevKit | Plugin descriptor | Plugin.xml dynamic plugin verification inspection</control> inspection on all plugin descriptor files.
 
-For plugins hosted on the [JetBrains Plugins Repository](https://plugins.jetbrains.com) the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/) will run these checks automatically.
+For plugins hosted on the [JetBrains Marketplace](https://plugins.jetbrains.com) the built-in [Plugin Verifier](https://blog.jetbrains.com/platform/2018/07/plugins-repository-now-integrates-with-the-plugin-verification-tool/) will run these checks automatically.
 See [Plugin Verifier](api_changes_list.md#plugin-verifier) for more information on how to run it locally or on CI.
 
 ### No Use of Components

topics/basics/plugin_structure/plugin_dependencies.md

@@ -25,7 +25,7 @@ If `NoClassDefFoundError` occurs at runtime, it means that either Step 3 was omi
 ## 1. Locating Plugin ID and Preparing Sandbox
 A compatible version must be chosen carefully according to the plugin's [compatibility](build_number_ranges.md).
 
-For plugins published on [JetBrains Plugins Repository](https://plugins.jetbrains.com)
+For plugins published on [JetBrains Marketplace](https://plugins.jetbrains.com)
 - open plugin's detail page
 - select <control>Versions</control> tab
 - open detail page for the desired version, displaying the <control>Compatibility Range</control> and <control>Plugin ID</control>

topics/basics/plugin_structure/plugin_icon_file.md

@@ -10,7 +10,7 @@ Previously this page referred to Plugin Logos as _Plugin Icons_.
 See [Working with Icons and Images](work_with_icons_and_images.md) for more information.
 
 ## Introduction
-Plugin Logos are shown in the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+Plugin Logos are shown in the [JetBrains Marketplace](https://plugins.jetbrains.com).
 They also appear in the Settings/Preferences [Plugin Manager](https://www.jetbrains.com/help/idea/managing-plugins.html) UI in IntelliJ Platform-based IDEs.
 Whether online or in the product UI, a Plugin Logo helps users to identify a plugin more quickly in a list, as shown below:
 

topics/tutorials/build_system/deployment.md

@@ -2,7 +2,7 @@
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
-Once you have [configured Gradle support](gradle_guide.md), you can automatically build and deploy your plugin to the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+Once you have [configured Gradle support](gradle_guide.md), you can automatically build and deploy your plugin to the [JetBrains Marketplace](https://plugins.jetbrains.com).
 To automatically deploy a plugin, you need to have _already published the plugin to the plugin repository at least once._
 Please see the guide page for manually [publishing a plugin](publishing_plugin.md) for the first time and [Building Distribution](#building-distribution) on obtaining the initial plugin distribution artifact.
 

topics/tutorials/gradle_build_system.md

@@ -4,7 +4,7 @@
 
 The [gradle-intellij-plugin](https://github.com/JetBrains/gradle-intellij-plugin) Gradle plugin is the recommended solution for building IntelliJ Platform plugins.
 The plugin takes care of the dependencies of your plugin project - both the base IDE and other plugin dependencies.
-It provides tasks to run the IDE with your plugin and to package and publish your plugin to the [JetBrains Plugins Repository](https://plugins.jetbrains.com).
+It provides tasks to run the IDE with your plugin and to package and publish your plugin to the [JetBrains Marketplace](https://plugins.jetbrains.com).
 To make sure that a plugin is not affected by [API changes](api_changes_list.md), which may happen between major releases of the platform, you can quickly verify your plugin against other IDEs and releases.
 
  >  [IntelliJ Platform Plugin Template](github_template.md) makes it easier to create and maintain your IDE plugins, having the Gradle plugin already integrated and CI covered with GitHub Actions.