Skip to content

Commit 33379e4

Browse files
guangy10dbort
authored andcommitted
Fix sdk-etdump.md (#949)
Summary: Pull Request resolved: #949 Reviewed By: tarun292 Differential Revision: D50329006 fbshipit-source-id: 8b66a99d8c1a816397b052f6a3fe5d84ceb69dac
1 parent d4c0625 commit 33379e4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/source/sdk-etdump.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ETDump (ExecuTorch Dump) is one of the core components of the ExecuTorch SDK exp
55

66
## Generating an ETDump
77

8-
Generating an ETDump is a relatively straight forward process. Users can follow the steps detailed below to integrate it into their application that uses ExecuTorch.
8+
Generating an ETDump is a relatively straightforward process. Users can follow the steps detailed below to integrate it into their application that uses ExecuTorch.
99

1010
1. ***Include*** the ETDump header in your code.
1111
```C++
@@ -20,7 +20,7 @@ Result<Method> method =
2020
program->load_method(method_name, &memory_manager, &etdump_gen);
2121
```
2222
23-
3. ***Dump Out the ETDump Buffer*** - after the inference iterations have been completed, users can dump out the ETDump buffer. If users are on a device which has a file-system, they could just write it out to the fileystem. For more constrained embedded devices, users will have to extract the ETDump buffer from the device through a mechanism that best suits them (e.g. UART, JTAG etc.)
23+
3. ***Dump Out the ETDump Buffer*** - after the inference iterations have been completed, users can dump out the ETDump buffer. If users are on a device which has a filesystem, they could just write it out to the filesystem. For more constrained embedded devices, users will have to extract the ETDump buffer from the device through a mechanism that best suits them (e.g. UART, JTAG etc.)
2424
2525
```C++
2626
etdump_result result = etdump_gen.get_etdump_data();

0 commit comments

Comments
 (0)