updating the the steps for network upgrade for forte (#1513)

* updating the the steps for network upgrade for forte

* updating the the steps for network upgrade for forte

* Apply suggestion from @peterargue

Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>

* updating based on review comment

* removing the line about build from source

---------

Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>

Author: vishalchangrani

docs/protocol/node-ops/node-operation/network-upgrade.md

@@ -16,12 +16,14 @@ Network Upgrades are approximately once every year.
 Upcoming network upgrades are announced in advance on the `#flow-validators-announcements` [Discord channel](https://discord.gg/flow) and on the [status](https://status.flow.com/) page.
 The `#flow-validators-announcements` channel is also used to coordinate during the upgrade process with all the node operators.
 
+> 📢 [Forte Upgrade](https://status.flow.com/incidents/x91d6t1x1qh4) on Wednesday, Oct 22nd, 2025 at 15:00 UTC
+
 This guide is for existing operators participating in a network upgrade. See [Node Bootstrap](./node-bootstrap.md)
 for a guide to joining the network for the first time.
 
 ## Step 1 - Cleaning Up Previous Spork State
 
-Once the spork start has been announced on, stop your node and clear your database. The node should stay stopped for the duration of the spork.
+Once the spork start has been announced on Discord, stop your node and clear your database. The node should stay stopped for the duration of the spork.
 
 <Callout type="warning">
   You can skip this step if it is your first time running a node on Flow.
@@ -54,7 +56,8 @@ If you had set the [dynamic bootstrap arguments](https://developers.flow.com/pro
     - It will generally be `testnet-x` or `mainnet-x` if execution data indexing is not enabled.
     - It will generally be `testnet-x-execution` or `mainnet-x-execution` if execution data indexing is enabled. See [here](../access-nodes/access-node-configuration-options.md) to enable execution date indexing.
 
-- `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification`, `access` based on the node(s) that you are running.
+- `YOUR_NODE_TYPE` should be one of `collection`, `consensus`, `execution`, `verification` based on the node(s) that you are running.
+  - For access nodes however, if you have execution data index enabled use the role `execution` to ensure the execution state files (`root.checkpoint*`) are also downloaded. If you do not have execution data indexing enabled, specify the role as `access`.
 
 ```shell Example
 $ ./boot-tools/transit pull -b ./bootstrap -t mainnet-16  -r consensus
@@ -78,7 +81,15 @@ $ tree ./bootstrap/
   └── random-beacon.priv.json.39fa54984b8eaa463e129919464f61c8cec3a4389478df79c44eb9bfbf30799a
 ```
 
-2. Start your Flow node via `docker` or `systemd`
+2. Update command line arguments
+
+For the Forte upgrade, remove the `pebble-dir` argument as it has been deprecated. This applies to all node types.
+The node will continue to use the `datadir` argument which points to the location of the node database.
+
+
+3. Start your Flow node via `docker` or `systemd`
+
+The FlowFoundation team will share the new docker tag at the completion of the upgrade. Please use that docker tag to bring up the node.
 
 See [Node Bootstrap](./node-bootstrap.md) for detailed information on Docker/Systemd configuration.