Improve documentation and example formatting consistency (#4299)

* Improve doc and example consistency

Improve consistency of formatting in example shaders and remove
trailing spaces in documentation files. Fix minor typos.

1 files changed, 2 insertions, 3 deletions

diff --git a/examples/model-viewer/shaders.slang b/examples/model-viewer/shaders.slang
index 81ec89d03..d99a4b1da 100644
--- a/examples/model-viewer/shaders.slang
+++ b/examples/model-viewer/shaders.slang
@@ -90,7 +90,7 @@ struct BlinnPhong : IBRDF
         // for our example cube, and the result is a non-finite value
         // coming out of `evaluate()` if we include the specular term.
 
-//        return kd*nDotL + ks*pow(nDotH, specularity);
+        // return kd*nDotL + ks*pow(nDotH, specularity);
         return kd*nDotL;
     }
 };
@@ -142,7 +142,6 @@ interface IMaterial
 // assumption in the shader code that `gMaterial` will be plugged
 // in using an instance of `SimpleMaterial`
 //
-//
 struct SimpleMaterial : IMaterial
 {
     // We declare the properties we need as fields of the material type.
@@ -200,7 +199,7 @@ interface ILightEnv
     float3 illuminate<B:IBRDF>(SurfaceGeometry g, B brdf, float3 wo);
     //
     // Note that the `illuminate()` method is allowed as an interface
-    // requirement in Slang even though it is a generic. Constract that
+    // requirement in Slang even though it is a generic. Contrast that
     // with C++ where a `template` method cannot be `virtual`.
 };