Merge pull request #310 from Permify/docs

docs: update getting started sections
Permify · Mar 8, 2023 · e9a1f13 · e9a1f13
2 parents 9741fb8 + 8202b4c
commit e9a1f13
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/documentation/docs/getting-started/modeling.md b/docs/documentation/docs/getting-started/modeling.md
@@ -189,7 +189,6 @@ entity repository {
 
 → For more fine grained permission let's examine the `read` action rules; user that is `organization admin` and following users can read the repository: `owner` of the repository, or `maintainer`, or `member` of the organization which repository belongs to.
 
-
 :::info
 You can add actions to another action like relations, see below.
 
@@ -199,7 +198,6 @@ You can add actions to another action like relations, see below.
 ``` 
 
 delete action can inherit the edit action rules like above. To sum up, only organization administrators and any relation that can perform edit action (member or manager) can perform delete action.
-
 :::
 
 ### Full Schema

diff --git a/docs/documentation/docs/getting-started/sync-data.md b/docs/documentation/docs/getting-started/sync-data.md
@@ -229,6 +229,8 @@ In Write Relationships API response you'll get a snap token of the operation. Th
 
 :::info
 Note: `relation: “...”` used when subject type is different from **user** entity. **#…** represents a relation that does not affect the semantics of the tuple.
+
+Simply, the usage of ... is straightforward: if you're use user entity as an subject, you should not be using the `...` If you're using another subject rather than user entity then you need to use the `...` 
 :::
 
 <!-- ## Write Database