# Minor change to examples in Doxygen comments

**URL:** <https://www.rubin.community/t/minor-change-to-examples-in-doxygen-comments/1752>\
**Category:** DM Notifications\
**Tags:** doc-engineering\
**Created:** [March 29, 2017, 11:53pm UTC](https://www.rubin.community/t/minor-change-to-examples-in-doxygen-comments/1752 "2017-03-29T23:53:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kfindeisen](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/kfindeisen/32/833_2.png) [@kfindeisen](https://www.rubin.community/u/kfindeisen)\
**Post date:** [March 29, 2017, 11:53pm UTC](https://www.rubin.community/t/minor-change-to-examples-in-doxygen-comments/1752/1 "2017-03-29T23:53:04Z")

</div>

The C++ documentation style guide, as published a month ago, had a minor mistake: it recommended that examples be delimited by `@code` Doxygen tags. This ran counter to the long-standing (\> 2 years) rule that Doxygen comments should use Markdown for formatting.

The guide has now been corrected, and requests that code blocks be delimited by four extra spaces compared to the surrounding text.