link to echo system now at the top

README.md

@@ -7,7 +7,7 @@ Disclaimer: This document is in beta state!!!!! Just to give a hint how the cour
 
 The course will be given as a self study course with a set of introductional seminars and accompanying mandatory assignments, followed by a larger assignment (project). The project can be carried out individually or in groups dependent on size. Grading will be individual, based on agreed requirements between the student and the teacher, showing understanding and abilities regarding:
 
-1. The Rust ecosystem.
+1. The Rust ecosystem. [ecosystem](doc/Ecosystem.md)
 
     Rustup (stable vs nightly), crates and toml files, cargo, rustc, llvm, gdb/lldb (and additional tooling rls, rustfmt, racer, xargo etc.) The Rust core and standard library. Building, bebugging/testing, documenting and publishing Rust applications and libraries.
 
@@ -164,7 +164,7 @@ Seminars
         * xargo for building non-`std` (bare metal) systems
         * [cortex-m-quickstart]
         * [cortex-m]
-        * ([bluepill/nucleo] crates)
+        * [bluepill/nucleo] crates
 
         * Building and debugging your first application.
     * Assignment
@@ -173,7 +173,8 @@ Seminars
 
         b. Discuss from a memory safety perspective the outcome.
 
-        c. Compare for the short message (`abc`), the number of cycles required for `decode` in `--dev` vs. `--release`. As a comparison my straightforword C implementation took 2200 cycles in best optimized mode using `gcc` (-o3), while my (transation) to Rust code took 1780 cycles. (Both executed on a bluepill board at 8MHz with flash memory wait states).
+        c. Compare for the short message (`abc`), the number of cycles required for `decode` in debug (standard) vs. `--release`. As a comparison my straightforword C implementation took 2200 cycles in best optimized mode using `gcc` (-o3), while my (transation) to Rust code took 1780 cycles. (Both executed on a bluepill board at 8MHz without (flash) memory wait states).
+
 
         Make a new git for your embedded development. Make three branches (`3a, 3b, 3c`) with updated documentation according to the above.
 
@@ -244,7 +245,7 @@ Seminars
 9.  Presentation of project ideas
     * Preparation
 
-        Be prepared to present progress of assignmont 5.
+        Be prepared to present progress of assignment 5.
     * Topic
 
         Discussion of projects