Spelling fixes

CMakeLists.txt

@@ -924,7 +924,7 @@ IF(ENABLE_TESTS)
   # same thing as an 'expected failure'. Rather, these
   # are tests that will need to be fixed eventually.
   #
-  # By placing them here, we can occasionaly turn this
+  # By placing them here, we can occasionally turn this
   # flag on and see if any known failures have been
   # fixed in the course of code improvement/other bug
   # fixes.

RELEASE_NOTES.md

@@ -111,7 +111,7 @@ See [GitHub #1251](https://github.com/Unidata/netcdf-c/issues/1251).
 (2) appending "#protocol=dap4" to the end of the url, or
 (3) appending "#dap4" to the end of the url
 Note that dap4 is enabled by default but remote-testing is
-disbled until the testserver situation is resolved.
+disabled until the testserver situation is resolved.
 * [Enhancement] The remote testing server can now be specified with the `--with-testserver` option to ./configure.
 * [Enhancement] Modified netCDF4 to use ASCII for NC_CHAR.  See [Github Pull request #316](https://github.com/Unidata/netcdf-c/pull/316) for more information.
 * [Bug Fix] Corrected an error with how dimsizes might be read. See [Github #410](https://github.com/unidata/netcdf-c/issues/410) for more information.
@@ -446,7 +446,7 @@ More details may be found at the Unidata JIRA Dashboard.  [NCF-316](https://bugt
 
 * Refactored how types are used for attributes, variables, and committed types, clarifying and categorizing fields in structs, and eliminating duplicated type information between variables and types they use.
 
-* Made type structure sharable by committed datatypes and variables that use it.
+* Made type structure shareable by committed datatypes and variables that use it.
 
 * Handled string datatypes correctly, particularly for fill value attributes. Expanded testing for string fill values.
 
@@ -1327,7 +1327,7 @@ variables.
 * Fixed ncgen to properly handle CDL input that uses Windows line endings
 ("\r\n"), instead of getting a syntax error.
 
-* Added "-s" option to ncdump to display performance characterisitics of
+* Added "-s" option to ncdump to display performance characteristics of
 netCDF-4 files as special virtual attributes, such as \_Chunking,
 \_DeflateLevel, \_Format, and \_Endianness.
 

dap4_test/test_fillmismatch.sh

@@ -22,7 +22,7 @@ else
 echo "*** XFail: ${NCDUMP} ${URL} failed"
 fi
 
-# Now check that with [fillmismatch], we get sucess
+# Now check that with [fillmismatch], we get success
 URL="[fillmismatch]${URL}"
 rm -f ./tmp_dap4_mismatch
 if ${NCDUMP} -h "${URL}" > ./tmp_dap4_mismatch ; then

docs/FAQ.md

@@ -28,7 +28,7 @@ NetCDF data is:
     efficiently.
 -   *Appendable*. Data may be appended to a properly structured netCDF
     file without copying the dataset or redefining its structure.
--   *Sharable*. One writer and multiple readers may simultaneously
+-   *Shareable*. One writer and multiple readers may simultaneously
     access the same netCDF file.
 -   *Archivable*. Access to all earlier forms of netCDF data will be
     supported by current and future versions of the software.

docs/credits.md

@@ -113,6 +113,6 @@ Science Foundation, Unidata's primary sponsor. Development of the
 netCDF-4 interface was initially funded by NASA's Earth Science
 Technology Office. Addition of OPeNDAP client support to the netCDF
 library is based on work supported by the National Science Foundation.
-Any opinions, findings and conclusions or recomendations expressed in
+Any opinions, findings and conclusions or recommendations expressed in
 this material are those of the authors and do not necessarily reflect
 the views of the sponsoring organizations.

docs/dispatch.dox

@@ -23,5 +23,5 @@ netCDF-4/HDF5 files, and the remote data access features.
 
 Conceptually, the dispatch layer provides the same capabilities as the
 IOSP in the netCDF-Java library. However, unlike Java, C does not
-provide the advanced features to make this seemless.
+provide the advanced features to make this seamless.
 */

docs/guide.dox

@@ -2370,7 +2370,7 @@ Examine the translated DDS for the DAP source from the specified URL:
 \endcode
 
 Without dumping all the data, show the special virtual attributes that indicate
-performance-related characterisitics of a netCDF-4 file:
+performance-related characteristics of a netCDF-4 file:
 
 \code
    ncdump -h -s nc4file.nc
@@ -2782,15 +2782,15 @@ netCDF specification. The C source code is written to standard
 output. This is only useful for relatively small CDL files, since all
 the data is included in variable initializations in the generated
 program. The -c flag is deprecated and the -lc flag should be used
-intstead.
+instead.
 
 -f
 Generate FORTRAN source code that will create a netCDF dataset
 matching the netCDF specification. The FORTRAN source code is written
 to standard output. This is only useful for relatively small CDL
 files, since all the data is included in variable initializations in
 the generated program. The -f flag is deprecated and the -lf77 flag
-should be used intstead.
+should be used instead.
 
 -k
 The -k file specifies the kind of netCDF file to generate. The

docs/indexing.dox

@@ -176,7 +176,7 @@ use a hash table for name indexing, but rather keep a list sorted by name
 and use binary search to do name-based lookup. If this alternative were
 implemented, then it is probable that we could get rid of using the NC_hashmap
 structure altogether for netcdf-4. There is a performance cost since binary
-search is O(log n). In practice, it is probable that this is of negligable
+search is O(log n). In practice, it is probable that this is of negligible
 effect. The advantage is that rename operations become considerably simpler.
 
 \section Sglobal_object_access Global Object Access

docs/inmeminternal.dox

@@ -77,7 +77,7 @@ caller, and it is the caller's responsibility to _free_ the memory.
 The implementation of in-memory support for netcdf-4 files
 is quite complicated. 
 
-The netCDF-4 implemention relies on the HDF5 library.  In order
+The netCDF-4 implementation relies on the HDF5 library.  In order
 to implement in-memory storage of data, the HDF5 core driver is
 used to manage underlying storage of the netcdf-c file.
 
@@ -248,7 +248,7 @@ then we cannot realloc and we must fake it as follows:
 
 1. If the chunk is big enough, then pretend to do a realloc by
    changing the vfd_image_size.
-2. If the chunk is not big enough to accomodate the requested new size,
+2. If the chunk is not big enough to accommodate the requested new size,
    then fail.
 
 There is one important complication. It turns out that the image_realloc

docs/inmemory.md

@@ -152,7 +152,7 @@ cannot complete because the memory needs to be expanded.
 the netcdf library will take control of the incoming memory.
 This means that the user should not make any attempt to free
 or even read the incoming memory block in this case.
-The newcdf library is free to reallocate the incomming
+The newcdf library is free to reallocate the incoming
 memory block to obtain a larger block when an attempt to modify
 the in-memory file requires more space. Note that implicit in this
 is that the old block -- the one originally provided -- may be

docs/known_problems.md

@@ -945,7 +945,7 @@ current support (and test on) at Unidata. The only known work around is
 to build without the --enable-shared option.
 
 Any user who can debug this problem with the NAG compiler should send
-the resuts to [email protected], so that it can be
+the results to [email protected], so that it can be
 incorporated into the netCDF distribution.
 
 Interested users may also wish to subscribe to the [netcdf-porting

docs/netcdf.m4

@@ -782,7 +782,7 @@ Learn about a variable length array type.
 .HP
 FDECL(free_vlen, (nc_vlen_t *vl))
 .sp
-Free memory comsumed by reading data of a variable length array type.
+Free memory consumed by reading data of a variable length array type.
 .HP
 FDECL(put_vlen_element, (INCID(), INCTYPE(), IVOIDP(vlen_element), ISIZET(len), IVOIDP(data)))
 .sp
@@ -794,7 +794,7 @@ Read one VLEN.
 .HP
 FDECL(free_string, (ISIZET(len), char **data))
 .sp
-Free memory comsumed by reading data of a string type.
+Free memory consumed by reading data of a string type.
 .HP
 FDECL(inq_user_type, (INCID(), INCTYPE(), ONAME(), OSIZET(), ONCTYPE(), OSIZET(), OINT()))
 .sp

docs/old/netcdf.texi

@@ -875,7 +875,7 @@ through the netCDF C or Fortran interfaces, support for parallel I/O
 on netCDF classic and 64-bit offset files using the PnetCDF
 library from Argonne/Northwestern, a new nc-config
 utility to help compile and link programs that use netCDF, inclusion
-of the UDUNITS library for hadling ``units'' attributes, and inclusion
+of the UDUNITS library for handling ``units'' attributes, and inclusion
 of libcf to assist in creating data compliant with the Climate and
 Forecast (CF) metadata conventions.
 
@@ -1589,7 +1589,7 @@ The extended CDL syntax for the enhanced
 data model supported by netCDF-4 allows optional type specifications,
 including user-defined types, for
 attributes of user-defined types.  See ncdump output or the reference
-documentation for ncgen for details of the extended CDL systax.
+documentation for ncgen for details of the extended CDL syntax.
 
 In the netCDF example (@pxref{Data Model}), units is an attribute for
 the variable lat that has a 13-character array value
@@ -4033,7 +4033,7 @@ Password for accessing the HTTP.SSL.KEY/HTTP.SSL.CERTIFICATE
     @item Type: String representing directory
     @item Description:
 Path to a directory containing trusted certificates for validating
-server sertificates.
+server certificates.
     @item Related CURL Flags: CURLOPT_CAPATH
     @end enumerate
 
@@ -4191,7 +4191,7 @@ double slash characters '//' on any line.
 A CDL description for a classic model file consists of three optional
 parts: dimensions, variables, and data. The variable part may contain
 variable declarations and attribute assignments.  For the enhanced
-model supported by netCDF-4, a CDL decription may also includes
+model supported by netCDF-4, a CDL description may also includes
 groups, subgroups, and user-defined types.
 
 A dimension is used to define the shape of one or more of the
@@ -4337,10 +4337,10 @@ Unsigned 16-bit integers.
 Unsigned 32-bit integers.
  
 @item int64
-64-bit singed integers.
+64-bit signed integers.
  
 @item uint64
-Unsigned 64-bit singed integers.
+Unsigned 64-bit signed integers.
  
 @item string
 Variable-length string of characters
@@ -4521,15 +4521,15 @@ netCDF specification. The C source code is written to standard
 output. This is only useful for relatively small CDL files, since all
 the data is included in variable initializations in the generated
 program.
-The -c flag is deprecated and the -lc flag should be used intstead.
+The -c flag is deprecated and the -lc flag should be used instead.
  
 @item -f
 Generate FORTRAN source code that will create a netCDF dataset
 matching the netCDF specification. The FORTRAN source code is written
 to standard output. This is only useful for relatively small CDL
 files, since all the data is included in variable initializations in
 the generated program.
-The -f flag is deprecated and the -lf77 flag should be used intstead.
+The -f flag is deprecated and the -lf77 flag should be used instead.
 
 @item -k
 The -k file specifies the kind of netCDF file to generate.
@@ -5947,7 +5947,7 @@ document.  For more information about HDF5, see the HDF5 web site:
 @uref{http://hdf.ncsa.uiuc.edu/HDF5/}. 
 
 The specification that follows is sufficient to allow HDF5 users to
-create files that will be accessable from netCDF-4.
+create files that will be accessible from netCDF-4.
 
 @subsection Creation Order 
 
@@ -6276,7 +6276,7 @@ Starting with version 4.1, the netCDF libraries can read HDF4 SD
 created with the Scientific Dataset API. Access is read-only.
 
 Dataset types are translated between HDF4 and netCDF in a
-straighforward manner.
+straightforward manner.
 
 @table @code
 @item DFNT_CHAR

docs/user_defined_formats.md

@@ -40,7 +40,7 @@ associated with the user-defined format, then netCDF will be able to
 correctly identify those files from nc_open(). It will not be
 necessary for the user to know or specify the underlying format.
 
-## Using User-Defined Formats from C Programms {#udf_With_C}
+## Using User-Defined Formats from C Programs {#udf_With_C}
 
 A user-defined format can be added dynamically in the case of C programs.
 
@@ -83,7 +83,7 @@ be specified with the --with-udf0-magic-number= argument.
 
 ## Creating a User-Defined Format {#udf_Create_UDF}
 
-Creators of user-defined format libraries will have to become familar
+Creators of user-defined format libraries will have to become familiar
 with the internals of the netCDF-4 code.
 
 ### Read-Only User-Defined Formats

dods.m4

@@ -317,10 +317,10 @@
 #     AC_MSG_RESULT($IDL_ROOT)
 #     AC_SUBST(IDL_ROOT)
 # 
-#     # Now find where the IDL 5.2 or later sharable libraries live.
+#     # Now find where the IDL 5.2 or later shareable libraries live.
 #     # NB: This won't work if libraries for several architecutures are 
 #     # installed for several machines.
-#     AC_MSG_CHECKING(for the IDL sharable library directory)
+#     AC_MSG_CHECKING(for the IDL shareable library directory)
 #     # cd to the IDL root because it is likely a symbolic link and find 
 #     # won't normally follow symbolic links.
 #     IDL_LIBS=`(cd $IDL_ROOT; find . -name 'libidl.so' -print)`

examples/C/file.c

@@ -55,7 +55,7 @@ main()
 
    int i, res;
 
-   /* Create a classic format netCDF file, overwritting any file of
+   /* Create a classic format netCDF file, overwriting any file of
       this name that may already exist. */
    if ((res = nc_create(FILENAME, NC_CLOBBER, &ncid)))
       BAIL(res);

examples/C/run_par_test.sh.in

@@ -7,6 +7,6 @@
 
 set -e
 echo
-echo "Runnung pnetcdf parallel I/O example..."
+echo "Running pnetcdf parallel I/O example..."
 @MPIEXEC@ -n 4 ./parallel_vara
 echo '*** SUCCESS!!!'

examples/C/simple_xy_nc4_rd.c

@@ -5,7 +5,7 @@
  * Read the simple_xy file, with some of the features of netCDF-4.
  *
  * This is a very simple example which is based on the simple_xy
- * example, but whch uses netCDF-4 features, such as
+ * example, but which uses netCDF-4 features, such as
  * compression. Please see the simple_xy example to learn more about
  * the netCDF-3 API.
  *

examples/C/simple_xy_nc4_wr.c

@@ -5,7 +5,7 @@
  * Write the simple_xy file, with some of the features of netCDF-4.
  *
  * This is a very simple example which is based on the simple_xy
- * example, but whch uses netCDF-4 features, such as
+ * example, but which uses netCDF-4 features, such as
  * compression. Please see the simple_xy example to learn more about
  * the netCDF-3 API.
  *

h5_test/tst_h_enums.c

@@ -18,7 +18,7 @@
 #define NUM_VALS 12
 #define STR_LEN 255
 
-/* This seems like a good sonnet for enumation:
+/* This seems like a good sonnet for enumeration:
 
 How do I love thee? Let me count the ways.
 I love thee to the depth and breadth and height

h5_test/tst_h_files.c

@@ -136,7 +136,7 @@ main()
 	  H5Fclose(fileid) < 0) ERR;
 
       /* Now create the file again, to make sure that it really is not
-       * just mearly dead, but really most sincerely dead. */
+       * just nearly dead, but really most sincerely dead. */
       if ((fileid = H5Fcreate(FILE_NAME, H5F_ACC_TRUNC, H5P_DEFAULT, 
 			      access_plist)) < 0) ERR;
       if (H5Fclose(fileid) < 0) ERR;

h5_test/tst_h_ints.c

@@ -20,7 +20,7 @@ main()
    printf("*** checking 1D int dataset with extend...");
    {
 
-/* Misspelling is deliberite. Please dont correct. */
+/* Misspelling is deliberate. Please dont correct. */
 #define INTERGERS "Intergers"      
 #define NUM_STR 1
 #define NDIMS 1

h5_test/tst_h_vars.c

@@ -27,7 +27,7 @@ main()
    hsize_t dims[1];
 
    printf("\n*** Checking HDF5 variable functions.\n");
-   printf("*** Checking HDF5 boolen variables...");
+   printf("*** Checking HDF5 boolean variables...");
 
    /* Open file and create group. */
    if ((fileid = H5Fcreate(FILE_NAME, H5F_ACC_TRUNC, H5P_DEFAULT,

hdf4_test/tst_hdf4_extra.c

@@ -87,7 +87,7 @@ main(int argc, char **argv)
       for (i = 0; i < LAT_LEN * LON_LEN; i++)
          if (data_int[i] != i) ERR;
 
-      /* NULL count is treated as meaing entire variable. */
+      /* NULL count is treated as meaning entire variable. */
       if (nc_get_vara_int(ncid, 0, start, NULL, data_int2)) ERR;
       for (i = 0; i < LAT_LEN * LON_LEN; i++)
          if (data_int2[i] != i) ERR;

include/hdf5internal.h

@@ -22,7 +22,7 @@
 
 #define NC_MAX_HDF5_NAME (NC_MAX_NAME + 10)
 
-/* These have to do with creating chuncked datasets in HDF5. */
+/* These have to do with creating chunked datasets in HDF5. */
 #define NC_HDF5_UNLIMITED_DIMSIZE (0)
 #define NC_HDF5_CHUNKSIZE_FACTOR (10)
 #define NC_HDF5_MIN_CHUNK_SIZE (2)

include/nc4internal.h

@@ -58,7 +58,7 @@ typedef enum {NCNAT, NCVAR, NCDIM, NCATT, NCTYP, NCFLD, NCGRP} NC_SORT;
 #define X_SCHAR_MIN     (-128)          /**< Minimum signed char value. */
 #define X_SCHAR_MAX     127             /**< Maximum signed char value. */
 #define X_UCHAR_MAX     255U            /**< Maximum unsigned char value. */
-#define X_SHORT_MIN     (-32768)        /**< Minumum short value. */
+#define X_SHORT_MIN     (-32768)        /**< Minimum short value. */
 #define X_SHRT_MIN      X_SHORT_MIN     /**< This alias is compatible with limits.h. */
 #define X_SHORT_MAX     32767           /**< Maximum short value. */
 #define X_SHRT_MAX      X_SHORT_MAX     /**< This alias is compatible with limits.h. */

include/nc_logging.h

@@ -5,7 +5,7 @@
  * interface for HDF5, or a HDF5 backend for netCDF, depending on your
  * point of view.
  *
- * This file contains macros and prototyes relating to logging.
+ * This file contains macros and prototypes relating to logging.
  *
  * @author Ed Hartnett
 */

include/netcdf.h

@@ -1765,7 +1765,7 @@ EXTERNL int
 nc_delete(const char *path);
 
 /*
- * The following functions were written to accomodate the old Cray
+ * The following functions were written to accommodate the old Cray
  * systems. Modern HPC systems do not use these functions any more,
  * but use the nc_open_par()/nc_create_par() functions instead. These
  * functions are retained for backward compatibibility. These