-
-
Notifications
You must be signed in to change notification settings - Fork 119
Minor text edits on multiple pages #207
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
Conversation
Besides minor editing and reformatting, I suggest removing the info indicating when the content was created since it doesn't bring much value to numpy.org users.
Proofreading before the deployment.
Proofreading before the deployment.
Proofreading before the deployment.
Proofreading before the deployment.
Proofreading before the deployment.
Proofreading before the deployment.
Proofreading before the deployment.
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.
Thanks @InessaPawson, very useful fixes.
I caught some more issues with the videos and tutorials listed, so I'll push a follow-up commit here for you to review.
|
||
*** | ||
|
||
## NumPy Talks | ||
|
||
* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) by Jaime Fernández (2016) |
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.
The style changes are an improvement, but I'd like to keep the years because that gives relevant context. For talks about the state of NumPy or future plans, it matters when the talk was given.
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.
I see your point. I was going back and forth on whether to include the years for the talks.
Plus a couple of trivial formatting things
I'll merge it so it's in, we can push a follow up commit if needed. Thanks @InessaPawson |
Proofreading the website content before the deployment.