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

fix wording #180

Merged
merged 1 commit into from Mar 9, 2017
Merged

fix wording #180

merged 1 commit into from Mar 9, 2017

Conversation

nomicode
Copy link
Contributor

@nomicode nomicode commented Mar 7, 2017

slightly more idiomatic wording I think

@nomicode nomicode requested a review from m-kharbat March 7, 2017 14:18
@coveralls
Copy link

coveralls commented Mar 7, 2017

Coverage Status

Coverage remained the same at 81.287% when pulling b9a0ed0 on nomi/fix-wording into 364024a on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 81.287% when pulling b9a0ed0 on nomi/fix-wording into 364024a on master.

@codecov-io
Copy link

Codecov Report

Merging #180 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #180   +/-   ##
=======================================
  Coverage   81.17%   81.17%           
=======================================
  Files          16       16           
  Lines        1865     1865           
=======================================
  Hits         1514     1514           
  Misses        351      351

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 364024a...b9a0ed0. Read the comment docs.

@nomicode nomicode merged commit c245bd4 into master Mar 9, 2017
@nomicode nomicode deleted the nomi/fix-wording branch March 9, 2017 14:26
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

Successfully merging this pull request may close these issues.

None yet

4 participants