Skip to content

Commit

Permalink
typo fix
Browse files Browse the repository at this point in the history
  • Loading branch information
lukaspie committed Jul 1, 2024
1 parent e41fd3c commit 1e4929e
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions contributed_definitions/NXcoordinate_system_set.nxdl.xml
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@
This :ref:`NXcoordinate_system_set` should define at least one NXcoordinate_system
instance. This shall be named such that it is clear how this coordinate system is
typically referred to in a community. For the NeXus `McStas coordinate system, it is
adviused to call it mcstas for the sake of improved clarity.
advised to call it mcstas for the sake of improved clarity.
Additional NXcoordinate_system instances should be specified if possible in that same
:ref:`NXcoordinate_system_set` instead of cluttering them across the tree.

Expand Down Expand Up @@ -118,5 +118,5 @@ Depends on cardinality of NXcoordinate_system_set, i.e. how many NXcoordinate_sy
- 0, the root of an NXtransformation chain i.e. "." means McStas
- 1, the root of an NXtransformation chain i.e. "." means "that specific CS" i.e. the one defined by the single instance of NXcoordinate_system in the set
- > 1, "." becomes ambiguous. My suggestion, spell out the name of the specific NXcoordinate_system instance to be used, using "."
despite all these, a warning should be raised, like a logic warning (and McStas kick in) or an error (i.e. be forbidden) be raised-->
despite all these, a warning should be raised, like a logic warning (and McStas kick in) or an error (i.e. be forbidden) be raised-->
</definition>
8 changes: 4 additions & 4 deletions contributed_definitions/nyaml/NXcoordinate_system_set.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ doc: |
This :ref:`NXcoordinate_system_set` should define at least one NXcoordinate_system
instance. This shall be named such that it is clear how this coordinate system is
typically referred to in a community. For the NeXus `McStas coordinate system, it is
adviused to call it mcstas for the sake of improved clarity.
advised to call it mcstas for the sake of improved clarity.
Additional NXcoordinate_system instances should be specified if possible in that same
:ref:`NXcoordinate_system_set` instead of cluttering them across the tree.
Expand Down Expand Up @@ -100,7 +100,7 @@ NXcoordinate_system_set(NXobject):
# despite all these, a warning should be raised, like a logic warning (and McStas kick in) or an error (i.e. be forbidden) be raised

# ++++++++++++++++++++++++++++++++++ SHA HASH ++++++++++++++++++++++++++++++++++
# 19dcdaa81b00c7163aed10d5e3a9fd6393f681c1df3bf0b79af8db1e9f8e746e
# 2c012af7dc8e09a7f7df9408a0d04886f58bc74feff6fc207658954ad8682422
# <?xml version='1.0' encoding='UTF-8'?>
# <?xml-stylesheet type="text/xsl" href="nxdlformat.xsl"?>
# <!--
Expand Down Expand Up @@ -142,7 +142,7 @@ NXcoordinate_system_set(NXobject):
# This :ref:`NXcoordinate_system_set` should define at least one NXcoordinate_system
# instance. This shall be named such that it is clear how this coordinate system is
# typically referred to in a community. For the NeXus `McStas coordinate system, it is
# adviused to call it mcstas for the sake of improved clarity.
# advised to call it mcstas for the sake of improved clarity.
# Additional NXcoordinate_system instances should be specified if possible in that same
# :ref:`NXcoordinate_system_set` instead of cluttering them across the tree.
#
Expand Down Expand Up @@ -221,5 +221,5 @@ NXcoordinate_system_set(NXobject):
# - 0, the root of an NXtransformation chain i.e. "." means McStas
# - 1, the root of an NXtransformation chain i.e. "." means "that specific CS" i.e. the one defined by the single instance of NXcoordinate_system in the set
# - > 1, "." becomes ambiguous. My suggestion, spell out the name of the specific NXcoordinate_system instance to be used, using "."
# despite all these, a warning should be raised, like a logic warning (and McStas kick in) or an error (i.e. be forbidden) be raised-->
# despite all these, a warning should be raised, like a logic warning (and McStas kick in) or an error (i.e. be forbidden) be raised-->
# </definition>

0 comments on commit 1e4929e

Please sign in to comment.