Make notation/naming convention consistent

From development there's a lot of legacy naming schemes/notations that don't fit with the current way we think of things.

We should become consistent.

A growing list of current inconsistencies are:

Session subtyping being <p: where p previously referred to protocols
~~lty/lsty; What is the l referring to? Linear? If so we should remove it for the session type variant~~
<++++> can just be an overload of <++>

Edited Apr 16, 2020 by Jonas Kastberg

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information