--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2018/11/06 01:45:14	1.82
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2018/11/06 01:51:49	1.83
@@ -75,7 +75,7 @@ Both will provide rpi.img.gz and rpi_ins
 
 ### Building yourself
 
-Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH".  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line is an example (equal to the second in effect, for RPI2/33).
+Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is eequal to the second in effect, for RPI2/3.
 
  - ./build.sh -m evbarm -a earmv6hf -u release
  - ./build.sh -m evbarm -a earmv7hf -u release