mock-array: rename mock-array

Signed-off-by: Øyvind Harboe <[email protected]>

Author: oharboe

flow/designs/asap7/mock-array/README.md

@@ -39,10 +39,10 @@ Element/constraint.sdc
 
 A relatively simple constraint.sdc is adequate for the Element as
 timing is exported when the Element macro is made and checked at the
-mock-array-big level.
+mock-array level.
 
 Note that a failure on timing at the Element level is
-not a problem, as long as timing is met at the mock-array-big level.
+not a problem, as long as timing is met at the mock-array level.
 
 The purpose of the constraint.sdc file at the Element level is to
 be able to iterate on the Element during development and work on,
@@ -56,7 +56,7 @@ Optimizing Element/constraint.sdc
 Before considering the various strategies to articulate an Element/constraint.sdc
 file below, note that no tests have been run to verify that these
 different constraint.sdc changes below have any effects on the quality
-of results at the mock-array-big level. If there are no substantial
+of results at the mock-array level. If there are no substantial
 differences in quality of results and timing is met, then the differences
 between the strategies below are inconsequential.