diff options
| author | Brian Carlstrom <bdc@google.com> | 2010-04-26 09:33:47 -0700 |
|---|---|---|
| committer | Mike Lockwood <lockwood@android.com> | 2010-04-28 11:38:39 -0400 |
| commit | 26bb6e92ba392b28eb2edabb639f8750f859ce20 (patch) | |
| tree | c26ca36b68c6b5b9705c17153582e709edd8605c /adb | |
| parent | a84a42eb20d43ffa2695a69d583a6e09532b49d9 (diff) | |
| download | system_core-26bb6e92ba392b28eb2edabb639f8750f859ce20.tar.gz system_core-26bb6e92ba392b28eb2edabb639f8750f859ce20.tar.bz2 system_core-26bb6e92ba392b28eb2edabb639f8750f859ce20.zip | |
Fixing spelling errors in adb docs
Change-Id: I9376717165a01e207034f84a31f85335d3740f18
Diffstat (limited to 'adb')
| -rw-r--r-- | adb/OVERVIEW.TXT | 2 | ||||
| -rw-r--r-- | adb/SERVICES.TXT | 12 |
2 files changed, 7 insertions, 7 deletions
diff --git a/adb/OVERVIEW.TXT b/adb/OVERVIEW.TXT index 6a5191ae..c40695af 100644 --- a/adb/OVERVIEW.TXT +++ b/adb/OVERVIEW.TXT @@ -35,7 +35,7 @@ As a whole, everything works through the following components: (through USB for devices, through TCP for emulators) and provide a few services for clients that run on the host. - The ADB server considers that a device is ONLINE when it has succesfully + The ADB server considers that a device is ONLINE when it has successfully connected to the adbd program within it. Otherwise, the device is OFFLINE, meaning that the ADB server detected a new device/emulator, but could not connect to the adbd daemon. diff --git a/adb/SERVICES.TXT b/adb/SERVICES.TXT index b0124a4d..be4d50be 100644 --- a/adb/SERVICES.TXT +++ b/adb/SERVICES.TXT @@ -74,7 +74,7 @@ host-usb:<request> host-local:<request> A variant of host-serial used to target the single emulator instance - running on the host. This will fail if therre is none or more than one. + running on the host. This will fail if there is none or more than one. host:<request> When asking for information related to a device, 'host:' can also be @@ -146,7 +146,7 @@ remount: dev:<path> Opens a device file and connects the client directly to it for read/write purposes. Useful for debugging, but may require special - priviledges and thus may not run on all devices. <path> is a full + privileges and thus may not run on all devices. <path> is a full path from the root of the filesystem. tcp:<port> @@ -173,7 +173,7 @@ log:<name> framebuffer: This service is used to send snapshots of the framebuffer to a client. - It requires sufficient priviledges but works as follow: + It requires sufficient privileges but works as follow: After the OKAY, the service sends 16-byte binary structure containing the following fields (little-endian format): @@ -190,14 +190,14 @@ framebuffer: one byte through the channel, which will trigger the service to send it 'size' bytes of framebuffer data. - If the adbd daemon doesn't have sufficient priviledges to open + If the adbd daemon doesn't have sufficient privileges to open the framebuffer device, the connection is simply closed immediately. dns:<server-name> This service is an exception because it only runs within the ADB server. It is used to implement USB networking, i.e. to provide a network connection to the device through the host machine (note: this is the exact opposite of - network thetering). + network tethering). It is used to perform a gethostbyname(<address>) on the host and return the corresponding IP address as a 4-byte string. @@ -209,7 +209,7 @@ recover:<size> - creating a file named /tmp/update - reading 'size' bytes from the client and writing them to /tmp/update - - when everything is read succesfully, create a file named /tmp/update.start + - when everything is read successfully, create a file named /tmp/update.start This service can only work when the device is in recovery mode. Otherwise, the /tmp directory doesn't exist and the connection will be closed immediately. |
