Skip to content

Commit 66b25a0

Browse files
authored
Merge pull request #337 from onflow/fix-example-link
Update index.mdx
2 parents a599c0d + e71dc61 commit 66b25a0

1 file changed

Lines changed: 5 additions & 8 deletions

File tree

docs/index.mdx

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The Go SDK library uses HTTP or gRPC APIs to communicate with the access nodes a
4646
The library provides default factories for connecting to Flow AN APIs and you can easily switch between HTTP or gRPC if you use the provided client interface.
4747

4848
You can check more examples for creating clients in the examples:
49-
**[<img src="https://raw.githubusercontent.com/onflow/sdks/main/templates/documentation/try.svg" width="130" />](https://github.com/onflow/flow-go-sdk/blob/master/examples/rest_grpc_clients/main.go)**
49+
**[<img src="https://raw.githubusercontent.com/onflow/sdks/main/templates/documentation/try.svg" width="130" />](https://github.com/onflow/flow-go-sdk/blob/master/examples/http_grpc_clients/main.go)**
5050

5151
Basic Example:
5252
```go
@@ -452,7 +452,7 @@ Flow, like most blockchains, allows anybody to submit a transaction that mutates
452452
Transaction data is composed and signed with help of the SDK. The signed payload of transaction then gets submitted to the access node API. If a transaction is invalid or the correct number of authorizing signatures are not provided, it gets rejected.
453453

454454
Executing a transaction requires couple of steps:
455-
- [Building transaction](#build-transactions).
455+
- [Building transaction](#build-the-transaction).
456456
- [Signing transaction](#sign-transactions).
457457
- [Sending transaction](#send-transactions).
458458

@@ -586,15 +586,15 @@ func main() {
586586
}
587587
```
588588

589-
After you have successfully [built a transaction](#build-transactions) the next step in the process is to sign it.
589+
After you have successfully [built a transaction](#build-the-transaction) the next step in the process is to sign it.
590590

591591
### Sign Transactions
592592
[<img src="https://raw.githubusercontent.com/onflow/sdks/main/templates/documentation/ref.svg" width="130" />](https://pkg.go.dev/github.com/onflow/flow-go-sdk#Transaction.SignEnvelope)
593593

594594
Flow introduces new concepts that allow for more flexibility when creating and signing transactions.
595595
Before trying the examples below, we recommend that you read through the [transaction signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/).
596596

597-
After you have successfully [built a transaction](#build-transactions) the next step in the process is to sign it. Flow transactions have envelope and payload signatures, and you should learn about each in the [signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/#anatomy-of-a-transaction).
597+
After you have successfully [built a transaction](#build-the-transaction) the next step in the process is to sign it. Flow transactions have envelope and payload signatures, and you should learn about each in the [signature documentation](https://docs.onflow.org/concepts/accounts-and-keys/#anatomy-of-a-transaction).
598598

599599
Quick example of building a transaction:
600600
```go
@@ -876,7 +876,7 @@ err = tx.SignEnvelope(account2.Address, key4.Index, key4Signer)
876876
### Send Transactions
877877
[<img src="https://raw.githubusercontent.com/onflow/sdks/main/templates/documentation/ref.svg" width="130" />](https://pkg.go.dev/github.com/onflow/flow-go-sdk/client#Client.SendTransaction)
878878

879-
After a transaction has been [built](#build-transactions) and [signed](#sign-transactions), it can be sent to the Flow blockchain where it will be executed. If sending was successful you can then [retrieve the transaction result](#get-transactions).
879+
After a transaction has been [built](#build-the-transaction) and [signed](#sign-transactions), it can be sent to the Flow blockchain where it will be executed. If sending was successful you can then [retrieve the transaction result](#get-transactions).
880880

881881

882882
**[<img src="https://raw.githubusercontent.com/onflow/sdks/main/templates/documentation/try.svg" width="130" />](https://github.com/onflow/flow-go-sdk/blob/master/examples/send_transactions/main.go)**
@@ -1014,9 +1014,6 @@ The example above uses an ECDSA key pair on the P-256 (secp256r1) elliptic curve
10141014
This is an example of how to construct a FLOW token transfer transaction
10151015
with the Flow Go SDK.
10161016

1017-
Before using this example, read the [Build a Transaction guide](../building-transactions)
1018-
for a general overview of how Flow transactions are constructed.
1019-
10201017
## Cadence Script
10211018

10221019
The following Cadence script will transfer FLOW tokens from a sender

0 commit comments

Comments
 (0)