-
Notifications
You must be signed in to change notification settings - Fork 27
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
Fix some typos in docs. #103
Conversation
Thanks for the PR and especially the call out! The only usage I can find of a cache setting an object’s state is when it creates a new ghost. So perhaps uninitalized it should be. (Though I didn’t try to review all docs for correctness. ) |
So, should I fix it, or wait for more reviewers? |
I think you can fix it. |
@ramiroluz Is this pull request ready to merge or are you still working on it? |
Almost done, just need a quick fix, mentioned in the review. I can do it
tomorrow (Tuesday) night.
Em seg, 19 de nov de 2018 02:29, Michael Howitz <notifications@github.com
escreveu:
… @ramiroluz <https://github.com/ramiroluz> Is this pull request ready to
merge or are you still working on it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAR5NtaYl0JPAc6-3jVbGk5KjNbjim4vks5uwl3ngaJpZM4YYVEy>
.
|
@icemac done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I do not think that merging this PR requires to sign a contributor agreement so I am going to merge it. |
Thank you! |
Indeed! |
Found some typos in the docs.
REVIEWER: please pay attention to the cache.rst doc. On the first Note, I assumed that the author intended to say: "... newly created and initialized objects directly ... " instead of "... uninitialized ..."