Update authorizations article

docs/en/modules/admin/pages/participants/authorizations.adoc

@@ -1,32 +1,36 @@
 = Authorizations
 
-This section allows you to manage participants' authorizations. It depends on which Authorizations you have configured and
-enabled by your developers. To understand more what are authorizations and how to configure them, please refer to the
-xref:customize:authorizations.adoc[Authorizations section in the Customize Guide].
+Authorizations allow to give specific participation rights to participants who have completed a verification process. 
+This verification process can be direct, have multiple steps, be online or presential. 
+
+For instance you can configure that only participants who have verified themselves by their identity documents can vote on
+proposals in a specific participatory process.
 
-With authorizations an administrator can define different permissions so participants can make some actions in a component.
-For instance you can configure that only participants who have verified herselves by their identity documents can vote on
-proposals in a participatory process.
+NOTE: Several authorizations are available by default in the software, but you can also create your own authorizations. 
 
-A participant can see which authorizations do they have available in their account settings.
+== Enable / Disable authorizations
+
+To enable an authorization, you need to have access to the xref:configure:system.adoc[System panel] or ask your administrator. 
+To understand more what are authorizations and how to configure them, please refer to the
+xref:customize:authorizations.adoc[Authorizations section in the Customize Guide].
 
-image:authorizations_account.png[Authorizations in participants account]
+Participants can access, update or delete their authorizations in their xref:admin:features/my_account/authorizations.adoc[account]. 
 
 == Authorizations revocation
 
 A default Decidim installation will not have verified participants.
 
 image:authorizations_admin_default.png[Authorizations in a default installation]
 
-In the moment that there are some participants verified, an administrator can revoke all the authorizations, as the attributes
-that give permissions to those participants could be changed in time and the platform didn't receive these changes in the
-participants statuses. For instance, an identity document of a participant could be expired, or if a participant have been
-authorized by the "code by postal letter", that participant could move in the meantime.
+From the moment some participants get verified with an authorization, administrators can revoke all the authorizations at once. 
+Indeed, after some time, some of the verifications can be deprecated.  
+For instance, identity documents expire after some time, or participants can move from a city. 
+Then, an administrator can want to force participants to renew their verification information. 
 
-image:authorizations_admin_revocation.png[Authorizations revocation]
+image:participants/authorizations_admin_revocation.png[Authorizations revocation]
 
-It's possible to revoke all the authorizations with "Revoke all", or to only revoke authorizations before a given date.
-Another possiblity is to revoke only the xref:admin:participants/impersonations.adoc[impersonated participants].
+It's possible to revoke all the authorizations with "Revoke all", or to only revoke authorizations created before a given date.
+Another possiblity is to revoke only the verifications for xref:admin:participants/impersonations.adoc[impersonated participants].
 
 == Verification methods