Skip to content

Commit e5f4c40

Browse files
committed
PRMerger edits
1 parent 19a144a commit e5f4c40

File tree

5 files changed

+4
-4
lines changed

5 files changed

+4
-4
lines changed

docs/profiling/cpu-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ You can click the **Expand Hot Path** and **Show Hot Path** buttons to see the f
160160
|![Step 3](../profiling/media/procguid_3.png "ProcGuid_3")|The children of the second-level node are the user-code methods and asynchronous routines that are called or created by the second-level system and framework code.|
161161
|![Step 4](../profiling/media/procguid_4.png "ProcGuid_4")|Child nodes of a method have data only for the calls of the parent method. When **Show External Code** is disabled, app methods can also contain an **[External Code]** node.|
162162

163-
For help understanding unexpected data in the call tree, see [Understanding the call tree](../profiling/understanding-call-tree-data.md).
163+
For help understanding unexpected data in the call tree, see [Understanding the call tree](../profiling/understand-call-tree-data.md).
164164

165165
#### <a name="BKMK_External_Code"></a> External code
166166

docs/profiling/instrumentation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ Here's more information on the column values:
111111

112112
- **Module** The name of the module containing the function.
113113

114-
For help understanding unexpected data in the call tree, see [Understanding the call tree](../profiling/understanding-call-tree-data.md).
114+
For help understanding unexpected data in the call tree, see [Understanding the call tree](../profiling/understand-call-tree-data.md).
115115

116116
### Async calls in the Instrumentation call tree (.NET)
117117

-944 Bytes
Loading

docs/profiling/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
- name: Flame Graph
3838
href: flame-graph.md
3939
- name: Understanding the call tree
40-
href: understanding-call-tree-data.md
40+
href: understand-call-tree-data.md
4141
- name: CPU Insights
4242
items:
4343
- name: CPU Insights

docs/profiling/understanding-call-tree-data.md renamed to docs/profiling/understand-call-tree-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Here are the most common reasons:
3535

3636
The **Call Tree** view shows that this work is happening in a generated method with a generated name, which might be unexpected.
3737

38-
![Screenshot that shows expression tree in the Call Tree view.](media/vs-2022/call-tree-dynamic-code-expression-tree-visual.png)
38+
:::image type="content" source="./media/vs-2022/call-tree-dynamic-code-expression-tree-visual.png" alt-text="Screenshot that shows expression tree in the Call Tree view." lightbox="media/vs-2022/call-tree-dynamic-code-expression-tree-visual.png":::
3939

4040
- Code that defers execution. For code that defers execution, such as LINQ, the call path can appear in unexpected ways if you're unfamiliar with how LINQ works. For example, if you use the following code:
4141

0 commit comments

Comments
 (0)