diff --git a/docs/hashcat-plugin-development-guide.md b/docs/hashcat-plugin-development-guide.md
index 2e85fa214..77bd92e33 100644
--- a/docs/hashcat-plugin-development-guide.md
+++ b/docs/hashcat-plugin-development-guide.md
@@ -537,20 +537,24 @@ Additionally there is a couple of command line parameters that you want to use:
 * -d 1: In case you have multi compute devices in your system, limit it to a single compute device. This is to reduce startup and JiT compile time.
 
 Typically a developer command line for hashcat looks the following:
+
 ```
 $ rm -rf kernels $HOME/.nv; ./hashcat -m XXXXX hash.txt word.txt --potfile-disable --self-test-disable -n 1 -u 1 -T 1 --quiet --backend-vector-width 1 -d 1 --force
 ```
 
-If you need to printf from without a _loop kernel, keep in mind that you need to add a branching manually for a specific loop position.
+When adding print statements keep in mind that you need to manually add a conditional to branch on a specific loop position, otherwise every parallel execution of the kernel will execute the printf(), flooding your terminal. So you can use either:
+
 ```
 if ((loop_pos + i) == 0) printf ("%08x\n", a);
 ```
 
-When using  -n 1 -u 1 -T 1 you shouldn't add
+from a _loop kernel, or
+
 ```
-if((gid==1) && (lid==1)) {
+if ((gid == 0) && (lid == 0)) printf ("%08x\n", a);
 ```
-to your kernel, as there will be only one kernel thread, there's no gid==1 (only gid==0) so your code won't be executed.
+
+from a kernel without _loop.
 
 Some last recommendations about printf() itself. Printing a string %s is not recommended. Missing zero bytes or big endian byte order can be very confusing. Instead try to use only the %08x template for everything. Especially for strings this makes a lot of sense, if for example you want to find unexpected non zero bytes. This can be done by calling printf() multiple times. Get used to this and it will simplify a lot of things for you.