During the import process, CiviMember and Core CiviCRM are very picky about the difference between 01 and 1. For instance, dates reading 1/1/2008 will not be accepted or understood by CiviCRM. On the other hand 01/01/2008 will be understood. This is very inconvenient, especially when Microsoft Excel 2003 is a common format many of my clients store their data in, and 01/01/2008 is not a valid date formatting option. Please consider modifying the import function to deal with more date functions, or at the very least provide some single-digit dates in your examples so that it is more clear to the user what is required. For instance 12/25/2008 is not a good example because that does not clarify that CiviCRM needs leading zeros to function properly. 01/01/2008 would be a better example.