Fix various typos

CHANGES

@@ -1428,7 +1428,7 @@ s/bu_dirname\(/bu_path_dirname\(/g
 s/bu_basename\(/bu_path_basename\(/g
 s/bu_normalize\(/bu_path_normalize\(/g
 s/bu_argv_from_path\(/bu_path_to_argv\(/g
-        renamed path functons with proper group label [7.27]
+        renamed path functions with proper group label [7.27]
 s/bu_fnmatch\(/bu_path_match\(/g
 s/BU_FNMATCH_LEADING_DIR/0x0/g
 s/BU_FNMATCH_/BU_PATH_MATCH/g

CMakeLists.txt

@@ -114,7 +114,7 @@ list(APPEND CMAKE_MODULE_PATH "${BRLCAD_CMAKE_DIR}")
 # a potential source of subtle problems.  Bail with an explanation if
 # it is found to be present.
 if (EXISTS "${BRLCAD_SOURCE_DIR}/.gitattributes")
-  message(FATAL_ERROR "\nBRL-CAD does not use a .gitattributes file in its repository.  This is intended to prevent subtle errors from creeping in due to inadvertant pattern matches.  See ${BRLCAD_SOURCE_DIR}/doc/git/mime_types.txt for an in-depth discussion of the recommended alternatives to use for the problems .gitattributes is intended to address.\n")
+  message(FATAL_ERROR "\nBRL-CAD does not use a .gitattributes file in its repository.  This is intended to prevent subtle errors from creeping in due to inadvertent pattern matches.  See ${BRLCAD_SOURCE_DIR}/doc/git/mime_types.txt for an in-depth discussion of the recommended alternatives to use for the problems .gitattributes is intended to address.\n")
 endif (EXISTS "${BRLCAD_SOURCE_DIR}/.gitattributes")
 
 
@@ -128,7 +128,7 @@ else(NOT EXISTS ${BRLCAD_CNT_FILE})
   set(BRLCAD_PRINT_MSGS 0)
 endif(NOT EXISTS ${BRLCAD_CNT_FILE})
 
-# Now that we know whether or not we're supposed to, print the CMake verison
+# Now that we know whether or not we're supposed to, print the CMake version
 if(BRLCAD_PRINT_MSGS)
   message(STATUS "CMake version: ${CMAKE_VERSION}")
 endif(BRLCAD_PRINT_MSGS)
@@ -430,7 +430,7 @@ CONFIG_H_APPEND(BRLCAD "#define BRLCAD_DATA_DIR \"${DATA_DIR}\"\n")
 CONFIG_H_APPEND(BRLCAD "#define BRLCAD_DOC_DIR \"${DOC_DIR}\"\n")
 CONFIG_H_APPEND(BRLCAD "#define BRLCAD_MAN_DIR \"${MAN_DIR}\"\n")
 
-# Define the ammendment count if we have one
+# Define the amendment count if we have one
 if(DEFINED BRLCAD_VERSION_AMEND)
   CONFIG_H_APPEND(BRLCAD "#define BRLCAD_VERSION_AMEND ${BRLCAD_VERSION_AMEND}\n")
 endif(DEFINED BRLCAD_VERSION_AMEND)
@@ -2175,7 +2175,7 @@ foreach(ad ${ALL_DIRS})
   endif (DIR_TARGETS)
 endforeach(ad ${ALL_DIRS})
 
-# Now, set up the target dependencies for tiemstamp and buildtimedelta.  These
+# Now, set up the target dependencies for timestamp and buildtimedelta.  These
 # dependencies will produce a build-tool-independent ordering that gives us the
 # timing behavior we want.
 foreach(ctarget ${ALL_TARGETS})

INSTALL

@@ -331,7 +331,7 @@ files.
 System PATH:
 
 Normally, BRL-CAD's install directories are not in system PATH lists and
-consequently BRL-CAD's executables will not be invokable without specifying
+consequently BRL-CAD's executables will not be invocable without specifying
 their full path.  This is normally handled in Unix environments by adding
 the desired BRL-CAD installation's binary directory to the user's local path:
 

NEWS

@@ -484,7 +484,7 @@ performance ray tracing pipeline.
 * added brlman -S option to specify man page section  - Cliff Yapp
 * modified rtg3 to avoid outputting excessive LOS - Nick Gerstner
 * extended burst and rtg3 to output 5 digit ID numbers - Nick Gerstner
-* improved draw command manual page documenation - Cliff Yapp
+* improved draw command manual page documentation - Cliff Yapp
 * added lc -m option to report multi-material/los regions - Cliff Yapp
 * added new 'icv' image conversion tool w/ pix, bw, dpix, png, ppm
 	- Mohit Daga, Cliff Yapp, Sean Morrison, Erik Greenwald

TODO

@@ -104,7 +104,7 @@ THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
   duplicate entries.
 
 * tree command shouldn't infinite loop when encountering a cyclic
-  path - need to print a warning and stop walking.  Requries full
+  path - need to print a warning and stop walking.  Requires full
   path awareness in tree command walk.
 
   Consider implementing a corollary to FTS instead of dirent for
@@ -236,7 +236,7 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 
 * the osgl libdm backend has what appears to be an off-by-one-pixel
   error in the x and y directions with respect to mouse placement.
-  Using kmag, can see tha putting the mouse cursor over the center
+  Using kmag, can see that putting the mouse cursor over the center
   yellow dot and center clicking (which should be a no-op, and is
   with ogl) results in the scene shifting slightly.
 
@@ -1722,7 +1722,7 @@ NEW OBJECTS
   orthogonal vs perspective, ambient lighting levels, and possibly
   styling/render modes.
 
-  obviously need to be able to derive a homogenous transformation
+  obviously need to be able to derive a homogeneous transformation
   matrix, but may want to encode/preserve scale, translate, rotate
   with prescribed ordering separately for proper reversibility.
 

bench/benchmark.c

@@ -393,7 +393,7 @@ main(int ac, char *av[])
 	bu_log("well-known datasets into 512x512 images where performance metrics are\n");
 	bu_log("documented and fairly well understood.  The local machine's\n");
 	bu_log("performance is compared to the base system (called VGR) and a numeric\n");
-	bu_log("\"VGR\" mulitplier of performance is computed.  This number is a\n");
+	bu_log("\"VGR\" multiplier of performance is computed.  This number is a\n");
 	bu_log("simplified metric from which one may qualitatively compare cpu and\n");
 	bu_log("cache performance, versions of BRL-CAD, and different compiler\n");
 	bu_log("characteristics.\n");
@@ -433,7 +433,7 @@ main(int ac, char *av[])
 	bu_log("effectively performing a multiplier amount of work over the initial\n");
 	bu_log("frame.\n");
 	bu_log("\n");
-	bu_log("Plese send your BRL-CAD Benchmark results to the developers along with\n");
+	bu_log("Please send your BRL-CAD Benchmark results to the developers along with\n");
 	bu_log("detailed system information to <devs@brlcad.org>.  Include at least:\n");
 	bu_log("\n");
 	bu_log("  0) Compiler name and version (e.g. gcc --version)\n");

db/faa/Generic_Twin.fg4

@@ -64920,7 +64920,7 @@ CQUAD         12      13       4      12      16       8   0.000       2
 CCONE2         1       4      17      18                           2.250 +      
  +         2.250   0.000   0.000
 SECTION        3     168       2       1
-$NAME          3     168                                Horiztonal Stabilator  Vector Pulley left forward
+$NAME          3     168                                Horizontal Stabilator  Vector Pulley left forward
 $COMMENT12345678123456781234567812345678123456781234567812345678123456781234567812345678
 $COMMENT       2       3       4       5       6       7       8       9      10
 GRID           1        -280.990   6.010 208.570
@@ -64992,7 +64992,7 @@ CQUAD         12      13       4      12      16       8   0.000       2
 CCONE2         1       4      17      18                           0.500 +      
  +         0.500   0.000   0.000
 SECTION        3     170       2       1
-$NAME          3     170                                Horiztonal Stabilator  Vector Pulley left aft
+$NAME          3     170                                Horizontal Stabilator  Vector Pulley left aft
 $COMMENT12345678123456781234567812345678123456781234567812345678123456781234567812345678
 $COMMENT       2       3       4       5       6       7       8       9      10
 GRID           1        -1239.68   7.150 204.800
@@ -65064,7 +65064,7 @@ CQUAD         12      13       4      12      16       8   0.000       2
 CCONE2         1       4      17      18                           0.500 +      
  +         0.500   0.000   0.000
 SECTION        3     172       2       1
-$NAME          3     172                                Horiztonal Stabilator  Vector Pulley right forward
+$NAME          3     172                                Horizontal Stabilator  Vector Pulley right forward
 $COMMENT12345678123456781234567812345678123456781234567812345678123456781234567812345678
 $COMMENT       2       3       4       5       6       7       8       9      10
 GRID           1        -280.990  -6.010 208.570
@@ -65136,7 +65136,7 @@ CQUAD         12      13       4      12      16       8   0.000       2
 CCONE2         1       4      17      18                           0.500 +      
  +         0.500   0.000   0.000
 SECTION        3     174       2       1
-$NAME          3     174                                Horiztonal Stabilator  Vector Pulley right aft
+$NAME          3     174                                Horizontal Stabilator  Vector Pulley right aft
 $COMMENT12345678123456781234567812345678123456781234567812345678123456781234567812345678
 $COMMENT       2       3       4       5       6       7       8       9      10
 GRID           1        -1239.68  -7.150 204.800
@@ -209761,7 +209761,7 @@ CTRI          10       1       4       6       8           0.100       2
 CTRI          11       1       5       7       1           0.100       2
 CTRI          12       1       7       2       1           0.100       2
 SECTION        9     639       2       0
-$NAME          9     639                                Standby power contol unit
+$NAME          9     639                                Standby power control unit
 GRID           1        -217.100 -43.700 249.434
 GRID           2        -217.100 -44.700 247.434
 GRID           3        -217.000 -43.700 249.434

doc/docbook/system/man1/burst.xml

@@ -584,7 +584,7 @@ depth 52.88mm at (-418.907,-812.8,0) x-2 y1 lvl1 purpose=spall ray
 	<refsection xml:id="bursting_1_2_1">
 	  <title>Burst on Armor</title>
 	  <para>
-	    If the <command>burst-distance</command> paramter is set to a negative or zero value, then
+	    If the <command>burst-distance</command> parameter is set to a negative or zero value, then
 	    interior burst points will be generated (see <link linkend="bursting_2_1">Burst Distance</link>).
 	    This method of bursting requires the input of burst armor idents and, by default, burst
 	    air idents are also required. If the user does not want to require that certain air be

doc/docbook/system/man1/iges-g.xml

@@ -43,7 +43,7 @@ combined into one BRL-CAD spline solid.
 The
 <option>-d</option>
 option indicates that IGES drawings should be converted to BRL-CAD NMG objects.
-Theses objects will be two-dimensional drawings, not solids.
+These objects will be two-dimensional drawings, not solids.
 The
 <option>-3</option>
 option is the same as the

doc/docbook/system/mann/facetize.xml

@@ -61,7 +61,7 @@
     <para>
       Creates <emphasis>new_object</emphasis> as planar primitive shape (either an NMG or a BOT)
       approximating the 3D volume bound by <emphasis>old_object</emphasis>.  The <emphasis>-r</emphasis>
-      option will operate per-region rather than on an entire object and produces a new hiearchy.
+      option will operate per-region rather than on an entire object and produces a new hierarchy.
     </para>
     <para>
       There are a number of different verbosity levels available for the facetize command.  One or mulitple specifications

doc/docbook/system/mann/get.xml

@@ -35,7 +35,7 @@
 
   <example><title>Elliptical Torus 'r' parameter extraction</title>
   <para>
-    Use the <command>get</command> command to exctract the
+    Use the <command>get</command> command to extract the
     r parameter value from an elliptical torus.
   </para>
 

doc/html/manuals/mged/ged.html

@@ -1798,7 +1798,7 @@ <h3>Ellipsoid Parameter Editing</h3>
   editing.</p>
   <p>The parameter editing of the ELLG consists of scaling the
   lengths of the individual vectors A, B, C. One may also scale all
-  theses vectors together of equal length.</p>
+  these vectors together of equal length.</p>
   <p>The scaling of these vectors is done using the data
   tablet/mouse in exactly the same manner as in object scaling. The
   <i>p</i> keyboard command again can be used to produce a vector

doc/html/manuals/mged/ged.tex

@@ -1992,7 +1992,7 @@ \subsection{Ellipsoid Parameter Editing}
 
 The parameter editing of the ELLG consists of scaling the lengths of the
 individual vectors A, B, C.
-One may also scale all theses vectors together of equal length.
+One may also scale all these vectors together of equal length.
 
 The scaling of these vectors is done using the data tablet/mouse in
 exactly the same manner as in object scaling.

doc/html/manuals/mged/shaders.html

@@ -1228,7 +1228,7 @@ <h3>Example</h3>
       <a class="c1" name="testmap" id="testmap">testmap</a>
     </dt>
     <dd>Ramps the red value from off to on as the "u" coord of a
-    texture map varis fro m0 to 1, and the blue value with the "v"
+    texture map varies from m0 to 1, and the blue value with the "v"
     coordinate. For debugging.</dd>
     <dd>
       <h3>Parameters</h3>

doc/mged/d.tex

@@ -619,7 +619,7 @@ \subsection{Ellipsoid Parameter Editing}
 
 The parameter editing of the ELLG consists of scaling the lengths of the
 individual vectors A, B, C.
-One may also scale all theses vectors together of equal length.
+One may also scale all these vectors together of equal length.
 
 The scaling of these vectors is done using the data tablet/mouse in
 exactly the same manner as in object scaling.

doc/mged/g.tex

@@ -1270,7 +1270,7 @@ \subsection{Scale Operation}
 of the scale operation from the Solid Edit menu
 will result in the values of all the vectors being
 multiplied by the value of the scale.
-Use of the scale operaton from the Ellipsoid menu
+Use of the scale operation from the Ellipsoid menu
 with a particular vector A, B, or C changes the
 magnitude of that vector to the value of the scale.
 

doc/notes/cmake_paths/test.cmake.in

@@ -9,7 +9,7 @@ set(BIN_DIR "@BIN_DIR@")
 message(BIN_DIR:  ${BIN_DIR})
 
 # Using the above two pieces of information, construct the "root" path
-# below which the standard BRL-CAD file hiearchy (binary, library, data,
+# below which the standard BRL-CAD file hierarchy (binary, library, data,
 # doc, etc.) is built.
 string(REGEX REPLACE "${BIN_DIR}$" "" ROOT_DIR "${EXEC_DIR}")
 message(ROOT_DIR: ${ROOT_DIR})

include/analyze/info.h

@@ -93,7 +93,7 @@ analyze_total_volume(struct current_state *context);
 
 /**
  * stores the region name, volume, high and low ranges of volume
- * for the specifed index of region in region table.
+ * for the specified index of region in region table.
  */
 ANALYZE_EXPORT extern void
 analyze_volume_region(struct current_state *context, int index, char** reg_name, double *volume, double *high, double *low);
@@ -112,7 +112,7 @@ analyze_total_mass(struct current_state *context);
 
 /**
  * stores the region name, mass, high and low ranges of mass
- * for the specifed index of region in region table.
+ * for the specified index of region in region table.
  */
 ANALYZE_EXPORT extern void
 analyze_mass_region(struct current_state *context, int index, char** reg_name, double *mass, double *high, double *low);
@@ -155,7 +155,7 @@ analyze_total_surf_area(struct current_state *state);
 
 /**
  * stores the region name, surf_area, high and low ranges of surf_area
- * for the specifed index of region in region table.
+ * for the specified index of region in region table.
  */
 ANALYZE_EXPORT extern void
 analyze_surf_area_region(struct current_state *state, int i, char **name, double *surf_area, double *high, double *low);

include/brlcad_ident.h.in

@@ -25,7 +25,7 @@
  * They should use the library-specific LIBRARY_version() functions.
  * (e.g. bu_version())
  *
- * NOTE: In order to use compile-time API, applicaitons need to define
+ * NOTE: In order to use compile-time API, applications need to define
  * BRLCADBUILD and HAVE_CONFIG_H before including this header.
  */
 

include/brlcad_version.h.in

@@ -27,7 +27,7 @@
  * versioning.  Applications are encouraged to use library-specific
  * LIBRARY_version() functions.  (e.g. bu_version())
  *
- * NOTE: In order to use compile-time API, applicaitons need to define
+ * NOTE: In order to use compile-time API, applications need to define
  * BRLCADBUILD and HAVE_CONFIG_H before including this header.
  */
 

include/bu/defines.h

@@ -180,7 +180,7 @@
 
 /**
  * shorthand declaration of a function that doesn't accept NULL
- * pointer arugments.  if a null pointer is detected during
+ * pointer arguments.  if a null pointer is detected during
  * compilation, a warning/error can be emitted.
  */
 #ifdef HAVE_NONNULL_ATTRIBUTE

include/bu/glob.h

@@ -116,7 +116,7 @@ BU_EXPORT struct bu_glob_context *bu_glob_init();
 
 
 /**
- * release any resoures allocated during bu_glob(), including any
+ * release any resources allocated during bu_glob(), including any
  * returned paths
  */
 BU_EXPORT extern void bu_glob_free(struct bu_glob_context *);

include/common.h

@@ -27,7 +27,7 @@
  * either detected via configure or hand crafted, as is the case for
  * the win32 platform.
  *
- * NOTE: In order to use compile-time API, applicaitons need to define
+ * NOTE: In order to use compile-time API, applications need to define
  * BRLCADBUILD and HAVE_CONFIG_H before including this header.
  *
  */
@@ -215,7 +215,7 @@ typedef ptrdiff_t ssize_t;
 
 /* off_t is 32 bit size even on 64 bit Windows. In the past we have tried to
  * force off_t to be 64 bit but this is failing on newer Windows/Visual Studio
- * verions in 2020 - therefore, we instead introduce the b_off_t define to
+ * versions in 2020 - therefore, we instead introduce the b_off_t define to
  * properly substitute the correct numerical type for the correct platform.  */
 #if defined(_WIN64)
 #  include <sys/stat.h>

include/dm/fbserv.h

@@ -67,8 +67,8 @@ struct fbserv_listener {
 
 struct fbserv_client {
     int fbsc_fd;                        /**< @brief socket to send data down */
-    void *fbsc_chan;                    /**< @brief platform/tookit specific channel */
-    void *fbsc_handler;                 /**< @brief platform/tookit specific handler */
+    void *fbsc_chan;                    /**< @brief platform/toolkit specific channel */
+    void *fbsc_handler;                 /**< @brief platform/toolkit specific handler */
     struct pkg_conn *fbsc_pkg;
     struct fbserv_obj *fbsc_fbsp;       /**< @brief points to its fbserv object */
 };
@@ -82,10 +82,10 @@ struct fbserv_obj {
 
     int (*fbs_is_listening)(struct fbserv_obj *);          /**< @brief return 1 if listening, else 0 */
     int (*fbs_listen_on_port)(struct fbserv_obj *, int);  /**< @brief return 1 on success, 0 on failure */
-    void (*fbs_open_server_handler)(struct fbserv_obj *);   /**< @brief platform/tookit method to open listener handler */
-    void (*fbs_close_server_handler)(struct fbserv_obj *);   /**< @brief platform/tookit method to close handler listener */
-    void (*fbs_open_client_handler)(struct fbserv_obj *, int, void *);   /**< @brief platform/tookit specific client handler setup (called by fbs_new_client) */
-    void (*fbs_close_client_handler)(struct fbserv_obj *, int);   /**< @brief platform/tookit method to close handler for client at index client_id */
+    void (*fbs_open_server_handler)(struct fbserv_obj *);   /**< @brief platform/toolkit method to open listener handler */
+    void (*fbs_close_server_handler)(struct fbserv_obj *);   /**< @brief platform/toolkit method to close handler listener */
+    void (*fbs_open_client_handler)(struct fbserv_obj *, int, void *);   /**< @brief platform/toolkit specific client handler setup (called by fbs_new_client) */
+    void (*fbs_close_client_handler)(struct fbserv_obj *, int);   /**< @brief platform/toolkit method to close handler for client at index client_id */
 
     void (*fbs_callback)(void *);                  /**< @brief callback function */
     void *fbs_clientData;