docs(user-guide): improve binding errors section

[pcoet]

Made a few edits to the binding errors guide:

• Added context in a couple of places.
• Made a few changes to improve readability.
• Made a couple of nitty copy edits.

I didn't add a "What's next" section because this feels like a different kind of content from the tutorials. Maybe at some point we could have a "Troubleshooting" section of the docs that includes this and other troubleshooting guides. There's a semi-consistent, implicit ordering to the site right now (getting started, using clients, handling errors, testing). If the docs get big enough, it might make sense to start making this organization explicit. Just thoughts!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.17%. Comparing base (19d8a87) to head (eddc065).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2928   +/-   ##
=======================================
  Coverage   96.17%   96.17%           
=======================================
  Files         105      105           
  Lines        4392     4392           
=======================================
  Hits         4224     4224           
  Misses        168      168           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coryan]

Thanks! You may want to look at https://www.conventionalcommits.org/en/v1.0.0/ we require the PR title to follow that format. It makes it easier to summarize the changes into a change log later.