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

Typo in Probability Theory (For Scientists and Engineers) #28

Open
AraujoH opened this issue Jan 14, 2020 · 3 comments
Open

Typo in Probability Theory (For Scientists and Engineers) #28

AraujoH opened this issue Jan 14, 2020 · 3 comments

Comments

@AraujoH
Copy link

AraujoH commented Jan 14, 2020

Hello, Michael

I was reading your case study on Probability Theory Concepts titled "Probability Theory (For Scientists and Engineers)" and I think I found a typo.

On the 4th paragraph of Section 2.1 Probability Distributions, you write:

Moreover, any distribution of probability should _globally consistent_ over any 
disjoint decomposition of the total space. 

I believe there is a missing "be" between "should" and "globally".

I know this is minor and won't affect the comprehension of your reader, yet, your work is so thorough and top-notch that I thought you'd like to know about it so you could make the correction should you judge it necessary.

P.S.: I'd also like to take this opportunity to thank you for your generosity. It's not every day that we find sterling work like yours available as free online tutorials. It's of prime quality and deeply insightful. Your clear written explanation aided by sharp visualizations helps all of us, non-Mathematicians, to have a firmer grip on vital concepts that sometimes are poorly covered at college-level courses.

@betanalpha
Copy link
Owner

betanalpha commented Jan 15, 2020 via email

@japhir
Copy link

japhir commented Jul 26, 2021

Hi @betanalpha, I only just found out about your nice material! I was reading through and found some typo's as well. Would making a pull request still be appreciated? I see there are still some open ones and I don't want to bother you or do work that ends up being useless ;-). Work in-progress of the stuff I could find thus far in my clone.

@betanalpha
Copy link
Owner

Thanks! There are a long list of typos and edits pointed out by others already both privately and in a few other pull requests, but as I have more significant updates to the case study in mind I'm waiting to handle everything at once. You're welcome to submit a PR or even just comment on any typos you've found in this or any of the other pull requests for this case study and I'll be sure to incorporate them then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants