doc: update readme to point at examples folder

README.md

@@ -6,39 +6,53 @@
 [![Spec: online](https://img.shields.io/badge/Spec-online-success)](https://triton-vm.org/spec/)
 [![Coverage Status](https://coveralls.io/repos/github/TritonVM/triton-vm/badge.svg?branch=master)](https://coveralls.io/github/TritonVM/triton-vm?branch=master)
 
-Triton is a virtual machine that comes with Algebraic Execution Tables (AET) and Arithmetic Intermediate Representations (AIR) for use in combination with a [STARK proof system](https://neptune.cash/learn/stark-anatomy/).
-It defines a Turing complete [Instruction Set Architecture](https://triton-vm.org/spec/isa.html), as well as the corresponding [arithmetization](https://triton-vm.org/spec/arithmetization.html) of the VM.
-The really cool thing about Triton VM is its efficient _recursive_ verification of the STARKs produced when running Triton VM.
+Triton is a virtual machine that comes with Algebraic Execution Tables (AET) and Arithmetic
+Intermediate Representations (AIR) for use in combination with
+a [STARK proof system](https://neptune.cash/learn/stark-anatomy/).
+It defines a Turing complete [Instruction Set Architecture](https://triton-vm.org/spec/isa.html), as
+well as the corresponding [arithmetization](https://triton-vm.org/spec/arithmetization.html) of the
+VM.
+The really cool thing about Triton VM is its efficient _recursive_ verification of the STARKs
+produced when running Triton VM.
 
 ## Getting Started
 
-If you want to start writing programs for Triton VM, check out [Triton TUI](triton-tui/).
-If you want to generate or verify proofs of correct execution, take a look at the [scaffolding repository](https://github.com/TritonVM/triton-vm-scaffold).
+If you want to start writing programs for Triton VM, check out [Triton TUI](triton-tui).
+If you want to generate or verify proofs of correct execution, take a look at
+the [examples](triton-vm/examples).
 
 ## Recursive STARKs of Computational Integrity
 
-Normally, when executing a machine – virtual or not – the flow of information can be regarded as follows.
-The tuple of (`input`, `program`) is given to the machine, which takes the `program`, evaluates it on the `input`, and produces some `output`.
+Normally, when executing a machine – virtual or not – the flow of information can be regarded as
+follows.
+The tuple of (`input`, `program`) is given to the machine, which takes the `program`, evaluates it
+on the `input`, and produces some `output`.
 
 ![](./specification/src/img/recursive-1.svg)
 
-If the – now almost definitely virtual – machine also has an associated STARK engine, one additional output is a `proof` of computational integrity.
+If the – now almost definitely virtual – machine also has an associated STARK engine, one additional
+output is a `proof` of computational integrity.
 
 ![](./specification/src/img/recursive-2.svg)
 
-Only if `input`, `program`, and `output` correspond to one another, i.e., if `output` is indeed the result of evaluating the `program` on the `input` according to the rules defined by the virtual machine, then producing such a `proof` is easy.
+Only if `input`, `program`, and `output` correspond to one another, i.e., if `output` is indeed the
+result of evaluating the `program` on the `input` according to the rules defined by the virtual
+machine, then producing such a `proof` is easy.
 Otherwise, producing a `proof` is next to impossible.
 
 The routine that checks whether a `proof` is, in fact, a valid one, is called the Verifier.
-It takes as input a 4-tuple (`input`, `program`, `output`, `proof`) and evaluates to `true` if and only if that 4-tuple is consistent with the rules of the virtual machine.
+It takes as input a 4-tuple (`input`, `program`, `output`, `proof`) and evaluates to `true` if and
+only if that 4-tuple is consistent with the rules of the virtual machine.
 
 ![](./specification/src/img/recursive-3.svg)
 
-Since the Verifier is a program taking some input and producing some output, the original virtual machine can be used to perform the computation.
+Since the Verifier is a program taking some input and producing some output, the original virtual
+machine can be used to perform the computation.
 
 ![](./specification/src/img/recursive-4.svg)
 
-The associated STARK engine will then produce a proof of computational integrity of _verifying_ some other proof of computational integrity – recursion!
+The associated STARK engine will then produce a proof of computational integrity of _verifying_ some
+other proof of computational integrity – recursion!
 Of course, the Verifier can be a subroutine in a larger program.
 
 Triton VM is specifically designed to allow fast recursive verification.
@@ -48,13 +62,15 @@ Triton VM is specifically designed to allow fast recursive verification.
 Triton VM is still under construction.
 We currently don't recommend using it in production.
 
-Please note that the [Instruction Set Architecture](https://triton-vm.org/spec/isa.html) is not to be considered final.
+Please note that the [Instruction Set Architecture](https://triton-vm.org/spec/isa.html) is not to
+be considered final.
 However, we don't currently foresee big changes.
 
 ## Specification
 
-The specification can be found [here](https://triton-vm.org/spec/).
-Alternatively, you can self-host the [mdBook](https://rust-lang.github.io/mdBook/) by first installing the dependencies, then serving the mdBook.
+The specification can be found [online](https://triton-vm.org/spec/).
+Alternatively, you can self-host the [mdBook](https://rust-lang.github.io/mdBook/) by first
+installing the dependencies, then serving the mdBook.
 
 ```sh
 cargo install mdbook
@@ -68,26 +84,30 @@ Potentially, `~/.cargo/bin` needs to be added to the PATH.
 
 ## Running the Code
 
-The Rust implementation of Triton VM resides in [triton-vm](./triton-vm) and can be [found on crates.io](https://crates.io/crates/triton-vm).
+The Rust implementation of Triton VM resides in [triton-vm](./triton-vm) and can
+be [found on crates.io](https://crates.io/crates/triton-vm).
 
-Triton VM depends on the [`twenty-first`](https://crates.io/crates/twenty-first) cryptographic library.
+Triton VM depends on the [`twenty-first`](https://crates.io/crates/twenty-first) cryptographic
+library.
 
 For trying out the code, [install Rust](https://www.rust-lang.org/tools/install) and run:
 
-```
-~/Projects $ git clone https://github.com/TritonVM/triton-vm.git
-~/Projects $ cd triton-vm
-~/Projects/triton-vm $ make test
+```sh
+~ $ git clone https://github.com/TritonVM/triton-vm.git
+~ $ cd triton-vm
+~/triton-vm $ make test
 ```
 
-For local development of both libraries, it is encouraged to follow [GitHub's fork & pull workflow][gh-fap] by forking and cloning both, place `twenty-first` relative to `triton-vm`, and change the dependency to be `path`-local:
+For local development of both libraries, it is encouraged to
+follow [GitHub's fork & pull workflow][gh-fap] by forking and cloning both, place `twenty-first`
+relative to `triton-vm`, and change the dependency to be `path`-local:
 
 [gh-fap]: https://reflectoring.io/github-fork-and-pull/
 
-```
-~/Projects $ git clone git@github.com:you/triton-vm.git
-~/Projects $ git clone git@github.com:you/twenty-first.git
-~/Projects $ cd triton-vm
-~/Projects/triton-vm $ ln -s ../twenty-first/twenty-first twenty-first
-~/Projects/triton-vm $ sed -i '/^twenty-first =/ s/{.*}/{ path = "..\/twenty-first" }/' triton-vm/Cargo.toml 
+```sh
+~ $ git clone git@github.com:you/triton-vm.git
+~ $ git clone git@github.com:you/twenty-first.git
+~ $ cd triton-vm
+~/triton-vm $ ln -s ../twenty-first/twenty-first twenty-first
+~/triton-vm $ sed -i '/^twenty-first =/ s/{.*}/{ path = "..\/twenty-first" }/' triton-vm/Cargo.toml 
 ```