Skip to content

INSTRUCTIONS.md: fix a couple of typos #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
greemfox wants to merge 1 commit into
base: main
Choose a base branch
from
Open

INSTRUCTIONS.md: fix a couple of typos #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/INSTRUCTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ Each problem has at least:
(def __ :tests-will-fail)
```
* The tests reference this symbol. You are sometimes supposed to redefine it to something that makes the tests pass, and sometimes you will need to edit the `(tests ...)` form and replace this symbol with something else.
1. An ”open” `(comment ...)` form (a Rich Comment Form, RFC)
1. An ”open” `(comment ...)` form (a Rich Comment Form, RCF)
1. A `(tests ...)` form

Some problems also have restrictions, e.g:
Expand All @@ -81,7 +81,7 @@ Some problems also have restrictions, e.g:
(def restricted [map mapcat])
```

Restrictions list ”things” shipped with **Clojure** that your solution is not allowed to use. Your editor's *lookup* features can give you documentation and defintions for the restricted symbols. Sometimes using the restricted ”things” in your solution, or just peeking at their documentation can help you find solutions that don't use them.
Restrictions list ”things” shipped with **Clojure** that your solution is not allowed to use. Your editor's *lookup* features can give you documentation and definitions for the restricted symbols. Sometimes using the restricted ”things” in your solution, or just peeking at their documentation can help you find solutions that don't use them.

### Running the tests

Expand Down