Avo::App -> Avo::Current

docs/3.0/customization.md

@@ -150,7 +150,7 @@ end
 It's recommended you don't store your current user here but using the [`current_user_method`](./authentication.html#customize-the-current-user-method) config.
 :::
 
-You can access the context data with `::Avo::App.context` object.
+You can access the context data with `::Avo::Current.context` object.
 
 ## Eject
 [This section has moved.](./eject-views)

docs/3.0/native-field-components.md

@@ -41,7 +41,7 @@ When you generate a new [resource tool](./resource-tools) you get access to the
             # @resource.model
             # form (on create & edit pages. please check for presence first)
             # params
-            # Avo::App.context
+            # Avo::Current.context
             # current_user
           %>
         </div>

docs/3.0/resource-tools.md

@@ -52,7 +52,7 @@ The partial is ready for you to customize further.
             # @resource.model
             # form (on create & edit pages. please check for presence first)
             # params
-            # Avo::App.context
+            # Avo::Current.context
             # current_user
           %>
         </div>
@@ -68,7 +68,7 @@ The partial is ready for you to customize further.
 
 You might need access to a few things in the partial.
 
-You have access to the `tool`, which is an instance of your tool `PostInfo`, and the `@resource`, which holds all the information about that particular resource (`view`, `model`, `params`, and others), the `params` of the request, the `Avo::App.context` and the `current_user`.
+You have access to the `tool`, which is an instance of your tool `PostInfo`, and the `@resource`, which holds all the information about that particular resource (`view`, `model`, `params`, and others), the `params` of the request, the `Avo::Current.context` and the `current_user`.
 That should give you all the necessary data to scope out the partial content.
 
 ## Tool visibility