Merge pull request #1800 from GeoffMaciolek/vertical-clarification

Clarify "vertical" = "department" for US eng. speakers. (Used in imgs…

packages/noco-docs/content/en/setup-and-usages/lookup.md

@@ -10,7 +10,7 @@ menuTitle: "Lookup"
 
 ### Sample simple Organization structure
 
-- 5 verticals, each vertical has a team name & associated team code. Vertical **has many** Employees - relationship has been defined
+- 5 verticals (company departments), each vertical/department has a team name & associated team code. Vertical **has many** Employees - relationship has been defined
 
 <img src="https://user-images.githubusercontent.com/35857179/161894091-6b6092c2-7184-4fe6-aa17-64ce5a7e97d5.png" width="70%"/>
 
@@ -65,4 +65,4 @@ We can apply the same steps to create the lookup column `TeamCode` in table `Pro
 
 Click save. Then `TeamCode` is populated in table `Project`.
 
-<img src="https://user-images.githubusercontent.com/35857179/161898396-c5c96485-3ec2-4452-88a0-6ed7665d6f34.png" width="50%"/>
+<img src="https://user-images.githubusercontent.com/35857179/161898396-c5c96485-3ec2-4452-88a0-6ed7665d6f34.png" width="50%"/>

packages/noco-docs/content/en/setup-and-usages/rollup.md

@@ -10,7 +10,7 @@ menuTitle: "Rollup"
 
 Sample simple Organization structure:
 
-- 5 verticals, each vertical has a team name & associated team code
+- 5 verticals (company departments), each vertical/department has a team name & associated team code
 - 5 employees working at different verticals
 - Vertical **has many** Employees : relationship has been defined