From aac45f541489a5244fe87559c0165176701f7c42 Mon Sep 17 00:00:00 2001
From: Bri <92327786+briwylde08@users.noreply.github.com>
Date: Fri, 7 Jun 2024 11:17:03 -0600
Subject: [PATCH] little nits

---
 docs/learn/encyclopedia/security/authorization.mdx       | 2 +-
 docs/learn/encyclopedia/security/signatures-multisig.mdx | 6 ++++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/learn/encyclopedia/security/authorization.mdx b/docs/learn/encyclopedia/security/authorization.mdx
index 6af3d42aa..cecbee532 100644
--- 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
index 99212d338..29f4db72d 100644
--- 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.