diff options
| -rw-r--r-- | README.md | 2 | ||||
| -rw-r--r-- | src/ql570.c | 2 | ||||
| -rw-r--r-- | src/ql570.h | 2 | ||||
| -rw-r--r-- | src/rastertoql570.c | 4 |
4 files changed, 5 insertions, 5 deletions
@@ -121,7 +121,7 @@ int main() } ~~~~~~~~~~~~~ -The fully commented example kann be found in `src/examples/minimal.c`. +The fully commented example can be found in `src/examples/minimal.c`. If you need some quick and dirty way to print something meaningful on a label, use GIMP to create a 720x150 pixel image and export it later as XBM. These are diff --git a/src/ql570.c b/src/ql570.c index e642f91..414560c 100644 --- a/src/ql570.c +++ b/src/ql570.c @@ -166,7 +166,7 @@ ql_page_end(bool last_page, FILE *device) * * The diagram is wrong. The description says, this is bit 3, the diagram * says, this is bit 4. This cost me some time. * TODO: Check 720N/NW. The documentation there lacks the diagram and the - * description sys it is bit 4. I bet this is wrong! + * description says it is bit 4. I bet this is wrong! * * Not cutting is the default. The description says that 'cut at end' is the * default. * diff --git a/src/ql570.h b/src/ql570.h index c346e9a..25b4f92 100644 --- a/src/ql570.h +++ b/src/ql570.h @@ -121,7 +121,7 @@ enum ql_print_info_validity { /** * A mysterious flag described as "Always ON" in the specification. An - * intial suspicion that this might signal the printer to recover from + * initial suspicion that this might signal the printer to recover from * errors after a short amount of time turned out to be wrong. (This * was based on the name `PI_RECOVER` as used in the specification.) */ diff --git a/src/rastertoql570.c b/src/rastertoql570.c index ffd16b5..dfa45bb 100644 --- a/src/rastertoql570.c +++ b/src/rastertoql570.c @@ -196,7 +196,7 @@ wait_for_page_end() * Turns status information into user visible information. * * This function returns true to indicate that an end state has been reached. - * This means either an error occured or the printer changed to PT_WAITING + * This means either an error occurred or the printer changed to PT_WAITING * (ready state). * * TODO: Maybe split this into further pieces, just look at that switch beneath @@ -276,7 +276,7 @@ handle_status(ql_status *status) /** * Initialise the printer. * - * This will try a few times to initalise the printer. After the first try, + * This will try a few times to initialise the printer. After the first try, * ql_init() will be called with flush=true. We will sleep for 100ms after each * call to ql_init(), because I observed that sometimes data is not ready, but * the timeout on cupsBackChannelRead will no come into effect. I guess I am |