typos

CHANGELOG.md

@@ -1,10 +1,10 @@
 Version History
 ---------------
 
-### Changes in v2.1.0
+### Changes in v2.1.0:
 
 -   New clipping geometries feature that allows clipping any scene
-    (gemetry and volumes); all OSPRay geometry types can by used as
+    (geometry and volumes); all OSPRay geometry types can by used as
     clipping geometry
     -   Inverted clipping is supported via new `invertNormals` parameter
         of `GeometricModel`
@@ -24,15 +24,15 @@ Version History
 -   Generalized `cpp::Device` parameter setting to match other handle
     types
 -   Passing `NULL` to `ospRelease` is not reported as error anymore
--   Fix computation of strides for ospData
+-   Fix computation of strides for `OSPData`
 -   Fix transparency in `scivis` renderer
 -   Add missing C++ wrapper for `ospGetVariance`
 -   Proper demonstration of `ospGetVariance` in `ospTutorialAsync`
 -   Fix handling of `--osp:device-params` to process and set all passed
     arguments first before committing the device, to ensure it is
     committed in a valid state.
 -   Object factory functions are now registered during module
-    initialization via the appropiate `registerType` function
+    initialization via the appropriate `registerType` function
 -   Fix issue with OSPRay ignoring tasking system thread count settings
 -   Fix issue where OSPRay always loaded the ISPC module, even if not
     required

doc/api.md

@@ -156,7 +156,7 @@ to avoid leaking the underlying device object.
 OSPRay allows applications to query runtime properties of a device in
 order to do enhanced validation of what device was loaded at runtime.
 The following function can be used to get these device-specific
-properties (attiributes about the device, not paramter values)
+properties (attributes about the device, not parameter values)
 
     int64_t ospDeviceGetProperty(OSPDevice, OSPDeviceProperty);
 
@@ -475,7 +475,7 @@ shared with OSPData by the application (created with
 
   - the source array must be shared as well (thus `ospCopyData` cannot
     be used to read opaque data)
-  - if source and destination memory overlaps (aliasing), then behaviour
+  - if source and destination memory overlaps (aliasing), then behavior
     is undefined
   - except if source and destination regions are identical (including
     matching strides), which can be used by application to mark that
@@ -681,7 +681,7 @@ the vertices and data values. Vertex ordering is the same as
 vertex.
 
 To maintain VTK data compatibility an index array may be specified via
-the `indexPrefixed` array that allow vertex indices to be interleaved
+the `indexPrefixed` array that allows vertex indices to be interleaved
 with cell sizes in the following format: $n, id_1, ..., id_n, m, id_1,
 ..., id_m$.
 
@@ -725,7 +725,7 @@ with cell sizes in the following format: $n, id_1, ..., id_n, m, id_1,
                                                      inaccuracies may appear if hex is not
                                                      parallelepiped
 
-  bool                 precomputedNormals      true  whether to accelerate by precomputing,
+  bool                 precomputedNormals     false  whether to accelerate by precomputing,
                                                      at a cost of 12 bytes/face
   -------------------  ------------------  --------  ---------------------------------------
   : Additional configuration parameters for unstructured volumes.
@@ -794,7 +794,7 @@ maximum of 2^32^ primitives.
 
 ### Mesh
 
-A mesh consiting of either triangles or quads is created by calling
+A mesh consisting of either triangles or quads is created by calling
 `ospNewGeometry` with type string "`mesh`". Once created, a mesh
 recognizes the following parameters:
 
@@ -966,7 +966,7 @@ discussion of curve types and data formatting).
 If a constant `radius` is used and positions are specified in a
 `vec3f[]` type of `vertex.position` format, then type/basis defaults to
 `OSP_ROUND` and `OSP_LINEAR` (this is the fastest and most memory
-efficient mode). Implementation is with round linear segements where
+efficient mode). Implementation is with round linear segments where
 each segment corresponds to a link between two vertices.
 
 The following section describes the properties of different curve basis'
@@ -1084,7 +1084,7 @@ and material information. To create a geometric model, call
 
 Color and material are fetched with the primitive ID of the hit (clamped
 to the valid range, thus a single color or material is fine), or mapped
-first via the `index` array (if present). All paramters are optional,
+first via the `index` array (if present). All parameters are optional,
 however, some renderers (notably the [path tracer]) require a material
 to be set. Materials are either handles of `OSPMaterial`, or indices
 into the `material` array on the [renderer], which allows to build a
@@ -1211,7 +1211,7 @@ the spotlight supports the special parameters listed in the table.
 
   float[]    intensityDistribution             luminous intensity distribution
                                                for photometric lights; can be 2D
-                                               for assymentric illumination;
+                                               for asymmetric illumination;
                                                values are assumed to be
                                                uniformly distributed
 
@@ -2036,7 +2036,7 @@ The supported texture formats for `texture2d` are:
   OSP_TEXTURE_RGB32F  32\ bit float components red, green, blue
   OSP_TEXTURE_R8      8\ bit [0–255] linear single component red
   OSP_TEXTURE_RA8     8\ bit [0–255] linear two components red, alpha
-  OSP_TEXTURE_L8      8\ bit [0–255] gamma encoded luminance (replicated into red, gree, blue)
+  OSP_TEXTURE_L8      8\ bit [0–255] gamma encoded luminance (replicated into red, green, blue)
   OSP_TEXTURE_LA8     8\ bit [0–255] gamma encoded luminance, and linear alpha
   OSP_TEXTURE_R32F    32\ bit float single component red
   OSP_TEXTURE_RGBA16  16\ bit [0–65535] linear components red, green, blue, alpha

doc/compilation.md

@@ -118,10 +118,10 @@ BUILD_EMBREE_FROM_SOURCE
 : set to OFF will download a pre-built version of Embree.
 
 BUILD_OIDN_FROM_SOURCE
-: set to OFF will download a pre-built version of OpenImageDenoise.
+: set to OFF will download a pre-built version of Open Image Denoise.
 
 BUILD_OIDN_VERSION
-: determines which verison of OpenImageDenoise to pull down.
+: determines which version of Open Image Denoise to pull down.
 
 For the full set of options, run:
 

doc/examples.md

@@ -71,8 +71,8 @@ objects for the specific scene like `cpp::Geometry`, `cpp::Volume`,
 `cpp::Light` etc.
 
 The `detail::Builder` base struct is mostly responsible for setting up
-OSPRay `world` and objects common in all scenes (for eg: lighting and
-ground plane), which can be conveniently overridden in the derived
+OSPRay `world` and objects common in all scenes (for example lighting
+and ground plane), which can be conveniently overridden in the derived
 builders.
 
 Given below are different scenes listed with their string identifiers: