Skip to content

Commit 440b42b

Browse files
committed
typos in docs
1 parent 78b135e commit 440b42b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/src/man/sectors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -894,7 +894,7 @@ for the specific case ``N_1=4`` and ``N_2=3``. We can separate this tree into th
894894
part ``(b_1⊗b_2)⊗b_3 → c`` and the splitting part ``c→(((a_1⊗a_2)⊗a_3)⊗a_4)``. Given that
895895
the fusion tree can be considered to be the adjoint of a corresponding splitting tree
896896
``c→(b_1⊗b_2)⊗b_3``, we now first consider splitting trees in isolation. A splitting tree
897-
which goes from one coupled sectors ``c`` to ``N`` uncoupled sectors ``a_1``, ``a_2``, …,
897+
which goes from one coupled sector ``c`` to ``N`` uncoupled sectors ``a_1``, ``a_2``, …,
898898
``a_N`` needs ``N-2`` additional internal sector labels ``e_1``, …, ``e_{N-2}``, and, if
899899
`FusionStyle(I) isa GenericFusion`, ``N-1`` additional multiplicity labels ``μ_1``,
900900
…, ``μ_{N-1}``. We henceforth refer to them as vertex labels, as they are associated with
@@ -908,7 +908,7 @@ the orthogonality condition
908908
which now forces all internal lines ``e_k`` and vertex labels ``μ_l`` to be the same.
909909

910910
There is one subtle remark that we have so far ignored. Within the specific subtypes of
911-
`Sector`, we do not explicitly distinguish between ``R_a^*`` (simply denoted as ``a`^*``
911+
`Sector`, we do not explicitly distinguish between ``R_a^*`` (simply denoted as ``a^*``
912912
and graphically depicted as an upgoing arrow ``a``) and ``R_{\bar{a}}`` (simply denoted as
913913
``\bar{a}`` and depicted with a downgoing arrow), i.e. between the dual space of ``R_a`` on
914914
which the conjugated irrep acts, or the irrep ``\bar{a}`` to which the complex conjugate of

0 commit comments

Comments
 (0)