This is plain text without any markdown headers.

It describes the project but doesn't use proper markdown formatting.

There are no section headers to organize the content.

- Guideline 1: keep each change small and explain it in the commit message.
- Guideline 2: keep each change small and explain it in the commit message.
- Guideline 3: keep each change small and explain it in the commit message.
- Guideline 4: keep each change small and explain it in the commit message.
- Guideline 5: keep each change small and explain it in the commit message.
- Guideline 6: keep each change small and explain it in the commit message.
- Guideline 7: keep each change small and explain it in the commit message.
- Guideline 8: keep each change small and explain it in the commit message.
- Guideline 9: keep each change small and explain it in the commit message.
- Guideline 10: keep each change small and explain it in the commit message.
- Guideline 11: keep each change small and explain it in the commit message.
- Guideline 12: keep each change small and explain it in the commit message.
- Guideline 13: keep each change small and explain it in the commit message.
- Guideline 14: keep each change small and explain it in the commit message.
- Guideline 15: keep each change small and explain it in the commit message.
- Guideline 16: keep each change small and explain it in the commit message.
- Guideline 17: keep each change small and explain it in the commit message.
- Guideline 18: keep each change small and explain it in the commit message.
- Guideline 19: keep each change small and explain it in the commit message.
- Guideline 20: keep each change small and explain it in the commit message.
- Guideline 21: keep each change small and explain it in the commit message.
- Guideline 22: keep each change small and explain it in the commit message.
- Guideline 23: keep each change small and explain it in the commit message.
- Guideline 24: keep each change small and explain it in the commit message.
- Guideline 25: keep each change small and explain it in the commit message.
- Guideline 26: keep each change small and explain it in the commit message.
- Guideline 27: keep each change small and explain it in the commit message.
- Guideline 28: keep each change small and explain it in the commit message.
- Guideline 29: keep each change small and explain it in the commit message.
- Guideline 30: keep each change small and explain it in the commit message.
- Guideline 31: keep each change small and explain it in the commit message.
- Guideline 32: keep each change small and explain it in the commit message.
- Guideline 33: keep each change small and explain it in the commit message.
- Guideline 34: keep each change small and explain it in the commit message.
- Guideline 35: keep each change small and explain it in the commit message.
- Guideline 36: keep each change small and explain it in the commit message.
- Guideline 37: keep each change small and explain it in the commit message.
- Guideline 38: keep each change small and explain it in the commit message.
- Guideline 39: keep each change small and explain it in the commit message.
- Guideline 40: keep each change small and explain it in the commit message.
- Guideline 41: keep each change small and explain it in the commit message.
- Guideline 42: keep each change small and explain it in the commit message.
- Guideline 43: keep each change small and explain it in the commit message.
- Guideline 44: keep each change small and explain it in the commit message.
- Guideline 45: keep each change small and explain it in the commit message.
- Guideline 46: keep each change small and explain it in the commit message.
- Guideline 47: keep each change small and explain it in the commit message.
- Guideline 48: keep each change small and explain it in the commit message.
- Guideline 49: keep each change small and explain it in the commit message.
- Guideline 50: keep each change small and explain it in the commit message.