diff --git a/doc/src/pgRouting-concepts.rst b/doc/src/pgRouting-concepts.rst
index d7213bfc12..c4de0fa65f 100644
--- a/doc/src/pgRouting-concepts.rst
+++ b/doc/src/pgRouting-concepts.rst
@@ -489,14 +489,21 @@ documentation and the `PostGIS <https://postgis.net/>`__ documentation.
 Build a routing topology
 ...............................................................................
 
+.. note::
+   When using topology creation (e.g. the deprecated ``pgr_createTopology`` or
+   the steps below), the edge table may be affected: if ``clean=true``, the
+   ``source`` and ``target`` column values are wiped and reassigned; otherwise
+   they are only updated where not already filled. Indexes may be created on
+   ``id``, ``the_geom``, ``source``, and ``target`` if they do not exist. A
+   vertices table is created if not present.
+
 The basic information to use the majority of the pgRouting functions ``id,
 source, target, cost, [reverse_cost]`` is what in pgRouting is called the
 routing topology.
 
 ``reverse_cost`` is optional but strongly recommended to have in order to reduce
 the size of the database due to the size of the geometry columns.
-Having said that, in this documentation ``reverse_cost`` is used in this
-documentation.
+Having said that, in this documentation ``reverse_cost`` is used throughout.
 
 When the data comes with geometries and there is no routing topology, then this
 step is needed.
diff --git a/locale/en/LC_MESSAGES/pgrouting_doc_strings.po b/locale/en/LC_MESSAGES/pgrouting_doc_strings.po
index 07c9b1af42..fadebcba7b 100644
--- a/locale/en/LC_MESSAGES/pgrouting_doc_strings.po
+++ b/locale/en/LC_MESSAGES/pgrouting_doc_strings.po
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: pgRouting v4.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-06 17:38+0000\n"
+"POT-Creation-Date: 2026-02-07 21:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -4797,6 +4797,15 @@ msgstr ""
 msgid "Build a routing topology"
 msgstr ""
 
+msgid ""
+"When using topology creation (e.g. the deprecated ``pgr_createTopology`` or "
+"the steps below), the edge table may be affected: if ``clean=true``, the "
+"``source`` and ``target`` column values are wiped and reassigned; otherwise "
+"they are only updated where not already filled. Indexes may be created on "
+"``id``, ``the_geom``, ``source``, and ``target`` if they do not exist. A "
+"vertices table is created if not present."
+msgstr ""
+
 msgid ""
 "The basic information to use the majority of the pgRouting functions ``id, "
 "source, target, cost, [reverse_cost]`` is what in pgRouting is called the "
@@ -4806,8 +4815,7 @@ msgstr ""
 msgid ""
 "``reverse_cost`` is optional but strongly recommended to have in order to "
 "reduce the size of the database due to the size of the geometry columns. "
-"Having said that, in this documentation ``reverse_cost`` is used in this "
-"documentation."
+"Having said that, in this documentation ``reverse_cost`` is used throughout."
 msgstr ""
 
 msgid ""
diff --git a/locale/pot/pgrouting_doc_strings.pot b/locale/pot/pgrouting_doc_strings.pot
index 0f446e9380..eb889c1deb 100644
--- a/locale/pot/pgrouting_doc_strings.pot
+++ b/locale/pot/pgrouting_doc_strings.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: pgRouting v4.1\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-06 17:38+0000\n"
+"POT-Creation-Date: 2026-02-07 21:55+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -4309,10 +4309,13 @@ msgstr ""
 msgid "Build a routing topology"
 msgstr ""
 
+msgid "When using topology creation (e.g. the deprecated ``pgr_createTopology`` or the steps below), the edge table may be affected: if ``clean=true``, the ``source`` and ``target`` column values are wiped and reassigned; otherwise they are only updated where not already filled. Indexes may be created on ``id``, ``the_geom``, ``source``, and ``target`` if they do not exist. A vertices table is created if not present."
+msgstr ""
+
 msgid "The basic information to use the majority of the pgRouting functions ``id, source, target, cost, [reverse_cost]`` is what in pgRouting is called the routing topology."
 msgstr ""
 
-msgid "``reverse_cost`` is optional but strongly recommended to have in order to reduce the size of the database due to the size of the geometry columns. Having said that, in this documentation ``reverse_cost`` is used in this documentation."
+msgid "``reverse_cost`` is optional but strongly recommended to have in order to reduce the size of the database due to the size of the geometry columns. Having said that, in this documentation ``reverse_cost`` is used throughout."
 msgstr ""
 
 msgid "When the data comes with geometries and there is no routing topology, then this step is needed."