summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Hector Martin2009-05-05 02:23:11 +0200
committerGravatar Hector Martin2009-05-05 02:23:11 +0200
commit71dc46c30ecb26d2630df2cda2d5ae2c385d88e9 (patch)
treeaedb9d1d9ca57af0dc0690c6c6f96a20dcb91be1
parentbbc6981c085b34169e7717d22426c5315d3ac382 (diff)
downloadusbmuxd-71dc46c30ecb26d2630df2cda2d5ae2c385d88e9.tar.gz
usbmuxd-71dc46c30ecb26d2630df2cda2d5ae2c385d88e9.tar.bz2
Format nitpicking
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 39e0a6c..33d758e 100644
--- a/README
+++ b/README
@@ -37,7 +37,7 @@ Generally speaking, this is what goes on in a typical usage scenario:
3. phone replies
4. usbmuxd now considers the phone to be connected and tells iTunes
5. iTunes opens another separate connection to usbmuxd and asks it to connect
-to, say, the afc port on the device
+ to, say, the afc port on the device
6. usbmuxd sends a pseudo-TCP SYN packet to the phone
7. the phone's kernel driver receives the SYN packet and itself opens a
TCP connection to localhost on the afc port