Skip to content
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

docs: changelog typo fix #18026

Merged
merged 1 commit into from
Jul 11, 2017
Merged

docs: changelog typo fix #18026

merged 1 commit into from
Jul 11, 2017

Conversation

oktav777
Copy link
Contributor

PR Checklist

Does please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

@oktav777
Copy link
Contributor Author

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@sibiraj-s
Copy link

sibiraj-s commented Jul 10, 2017

I don't think that was a typo. iff is a short word for if and only if

@gkalpak
Copy link
Member

gkalpak commented Jul 10, 2017

There sure is a typo in there, because it says only iff (which would be sort for only if and only if 😃).
So, it should be either iff or only if (either is equally accurate in this context).

@smart--petea
Copy link

Hm. Scratching my head about that "iff" 😕

@IgorMinar IgorMinar added the action: merge The PR is ready for merge by the caretaker label Jul 11, 2017
@IgorMinar IgorMinar merged commit db3bcc9 into angular:master Jul 11, 2017
IgorMinar pushed a commit that referenced this pull request Jul 11, 2017
(cherry picked from commit db3bcc9)
@oktav777 oktav777 deleted the patch-1 branch July 17, 2017 13:23
asnowwolf pushed a commit to asnowwolf/angular that referenced this pull request Aug 11, 2017
juleskremer pushed a commit to juleskremer/angular that referenced this pull request Aug 26, 2017
juleskremer pushed a commit to juleskremer/angular that referenced this pull request Aug 28, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants