1 files changed, 3 insertions, 2 deletions
diff --git a/README.md b/README.md
index fc71f2d..de56f9d 100644
--- a/README.md
+++ b/README.md
@@ -109,8 +109,9 @@ table to solving EO with HTM moveset and this coordinate would have values 0 (fo
 There is one caveat: each coordinates also needs an inverse function that takes a
 coordinate value and returns a cube which has that coordinate. This is in general
 more complicated, but luckily the cube does not need to be fully built or consistent.
-This inverse-coordinate is used only in one specific step when building pruning tables
+This inverse-coordinate is used only in one specific step when generating symmetry
-to avoid using up hundreds of Gb of memory.
+data, and I don't know if it is possible to avoid it (maybe it is). It is also used
+when building pruning tables, but in that case it is avoidable.
 Note: this part is different from what Cube Explorer does. Overall I think it is
 conceptually easier, although in practice it was still hard to implement.

diff --git a/README.md b/README.md index fc71f2d..de56f9d 100644 --- a/README.md +++ b/README.md
@@ -109,8 +109,9 @@ table to solving EO with HTM moveset and this coordinate would have values 0 (fo
109	There is one caveat: each coordinates also needs an inverse function that takes a	109	There is one caveat: each coordinates also needs an inverse function that takes a
110	coordinate value and returns a cube which has that coordinate. This is in general	110	coordinate value and returns a cube which has that coordinate. This is in general
111	more complicated, but luckily the cube does not need to be fully built or consistent.	111	more complicated, but luckily the cube does not need to be fully built or consistent.
112	This inverse-coordinate is used only in one specific step when building pruning tables	112	This inverse-coordinate is used only in one specific step when generating symmetry
113	to avoid using up hundreds of Gb of memory.	113	data, and I don't know if it is possible to avoid it (maybe it is). It is also used
		114	when building pruning tables, but in that case it is avoidable.
114		115
115	Note: this part is different from what Cube Explorer does. Overall I think it is	116	Note: this part is different from what Cube Explorer does. Overall I think it is
116	conceptually easier, although in practice it was still hard to implement.	117	conceptually easier, although in practice it was still hard to implement.