Fixing documentation for error handling

[Chengxuan]

Issue

Issue number, if available, prefixed with "#"

Description

What does this implement/fix? Explain your changes.

The error object looks like below:

{
  "name":"NoSuchBucket",
  "$fault":"client",
  "$metadata": {
    "httpStatusCode": 404,
    "requestId":"xxx",
    "extendedRequestId":"xxx=",
    "attempts":1,
    "totalRetryDelay":0
  },
  "Code":"NoSuchBucket",
  "BucketName":"xxx",
  "RequestId":"xxx",
  "HostId":"xxx=",
  "message":"The specified bucket does not exist"
}

So the example code snippet doesn't work as it had an extra $.

Testing

How was this change tested?

Against an AWS S3 service

Additional context

Add any other context about the PR here.

Checklist

• If you wrote E2E tests, are they resilient to concurrent I/O?
• If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kuhe]

this requires a code generation fix, so it will be done in #5476

[Chengxuan]

thanks @kuhe

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.