@@ -1,6 +1,6 @@
11# 
22
3−Prybar is a universal interpreter front-end. Same interface, same REPL, different languages.
3+Prybar is a universal interpreter front-end. Same interface, same REPL, different languages.
44
55## Why
66
@@ -9,7 +9,7 @@ every language implements them differently. We wanted them to all behave the sam
99
1010## How it works
1111
12−Prybar, written in Golang, maintains a common command-line interface that calls into
12+Prybar, written in Golang, maintains a common command-line interface that calls into
1313a select language backend. The language backends are implemented using cgo and the langauge's C-bindings.
1414
1515## Usage
@@ -23,8 +23,6 @@ Usage of ./prybar:
2323 -e string
2424 expression to print
2525 -i interactive
26− -l string
27− langauge (default "python2")
2826 -ps1 string
2927 PS1 (default "--> ")
3028 -ps2 string
@@ -43,7 +41,7 @@ Usage of ./prybar:
4341
4442## Building
4543
46−Prybar uses a unix make file to build prybar along with plugins for the langage libraries `pkg-config` detects on your system.
44+Prybar uses a unix make file to build each Prybar binary with `pkg-config` to find language dependencies on your system.
4745
4846### Linux
4947
@@ -57,7 +55,7 @@ brew install go r ruby python python@2 lua spidermonkey
5755
5856## Docker
5957
60−The script `./extract.sh` can be used to compile all plugins and produce a tarball containing a `prybar` binary and supporting `plugin.so` files.
58+The script `./extract.sh` can be used to compile and produce a tarball containing all the Prybar binaries. Each binary will be named `prybar-<language>`. You can build all languages by running `make` in the repo's root or run `make prybar-<language>` to build a specific language.
6159
6260## License
6361