Update documentation with zap supporting amd64 (#28210)
* ZAP supports arm64, doc this
* Fix file name
diff --git a/docs/code_generation.md b/docs/code_generation.md
index 318cfed..e12bf40 100644
--- a/docs/code_generation.md
+++ b/docs/code_generation.md
@@ -40,10 +40,6 @@
environment bootstrap (see `scripts/setup/zap.json`), which makes `zap-cli`
available in `$PATH` when running in a build environment.
-**NOTE**: zap packages are currently NOT available for `arm64` (like when
-compiling on Raspberry PI.). In these cases one should check out zap from source
-and set `$ZAP_DEVELOPMENT_PATH` as described below.
-
When matter scripts need to invoke `zap-cli` (for code generation) or `zap` (to
start the UI tool), they make use of the following environment variables to
figure out where the zap tool is located (in order of precedence):
diff --git a/docs/guides/BUILDING.md b/docs/guides/BUILDING.md
index 26ff8d5..359b35e 100644
--- a/docs/guides/BUILDING.md
+++ b/docs/guides/BUILDING.md
@@ -169,8 +169,8 @@
- Use this if you are developing ZAP locally and would like to run ZAP
with your changes.
-- `$ZAP_INSTALL_PATH` to point to where `zap-linux.zip` or `zap-mac.zip` was
- unpacked.
+- `$ZAP_INSTALL_PATH` to point to where `zap-linux-x64.zip`,
+ `zap-linux-arm64.zip` or `zap-mac-x64.zip` was unpacked.
- This allows you to not need to place `zap` or `zap-cli` (or both) in
`$PATH`.
