diff --git a/7.6.1/advanced/performance/build-performance-breakdown.mdx b/7.6.1/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/7.6.1/advanced/performance/build-performance-breakdown.mdx
+++ b/7.6.1/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/8.0.1/advanced/performance/build-performance-breakdown.mdx b/8.0.1/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/8.0.1/advanced/performance/build-performance-breakdown.mdx
+++ b/8.0.1/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/8.1.1/advanced/performance/build-performance-breakdown.mdx b/8.1.1/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/8.1.1/advanced/performance/build-performance-breakdown.mdx
+++ b/8.1.1/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/8.2.1/advanced/performance/build-performance-breakdown.mdx b/8.2.1/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/8.2.1/advanced/performance/build-performance-breakdown.mdx
+++ b/8.2.1/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/8.3.1/advanced/performance/build-performance-breakdown.mdx b/8.3.1/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/8.3.1/advanced/performance/build-performance-breakdown.mdx
+++ b/8.3.1/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/8.4.2/advanced/performance/build-performance-breakdown.mdx b/8.4.2/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/8.4.2/advanced/performance/build-performance-breakdown.mdx
+++ b/8.4.2/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/advanced/performance/build-performance-breakdown.mdx b/advanced/performance/build-performance-breakdown.mdx
index 477e757..cba9593 100644
--- a/advanced/performance/build-performance-breakdown.mdx
+++ b/advanced/performance/build-performance-breakdown.mdx
@@ -144,9 +144,8 @@ system load average during the invocation.
 
 A high load during a Bazel invocation can be an indication that Bazel schedules
 too many local actions in parallel for your machine. You might want to look into
-adjusting
-[`--local_cpu_resources`](/reference/command-line-reference#flag--local_cpu_resources)
-and [`--local_ram_resources`](/reference/command-line-reference#flag--local_ram_resources),
+adjusting [`--local_resources`](/reference/command-line-reference#flag--local_resources)
+(e.g., `--local_resources=cpu=HOST_CPUS*.5` or `--local_resources=memory=HOST_RAM*.5`),
 especially in container environments (at least until
 [#16512](https://github.com/bazelbuild/bazel/pull/16512) is merged).
 
diff --git a/reference/command-line-reference.mdx b/reference/command-line-reference.mdx
index 73ed4cc..aa7d680 100644
--- a/reference/command-line-reference.mdx
+++ b/reference/command-line-reference.mdx
@@ -4464,6 +4464,10 @@ Tags:
 
 `--local_cpu_resources=<an integer, or "HOST_CPUS", optionally followed by [-|*]<float>.>` default: "HOST\_CPUS"
 
+<Warning>
+**Deprecated:** This flag is deprecated. Use [`--local_resources`](#flag--local_resources) instead with `cpu=<value>` syntax (e.g., `--local_resources=cpu=HOST_CPUS*.5`).
+</Warning>
+
 Explicitly set the total number of local CPU cores available to Bazel to spend on build actions executed locally. Takes an integer, or "HOST\_CPUS", optionally followed by \[-\| _\]<float> (eg. HOST\_CPUS_.5 to use half the available CPU cores). By default, ("HOST\_CPUS"), Bazel will query system configuration to estimate the number of CPU cores available.
 
 Tags:
@@ -4478,6 +4482,10 @@ Tags:
 
 `--local_ram_resources=<an integer number of MBs, or "HOST_RAM", optionally followed by [-|*]<float>.>` default: "HOST\_RAM\*.67"
 
+<Warning>
+**Deprecated:** This flag is deprecated. Use [`--local_resources`](#flag--local_resources) instead with `memory=<value>` syntax (e.g., `--local_resources=memory=HOST_RAM*.5`).
+</Warning>
+
 Explicitly set the total amount of local host RAM (in MB) available to Bazel to spend on build actions executed locally. Takes an integer, or "HOST\_RAM", optionally followed by \[-\| _\]<float> (eg. HOST\_RAM_.5 to use half the available RAM). By default, ("HOST\_RAM\*.67"), Bazel will query system configuration to estimate the amount of RAM available and will use 67% of it.
 
 Tags: