aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPřemysl Janouch <p.janouch@gmail.com>2017-06-25 22:22:00 +0200
committerPřemysl Janouch <p.janouch@gmail.com>2017-06-25 22:22:00 +0200
commitd1d43387e53a997cb25931efc30004711a4f6652 (patch)
tree3c7b17d3cf9769cfe881d00de5ca390f92e5f874
parent22057350e0b6fb8467439a035955d12d41ada712 (diff)
downloadbfc-d1d43387e53a997cb25931efc30004711a4f6652.tar.gz
bfc-d1d43387e53a997cb25931efc30004711a4f6652.tar.xz
bfc-d1d43387e53a997cb25931efc30004711a4f6652.zip
Word the README better
-rw-r--r--README.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.adoc b/README.adoc
index e01e374..307f05e 100644
--- a/README.adoc
+++ b/README.adoc
@@ -50,8 +50,8 @@ Use `break *0x4000b7` to get a breakpoint at the first Brainfuck instruction.
image::gdb-experiment.png[align="center"]
There is also `gdb-object-file.go` that generates an object file that can be
-statically linked with `ld`, and with `gdb-object-file-libc.go` you can link
-against the libc with the C compiler, generating an OS-independent binary:
+statically linked with `ld`, and `gdb-object-file-libc.go` generates an
+OS-independent binary that can be linked against the libc with the C compiler:
$ go run gdb-object-file-libc.go program.bf program.o
$ cc program.o -o program