The information in that article simply alludes to the fact that you can create more than one log file. As you've stated, and as reported in Microsoft's own documentation,
Having multiple log files in a database does not enhance performance
in any way, because the transaction log files do not use proportional
fill like data files in a same filegroup.
As for reasons why someone might have multiple log files:
- You may have filled your log drive and need to add an additional log file on another drive to allow for additional growth.
- You may be preparing for an activity that will cause substantial, but temporary, log growth. In this instance, capping your existing log file and adding a new one (on a new drive for example) can be a cleaner solution when you go to clean up the excess usage at a later date.
- You may have limited space on high-performance disks, which is enough for your usual operational load, but you require additional space capacity for periodic workloads that can be on lower performance disks. In this instance, having your first log file limited and stored on the high-performance disks would give you the best performance during normal operational workloads, with space capacity during periodic workloads pushed to the additional log files on slower disks.
There are probably plenty of additional scenarios where additional log files could be useful, the key thing to remember is that additional log files do not aid performance, but are possible if required.