Update Documention - #189
Conversation
|
I plan on looking over Sunday |
justinschwerdtfeger
left a comment
There was a problem hiding this comment.
Overall, looks very good, and I appreciate lots of areas you made the docs more concise (including what I wrote).
I made some suggestions, let me know what you think and if you agree
I'll definitely need to make some changes of my own to Docker-Guide.md and Troubleshooting.md, and README.md
|
I've addressed all of the requested changes. Please see my replies to the specific comments, as there were a few cases where I made a different choice or had some disagreement with the suggested change. |
|
Could add something like api-tools is a collection of tools, many are self contained and can be run from command line following instructions from readme.md |
justinschwerdtfeger
left a comment
There was a problem hiding this comment.
I left a couple of small tweaks
|
I've addressed all of the tweaks except for the conversations that are unresolved |
|
I can't request you for a review, but @Yogeb-tech can you review my changes? |
I found orchrestration could be replaced with simpler language
|
@justinschwerdtfeger rewrite is done :) |
|
I accidnetally pushed a large 45 mb file that contains scrapped data. this is very large and shouldnt be here, I will force push to fix it |
4b1073a to
392f482
Compare
Overall the documentation looks a lot cleaner. However, I'm sure there are improvements I can make overtime until Thursday.
My only difficulty is I do not know of any good video resources for GUIDES.md
Additionally I think it's best if you handled TroubleShooting.md. You have more knowledge of the bugs in api-tools than I do