Changed references from HeteroC to Hetero-C++

hpvm/docs/developerdocs/specifications/hetero-c.rst

-Hetero-C Language Specification
+Hetero-C++ Language Specification
 ===============================
 
-A Hetero-C program consists of Parallel Sections, Parallel Tasks, and
+A Hetero-C++ program consists of Parallel Sections, Parallel Tasks, and
 Parallel Loops. Parallel Sections correspond to Internal Nodes in the
 hetero DataFlow Graph (DFG), while Parallel Tasks/Loops may translate to
 either Internal Nodes or Leaf Nodes. Please refer to
@@ -12,8 +12,8 @@ Buffer Pair
 -----------
 
 A buffer pair denotes a Pointer value followed by the size of the memory
-it points to. Various Hetero-C api calls require specifying both of
-these arguments together to insert the hetero C intrinsics correctly.
+it points to. Various Hetero-C++ api calls require specifying both of
+these arguments together to insert the hetero-C++ intrinsics correctly.
 For example ``(…, int* ptr1, size_t ptr1Sz, ...)``
 
 Launch & Wait API
@@ -113,13 +113,13 @@ This marker also takes an optional string literal as a final argument to overrid
 Optional API
 ------------
 
-The following methods are not required for generating correct HeteroC++
+The following methods are not required for generating correct Hetero-C++
 code but can aid the compiler in generating more performant code as well
 as dictating which to offload a particular computation too.
 
 ``void __hetero_hint(int i)``
 
-By default, each node generated by the HeteroC++ compiler gets assigned
+By default, each node generated by the Hetero-C++ compiler gets assigned
 to execute on the CPU. To overide this default behavior, users can call
 this method inside their parallel task or parallel loop where the
 argument specifies the enum value of the target device. The value
@@ -143,7 +143,7 @@ sufficient and we want to continue tracking the memory even after the
 Dataflow code has completed executing. Note that use of this API
 overides the automatically generation of the specific hpvm runtime calls
 and so these calls must be generated for all memory passed into the
-HeteroC++ DFG calls (on the host side only).
+Hetero-C++ DFG calls (on the host side only).
 
 ``void* __hetero_free(void* p)``
 
@@ -157,7 +157,7 @@ this behavior is not sufficient and we want to continue tracking the
 memory even after the Dataflow code has completed executing. Note that
 use of this API overides the automatically generation of the specific
 hpvm runtime calls and so these calls must be generated for all memory
-passed into the HeteroC++ DFG calls (on the host side only).
+passed into the Hetero-C++ DFG calls (on the host side only).
 
 ``void __hetero_request_mem(void*)``
 
@@ -169,7 +169,7 @@ markers generate these automatically for any memory which is specified
 as an output to the graph being launched. Note that use of this API
 overides the automatically generation of the specific hpvm runtime calls
 and so these calls must be generated for all (output) memory passed into
-the HeteroC++ DFG calls (on the host side only).
+the Hetero-C++ DFG calls (on the host side only).