chore: blobstream -> Blobstream

cips/cip-20.md

@@ -12,11 +12,11 @@ created: 2024-04-16
 
 ## Abstract
 
-The purpose of this proposal is to disable the blobstream module in celestia-app.
+The purpose of this proposal is to disable the Blobstream module in celestia-app.
 
 ## Motivation
 
-The blobstream module is a celestia-app specific state machine module. The blobstream module was designed to serve as a single component in the original blobstream architecture. The original blobstream architecture has been deprecated in favor of [Blobstream X](https://github.com/succinctlabs/blobstreamx) so the blobstream module is no longer needed and thus can be disabled.
+The Blobstream module is a celestia-app specific state machine module. The Blobstream module was designed to serve as a single component in the original Blobstream architecture. The original Blobstream architecture has been deprecated in favor of [Blobstream X](https://github.com/succinctlabs/blobstreamx) so the Blobstream module is no longer needed and thus can be disabled.
 
 ## Specification
 
@@ -37,7 +37,7 @@ If this CIP is adopted, the following parameter can be removed:
 
 ## Rationale
 
-Disabling the blobstream module reduces the functionality of the celestia-app state machine. Disabling the Blobstream module also reduces the amount of state that needs to be stored and maintained in the celestia-app state machine.
+Disabling the Blobstream module reduces the functionality of the celestia-app state machine. Disabling the Blobstream module also reduces the amount of state that needs to be stored and maintained in the celestia-app state machine.
 
 ## Backwards Compatibility
 
@@ -48,12 +48,12 @@ This proposal is backwards-incompatible because it is state-machine breaking. Th
 > [!NOTE]
 > Blobstream was previously named Quantum Gravity Bridge (QGB) and the codebase never fully adopted the name change so you may interpret instances of `qgb` as `blobstream`.
 
-1. Ensure that celestia-app no longer accepts transactions for the blobstream module. Example: `celestia-app tx qgb <command>` should return an error message.
-1. Ensure that celestia-app no longer accepts gRPC, RPC, or CLI queries for the blobstream module. Example: `celestia-app query qgb <command>` should return an error message.
+1. Ensure that celestia-app no longer accepts transactions for the Blobstream module. Example: `celestia-app tx qgb <command>` should return an error message.
+1. Ensure that celestia-app no longer accepts gRPC, RPC, or CLI queries for the Blobstream module. Example: `celestia-app query qgb <command>` should return an error message.
 
 ## Reference Implementation
 
-Celestia-app uses a versioned module manager and configurator that enables the removal of modules during app version upgrades. Concretely, the blobstream module can be disabled via this diff in `app.go`:
+Celestia-app uses a versioned module manager and configurator that enables the removal of modules during app version upgrades. Concretely, the Blobstream module can be disabled via this diff in `app.go`:
 
 ```diff
 {
@@ -64,7 +64,7 @@ Celestia-app uses a versioned module manager and configurator that enables the r
 },
 ```
 
-Additionally, a store migration needs to be registered during the upgrade process to ensure that the blobstream module's state is removed. Lastly, the blobstream module's tx commands and query commands should be removed from the CLI.
+Additionally, a store migration needs to be registered during the upgrade process to ensure that the Blobstream module's state is removed. Lastly, the Blobstream module's tx commands and query commands should be removed from the CLI.
 
 ## Security Considerations