Skip to content

Commit 3c27d6f

Browse files
committed
nit
1 parent b1dab21 commit 3c27d6f

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

docs/0_internal/3_b_1_deploy_new_impl.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,6 @@ You can deploy the new implementation of the following contracts:
5656
This will show two addresses. The first one is the `alignedLayerServiceManager` address, and the second one is the new implementation address of `alignedServiceManagerImplementation`.
5757
5858
> [!NOTE]
59-
>
6059
> Make sure the `alignedLayerServiceManager` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
6160
>
6261
> Make sure the `alignedServiceManagerImplementation` address is the same as the one you deployed in this guide.
@@ -95,8 +94,8 @@ You can deploy the new implementation of the following contracts:
9594
9695
This will show the `batcherPaymentServiceImplementation` address.
9796
98-
> [!NOTE]
99-
> Make sure the `batcherPaymentServiceImplementation` address is the same as the one you deployed in this guide.
97+
> [!NOTE]
98+
> Make sure the `batcherPaymentServiceImplementation` address is the same as the one you deployed in this guide.
10099
101100
102101
### Deploy New Implementation for RegistryCoordinator
@@ -132,9 +131,10 @@ You can deploy the new implementation of the following contracts:
132131

133132
This will show two addresses. The first one is the `registryCoordinator` address, and the second one is the new implementation address of `registryCoordinatorImplementation`.
134133

135-
> [!NOTE]
136-
> Make sure the `registryCoordinator` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
137-
> Make sure the `registryCoordinatorImplementation` address is the same as the one you deployed in this guide.
134+
> [!NOTE]
135+
> Make sure the `registryCoordinator` address is the same as the one you deployed in the [Deploy Contracts Guide](./2_deploy_contracts.md).
136+
>
137+
> Make sure the `registryCoordinatorImplementation` address is the same as the one you deployed in this guide.
138138
139139

140140
## Next Steps

docs/0_internal/3_b_2_propose_upgrade.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,8 +96,8 @@ To propose the upgrade transaction you can follow the steps below:
9696
jq -r ".addresses.alignedLayerProxyAdmin" contracts/script/output/mainnet/alignedlayer_deployment_output.json | pbcopy
9797
```
9898

99-
> [!NOTE]
100-
> Make sure to set the path to the correct deployment output file.
99+
> [!NOTE]
100+
> Make sure to set the path to the correct deployment output file.
101101

102102
8. Once you paste the `ProxyAdmin` address, the ABI should be automatically filled.
103103

docs/0_internal/3_b_3_approve_upgrade.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,8 @@ To approve the upgrade transaction, you can follow the steps below:
3434

3535
6. Once you are sure everything is correct, click on `Execute` to approve the transaction.
3636

37-
> [!NOTE]
38-
> The transaction gas usage is approximately 100,000 gas units. Make sure you have enough ETH to cover the gas fees.
37+
> [!NOTE]
38+
> The transaction gas usage is approximately 100,000 gas units. Make sure you have enough ETH to cover the gas fees.
3939
4040
7. Wait for the transaction to be executed. You can check the transaction status on the `Transactions` tab.
4141

0 commit comments

Comments
 (0)