[getsentry/action-github-commit] Auto commit

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)