From e4e2e990e1c4e9f6d59792acc4e8d3b02029256c Mon Sep 17 00:00:00 2001
From: 1HXb9KMAtwNJqz4egi6hJx08EQgJajiBTH
 <1HXb9KMAtwNJqz4egi6hJx08EQgJajiBTH@reference.cash>
Date: Thu, 2 Jan 2020 11:04:10 -0500
Subject: [PATCH] wiki commit

---
 .../transaction-validation/network-level-validation-rules.md  | 4 +++-
 protocol/blockchain/transaction/locking-script.md             | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/protocol/blockchain/transaction-validation/network-level-validation-rules.md b/protocol/blockchain/transaction-validation/network-level-validation-rules.md
index 54fe474..b0c0e3e 100644
--- a/protocol/blockchain/transaction-validation/network-level-validation-rules.md
+++ b/protocol/blockchain/transaction-validation/network-level-validation-rules.md
@@ -12,8 +12,10 @@ Standard transactions are those that:
  - Have input scripts that only contain push operations
  - Have input scripts with unlocking scripts below the 1650 byte maximum
  - Have at most one [data output](/protocol/blockchain/transaction/locking-script#Data%20Output)
+ - For [multisig](/protocol/blockchain/transaction/locking-script#Multisig) outputs, must have at most 3 parties and at least 1 required party (i.e. 1-of-1 through 3-of-3).
  - Have non-data outputs with amount above the [dust](#dust) threshold
 
 Be aware, however, that these rules may vary from node-to-node as they are often configurable.  Some nodes may also accept and relay non-standard transactions.  For this reason, among others, it is always wise to send transactions to multiple nodes.
 
-### Dust
\ No newline at end of file
+### Dust
+
diff --git a/protocol/blockchain/transaction/locking-script.md b/protocol/blockchain/transaction/locking-script.md
index 17522ff..11b3703 100644
--- a/protocol/blockchain/transaction/locking-script.md
+++ b/protocol/blockchain/transaction/locking-script.md
@@ -84,7 +84,7 @@ One drawback of this is that it is not possible to determine whether certain ins
 This makes retirement of opcodes impossible.
 However, it's also possible for people to create transactions and not commit them to the blockchain, so the viability of opcode retirement is questionable anyway.
 
-### Multisig Script
+### Multisig
 
 Multiple-signature, or multisig, scripts provide a mechanism to have multiple private keys coordinate with spending funds.
 For example, three people could share funds and require that for some transactions any one of them could spend it while, for others, two of them would need to agree, and for others still, all three people would need to agree to spend the funds.