Package: netrik / 1.16.1-2

fix-spelling-errors-found-by-lintian.patch Patch series | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
Description: Fix spelling errors found by Lintian
Author: Axel Beckert <abe@debian.org>
Forwarded: no

Index: netrik/README
===================================================================
--- netrik.orig/README	2015-12-01 00:45:15.351853090 +0100
+++ netrik/README	2015-12-01 23:41:55.394272977 +0100
@@ -132,17 +132,17 @@
 are missing:
 
 If you want to have fancy command line editing in netrik, you need a shared
-library version of the GNU Readline library, and the developement files
+library version of the GNU Readline library, and the development files
 (headers) going with it. If using GNU/Linux, your distribution should provide a
 package named something like "libreadline-dev"; some distributions fail to do
 so, however. In that case you can get the source (from your distribution or
 from ftp://ftp.gnu.org/gnu/readline/ ) and compile it with "make shared" and
 "make install-shared".
 
-You also need the ncurses developement files. (These are mandatory.) Your
+You also need the ncurses development files. (These are mandatory.) Your
 distribution should provide a "libncurses-dev" package (or something similar);
 some distributions have only one "ncurses" package providing both the library
-and the developement files.
+and the development files.
 
 On FreeBSD, the GNU Getopt port (libgnugetopt) needs to be installed.
 
@@ -165,7 +165,7 @@
 
 As of course you are very interested in netrik ;-), you may want to subscribe
 to the mailing list. Probably not all messages will be of interest to you, but
-you will have a good overview on current netrik developement.
+you will have a good overview on current netrik development.
 
 To subscribe, either send a mail to
 netrik-general-request@lists.sourceforge.net with the word "subscribe" as
