Personally, I wouldn't worry about it. There is no ISO standard definition for a shakeout test for software. People have all kinds of terms for distinguishing one kind of testing from another but everyone uses them differently. It's more important to understand that how you test depends on your goals (e.g. accepting a customized product before writing a big check, making sure a change works before you check it in to your version control system, or making sure a build installs and performs essential functions before you unleash your entire test team on it) and circumstances (e.g. product has been completely rewritten, an independent subsystem was refactored but its interface did not change, or a developer made a small, isolated tweak that feels low-risk because you reviewed the source code).
Names are just names. In our business, what matters is understanding why you do what you do.