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

Introduction - spelling, grammar, and prose #196

Merged
merged 1 commit into from Oct 6, 2015

Conversation

ecorm
Copy link
Contributor

@ecorm ecorm commented Oct 6, 2015

Reviewed and edited for the quality of English prose. I have not attempted to change the meaning of anything.

My line notes are for the line immediately above.

@@ -31,7 +31,7 @@

.# Abstract

This document defines the Web Application Messaging Protocol (WAMP). WAMP is a routed protocol that provides two messaging patterns: Publish & Subscribe and routed Remote Procedure Calls. It is intended to connect application components in distributed applications. WAMP uses WebSocket as its default transport, but can be transmitted via any other protocol that allows for ordered, reliable, bi-directional and message-based communication.
This document defines the Web Application Messaging Protocol (WAMP). WAMP is a routed protocol that provides two messaging patterns: Publish & Subscribe and routed Remote Procedure Calls. It is intended to connect application components in distributed applications. WAMP uses WebSocket as its default transport, but can be transmitted via any other protocol that allows for ordered, reliable, bi-directional, and message-oriented communications.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

One finds "stream-oriented" and "message-oriented" to be the popular terms in use.

oberstet pushed a commit that referenced this pull request Oct 6, 2015
Introduction - spelling, grammar, and prose
@oberstet oberstet merged commit b402b79 into wamp-proto:master Oct 6, 2015
@oberstet
Copy link
Member

oberstet commented Oct 6, 2015

@ecorm Awesome!! I've looked through all your changes and your detailed comments (thanks for explaining each of your changes!): I think it's exactly this kind of polishing and attention to detail the spec needs. Regarding the prose: I am trying to learn from your changes. But in the end, I guess some of these are subtle and can only be spotted by native speakers. So thanks again!

@goeddea
Copy link
Contributor

goeddea commented Oct 7, 2015

@ecorm - Thanks for the edits!

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

3 participants