Team's Response

We think this is a not a bug for 2 reasons:

In the module website, there was no requirement to set up a glossary for the user guide, and even the original Addressbook did not have a glossary in the UG.

In our case, the glossary is also not required since there is no term that is specific to our app.

The 'Original' Bug

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

Absence of Glossary in UG

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
Absence of a Glossary in UG to help users read the guide

_{[original: nus-cs2103-AY2122S2/pe-interim#2451] [original labels: severity.Medium type.DocumentationBug]}

Their Response to the 'Original' Bug

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

We think this is a not a bug for 2 reasons:

In the module website, there was no requirement to set up a glossary for the user guide, and even the original Addressbook did not have a glossary in the UG.

In our case, the glossary is also not required since there is no term that is specific to our app.

Items for the Tester to Verify

:question: 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]

:question: Issue response

Team chose [response.Rejected]

[x] I disagree

Reason for disagreement:

In the section of possible UG bugs, "The information is hard to understand for the target audience. e.g., using terms the reader might not know", some terms such as CLI and GUI in the user guide are hard to understand for the target audience, recruiters in a company who might not have knowledge of such technical terms. Therefore, a glossary would help to explain these terms to the target audience.

:question: Issue severity

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

[ ] I disagree