Move away from 'ipblock' terminology to more general 'hardware block' (#201)

Signed-off-by: colramos-amd <colramos@amd.com>

src/docs-2.x/getting_started.md

@@ -14,7 +14,7 @@
 
     To collect the default set of data for all kernels in the target application, launch, e.g.:
     ```shell
-    $ omniperf profile -n vcopy_data -- ./vcopy 1048576 256
+    $ omniperf profile -n vcopy_data -- ./vcopy -n 1048576 -b 256
     ```
     The app runs, each kernel is launched, and profiling results are generated. By default, results are written to e.g., ./workloads/vcopy_data (configurable via the `-n` argument). To collect all requested profile information, it may be required to replay kernels multiple times.
 
@@ -27,7 +27,7 @@
 
     - `-k`/`--kernel` enables filtering kernels by name. 
     - `-d`/`--dispatch` enables filtering based on dispatch ID.
-    - `-b`/`--ipblocks` enables collects metrics for only the specified (one or more) hardware component blocks.
+    - `-b`/`--block` enables collects metrics for only the specified (one or more) hardware component blocks.
 
     To view available metrics by IP Block you can use the `--list-metrics` argument:
     ```shell