fixed notational issues

Author: jurgenvinju

courses/RascalAmendmentProposals/RAP1/RAP1.md

@@ -108,7 +108,7 @@ Each library will be deployed as a single jar and adding a library to a given Ra
 
 * \[**Deployment**\] The packaged jar will be uploaded to a Rascal Package Server, e.g. r2d2.rascal-mpl.org/\<name\>-\<version\>.jar. This is simply a http file server. It could also be our Nexus (which is indeed a file server), but we should not force people to use nexus as their file servers. Http should be the only requirement. Next to the jar should be a checksum file with the same name, i.e. \<name\>-\<version\>.sha1, and a synopsis (description) file, i.e. \<name\>-\<version\>.descr which could be the first sentence of the README.md or something like that (see \[**Discovery**\])  
 * \[**Discovery**\] The Rascal shell provides a means to query the currently available libraries on a given server, i.e. by default r2d2.usethesource.io. It should also be possible to query the list of currently installed Rascal packages. E.g. “pkg find \[string\]” will find all packages matching the optional string name on the server or list them all, and “pkg list \[string\]” does the same for the local packages. The discover and list comments also present the single line synopsis next to the name and all available version numbers for the package. Discover will also label already installed packages by a (\*) or something to make sure the user can see what already is there and what is available for download.  
-* \[**Installation**\] The Rascal shell offers an “install” command to download a library and install it in a local machine repository, i.e. \~/.r2d2/myLibrary-1.0.0.jar. There is also a staging directory to make sure installation is an atomic operation, i.e. \~/.r2d2/staging.  “pkg install \<name\> \[version\]” will go through the following steps:  
+* \[**Installation**\] The Rascal shell offers an “install” command to download a library and install it in a local machine repository, i.e. \/.r2d2/myLibrary-1.0.0.jar. There is also a staging directory to make sure installation is an atomic operation, i.e. \~/.r2d2/staging.  “pkg install \<name\> \[version\]” will go through the following steps:  
   1. Clear the staging directory (for possible left-overs from a failed previous install)  
   2. Push this package name and server on the installation stack file in the staging directory file “TODO”.  
   3. Download a package from the **server**, put it in the staging directory.