Skip to content

Commit 4d81f8e

Browse files
committed
SEP style in metas
1 parent 9950e43 commit 4d81f8e

File tree

8 files changed

+16
-16
lines changed

8 files changed

+16
-16
lines changed

docs/build/apps/example-application-tutorial/anchor-integration/sep6.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Since many of the SEP-6 (and SEP-24) endpoints require authentication, we wait u
5151

5252
The user can then initiate one of the transfer methods (in BasicPay, only deposits and withdraws are supported) by clicking the “Deposit” or “Withdraw” button underneath a supported asset.
5353

54-
![Sep6 Tutorial Screenshot](/assets/basic-pay/sep6/deposit-withdraw.png)
54+
![SEP-6 Tutorial Screenshot](/assets/basic-pay/sep6/deposit-withdraw.png)
5555

5656
```html title=/src/routes/dashboard/transfers/+page.svelte
5757
<script>

docs/build/apps/wallet/sep30.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
88

99
<Header />
1010

11-
The [Sep-30](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md) standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private key without providing any third party control of the account. During this flow the wallet communicates with one or more recovery signer servers to register the wallet for a later recovery if it's needed.
11+
The [SEP-30](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md) standard defines the standard way for an individual (e.g., a user or wallet) to regain access to their Stellar account after losing its private key without providing any third party control of the account. During this flow the wallet communicates with one or more recovery signer servers to register the wallet for a later recovery if it's needed.
1212

1313
## Create Recoverable Account
1414

docs/build/apps/wallet/sep38.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@ import Header from "./component/header.mdx";
1212

1313
The [SEP-38](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md) standard defines a way for anchors to provide quotes for the exchange of an off-chain asset and a different on-chain asset, and vice versa. Quotes may be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or [firm](https://www.investopedia.com/terms/f/firmquote.asp) ones. When either is used is explained in the sections below.
1414

15-
## Creating Sep-38 Object
15+
## Creating SEP-38 Object
1616

1717
Let's start with creating a sep38 object, which we'll use for all SEP-38 interactions. Authentication is optional for these requests, and depends on the anchor implementation. For our example we will include it.
1818

19-
Authentication is done using [Sep-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md), and we add the authentication token to the sep38 object.
19+
Authentication is done using [SEP-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md), and we add the authentication token to the sep38 object.
2020

2121
<WalletCodeExample>
2222

docs/build/apps/wallet/sep7.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
88

99
<Header />
1010

11-
The [Sep-7](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign. The scheme used is `web+stellar`, followed by a colon. Example: `web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>`
11+
The [SEP-7](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign. The scheme used is `web+stellar`, followed by a colon. Example: `web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>`
1212

1313
## Tx Operation
1414

@@ -27,7 +27,7 @@ const xdr = encodeURIComponent(tx.toEnvelope().toXDR().toString("base64"));
2727
const callback = encodeURIComponent("https://example.com/callback");
2828
const txUri = `web+stellar:tx?xdr=${xdr}&callback=${callback}`;
2929
const uri = wallet.parseSep7Uri(txUri);
30-
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
30+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
3131
```
3232

3333
```dart
@@ -39,7 +39,7 @@ final xdr = Uri.encodeComponent(tx.toEnvelopeXdrBase64());
3939
final callback = Uri.encodeComponent('https://example.com/callback');
4040
final txUri = 'web+stellar:tx?xdr=$xdr&callback=$callback';
4141
final uri = wallet.parseSep7Uri(txUri);
42-
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
42+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
4343
```
4444

4545
```swift
@@ -51,12 +51,12 @@ let xdr = try tx.encodedEnvelope().addingPercentEncoding(withAllowedCharacters:
5151
let callback = "https://example.com/callback".addingPercentEncoding(withAllowedCharacters: .urlHostAllowed) // url encoded
5252
let txUri = "web+stellar:tx?xdr=\(xdr!)&callback=\(callback!)"
5353
let uri = try wallet.parseSep7Uri(uri: txUri)
54-
// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
54+
// uri can be parsed and transaction can be signed/submitted by an application that implements SEP-7
5555
```
5656

5757
</WalletCodeExample>
5858

59-
You can set replacements to be made in the xdr for specific fields by the application, these will be added in the [Sep-11 transaction representation format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) to the URI.
59+
You can set replacements to be made in the xdr for specific fields by the application, these will be added in the [SEP-11 transaction representation format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) to the URI.
6060

6161
<WalletCodeExample>
6262

