diff --git a/docs/2.0/associations.md b/docs/2.0/associations.md
index 9dc9d051..5a9d4e3d 100644
--- a/docs/2.0/associations.md
+++ b/docs/2.0/associations.md
@@ -50,7 +50,7 @@ You may want to use the `PersonResource` to list all the records, but when your
 There are two ways you can use this:
 
 1. `self.link_to_child_resource = true` Declare this option on the parent resource. When a user is on the <Index /> view of your the `PersonResource` and clicks on the view button of a `Person` they will be redirected to a `Child` or `Spouse` resource instead of a `Person` resource.
-2. `field :peoples, as: :has_many, link_to_child_resource: false` Use it on a `has_many` field. On the `PersonResource` you may want to show all the related people on the <Show /> page, but when someone click on a record, they are redirected to the inherited `Child` or `Spouse` resource.
+2. `field :peoples, as: :has_many, link_to_child_resource: true` Use it on a `has_many` field. On the `PersonResource` you may want to show all the related people on the <Show /> page, but when someone click on a record, they are redirected to the inherited `Child` or `Spouse` resource.
 
 ## Add custom labels to the associations' pages
 
diff --git a/docs/3.0/upgrade.md b/docs/3.0/upgrade.md
index e9b0ef39..2c5dcbe9 100644
--- a/docs/3.0/upgrade.md
+++ b/docs/3.0/upgrade.md
@@ -6,6 +6,12 @@ If you're looking for the Avo 2 to Avo 3 upgrade guide, please visit [the dedica
 
 ## Upgrade from 3.0.1.beta24 to 3.0.1.beta25
 
+:::option Dashboards visibility and authorization
+Previously, if the `visible` attribute was set to `false` on dashboards, visiting them was impossible because the controller would trigger a "Not found" error. In cases where `authorize` returned `false`, the controller would block access but still keep the dashboard visible.
+
+This behavior has been enhanced. Now, even if `visible` is set to `false`, the dashboard remains accessible but won't appear in the menu. Additionally, if `authorize` returns `false`, the dashboards are now hidden.
+:::
+
 :::option Actions
 We've internally implemented some changes around actions to resolve certain bugs. No action is needed from your end, but if you happen to notice any anomalies in the actions flow, please get in touch with us so we can address them promptly. Thank you.
 :::