Nit fix in sdk-profiling.md (#951)

Summary:
Pull Request resolved: #951

Rephrase a bit to avoid confusion that step for is NOT optional, only the part of using ETRecord is.

Reviewed By: mergennachin

Differential Revision: D50329528

fbshipit-source-id: 4d454e81a5438864eaebbe075710aa26b4f686a5

Author: guangy10

docs/source/sdk-profiling.md

@@ -16,7 +16,7 @@ We provide access to all the profiling data via the Python [Inspector API](./sdk
 1. [Optional] Generate an [ETRecord](./sdk-etrecord.rst) while you're exporting your model. If provided this will enable users to link back profiling details to eager model source code (with stack traces and module hierarchy).
 2.  Build the runtime with the pre-processor flags that enable profiling. Detailed in the [ETDump documentation](./sdk-etdump.md).
 3.  Run your Program on the ExecuTorch runtime and generate an [ETDump](./sdk-etdump.md).
-4. Create an instance of the [Inspector API](./sdk-inspector.rst) by passing in the ETDump you have sourced from the runtime along with the ETRecord generated earlier (optional).
+4. Create an instance of the [Inspector API](./sdk-inspector.rst) by passing in the ETDump you have sourced from the runtime along with the optionally generated ETRecord from step 1.
     - Through the Inspector API, users can do a wide range of analysis varying from printing out performance details to doing more finer granular calculation on module level.