Skip to content

Commit 2a7d632

Browse files
committed
Remove unnecessary code group formatting from builder codes and revshare documentation
1 parent ef54b6f commit 2a7d632

File tree

2 files changed

+0
-20
lines changed

2 files changed

+0
-20
lines changed

docs/pages/interaction/integration/integration-builder-codes.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,6 @@ Builder fees and addresses can be queried via the indexer using the `/orders` an
1515
- `partner address` - where fees will be routed
1616
- `fee (in ppm)` that will be charged on order matching
1717

18-
:::code-group
19-
2018
```typescript [TypeScript]
2119
// BuilderCodeParameters interface
2220
export interface IBuilderCodeParameters {
@@ -61,8 +59,6 @@ await client.validatorClient.post.placeOrder(
6159
);
6260
```
6361

64-
:::
65-
6662
:::note
6763
`BuilderCodeParameters` is an optional field
6864
:::

docs/pages/interaction/integration/integration-revshare.mdx

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ To participate in the Order Router Rev Share program, users need to propose and
1919

2020
To participate in the Order Router Rev Share program, you need to create and submit a governance proposal. Below are examples of the governance message structure:
2121

22-
:::code-group
23-
2422
```python [Python]
2523
# Example: Set order router revenue share via governance
2624
from dydx_v4_client.node.client import NodeClient
@@ -43,8 +41,6 @@ async def set_order_router_revenue_share_example():
4341
print(response)
4442
```
4543

46-
:::
47-
4844
The key components of this message are:
4945

5046
- `address` - The address of the order router that will receive the revenue share. This is also the id you place in your order message
@@ -58,8 +54,6 @@ The process for updating an existing order router's revenue share is the same as
5854

5955
To update the revenue share percentage for an existing order router, create a governance message with the same structure:
6056

61-
:::code-group
62-
6357
```python [Python]
6458
# Update existing order router revenue share
6559
async def update_order_router_revenue_share_example():
@@ -76,8 +70,6 @@ async def update_order_router_revenue_share_example():
7670
print(response)
7771
```
7872

79-
:::
80-
8173
The proposal must go through the standard governance voting process and receive a passing vote before the updated revenue share percentage takes effect.
8274

8375
:::note
@@ -92,8 +84,6 @@ To delete an order router's revenue share configuration, you simply need to set
9284

9385
Submit a governance proposal with the following message structure:
9486

95-
:::code-group
96-
9787
```python [Python]
9888
# Delete order router revenue share by setting share_ppm to 0
9989
async def delete_order_router_revenue_share_example():
@@ -110,8 +100,6 @@ async def delete_order_router_revenue_share_example():
110100
print(response)
111101
```
112102

113-
:::
114-
115103
:::note
116104
Key points to note:
117105

@@ -128,8 +116,6 @@ The `order_router_address` field is set when an order is placed
128116

129117
- `order_router_address` - the ID of the order router and where fees will be sent to
130118

131-
:::code-group
132-
133119
```python [Python]
134120
# Place an order with order router address for revenue share
135121
from dydx_v4_client.node.market import Market
@@ -156,8 +142,6 @@ transaction = await node.place_order(
156142
)
157143
```
158144

159-
:::
160-
161145
## Order Validation Checks
162146

163147
- Ensure the `order_router_address` field is valid and already voted in via governance

0 commit comments

Comments
 (0)