Skip to content

Commit

Permalink
Update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
yashpola committed Feb 18, 2024
1 parent 0b4c269 commit 5f73fa2
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Take note that when typing the actual commands,
you should omit any square braces ([ ]) pictured above.

You can find other helpful pointers below for a few of Nicole's commands.
Pay closer attention to the points marked with πŸ“!
Pay closer attention to the points marked with :writing_hand:!

## Adding an item

Expand Down Expand Up @@ -90,7 +90,7 @@ and then accordingly `delete 1` to see a confirmation:
In this particular case since `borrow book` was the only
item, no items remained after deleting it.

πŸ“ If you `mark` an item, its `I` status will change to `C` (meaning `Complete`). Vice versa for `unmark`.
:writing_hand: If you `mark` an item, its `I` status will change to `C` (meaning `Complete`). Vice versa for `unmark`.

## Adding Deadlines and Events

Expand All @@ -99,7 +99,7 @@ Take note!
and `from YYYY:MM:DD at HH:MM:SS to YYYY:MM:DD at HH:MM:SS`
for events are strict!

Potential triggers for errors ❌
Potential triggers for errors :warning:
- For events specifically:
- Adding events that overlap one another in any way
- Specifying a `to...at` datetime for events that precedes the
Expand All @@ -111,7 +111,7 @@ Nicole will indicate to you very clearly if you made
any of the above errors and also guide you
on how to rectify your command, so fret not!

πŸ“ Updating an event could also lead to
:writing_hand: Updating an event could also lead to
problems with clashing events. When in doubt, `list` to
peruse your current items first.

Expand All @@ -122,11 +122,11 @@ of items from earliest to latest as per their date(time) like so:

![sort.png](sortByDateSS.png)

Where events are sorted per their `from` datetime. If an event's
where events are sorted per their `from` datetime. If an event's
`from` date matches the date of a deadline, the event will
take precedence.
take precedence (such as items 2 and 3 above).

πŸ“ Since `todos` do not have a datetime, they are ordered
:writing_hand: Since `todos` do not have a datetime, they are ordered
**last** by default.

## Finally...
Expand Down

0 comments on commit 5f73fa2

Please sign in to comment.