From 522a88acbccff592676ffb0890bfdf0ad68b9900 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1rk=20Lukovics?= Date: Tue, 18 Oct 2022 18:21:56 +0200 Subject: [PATCH] Fixing typos --- Readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index 50f5b4ea..d35b5ea0 100644 --- a/Readme.md +++ b/Readme.md @@ -55,7 +55,7 @@ Adds a dump of metadata to the output about every shape. This will help you unde #### Strict Security -When applied to a content type definition, `StrictSecuritySetting` requires the user to have the exact Securable permission for that content type. For example if you apply it to Page, then just having the common ViewContent permission won't be enough and you must explicitly have the View_Page permission too. Don't worry, the normal implications such as ViewOwn beig fulfilled by View still apply within the content type, they just no longer imply their common counterparts. +When applied to a content type definition, `StrictSecuritySetting` requires the user to have the exact Securable permission for that content type. For example if you apply it to Page, then just having the common ViewContent permission won't be enough and you must explicitly have the View_Page permission too. Don't worry, the normal implications such as ViewOwn being fulfilled by View still apply within the content type, they just no longer imply their common counterparts. Make content type use strict security in migration: