fixup: Epoch.coinDenyList doc comment

Author: amnn

crates/sui-indexer-alt-graphql/schema.graphql

@@ -63,7 +63,7 @@ type Epoch {
 	"""
 	State of the Coin DenyList object (0x403) at the start of this epoch.
 	
-	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Subsequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
+	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Consequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
 	"""
 	coinDenyList: Object
 	"""

crates/sui-indexer-alt-graphql/src/api/types/epoch.rs

@@ -71,7 +71,7 @@ impl Epoch {
 impl EpochStart {
     /// State of the Coin DenyList object (0x403) at the start of this epoch.
     ///
-    /// The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Subsequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
+    /// The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Consequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
     async fn coin_deny_list(
         &self,
         ctx: &Context<'_>,

crates/sui-indexer-alt-graphql/src/snapshots/sui_indexer_alt_graphql__tests__schema.graphql.snap

@@ -67,7 +67,7 @@ type Epoch {
 	"""
 	State of the Coin DenyList object (0x403) at the start of this epoch.
 
-	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Subsequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
+	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Consequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
 	"""
 	coinDenyList: Object
 	"""

crates/sui-indexer-alt-graphql/src/snapshots/sui_indexer_alt_graphql__tests__staging.graphql.snap

@@ -67,7 +67,7 @@ type Epoch {
 	"""
 	State of the Coin DenyList object (0x403) at the start of this epoch.
 
-	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Subsequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
+	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Consequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
 	"""
 	coinDenyList: Object
 	"""

crates/sui-indexer-alt-graphql/staging.graphql

@@ -63,7 +63,7 @@ type Epoch {
 	"""
 	State of the Coin DenyList object (0x403) at the start of this epoch.
 	
-	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Subsequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
+	The DenyList controls access to Regulated Coins. Writes to the DenyList are accumulated and only take effect on the next epoch boundary. Consequently, it's possible to determine the state of the DenyList for a transaction by reading it at the start of the epoch the transaction is in.
 	"""
 	coinDenyList: Object
 	"""