change formatting

input examples are now given as

```bash
input $ARG1
```

While outputs use md's '> ' sign as a quote.

data/taskwarrior/task.md

@@ -5,95 +5,137 @@ tags: [ "Documentation", "Organization" ]
 
 Set up the configuration file:
 
-> task
+```bash
+task
+```
 
 Add a task:
 
-> task add *update linux*
+```bash
+task add update linux
+```
 
 See which task is next:
 
-> task next
+```bash
+task next
+```
 
 Note the id number.
 
 Mark a task as started:
 
-> task start *1*
+```bash
+task start 1
+```
 
 Once finished:
 
-> task *1 done*
+```bash
+task 1 done
+```
 
 # Projects
 
 Add a project:
 
-> task add project:*house buy potted plant*
-> task add proj:*house.repair buy screwdriver*
-> task add proj:*house.repair buy shelf brackets*
-3 task add pro:*house.paint buy white paint*
-> task add pro:*house.paint buy red paint*
-> task add pro:*house.paint buy black paint*
-> task add pro:*house.paint buy brushes*
+```bash
+task add project:house buy potted plant
+task add proj:house.repair buy screwdriver
+task add proj:house.repair buy shelf brackets
+task add pro:house.paint buy white paint
+task add pro:house.paint buy red paint
+task add pro:house.paint buy black paint
+task add pro:house.paint buy brushes
+```
 
 ## Summary
 
-> task pro:house sum
+```bash
+task pro:house sum
+```
 
-> task burndown.daily pro:house
+```bash
+task burndown.daily pro:house
+```
 
 The summaries will show how fast a project is being completed, and when you can expect it to finish at the present rate.
 
 # Tags
 
-> task add +buy toothbrush
+```bash
+task add +buy toothbrush
+```
 
 You can then see only tasks which involve buying something with:
 
-> task +buy
+```bash
+task +buy
+```
 
 # Contexts
 
 Set three contexts by their tags:
 
-> task context define *work +sa or +hr*
+```bash
+task context define work +sa or +hr
+```
 
-> task context define *study +ed or +void or +rat*
+```bash
+task context define study +ed or +void or +rat
+```
 
-> task context define *home -sa -hr -ed -void -rat*
+```bash
+task context define home -sa -hr -ed -void -rat
+```
 
 Change to the first context.
 
-> task context *work*
+```bash
+task context work
+```
 
 Then stop.
 
-> task context none
+```bash
+task context none
+```
 
 # Review
 
 View list of tasks completed in the last week:
 
-> task end.after:today-1wk completed
+```bash
+task end.after:today-1wk completed
+```
 
 # User Defined Attributes
 
 Make a UDA 'size'.
 
-> task config uda.size.type string
+```bash
+task config uda.size.type string
+```
 
-> task config uda.size.label Size
+```bash
+task config uda.size.label Size
+```
 
-> task config uda.size.values large,medium,small
+```bash
+task config uda.size.values large,medium,small
+```
 
-> uda.size.default=medium
+```bash
+uda.size.default=medium
+```
 
 # Tricks
 
 This command shows tasks I'm most interested in:
 
-> task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H
+```bash
+task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H
+```
 
 The command is long, so `alias` is your friend.
 

data/taskwarrior/timew.md

@@ -6,76 +6,88 @@ tags: [ "Documentation", "Data" ]
 
 Try:
 
-> timew summary :yesterday
+```bash
+timew summary :yesterday
+```
 
 You can also use :week, :lastweek, :month, :quarter, :year, or a range such as:
 
-> timew summary today to tomorrow
-
-> timew today - tomorrow
-
-> 2018-10-15T06:00 - 2018-10-17T06:00
+```bash
+timew summary today to tomorrow
+timew today - tomorrow
+2018-10-15T06:00 - 2018-10-17T06:00
+```
 
 Each of these can gain with the :ids tag.
 
 # Basics
 
-> timew start
-
-> timew stop
-
-> timew continue
-
-> timew summary
-
-> timew tags
+```bash
+timew start
+timew stop
+timew continue
+timew summary
+timew tags
+```
 
 And add ids with:
 
-> timew summary :ids
-
-
-> timew track 10am - 1pm timewarrior
-
-> timew track 1pm for 2h walk
+```bash
+timew summary :ids
+timew track 10am - 1pm timewarrior
+timew track 1pm for 2h walk
+```
 
 # Adjusting Timewarrior
 
 First get ids.
 
-> timew summary :ids
+```bash
+timew summary :ids
+```
 
 Then if we're looking at task @2:
 
-> timew move @2 12:00
+```bash
+timew move @2 12:00
+timew lengthen @2 3mins
+```
 
-> timew lengthen @2 3mins
-
-> time shorten @2 40mins
+```bash
+time shorten @2 40mins
+```
 
 # Forgetting
 
-> timew start 1h ago @4
+```bash
+timew start 1h ago @4
+```
 
 Or if your action actually had a break:
 
-> timew split @8
+```bash
+timew split @8
+```
 
 Or maybe not?
 
-> timew join @4 @8
-
-> timew @8 delete
+```bash
+timew join @4 @8
+timew @8 delete
+```
 
 Start at previous time
 
-> timew start 3pm 'Read chapter 12'
-
-> timew start 90mins ago 'Read chapter 12'
+```bash
+timew start 3pm 'Read chapter 12'
+timew start 90mins ago 'Read chapter 12'
+```
 
 Cancel currently tracked time.
 
-> timew cancel
+```bash
+timew cancel
+```
 
 # Backdated tracking
 
@@ -129,25 +141,29 @@ task end.after:today-1wk completed
 
 Replace 
 
-`os.system('timew start ' + combined + ' :yes')`
+> os.system('timew start ' + combined + ' :yes')
 
 with:
 
-`os.system('timew start ' + combined.decode() + ' :yes')`
+> os.system('timew start ' + combined.decode() + ' :yes')
 
 and 
 
-`os.system('timew stop ' + combined + ' :yes')`
+> os.system('timew stop ' + combined + ' :yes')
 
 with:
 
-`os.system('timew stop ' + combined.decode() + ' :yes')`
+> os.system('timew stop ' + combined.decode() + ' :yes')
 
 # Fixing Errors
 
-> curl -O https://taskwarrior.org/download/timew-dbcorrection.py
+```bash
+curl -O https://taskwarrior.org/download/timew-dbcorrection.py
+```
 
-> python timew-dbcorrections.py
+```bash
+python timew-dbcorrections.py
+```
 
 # Setup