@@ -153,7 +153,7 @@ const message = encodeURIComponent("pay me with lumens");
153153
const originDomain = "example.com";
154154
const payUri = `web+stellar:pay?destination=${destination}&amount=${amount}&memo=${memo}&msg=${message}&origin_domain=${originDomain}&asset_issuer=${assetIssuer}&asset_code=${assetCode}`;
155155
const uri = parseSep7Uri(payUri);
156-
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
156+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
157157
```
158158

159159
```dart
@@ -166,7 +166,7 @@ final message = Uri.encodeComponent('pay me with lumens');
166166
const originDomain = 'example.com';
167167
final payUri = 'web+stellar:pay?destination=$destination&amount=$amount&memo=$memo&msg=$message&origin_domain=$originDomain&asset_issuer=$assetIssuer&asset_code=$assetCode';
168168
final uri = Sep7.parseSep7Uri(payUri);
169-
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
169+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
170170
```
171171

172172
```swift
@@ -179,7 +179,7 @@ let message = "pay me with lumens".addingPercentEncoding(withAllowedCharacters:
179179
let originDomain = "example.com"
180180
let payUri = "web+stellar:pay?destination=\(destination)&amount=\(amount)&memo=\(memo)&msg=\(message!)&origin_domain=\(originDomain)&asset_issuer=\(assetIssuer)&asset_code=\(assetCode)"
181181
uri = try Sep7.parseSep7Uri(uri: payUri)
182-
// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
182+
// uri can be parsed and transaction can be built/signed/submitted by an application that implements SEP-7
183183
```
184184

185185
</WalletCodeExample>

docs/data/oracles/oracle-providers.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Oracles exist on the Stellar network to bring off-chain data onto the blockchain
1111

1212
The Reflector oracle protocol is a combination of specialized smart contracts and peer-to-peer consensus of data provider nodes maintained by trusted Stellar ecosystem organizations. Feeds include on-chain and off-chain asset prices, CEX & DEX exchange rates, foreign exchange rates, etc. Reflector nodes process, normalize, aggregate, and store trades information from Stellar Classic DEX, Soroban protocols, as well as external sources.
1313

14-
Publicly availble free price oracles are compatible with [SEP40](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0040.md) ecosystem standard interface. Learn how to integrate Reflector feeds [in their documentation](https://reflector.network/docs).
14+
Publicly availble free price oracles are compatible with [SEP-40](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0040.md) ecosystem standard interface. Learn how to integrate Reflector feeds [in their documentation](https://reflector.network/docs).
1515

1616
[Reflector Subscriptions](https://reflector.network/subscription) provide a service for user-defined customized triggers invoked automatically once the price change for a specified symbol reaches a certain threshold. When the condition is met, cluster nodes simultaneously push a notification to the WebHook URL provided in the subscription and publish an on-chain proof of the triggered event.
1717

docs/platforms/stellar-disbursement-platform/admin-guide/security.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ SDP enforces rate limiting at the HTTP layer to curb scripted abuse. Each unique
4141

4242
### Authentication and Authorization Models
4343

44-
All authenticated API routes require clients to present either an SDP-issued API key or a JWT derived from the SEP10/SEP24 flows. These two mechanisms run in parallel: JWTs are for interactive users, while API keys enable programmatic integrations with their own scoping model.
44+
All authenticated API routes require clients to present either an SDP-issued API key or a JWT derived from the SEP-10/SEP-24 flows. These two mechanisms run in parallel: JWTs are for interactive users, while API keys enable programmatic integrations with their own scoping model.
4545

4646
#### JWT Roles
4747

docs/tokens/publishing-asset-info.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -345,7 +345,7 @@ issuer="GAOO3LWBC4XF6VWRP5ESJ6IBHAISVJMSBTALHOQM2EZG7Q477UWA6L7U"
345345
display_decimals=7
346346
anchor_asset_type="crypto"
347347
anchor_asset="BTC"
348-
redemption_instructions="Use SEP6 with our federation server"
348+
redemption_instructions="Use SEP-6 with our federation server"
349349
collateral_addresses=["2C1mCx3ukix1KfegAY5zgQJV7sanAciZpv"]
350350
collateral_address_signatures=["304502206e21798a42fae0e854281abd38bacd1aeed3ee3738d9e1446618c4571d10"]
351351

docs/tools/developer-tools/anchor-tools.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ An application for interactively testing anchor services. Lets financial applica
1717

1818
### [Anchor Test Suite](https://anchor-tests.stellar.org/)
1919

20-
A test suite for validating SEP6, SEP24, SEP31 transfer servers.
20+
A test suite for validating SEP-6, SEP-24, SEP-31 transfer servers.

0 commit comments

Comments
 (0)