Merge pull request #1490 from gsjaardema/spelling_fixes

Spelling fixes

Author: WardF

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