fix a bunch of typos found on website (#1517)

cmd/minimega/cc_cli.go

@@ -88,7 +88,7 @@ Users can also filter by any column in "vm info" using a similar syntax:
 	cc filter name=server
 	cc filter vlan=DMZ
 
-"vm info" columns take precedance over tags when both define the same key.
+"vm info" columns take precedence over tags when both define the same key.
 
 "cc mount" allows direct access to a guest's filesystem over the command and
 control connection. When given a VM uuid or name and a path, the VM's

cmd/minimega/external.go

@@ -66,7 +66,7 @@ var externalCLIHandlers = []minicli.Handler{
 		HelpLong: `
 minimega maintains a list of external packages that it depends on, such as
 qemu. Calling check will attempt to find each of these executables in the
-avaiable path and check to make sure they meet the minimum version
+available path and check to make sure they meet the minimum version
 requirements. Returns errors for all missing executables and all minimum
 versions not met.`,
 		Patterns: []string{

cmd/minimega/kvm.go

@@ -73,7 +73,7 @@ type KVMConfig struct {
 
 	// Assign a migration image, generated by a previously saved VM to boot
 	// with. By default, images are read from the files directory as specified
-	// with -filepath. This can be overriden by using an absolute path.
+	// with -filepath. This can be overridden by using an absolute path.
 	// Migration images should be booted with a kernel/initrd, disk, or cdrom.
 	// Use 'vm migrate' to generate migration images from running VMs.
 	//
@@ -180,7 +180,7 @@ type KVMConfig struct {
 	Disks DiskConfigs
 
 	// If true will use xHCI USB controller. Otherwise will use EHCI.
-	// EHCI does not support USB 3.0, but may be used for backwards compatability.
+	// EHCI does not support USB 3.0, but may be used for backwards compatibility.
 	//
 	// Default: true
 	UsbUseXHCI bool

cmd/minimega/router_cli.go

@@ -35,7 +35,7 @@ router takes a number of subcommands:
   using DHCP. The interface field is an integer index of the interface defined
   with 'vm config net'. You could also specify if that interface will be a
   loopback interface For example, to configure the second interface of the
-  router with a static IP and a loopback witha  different IP:
+  router with a static IP and a loopback with a different IP:
 
 	vm config net 100 200
 	# ...
@@ -90,20 +90,20 @@ router takes a number of subcommands:
   Neighbor ip address and AS, and what networks need to be advertised
 
   For example, local router is in AS 100 with an ip 10.0.0.1 and bgp peer is in AS 200 with an ip of 20.0.0.1
-  and you want to advterise network 10.0.0.0/24:
+  and you want to advertise network 10.0.0.0/24:
 
 	router foo route static 10.0.0.0/24 0 foo_out
 	router foo bgp bar local 10.0.0.1 100
 	router foo bgp bar neighbor 20.0.0.1 200
 	router foo bgp bar export filter foo_out
 
-  You can set up route reflection for BGP by ussing the rrclient command for that process.
+  You can set up route reflection for BGP by using the rrclient command for that process.
   By using the command it indicates that the peer is a bgp client:
 
 	router foo bgp bar rrclient
 
-- 'rid': Sets the 32 bit router ID for the router. Typically this ID is unqiue
-  across the orginizations network and is used for various routing protocols ie OSPF
+- 'rid': Sets the 32 bit router ID for the router. Typically this ID is unique
+  across the organization's network and is used for various routing protocols ie OSPF
 
 	router foo rid 1.1.1.1
 

cmd/minimega/vm_cli.go

@@ -47,7 +47,7 @@ info include:
 - ip         : IPv4 address
 - ip6        : IPv6 address
 - bandwidth  : stats regarding bandwidth usage
-- qos        : quality-of-service contraints on network interfaces
+- qos        : quality-of-service constraints on network interfaces
 - tags       : any additional information attached to the VM
 
 Additional fields are available for KVM-based VMs:
@@ -110,7 +110,7 @@ naming scheme:
 
 Note: VM names cannot be integers or reserved words (e.g. "all").
 
-Users may specify a saved config explicity rather than use the current one, for
+Users may specify a saved config explicitly rather than use the current one, for
 example:
 
 	vm config save endpoint
@@ -250,7 +250,7 @@ To add a network connection, you can specify the same options as you do when you
 connections via vm config when launching VMs. See "vm config net" for more details.
 
 You will need to specify the VLAN of which the interface is a member. Optionally, you may
-specify the brige the interface will be connected on. You may also specify a MAC address for
+specify the bridge the interface will be connected on. You may also specify a MAC address for
 the interface. Finally, you may also specify the network device for qemu to use. By default,
 "e1000" is used. The order is:
 

cmd/minimega/vmconfig_cli.go

@@ -112,7 +112,7 @@ interface will be connected on. If the bridge name is omitted, minimega will
 use the default "mega_bridge".
 
 You can also optionally specify the MAC address of the interface to connect to
-that network. If not specifed, the MAC address will be randomly generated.
+that network. If not specified, the MAC address will be randomly generated.
 
 You can also optionally specify a network device for qemu to use (which is
 ignored by containers). By default, "e1000" is used. To see a list of valid

cmd/pyapigen/template.go

@@ -61,7 +61,7 @@ except NameError:
 def connect(path='/tmp/minimega/minimega', raise_errors=True, debug=False, namespace=None):
 	'''
 	Connect to the minimega instance with UNIX socket at <path> and return a
-	new minimega API object. See help(minimega.minimega) for an explaination of
+	new minimega API object. See help(minimega.minimega) for an explanation of
 	the other parameters.
 	'''
 	mm = minimega(path, raise_errors, debug, namespace)