Make media type descriptions more consistent

Hi,
I have changed the media type description and added in patch. Please review the changes.

Created a MR !6313 for the above patch.

Moved to needs review.

Should also be done in other spots used. Umami has media types also.

Tested MR 6313 changes are updated as per the proposed solution. Proposed#3 has been applied.
Thanks

Hi,
I have verified and tested MR !6313 on Drupal version 11.x for Standard and Umami

Testing steps:

1. Install Drupal 11.x
2. added Media and Media Library modules
3. Check for Media type descriptions
4. Apply the patch and check again for the same

Test Result:
The media type description has been updated, but the Media name should be Italic and
Image Description should - "Use Image for locally hosted image files ( use "for" not "or")

Attaching screenshots for reference.

@bharath_kondeti this was tagged for novice just yesterday, which is intended for newer users. Based on your post history believe you should avoid novice issues in the future please

I came across this issue during the Drupal Contribution Day Japan 2025.
https://www.drupal.org/community/events/drupal-japan-contribution-day-ju...

It looks like both the Standard and Umami profiles' config have already been updated.

If there's anything left to be done, I'd be happy to work on it.

Tagging for subsystem maintainer review to weigh in on which proposed description format we want to use.

If option 3 is chosen, then this needs to go back to Needs Work status to italicize the type name as noted in #18.

And in my opinion the issue summary needs to be updated because the text included in that image is not accessible. Someone should rewrite it into plain text in the summary.

Updated summary and remaining tasks

Changed to single quotes

I'm not sure where "proposed 3" came from, but it's not grammatically correct without the italics (e.g. "Use image for locally hosted image files" is missing an article).

Also, fewer words is better. So, if we're repeating "Use foo for [what foo is] every time when the context already makes it clear that we're talking about a foo, that's not helpful. Therefore, I'd propose we instead use the format like (e.g.):
"A locally hosted image file."
And standardize on the singular.

This will need the issue summary updated to reflect that new approach, and an updated MR. Thanks!

The Drupal Contribution Mentoring team is triaging issues for DrupalCon Nara 2025, and we are reserving this issue for Mentored Contribution during the event. After November 19, this issue returns to being open to all. Thanks!

I agree with #29, as it sounds good & correct in context.
I’d like to contribute this issue — working on refining the description text patch as proposed.

Here is patch with proposed changes
It would be helpful, if anyone could review.

@sourav_paul, are you contributing at DrupalCon Nara? If so, welcome, and come find one of the mentors tomorrow for help creating a proper merge request!

If not, please follow the green message in #29 until after November 19. Thanks!

Hi all, I am at DrupalCon Nara 2025 and am working with my team to create a merge request.

I am contributing on this issue with a team at Nara DrupalCon 2025

We added a new approach as proposed 4 in the issue summary based on #29

Our team (@silverham, @h_bee, @suryanto, @rduterte, @akmalfikri and myself) proposed the above changes for review.

1. We reviewed the issue history and agreed to implement the proposal by @xjm (#29), mainly to use concise and consistent language.
2. We updated the issue summary by added Option 4, based on the discussion history on this thread.
3. We reversed the changes instead of force-pushing our changes, based on advice by @silverham.
4. We have confirm the CI checks passed, and updated the issue status to "Needs Review".

I am contributing on this issue with a team at Nara DrupalCon 2025

After the changes were put into a merge request, we reviewed the merge request. I added some small remarks about the quote format to be used, so it can become more consistent. I also updated the issue description for the next steps to be taken.

This is amazing work, everyone.

Can we update the issue summary to mention which of the propose resolutions is the one in the merge request?

And then I think based on the discussion at the table in Nara, we decided to link the related issue about standardizing the quote formats, and then we can remove that as an action item and resolve the merge request threads.

Then remove the Needs issue summary update and I think we can change the status to RTBC!

Thanks for the great work on this everyone! I think we've come up with the best solution.

Now that we've settled on a proposed resolution, we can simplify the proposed resolution section to just say that several different proposals were considered, and to document the one we chose.

I agree with @rduterte's assessment that the issue of inconsistency between single and double quotes already has its own issue, and is therefore best not managed here. Good scope management! (There are legitimate cases for double quotes when strings contain apostrophes, for example, etc. etc.... and all that discussion would derail this issue, which is why we move the discussion outside this scope.)

I've made two very tiny suggestions on the merge request. If the contributors think these are good changes, then you can review them and mark the issue back to "Reviewed and tested by the community".

The issue summary has been changed and it has been reviewed again. The change(s) suggested by @xjm is/are integrated.

(comment as helped with cherry pick of git code at DrupalCon Nara 2025)

Committed LIVE at DrupalCon Nara! Thanks to everyone who helped contribute to this issue over the past for years.

Cherry-picked to 11.3.x as a minor-safe string change.

Thanks!

Awesome team!
Nice to see that, it got resolved.