diff --git a/bip-0380.mediawiki b/bip-0380.mediawiki
index eea5ce14..a6a147b4 100644
--- a/bip-0380.mediawiki
+++ b/bip-0380.mediawiki
@@ -31,13 +31,13 @@ Given just the private keys, it is not possible for restored wallets to know whi
 This has lead to incompatibilities between wallets when restoring a backup or exporting data for a watch only wallet.
 
 Further complicating matters are BIP 32 derivation paths.
-Although BIPs 44, 49, and 84 have specified standard BIP 32 derivation paths for different output scripts and addresses, not all wallets support them nor use those derivation paths.
+Although BIPs 44, 49, and 84 have specified standard BIP 32 derivation paths for different output scripts and addresses, not all wallets support those derivation paths nor use them.
 The lack of derivation path information in these backups and exports leads to further incompatibilities between wallets.
 
 Current solutions to these issues have not been generic and can be viewed as being layer violations.
 Solutions such as introducing different version bytes for extended key serialization both are a layer violation (key derivation should be separate from script type meaning) and specific only to a particular derivation path and script type.
 
-Output Script Descriptors introduces a generic solution to these issues.
+Output Script Descriptors introduce a generic solution to these issues.
 Script types are specified explicitly through the use of Script Expressions.
 Key derivation paths are specified explicitly in Key Expressions.
 These allow for creating wallet backups and exports which specify the exact scripts, subscripts (redeemScript, witnessScript, etc.), and keys to produce.
@@ -75,7 +75,7 @@ Key expressions consist of:
 ** Followed by zero or more <tt>/NUM</tt> or <tt>/NUMh</tt>  path elements to indicate the unhardened or hardened derivation steps between the fingerprint and the key that follows.
 ** A closing bracket <tt>]</tt>
 * Followed by the actual key, which is either:
-** A hex encoded public key, which depending the script expression, may be either:
+** A hex encoded public key, which depending on the script expression, may be either:
 *** 66 hex character string beginning with <tt>02</tt> or <tt>03</tt> representing a compressed public key
 *** 130 hex character string beginning with <tt>04</tt> representing an uncompressed public key
 ** A [[https://en.bitcoin.it/wiki/Wallet_import_format|WIF]] encoded private key