fix(docs): fix build failure of the CWT example

[shizhMSFT]

Fix #213 for the build failure of the CWT example.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.27%. Comparing base (92fbe95) to head (babaebc).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #214      +/-   ##
==========================================
- Coverage   92.35%   91.27%   -1.09%     
==========================================
  Files          12       12              
  Lines        1622     2005     +383     
==========================================
+ Hits         1498     1830     +332     
- Misses         68      119      +51     
  Partials       56       56              

☔ 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.

[Copilot]

Pull Request Overview

This pull request addresses build failures in the CWT example by modifying the example function's name.

• Renamed the example function from ExampleCWTMessage to Example_cWTMessage to resolve build issues.

Comments suppressed due to low confidence (1)

cwt_test.go:13

• [nitpick] Consider revisiting the naming convention for Go example functions. The standard approach typically uses CamelCase (e.g., ExampleCWTMessage), so if the change to Example_cWTMessage is required for the build, adding a clarifying comment might help future maintainers.

func Example_cWTMessage() {

[shizhMSFT]

Local preview:

[qmuntal]

What if it is renamed as ExampleCWTClaims? This way the example will be attached to the CWTClaims struct, which is probably more aligned with the original intention.

[shizhMSFT]

@qmuntal That also works. Updated to CWTClaims.

[shizhMSFT]

New look: