Fix small typos

[code0xff]

High Level Overview of Change

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

API Impact

• Public API: New feature (new methods and/or new fields)
• Public API: Breaking change (in general, breaking changes should only impact the next api_version)
• libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
• Peer protocol change (must be backward compatible or bump the peer protocol version)

[ximinez]

@code0xff Can you affirm this is ready to merge?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.2%. Comparing base (a079bac) to head (2c551b4).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop   #5279     +/-   ##
=========================================
- Coverage     78.2%   78.2%   -0.0%     
=========================================
  Files          790     790             
  Lines        67639   67638      -1     
  Branches      8160    8164      +4     
=========================================
- Hits         52869   52862      -7     
- Misses       14770   14776      +6     

Files with missing lines	Coverage Δ
include/xrpl/protocol/AccountID.h	61.5% <ø> (ø)
include/xrpl/protocol/Sign.h	100.0% <ø> (ø)
src/xrpld/app/main/Main.cpp	79.0% <ø> (ø)

... and 4 files with indirect coverage changes

[code0xff]

@code0xff Can you affirm this is ready to merge?

Yes, this is ready to merge. The changes are just simple typo fixes. Please let me know if there's anything else that needs to be done.

[bthomee]

@code0xff would you be able to sign your commits?

• See https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits for the official documentation. Although if you use something like 1Password, you can generate an SSH key there and configured that one to sign the commits.
• To amend an earlier unsigned commit and sign it, this set of instructions is useful: https://dev.to/za-h-ra/git-fixing-unsigned-gpg-commits-phn.