Index: netrik/cfg.c
===================================================================
--- netrik.orig/cfg.c	2015-12-01 00:45:15.351853090 +0100
+++ netrik/cfg.c	2015-12-01 23:42:14.818226815 +0100
@@ -16,7 +16,7 @@
 #include "cfg.h"
 
 struct Config cfg={
-   -1, /* force_colors (no default; determined at run time if not explicitely set) */
+   -1, /* force_colors (no default; determined at run time if not explicitly set) */
    1, /* term_width */
 #ifndef XHTML_ONLY
    BROKEN_HTML, /* parser */
@@ -31,7 +31,7 @@
    5, /* anchor_offset */
    0, /* cursor_keys */
    "<<", /* anchor_mark */
-   -1,    /* inverse_bold (no default; determined at run time if not explicitely set) */
+   -1,    /* inverse_bold (no default; determined at run time if not explicitly set) */
    0,    /* bright_background */
    1,    /* color */
    1  /* proxy */
Index: netrik/doc/README
===================================================================
--- netrik.orig/doc/README	2015-12-01 00:45:15.351853090 +0100
+++ netrik/doc/README	2015-12-01 23:41:55.394272977 +0100
@@ -132,17 +132,17 @@
 are missing:
 
 If you want to have fancy command line editing in netrik, you need a shared
-library version of the GNU Readline library, and the developement files
+library version of the GNU Readline library, and the development files
 (headers) going with it. If using GNU/Linux, your distribution should provide a
 package named something like "libreadline-dev"; some distributions fail to do
 so, however. In that case you can get the source (from your distribution or
 from ftp://ftp.gnu.org/gnu/readline/ ) and compile it with "make shared" and
 "make install-shared".
 
-You also need the ncurses developement files. (These are mandatory.) Your
+You also need the ncurses development files. (These are mandatory.) Your
 distribution should provide a "libncurses-dev" package (or something similar);
 some distributions have only one "ncurses" package providing both the library
-and the developement files.
+and the development files.
 
 On FreeBSD, the GNU Getopt port (libgnugetopt) needs to be installed.
 
@@ -165,7 +165,7 @@
 
 As of course you are very interested in netrik ;-), you may want to subscribe
 to the mailing list. Probably not all messages will be of interest to you, but
-you will have a good overview on current netrik developement.
+you will have a good overview on current netrik development.
 
 To subscribe, either send a mail to
 netrik-general-request@lists.sourceforge.net with the word "subscribe" as
Index: netrik/doc/hacking-layout.html
===================================================================
--- netrik.orig/doc/hacking-layout.html	2015-12-01 00:51:16.906822496 +0100
+++ netrik/doc/hacking-layout.html	2015-12-01 23:42:14.830226787 +0100
@@ -1545,7 +1545,7 @@
  This isn't really an error, but can be handled very convenient this way...
 </li> <li>
  SE_DISCOURAGED: Some constructs were found that are strictly speaking valid
- SGML, but explicitely discouraged in the HTML standard. These may be handled
+ SGML, but explicitly discouraged in the HTML standard. These may be handled
  differently by other browsers -- especially comments.
 </li> <li>
  SE_UNIMPLEMENTED: Also valid SGML and discouraged in HTML, but not handled
Index: netrik/doc/hacking-layout.txt
===================================================================
--- netrik.orig/doc/hacking-layout.txt	2015-12-01 00:45:43.499772620 +0100
+++ netrik/doc/hacking-layout.txt	2015-12-01 23:42:14.838226768 +0100
@@ -1072,7 +1072,7 @@
 - SE_BREAK: The user issued an interrupt (SIGINT) while loading the document.
   This isn't really an error, but can be handled very convenient this way...
 - SE_DISCOURAGED: Some constructs were found that are strictly speaking valid
-  SGML, but explicitely discouraged in the HTML standard. These may be handled
+  SGML, but explicitly discouraged in the HTML standard. These may be handled
   differently by other browsers -- especially comments.
 - SE_UNIMPLEMENTED: Also valid SGML and discouraged in HTML, but not handled
   correctly by netrik nor any other popular browser.
Index: netrik/doc/hacking-links.html
===================================================================
--- netrik.orig/doc/hacking-links.html	2015-12-01 00:45:43.431772815 +0100
+++ netrik/doc/hacking-links.html	2015-12-01 23:42:14.838226768 +0100
@@ -59,7 +59,7 @@
  The "value" contains the link's destination URL for normal links, or the form
  data for form controls. "value" is of type "struct Data_string", which is a
  Pascal-like string structure with a data area (dynamic array of char) and an
- explicitely stored string length. This is necessary for binary form data, as
+ explicitly stored string length. This is necessary for binary form data, as
  this can contain NUL bytes. For normal links, the URL is stored as a normal C
  string in the "data" component, and the "size" component is unused.
 </li><li>
@@ -156,7 +156,7 @@
 
 <p>
 Actually activating (or deactivating) a selected link is done with the
-activate_link() function. This function is explicitely called by the link
+activate_link() function. This function is explicitly called by the link
 selection commands, but can be also called by
 <a href="hacking-pager.html#scrollTo">scroll_to()</a> (see
 hacking-pager.*) automatically, if the active link is scrolled out of the valid
@@ -558,7 +558,7 @@
 <p>
 Just like in <a href="#urlEncode">url_encode</a>, "file"
 controls need a special handling. As in mime encoding the file name is
-submitted explicitely, we need an additional "file_name" parameter. This makes
+submitted explicitly, we need an additional "file_name" parameter. This makes
 the handling more complicated than in url_encode().
 </p>
 
Index: netrik/doc/hacking-links.txt
===================================================================
--- netrik.orig/doc/hacking-links.txt	2015-12-01 00:45:43.503772609 +0100
+++ netrik/doc/hacking-links.txt	2015-12-01 23:42:14.842226758 +0100
@@ -35,7 +35,7 @@
 - The "value" contains the link's destination URL for normal links, or the form
   data for form controls. "value" is of type "struct Data_string", which is a
   Pascal-like string structure with a data area (dynamic array of char) and an
-  explicitely stored string length. This is necessary for binary form data, as
+  explicitly stored string length. This is necessary for binary form data, as
   this can contain NUL bytes. For normal links, the URL is stored as a normal C
   string in the "data" component, and the "size" component is unused.
 - "form" is an "enum Form_control", telling to what kind of link or form control
@@ -88,7 +88,7 @@
 _activate_link()_
 
 Actually activating (or deactivating) a selected link is done with the
-activate_link() function. This function is explicitely called by the
+activate_link() function. This function is explicitly called by the
 link selection commands, but can be also called by _scroll_to()_ (see
 hacking-pager.*) automatically, if the active link is scrolled out of the
 valid screen area.
@@ -348,7 +348,7 @@
 will be used up later anyways...)
 
 Just like in _url_encode_ , "file" controls need a special handling. As in
