Capitalization.

Author: janpgit

modules/dynamic-allocation.md

@@ -46,7 +46,7 @@ See `man malloc` for more memory allocation related functions.
 The C runtime does not have a garbage collector so all heap allocated memory
 has to be explicitly freed via `free`() after it is no longer needed.
 
-:wrench: write a program that takes at least 2 arguments.  First argument
+:wrench: Write a program that takes at least 2 arguments.  First argument
 specifies a dimension of an array of `int`s, the rest are the `int`s to fill
 out the array.  To allocate memory for the array, use `malloc`.  When filling
 out the array, ignore extra arguments.  If you have less arguments, use zero
@@ -55,7 +55,7 @@ a string to an integer, use `atoi` and assume numbers are correctly entered.
 
 ```
 ./a.out 10 1 2 3 7 8 999 7 7 7 9 9 9 10 11
-1 2 3 7 8 999 7 7 7 9 
+1 2 3 7 8 999 7 7 7 9
 ```
 
 #solution allocate-and-fill-out-array.c

modules/heap-memory-woes.md

@@ -2,16 +2,19 @@
 
 ## Correctness
 
-- use after free: read/write memory that is part of memory chunk that was free'd
-  - *dangling pointer* is often the cause of this; e.g. a structure contains pointer
-    to heap allocated memory which is freed at some point of time and the
-    pointer is still used to access the memory afterwards. In the meantime some other part
-    of the program could have allocated piece(s) of the free'd memory.
-  - the way to detect/prevent this is to set the pointer to `NULL` after freeing it
-- double free: free already free'd buffer
-  - can corrupt internal heap allocator structures if it does not
-    track the state of memory chunks
-  - use static/dynamic analysis and/or heap allocator with the ability to detect this
+- Use after free: read/write memory that is part of memory chunk that was free'd
+  - *Dangling pointer* is often the cause of this; e.g. a structure contains a
+    pointer to heap allocated memory which is freed at some point of time and
+    the pointer is still used to access the memory afterwards, and expected data
+    could be found in there, or not - in the meantime some other part of the
+    program could have allocated piece(s) of the free'd memory.
+  - The way to detect/prevent this is to set the pointer to `NULL` after freeing
+    it.
+- Double free: free already free'd buffer
+  - Can corrupt internal heap allocator structures if it does not track the
+    state of memory chunks
+  - Use static/dynamic analysis and/or heap allocator with the ability to detect
+    this
 
 #source use-after-free.c