chore: fix some typos in comment (#980)

<!--
Thanks for submitting a pull request! Here are some helpful tips:

* Always create branches on and target the `develop` branch.
* Run all the tests locally and ensure that they are passing.
* Run `make format` to ensure that the code is formatted.
* Run `make check` to ensure that all checks passed successfully.
* Small commits and contributions that attempt one single goal is
preferable.
* If the idea changes or adds anything functional which will affect
users, an
AIP discussion is required first on the Aurora forum: 

https://forum.aurora.dev/discussions/AIPs%20(Aurora%20Improvement%20Proposals).
* Avoid breaking the public API (namely in engine/src/lib.rs) unless
required.
* If your PR is a WIP, ensure that you enable "draft" mode.
* Your first PRs won't use the CI automatically unless a maintainer
starts.
If this is not your first PR, please do NOT abuse the CI resources.

Checklist:
- [ ] I have performed a self-review of my code
- [ ] I have documented my code, particularly in the hard-to-understand
areas
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests to prove my fix or new feature is effective and
works
- [ ] Any dependent changes have been merged
- [ ] The PR is targeting the `develop` branch and not `master`
- [ ] I have pre-squashed my commits into a single commit and rebased.
-->

## Description

fix some typos in comment

<!-- 
Provide a general summary of your changes. A clear overview along with
an
in-depth explanation is beneficial.

If this PR closes any issues, be sure to add "closes #<number>"
somewhere.
-->

## Performance / NEAR gas cost considerations

<!--
Performance regressions are not ideal, though we welcome performance 
improvements. Any PR must be completely mindful of any gas cost
increases. The
CI will fail if the gas costs change at all. Do update these tests to 
accommodate for the new gas changes. It is good to explain 
this change, if necessary.
-->

## Testing

No need.

<!--
Please describe the tests that you ran to verify your changes.
-->

## How should this be reviewed

<!--
Include any recommendations of areas to be careful of to ensure that the
reviewers use extra attention.
-->

## Additional information

<!--
Include any additional information which you think should be in this PR,
such
as prior arts, future extensions, unresolved problems, or a TODO list
which
should be followed up.
-->

Signed-off-by: cuibuwei <cuibuwei@gmail.com>

engine-standalone-tracing/.catalog-info.yaml

@@ -4,7 +4,7 @@ kind: Component
 metadata:
   name: aurora-engine-standalone-tracing
   description: |-
-    Aurora engine standalone tracing library. Provides functions and types for extracing geth-like traces from standalone engine execution.
+    Aurora engine standalone tracing library. Provides functions and types for extracting geth-like traces from standalone engine execution.
   tags:
     - near
   links: []

engine-standalone-tracing/Cargo.toml

@@ -3,7 +3,7 @@ name = "engine-standalone-tracing"
 version = "0.1.0"
 edition.workspace = true
 authors.workspace = true
-description = "Aurora engine standalone tracing library. Provides functions and types for extracing geth-like traces from standalone engine execution."
+description = "Aurora engine standalone tracing library. Provides functions and types for extracting geth-like traces from standalone engine execution."
 homepage.workspace = true
 repository.workspace = true
 license.workspace = true

engine-tests-connector/src/connector.rs

@@ -1076,7 +1076,7 @@ async fn test_deposit_to_aurora_amount_zero_fee_non_zero() -> anyhow::Result<()>
     let res = contract
         .deposit_with_proof(&contract.get_proof(proof_str))
         .await?;
-    assert!(contract.check_error_message(res, "The amount should be a positive numbe"));
+    assert!(contract.check_error_message(res, "The amount should be a positive number"));
     assert!(!contract.call_is_used_proof(proof_str).await?);
     Ok(())
 }