Proposed etiquette when reporting documentation errors

Please report errors, omissions, corrections and suggestions for the DM32 User Manual and the built-in Quick Reference Guide.
Post Reply
BruceH
Posts: 82
Joined: Sat May 06, 2017 2:39 am

Proposed etiquette when reporting documentation errors

Post by BruceH »

When reporting a documentation error, please could you put the section that is in error in the subject line.

For example: "Section 1.2.3, typo in example"

And then put the rest of the info about the problem into the body of the post as normal.

The reason for requesting this is to make it easier to spot (and therefore avoid) duplicate reports.
rprosperi
Posts: 1703
Joined: Mon Apr 24, 2017 7:48 pm
Location: New York

Re: Proposed etiquette when reporting documentation errors

Post by rprosperi »

BruceH wrote:
Wed May 24, 2023 11:12 pm
When reporting a documentation error, please could you put the section that is in error in the subject line.

For example: "Section 1.2.3, typo in example"

And then put the rest of the info about the problem into the body of the post as normal.

The reason for requesting this is to make it easier to spot (and therefore avoid) duplicate reports.
Good suggestion! (though I predict it will be widely ignored... <sigh>)
--bob p

DM42: β00071 & 00282, DM41X: β00071 & 00656, DM10L: 071/100
User avatar
Emy
Posts: 103
Joined: Tue May 03, 2022 9:29 am
Location: Switzerland

Re: Proposed etiquette when reporting documentation errors

Post by Emy »

This would help quite a bit indeed. Good suggestion.
Post Reply