From 509531735deda2fab698f00ce056c96cff0416ce Mon Sep 17 00:00:00 2001 From: Taylor Barrella Date: Wed, 15 Jan 2025 02:14:15 -0800 Subject: [PATCH] site: fix typo "inovcation" Closes #24907. PiperOrigin-RevId: 715709973 Change-Id: Ic2625cf517bfa2ba45c66dbd64543e38206c8bfb --- site/en/advanced/performance/json-trace-profile.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site/en/advanced/performance/json-trace-profile.md b/site/en/advanced/performance/json-trace-profile.md index 17ec7c22fdce8c..44b4d6a3eb2e09 100644 --- a/site/en/advanced/performance/json-trace-profile.md +++ b/site/en/advanced/performance/json-trace-profile.md @@ -9,8 +9,8 @@ The JSON trace profile can be very useful to quickly understand what Bazel spent time on during the invocation. By default, for all build-like commands and query, Bazel writes a profile into -the output base named `command-$INOVCATION_ID.profile.gz`, where -`$INOVCATION_ID` is the invocation identifier of the command. Bazel also creates +the output base named `command-$INVOCATION_ID.profile.gz`, where +`$INVOCATION_ID` is the invocation identifier of the command. Bazel also creates a symlink called `command.profile.gz` in the output base that points the profile of the latest command. You can configure whether a profile is written with the [`--generate_json_trace_profile`](/reference/command-line-reference#flag--generate_json_trace_profile)