Explanation/Reference:
Explanation:
Box1: New-SPWOBIBinding
The New-SPWOPIBinding cmdlet associates file name extensions or applications to actions on the current SharePoint farm where this cmdlet is run. Each binding allows you to use the WOPI application to view or edit files in your SharePoint library.
To use a WOPI application, such as a server that runs Office Web Apps Server, for Office Web Apps, you must run this cmdlet on the SharePoint farm before you can use the Office Web Apps.
Example: New-SPWOPIBinding -ServerName "Server.corp.Contoso.com"
This example creates bindings for all the applications and file name extensions that the WOPI application supports on the current SharePoint farm where this cmdlet is run.
Box 2: Get-SPWOPIZone
The Get-SPWOPIZone returns the zone that is configured on the current SharePoint farm for the WOPI application (such as a server that runs Office Web Apps Server) to use.
Box 3: Set-SPWOPIZone
The Set-SPWOPIZone cmdlet configures the zone that the current SharePoint farm will use to navigate the browser to the WOPI application (such as a server that runs Office Web Apps Server). The SharePoint Server page in the browser creates a frame that contains a page on the WOPI application. The zone for the URL of the WOPI application page is determined by this setting.
Box 4: external-https
If you have a SharePoint farm that's internal and external as in this scenario, we must specify external.
We must use secure communication, https not http. Only use HTTP when you are on a fully secure network that uses IPSEC (full encryption) or in a test environment that does not contain sensitive data.
Example:
Set-SPWOPIZone -Zone "external-https"
This example configures the current SharePoint farm to use external connections through HTTPS to the WOPI application (such as a server that runs Office Web Apps Server).
Reference: https://technet.microsoft.com/en-us/library/jj219441.aspx
https://technet.microsoft.com/en-us/library/jj219451.aspx