Apply suggestions from code review

Apply PR review suggestions

Co-authored-by: Ewan Crawford <[email protected]>
Co-authored-by: Ben Tracy <[email protected]>

sycl/doc/extensions/experimental/sycl_ext_oneapi_graph.asciidoc

@@ -822,14 +822,14 @@ exception will be thrown if a user tries to update an executable graph. This
 guarantee allows the backend to provide a more optimized implementation, if
 possible.
 
-===== Supported Features:
+===== Supported Features
 
-The only type of nodes that are currently able to be updated in a graphs are
+The only types of nodes that are currently able to be updated in a graph are
 kernel execution nodes.
 
-There is two different API's that can be used to update a graph:
+There are two different API's that can be used to update a graph:
 
-* <individual-node-update, Individual Node Update>> which allows updating
+* <<individual-node-update, Individual Node Update>> which allows updating
 individual nodes of a command-graph.
 * <<whole-graph-update, Whole Graph Update>> which allows updating the
 entirety of the graph simultaneously by using another graph as a
@@ -897,7 +897,7 @@ Command-group updates are performed by creating an instance of the
 `dynamic_command_group` class. A dynamic command-group is created with a modifiable
 state graph and a list of possible command-group functions. Command-group functions
 within a dynamic command-group can then be set to active by using the member function
-`dynamic_command_group::setActiveCgf()`.
+`dynamic_command_group::set_active_cgf()`.
 
 Dynamic command-groups are compatible with dynamic parameters. This means that
 dynamic parameters can be used in command-group functions that are part of