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

Final edits #14

Merged
merged 3 commits into from
Mar 31, 2016
Merged

Conversation

chimericalidea
Copy link
Collaborator

Changed flow of architecture page and added transition text.

added link in Architecture page to Span Receivers page (I hope!)

minor updates throughout
-simplified language

@@ -6,17 +6,17 @@ weight: 0
![Web interface screenshot]({{ site.github.url }}/public/img/web-screenshot.png)

Zipkin is a distributed tracing system. It helps gather timing data needed to
troubleshoot latency problems in microservice architectures. It manages both the
troubleshoot latency problems in micro-service architectures. It manages both the
Copy link
Member

Choose a reason for hiding this comment

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

microservice is more commonly used than micro-service https://en.wikipedia.org/wiki/Microservices

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

corrected

@codefromthecrypt
Copy link
Member

Hi, there.

I know I made comments, but please don't lose hope :) The documentation site was forklifted and needs a lot of refactoring. You can choose how much of that you feel up to, and any amount will be very appreciated.

@codefromthecrypt
Copy link
Member

ps added a note about packaging as it relates to why we don't need zipkin-web anymore (spoiler, it is hosted on the same process as the api, most typically) #15

@chimericalidea chimericalidea mentioned this pull request Mar 30, 2016
request back to the client. The difference between this and `ss` will be the
amount of time it took the server to process the request.
* **cr** - Client Recieve. The client has received the response from the server.
* **cr** - Client Receiver: The client has received the response from the server.
Copy link
Member

Choose a reason for hiding this comment

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

Receive

@codefromthecrypt
Copy link
Member

some unimportant nits. thanks for offering follow-up changes!

@codefromthecrypt codefromthecrypt merged commit 4c5fc6d into openzipkin:master Mar 31, 2016
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.

3 participants