diff --git a/adr/2021_07_05_api_providing_locales_available_in_active_channel.md b/adr/2021_07_05_api_providing_locales_available_in_active_channel.md
index e7a68dfacd..0f78033760 100644
--- a/adr/2021_07_05_api_providing_locales_available_in_active_channel.md
+++ b/adr/2021_07_05_api_providing_locales_available_in_active_channel.md
@@ -1,7 +1,8 @@
-# Using data provider for getting available locales in active channel for shop user
+# Using Doctrine Collection extension for getting available locales in active channel for shop user
 
-* Status: proposed
-* Date: 2021-07-05
+* Status: accepted
+* Propose date: 2021-07-05
+* Update date: 2022-03-15
 
 ## Context and Problem Statement
 Customer should have access only to locales available in their channel
@@ -16,11 +17,11 @@ Customer should have access only to locales available in their channel
 
 ### Using Data Provider
 
-* Good, because we already have this approach for older resources
 * Good, because it is easy to implement 
 * Bad, because using data providers omits extra Doctrine extensions like pagination
 
 ## Decision Outcome
 
-Chosen option: Using Data Provider
-Shops shouldn't have many locales for each channel, so lack of a pagination is smaller problem than creating overcomplicated query in Doctrine Collection extension
+Chosen option: **"Using Doctrine Collection extension"**
+
+This option is consistent with current approach and does not omit Doctrine extensions like pagination.