goravel · hwbrzzl · Sep 14, 2023 · Sep 13, 2023
diff --git a/security/authorization.md b/security/authorization.md
@@ -6,7 +6,7 @@
 
 In addition to providing built-in [authentication](./authentication.md) services, Goravel also provides a simple way to authorize user actions against a given resource. For example, even though a user is authenticated, they may not be authorized to update or delete certain Eloquent models or database records managed by your application. Goravel's authorization features provide an easy, organized way of managing these types of authorization checks.
 
-Laravel provides two primary ways of authorizing actions: [gates](#Gates) and [policies](#Policies). Think of gates and policies like routes and controllers. Gates provide a simple, closure-based approach to authorization while policies, like controllers, group logic around a particular model or resource. In this documentation, we'll explore gates first and then examine policies.
+Goravel provides two primary ways of authorizing actions: [gates](#Gates) and [policies](#Policies). Think of gates and policies like routes and controllers. Gates provide a simple, closure-based approach to authorization while policies, like controllers, group logic around a particular model or resource. In this documentation, we'll explore gates first and then examine policies.
 
 You do not need to choose between exclusively using gates or exclusively using policies when building an application. Most applications will most likely contain some mixture of gates and policies, and that is perfectly fine!
 
@@ -195,4 +195,4 @@ facades.Gate().Define("update-post", policies.NewPostPolicy().Update)
 
 You may continue to define additional methods on the policy as needed for the various actions it authorizes. For example, you might define `View` or `Delete` methods to authorize various `models.Post` related actions, but remember you are free to give your policy methods any name you like.
 
-<CommentService/>
+<CommentService/>