Fix broken link and typos in docs and diagrams [#681 - #682]

Signed-off-by: Farhan Tariq <[email protected]>

Author: f4ni

documentation/general/dash-high-level-design.md

@@ -523,7 +523,7 @@ per scenario and document them in a repeatable format. The behavioral model is
 compiled as software to behave exactly as hardware.  From there we will be able
 to auto-generate the APIs. The *implementation* itself does not have to be P4.
 
-For more information see the [pipeline README](../../../dash-pipeline/README.md) file.
+For more information see the [pipeline README](../../dash-pipeline/README.md) file.
 
 ## SONiC Integration testing
 

documentation/general/images/sdn/eni-match-flow-direction.svg

@@ -210,7 +210,7 @@ ACL groups need to be evaluated in order. The following rules apply:
   - Priority is only within rules in the same group. No priorities across groups
     are allowed. 
   - A smaller priority number means the rule will be evaluated first.
-  - Priorities are unique withing an ACL group. Priorities might overlap across
+  - Priorities are unique within an ACL group. Priorities might overlap across
     ACL groups. 
 
 #### ACL levels