updated docs

Author: jclc

README.md

@@ -42,7 +42,7 @@ If for some reason the alias was not added to your .bashrc or your shell of choi
 
 If you are using Windows and you downloaded the .jar file, you must use tmc-cli directly with Java like so: `java -jar [path_to_tmc-cli.jar]`. In the following examples, replace `tmc` with this command. (note: you must have set Java on your system `%PATH%`. For more information, see [this Java help page](https://www.java.com/en/download/help/path.xml).)
 
-Tip: On Windows, use `doskey tmc="java - jar [path_to_tmc-cli.jar] $@"` to create a convenient alias.
+Tip: On Windows, use `doskey tmc="java -jar [path_to_tmc-cli.jar] $*"` in cmd.exe or `doskey /exename=powershell.exe tmc="java -jar [path_to_tmc-cli.jar] $*"` in PowerShell to create a convenient alias.
 
 Now that you've installed tmc-cli, you can view all available commands by running tmc without arguments or with `tmc --help`. You can also view all available options for commands by running them with the `--help` switch, for example `tmc courses --help`.
 

docs/HACKING.md

@@ -2,8 +2,8 @@ Architecture and Hacking the tmc-cli
 ====================================
 
 ## Requirements for developing tmc-cli
- * jdk 7
- * linux bash (mac's bash won't work)
+ * JDK 7
+ * Modern Linux Bash (Mac's Bash won't work)
 
 
 ## Building tmc-cli
@@ -21,9 +21,9 @@ Conceptually, there are three main parts in the program; the launch code, backen
 and the commands. The commands are gathered into their own package. In addition, there are utility
 classes in order to take care of user input/output and file handling.
 
-The tmc-cli itself is mostly just an command line interface for the backend libraries.
+Tmc-cli itself is mostly just an command line interface for the backend libraries.
 All the heavy lifting is done by [tmc-core](https://github.com/testmycode/tmc-core) and
-[tmc-langs](https://github.com/testmycode/tmc-langs) libraries. The tmc-cli also requires the
+[tmc-langs](https://github.com/testmycode/tmc-langs) libraries. Tmc-cli also requires the
 server-side component of TestMyCode aka. [tmc-server](https://github.com/testmycode/tmc-server).
 
 ### Important classes
@@ -115,3 +115,11 @@ public class ExampleCommandTest {
 
 If you are doing tests for any other class, simply create normal unit tests
 that don't depend on any command.
+
+##Updating the documentation
+
+Please document any new features or revisions in MANUAL.md and HISTORY.md as well
+as README.md, if the affected feature is already documented there.
+
+If you make changes to MANUAL.md, please rebuild tmc.1 before you push your changes.
+Use `[md2man](https://github.com/sunaku/md2man)-roff docs/MANUAL.md > docs/tmc.1` to build the manpage.

docs/MANUAL.md

@@ -1,5 +1,5 @@
-TMC-CLI 1 2016-06-30 "Helsinki Univ. Dep. of CS" "TMC-CLI Manual"
-=================================================================
+TMC-CLI 1 2016-06-30 "TestMyCode" "TMC-CLI Manual"
+==================================================
 
 NAME
 ----
@@ -207,8 +207,7 @@ FILES
 `[course directory]/.tmc.json`
   Course configuration and cache file. Saves the status of the username, server
   address and course's exercises. Manually editing this file may have adverse
-  effects.
-  
+  effects.  
 
 `~/.config/tmc-cli/properties.json`
   User configuration file. Use `tmc prop` to edit properties.