[Cryptech-Commits] [user/ln5/tamper] 03/05: Minor updates of README.

[git at cryptech.is]

This is an automated email from the git hooks/post-receive script.

linus at nordberg.se pushed a commit to branch master
in repository user/ln5/tamper.

commit 104c1c41f09fb3a1e7ed852bd14dd03c225308b8
Author: Linus Nordberg <linus at nordberg.se>
AuthorDate: Fri Jun 10 16:01:21 2016 +0200

    Minor updates of README.
---
 README.md | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/README.md b/README.md
index 8dd2b77..a36367d 100644
--- a/README.md
+++ b/README.md
@@ -25,16 +25,17 @@ board, rev02, implementing tamper detection and master key erasure.
 
 The MKM holds the master key for the device.
 
-The AVR, MKM and the mux are battery powered.
+The AVR, MKM and the mux are all battery powered.
 
-The AVR and the FPGA are sharing access to the MKM through the mux,
-with the AVR connected to the pins used for deciding who's in control
-of the memory. The FPGA is in control by default.
+The AVR and the FPGA are both sharing access to the MKM through the
+mux, with the AVR connected to the pins used for deciding who's in
+control of the memory. If the AVR doesn't actively grab control of the
+MKM, the FPGA is in control.
 
-When the panic button is pressed, the AVR grabs the MKM and writes
-zeros to it as quickly as possible. In idle mode, i.e. when the panic
-button is not pressed, the AVR tries to consume as little power as
-possible.
+When the panic button is pressed, the AVR takes control over the MKM
+and writes zeros to it as quickly as possible. In idle mode, i.e. when
+the panic button is not pressed, the AVR tries to consume as little
+power as possible.
 
 ## Building the software
 
@@ -58,10 +59,10 @@ this directory could be appended to avrdude.conf:
 
     cat attiny828.conf >> /etc/avrdude.conf
 
-Often, a piece of hardware often called an SPI programmer is needed in
-order to upload the .hex file. The one I've been using has
-"sparkfun.com" printed on it. This small board has a mini-USB port to
-connect to a host system and a header with SPI pins to connect to a
+Often, a piece of hardware called "SPI programmer" is needed in order
+to upload the .hex file to the target system. The one I've been using
+has "sparkfun.com" printed on it. This small board has a mini-USB port
+to connect to a host system and a header with SPI pins to connect to a
 board with an AVR on it.
 
 To upload a .hex file to a board, use the upload.sh shell script in
@@ -71,4 +72,3 @@ this directory with the name of the file as the only argument:
 
 Depending on permissions on your host system you might want to run the
 upload script as root.
-