-mime encoding the file name is submitted explicitely, we need an additional
+mime encoding the file name is submitted explicitly, we need an additional
 "file_name" parameter. This makes the handling more complicated than in
 url_encode().
 
Index: netrik/doc/hacking-page.html
===================================================================
--- netrik.orig/doc/hacking-page.html	2015-12-01 00:45:43.483772666 +0100
+++ netrik/doc/hacking-page.html	2015-12-01 23:41:55.394272977 +0100
@@ -345,7 +345,7 @@
 "active_link". (Instead of testing all, we could limit the search to a smaller
 range by pre-testing some of the criteria. However, a situation were this would
 make a difference is unrealistic; it would be just a waste of code, meaning
-wasted developement time, increased binary size, and most important additional
+wasted development time, increased binary size, and most important additional
 error sources and worse maintainability.)
 </p>
 
@@ -361,7 +361,7 @@
 <p>
 Of course, this heuristic isn't perfect by any means; however, it is certainly
 more than sufficient. Anything better would be waste of performance and
-developement efforts. Recognition whether a candidate is worth considering
+development efforts. Recognition whether a candidate is worth considering
 should be robust. Choosing the best if there are multiple similar candidates is
 suboptimal, but such a situation is really unlikely; and if it occurs, the
 question which is really the best link is disputable alyways...
Index: netrik/doc/hacking-page.txt
===================================================================
--- netrik.orig/doc/hacking-page.txt	2015-12-01 00:45:43.535772517 +0100
+++ netrik/doc/hacking-page.txt	2015-12-01 23:41:55.398272968 +0100
@@ -222,7 +222,7 @@
 "active_link". (Instead of testing all, we could limit the search to a smaller
 range by pre-testing some of the criteria. However, a situation were this
 would make a difference is unrealistic; it would be just a waste of code,
-meaning wasted developement time, increased binary size, and most important
+meaning wasted development time, increased binary size, and most important
 additional error sources and worse maintainability.)
 
 At start "best" is set to -1 (i.e. no link), and "best_deviation" to 1.0. Thus,
@@ -234,7 +234,7 @@
 
 Of course, this heuristic isn't perfect by any means; however, it is certainly
 more than sufficient. Anything better would be waste of performance and
-developement efforts. Recognition whether a candidate is worth considering
+development efforts. Recognition whether a candidate is worth considering
 should be robust. Choosing the best if there are multiple similar candidates
 is suboptimal, but such a situation is really unlikely; and if it occurs,
 the question which is really the best link is disputable alyways...
Index: netrik/doc/hacking-terminal.html
===================================================================
--- netrik.orig/doc/hacking-terminal.html	2015-12-01 00:45:43.471772700 +0100
+++ netrik/doc/hacking-terminal.html	2015-12-01 23:42:14.842226758 +0100
@@ -105,7 +105,7 @@
 </p>
 
 <p>
-Note that, unless explicitely overridden by --no-force-colors,
+Note that, unless explicitly overridden by --no-force-colors,
 "cfg.force_colors" is automatically set if "cfg.bright_background" is not set,
 so a black background will always be used with the dark color scheme, even on a
 terminal normally having a bright background. This isn't done with the bright
Index: netrik/doc/hacking-terminal.txt
===================================================================
--- netrik.orig/doc/hacking-terminal.txt	2015-12-01 00:45:43.527772540 +0100
+++ netrik/doc/hacking-terminal.txt	2015-12-01 23:42:14.842226758 +0100
@@ -70,7 +70,7 @@
 in load_color_map(), which is called after reading the command line/config
 file options in main().
 
-Note that, unless explicitely overridden by --no-force-colors,
+Note that, unless explicitly overridden by --no-force-colors,
 "cfg.force_colors" is automatically set if "cfg.bright_background" is not
 set, so a black background will always be used with the dark color scheme,
 even on a terminal normally having a bright background. This isn't done with
Index: netrik/doc/hacking.html
===================================================================
--- netrik.orig/doc/hacking.html	2015-12-01 00:45:43.459772735 +0100
+++ netrik/doc/hacking.html	2015-12-01 23:41:55.402272958 +0100
@@ -101,7 +101,7 @@
 <p>
 On the other hand, this isn't terribly efficient the way it is done now. We
 think however that in the early stage netrik is now, it's more important to
-keep the code as simple as possible to faciliate fast developement.
+keep the code as simple as possible to faciliate fast development.
 </p>
 
 <p>
