diff --git a/_posts/2018-07-13-whats-new-in-sapling.md b/_posts/2018-07-13-whats-new-in-sapling.md
index 2bc83ca..3f873aa 100644
--- a/_posts/2018-07-13-whats-new-in-sapling.md
+++ b/_posts/2018-07-13-whats-new-in-sapling.md
@@ -29,7 +29,7 @@ The increased use of shielded addresses will improve the effective privacy for t
 <h4>Changes</h4>
 All shielded transactions require the creation of a <a href="https://z.cash/technology/zksnarks.html">zero-knowledge proof</a>. Today, the hardware that constructs the proof must also be in possession of the spending key that authorizes the transaction. Sapling changes this by allowing the hardware that constructs the proof to be independent from the hardware that signs for the transaction.
 <h4>Implications</h4>
-Enterprises can perform an inexpensive signature step in a trusted environment while allowing a another computer, not trusted with the spending key, to construct the proof. Additionally, hardware wallets can support shielded addresses by allowing the connected computer to construct the proof without exposing the spending key to that machine.
+Enterprises can perform an inexpensive signature step in a trusted environment while allowing another computer, not trusted with the spending key, to construct the proof. Additionally, hardware wallets can support shielded addresses by allowing the connected computer to construct the proof without exposing the spending key to that machine.
 <h2>Improved keys</h2>
 <h4>Changes</h4>
 Shielded addresses currently support an <a href="https://blog.z.cash/viewing-keys-selective-disclosure/">incoming viewing key</a>. The holder of an incoming viewing key for a shielded address are able to see the value of all incoming transactions and the memo field. They cannot see the sending address and cannot spend the funds.