docs: clarify retry behavior

[picunada]

Added explanation in which cases retry occur.

🔗 Linked issue

Issue #263 .

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Added an explanation in which cases retries occurs to avoid confusion.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

thanks :100

[codecov]

Codecov Report

Merging #264 (c5f9810) into main (41c3b56) will not change coverage.
Report is 5 commits behind head on main.
The diff coverage is 100.00%.

❗ Current head c5f9810 differs from pull request most recent head 0c957b2. Consider uploading reports for the commit 0c957b2 to get more accurate results

@@           Coverage Diff           @@
##             main     #264   +/-   ##
=======================================
  Coverage   90.47%   90.47%           
=======================================
  Files           5        5           
  Lines         462      462           
  Branches       74       74           
=======================================
  Hits          418      418           
  Misses         44       44           

Files Changed	Coverage Δ
src/utils.ts	95.49% <100.00%> (ø)