Skip to content

Commit 23196cc

Browse files
committed
documentation fixes
Signed-off-by: Arseniy Alekseyev <[email protected]>
1 parent c2bbc87 commit 23196cc

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

HACKING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ rules.
9797
### Accepting Corrections
9898

9999
A failing expect test will generate a diff between the expected and actual
100-
output. If the new output generate by the command is satisfactory, it can be
100+
output. If the new output generated by the command is satisfactory, it can be
101101
*promoted* with the `$ make promote` command.
102102

103103
## Code flow

src/memo/memo_intf.ml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,14 @@ module type S = sig
2121
(** Type of memoized functions *)
2222
type 'a t
2323

24-
(** [create name ?lifetime ouput_spec f] creates a memoized version
24+
(** [create name ?allow_cutoff ouput_spec f] creates a memoized version
2525
of [f]. The result of [f] for a given input is cached, so that
2626
the second time [exec t x] is called, the previous result is
2727
re-used if possible.
2828
2929
[exec t x] tracks what calls to other memoized function [f x]
3030
performs. When the result of such dependent call changes, [exec t
31-
x] will automatically recomputes [f x].
31+
x] will automatically recompute [f x].
3232
3333
Running the computation may raise [Memo.Cycle_error.E] if a cycle is
3434
detected. *)
@@ -48,7 +48,7 @@ module type S = sig
4848
val peek_exn : 'a t -> input -> 'a
4949

5050
(** After running a memoization function with a given name and
51-
input, it is possibly to query which dependencies that function
51+
input, it is possible to query which dependencies that function
5252
used during execution by calling [get_deps] with the name and
5353
input used during execution. *)
5454
val get_deps : _ t -> input -> (string * Sexp.t) list option

test/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
This file describe how the jbuilder test suite is organized.
1+
This file describes how the dune test suite is organized.
22

33
# Unit testing
44

@@ -20,7 +20,7 @@ enclosed in an `[%%expect]` extension point. For instance:
2020
# Blackbox testing
2121

2222
The `blackbox-tests` contains blackbox tests. I.e. we are testing the
23-
fully built `jbuilder` executable on various example projects.
23+
fully built `dune` executable on various example projects.
2424

2525
The tests are written in [cram](https://bitheap.org/cram/) style. The
2626
logic is implemented in `blackbox-tests/cram.mll`. It only implements
@@ -29,8 +29,8 @@ is currently not preserved between commands, so you cannot define a
2929
variable and use it.
3030

3131
Test cases are in `blackbox-tests/test-cases`. Each sub-directory is a
32-
full blown jbuilder project. Each sub-directory contains a `run.t`
33-
file, which represents a few invocations of jbuilder along with the
32+
full blown dune project. Each sub-directory contains a `run.t`
33+
file, which represents a few invocations of dune along with the
3434
expected output.
3535

3636
Here is a sample `.t` file:

0 commit comments

Comments
 (0)