diff --git a/README.md b/README.md
index 6bff09cc..288aa7b4 100644
--- a/README.md
+++ b/README.md
@@ -128,16 +128,8 @@ Or, if that doesn't work:
     doesn't work properly on your network.
     
  4. Prepare a text file with a filename ending with .remote; the filename
-    doesn't matter, only the .remote ending does. This file must contain
-    two lines: the first line is the name of your iPod/iPhone/iPad, the second
-    is the 4-digit pairing code displayed by Remote.
-    
-    If your iPod/iPhone/iPad is named "Foobar" and Remote gives you the pairing
-    code 5387, the file content must be:
-    ```
-    Foobar
-    5387 
-    ```
+    doesn't matter, only the .remote ending does. This first line in the file
+    must contain the 4-digit pairing code displayed by Remote.
     
  5. Move this file somewhere in your library
 
@@ -154,12 +146,11 @@ forked-daapd does not get notified about new files on network mounts, so the
 Solution: Set two library paths in the config, and add the .remote file to the
 local path. See [Libraries on network mounts](#libraries-on-network-mounts).
 
-#### You did not enter the correct name or pairing code
+#### You did not enter the correct pairing code
 You will see an error in the log about pairing failure with a HTTP response code
 that is *not* 0.
-Solution: Copy-paste the name to be sure to get specials characters right. You
-can also try the pairinghelper script located in the scripts-folder of the
-source.
+Solution: Try again. You can also try the pairinghelper script located in the
+scripts-folder of the source or the mpc method described above.
 
 #### No response from Remote, possibly a network issue
 If you see an error in the log with either:
@@ -191,9 +182,8 @@ Otherwise try using avahi-browse for troubleshooting:
 
 Hit Ctrl-C to terminate avahi-browse.
 
-The name of your iPod/iPhone/iPad is the value of the DvNm field above. In this
-example, the correct value is Foobar. To check for network issues you can try to
-connect to address and port with telnet.
+To check for network issues you can try to connect to address and port with
+telnet.
 
 ### Selecting output devices