docs: fix instances of network upgrade -> breaking network upgrade

celestiaorg · Sep 17, 2024 · 21d8af5 · 21d8af5
1 parent b7ca0c9
commit 21d8af5
Show file tree

Hide file tree

Showing 7 changed files with 18 additions and 18 deletions.
diff --git a/cips/README.md b/cips/README.md
@@ -44,7 +44,7 @@ Read [CIP-1](./cip-1.md) for information on the CIP process.
 | [14](./cip-14.md) |                          ICS-27 Interchain Accounts                          | Susannah Evans <[email protected]> ([@womensrights](https://github.com/womensrights)), Aidan Salzmann <[email protected]> ([@asalzmann](https://github.com/asalzmann)), Sam Pochyly <[email protected]> ([@sampocs](https://github.com/sampocs)) |
 | [15](./cip-15.md) |                            Discourage memo usage                             |                                                    Rootul Patel ([@rootulp](https://github.com/rootulp)), NashQueue ([@nashqueue](https://github.com/nashqueue))                                                     |
 | [16](./cip-16.md) |            Make Security Related Governance Parameters Immutable             |                                                               Mingpei CAO ([@caomingpei](https://github.com/caomingpei))                                                                |
-| [17](./cip-17.md) |                             Lemongrass Network Upgrade                              |                                                               Evan Forbes ([@evan-forbes](https://github.com/evan-forbes))                                                               |
+| [17](./cip-17.md) |                             Lemongrass Breaking Network Upgrade                              |                                                               Evan Forbes ([@evan-forbes](https://github.com/evan-forbes))                                                               |
 | [18](./cip-18.md) |              Standardised Gas and Pricing Estimation Interface               |                                                               Callum Waters ([@cmwaters](https://github.com/cmwaters))                                                                |
 | [19](./cip-19.md) |                                Shwap Protocol                                |                                                              Hlib Kanunnikov ([@Wondertan](https://github.com/Wondertan))                                                              |
 | [20](./cip-20.md) |                          Disable Blobstream module                           |                                                                Rootul Patel ([@rootulp](https://github.com/rootulp))                                                                 |

diff --git a/cips/cip-16.md b/cips/cip-16.md
@@ -62,7 +62,7 @@ Additionally, suppose that an on-chain governance proposal sets the `evidence.Ma
 
 ### Summary
 
-In summary, configuring these two parameters as immutable values that can NOT be changed via on-chain governance can mitigate the risks of inconsistency and security issues introduced by unintentional (or malicious) governance activities. Moreover, in the face of a security incident that concerns these parameters, reliance on on-chain governance may be inadequate. Implementing modifications through a hard fork represents a more resilient approach.
+In summary, configuring these two parameters as immutable values that can NOT be changed via on-chain governance can mitigate the risks of inconsistency and security issues introduced by unintentional (or malicious) governance activities. Moreover, in the face of a security incident that concerns these parameters, reliance on on-chain governance may be inadequate. Implementing modifications through a breaking network upgrade represents a more resilient approach.
 
 ## Backwards Compatibility
 

diff --git a/cips/cip-17.md b/cips/cip-17.md
@@ -1,7 +1,7 @@
 | cip | 17 |
 | - | - |
-| title | Lemongrass Network Upgrade |
-| description | Reference specifications included in the Lemongrass Network Upgrade |
+| title | Lemongrass Breaking Network Upgrade |
+| description | Reference specifications included in the Lemongrass Breaking Network Upgrade |
 | author | [@evan-forbes](https://github.com/evan-forbes) |
 | discussions-to | <https://forum.celestia.org/t/lemongrass-hardfork/1589> |
 | status | Final |
@@ -11,7 +11,7 @@
 
 ## Abstract
 
-This Meta CIP lists the CIPs included in the Lemongrass network upgrade.
+This Meta CIP lists the CIPs included in the Lemongrass breaking network upgrade.
 
 ## Specification
 
@@ -27,7 +27,7 @@ All of the above CIPs are state breaking, and thus require a breaking network up
 
 ## Rationale
 
-This CIP provides a complete list of breaking changes for the Lemongrass upgrade, along with links to those specs.
+This CIP provides a complete list of breaking changes for the Lemongrass breaking network upgrade, along with links to those specs.
 
 ## Security Considerations
 

diff --git a/cips/cip-21.md b/cips/cip-21.md
@@ -75,7 +75,7 @@ As a small digression, it may be feasible to additionally introduce a new namesp
 
 ## Backwards Compatibility
 
-This change requires a hard fork network upgrade as older nodes will not be able to verify the new blob format. The old blob format will still be supported allowing rollups to opt into the change as they please.
+This change requires a breaking network upgrade as older nodes will not be able to verify the new blob format. The old blob format will still be supported allowing rollups to opt into the change as they please.
 
 ## Test Cases
 

diff --git a/cips/cip-24.md b/cips/cip-24.md
@@ -1,7 +1,7 @@
 | cip | 24 |
 | - | - |
 | title | Versioned Gas Scheduler Variables |
-| description | Transition to hard fork-only updates for gas scheduler variables |
+| description | Transition to breaking-network-upgrade-only updates for gas scheduler variables |
 | author | Nina Barbakadze ([@ninabarbakadze](https://github.com/ninabarbakadze)) |
 | discussions-to | <https://forum.celestia.org/t/cip-versioned-gas-scheduler-variables/1785> |
 | status | Draft |
@@ -11,7 +11,7 @@
 
 ## Abstract
 
-Gas scheduler parameters `blob.GasPerBlobByte` and `auth.TxSizeCostPerByte` will no longer be modifiable by governance but may only change via a hard fork upgrade.
+Gas scheduler parameters `blob.GasPerBlobByte` and `auth.TxSizeCostPerByte` will no longer be modifiable by governance but may only change via a breaking network upgrade.
 
 ## Motivation
 
@@ -23,7 +23,7 @@ Currently, `GasPerBlobByte` and `TxSizeCostPerByte` are module parameters within
 
 ### Parameters
 
-The proposal makes these two variables modifiable through hard fork upgrades:
+The proposal makes these two variables modifiable through breaking network upgrades:
 
 Previously:
 
@@ -37,11 +37,11 @@ Now:
 
 ## Backwards Compatibility
 
-Enabling this feature requires a hard fork network upgrade.
+Enabling this feature requires a breaking network upgrade.
 
 ## Test Cases
 
-Test cases should verify that gas scheduler variables are exclusively updated via hard forks, effectively preventing updates through governance mechanisms and that the gas meter uses those constants.
+Test cases should verify that gas scheduler variables are exclusively updated via breaking network upgrade, effectively preventing updates through governance mechanisms and that the gas meter uses those constants.
 
 ## Reference Implementation
 

diff --git a/cips/notes/cdc-14.md b/cips/notes/cdc-14.md
@@ -2,13 +2,13 @@
 
 ## Overview
 
-- Lemongrass hard fork ([CIP-17](../cip-17.md)) final release expected by end of week, to be deployed on Arabica testnet in early August
+- Lemongrass breaking network upgrade ([CIP-17](../cip-17.md)) final release expected by end of week, to be deployed on Arabica testnet in early August
 - [CIP-21](../cip-21.md) (blob with verified signers) in Last Call stage, integration with celestia-app in progress
 - [CIP-22](../cip-22.md) (remove `IndexWrapper`) moved to review status, discussion on potential impacts
 - [CIP-23](../cip-23.md) (coordinated prevote time) introduced to solve inconsistent block times, prototype expected in 1-2 weeks
 - Celestia state machine v3 to include author blobs and delayed voting features, with potential upgrade system refactor
 
-## Lemongrass hard fork update
+## Lemongrass breaking network upgrade
 
 - Final release of celestia-app v2.0.0 expected by end of week
 - To be incorporated into celestia-node v0.16.0 (tentative)
@@ -51,4 +51,4 @@
 - Potential inclusion:
   - Refactor of upgrade system for Cosmos SDK compatibility
 - Meta CIP for v3 features to be written and discussed in next call
-- v3 upgrade planned to follow shortly after Lemongrass hard fork
+- v3 upgrade planned to follow shortly after Lemongrass breaking network upgrade
diff --git a/cips/notes/cdc-15.md b/cips/notes/cdc-15.md
@@ -8,7 +8,7 @@
 #### Overview
 
 *   Celestia Core Dev's Call 15 focused on working group updates and upcoming upgrades
-*   Lemongrass hard fork ([CIP-17](../cip-17.md)) and Celestia App v2 upgrades timelines slightly pushed back:
+*   Lemongrass breaking network upgrade ([CIP-17](../cip-17.md)) and Celestia App v2 upgrades timelines slightly pushed back:
   * Arabica (mid-August)
   * Mocha (end of August)
   * Mainnet (early September)
@@ -20,12 +20,12 @@
 *   ZK working group: Started work on exploring paths leading to ZK accounts, discussion planned for next week
 *   ZK working group sync meetings now biweekly, alternating with core dev calls
 
-#### Lemongrass hard fork and Celestia App v2 upgrades
+#### Lemongrass breaking network upgrade and Celestia App v2 upgrades
 
 *   Celestia Node to release update supporting Celestia App v2 soon
 *   Arabica devnet upgrade planned for **August 14th**
 *   Node operators must upgrade within **1 week** timeframe
-*   Consensus node operators need to use a specific CLI flag ([see documentation](https://docs.celestia.org/nodes/network-upgrade-process#lemongrass-network-upgrade))
+*   Consensus node operators need to use a specific CLI flag ([see documentation](https://docs.celestia.org/nodes/network-upgrade-process#lemongrass-breaking-network-upgrade))
 *   **Application owners on Arabica advised to monitor before and after upgrade**
 *   Upgrade process: Arabica first, then Mocha, finally Mainnet