Index: netrik/doc/hacking.txt
===================================================================
--- netrik.orig/doc/hacking.txt	2015-12-01 00:45:43.519772563 +0100
+++ netrik/doc/hacking.txt	2015-12-01 23:41:55.402272958 +0100
@@ -68,7 +68,7 @@
 
 On the other hand, this isn't terribly efficient the way it is done now. We
 think however that in the early stage netrik is now, it's more important to
-keep the code as simple as possible to faciliate fast developement.
+keep the code as simple as possible to faciliate fast development.
 
 Also, splitting up the processing is necessary to allow rendering of not
 completely loaded pages. As this is to be one of the major features of netrik
Index: netrik/doc/in/hacking-layout.in
===================================================================
--- netrik.orig/doc/in/hacking-layout.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/hacking-layout.in	2015-12-01 23:42:14.846226749 +0100
@@ -1153,7 +1153,7 @@
 ��$  This isn't really an error, but can be handled very convenient this way...
 $#</li> <li>
 ��$- SE_DISCOURAGED: Some constructs were found that are strictly speaking valid
-��$  SGML, but explicitely discouraged in the HTML standard. These may be handled
+��$  SGML, but explicitly discouraged in the HTML standard. These may be handled
 ��$  differently by other browsers -- especially comments.
 $#</li> <li>
 ��$- SE_UNIMPLEMENTED: Also valid SGML and discouraged in HTML, but not handled
Index: netrik/doc/in/hacking-links.in
===================================================================
--- netrik.orig/doc/in/hacking-links.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/hacking-links.in	2015-12-01 23:42:14.850226739 +0100
@@ -48,7 +48,7 @@
 ��$- The "value" contains the link's destination URL for normal links, or the form
 ��$  data for form controls. "value" is of type "struct Data_string", which is a
 ��$  Pascal-like string structure with a data area (dynamic array of char) and an
-��$  explicitely stored string length. This is necessary for binary form data, as
+��$  explicitly stored string length. This is necessary for binary form data, as
 ��$  this can contain NUL bytes. For normal links, the URL is stored as a normal C
 ��$  string in the "data" component, and the "size" component is unused.
 $#</li><li>
@@ -129,7 +129,7 @@
 $=$$<h4>$$$_activate_link()$_$$</h4>$$
 
 Actually activating (or deactivating) a selected link is done with the
-activate_link() function. This function is explicitely called by the link
+activate_link() function. This function is explicitly called by the link
 selection commands, but can be also called by
 $$<a$+href="hacking-pager.html#scrollTo">$$$_scroll_to()$_$$</a>$$ (see
 hacking-pager.*) automatically, if the active link is scrolled out of the valid
@@ -437,7 +437,7 @@
 
 Just like in $$<a$+href="#urlEncode">$$$_url_encode$_$$</a>$$$ , "file"
 controls need a special handling. As in mime encoding the file name is
-submitted explicitely, we need an additional "file_name" parameter. This makes
+submitted explicitly, we need an additional "file_name" parameter. This makes
 the handling more complicated than in url_encode().
 
 Note that, to reduce the amount of extra code, the "file_name" parameter is
Index: netrik/doc/in/hacking-page.in
===================================================================
--- netrik.orig/doc/in/hacking-page.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/hacking-page.in	2015-12-01 23:41:55.402272958 +0100
@@ -268,7 +268,7 @@
 "active_link". (Instead of testing all, we could limit the search to a smaller
 range by pre-testing some of the criteria. However, a situation were this would
 make a difference is unrealistic; it would be just a waste of code, meaning
-wasted developement time, increased binary size, and most important additional
+wasted development time, increased binary size, and most important additional
 error sources and worse maintainability.)
 
 At start "best" is set to -1 (i.e. no link), and "best_deviation" to 1.0. Thus,
@@ -280,7 +280,7 @@
 
 Of course, this heuristic isn't perfect by any means; however, it is certainly
 more than sufficient. Anything better would be waste of performance and
-developement efforts. Recognition whether a candidate is worth considering
+development efforts. Recognition whether a candidate is worth considering
 should be robust. Choosing the best if there are multiple similar candidates is
 suboptimal, but such a situation is really unlikely; and if it occurs, the
 question which is really the best link is disputable alyways...
