1st enabled will be the default one so rename the config file of the default vhost to something like 00-config_file_name
so it is the 1st loaded.
As you (rightfully) would like something documented:
From Apache docs: An In-Depth Discussion of Virtual Host Matching
Name-based vhost
If the entry corresponds to a name-based vhost the name list contains one or more vhost structures. This list contains the vhosts in the same order as the VirtualHost directives appear in the config file.
The first vhost on this list (the first vhost in the config file with the specified IP address) has the highest priority and catches any request to an unknown server name or a request without a Host: header field.
If the client provided a Host: header field the list is searched for a matching vhost and the first hit on a ServerName or ServerAlias is taken and the request is served from that vhost. A Host: header field can contain a port number, but Apache always matches against the real port to which the client sent the request.
So if you use only 1 config file for your vhosts, you need to order them in the file and if you include several separated files (including ../sites-enabled directory which is the way Apache2 sample site is defined) you need to load the files in the order you need to define the default site first and they are loaded according to the directory alphabetical order.
Always according to the same Apache doc (following examples link in the page), if you use _default_
vhost, it must be defined before other vhosts and that's exactly what you will be doing defining the vhost in the order you want but when using _default_
vhost, the main server will not respond anymore to requests.