Skip to content

Commit 6cca321

Browse files
authored
correct spelling
1 parent 03d7a8b commit 6cca321

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/profiling/how-to-specify-pre-and-post-instrument-commands.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can specify commands that run before or after the binaries in a performance
2323

2424
You can specify commands for all instrumented binaries in the profiling run or for individual binaries. However, you can specify only one pre-instrument command to run before and only one post-instrument command to run after the instrumentation process. You cannot specify commands for both all binaries and for individual binaries. When you specify commands for all binaries, the commands are run before or after the instrumentation of each binary in the session.
2525

26-
The working directory in which the commands are executed depends on the operating systen where you are running [!INCLUDE[vs_current_short](../code-quality/includes/vs_current_short_md.md)] and on the target platform of the profiled application.
26+
The working directory in which the commands are executed depends on the operating system where you are running [!INCLUDE[vs_current_short](../code-quality/includes/vs_current_short_md.md)] and on the target platform of the profiled application.
2727

2828
To get the path to the profiling tools, see [Specify the path to command line tools](../profiling/specifying-the-path-to-profiling-tools-command-line-tools.md).
2929

@@ -67,4 +67,4 @@ To get the path to the profiling tools, see [Specify the path to command line to
6767

6868
## See also
6969

70-
[Configure performance sessions](../profiling/configuring-performance-sessions.md)
70+
[Configure performance sessions](../profiling/configuring-performance-sessions.md)

0 commit comments

Comments
 (0)