[ISSUE-4] Closes #4

Signed-off-by: Jacek Ciwiś <jacek.ciwis@gmail.com>

Author: kruc

README.md

@@ -1,10 +1,10 @@
-# toggle-to-jira
+# toggl-to-jira
 
-### What is toggle-to-jira?
-Toggl-to-jira is an application which allows you to migrate toggle time entries into multiple jira instances.
+### What is toggl-to-jira?
+Toggl-to-jira is an application which allows you to migrate toggl time entries into multiple jira instances.
 
 ### How it works?
-Toggl-to-jira takes toggle time entries from the given time period and it creates workloads in related jira issues. To work properly each toogle timeentry has to be assigned to the client. Base on this assignment and app configuration, application recognize in which jira instance should create workloads.
+Toggl-to-jira takes toggl time entries from the given time period and it creates workloads in related jira issues. To work properly each toogle timeentry has to be assigned to the client. Base on this assignment and app configuration, application recognize in which jira instance should create workloads.
 
 ### Installation
 
@@ -39,7 +39,7 @@ Linux
 toggl-to-jira
 ```
 it will generate configuration at `$HOME/.toggl-to-jira/config.yaml`
-```
+```yaml
 default_client:
   jira_client_user: firstname.lastname
   jira_host: https://jira.atlassian.net
@@ -54,7 +54,7 @@ log_output: stdout
 period: 1
 toggl_token: (visit https://www.toggl.com/app/profile)
 ```
-2. Adjust following keys
+2. Adjust following keys:
     - default_client.jira_client_user
     - default_client.jira_host
     - default_client.jira_password
@@ -69,15 +69,15 @@ toggl_token: (visit https://www.toggl.com/app/profile)
     INFO[0000] Customize configuration in file: /Users/jacekciwis/.toggl-to-jira/config.yaml
     INFO[0000] Start processing 1478671803: ISSUE-123 Work description
     51m32s - toggl value
-    52m0s - stachursky mode (m)
+    52m0s - stachursky mode (1m)
 
     Workload details:
     Time spent: 50m0s
     Comment: ISSUE-123 Work description
     Issue url: https://jira.atlassian.net/browse/ISSUE-123
     ```
 4. Configuration for missing clients will be autogenerated
-    ```
+    ```yaml
     client:
       client_foo:
         enabled: true
@@ -89,10 +89,10 @@ toggl_token: (visit https://www.toggl.com/app/profile)
     You can overwrite default_client configuration here
 
 5. If everything is correct, run with the `--apply` flag
-    ```
+    ```bash
     toggl-to-jira --apply
     ```
-    ```
+    ```bash
     INFO[0000] Checking configuration...
     INFO[0000] Customize configuration in file: $HOME/.toggl-to-jira/config.yaml
     INFO[0000] Start processing 1478671803: ISSUE-123 Work description
@@ -101,6 +101,6 @@ toggl_token: (visit https://www.toggl.com/app/profile)
     INFO[0001] Issue url: https://jira.atlassian.net/browse/ISSUE-123
     INFO[0002] Finish processing 1478671803: ISSUE-123 Work description
     ```
-6. After migration success toggle time entry will be tag with `jira_migration_success_tag` configuration key value (default: `logged`) - this tag causes skip on next migration
+6. After migration success toggl time entry will be tag with `jira_migration_success_tag` configuration key value (default: `logged`) - this tag causes skip on next migration
 7. If you want to skip some time entry migration, tag it with `jira_migration_skip_tag` configuration key value (default: `jira-migration-skip`)
-8. After migration fail toggle time entry will be tag with `jira_migration_failed_tag` configuration key value (default: `jira-migration-failed`) - this tag will be remove after migration success
+8. After migration fail toggl time entry will be tag with `jira_migration_failed_tag` configuration key value (default: `jira-migration-failed`) - this tag will be remove after migration success