It's not technically a memory leak though. It's more to do with finding errors in your code that use unexpectedly large quantities of memory. But since everything is being allocated and deallocated correctly, you're not actually leaking any memory (which I guess you could argue, makes the article even more basic).

In any case, you're right that the title is a little misleading, but pedantry aside, it's still a useful resource.