Fixed a spelling mistake

[TNorbury]

Pull Request Checklist

Please review the Contribution Guidelines before submitting.

• Pulling from a topic/feature/bugfix branch (right side).
• Pulling against the canary branch (left side).
• Code passes linting.
• Code passes unit tests.
• Code coverage is the same or better.
• You have previously submitted a Contributor License Agreement or have contacted a maintainer to request one. (I work at Tektronix, so I don't think I need to submit one of these)

Description

Fixed a small spelling mistake in the name_map function doc

[CLAassistant]

All committers have signed the CLA.

[zkoppert]

Hey @TNorbury, Can you confirm that you have your tektronix email in your github account?

[TNorbury]

@zkoppert
Yeah, my email is there. Though I have my emails set to private, do I need to change that and then set my Tek email as my "public" one?

[zkoppert]

@zkoppert
Yeah, my email is there. Though I have my emails set to private, do I need to change that and then set my Tek email as my "public" one?

I don't think so. I will get @nlynchjo to take a look at the requirements for the CLA bot to work. Hold tight. Might be until Monday.

[codecov]

Codecov Report

Merging #17 into canary will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           canary    #17   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          15     15           
  Lines         589    589           
=====================================
  Hits          589    589

Impacted Files	Coverage Δ
syphon/hash.py	100% <ø> (ø)	⬆️

[TNorbury]

Per the changes from #18 my original change was made obsolete, however I made another change that I feel like it similar enough in scope and so I'm just going to make it part of this PR

[ethall]

Thanks for the fix, @TNorbury!

Unfortunately you submitted your pull request a few minutes before I created PR #18, which reworded the documentation you corrected.

If you see any other typos or opportunities to extend the documentation, then don't hesitate to submit another PR. (#18 finalizes the module structure, so additional PR's won't be as dangerous to make.)

[ethall]

Looks like I spoke too soon.