Skip to content

Entries: Use "properties" when referring to individual options #251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

jzaefferer
Copy link
Member

Removes some ambiguity since we also "setting" as a verb.

Fixes #247

Removes some ambiguity since we also "setting" as a verb.

Fixes #247
@@ -78,7 +78,7 @@
<desc>Name of <a href="/easings/">easing</a> to use with default duration.</desc>
</type>
<type name="Object">
<desc>Animation settings with <code>easing</code> and <code>duration</code> properties.
<desc><code>easing</code> and <code>duration</code> properties to configure animations.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps "An object containing easing..."

@scottgonzalez
Copy link
Member

One minor suggestion, but other than that, this looks good.

@jzaefferer
Copy link
Member Author

Updated

@scottgonzalez
Copy link
Member

Looks good.

@jzaefferer
Copy link
Member Author

Also checked the 1-12 branch, no regressions there.

@jzaefferer jzaefferer deleted the properties branch March 12, 2015 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Use consistent noun to refer to "nested options" (properties of an option)
3 participants