minor edits

README.TXT

 shall we say, user-friendly. So you may find what you have to do to make it work somewhat
 awkward. 
 
-Then, you should read thru the code seeing how the code actually implements the things you 
+Then, you should read thru the code repository seeing how the code actually implements the things you 
 see when you run the code. Find the "main" routine, which is where the app starts up. Trace from there
 to see what code gets called where and when. Trace how the operations of the code work.
 
 
 Notice when reading the code...
 
-- Each account has: id, name, email, balance
+- Each account has: id, name, email, balance; find that in a class.
 - What does Premium account do that Basic does not?
 - What are the two starter account already built into the project?
-- Trace how the Cash machine sets the account
+- Trace how the Cash machine sets the current account
+-- enter account id and "login to account"
 - Trace how a deposit happens
 -- enter a number then click deposit
 - Trace how a withdrawal happens
 -- enter a number then click withdraw
 - How does "exit" log out of the account?
+- What might be a better name for "exit"?
 
 
 Things to Change for the Lab
 
      After getting each of these items completed, 
      be sure to do a 'git commit' to save you work. 
+     Learn your git.
      Never Lose Code. 
      NEVER LOSE CODE. EVER. :-)
 
   * Make the login stuff more clear
   * Disable the three buttons that operate on an account until a login happens 
   * and then enable them. add another TextField for the amount entries. 
-  * Make it different from the fieldwhere you set the account ID.
+  * Make it different from the TextField where you set the account ID.
 
 * Enable the amount entries to be floating point numbers instead of 
   just integers when doing deposits and withdrawals.

README.md

 launches a window on your computer and lets you play with a couple of "banking accounts".
 You should run the app, learn how to use it, so you understand what it does. It is not,
 shall we say, user-friendly. So you may find what you have to do to make it work somewhat
-awkward. 
+awkward.
 
-Then, you should read thru the code seeing how the code actually implements the things you 
-see when you run the code. Find the "main" routine, which is where the app starts up. Trace from there
-to see what code gets called where and when. Trace how the operations of the code work.
+Then, you should read thru the code repository seeing how the code actually implements the 
+things you see when you run the code. Find the "main" routine, which is where the app 
+starts up. Trace from there to see what code gets called where and when. Trace how the 
+operations of the code work.
 
 Finally, you are to add some new functionality to the app, to make it "more useful, powerful &
-more rewarding for the user". 
+more rewarding for the user".  
 Your effort will be met with promotions, parades, and stock options. (no, just kidding).
 
 ## Lab Brief