Skip to content

Commit 8a2fe2a

Browse files
committed
docs: fix grammar and trailing spaces
1 parent 5dca110 commit 8a2fe2a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ however you probably want to use it in combination with CodeTracer, which would
5555

5656
### ENV variables
5757

58-
* if you pass `CODETRACER_RUBY_RECORDER_DEBUG=1`, you enables some additional debug-related logging
58+
* if you pass `CODETRACER_RUBY_RECORDER_DEBUG=1`, you enable some additional debug-related logging
5959
* `CODETRACER_RUBY_RECORDER_OUT_DIR` can be used to specify the directory for trace files
6060

6161
## Future directions
@@ -65,7 +65,7 @@ The current Ruby support is a prototype. In the future, it may be expanded to fu
6565
### Current approach: TracePoint API
6666

6767
Currently we're using the TracePoint API: https://rubyapi.org/3.4/o/tracepoint .
68-
This is very flexible and can function with probably multiple Ruby versions out of the box.
68+
This is very flexible and can function with probably multiple Ruby versions out of the box.
6969
However, this is limited:
7070

7171
* it's not optimal
@@ -87,7 +87,7 @@ The patching can be done either directly in the source code of the VM or through
8787

8888
#### Filtering
8989

90-
It would be useful to have a way to record only certain intervals within the program execution, or certain functions or modules:
90+
It would be useful to have a way to record only certain intervals within the program execution, or certain functions or modules:
9191
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
9292
parts of even long-running or more heavy programs.
9393

0 commit comments

Comments
 (0)