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

4-D Open/Close #88

Open
thomasfischersm opened this issue Jun 2, 2017 · 0 comments
Open

4-D Open/Close #88

thomasfischersm opened this issue Jun 2, 2017 · 0 comments

Comments

@thomasfischersm
Copy link

  • "Show another way of opening the embrace, at the cross from crossed system (leader takes shorter step)"
    No comma.

  • "Practice both these ways"
    "Practice both ways" or "Practice both of these ways".

  • "basketball distance, baseball distance, vs ping-pong ball distance"
    Those are fun terms.

  • Steps 4 and 5 are unnecessary fluff.

  • "When opening up on the backward ocho, the follower rolls her upper body across the embrace: point of contact moves from sternum-to-sternum, across closer to side so there is more of a v-shape"
    This is a very long sentence. Some long sentences are good, like when I read the NY Times for pleasure on a Sunday morning. This one is also a little hard to follow.

What about breaking the information down like this:
"The point of contact never cuts abruptly. The follower rolls her/his upper body across the embrace (from sternum-to-sternum to the side). For example, the close embrace can open to a v-shape during the backward ocho."

(This isn't the best copy. It's only to illustrate how to break key concepts out of your sentence to make short/clear sentences.)

  • "The follower’s arms need to be mobile and allow distance to change"
    Debatable: "need to be mobile to allow the distance to change" There is a cause-and-effect relationship. The mobility is the reason that the distance can change.
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

No branches or pull requests

1 participant