little nits

stellar · Jun 7, 2024 · aac45f5 · aac45f5
1 parent 56e3e7f
commit aac45f5
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/docs/learn/encyclopedia/security/authorization.mdx b/docs/learn/encyclopedia/security/authorization.mdx
@@ -1,5 +1,5 @@
 ---
-title: Authorization
+title: Smart Contract Authorization
 sidebar_position: 10
 ---
 

diff --git a/docs/learn/encyclopedia/security/signatures-multisig.mdx b/docs/learn/encyclopedia/security/signatures-multisig.mdx
@@ -5,6 +5,12 @@ sidebar_position: 20
 
 import { CodeExample } from "@site/src/components/CodeExample";
 
+:::note
+
+This section details signing non-smart contract transactions. For auth related to smart contract transactions, see [authorization](./authorization.mdx)
+
+:::
+
 Signatures are authorization for transactions on the network. Transactions always need authorization from at least one public key to be valid and generally, the signature comes from the source account. Sometimes transactions require more signatures, which we’ll get into in the multisig section.
 
 Transaction signatures are created by signing the transaction object contents with a secret key. Stellar uses the ed25519 signature scheme, but there is also a mechanism for adding additional types of public and private key schemes. A transaction with an attached signature is considered to have authorization from that public key.