diff --git a/general/community/plugincontribution/index.md b/general/community/plugincontribution/index.md
index c8d6660547..a9f3a80fa6 100644
--- a/general/community/plugincontribution/index.md
+++ b/general/community/plugincontribution/index.md
@@ -66,8 +66,12 @@ Workflow of contributing a plugin into the Moodle plugins directory ([SVG versio
 
 You are expected to have a system where users can report feature requests, bugs, and other code issues. Following the open source best practise, these reports should be open and public and the associated procedures should be as transparent as possible.
 
+:::info
+
 There are multiple options on where to host the issues tracker. Most plugin developers today prefer to have the issue tracker close to their source code management system - so they use the native issue tracker built into Github, BitBucket or some similar system. It is suggested to use a system that your users are likely to be familiar with.
 
+:::
+
 ## Tutorial
 
 There is a [Tutorial](https://docs.moodle.org/dev/Tutorial) to help you learn how to write plugins for Moodle from start to finish, while showing you how to navigate the most important developer documentation along the way.