Fix typos and minor errors in documentation and comments

[HusseinAdeiza]

While reviewing the repository, I noticed several typos and minor errors in the documentation and code comments. Correcting these will improve the clarity and professionalism of the project.

Suggested Actions:

• Review the documentation (README, guides, etc.) for spelling mistakes and grammatical errors.
• Check code comments and inline documentation for typos or unclear language.
• Update the affected files with corrections for better readability and understanding.

Making these changes will help users and contributors better understand and utilize the project.

[HusseinAdeiza]

Issue: Point out and Fix Typos, Grammar, and Clarity Issues in Documentation and Comments

Problem

While reviewing the repository, I found several typos, inconsistent terms, minor grammar errors, and unclear or inconsistent phrasing in the documentation and code comments. Addressing these will improve the clarity and professionalism of the project.

---

Examples of Issues

1. README.md

a. Consistency in Option Names

• Both --tier normal and --tier ultra are used. Make sure these are consistent and documented in one place.
• Example placeholders: pipe referral apply USERNAME-XXXX vs. pipe referral apply CODE-1234 (pick one style).

b. Grammar and Phrasing

• "Pipe-cli now supports intelligent directory synchronization with metadata tracking:"
  Suggestion: Remove colon at end.
• "Check upload cost before uploading (NEW!)"
  Suggestion: "Check upload cost before uploading."
• "Directory Download Features" vs. "Directory Downloads (NEW!)" — use consistent section headers.

c. Clarity and Minor Typos

• "Your data is encrypted before leaving your device"
  Suggestion: "Your data is encrypted before it leaves your device."
• "Decrypt files during download"
  Suggestion: "Decrypt files automatically during download."
• "No manual base64 decoding is needed"
  Suggestion: "Manual base64 decoding is not required."

d. Formatting

• Some code blocks (JSON examples) may be missing closing code fences.
• Some lines have extra trailing whitespace.

---

2. Code Comments

a. Redundant or Unclear Phrases

• // Test with tokio runtime
  Suggestion: "Test with Tokio runtime."
• "Should skip malformed entries"
  Suggestion: "Skips malformed entries."

b. Comment Consistency

• Some comments start with capital letters and end with periods; others do not. Choose one style and apply throughout.

---

3. Spelling

• "Deduplication detection" is correct, but sometimes "deduplication" may be misspelled (check all instances).
• "Kyber-1024 (ML-KEM)" and "Dilithium5 (ML-DSA)" — use consistent spacing: ("Dilithium 5" or "Dilithium5").
• "Keyring" vs. "keyring" — use consistent capitalization.

---

4. Miscellaneous

• "Upload shows the Blake3 hash"
  Suggestion: "The upload command displays the Blake3 hash."
• "Legacy mode: If you see warnings about 'legacy keyring', your keys are still using the old hardcoded password keyring-protection."
  Suggestion: "Legacy mode: If you see warnings about the 'legacy keyring', your keys are still using the old, hardcoded password: keyring-protection."

---

Suggested Actions

• Review documentation and code comments for these and similar issues.
• Apply corrections for clarity, grammar, and consistency.
• Update affected files to improve readability.

---

Addressing these changes will make the project more welcoming and easier to understand for users and contributors.