More https changes in the docs

docs/boot-ipxe.md

@@ -5,7 +5,7 @@
 If you've already compiled your own iPXE, you can load up the netboot.xyz menu easily by entering CTRL-B when prompted setting DHCP and then chainloading iPXE:
 
     dhcp
-    chain --autofree http://boot.netboot.xyz
+    chain --autofree https://boot.netboot.xyz
 
 If you don't have DHCP on your network, you can manually set your network information:
 
@@ -14,4 +14,4 @@ If you don't have DHCP on your network, you can manually set your network inform
     set net0/gateway <gateway>
     set dns <nameserver>
     ifopen net0
-    chain --autofree http://boot.netboot.xyz
+    chain --autofree https://boot.netboot.xyz

docs/boot-iso.md

@@ -1,7 +1,7 @@
 ### Booting from ISO
 
 #### Burning a CD/DVD
-To create a bootable CD-ROM/DVD, burn the ISO image [netboot.xyz-dhcp.iso](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.iso) if you have DHCP or [netboot.xyz-static.iso](http://boot.netboot.xyz/ipxe/netboot.xyz-static.iso) if you require manual entry (~1MB in size) to a blank CD-ROM/DVD.  Insert the media into the server, set the proper boot order and boot up.
+To create a bootable CD-ROM/DVD, burn the ISO image [netboot.xyz-dhcp.iso](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.iso) if you have DHCP or [netboot.xyz-static.iso](https://boot.netboot.xyz/ipxe/netboot.xyz-static.iso) if you require manual entry (~1MB in size) to a blank CD-ROM/DVD.  Insert the media into the server, set the proper boot order and boot up.
 
 #### Virtual Machine Software
 You can also use these ISOs to boot any sort of VM in Citrix XenServer, VMware ESXi, VMware Fusion, VirtualBox. 

docs/boot-tftp.md

@@ -3,7 +3,7 @@
 If you want to utilize netboot.xyz from your home or office network, it's relatively easy to set up.  It will allow all of your devices on your network to have netboot.xyz available whenever you need it by just changing the boot order on your device, selecting network boot, or manually selecting the device to boot.
 
 #### DHCP Server Setup
-You will have to tell your DHCP server to provide a "next-server", the address of a TFTP server on your network, and a "filename", the [netboot.xyz DHCP boot file](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe).  When your clients boot up, if they are set to network boot, they'll automatically get a valid DHCP address, pull down the netboot.xyz iPXE bootloader and load up the Operating System menu.  
+You will have to tell your DHCP server to provide a "next-server", the address of a TFTP server on your network, and a "filename", the [netboot.xyz DHCP boot file](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe).  When your clients boot up, if they are set to network boot, they'll automatically get a valid DHCP address, pull down the netboot.xyz iPXE bootloader and load up the Operating System menu.  
 
 Example:
 
@@ -22,5 +22,5 @@ If you use dnsmasq you can add this configuration to /etc/dnsmasq.conf:
 
 #### Regular and Undionly Boot Files
 
-If you experiencing issues with the regular [netboot.xyz-dhcp.kpxe](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe) bootloader, you can try and use the [netboot.xyz-dhcp-undionly.kpxe](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp-undionly.kpxe) bootloader.  The regular bootloader includes common NIC drivers in the iPXE image, while the undionly loader will piggyback off the NIC boot firmware.
+If you experiencing issues with the regular [netboot.xyz-dhcp.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.kpxe) bootloader, you can try and use the [netboot.xyz-dhcp-undionly.kpxe](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp-undionly.kpxe) bootloader.  The regular bootloader includes common NIC drivers in the iPXE image, while the undionly loader will piggyback off the NIC boot firmware.
  

docs/boot-usb.md

@@ -4,8 +4,8 @@
 
 Download a netboot.xyz USB disk:
 
-* [dhcp](http://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.usb) - Automatically detects your networking
-* [static](http://boot.netboot.xyz/ipxe/netboot.xyz-static.usb) - Prompts for manual entry of your networking information
+* [dhcp](https://boot.netboot.xyz/ipxe/netboot.xyz-dhcp.usb) - Automatically detects your networking
+* [static](https://boot.netboot.xyz/ipxe/netboot.xyz-static.usb) - Prompts for manual entry of your networking information
 
 ### Creating USB Key on Linux
 

docs/faq.md

@@ -16,7 +16,7 @@ You can read more about my thoughts and possible solutions [here](https://www.re
 #### My distribution uses ISOs for delivery, how can I see if they work?
 You can do a quick check by loading up netboot.xyz in a virtual environment baremetal.  Make sure you have plenty of RAM as you are loading the ISO into RAM.  Then select the iPXE command line and enter the following;
 
-    kernel http://boot.netboot.xyz/memdisk iso raw
+    kernel https://boot.netboot.xyz/memdisk iso raw
     initrd http://url/to/iso
     boot
 

docs/usage-digitalocean.md

@@ -10,7 +10,7 @@ Tests were done using a [Fedora 23](https://getfedora.org) instance on [Digital
 
 #### Download an iPXE linux kernel
 
-Obtain an iPXE generic kernel [here](http://boot.netboot.xyz/ipxe/generic-ipxe.lkrn) or [compile your own](http://ipxe.org/download) and save it to /boot/generic-ipxe.lkrn.
+Obtain an iPXE generic kernel [here](https://boot.netboot.xyz/ipxe/generic-ipxe.lkrn) or [compile your own](http://ipxe.org/download) and save it to /boot/generic-ipxe.lkrn.
 
 #### Create a netboot.xyz initrd file
 
@@ -26,7 +26,7 @@ Save as /boot/netboot.xyz-initrd (replace your networking information where appr
     set net0/gateway <instance public gateway>
     set dns <instance dns address>
     ifopen net0
-    chain --autofree http://boot.netboot.xyz
+    chain --autofree https://boot.netboot.xyz
 
 #### Add a Grub2 custom entry
 

docs/usage-rackspace.md

@@ -2,4 +2,4 @@
 
 See [boot.rackspace.com](http://boot.rackspace.com) for now.  You can chain to netboot.xyz from there:
 
-    chain --autofree http://boot.netboot.xyz
+    chain --autofree https://boot.netboot.xyz