Skip to content

Commit 946604b

Browse files
authored
doc(multi-staging): more typos
1 parent d7ee473 commit 946604b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/docs/reference/metaprogramming/staging.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,9 +84,9 @@ It will create a project with the necessary dependencies and some examples.
8484
## Example
8585

8686
Now take exactly the same example as in [Macros](./macros.md). Assume that we
87-
do not want to pass an array statically but generated code at run-time and pass
87+
do not want to pass an array statically but generate code at run-time and pass
8888
the value, also at run-time. Note, how we make a future-stage function of type
89-
`Expr[Array[Int] => Int]` in line 4 below. Using `run { ... }` we can evaluate an
89+
`Expr[Array[Int] => Int]` in line 6 below. Using `run { ... }` we can evaluate an
9090
expression at runtime. Within the scope of `run` we can also invoke `show` on an expression
9191
to get a source-like representation of the expression.
9292

@@ -106,7 +106,7 @@ f.apply(Array(1, 2, 3)) // Returns 6
106106
```
107107

108108
Note that if we need to run the main (in an object called `Test`) after
109-
compilation we need make available the compiler to the runtime:
109+
compilation we need to make available the compilation to the runtime:
110110

111111
```shell
112112
dotc -with-compiler -d out Test.scala

0 commit comments

Comments
 (0)