From 8a69c0555bf38f20987a635827efc45eb5d42bf1 Mon Sep 17 00:00:00 2001
From: PrinsFrank <25006490+PrinsFrank@users.noreply.github.com>
Date: Tue, 6 Feb 2024 12:57:34 +0100
Subject: [PATCH] Update plugin documentation (#11813)

---
 doc/articles/plugins.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/articles/plugins.md b/doc/articles/plugins.md
index 019ab5d45..6c729a4e0 100644
--- a/doc/articles/plugins.md
+++ b/doc/articles/plugins.md
@@ -271,6 +271,8 @@ class Command extends BaseCommand
     protected function execute(InputInterface $input, OutputInterface $output): int
     {
         $output->writeln('Executing');
+
+        return 0;
     }
 }
 ```
@@ -285,7 +287,7 @@ Plugins for an event can be run manually by the `run-script` command. This works
 [running scripts manually](scripts.md#running-scripts-manually).
 
 If it is another type of plugin the best way to test it is probably using a [path repository](../05-repositories.md#path)
-to require the plugin in a test project, and then `rm -rf vendor && composer update`
+to require the plugin in a test project. If you are developing locally and want to test frequently, you can make sure the path repository uses symlinks, as changes are updated immediately. Otherwise, you'll have to run `rm -rf vendor && composer update`
 every time you want to install/run it again.
 
 ## Using Plugins