chore: remove duplicate word in comment (#21907)

## Description 

remove duplicate word in comment

## Test plan 

How did you test the new or updated feature?

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] gRPC:
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:

Signed-off-by: wangcundashang <wangcundashang@qq.com>

Author: wangcundashang

crates/sui-indexer-alt-jsonrpc/src/api/name_service/response.rs

@@ -17,7 +17,7 @@ use crate::{
 
 use super::Error;
 
-/// Attempt to to translate the given SuiNS `name` to its address, as long as the mapping exists,
+/// Attempt to translate the given SuiNS `name` to its address, as long as the mapping exists,
 /// and it hasn't expired.
 pub(super) async fn resolved_address(
     ctx: &Context,
@@ -91,7 +91,7 @@ pub(super) async fn resolved_address(
     }
 }
 
-/// Attempt to to translate the given `address` to its SuiNS name, as long as the reverse mapping
+/// Attempt to translate the given `address` to its SuiNS name, as long as the reverse mapping
 /// exists, and the forward mapping points to the address.
 pub(super) async fn resolved_name(
     ctx: &Context,

crates/sui-indexer-alt-schema/migrations/2024-11-01-182359_kv_genesis/up.sql

@@ -1,4 +1,4 @@
--- Stores information related to to the genesis checkpoint.
+-- Stores information related to the genesis checkpoint.
 CREATE TABLE IF NOT EXISTS kv_genesis
 (
     -- The checkpoint digest of the genesis checkpoint

docs/content/concepts/grpc-overview.mdx

@@ -31,7 +31,7 @@ These definitions can be used to generate client libraries in various programmin
 
 :::info
 
-There are some proto files in the folder `sui/rpc/v2alpha` as well. Those are are in alpha because they are early experimental versions that are subject to change and not recommended for production use.
+There are some proto files in the folder `sui/rpc/v2alpha` as well. Those are in alpha because they are early experimental versions that are subject to change and not recommended for production use.
 
 :::
 
@@ -239,7 +239,7 @@ require (
 
 **Generate Golang code from proto files**
 
-Assuming you have the the proto files from [Github v2beta](https://github.com/MystenLabs/sui/tree/main/crates/sui-rpc-api/proto), run:
+Assuming you have the proto files from [Github v2beta](https://github.com/MystenLabs/sui/tree/main/crates/sui-rpc-api/proto), run:
 
 ```shell
 protoc --proto_path=./protos --go_out=. --go-grpc_out=. protos/sui/rpc/v2beta/ledger_service.proto
@@ -336,7 +336,7 @@ pip install grpcio grpcio-tools protobuf
 
 **Generate Python code from proto files**
 
-Assuming you have the the proto files from [Github v2beta](https://github.com/MystenLabs/sui/tree/main/crates/sui-rpc-api/proto), run:
+Assuming you have the proto files from [Github v2beta](https://github.com/MystenLabs/sui/tree/main/crates/sui-rpc-api/proto), run:
 
 ```shell
 python -m grpc_tools.protoc -I./protos --python_out=. --grpc_python_out=. ./protos/sui/rpc/v2beta/ledger_service.proto

external-crates/move/crates/move-analyzer/trace-adapter/src/runtime.ts

@@ -506,7 +506,7 @@ export class Runtime extends EventEmitter {
                     // and `baz` in the example above).
                     //
                     // The following explains a bit more formally what needs
-                    // to happen both on on `next` and `step` actions when
+                    // to happen both on `next` and `step` actions when
                     // call and non-call instructions are interleaved:
                     //
                     // When `step` is called: