Format improvement: highlight text

Co-authored-by: Sara Arjona <[email protected]>

general/community/plugincontribution/index.md

@@ -60,7 +60,7 @@ Workflow of contributing a plugin into the Moodle plugins directory ([SVG versio
 - You are supposed to publish and share your plugin code so that others can clone it easily and eventually contribute patches for it easily.
 - [Github](https://github.com/) is a popular choice of many Moodle developers these days.
 - The layout should be that the root of the repository is the root of the plugin folder. In other words, in the root of your repository there should be files like version.php and folders like lang or classes. That way, your plugin can be directly cloned (checked out) into existing Moodle installation without conflicting with other contributed plugins of the same type, also obtained via Git.
-- It is suggested to follow the common naming convention of Moodle related repositories: moodle-{plugintype}_{pluginname}. For example, the birthday block has a repository name of moodle-block_birthday and is located at https://github.com/arborrow/moodle-block_birthday. Other developers can fork the code and work from their repositories.
+- It is suggested to follow the common naming convention of Moodle related repositories: moodle-`{plugintype}_{pluginname}`. For example, the birthday block has a repository name of `moodle-block_birthday` and is located at https://github.com/arborrow/moodle-block_birthday. Other developers can fork the code and work from their repositories.
 
 ### Tracker