Skip to content

Commit c5a4ad5

Browse files
committed
minor updates to tagging workshop
1 parent 89a6347 commit c5a4ad5

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

content/en/scenarios/understand_impact_of_changes/3-capture-tags.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ Once these changes are made, let's run the following script to rebuild the Docke
9696

9797
## Confirm Tag is Captured Successfully
9898

99-
After a few minutes, return to **Splunk Observability Cloud** and load one of the latest traces to confirm that the tags were captured successfully (hint: sort by duration to find the latest traces):
99+
After a few minutes, return to **Splunk Observability Cloud** and load one of the latest traces to confirm that the tags were captured successfully (hint: sort by the timestamp to find the latest traces):
100100

101101
**![Trace with Attributes](../images/trace_with_attributes.png)**
102102

content/en/scenarios/understand_impact_of_changes/4-explore-trace-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ weight: 4
66

77
{{% badge icon="clock" style="primary" %}}5 minutes{{% /badge %}}
88

9-
Now that we've captured several tags from our application, let's explore some of the trace data we've captured that include this additional context, and see if we can identify what's causing poor user experience in some cases.
9+
Now that we've captured several tags from our application, let's explore some of the trace data we've captured that include this additional context, and see if we can identify what's causing a poor user experience in some cases.
1010

1111
## Use Trace Analyzer
1212

0 commit comments

Comments
 (0)