From 2bce1a7baefe6b90a0c1f4f965e6408af8a98e4b Mon Sep 17 00:00:00 2001 From: Pavel Voronin Date: Tue, 16 Mar 2021 14:32:43 +0300 Subject: [PATCH] fix typo (#8891) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> --- docs/intro/sdk-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/intro/sdk-design.md b/docs/intro/sdk-design.md index d9629a3abd..4d31fbbbc2 100644 --- a/docs/intro/sdk-design.md +++ b/docs/intro/sdk-design.md @@ -15,7 +15,7 @@ Here is a simplified view of how transactions are handled by an application buil ## `baseapp` -`baseapp` is the boilerplate implementation of a Cosmos SDK application. It comes with an implementation of the ABCI to handle the connexion with the underlying consensus engine. Typically, a Cosmos SDK application extends `baseapp` by embedding it in [`app.go`](../basics/app-anatomy.md#core-application-file). See an example of this from the SDK application tutorial: +`baseapp` is the boilerplate implementation of a Cosmos SDK application. It comes with an implementation of the ABCI to handle the connection with the underlying consensus engine. Typically, a Cosmos SDK application extends `baseapp` by embedding it in [`app.go`](../basics/app-anatomy.md#core-application-file). See an example of this from the SDK application tutorial: +++ https://github.com/cosmos/sdk-tutorials/blob/c6754a1e313eb1ed973c5c91dcc606f2fd288811/app.go#L72-L92