clarified why there might be less signal in the TXPipe outputted Cosm…

…oDC2 thing

examples/demo_coordinate_system_datasets.ipynb

@@ -226,7 +226,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Here we create a `GalaxyCluster` object, specifying the *correct* coordinate system.  For source galaxies from CosmoDC2, these are in the **euclidean** coordinate system.  We use the implemented kwarg when defining the galaxy cluster object to also specify the **euclidean** coordinate system.  However, with a single galaxy cluster, the signal is not significant enough to clearly see a difference.  There is a possible excess excess with the correct coordinate system at larger radii.  Note:  The lensing signal in CosmoDC2 clusters at the inner radii is known to be weak due to a limitation in the resolution when the ray tracing was performed in generating the source galaxy shears."
+    "Here we create a `GalaxyCluster` object, specifying the *correct* coordinate system.  For source galaxies from CosmoDC2, these are in the **euclidean** coordinate system.  We use the implemented kwarg when defining the galaxy cluster object to also specify the **euclidean** coordinate system.  However, with a single galaxy cluster, the signal is not significant enough to clearly see a difference.  There is a possible excess excess with the correct coordinate system at larger radii.  Note:  First, the lensing signal in CosmoDC2 clusters at the inner radii is known to be weak due to a limitation in the resolution when the ray tracing was performed in generating the source galaxy shears.  Second, this has been process through `TXPipe`, which is something else we will need to understand."
    ]
   },
   {