From 7271e25099e8cd9001a7885ddb1f98ec232ecb8e Mon Sep 17 00:00:00 2001 From: zerojay Date: Sat, 2 Apr 2016 20:28:17 -0300 Subject: [PATCH] Fixing all instances of "heapdhones" --- Troubleshooting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 44c9e34..ad6486f 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -95,8 +95,8 @@ For Synology users it may be necessary to specify the full path to the `git` bin ### Manual update ### Use the following commands to _reset_ your repository. Backup your configuration and database files, just in case. -* `cd /path/to/heapdhones` -* `git branch` should list either `master` or `develop`. +* `cd /path/to/headphones` +* `git branch` should list eith/er `master` or `develop`. * `git remote show origin` should exist and point to https://github.com/rembo10/headphones * `git reset --hard` — this WILL overwrite all local changes! It will spare your config and database. * `git remote update` @@ -105,7 +105,7 @@ Use the following commands to _reset_ your repository. Backup your configuration ### Reinstallation ### There are some issues with specific version of Headphones for Synology, where the first method will not work (see issues #1770, #1742 and #1774). The following provides some steps to reinstall Headphones, but should be tailored to your specific installation. -* `cd /path/to/heapdhones` +* `cd /path/to/headphones` * Backup your database and config file. In my case, I just copy them to the parent folder. Make sure you have copied them! * `cp headphones.db* ../` * `cp config.ini ../` @@ -118,7 +118,7 @@ There are some issues with specific version of Headphones for Synology, where th ### Downgrade to previous version ### Sometimes, you just want to go back to an older version. For instance, there is no update or fix available (yet) for a problem you did not have in an older version. Backup your configuration and database files, just in case. -* `cd /path/to/heapdhones` +* `cd /path/to/headphones` * `git log`, which should give a list of all changes. * Pick a commit hash (long string of letters and digits) * `git reset --hard PUT_HASH_HERE` — this WILL overwrite all local changes! It will spare your config and database.