I would suggest;
Get a coffee. Coffee's good.
Do your daily routine checks just in case there's actually something wrong. Rather than SQL Server doing exactly what it's supposed to do.
Drink coffee.
Lots of interesting and important to know stuff in there. You may actually even, as a result of going through this, find stuff you actually need to worry about.
HTH
EDIT - reply to wrong post. Argh, who's this clown to give advice, eh?
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.