chore: remove repetitive words

[clonemycode]

Description

remove repetitive words

Applicable issues

• fixes #

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[codecov]

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 66.06%. Comparing base (b379a0a) to head (186b828).
Report is 158 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff              @@
##           develop    #4774       +/-   ##
============================================
+ Coverage    15.53%   66.06%   +50.52%     
============================================
  Files          476      487       +11     
  Lines       344100   348885     +4785     
  Branches         0      323      +323     
============================================
+ Hits         53460   230479   +177019     
+ Misses      290640   118398   -172242     
- Partials         0        8        +8     

Files	Coverage Δ
clarity/src/vm/contexts.rs	81.46% <ø> (+42.86%)	⬆️
stackslib/src/chainstate/stacks/index/storage.rs	80.80% <100.00%> (+20.49%)	⬆️
stackslib/src/chainstate/stacks/miner.rs	79.26% <ø> (+34.21%)	⬆️
clarity/src/vm/tests/principals.rs	46.99% <0.00%> (+46.99%)	⬆️
testnet/stacks-node/src/tests/epoch_23.rs	0.00% <0.00%> (ø)

... and 436 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3d96d53...186b828. Read the comment docs.

[blockstack-devops]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.