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

Fixing Typos outside the 1.6 RC1 release PR #545

Closed
ahayashi opened this issue Sep 27, 2024 · 2 comments
Closed

Fixing Typos outside the 1.6 RC1 release PR #545

ahayashi opened this issue Sep 27, 2024 · 2 comments

Comments

@ahayashi
Copy link

Problem Statement

We have found the following typos that are outside the changes made in pull request #540.

Proposed Changes

  1. content/backmatter.tex (L1185 in the updated version in OpenSHMEM 1.6rc1 Draft #540)

    and general readabilty and usability improvements to the document structure.

    • “readabilty” -> “readability”?
  2. content/shmem_ctx_session_config_t.tex

    the occurence of any completion or memory ordering operations.

    • “occurence” -> “occurrence”?
  3. content/shmem_ctx_session_start.tex

    exact threshold for this benefit depends on the \openshmem implemenation

    • “implemenation” -> “implementation”?
  4. content/shmem_team_config_t.tex

    in existance at any given time. It is not a guarantee that $N$

    • "existance” -> “existence”?
  5. content/shmem_reductions.tex (L382 in the updated version in OpenSHMEM 1.6rc1 Draft #540)

    {In the following \Cstd[11] example, each \ac{PE} intializes an array of

    • “intializes” -> “initializes”?
  6. content/p2p_sync_intro.tex

    \openshmem implemementation is not required to provide support for these types.

    • “implemementation” -> “implementation”?
  7. example_code/shmem_reduce_example.c

    printf("A maximal number occured (at least once) at the following indices:\n");

    • “occured” -> “occurred”?

Impact on Implementations

N/A

Impact on Users

N/A

References and Pull Requests

#540

@ahayashi
Copy link
Author

ahayashi commented Sep 27, 2024

@jdinan I'm not sure if this is the right place to report these typos. Please feel free to close this and let me know if there is a better option. Thank you!

@jdinan
Copy link
Collaborator

jdinan commented Sep 27, 2024

Thanks! These have all been applied to #546

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Doc Editor
Development

No branches or pull requests

2 participants