--- wikisrc/ports.mdwn	2018/11/11 16:27:47	1.19
+++ wikisrc/ports.mdwn	2018/11/11 16:31:56	1.20
@@ -142,7 +142,7 @@ x86_64		|I		|[[amd64]] (Can also run i38
 
 ## Various ways of denoting ports and CPUs
 
-When discussing ports and CPUs, there are two concepts each of which have three ways of being named.  Strictly, the word port refers to the value shown by "uname -m", and typically corresponds to a directory under src/sys.  build.sh supports aliases, which are passed as if they were a port, but expand to a port and a cpu (MACHINE and MACHINE_ARCH); an example is evbearmv7hf-el which expands to the evbarm port and earmv7hf cpu.
+When discussing ports and CPUs, there are two concepts, each of which have three ways of being named.  Strictly, the word port refers to the value shown by "uname -m", and typically corresponds to a directory under src/sys.  build.sh supports aliases, which are passed as if they were a port, but expand to a port and a cpu (MACHINE and MACHINE_ARCH); an example is evbearmv7hf-el which expands to the evbarm port and earmv7hf cpu.
 
 [[!table data="""
 concept | /usr/share/mk variable | uname | build.sh
@@ -150,4 +150,4 @@ port | MACHINE      | uname -m | build.s
 cpu  | MACHINE_ARCH | uname -p | build.sh -a
 """]]
 
-Additonally, there are things referred to as ports which are notably different but are not actually "uname -m" values.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.
+Additonally, there are things referred to as ports which are not actually "uname -m" values, but are notably different than what would be expected from that port name.  One is xen, which is a system architecture variant of i386/amd64, and aarch64, which is CPU type variant of evbarm.