diff --git a/docs/en/modules/admin/pages/components/budgets.adoc b/docs/en/modules/admin/pages/components/budgets.adoc index 9121bbf68f..906b1d89db 100644 --- a/docs/en/modules/admin/pages/components/budgets.adoc +++ b/docs/en/modules/admin/pages/components/budgets.adoc @@ -344,7 +344,7 @@ After the voting step has finished, then an administrator need to: . Change the Voting configuration for the Budget component to "Voting finished" . Go to the Budgets and view the results -. On the projects that according to the normative have been selected, she'll need to go to each project, edit it and +. On the projects that according to the normative have been selected, they will need to go to each project, edit it and then check the "Selected for implementation". image:components/budgets/results_unselected.png[Unselected projects after voting] diff --git a/docs/en/modules/admin/pages/components/meetings.adoc b/docs/en/modules/admin/pages/components/meetings.adoc index 478753092b..68b7ec471f 100644 --- a/docs/en/modules/admin/pages/components/meetings.adoc +++ b/docs/en/modules/admin/pages/components/meetings.adoc @@ -130,7 +130,7 @@ if you have two components, "Proposals" with weight "10" and "Meetiings" with we Meetings can be created by participants if the setting is "Participants can create meetings" is checked. -If a participant belongs to a xref:admin:participants/groups.adoc[user group], then she'll be able to create meetings as that group also. +If a participant belongs to a xref:admin:participants/groups.adoc[user group], then they will be able to create meetings as that group also. image:components/meetings/new_meeting_form_frontend01.png[Create a new meeting form (frontend)] image:components/meetings/new_meeting_form_frontend02.png[Create a new meeting form (frontend)] @@ -201,7 +201,7 @@ image:components/meetings/new_meeting_form_frontend02.png[Create a new meeting f |Create meeting as |Required if the participant belongs to a group -|With which identity she wants to create this meeting: as her user or as a group that she's reprensenting? +|With which identity they want to create this meeting: as their user or as a group that they are reprensenting? |=== diff --git a/docs/en/modules/admin/pages/components/meetings/registrations.adoc b/docs/en/modules/admin/pages/components/meetings/registrations.adoc index 98068256cf..8c09e527ea 100644 --- a/docs/en/modules/admin/pages/components/meetings/registrations.adoc +++ b/docs/en/modules/admin/pages/components/meetings/registrations.adoc @@ -81,7 +81,7 @@ The exported data will have these fields: * code: the xref:_registration_code[registration code] (if this feature is enabled) * user/name: the name of the user * user/email: the email of the user -* user/user_group: the group of the user if she has selected that's representing a group when registering +* user/user_group: the group of the user if they have selected that's representing a group when registering == Invitations @@ -92,7 +92,7 @@ image:components/meetings/registrations/invite_attendee.png[Invite attendee for == Registration code -This feature allows you to check if the attendee is registered in the meeting. She needs to provide her code, that gets +This feature allows you to check if the attendee is registered in the meeting. They need to provide their code, that gets entered in this form and it's checked against the database. image:components/meetings/registrations/backend_w_registration_code.png[Registration code form in a meeting] diff --git a/docs/en/modules/admin/pages/components/proposals.adoc b/docs/en/modules/admin/pages/components/proposals.adoc index bc42a9ebf9..3000b0ba8a 100644 --- a/docs/en/modules/admin/pages/components/proposals.adoc +++ b/docs/en/modules/admin/pages/components/proposals.adoc @@ -67,8 +67,8 @@ For instance, if you have two components, "Proposals" with weight "10" and "Meet |Minimum supports per user |Optional -|Must be a number. How many supports does a participant needs to give to proposals so their supports are counted. If she doesn't -reach this number, her supports will not be taken in account. +|Must be a number. How many supports does a participant needs to give to proposals so their supports are counted. If they don't +reach this number, their supports will not be taken in account. |Proposal limit per participant |Optional @@ -321,7 +321,7 @@ image:components/proposals/new_proposal_frontend.png[New proposal form] Proposals can be created by participants if the setting is "Proposal creation enabled" is checked for the active phase. -If a participant belongs to a xref:admin:participants/groups.adoc[user group], then she'll be able to create proposals as that group also. +If a participant belongs to a xref:admin:participants/groups.adoc[user group], then they will be able to create proposals as that group also. This form depends a lot in which settings you've enabled in this component. It can be really short (with only a Title and Body by default) or very long (Title, Body, Hashtags, Address, Scope, Category, Image and Attachment). diff --git a/docs/en/modules/admin/pages/components/proposals/amendments.adoc b/docs/en/modules/admin/pages/components/proposals/amendments.adoc index ca215d0a98..27904d8f20 100644 --- a/docs/en/modules/admin/pages/components/proposals/amendments.adoc +++ b/docs/en/modules/admin/pages/components/proposals/amendments.adoc @@ -42,7 +42,7 @@ image:components/proposals/amendments/amendment_list.png[] image:components/proposals/amendments/amendment_view_side_by_side.png[] . It's also possible to filter the amended proposals image:components/proposals/amendments/amendment_list_filter.png[] -. Alice receives a notification that Bob has proposed an amendment to her original proposal +. Alice receives a notification that Bob has proposed an amendment to their original proposal image:components/proposals/amendments/proposal_amendmed_notification.png[] . Alice can see the amendment proposal image:components/proposals/amendments/proposal_amendmed_to_review.png[] diff --git a/docs/en/modules/admin/pages/components/proposals/collaborative_drafts.adoc b/docs/en/modules/admin/pages/components/proposals/collaborative_drafts.adoc index 3a752fbd75..9026a00138 100644 --- a/docs/en/modules/admin/pages/components/proposals/collaborative_drafts.adoc +++ b/docs/en/modules/admin/pages/components/proposals/collaborative_drafts.adoc @@ -6,7 +6,7 @@ It's useful to propose improvements or corrections. It has similarities with xref:components/proposals/amendments.adoc[Amendments] but the main difference is that with collaborative drafts there is a need to trust other authors, as they can make any change to the original proposal without approval by the -original author, although the original author can decide if she promotes the collaborative draft as a proposal. +original author, although the original author can decide if they promote the collaborative draft as a proposal. image:components/proposals/collaborative_drafts/collaborative_draft_request_access.png[Collaborative draft with request access button] @@ -24,7 +24,7 @@ For instance, it could be "Processes", "Assemblies", or "Conferences" == How it works -. A participant (Alice) wants to create a collaborative draft. For that, she goes to the proposals list page. +. A participant (Alice) wants to create a collaborative draft. For that, they go to the proposals list page. . Alice clicks in the "Access collaborative drafts" button image:components/proposals/collaborative_drafts/proposals_list01.png[] . Alice clicks in "New collaborative draft" button @@ -40,7 +40,7 @@ image:components/proposals/collaborative_drafts/collaborative_draft_request_acce image:components/proposals/collaborative_drafts/access_requested.png[] . Alice receives the notification image:components/proposals/collaborative_drafts/notification.png[] -. Alice goes to the collaborative draft. There she can accept or reject the collaboration request +. Alice goes to the collaborative draft. There they can accept or reject the collaboration request image:components/proposals/collaborative_drafts/author_sidebar.png[] . Alice approves the collaboration request. Once a request is approved it can't be rejected . Now the collaborative draft has multiple authors @@ -53,7 +53,7 @@ image:components/proposals/collaborative_drafts/collaborative_draft_edited.png[] image:components/proposals/collaborative_drafts/collaborative_draft_edited_versions.png[] image:components/proposals/collaborative_drafts/collaborative_draft_edited_versions_show_v2_01.png[] image:components/proposals/collaborative_drafts/collaborative_draft_edited_versions_show_v2_02.png[] -. Once Alice is satisfied with the collaborative draft, she can publish it by click in the "Publish" button +. Once Alice is satisfied with the collaborative draft, they can publish it by click in the "Publish" button image:components/proposals/collaborative_drafts/publish_modal.png[] . When it's published it becomes a proposal image:components/proposals/collaborative_drafts/proposal.png[] diff --git a/docs/en/modules/admin/pages/features/badges.adoc b/docs/en/modules/admin/pages/features/badges.adoc index 9d4b6ac620..453776727f 100644 --- a/docs/en/modules/admin/pages/features/badges.adoc +++ b/docs/en/modules/admin/pages/features/badges.adoc @@ -5,16 +5,16 @@ and interacting in the platform, they will earn different badges. Here is the li It's a https://en.wikipedia.org/wiki/Gamification[gamification] mechanism to improve the engagement of the participants in a ludic way. -The badges a participant has are visible in her account. There's also a general explanation page with a short description of every badge. +The badges a participant has are visible in their account. There's also a general explanation page with a short description of every badge. image:features/badges/example01.png[Example of badges in profile] -When a participant earns a badge she receives a notification. +When a participant earns a badge they receive a notification. image:features/badges/notification.png[Example of badges notification] -Badges have multiple levels, depending in the number of times she has made the action. For instance, for Proposals badge -she'll receive the first level badge when arriving at 1 follower, the second level at 15 followers, the third level at 30 followers, +Badges have multiple levels, depending in the number of times they have made the action. For instance, for Proposals badge +they will receive the first level badge when arriving at 1 follower, the second level at 15 followers, the third level at 30 followers, the fourth level at 60 and the fifth level at 100. .Badges @@ -24,14 +24,14 @@ the fourth level at 60 and the fifth level at 100. |image:features/badges/accepted_proposals_badge.png[Accepted proposals badge] |Accepted proposals |Granted when particiapnts actively participate with new proposals and these are accepted. -|The participant needs to choose the participation space of her interest with submission for proposals enabled and try to +|The participant needs to choose the participation space of their interest with submission for proposals enabled and try to make proposals that can be carried out. This way they are more likely to be accepted. |1, 5, 15, 30, 50 |image:features/badges/attended_meetings_badge.png[Attended meetings badge] |Attended meetings |Granted when participants attend several face-to-face meetings. -|The participant needs to register for the meetings she want to attend +|The participant needs to register for the meetings they want to attend |1, 3, 5, 10, 30 |image:features/badges/debates_badge.png[Debates badge] @@ -44,7 +44,7 @@ make proposals that can be carried out. This way they are more likely to be acce |Followers |Granted when participant reach a certain number of followers. The platform is a social and political network, so participants ned to weave their web to communicate with other people in the platform. -|The participant needs to be be active and follow other people. That will surely make other people follow her. +|The participant needs to be be active and follow other people. That will surely make other people follow them. |1, 15, 30, 60, 100 |image:features/badges/published_initiatives_badge.png[Published initiatives badge] @@ -56,21 +56,21 @@ participants ned to weave their web to communicate with other people in the plat |image:features/badges/invitations_badge.png[invitations badge] |Invitations |Granted when participants invite some people and they have become participants. -|The participant needs to use the “invite friends” link on her user page to invite her friends. She can customize the -message she's sending. She’ll level up by sending invitations and getting them registered. Note that this feature is disabled +|The participant needs to use the “invite friends” link on their user page to invite their friends. They can customize the +message they are sending. They will level up by sending invitations and getting them registered. Note that this feature is disabled and this badge is not available, so it'll be removed in the future. |1, 5, 10, 30, 50 |image:features/badges/proposal_supports_badge.png[Proposal supports badge] |Proposal supports |Granted when participants support other people's proposals. -|The participant needs to browse and spend some time reading other people's proposals and give support to the proposals she like or find interesting. +|The participant needs to browse and spend some time reading other people's proposals and give support to the proposals they like or find interesting. |5, 15, 50, 100, 500 |image:features/badges/proposals_badge.png[Proposals badge] |Proposals |Granted when participants actively participate with new proposals. -|The participant needs to choose the participation space of her interest with submission for proposals enabled and create a new proposal. +|The participant needs to choose the participation space of their interest with submission for proposals enabled and create a new proposal. |1, 5, 10, 30, 60 |=== diff --git a/docs/en/modules/admin/pages/features/endorsements.adoc b/docs/en/modules/admin/pages/features/endorsements.adoc index 4522cd073d..e6abad9003 100644 --- a/docs/en/modules/admin/pages/features/endorsements.adoc +++ b/docs/en/modules/admin/pages/features/endorsements.adoc @@ -8,7 +8,7 @@ This is done through the button in the sidebar. Administrators can enable or dis image:features/endorsements/sidebar.png[Endorsement button in sidebar] -When a participant belongs to a verified group she can also endorse like that group by selecting the identity. +When a participant belongs to a verified group they can also endorse like that group by selecting the identity. image:features/endorsements/modal.png[Select identity modal] diff --git a/docs/en/modules/admin/pages/features/my_account.adoc b/docs/en/modules/admin/pages/features/my_account.adoc index 0d30d38de3..15a381fbef 100644 --- a/docs/en/modules/admin/pages/features/my_account.adoc +++ b/docs/en/modules/admin/pages/features/my_account.adoc @@ -1,6 +1,6 @@ = My account -My account is all the pages where a participant can change her personal data that is displayed in her xref:admin:features/my_public_profile.adoc[My public profile] page, change her notifications settings, see which groups she belongs, etc. +My account is all the pages where a participant can change their personal data that is displayed in their xref:admin:features/my_public_profile.adoc[My public profile] page, change their notifications settings, see which groups they belong to, etc. To go to this section: @@ -8,7 +8,7 @@ To go to this section: . Click in the name of the participant in the header . Click in "My account" -The actions that she can do are: +The actions that they can do are: * xref:admin:features/my_account/account.adoc[Account] * xref:admin:features/my_account/notifications_settings.adoc[Notifications settings] diff --git a/docs/en/modules/admin/pages/features/my_account/account.adoc b/docs/en/modules/admin/pages/features/my_account/account.adoc index 095e4e3c4a..18b23060ce 100644 --- a/docs/en/modules/admin/pages/features/my_account/account.adoc +++ b/docs/en/modules/admin/pages/features/my_account/account.adoc @@ -27,7 +27,7 @@ The service crops the image. Maximum file size: 5MB |Your email |Required -|The email of the participant, where she'll receive notifications, password recovery, etc. If it's changed it needs to be +|The email of the participant, where they will receive notifications, password recovery, etc. If it's changed it needs to be confirmed. |Personal URL diff --git a/docs/en/modules/admin/pages/features/my_account/delete_my_account.adoc b/docs/en/modules/admin/pages/features/my_account/delete_my_account.adoc index fe2a6c0d94..3fc0c019fc 100644 --- a/docs/en/modules/admin/pages/features/my_account/delete_my_account.adoc +++ b/docs/en/modules/admin/pages/features/my_account/delete_my_account.adoc @@ -10,7 +10,7 @@ To delete the account: . Click in the name of the participant in the header . Click in "My account" . Click in "Delete my account" in the sidebar -. Optionally, she can provide a reason for the deletion +. Optionally, they can provide a reason for the deletion . Click in "Delete my account" . Click in "Yes, I want to delete my account" diff --git a/docs/en/modules/admin/pages/global_moderations.adoc b/docs/en/modules/admin/pages/global_moderations.adoc index 86b776bca2..7abe85cf51 100644 --- a/docs/en/modules/admin/pages/global_moderations.adoc +++ b/docs/en/modules/admin/pages/global_moderations.adoc @@ -36,8 +36,8 @@ process and the framework for discussion, and > * to create multiple users by pretending to be different people (astroturfing). Anyone can propose a moderation in Decidim, through the "Flag" icon in the participant -profile. After a participant has clicked in this action then she needs to provide a -reason why she's making this report: +profile. After a participant has clicked in this action then they need to provide a +reason why they are making this report: * Contains clickbait, advertising, scams or script bots. * Contains racism, sexism, slurs, personal attacks, death threats, suicide requests or any form of hate speech. diff --git a/docs/en/modules/admin/pages/help_sections.adoc b/docs/en/modules/admin/pages/help_sections.adoc index 7e942f55d7..9be6d5e3d7 100644 --- a/docs/en/modules/admin/pages/help_sections.adoc +++ b/docs/en/modules/admin/pages/help_sections.adoc @@ -1,6 +1,6 @@ = Help sections -The first time a visitor goes to any Space page she'll see an information box about what's this Space about. +The first time a visitor goes to any Space page they will see an information box about what's this Space about. This is how the information box is shown to participants and visitors: diff --git a/docs/en/modules/admin/pages/newsletters.adoc b/docs/en/modules/admin/pages/newsletters.adoc index f7e8c66b33..46fb7fec80 100644 --- a/docs/en/modules/admin/pages/newsletters.adoc +++ b/docs/en/modules/admin/pages/newsletters.adoc @@ -140,8 +140,8 @@ the selected participatory spaces in the list * Sending the newsletter to all the participants that have selected an scope in their "My interests" settings in their account. -It's important to note that even if a participant has confirmed its account and -is following the space, the system will not send her a newsletter email if she +It's important to note that even if a participant has confirmed their account and +is following the space, the system will not send them a newsletter email if they haven't activated the "I want to receive newsletters". image::newsletter_select_recipients.png[Newsletter select recipients] diff --git a/docs/en/modules/admin/pages/pages.adoc b/docs/en/modules/admin/pages/pages.adoc index 859defee13..67047552ab 100644 --- a/docs/en/modules/admin/pages/pages.adoc +++ b/docs/en/modules/admin/pages/pages.adoc @@ -100,11 +100,11 @@ image::pages_backend_tos_change.png[Backend: ToS change] image::pages_frontend_tos_change.png[Frontend: ToS change] -If a participant rejects to accept the terms, then she has three options: +If a participant rejects to accept the terms, then they have three options: -. To review this again later. It signs her out automatically. +. To review this again later. It signs them out automatically. . To download their personal data -. To delete her account +. To delete their account image::pages_frontend_tos_reject.png[Frontend: ToS reject] diff --git a/docs/en/modules/admin/pages/participants/admins.adoc b/docs/en/modules/admin/pages/participants/admins.adoc index f88bcff92b..0746ef9183 100644 --- a/docs/en/modules/admin/pages/participants/admins.adoc +++ b/docs/en/modules/admin/pages/participants/admins.adoc @@ -11,7 +11,7 @@ Here you can: * see when was the last time an administrator logged in For inviting a new administrator, you need to go to the button "New user" and fill -the form with the admin username, email and which role will she have: +the form with the admin username, email and which role will they have: * Admin: to give full access to the platform * Participant manager: to give permission to only do xref:admin:participants/impersonations.adoc[Impersonations] diff --git a/docs/en/modules/admin/pages/participants/authorizations.adoc b/docs/en/modules/admin/pages/participants/authorizations.adoc index 3f4cfd63ab..8c460ed37e 100644 --- a/docs/en/modules/admin/pages/participants/authorizations.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations.adoc @@ -8,7 +8,7 @@ With authorizations an administrator can define different permissions so partici For instance you can configure that only participants who have verified herselves by their identity documents can vote on proposals in a participatory process. -A participant can see which authorizations does she have available in her account settings. +A participant can see which authorizations do they have available in their account settings. image:authorizations_account.png[Authorizations in participants account] diff --git a/docs/en/modules/admin/pages/participants/authorizations/census.adoc b/docs/en/modules/admin/pages/participants/authorizations/census.adoc index b7e2cfbb9d..bc81ab9578 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/census.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/census.adoc @@ -15,7 +15,7 @@ In the admin panel, the administrator can review the request by going to the "Or image:authorizations_organization_census.png[Organization's census in admin panel] -After the CSV is imported then the administrator can see how many participants where imported. She can also delete this +After the CSV is imported then the administrator can see how many participants where imported. They can also delete this imported census. image:authorizations_organization_census_imported.png[Imported CSV] @@ -29,6 +29,6 @@ image:authorizations_organization_census_account.png[Organization's census in pa == 3. The participant is verified (or not) -After is verified, as with other verifications, she can see it in her account settings. +After is verified, as with other verifications, they can see it in their account settings. image:authorizations_organization_census_verified.png[Verified by organization's census] \ No newline at end of file diff --git a/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc b/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc index 20ff86d715..9abae9a45d 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/code_postal_letter.adoc @@ -1,7 +1,7 @@ = Code by postal letter authorization -This authorization allows a participant to request for a verification code to be sent to its address, to confirm that she -lives or works in this place. She'll need to then fill the code in the platform. +This authorization allows a participant to request for a verification code to be sent to its address, to confirm that they +live or work in this place. They will need to then fill the code in the platform. The process is: @@ -9,16 +9,16 @@ The process is: . An administrator sends the letter to their address with the verification code. . An administrator marks the letter as sent. . Once you mark the letter as sent, the participant will be able to introduce the code. -. If this code matchs, then she gets verified. +. If this code matchs, then they get verified. == 1. A participant request the verification code By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, -a participant can see the form for filling in her full address to request the verification code. +a participant can see the form for filling in their full address to request the verification code. image:authorizations_code_postal_letter_request.png[Code by postal letter request by participant] -If she tries to edit it, she'll see this message: +If they try to edit it, they will see this message: image:authorizations_code_postal_letter_edit.png[Edit the postal letter request] @@ -31,17 +31,17 @@ In the admin panel, the administrator can review the request by going to the "Co image:authorizations_code_postal_letter_ongoing.png[Code by postal letter ongoing panel in admin] -Here she can see the verification code and can send it to the participant by mail. After the code is sent she can mark it +Here they can see the verification code and can send it to the participant by mail. After the code is sent they can mark it as sent with the icon image:action_mark_as_sent.png[Mark as sent]. It'll also show when the letter was sent. == 3. A participant fills in the verification code -After the participant has received the code, she can go to it's account settings and click in the "Code by postal letter" +After the participant has received the code, they can go to their account settings and click in the "Code by postal letter" verfication method. image:authorizations_code_postal_letter_verify.png[Code by postal letter ongoing in the participant account] -Then she'll see the form for confirming the code. +Then they will see the form for confirming the code. image:authorizations_code_postal_letter_confirm.png[Code by postal letter confirmation form] @@ -52,6 +52,6 @@ If the verification code matches, then the participant will see the message "Con On the other hand, if the verification code doesn't match, then the participant will see the message "Your verification code doesn't match ours. Please double-check the letter we sent to you." -After is verified, as with other verifications, she can see it in her account settings. +After is verified, as with other verifications, they can see it in their account settings. image:authorizations_code_postal_letter_verified.png[Verified by code by postal letter] diff --git a/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc b/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc index 34b1e2585c..bd959dd2c6 100644 --- a/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc +++ b/docs/en/modules/admin/pages/participants/authorizations/identity_documents.adoc @@ -6,7 +6,7 @@ they could be a driver's license, a passport, a national identity card, a club m These documents will be reviewed by an administrator to accept or reject them. It's possible to do this process in two ways: Online or Offline. * Online: the participant will be asked to upload the documents, and the administrator will review these documents. -* Offline: the participant will be asked to fill in some data, and then she'll need to go to a presential place to show her documents face to face. +* Offline: the participant will be asked to fill in some data, and then they will need to go to a presential place to show their documents face to face. == Configuration @@ -42,13 +42,13 @@ The process is: . Participants fill in their document type and number and upload a copy of their document. . An administrator fills in the information present in the uploaded image. . The information should match whatever the user filled in. -. If the administrator can't clearly see the information or she can't get it verified, she can reject the request and +. If the administrator can't clearly see the information or they can't get it verified, they can reject the request and the user will be able to fix it. -=== 1. A participant fill in the document information and upload a copy of her document +=== 1. A participant fill in the document information and uploads a copy of their document By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, -a participant can see the form for uploading a copy of her document. She also needs to fill in her document type and number. +a participant can see the form for uploading a copy of their document. They also need to fill in their document type and number. image:authorizations_id_document_online.png[ID document authorization online form] @@ -69,7 +69,7 @@ image:authorizations_id_document_online_confirm.png[ID document authorization on There are two actions an admin can do: * Accept: the participant will be fully authorized. -* Reject: the participant will be prompted to amend her documents +* Reject: the participant will be prompted to amend their documents If the request is rejected then the participant can provide other pictures or document. @@ -84,7 +84,7 @@ The process is: specific time to show their documents. . An administrator go to the "Offline verification" panel and fills in the information present in the physical documents. . The information should match whatever the user filled in. -. If the administrator can't clearly see the information or she can't get it verified, she can reject the request and +. If the administrator can't clearly see the information or they can't get it verified, they can reject the request and the user will be able to fix it. For this authorization to work, an administrator need to first configure it in the admin panel with the instructions explaining @@ -95,7 +95,7 @@ image:authorizations_id_document_configuration_offline.png[ID document authoriza === 1. A participant fill in the document information and follow the instructions By going to the authorization section in its profile, or by clicking on the action button if this permission is requested, -a participant can see the form for filling in her document type and number. +a participant can see the form for filling in their document type and number. image:authorizations_id_document_offline_request.png[ID document authorization offline form] @@ -105,7 +105,7 @@ In the admin panel, the administrator can review the request by clicking in the image:authorizations_id_document_offline_button.png[ID document authorization offline button in admin] -Then she'll need to fill some data provided by the participant and by reviewing the document physically provided by her. +Then they will need to fill some data provided by the participant and by reviewing the document physically provided by them. image:authorizations_id_document_offline_confirm.png[ID document authorization offline confirmation form in admin] @@ -130,12 +130,12 @@ image:authorizations_id_document_offline_confirm.png[ID document authorization o === 3. The request is accepted or rejected In the cases where the verifications don't match (meaning that the email or the document number provided by the -participant and the ones filled by the administrators aren't the same), then the participant need to ammend it with her +participant and the ones filled by the administrators aren't the same), then the participant needs to amend it with their user account. == Both It's also possible to enable both of these verifications methods. In this case, the participant will be asked to choose -which kind of verification she wants to do. +which kind of verification they want to do. image:authorizations_id_document_account_choose.png[Choose ID document verification kind] diff --git a/docs/en/modules/admin/pages/participants/groups.adoc b/docs/en/modules/admin/pages/participants/groups.adoc index 2330cf8b74..e0f57dcb75 100644 --- a/docs/en/modules/admin/pages/participants/groups.adoc +++ b/docs/en/modules/admin/pages/participants/groups.adoc @@ -4,7 +4,7 @@ An user group is a group of participants. Depending in the installation and the == Creation -This action is done by **a participant**. She needs to go to their profile and in the sidebar there's a button that says "Create group": +This action is done by **a participant**. They need to go to their profile and in the sidebar there's a button that says "Create group": image:user_sidebar.png[User sidebar] @@ -49,7 +49,7 @@ image:user_group_new_form.png[New user group form] == Membership -After a group has been created, it's possible to invite participants to become members of the group. After a participant has accepted to be part of this group then she can become an admin. +After a group has been created, it's possible to invite participants to become members of the group. After a participant has accepted to be part of this group then they can become an admin. The actions that can be done by a participant in the user group are: diff --git a/docs/en/modules/admin/pages/participants/impersonations.adoc b/docs/en/modules/admin/pages/participants/impersonations.adoc index 24fc6e580b..90912de6f8 100644 --- a/docs/en/modules/admin/pages/participants/impersonations.adoc +++ b/docs/en/modules/admin/pages/participants/impersonations.adoc @@ -36,7 +36,7 @@ After this data is confirmed then there'll be a session for the participant for image::participants_impersonations_user.png[Impersonated user session] Finally, it's also possible to Promote a participant, meaning that after a -participant has been managed, an administrator can add the email and send her +participant has been managed, an administrator can add the email and send them an Invitation: image::participants_impersonations_promotion.png[Admin's promotion Impersonations] diff --git a/docs/en/modules/admin/pages/participants/participants.adoc b/docs/en/modules/admin/pages/participants/participants.adoc index e3649ae16c..8b82a34d4b 100644 --- a/docs/en/modules/admin/pages/participants/participants.adoc +++ b/docs/en/modules/admin/pages/participants/participants.adoc @@ -2,7 +2,7 @@ In this page an administrator can: -* Block a participant, for instance because she's spamming or acting against the Terms of Service +* Block a participant, for instance because they are spamming or acting against the Terms of Service * Contact a participant with Decidim private messages (Conversations) * Officialize a participant * See its email @@ -48,7 +48,7 @@ blocking this participant: image:participants_block_user_justification.png[Justificate the blocked user action] -Once a blocked participant tries to log-in she'll see an error message: +Once a blocked participant tries to log-in they will see an error message: image:participants_block_user_alert.png[Message shown to blocked user] @@ -58,7 +58,7 @@ See more at xref:admin:participants/reported_users.adoc[Reported users] === Show email address -After clicking this option, the admin will see a modal. She'll have to click in +After clicking this option, the admin will see a modal. They will have to click in button "Show email address". image:participants_show_email.png[Modal in show email] diff --git a/docs/en/modules/admin/pages/participants/reported_users.adoc b/docs/en/modules/admin/pages/participants/reported_users.adoc index cfd34bf176..947ae12825 100644 --- a/docs/en/modules/admin/pages/participants/reported_users.adoc +++ b/docs/en/modules/admin/pages/participants/reported_users.adoc @@ -8,8 +8,8 @@ A participant can be blocked from the xref:participants/participants.adoc[partic section in the admin panel] or through this "Reported users" section. Anyone can propose a moderation in Decidim, through the "Flag" icon in the participant -profile. After a participant has clicked in this action she needs to provide a -reason why she's making this report: +profile. After a participant has clicked in this action they need to provide a +reason why they are making this report: * Contains clickbait, advertising, scams or script bots. * Contains racism, sexism, slurs, personal attacks, death threats, suicide requests @@ -26,7 +26,7 @@ blocking this participant: image:participants_block_user_justification.png[Justificate the blocked user action] -Once a blocked participant tries to log-in she'll see an error message: +Once a blocked participant tries to log-in they will see an error message: image:participants_block_user_alert.png[Message shown to blocked user] diff --git a/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc b/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc index bdf1b9bf7f..972d70114a 100644 --- a/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc +++ b/docs/en/modules/admin/pages/participants/verifications_conflicts.adoc @@ -4,8 +4,8 @@ There are cases depending on which kind of verifications you've enabled that the For instance: -. A participant get xref:admin:participants/impersonations.adoc[impersonated], and she doesn't provide an email -. Then she creates an account and tries to verify herself with the Census verification +. A participant get xref:admin:participants/impersonations.adoc[impersonated], and they don't provide an email +. Then they create an account and try to verify themselves with the Census verification For security, we try to be extra cautious in these cases, and we want that an administrator reviews these verifications. As you can see, this depends a lot on which kind of verifications you've enabled in your organization, so it's easy to say @@ -17,7 +17,7 @@ image:verifications_conflicts.png[Verification's conflicts panel] An administrator can review these conflicts by clicking in the Transfer user image:action_transfer_user.png[Transfer user] icon. -Then she'll see the Transfer user form, where she can provide a reason for the transfer. +Then they will see the Transfer user form, where they can provide a reason for the transfer. image:verifications_conflicts_transfer_user.png[] diff --git a/docs/en/modules/admin/pages/scopes.adoc b/docs/en/modules/admin/pages/scopes.adoc index 39cc48aa55..8657bdbba0 100644 --- a/docs/en/modules/admin/pages/scopes.adoc +++ b/docs/en/modules/admin/pages/scopes.adoc @@ -96,7 +96,7 @@ On a participatory space which concerns only one of the cities, you will be able === User interests and Newsletters -A Participant can choose which Scopes she wants to follow in its account. +A Participant can choose which Scopes they want to follow in its account. image:account_my_interests.png[Account: my interests] diff --git a/docs/en/modules/admin/pages/spaces/assemblies/members.adoc b/docs/en/modules/admin/pages/spaces/assemblies/members.adoc index 2649609a99..b64508b465 100644 --- a/docs/en/modules/admin/pages/spaces/assemblies/members.adoc +++ b/docs/en/modules/admin/pages/spaces/assemblies/members.adoc @@ -27,7 +27,7 @@ image:assembly_members_new_form.png[Assembly members new form] |Participant type |Required -|Wheter this assembly member is non-participant or existing participant. Does she already have an account created on the platform? +|Wheter this assembly member is non-participant or existing participant. Do they already have an account created on the platform? |Full name |Required if it's non-participant. diff --git a/docs/en/modules/admin/pages/spaces/conferences/registrations/invites.adoc b/docs/en/modules/admin/pages/spaces/conferences/registrations/invites.adoc index 18de0c306e..d95b4056e3 100644 --- a/docs/en/modules/admin/pages/spaces/conferences/registrations/invites.adoc +++ b/docs/en/modules/admin/pages/spaces/conferences/registrations/invites.adoc @@ -17,7 +17,7 @@ image:spaces/conferences/invite_participant_form.png[Invite a participant form] |Attendee type |Required -|Wheter this invited person is a non-existing or existing participant. Does she already have an account created on the platform? +|Wheter this invited person is a non-existing or existing participant. Do they already have an account created on the platform? |Name |Required if it's a non-existing participant. diff --git a/docs/en/modules/admin/pages/spaces/conferences/registrations/types.adoc b/docs/en/modules/admin/pages/spaces/conferences/registrations/types.adoc index 1b0a31b831..c343880b08 100644 --- a/docs/en/modules/admin/pages/spaces/conferences/registrations/types.adoc +++ b/docs/en/modules/admin/pages/spaces/conferences/registrations/types.adoc @@ -54,6 +54,6 @@ image:spaces/conferences/registration_types_backend.png[Manage registration type |=== -If the participant is already logged in then she'll see her username and email in the registration page. +If the participant is already logged in then they will see their username and email in the registration page. image:spaces/conferences/registration_types_frontend_w_user.png[Select registration type with user account] diff --git a/docs/en/modules/admin/pages/spaces/conferences/registrations/users.adoc b/docs/en/modules/admin/pages/spaces/conferences/registrations/users.adoc index dfc1e486bc..fde51db0ec 100644 --- a/docs/en/modules/admin/pages/spaces/conferences/registrations/users.adoc +++ b/docs/en/modules/admin/pages/spaces/conferences/registrations/users.adoc @@ -16,12 +16,12 @@ It's possible to export the registrations in multiple formats: CSV, JSON, and XL ## Flow . A participant registers to the conference -. She receives a pending registration notification +. They receive a pending registration notification image:spaces/conferences/user_registration_pending_notification.png[Notification for pending user registration] -. She receives a pending registration email +. They receive a pending registration email image:spaces/conferences/user_registration_pending_email.png[Email for pending user registration] . An administrator reviews and confirms the registration with the image:action_check.png[Confirm] button . The participant receives a confirmed registration notification image:spaces/conferences/user_registration_confirmed_notification.png[Notification for confirmed user registration] -. She receives a confirmed registration email with an calendar file (.ICS). +. They receive a confirmed registration email with an calendar file (.ICS). image:spaces/conferences/user_registration_confirmed_email.png[Email for confirmed user registration] diff --git a/docs/en/modules/admin/pages/spaces/conferences/speakers.adoc b/docs/en/modules/admin/pages/spaces/conferences/speakers.adoc index 0a4adf6483..524f2ec414 100644 --- a/docs/en/modules/admin/pages/spaces/conferences/speakers.adoc +++ b/docs/en/modules/admin/pages/spaces/conferences/speakers.adoc @@ -25,7 +25,7 @@ image:spaces/conferences/new_speaker.png[Conferences speakers] |Participant type |Required -|Wheter this speaker is a non-participant or existing participant. Does she already have an account created on the platform? +|Wheter this speaker is a non-participant or existing participant. Do they already have an account created on the platform? |Full name |Required if it's non-participant. diff --git a/docs/en/modules/admin/pages/spaces/initiatives.adoc b/docs/en/modules/admin/pages/spaces/initiatives.adoc index 0c9b7eb3c7..e6df8dcdfb 100644 --- a/docs/en/modules/admin/pages/spaces/initiatives.adoc +++ b/docs/en/modules/admin/pages/spaces/initiatives.adoc @@ -89,7 +89,7 @@ image:admin_initiative_type.png[New initiative type form] |Collect participant personal data on signature |Optional -|Adds a step to the signature process. When a participant clicks on the signature button, she'll be redirected to a form asking for some personal data. This will be used with the PDF export action after the recollection period has ended. +|Adds a step to the signature process. When a participant clicks on the signature button, they will be redirected to a form asking for some personal data. This will be used with the PDF export action after the recollection period has ended. |Legal information about the collection of personal data |Depends on whether the option "Collect participant personal data on the signature" is checked @@ -103,7 +103,7 @@ image:admin_initiative_type.png[New initiative type form] |Authorization to verify document number on signatures |Optional -|When a participant is making the signature process, will she be asked for an authorization? +|When a participant is making the signature process, will they be asked for an authorization? |Add SMS code validation step to the signature process | @@ -137,7 +137,7 @@ This action is done by **the author**. The author is a participant that creates image:initiative_list.png[Initiatives list] -For creating an initiative, a participant must click in the "New initiative" button. Then she'll have a wizard with multiple steps: +For creating an initiative, a participant must click in the "New initiative" button. Then they will have a wizard with multiple steps: === 1.1 Choose the initiative type @@ -182,7 +182,7 @@ image:initiative_print.png[Print an initiative] ==== Technical validation -After the author has reviewed how the initiative will look, she can send it to technical validation. +After the author has reviewed how the initiative will look, they can send it to technical validation. image:initiative_send_to_technical_validation.png[Send initiative to technical validation] diff --git a/docs/en/modules/admin/partials/page_admins.adoc b/docs/en/modules/admin/partials/page_admins.adoc index ff19a4d5b4..04153a3a73 100644 --- a/docs/en/modules/admin/partials/page_admins.adoc +++ b/docs/en/modules/admin/partials/page_admins.adoc @@ -27,7 +27,7 @@ image:spaces/admins_form.png[New space admin form] |Email |Required -|What is the email of the new admin, so she can receive the invitation. +|What is the email of the new admin, so they can receive the invitation. |Role |Required @@ -58,7 +58,7 @@ image:spaces/admins_role_moderator.png[Process moderators view] === Process valuators -A space valuator can review the proposals of the space. She can: +A space valuator can review the proposals of the space. They can: * change the status of the proposals, by accepting or rejecting them * add a monetary value to the proposals, so they can be voted with the budget component. diff --git a/docs/en/modules/admin/partials/page_private_participants.adoc b/docs/en/modules/admin/partials/page_private_participants.adoc index 265233da9c..2f438591e3 100644 --- a/docs/en/modules/admin/partials/page_private_participants.adoc +++ b/docs/en/modules/admin/partials/page_private_participants.adoc @@ -66,11 +66,11 @@ image:spaces/private_participants_actions.png[Private participants actions] == Invitation -When a participant was invited she'll get an email with a link for accepting the invitation: +When a participant was invited they will get an email with a link for accepting the invitation: image:spaces/private_participants_email_invite.png[Email invitation of a private participant] -After clicking in this email, she'll have to fill a form for setting her password, accepting the Terms of Service and giving -her consent if she wants to receive newsletters. +After clicking in this email, they will have to fill a form for setting their password, accepting the Terms of Service and giving +their consent if they want to receive newsletters. image:spaces/private_participants_user_registration_form.png[User registration form of a private participant] diff --git a/docs/en/modules/features/pages/general-description.adoc b/docs/en/modules/features/pages/general-description.adoc index 2e865ae0db..1659edd73a 100644 --- a/docs/en/modules/features/pages/general-description.adoc +++ b/docs/en/modules/features/pages/general-description.adoc @@ -50,7 +50,7 @@ Administrators can *manage permissions* for registered or verified users selecti There are different types of administrators: *administrators* of the whole platform or of specific spaces and components, they can also be *moderators* (with the exclusive power of moderating proposals, comments or debates) or *collaborators* that can read unpublished content, create notes and responses to proposals. -Participants can register as an *individual* or as a *collective* (associations, working groups, etc. within the main organization). User *groups* might also be created so that individuals can be associated to a *group*. Decidim allows participants belonging to such a group to express or act individually or embodying the group identity: when an action is carried the platform prompts the participant to choose wether she wants to act as herself or as the group she belong to. +Participants can register as an *individual* or as a *collective* (associations, working groups, etc. within the main organization). User *groups* might also be created so that individuals can be associated to a *group*. Decidim allows participants belonging to such a group to express or act individually or embodying the group identity: when an action is carried the platform prompts the participant to choose wether they want to act as themselves or as the group they belong to. Participants can not only navigate the content of Decidim through the top menu and move down the architectural hierarchy, from a space to its different components; they can also get information through the *search engine*, or via *notifications*. Participants can also talk to each other by internal messaging or *chat*.