summaryrefslogtreecommitdiff
path: root/firmware
diff options
context:
space:
mode:
authorAlexander Levin <al.le@rockbox.org>2009-09-04 22:00:30 +0000
committerAlexander Levin <al.le@rockbox.org>2009-09-04 22:00:30 +0000
commit3c3d39e836034cd26635074228e7b80b844c64e1 (patch)
tree1bb422c6dc384757393236f1bb2880f3d89d7bb3 /firmware
parent4d86861ce5e736503de058e221d13d600807efb4 (diff)
Fix typos in the comment
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@22625 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'firmware')
-rw-r--r--firmware/export/lcd.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/firmware/export/lcd.h b/firmware/export/lcd.h
index c301c4c0d1..a8253db656 100644
--- a/firmware/export/lcd.h
+++ b/firmware/export/lcd.h
@@ -62,7 +62,7 @@ struct viewport {
* then you need to add X pixels to get to the next line. (the next line
* in this case is height1).
*
- * Similarly, if the screens is has the pixels in contiguous vertical strips
+ * Similarly, if the screen has the pixels in contiguous vertical strips
* the stride would be equal to the image height.
*
* For example if the screen pixels are layed out as follows:
@@ -83,7 +83,7 @@ struct viewport {
* number needs to be passed to the STRIDE macro so that the appropriate height
* or width can be passed to the lcd_bitmap, or lcd_remote_bitmap calls.
*
- * STRIDE_REMOTE and STRIDE_MAIN should never used when it is not clear whether
+ * STRIDE_REMOTE and STRIDE_MAIN should never be used when it is not clear whether
* lcd_remote_bitmap calls or lcd_bitmap calls are being made (for example the
* screens api).
*