Update deploy-to-testnet.md (#513) (#537)

* Update deploy-to-testnet.md (#513)

* Update deploy-to-testnet.md

* Update tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

Co-authored-by: 0xLucca <[email protected]>

* Update tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

---------

Co-authored-by: Nicolás Hussein <[email protected]>
Co-authored-by: 0xLucca <[email protected]>

* fix: llms

---------

Co-authored-by: Yung Beef 4.2 <[email protected]>
Co-authored-by: 0xLucca <[email protected]>

Author: 3 people

llms.txt

@@ -25139,6 +25139,8 @@ Polkadot SDK-based blockchains are defined by a file called the [chain specifica
 - **Plain chain spec** - a human-readable JSON file that can be modified to suit your parachain's requirements. It serves as a template for initial configuration and includes human-readable keys and structures
 - **Raw chain spec** - a binary-encoded file used to start your parachain node. This file is generated from the plain chain spec and contains the encoded information necessary for the parachain node to synchronize with the blockchain network. It ensures compatibility across different runtime versions by providing data in a format directly interpretable by the node's runtime, regardless of upgrades since the chain's genesis
 
+The chain spec file is only required during the initial blockchain creation (genesis). You do not need to generate a new chain spec when performing runtime upgrades after your chain is already running.
+
 The files required to register a parachain must specify the correct relay chain to connect to and the parachain identifier you have been assigned. To make these changes, you must build and modify the chain specification file for your parachain. In this tutorial, the relay chain is `paseo`, and the parachain identifier is `4508`.
 
 To define your chain specification:

tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

@@ -98,6 +98,8 @@ Polkadot SDK-based blockchains are defined by a file called the [chain specifica
 - **Plain chain spec** - a human-readable JSON file that can be modified to suit your parachain's requirements. It serves as a template for initial configuration and includes human-readable keys and structures
 - **Raw chain spec** - a binary-encoded file used to start your parachain node. This file is generated from the plain chain spec and contains the encoded information necessary for the parachain node to synchronize with the blockchain network. It ensures compatibility across different runtime versions by providing data in a format directly interpretable by the node's runtime, regardless of upgrades since the chain's genesis
 
+The chain spec file is only required during the initial blockchain creation (genesis). You do not need to generate a new chain spec when performing runtime upgrades after your chain is already running.
+
 The files required to register a parachain must specify the correct relay chain to connect to and the parachain identifier you have been assigned. To make these changes, you must build and modify the chain specification file for your parachain. In this tutorial, the relay chain is `paseo`, and the parachain identifier is `4508`.
 
 To define your chain specification: