update sha256sum for boot-tools of v0.37 (#876)

docs/networks/node-ops/access-onchain-data/access-nodes/access-node-setup.mdx

@@ -29,7 +29,7 @@ You can read more about epochs [here](../../../staking/03-schedule.md).
 
 In order to join the network at epoch N+1, the access node **must** be registered with at least 100 FLOW staked prior to the end of epoch N's Staking Auction Phase.
 
-Currently on mainnet, the staking auction starts every Wednesday at around 20:00 UTC and ends on the next Wednesday at around 12:00 UTC. 
+Currently on mainnet, the staking auction starts every Wednesday at around 20:00 UTC and ends on the next Wednesday at around 12:00 UTC.
 Since this deadline may shift slightly from epoch to epoch, we recommend the node be staked by _Wednesday, 8:00 UTC_ to be able to join the network in the next epoch.
 
 Confirmation of a new node's inclusion in epoch N+1 is included in the [`EpochSetup` event](../../../staking/05-epoch-scripts-events.md#epochsetup).
@@ -78,7 +78,7 @@ tar -xvf boot-tools.tar
 
 ```shell CheckSHA256
 sha256sum ./boot-tools/bootstrap
-a06e3e9b2443c6755214150e9e101b70dd48ae30ffcfcbbcc471ba430cb104bf  ./boot-tools/bootstrap
+f3745f72d917631636161190a2bc4968543e2213944e9fb9b83c991852d1458d  ./boot-tools/bootstrap
 ```
 
 > If you have downloaded the bootstrapping kit previously, ensure the SHA256 hash for it still matches. If not, re-download to ensure you are using the most up-to-date version.

docs/networks/node-ops/node-operation/node-bootstrap.md

@@ -44,10 +44,10 @@ chmod +x ./boot-tools/transit
 
 ```shell CheckSHA256
 sha256sum ./boot-tools/bootstrapcmd
-a06e3e9b2443c6755214150e9e101b70dd48ae30ffcfcbbcc471ba430cb104bf  ./boot-tools/bootstrap
+f3745f72d917631636161190a2bc4968543e2213944e9fb9b83c991852d1458d  ./boot-tools/bootstrap
 
 sha256sum ./boot-tools/transit
-bc34a311f934fafed984a195f6bdca659ed21bfe50dd9947a39eb8edca6b10aa  ./boot-tools/transit
+7a105a9f8340c7c881553e527a7a7fcdcb87388d20487f48dc5c6519153de757  ./boot-tools/transit
 ```
 
 ### Generate Your Node Keys