The solution will work, however, to avoid something like this in the future you could number them differently.  Instead of numbering them 1, 2, 3, 4.... you can number them...

If you backup & restore database yyy it will automatically shrink the transaction log, or you can run this script which should work as well:

USE master

declare @dbname nvarchar(255)

set @dbname =...

AppDev has good training CDs, although they can be pretty expensive.