docs: minor - accept suggested edits

Co-authored-by: Nana Essilfie-Conduah <56320167+Nana-EC@users.noreply.github.com>
Signed-off-by: Brendan Graetz <bguiz@users.noreply.github.com>

Author: bguiz

HIP/hip-792.md

@@ -98,7 +98,7 @@ within "complex" keys **should** be supported, as noted in
 
 > Note that when a Key is a smart contract ID,
 > it doesn't mean the contract with that ID will actually create a cryptographic signature.
-> It only means that when the contract calls a precompiled contract,
+> It only means that when the contract calls a system contract function,
 > the resulting "child transaction" will be authorized to perform any action controlled by the Key.
 
 Therefore this HIP proposes a means, via the `hederaAccountSystem` system contract,
@@ -246,6 +246,7 @@ which demonstrates this HIP, with both happy path and error path examples.
 This will be in the style of existing work:
 
 - [Multisig Account](https://github.com/hedera-dev/hedera-code-snippets/tree/main/multisig-account)
+- [Multisig Smart Contract Account](https://github.com/hedera-dev/hedera-code-snippets/tree/main/multisig-sc-account)
 
 Provide sufficient warnings about improper use of `isAuthorizedCurrentTransaction` in a tutorial,
 at minimum including a list of "Do's and Don'ts".