DOCS: Update log location for "Deploy Plugin" message

diff --git a/server/sonar-docs/src/pages/extend/developing-plugin.md b/server/sonar-docs/src/pages/extend/developing-plugin.md
index 7947a9b575f8ca6c16f2676a9870ae2ad7c72af0..2777a64d19027673e38f1025b9ceab7bdcc3fd5e 100644 (file)
--- a/server/sonar-docs/src/pages/extend/developing-plugin.md
+++ b/server/sonar-docs/src/pages/extend/developing-plugin.md
@@ -64,7 +64,7 @@ The plugin jar file is generated in the project's `target/` directory.
 
 ### Deploy
 **"Cold" Deploy**  
-The standard way to install the plugin for regular users is to copy the JAR artifact, from the `target/` directory  to the `extensions/plugins/` directory of your SonarQube installation then start the server. The file `logs/sonar.log` will then contain a log line similar to:  
+The standard way to install the plugin for regular users is to copy the JAR artifact, from the `target/` directory  to the `extensions/plugins/` directory of your SonarQube installation then start the server. The file `logs/web.log` will then contain a log line similar to:  
 `Deploy plugin Example Plugin / 0.1-SNAPSHOT`  
 Scanner extensions such as sensors are immediately retrieved and loaded when scanning source code.