Docs: A wether, as it turns out, is a castrated ram

[JustinSainton]

Description

A simple documentation change, updating several instances of a mis-applied word throughout the codebase.

How has this been tested?

Nothing functional changed, only documentation.

Types of changes

Only docs.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

[ockham]

Thanks for this! The title made my day 🐏 😆

[ockham]

Oh, I just noticed that the Static Analysis CI job is actually complaining about the removal of the (auto-generated) whitespace after "void:"

[ockham]

Thanks for addressing!

The remaining error in the Static Analysis workflow seems unrelated:

 75:4  error  Deprecated functions must be removed before releasing this version  no-restricted-syntax

referring to this:

gutenberg/packages/interface/src/components/interface-skeleton/index.js

Lines 73 to 77 in 637c43d

	deprecated( 'leftSidebar prop in InterfaceSkeleton component', {
	alternative: 'secondarySidebar prop',
	version: '9.7.0',
	plugin: 'Gutenberg',
	} );

I'll investigate some more tomorrow!

cc/ @youknowriad

[ockham]

I've filed an issue here: #28027

[ockham]

#28027 has been fixed. @JustinSainton Can you rebase the branch on latest master? That should fix the issue 🙂

[JustinSainton]

#28027 has been fixed. @JustinSainton Can you rebase the branch on latest master? That should fix the issue 🙂

sure thing, should be square now! watching the checks with baited breath 🍿

[ockham]

Hmm, looks like the rebase didn't produce quite the right result 😅

I'll have another stab at it if you don't mind 😄

[ockham]

Hmm, looks like the rebase didn't produce quite the right result

I'll have another stab at it if you don't mind

Ah, I'd missed that this branch is in a fork of the Gutenberg repo (zao-web) to which I don't have write access 😅

@JustinSainton Can you try the following for me? On the zao-web master branch,

git fetch upstream
git rebase upstream/master
git push --force-with-lease

(assuming that you have added the original Gutenberg repo as your upstream remote. If you haven't, you can do so via git add remote upstream git@github.com:WordPress/gutenberg.git.)

[gziolo]

The more detailed docs related to updating your branch when using a fork can be found at:
https://github.com/WordPress/gutenberg/blob/master/docs/contributors/git-workflow.md#keeping-your-fork-up-to-date

[JustinSainton]

The more detailed docs related to updating your branch when using a fork can be found at:
https://github.com/WordPress/gutenberg/blob/master/docs/contributors/git-workflow.md#keeping-your-fork-up-to-date

Reading this now - thanks so much for that, @gziolo!

Hmm, looks like the rebase didn't produce quite the right result

I'll have another stab at it if you don't mind

Ah, I'd missed that this branch is in a fork of the Gutenberg repo (zao-web) to which I don't have write access 😅

@JustinSainton Can you try the following for me? On the zao-web master branch,

git fetch upstream
git rebase upstream/master
git push --force-with-lease

(assuming that you have added the original Gutenberg repo as your upstream remote. If you haven't, you can do so via git add remote upstream git@github.com:WordPress/gutenberg.git.)

Giving that a go now!

Thank you both for your patience - it's a goal of mine to contribute to Gutenberg more this year, so getting past some of these initial hurdles is hugely helpful. Thank you!

[ockham]

Giving that a go now!

Seems to have worked now 🎉 Lookin' good!

Thank you both for your patience - it's a goal of mine to contribute to Gutenberg more this year, so getting past some of these initial hurdles is hugely helpful. Thank you!

Thank you -- and welcome to Gutenberg! Looking forward to having you join the party 🥳

[github-actions]

Congratulations on your first merged pull request, @JustinSainton! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts:

https://profiles.wordpress.org/me/profile/edit/

And if you don't have a WordPress.org account, you can create one on this page:

https://login.wordpress.org/register

Kudos!