Skip to content

Commit 87f38d6

Browse files
authored
Merge pull request #2676 from mooreds/mooreds/update-busted-faq-link
docs(general): corrected links to FAQs
2 parents 06116c4 + fdf10fb commit 87f38d6

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

docs/api-reference/schema/write-schema.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ Permify Schema needed to be send to API endpoint **/v1/tenants/{tenant_id}/schem
2222

2323
![permify-schema](https://user-images.githubusercontent.com/34595361/197405641-d8197728-2080-4bc3-95cb-123e274c58ce.png)
2424

25-
See the following FAQ page to refer to the suggested workflow for: [Managing Schema Changes](../../introduction/faqs#how-to-manage-schema-changes).
25+
See the following FAQ page to refer to the suggested workflow for: [Managing Schema Changes](../../permify-overview/faqs#how-to-manage-schema-changes).

docs/getting-started/testing.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ For managing permission/relation changes, we suggest storing schema in an abstra
297297

298298
We recommend adding our [schema validator](https://github.com/Permify/permify-validate-action) to the pipeline to ensure that any changes are automatically validated.
299299

300-
You can find more details about our suggested workflow to handle schema changes in following [FAQS page](../introduction/faqs#how-to-manage-schema-changes).
300+
You can find more details about our suggested workflow to handle schema changes in following [FAQS page](../permify-overview/faqs#how-to-manage-schema-changes).
301301

302302
## Need any help ?
303303

docs/permify-overview/faqs.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Since edit action consist **or** between owner and parent.admin, if Permify Engi
6565

6666
Rather than **or**, if we had an **and** relation then Permify Engine waits the results of these queries to returning a decision.
6767

68-
### How To Manage Schema Changes ?
68+
### How To Manage Schema Changes?
6969

7070
It's expected that your initial schema will eventually change as your product or system evolves
7171

@@ -126,4 +126,4 @@ Permify was designed and structured as a true ReBAC solution, so besides roles a
126126

127127
With Permify, you can define that a user has certain permissions because of their relation to other entities. An example of this would be granting a manager the same permissions as their subordinates, or giving a user access to a resource because they belong to a certain group.
128128

129-
This is facilitated by our relationship-based access control, which allows the definition of complex permission structures based on the relationships between users, roles, and resources.
129+
This is facilitated by our relationship-based access control, which allows the definition of complex permission structures based on the relationships between users, roles, and resources.

0 commit comments

Comments
 (0)