From ca29c7a7e7ec0f3fb050050bbe0bf00bb6ae1237 Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Thu, 23 Apr 2020 16:53:14 -0400
Subject: [PATCH] instead m instead of make

---
 static/build.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/static/build.html b/static/build.html
index fdb34d54..1b9c9bd1 100644
--- a/static/build.html
+++ b/static/build.html
@@ -400,7 +400,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
 
             <pre>rm -r out</pre>
 
-            <pre>make target-files-package</pre>
+            <pre>m target-files-package</pre>
 
             <p><strong>For an emulator build, always use the development build approach below.</strong></p>
 
@@ -415,7 +415,7 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
             bootloader unlocked and flashing the raw images that are signed with the default
             public test keys:</p>
 
-            <pre>make</pre>
+            <pre>m</pre>
 
             <p>Technically, you could generate test key signed update packages. However, there's
             no point of sideloading update packages when the bootloader is unlocked and there's no
@@ -523,7 +523,7 @@ cd ../..</pre>
 
             <p>Build the tool needed to generate A/B updates:</p>
 
-            <pre>make brillo_update_payload</pre>
+            <pre>m brillo_update_payload</pre>
 
             <p>Generate a signed release build with the release.sh script:</p>