diff --git a/build_overview.md b/build_overview.md
index 5bcdc449ab9297a8ff7b7bdeccde3d646b4c532c..b1514231cb661d9b279d94a06a8d1a94698822c6 100644
--- a/build_overview.md
+++ b/build_overview.md
@@ -117,13 +117,13 @@ $ dot -Tpng tree.dot -o tree.png
### Inspecting the content of a GN target
```bash
-$ buildtools/gn desc out/debug-x86-64 //path/to/my:target
+$ buildtools/gn desc out/debug-x86 //path/to/my:target
```
### Finding references to a GN target
```bash
-$ buildtools/gn refs out/debug-x86-64 //path/to/my:target
+$ buildtools/gn refs out/debug-x86 //path/to/my:target
```
### Referencing targets for the build host
@@ -146,7 +146,7 @@ file:
If a target is defined in a GN build file as `//foo/bar/blah:dash`, that target
(and its dependencies) can be built with:
```bash
-$ buildtools/ninja -C out/debug-x86-64 -j64 foo/bar/blah:dash
+$ buildtools/ninja -C out/debug-x86 -j64 foo/bar/blah:dash
```
Note that this only works for targets in the default toolchain.
@@ -161,7 +161,7 @@ $ buildtools/gn help ninja_rules
You can also browse the set of Ninja targets currently defined in your output
directory with:
```bash
-$ buildtools/ninja -C out/debug-x86-64 -t browse
+$ buildtools/ninja -C out/debug-x86 -t browse
```
Note that the presence of a Ninja target does not mean it will be built - for
that it needs to depend on the “default†target.
diff --git a/build_variants.md b/build_variants.md
index b01e6df687934caba7f7f55302af0b9c00d02192..8df384bc5227abe9ec756ecf1fb815644c2cc7b9 100644
--- a/build_variants.md
+++ b/build_variants.md
@@ -53,9 +53,9 @@ set the `select_variant` GN build argument directly.
approximate what you want and then edit the `select_variant` value `gen.py`
produces:
* You can just edit the `args.gn` file in the GN output directory
- (e.g. `out/debug-x86-64/args.gn`) and the next `ninja` run (aka `fx build`)
+ (e.g. `out/debug-x86/args.gn`) and the next `ninja` run (aka `fx build`)
will re-run `gn gen` with those changes.
- * You can use the command `./buildtools gn args out/debug-x86-64`, which
+ * You can use the command `./buildtools gn args out/debug-x86`, which
will run your `$EDITOR` on the `args.gn` file and then do `gn gen`
immediately so you can see any errors in your GN syntax.
diff --git a/ctu_analysis.md b/ctu_analysis.md
index dfeda431910ebec50b749b91bba6a35c127b34f3..a37cad6dba833d33dd0b0e1e39b6a0e7c04c1c80 100644
--- a/ctu_analysis.md
+++ b/ctu_analysis.md
@@ -75,7 +75,7 @@ make clean && ./run.sh
In order to build only the kernel, specify a `TARGET` as an environment variable:
```
-make clean && TARGET=./build-zircon-pc-x86-64/zircon.elf ./run.sh
+make clean && TARGET=./build-zircon-pc-x86/zircon.elf ./run.sh
```
The script also requires [clangify.py](https://gist.github.com/karkhaz/2ab5e8c7a8783318d44ceca715f20438) to be in the zircon directory with executable bit set. After the analysis has finished, there will be a `.result-xtu` directory, containing:
diff --git a/development/languages/dart/ides.md b/development/languages/dart/ides.md
index f093d22862d999be4e4d6bf551883405665da021..f224f01d28422a5123062c71a32e7f493ee4263b 100644
--- a/development/languages/dart/ides.md
+++ b/development/languages/dart/ides.md
@@ -52,5 +52,5 @@ following:
build. This means that if you have a broken release build, any release build
overrides a debug build. With a broken release build, no amount of correct
rebuilding on debug will solve the issue until you delete
- `//out/release-x86-64`.
+ `//out/release-x86`.
- Delete the .packages file in your project and rebuild.
diff --git a/development/languages/rust/README.md b/development/languages/rust/README.md
index 85968bd5368c49fd75e56b5dca1f1b3f4044f4ee..2e1decae940bafc01c59052c6d9ad3097ce948a8 100644
--- a/development/languages/rust/README.md
+++ b/development/languages/rust/README.md
@@ -116,7 +116,7 @@ If you want to test out Fuchsia with your own custom-built versions of rustc or
you can set the `rustc_prefix` argument to `fx set`, like this:
```
-fx set x86-64 --release --args "rustc_prefix=\"/path/to/bin/dir\""
+fx set x86 --release --args "rustc_prefix=\"/path/to/bin/dir\""
```
## Going further
diff --git a/fuchsia_paver.md b/fuchsia_paver.md
index 568e01452693253c93f64f88b3a3769317da892f..feed33e97c26c94806cec2db40050ff1271d8e3e 100644
--- a/fuchsia_paver.md
+++ b/fuchsia_paver.md
@@ -23,7 +23,7 @@ extend to allow you to build what you need.
## TL;DR
Read this all before? Here are the common case commands
-1. `fx set x86-64`
+1. `fx set x86`
2. `fx full-build`
3. Make the install media
* [[ insert USB drive into host ]]
@@ -37,7 +37,7 @@ Read this all before? Here are the common case commands
Detailed instructions for obtaining and building Fuchsia are available from the
[Getting Started](getting_started.md) guide, but we'll assume here that the
target system is x86-based and that you want to build a complete system. To
-configure our build for this we can run `fx set x86-64` and then build with
+configure our build for this we can run `fx set x86` and then build with
`fx full-build`.
## Creating install media
diff --git a/getting_started.md b/getting_started.md
index cf75f256aaa12a123d2bc7da520d263ea81866a6..9f378d20d683429f4485bc5eb2d98409f94d8a67 100644
--- a/getting_started.md
+++ b/getting_started.md
@@ -67,13 +67,13 @@ the `fx` command should already be in your path. If not, the command is also
available as `scripts/fx`.
```
-fx set x86-64
+fx set x86
fx full-build
```
The first command selects the build configuration you wish to build and
generates the build system itself in an output directory
-(e.g., `out/debug-x86-64`).
+(e.g., `out/debug-x86`).
The second command actually executes the build, transforming the source code in
build products. If you modify the source tree, you can do an incremental build
@@ -83,15 +83,15 @@ Alternatively, you can use the [underlying build system directly](build_system.m
#### [optional] Customize Build Environment
-By default you will get a x86-64 debug build. You can skip this section unless
+By default you will get a x86 debug build. You can skip this section unless
you want something else.
Run `fset-usage` to see a list of build options. Some examples:
```
-fx set x86-64 # x86-64 debug build
+fx set x86 # x86 debug build
fx set arm64 # arm64 debug build
-fx set x86-64 --release # x86-64 release build
+fx set x86 --release # x86 release build
```
#### [optional] Accelerate builds with `ccache` and `goma`