Address Libby's feedback.

src/components/AnnotatedCode.js

@@ -73,22 +73,15 @@ const Description = styled.div`
 `;
 
 const NoteOuter = styled.div`
+  background-color: #ffffc6;
   font-family: Consolas, Courier, monospace;
   margin-left: 0;
-  padding: 5px 0;
-`;
-
-const NoteNote = styled.div`
-  background-color: white;
-  display: inline-block;
-  margin-right: 10px;
-  padding: 0 10px;
+  padding: 5px 0 5px 20px;
 `;
 
 function Note({ children }) {
   return (
     <NoteOuter>
-      <NoteNote>note</NoteNote>
       {children}
     </NoteOuter>
   );
@@ -113,7 +106,7 @@ const pages = [
     preDescription: (
       <div>
         <p>
-          In the initial version of our smart contract, the <code>transfer</code> function checks that the sender authorized the transfer (by signing the transaction sent to the blockchain) and that they have sufficient funds. It then updates both the sending (<code>from</code>) and receiving (<code>to</code>) account balances.
+          In the initial version of our smart contract, the <code>transfer</code> function checks that the sender authorized the transfer (the transaction sent to the blockchain was signed by the sender) and that they have sufficient funds. It then updates both the sending (<code>from</code>) and receiving (<code>to</code>) account balances.
         </p>
         <p>
           Note that we start out with one property, using <code>row-enforced</code>. This states that the row indexed by <code>name</code> must have the keyset it contains (in its <code>ks</code> column) "enforced" in every possible code path. If the function's implementation enforces the keyset, the transaction will abort if it was not signed by "owner" of that row.

src/pages/introducing-the-pact-property-checker/index.md

@@ -20,7 +20,11 @@ Like most smart contract languages, Pact is deterministic (so that the same code
   (read users name))
 ```
 
-Here you can think of the `admins` *keyset* as a pre-published list of the public keys for all administrators of the smart contract.
+### Aside: keysets
+
+Here you can think of the `admins` *keyset* as a pre-published list of administrators of the smart contract.
+
+In general, a *keyset* is a set of users (public keys) authorized to perform some action. `enforce-keyset` checks that the current user matches a keyset. In this case we're checking that the user is an admin. One interesting feature of keysets in Pact is that they're first-class: they can be (e.g.) passed as arguments to a function or stored in the database.
 
 ## The state of smart contract security