client/src/locale/en.js
attirbutes
alllConnections
idpConfigExceptionIfo
impportApplicationConfirmation
impportConnectionConfirmation
....
Or we can just feed the whole en.js file to an LLM. Some of the findings are nitpicks, others are genuinely bad. ;)
....
Major grammar/spelling issues
"Message included in the join request send to the administrators"
→ "Message included in the join request sent to the administrators"
"The apps that are linked to our IdP"
→ "The applications linked to your IdP" (or "...our IdP" if that is actually intended)
"responsible:"
→ "Responsible:"
"Decentral team"
→ "Decentralised team"
"utitility"
→ "utility"
"privacy friendly"
→ "privacy-friendly"
"IdP's"
→ "IdPs"
"Congifuration details"
→ "Configuration details"
"Extract metadata from url"
→ "Extract metadata from URL"
"Description in Engels"
→ "Description in English"
"Image is larger then 2MB."
→ "Image is larger than 2 MB."
"Activate dummy IdP's after comfirmation"
→ "Activate dummy IdPs after confirmation"
"Applicatieteam"
→ "Application team"
"organisationusers"
→ "organisation users"
"Rol"
→ "Role"
"on seperate lines"
→ "on separate lines"
"directy"
→ "directly"
"directy via SURFconext, others via eduGAIN.."
→ "directly via SURFconext, others via eduGAIN."
"Terug"
→ "Back"
"attirbutes"
→ "attributes"
"self-explanatoy"
→ "self-explanatory"
"The proces consists"
→ "The process consists"
"organisatie"
→ "organisation"
"Applicatie koppeling"
→ "Application connection"
"SURFconcext Invite"
→ "SURFconext Invite"
"idpConfigExceptionIfo"
→ Probably intended to be idpConfigExceptionInfo (key name)
"your are"
→ "you are" (appears twice)
"Your request has been send"
→ "Your request has been sent"
"diconnect"
→ "disconnect"
"propogate"
→ "propagate"
"acces"
→ "access" (appears twice)
"has been send"
→ "has been sent" (contract message)
"SURF klant support"
→ "SURF customer support"
"impportApplicationConfirmation"
→ Probably intended to be importApplicationConfirmation (key)
"impportConnectionConfirmation"
→ Probably intended to be importConnectionConfirmation (key)
Grammar/wording improvements
"You work for a (commercial) organisation"
→ "You work for a commercial organisation"
(Parentheses are unnecessary.)
"Then sign in with eduID."
→ "Sign in with eduID."
"Give students, staff and researchers..."
→ "Give students, staff, and researchers..."
(Depends on your preferred comma style.)
"takes care of central policies and is made to be privacy friendly."
→ "provides central policy management and is designed to be privacy-friendly."
"Your organisation is created."
→ "Your organisation has been created."
"You will be contacted by mail"
→ "You will be contacted by email."
"Go back to create your own organisation."
This is split into:
"Go back to "
" create your own organisation."
Consider:
→ "Go back to create or join an organisation."
(depending on the UI)
"Just relax, your request..."
→ "Your request to join the organisation... is pending."
"Manage the technical connection and metadata of your apps."
→ "...applications."
"Discover apps that aren't yet connected."
More natural:
→ "Discover applications that are not yet connected."
"Schac home"
→ "SCHAC home organisation" (if referring to the SCHAC attribute)
"Only external organisations from external (commercial) service providers are mutable."
Slightly repetitive:
→ "Only organisations belonging to commercial service providers can be modified."
"A connection with entityID..."
→ "A connection with Entity ID..."
"Request activation for {{name}}."
→ "Request production activation for {{name}}."
"Refresh tokens"
→ Usually "Refresh Tokens" to match the capitalization of the other OAuth grant types.
PKCE tooltip:
→ "...preventing interception of authorization codes. It is especially important..."
"Receive all claims directly in the ID Token"
→ "Include all claims directly in the ID token."
("ID token" is the more common capitalization.)
"Error in parsing the metadata"
→ "Error parsing the metadata"
"You'll receive..."
Your file otherwise mostly uses "You will". Consider consistency.
"Privacy friendly including reliability"
→ "Privacy-friendly with persistent identification"
"his bundle is specifically designed..."
→ "This bundle is specifically designed..."
"The following attributes are available with this bundle"
→ "...in this bundle."
"Only employees of linked institutions"
→ "Only users from linked institutions"
"The client secret is displayed once below."
→ "The client secret is shown only once."
"For security reasons your current secret can not be displayed."
→ "For security reasons, your current secret cannot be displayed."
"The SAML connection is ready"
→ "Your SAML connection is ready"
"Use functional email addresses (like {{example}})"
→ "...(such as {{example}})"
"One real email is required"
→ "At least one valid email address is required."
"This way the institutions interested..."
→ "This way, institutions interested..."
"This connection is pending production-ready status. If you want to test connections, create a new connection"
→ "...If you want to continue testing, create a new test connection."
"OpenID Connect Discovery"
→ "OpenID Connect discovery document" (if applicable)
"Application access has been set"
→ "Application access has been configured."
"How do you want to configure default access?"
→ "How would you like to configure default access?"
"Still don't want to connect?"
→ "Do you still want to disconnect?"
"There are users yet from outside with a role"
→ "There are no external users with a role yet."
"Users with role"
→ "Users with roles"
"Type your descriptive message"
→ "Enter a message to display to users."
"No one (hide the app for now)"
→ "No one (hide the application for now)"
"The authority determines the rights..."
→ "The selected role determines the permissions..."
client/src/locale/en.js
attirbutes
alllConnections
idpConfigExceptionIfo
impportApplicationConfirmation
impportConnectionConfirmation
....
Or we can just feed the whole en.js file to an LLM. Some of the findings are nitpicks, others are genuinely bad. ;)
....
Major grammar/spelling issues
Grammar/wording improvements