Here is a recapitulation of the items from the outermost read me that apply specifically to Leverage version 3.0 itself, as opposed to the supporting files.  Be sure to read addendum four on new Leverage 3.0 features.

Brand New Features
------------------
Features that have somehow escaped being documented in an addendum:

Modem connections are supported for import and export.  Of course, something has to be on the other end of the line waiting for the call.  The MicroPhone folder includes a Leverage Modem Server settings file similar to the Leverage ADSP Server settings file.  See the Read Me in the Connection:Microphone:MPPro folder for information.

If the current database includes a bar code field, scanning a bar code while the Go dialog is up places the bar code input into the Go dialog.  This is useful for quickly moving to records indexed by large serial numbers, for example.  The indexed field (the one you're "Go"ing on) doesn't have to be a bar code field itself, but there does have to be a bar code field in the database.

Things you shouldn't try:
----------------------
You are advised that the "Assimilate" selection from the Action button is for thrill seekers only.  You will search in vain for documentation.  The user interface for this feature is inadequate for most uses.

Don't use colons (':') in field names (e.g., don't call a time string "HH:MM" or a blood pressure field "Sys:Dia") as it will cause confusion with multifield indices.  You also shouldn't use slashes in field names (e.g., "Sys/Dia") since it will confuse smart links (if they're so smart, how come they get confused?)  Of course, you can live without smart links, so this may not be a problem, but any use of colons in a field name will cause trouble with sorting on that field.

The following installation/deinstallation sequence will annoy Leverage:
1. install Leverage on a card,
2. erase Leverage (without removing databases),
3. remove card,
4. install Leverage internally
5. put card back in
Leverage will recreate the internal databases in step 4, so there will be duplicates after step 5.  This is not fatal, but it will probably cause Leverage to complain about internal database definitions being corrupted when it starts.  The error message is benign, but becomes irksome after a few weeks.  If you install Leverage on a card and later decide you would rather have it installed internally, you should erase all databases before removing Leverage.  Of course, if you have data you don't want to lose you'll want to export it first (see Chapter 13 of the Leverage Reference) so you can import it back into Leverage after it is installed where you want it.

It is best not to cancel a database modification after changes have been made to link options (specifically SmartLinks) since these changes will not be undone properly.  If it is necessary to cancel changes, you will probably need to go into expert mode, remove the appropriate records from the _links database, and then re-add them in the Modify Database dialog (or you could correct them by hand, but this is fraught with peril).

Fields connected by smart links should be of the same type.  It would probably be nice of Leverage to automatically convert as needed (or at least warn you of mismatches), but it does not do so.  Even something as apparently reasonable as linking a real and an integer field is unlikely to behave as desired.

Known bugs and misfeatures:
--------------------------
You cannot transfer note fields from Newton to Newton yet (i.e., export a database with note fields from Leverage on one Newton and import it into Leverage on another Newton).  You can beam (or email) individual records that include notes, however.

Adds to the _tables database will sometimes fail during import to Leverage (producing a Leverage Add Failed notification on the Newton.)  This problem is due to a bug in the Newton OS regarding the handling of duplicate keys.  A likely candidate would be a very large table since table elements are indexed by table name, so every element in a table has the same key value.  Apple is working on a resolution.

Leverage sometimes fails to ask whether to add a value to a table when a new value is entered and you have "Ask whether to add" checked for that table field.  In particular, selecting a value from the pop-up list and then appending text to the end of the value by writing into the field usually exhibits this behavior.  The data is stored correctly in the record and the table is not damaged, although the pop-up list is confused.

The "Go" button works with multi-field indices, but you can only go based on the value of the first field in the index.

You can use 8-bit characters (i.e., accented characters, characters with diacritical marks such as an umlaut) in field names, but, since NewtonScript is a 7-bit language, such fields cannot then be used in code.