Fix consistency of using `compose1' #119

Merged
leafac merged 1 commits from patch-1 into master 9 years ago
leafac commented 9 years ago (Migrated from github.com)

Previously, on the tutorial, compose1 is used and explained. Furthermore, the documentation on compose/compose1 favors compose1.

Previously, on the tutorial, `compose1` is used and explained. Furthermore, the [documentation on `compose/compose1`](http://docs.racket-lang.org/reference/procedures.html#%28def._%28%28lib._racket%2Fprivate%2Flist..rkt%29._compose1%29%29) favors `compose1`.
mbutterick commented 9 years ago (Migrated from github.com)

Agreed, thanks

Agreed, thanks
The pull request has been merged as 24bbf1c3f7.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b patch-1 master
git pull origin patch-1

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff patch-1
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mbutterick/pollen#119
Loading…
There is no content yet.