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

updates to doc\MONSTERS.md #36116

Merged
merged 2 commits into from
Dec 18, 2019
Merged

updates to doc\MONSTERS.md #36116

merged 2 commits into from
Dec 18, 2019

Conversation

Jerimee
Copy link
Contributor

@Jerimee Jerimee commented Dec 14, 2019

Summary

SUMMARY: None

Purpose of change

Minor updates to the documentation for name, volume, and weight of monster JSON

Describe alternatives you've considered

These changes are based upon instructions I received from active/trusted contributors. I double checked and asked follow up questions in an attempt to be as accurate as possible.

Additional context

only one file should be changed: MONSTERS.md

Copy link
Member

@I-am-Erk I-am-Erk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some small additions and then I think it's good.

doc/MONSTERS.md Outdated Show resolved Hide resolved
doc/MONSTERS.md Outdated Show resolved Hide resolved
@KorGgenT KorGgenT added the <Documentation> Design documents, internal info, guides and help. label Dec 15, 2019
Copy link
Contributor Author

@Jerimee Jerimee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Umm... I don't think I should have started this review. Disregard.

@Jerimee Jerimee requested a review from I-am-Erk December 18, 2019 19:17
@Jerimee
Copy link
Contributor Author

Jerimee commented Dec 18, 2019

@I-am-Erk sorry for hassle - I did a bunch of weird stuff to try and clean up github fork and this PR suffers from that.

This PR should be merged or closed without merging. Let me know if you'd like me to close it myself.

@I-am-Erk
Copy link
Member

I don't think you need to do final edits in a second PR. Just add the phrases describing what units are accepted to your current changes. It's well within the scope of this PR

@Jerimee
Copy link
Contributor Author

Jerimee commented Dec 18, 2019

I think I made the changes requested (re units accepted).

I've made multiple forks (using organizations) and then archived them (including the one associated with this PR) as I flail about making a giant mess of my local repo. I was trying to spare myself the trouble of unarchiving etc etc etc. But I think I did it correctly.

@I-am-Erk I-am-Erk merged commit a7caa2a into CleverRaven:master Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
<Documentation> Design documents, internal info, guides and help.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants