This change doesn't seem to be right. With the new version I'm getting a bogus warning telling me to change wp-content to mode 755, even though it's already mode 755.
This appears to be happening because the code does:
if( is_writable( ABSPATH . 'wp-content/' ) )
... then tells people to chmod 755 if so.
However, decent hosting companies run PHP scripts under the individual user's unique UID in the first place, meaning that it's perfectly possible for a mode 755 directory to be writable by the script. In other words, is_writable() doesn't necessarily mean the directory has been left as mode 777.
If you're trying to check whether the directory has been left as world-writable on a lame hosting company that uses shared uids (and where leaving it world-writable would therefore be a security risk), which is a good idea, it should probably do something like this instead (untested):
if( fileperms( ABSPATH . 'wp-content/' ) & 0x0022 )
That will tell you if it's world- or group-writable, I think.
Thanks for the great plugin!