From 488f91a646b0e0036d6a37c64468dcf7a904eec7 Mon Sep 17 00:00:00 2001
From: "getsantry[bot]" <66042841+getsantry[bot]@users.noreply.github.com>
Date: Thu, 7 Dec 2023 13:45:14 +0000
Subject: [PATCH] [getsentry/action-github-commit] Auto commit

---
 src/docs/product/profiling/differential-flamegraphs.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/product/profiling/differential-flamegraphs.mdx b/src/docs/product/profiling/differential-flamegraphs.mdx
index 88f3c2bef7e04..8cc47f5f02753 100644
--- a/src/docs/product/profiling/differential-flamegraphs.mdx
+++ b/src/docs/product/profiling/differential-flamegraphs.mdx
@@ -34,7 +34,7 @@ We can see that new function calls to `OrganizationTeamsEndpoint.dispatch` were
 
 If you followed closely, you might have noticed that the top right corner contains a `Before -> After` and `After -> Before` toggle. This is because by default, the differential flamegraphs draw the aggregate flamegraph from after the regression as the source of truth, which means that any code which might have been removed, will no longer be drawn (after all, it's not there anymore). This is why negating the view is useful, as it allows us to compare the data from before and peek into the future of how our code will change.
 
-Let us see an example of how our module lock problem looks like when using the profiling data from after the regression as the source of truth:
+Here's an example of what our module lock problem looks like when using the profiling data from after the regression has occurred as the source of truth:
 
 ![Differential flamegraph new functions](./differential-flamegraph-regular.png)