### Man Page Sections
1. User Commands
- Programs supplied by GNU C library
- git
- htop
2. System Calls
- System calls provided by Linux kernel
- write
- read
3. Library Functions
- Standard C library functions
- pthread_create
- rand
4. Devices
- Devices in /dev and other places
- loop
- zero
- sd
5. Files
- File formats and processes
- resolv.conf
- passwd
7. Miscellaneous
- UTF-8
- cgroups
- daemon

### How to Read a Man Page
- Command, section number, implementation (Linux Programmers Manual vs POSIX Programmers Manual)
- Synopsis
- Many (all) options
- Can be read literally or as an example
- Description
- Technical details, brief explanation and history, program associations
- Commands
- How to interface with application
- In the case of `less`, you are given navigation instructions
- Options
- Arguments or flags
- Some documentation (sed) will use "Commands" and "Description" for technical usage
- Additional Information
- Environment Variables
- Application specific commands or arguments (not POSIX or Linux, such as git)
- Technical documentation such as security concerns, additional interfaces, and use cases
- "EXAMPLES" sometimes included in this area
- Author or Organization information
- See Also

### Things to Lookout For
- Look for underlines or italics (underlines are not literal, but implications)
- Learn to navigate and search
- /
- h, j, k, l
- n, b
- Ctrl f, Ctrl b
- gg and G
- A and 0
- b/e, W/E
- q

### Resources
- https://explainshell.com/
- https://stackoverflow.com/questions
- https://unix.stackexchange.com/
- https://www.reddit.com/r/bash/
- https://nostarch.com/absfreebsd3
- https://codingblocks.slack.com/ (go to their main page to join)