Hi,
The note tells about AlwaysOn which runs on WFCS framework but, it is not the usual SQL Server installed as a Failover Cluster. Please save some time to read the blog series about AlwaysOn: http://blogs.msdn.com/b/saponsqlserver/archive/tags/alwayson/
Log Shipping would be a solution for example in case you were running SQL Server 2008 R2 or early versions. With AlwaysOn you can create an Availability Group, set a listener and set your primary and secondary replicas.
The secondary replicas can be either synchronous (required for automatic failover) and the asynchronous (which is similar to the database mirroring).
You can perform automatic failover between the Synchronous replicas (SQL Server 2012-2014 allows 2 synchronous replicas to failover automatically between then, SQL Server 2016 will increase to 3), and the asynchronous secondary replicas can only be failed over manually, as they're not always synchronized.
Each replica (node) has its own storage and doesn't share with the others.
You can use the other replicas to perform jobs like log Backups and full backup (copy only), as well run some jobs that doesn't alter data.
It requires some time to study, plan and deploy, but you can be like invincible with AlwaysOn.
But in case you want to stick with Log shipping and other methods of DR with SQL Server, you can refer to notes 965908 and 2021980.
Best Regards,
Luis Darui