Skip to content

Commit de9e726

Browse files
committed
docs(readme): fix typos
1 parent 8a2fe2a commit de9e726

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ recorder.flush_trace(Dir.pwd)
3636
you can currently use it directly with
3737

3838
```bash
39-
ruby trace.rb [--out-dir DIR] <path to ruby file>
39+
ruby gems/pure-ruby-tracer/lib/trace.rb [--out-dir DIR] <path to ruby file>
4040
# produces several trace json files in DIR,
4141
# or in `$CODETRACER_RUBY_RECORDER_OUT_DIR` if DIR is not provided.
4242
# Defaults to the current directory.
@@ -60,7 +60,7 @@ however you probably want to use it in combination with CodeTracer, which would
6060

6161
## Future directions
6262

63-
The current Ruby support is a prototype. In the future, it may be expanded to function in a way to similar to the more complete implementations, e.g. [Noir](https://github.com/blocksense-network/noir/tree/blocksense/tooling/tracer).
63+
The current Ruby support is a prototype. In the future, it may be expanded to function in a way similar to the more complete implementations, e.g. [Noir](https://github.com/blocksense-network/noir/tree/blocksense/tooling/tracer).
6464

6565
### Current approach: TracePoint API
6666

@@ -77,7 +77,7 @@ For other languages, we've used a more deeply integrated approach: patching the
7777

7878
#### Create a C extension for the VM, based on the `rb_add_event_hook2`
7979

80-
This would be a straigh-forward port of the current code, but developed as a native extension (e.g. in C/C++ or Rust). The expected speedup will be significant.
80+
This would be a straight-forward port of the current code, but developed as a native extension (e.g. in C/C++ or Rust). The expected speedup will be significant.
8181

8282
#### Patching the VM
8383

@@ -88,7 +88,7 @@ The patching can be done either directly in the source code of the VM or through
8888
#### Filtering
8989

9090
It would be useful to have a way to record only certain intervals within the program execution, or certain functions or modules:
91-
we plan on expanding the [trace format](https://github.com/metacraft-labs/runtime_tracing/) and CodeTracer' support, so that this is possible. It would let one be able to record interesting
91+
we plan on expanding the [trace format](https://github.com/metacraft-labs/runtime_tracing/) and CodeTracer's support, so that this is possible. It would let one be able to record interesting
9292
parts of even long-running or more heavy programs.
9393

9494
### Contributing

0 commit comments

Comments
 (0)