Index: netrik/doc/in/hacking-terminal.in
===================================================================
--- netrik.orig/doc/in/hacking-terminal.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/hacking-terminal.in	2015-12-01 23:42:14.850226739 +0100
@@ -82,7 +82,7 @@
 in load_color_map(), which is called after reading the command line/config file
 options in main().
 
-Note that, unless explicitely overridden by --no-force-colors,
+Note that, unless explicitly overridden by --no-force-colors,
 "cfg.force_colors" is automatically set if "cfg.bright_background" is not set,
 so a black background will always be used with the dark color scheme, even on a
 terminal normally having a bright background. This isn't done with the bright
Index: netrik/doc/in/hacking.in
===================================================================
--- netrik.orig/doc/in/hacking.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/hacking.in	2015-12-01 23:41:55.402272958 +0100
@@ -86,7 +86,7 @@
 
 On the other hand, this isn't terribly efficient the way it is done now. We
 think however that in the early stage netrik is now, it's more important to
-keep the code as simple as possible to faciliate fast developement.
+keep the code as simple as possible to faciliate fast development.
 
 Also, splitting up the processing is necessary to allow rendering of not
 completely loaded pages. As this is to be one of the major features of netrik
Index: netrik/doc/in/keys.in
===================================================================
--- netrik.orig/doc/in/keys.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/keys.in	2015-12-01 23:41:55.402272958 +0100
@@ -12,7 +12,7 @@
 $$<a href="index.html">$$index.html$$</a>$$ for an overview of available netrik
 documentation.]
 
-Note: netrik is still in early developement state; keystrokes and commands are
+Note: netrik is still in early development state; keystrokes and commands are
 subject to changes.
 
 $=$$<h2>$$$_Introduction$_$$</h2>$$
Index: netrik/doc/in/options.in
===================================================================
--- netrik.orig/doc/in/options.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/options.in	2015-12-01 23:41:55.402272958 +0100
@@ -12,7 +12,7 @@
 index.txt or $$<a href="index.html">$$index.html$$</a>$$ for an overview of
 available netrik documentation.]
 
-Note: netrik is still in early developement state; options are subject to
+Note: netrik is still in early development state; options are subject to
 changes.
 
 $#<dl><dt>
Index: netrik/doc/in/syntax_error.in
===================================================================
--- netrik.orig/doc/in/syntax_error.in	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/in/syntax_error.in	2015-12-01 23:42:14.850226739 +0100
@@ -113,7 +113,7 @@
 $=$$<h2>$$Warnings in general$$</h2>$$
 
 Other similar situations are thinkable. That's why netrik also prints warnings
-on things that are strictly speaking valid hatml, but explicitely discouraged
+on things that are strictly speaking valid hatml, but explicitly discouraged
 in the HTML standard -- while some browsers will handle them correctly, others
 might do otherwise; or sometimes a really correct behaviour even produces
 results different from what the author intended and sees in popular browsers.
Index: netrik/doc/keys.html
===================================================================
--- netrik.orig/doc/keys.html	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/keys.html	2015-12-01 23:41:55.406272949 +0100
@@ -13,7 +13,7 @@
 </p>
 
 <p>
-Note: netrik is still in early developement state; keystrokes and commands are
+Note: netrik is still in early development state; keystrokes and commands are
 subject to changes.
 </p>
 
Index: netrik/doc/keys.txt
===================================================================
--- netrik.orig/doc/keys.txt	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/keys.txt	2015-12-01 23:41:55.406272949 +0100
@@ -4,7 +4,7 @@
 [This file explains the usage of the netrik interactive UI. See index.txt or
 index.html for an overview of available netrik documentation.]
 
-Note: netrik is still in early developement state; keystrokes and commands
+Note: netrik is still in early development state; keystrokes and commands
 are subject to changes.
 
 _Introduction_
Index: netrik/doc/netrik.1
===================================================================
--- netrik.orig/doc/netrik.1	2015-12-01 23:39:18.738644740 +0100
+++ netrik/doc/netrik.1	2015-12-01 23:42:14.850226739 +0100
@@ -383,7 +383,7 @@
 .SH EXIT STATUS
 .TP
 .B 0
