[rename] random [aA] Aptos to [aA]n Aptos

config/management/genesis/README.md

@@ -86,7 +86,7 @@ validator_backend:
 Overview of fields:
 
 * `chain_id` specifies a distinct chain and is written into genesis, checked during network connections, and part of each transaction. It is provided by the association.
-* `json_server` specifies a Aptos JSON Server. This can be any that connect to your network including your own of one run by the association. It is not used in genesis, so a dummy value is acceptable during initial configuration.
+* `json_server` specifies an Aptos JSON Server. This can be any that connect to your network including your own of one run by the association. It is not used in genesis, so a dummy value is acceptable during initial configuration.
 * `shared_backend` is a pointer to the associaton's `shared storage`.
 * `validator_backend` is a pointer to the local validator node's secure storage.
 

developer-docs-site/docs/reference/glossary.md

@@ -38,7 +38,7 @@ Aptos-core is the open source technology on which the Aptos Payment Network runs
 The Aptos Framework defines the public API for blockchain updates and the structure of on-chain data. It defines the business logic and access control for the three key pillars of Aptos functionality: payments, treasury, and on-chain governance. It is implemented as a set of modules written in the Move programming language and stored on-chain as Move bytecode.
 
 ## Aptos node
-A Aptos node is a peer entity of the Aptos network that tracks the state of the Aptos Blockchain. There are two types of Aptos nodes, [validators](#validator) and [FullNodes](#fullnode)).
+An Aptos node is a peer entity of the Aptos network that tracks the state of the Aptos Blockchain. There are two types of Aptos nodes, [validators](#validator) and [FullNodes](#fullnode)).
 
 ## Aptos Protocol
 
@@ -210,7 +210,7 @@ then there is a guarantee that T_N will never be included in the blockchain.
 ## Node
 
 - A **node** is a peer entity of the Aptos network that tracks the state of the Aptos Blockchain.
-- A Aptos node consists of logical components. [Mempool](#mempool), [consensus](#consensus), and the [virtual machine](#virtual-machine) are examples of node components.
+- An Aptos node consists of logical components. [Mempool](#mempool), [consensus](#consensus), and the [virtual machine](#virtual-machine) are examples of node components.
 
 # O
 

documentation/specifications/db_backup/spec.md

@@ -23,7 +23,7 @@ pub type FileHandle = String;
 pub struct TextLine(String);
 ```
 
-A AptosDB **backup storage** stores **backups** and **metadata lines**.
+An AptosDB **backup storage** stores **backups** and **metadata lines**.
 
 Each of the **backups** contains information that reflects different aspects of the blockchain history. It is identified by its manifest file (human readable, in JSON), which can contain links to data files. Depending on the specific type of backup, the content differs. The backup system doesn’t care about how physically the storage organizes backups, it dumps backups as group of files (although it does try to hint the storage that the group are related to each other, see the [Backup Storage interface](#backup-storage-interface)), asking back one single FileHandle to identify the whole backup. The restore system takes `FileHandle`s pointing to manifests, it’s up to the human / external system to decide which manifests are relevant, probably based on the **metadata**.
 

storage/storage-interface/src/lib.rs

@@ -180,7 +180,7 @@ pub enum Order {
 }
 
 /// Trait that is implemented by a DB that supports certain public (to client) read APIs
-/// expected of a Aptos DB
+/// expected of an Aptos DB
 #[allow(unused_variables)]
 pub trait DbReader: Send + Sync {
     /// See [`AptosDB::get_epoch_ending_ledger_infos`].
@@ -567,7 +567,7 @@ impl MoveStorage for &dyn DbReader {
 }
 
 /// Trait that is implemented by a DB that supports certain public (to client) write APIs
-/// expected of a Aptos DB. This adds write APIs to DbReader.
+/// expected of an Aptos DB. This adds write APIs to DbReader.
 #[allow(unused_variables)]
 pub trait DbWriter: Send + Sync {
     /// Persist transactions. Called by the executor module when either syncing nodes or committing