the `add savings` + `add split expense` section in manual testing of DG is incorrect format

[nidhi-nayak]

in the DG, the manual testing for Adding Savings and Add Split Expenses lacks the specific test cases to use. While it describes the input, it does not define a specific test case for manual testers to use. This could be problematic for developers.

[nus-se-script]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

The identified documentation bug, while noting an absence of an exact command format in the manual, should still be classified as low severity due to several key factors. First, the documentation does provide sufficient information on what inputs are to be entered, even if it does not detail the exact command syntax. This guidance, albeit not exhaustive, equips users with enough context to make informed input choices that align with the required parameters. This is less severe since the exact syntax is provided in the user guide.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your reason]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]

---