diff --git a/BlissRoms/build-guide/index.html b/BlissRoms/build-guide/index.html
index ef88447..1920922 100644
--- a/BlissRoms/build-guide/index.html
+++ b/BlissRoms/build-guide/index.html
@@ -326,8 +326,8 @@
     <ul class="md-nav__list" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#updated-for-pie-p90" class="md-nav__link">
-    Updated for Pie (p9.0)
+  <a href="#updated-for-android-10-q" class="md-nav__link">
+    Updated for Android 10 (q)
   </a>
   
     <nav class="md-nav">
@@ -632,8 +632,8 @@
     <ul class="md-nav__list" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#updated-for-pie-p90" class="md-nav__link">
-    Updated for Pie (p9.0)
+  <a href="#updated-for-android-10-q" class="md-nav__link">
+    Updated for Android 10 (q)
   </a>
   
     <nav class="md-nav">
@@ -799,7 +799,7 @@
                 
                 
                 <h1 id="build-guide">Build Guide</h1>
-<h2 id="updated-for-pie-p90">Updated for Pie (p9.0)</h2>
+<h2 id="updated-for-android-10-q">Updated for Android 10 (q)</h2>
 <h3 id="introduction">Introduction</h3>
 <p>This is the official guide to build BlissRoms for your device. In this guide, we will only cover official devices with actual maintainers. We will not delve into porting devices.</p>
 <p>The golden rule to building is patience. If something breaks, wait for your maintainer to fix it, send a polite message to your maintainer, or better yet, try and fix it yourself. Then you can make a merge request and contribute!</p>
@@ -852,17 +852,17 @@
 <p>Now we’re ready to download the source code.</p>
 <h3 id="download">Download</h3>
 <p>Create a directory for the source:</p>
-<pre><code>mkdir -p ~/bliss/p9.0
-cd ~/bliss/p9.0
+<pre><code>mkdir -p ~/bliss/q
+cd ~/bliss/q
 </code></pre>
 <p>Before we download, we need to tell <code>repo</code> and <code>git</code> who we are. Run the following commands, substituting your information:</p>
 <pre><code>git config --global user.email “randy.mcrandyface@hotmail.net”
 git config --global user.name “Randy McRandyface”
 </code></pre>
 <p>Now, we’re ready to initialize. We need to tell <code>repo</code> which manifest to read:</p>
-<pre><code>repo init -u https://github.com/BlissRoms/platform_manifest.git -b p9.0
+<pre><code>repo init -u https://github.com/BlissRoms/platform_manifest.git -b q
 </code></pre>
-<p><code>-b</code> is for the branch, and we’re on <code>p9.0</code>, Android Pie. It’ll take a couple of seconds. You may need to type <code>y</code> for the color prompt.</p>
+<p><code>-b</code> is for the branch, and we’re on <code>q</code>, Android 10. It’ll take a couple of seconds. You may need to type <code>y</code> for the color prompt.</p>
 <p>Then sync the source:</p>
 <pre><code>repo sync -j24 -c
 </code></pre>
@@ -901,7 +901,7 @@
 <p>And the build should start. The build process will take a long time. Prepare to wait a few hours, even on a decent machine.</p>
 <h4 id="why-mka-and-not-make">Why <code>mka</code> and not <code>make</code>?</h4>
 <p><code>make</code> only runs with 1 thread. <code>mka</code> is properly aliased to use all of your threads by checking <code>nproc</code>.</p>
-<p>If you want to customize your thread count (maybe you're building with a fan-screaming laptop in a quiet coffee shop), use <code>make -j#</code>, replacing the hash with the number of threads (example of <code>make -j4</code>).</p>
+<p>If you want to customize your thread count (maybe you're building with a fan-screaming laptop in a quiet coffee shop), use <code>make blissify -j#</code>, replacing the hash with the number of threads (example of <code>make blissify -j4</code>).</p>
 <h4 id="i-get-an-error-about-no-blissify-targets-to-build-against-whats-wrong">I get an error about no <code>blissify</code> targets to build against, what's wrong?</h4>
 <p>If you are building other ROMs, it is usually <code>make bacon</code>. For BlissRoms, we chose the build target of <code>blissify</code>. If that doesn't work, sometimes there is a bug, or the ROM developers do not implement a <code>bacon</code> target to build against. In this case, you will need to find what name they use to initialize a full build of the ROM. Conventionally, it is supposed to be <code>bacon</code>, but some ROM developers change this name inadvertently, or actually have a bug that causes the build target to never be found. If you cannot locate the build target, ask the developers of the ROM. Alternatively, you can try poking around in <code>build/make/core/Makefile</code> to see what the build target name is. But this is out of the scope of this article as you're not supposed to be building other ROMs (that's not what this tutorial is for, sorry!)</p>
 <p>All right, but that's annoying. You had to type <strong>three</strong> commands to build it all. What about running one command?</p>