Terms in user guide can be quite confusing

[LimJiaJing]

UserGuide uses "module name" and "module code" , and "module" ambiguously. At times, "module name" should be more appropriate, but "module code" is used. Attached are some instances where the terms could confuse the user.

In the above two pictures, the command referred i assume it is the same, but the command format given in the UserGuide differs i.e. module name vs module. As a result, i tried to do "add Software Engineering and OOP", took away the space to "add_Software_Enginnering_and_OOP" and hit another error. Until I realised I had to put in a module code instead.

[soc-pe-bot]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Input for add is different between help and UG

---

_{[original: nus-cs2113-AY2122S1/pe-interim#2056] [original labels: severity.Low type.DocumentationBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

Team chose [severity.VeryLow]
Originally [severity.Low]

• I disagree

Reason for disagreement: This is a little confusing to explain. I agree that the bug stems from the same part of the documentation/code, however, the reasoning I gave behind the bug is different. In the case of the other bug report, I agree that its severity is verylow since how they report it makes it like a cosmetic issue. However, the reasoning I gave behind my bug report points towards causing users inconvenience during usage. This bug causes an inconvenience in usage, hence I marked it as severity.low.

---