Skip to content

Use neutral phrasing in README - #360

Merged
iCharlesHu merged 1 commit into
swiftlang:mainfrom
broken-circle:readme-phrasing
Aug 10, 2026
Merged

Use neutral phrasing in README#360
iCharlesHu merged 1 commit into
swiftlang:mainfrom
broken-circle:readme-phrasing

Conversation

@broken-circle

Copy link
Copy Markdown
Member

#328 made wording changes to use more neutral phrasing:

I went ahead and extended this to remove the biological or family metaphors from the documentation content (such as "spawn", "kill", "children", "parent") to use more neutral/agnostic terms.

I noticed some of these phrases were still present in the README.

cc @heckj

@broken-circle

broken-circle commented Aug 6, 2026

Copy link
Copy Markdown
Member Author

This and prior PRs address user-facing documentation, but many uses of the non-neutral phrases still exist in internal documentation and code comments. If we're open to removing these, I'll open a separate PR to do that. I think it's a good idea because it keeps the entire codebase, public or otherwise, aligned on the same phrasing.

One exception is when referring specifically to APIs like posix_spawn; any documentation or comments referring to such an API would be left as-is.

@iCharlesHu

Copy link
Copy Markdown
Contributor

@broken-circle could you rebase? I'm not sure why the jobs are not running...

@broken-circle

Copy link
Copy Markdown
Member Author

@iCharlesHu Sure thing. Something seemed to be wrong with GitHub Actions late last week, since it didn't run here or on a few other PRs I updated, but looks like it's working now!

@iCharlesHu
iCharlesHu merged commit 44f6d55 into swiftlang:main Aug 10, 2026
89 of 90 checks passed
@heckj

heckj commented Aug 12, 2026

Copy link
Copy Markdown
Member

(thank you @broken-circle - I didn't see the ping to review until after it was merged, but it looks great!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants