chore: fix some function names in comment

[linchizhen]

Which problem is this PR solving?

Description of the changes

fix some function names in comment

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.81%. Comparing base (9a30dfc) to head (f362c8e).
Report is 22 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5909      +/-   ##
==========================================
- Coverage   96.83%   96.81%   -0.03%     
==========================================
  Files         342      342              
  Lines       16524    16524              
==========================================
- Hits        16001    15997       -4     
- Misses        337      340       +3     
- Partials      186      187       +1     

Flag	Coverage Δ
badger_v1	8.05% <ø> (ø)
badger_v2	1.82% <ø> (ø)
cassandra-3.x-v1	16.62% <ø> (ø)
cassandra-3.x-v2	1.75% <ø> (ø)
cassandra-4.x-v1	16.62% <ø> (ø)
cassandra-4.x-v2	1.75% <ø> (ø)
elasticsearch-6.x-v1	18.79% <ø> (+0.01%)	⬆️
elasticsearch-7.x-v1	18.85% <ø> (+0.01%)	⬆️
elasticsearch-8.x-v1	19.04% <ø> (+0.01%)	⬆️
elasticsearch-8.x-v2	1.81% <ø> (-0.02%)	⬇️
grpc_v1	9.49% <ø> (ø)
grpc_v2	7.16% <ø> (ø)
kafka-v1	9.74% <ø> (ø)
kafka-v2	1.82% <ø> (ø)
memory_v2	1.82% <ø> (ø)
opensearch-1.x-v1	18.90% <ø> (+0.01%)	⬆️
opensearch-2.x-v1	18.89% <ø> (-0.02%)	⬇️
opensearch-2.x-v2	1.82% <ø> (ø)
unittests	95.29% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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