developer guide could benefit from consistent formatting of numbered points.

[nus-se-script]

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.

---

The numbering for Non-Functional Requirements goes from 1. to a circled bullet point. while the numbering for the next section goes from 1. to i.

---

_{[original: nus-cs2113-AY2324S2/pe-interim#1048] [original labels: type.DocumentationBug severity.VeryLow]}

[tayponghee]

Team's Response

Duplicate as the bug refers to formatting of bullet points at the section level of the DG, which is the same as 983.

We are unsure what the problem is with our style of formatting the bullet points. We are also not sure of what consistent formatting the points mean, let alone what benefit it would bring. Do you mean the hierarchy of the bullet points within each sections, or syncing hierarchies between all chapters?

Regardless, as per current formatting of instructions for manual testing, the type of bullet point used does not seem to hinder the user's ability to understand the section at all. Bullet point formatting is only cosmetic, and whether it is a cosmetic problem is questionable.

Duplicate status (if any):

Duplicate of #983