diff --git a/test/unittest_about.cxx b/test/unittest_about.cxx index e51b1967c..50ceb2e9b 100644 --- a/test/unittest_about.cxx +++ b/test/unittest_about.cxx @@ -38,13 +38,13 @@ public: About(int x, int y, int w, int h) : Fl_Help_View(x, y, w, h) { value( "

About Unit Testing...

\n" -"The Unit Testing application can be used to verify correct graphis rendering " +"The Unit Testing application can be used to verify correct graphics rendering " "on the current platform. The core developer team uses this program to make sure that the " -"FLTK user experience is identical on all supprted graphics systems." +"FLTK user experience is identical on all supported graphics systems." "

the UI Designer

\n" "

Designing a good user interface is an art. Widgets must be selected and carefully positioned " "to create a consistent look and feel for the user. Text must fit into given boxes and graphic " -"elements must be correctly aligned. A good UI library will give consisten results on any " +"elements must be correctly aligned. A good UI library will give consistent results on any " "supported platform and render all graphics in the way the UI designer intended.

\n" "

FLTK supports a large collection of platforms and graphics drivers. This unit testing " "application contains modules which will test rendering and alignment for most " @@ -54,7 +54,7 @@ public: "in the same order in which a new graphics driver could be implemented. Most tests rely " "on the previous test to function correctly, so sticking to the given order is a good idea.

\n" "

Conventions

\n" -"

Two layers of graphics are drawn for most test. The lower layer contains " +"

Two layers of graphics are drawn for most tests. The lower layer contains " "red and green pixels. The upper layer contains black pixels. The test is rendered correctly " "if all red pixels are covered, but none of the green pixels. The top graphics layer can be " "switched on and off.

"