-Normal exit. (Should occur only if explicitely issued 'q' command, or after whole page has been printed with --dump.)
+Normal exit. (Should occur only if explicitly issued 'q' command, or after whole page has been printed with --dump.)
 .TP
 .B 1
 Some condition occured that prevents netrik from continuing normal operation. This might be a memory allocation error, failure to open some important file etc. Note that it might also indicate some bug in netrik; if the error message printed doesn't seem to make sense (e.g. a memory allocation error when there is plenty of free RAM available), please report that. (See \fBBUGS\fP below.)
@@ -404,7 +404,7 @@
 It doesn't conform to XHTML also for the reason that it only warns about syntax
 errors (rather than aborting), and some may even slip through alltogether.
 .P
-Note that full standards compliance is not a primary developement goal; we may
+Note that full standards compliance is not a primary development goal; we may
 ignore known minor incompatibilities, as long as they do not undermine W3C's
 standardization efforts, and there is more important work to do...
 
Index: netrik/doc/options.html
===================================================================
--- netrik.orig/doc/options.html	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/options.html	2015-12-01 23:41:55.406272949 +0100
@@ -13,7 +13,7 @@
 </p>
 
 <p>
-Note: netrik is still in early developement state; options are subject to
+Note: netrik is still in early development state; options are subject to
 changes.
 </p>
 
Index: netrik/doc/options.txt
===================================================================
--- netrik.orig/doc/options.txt	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/options.txt	2015-12-01 23:41:55.406272949 +0100
@@ -4,7 +4,7 @@
 [This file lists all available command line options for netrik invocation. See
 index.txt or index.html for an overview of available netrik documentation.]
 
-Note: netrik is still in early developement state; options are subject
+Note: netrik is still in early development state; options are subject
 to changes.
 
 --no-term-width
Index: netrik/doc/syntax_error.html
===================================================================
--- netrik.orig/doc/syntax_error.html	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/syntax_error.html	2015-12-01 23:42:14.850226739 +0100
@@ -148,7 +148,7 @@
 
 <p>
 Other similar situations are thinkable. That's why netrik also prints warnings
-on things that are strictly speaking valid hatml, but explicitely discouraged
+on things that are strictly speaking valid hatml, but explicitly discouraged
 in the HTML standard -- while some browsers will handle them correctly, others
 might do otherwise; or sometimes a really correct behaviour even produces
 results different from what the author intended and sees in popular browsers.
Index: netrik/doc/syntax_error.txt
===================================================================
--- netrik.orig/doc/syntax_error.txt	2015-12-01 00:45:15.359853067 +0100
+++ netrik/doc/syntax_error.txt	2015-12-01 23:42:14.850226739 +0100
@@ -103,7 +103,7 @@
 Warnings in general
 
 Other similar situations are thinkable. That's why netrik also prints warnings
-on things that are strictly speaking valid hatml, but explicitely discouraged
+on things that are strictly speaking valid hatml, but explicitly discouraged
 in the HTML standard -- while some browsers will handle them correctly, others
 might do otherwise; or sometimes a really correct behaviour even produces
 results different from what the author intended and sees in popular browsers.
Index: netrik/main.c
===================================================================
--- netrik.orig/main.c	2015-12-01 00:45:15.359853067 +0100
+++ netrik/main.c	2015-12-01 23:42:14.850226739 +0100
@@ -157,7 +157,7 @@
    }
 /* <-- Patrice */
 
-   if(cfg.force_colors < 0)    /* not explicitely set -> default depends on color scheme */
+   if(cfg.force_colors < 0)    /* not explicitly set -> default depends on color scheme */
       cfg.force_colors=!cfg.bright_background;    /* force colors if dark color scheme to be used */
 
    load_color_map();
Index: netrik/parse-struct.c
===================================================================
--- netrik.orig/parse-struct.c	2015-12-01 00:45:15.359853067 +0100
+++ netrik/parse-struct.c	2015-12-01 23:42:14.854226730 +0100
@@ -529,7 +529,7 @@
 	       cur_state->form_enabled=1;
 
 	       if(cur_state->link_type==FORM_FILE)
-		  cur_state->link_value=NULL;    /* don't allow default values for file upload! (prevent uploading files not explicitely requested by user) */
+		  cur_state->link_value=NULL;    /* don't allow default values for file upload! (prevent uploading files not explicitly requested by user) */
 
                add_text(cur_state->link_type==FORM_FILE ? "[/" : "[", color_map[TM_FORM]^(cur_state->high<<3));
 	       {