diff --git a/_troubleshooting/cagg-watermark-in-future.md b/_troubleshooting/cagg-watermark-in-future.md
index de852e54c7..aaabb884ea 100644
--- a/_troubleshooting/cagg-watermark-in-future.md
+++ b/_troubleshooting/cagg-watermark-in-future.md
@@ -86,7 +86,7 @@ window.
 
     ```sql
     SELECT COALESCE(
-        _timescaledb_internal.to_timestamp(_timescaledb_internal.cagg_watermark(<ID>)),
+        _timescaledb_functions.to_timestamp(_timescaledb_functions.cagg_watermark(<ID>)),
         '-infinity'::timestamp with time zone
     );
     ```
diff --git a/_troubleshooting/scheduled-jobs-stop-running.md b/_troubleshooting/scheduled-jobs-stop-running.md
index 64cf26cb12..5a6bdb5843 100644
--- a/_troubleshooting/scheduled-jobs-stop-running.md
+++ b/_troubleshooting/scheduled-jobs-stop-running.md
@@ -32,7 +32,7 @@ Your scheduled jobs might stop running for various reasons. On self-hosted
 TimescaleDB, you can fix this by restarting background workers:
 
 ```sql
-SELECT _timescaledb_internal.start_background_workers();
+SELECT _timescaledb_functions.start_background_workers();
 ```
 
 <CloudMSTRestartWorkers />
diff --git a/quick-start/ruby.md b/quick-start/ruby.md
index 6cf59f0158..b39e12a0cd 100644
--- a/quick-start/ruby.md
+++ b/quick-start/ruby.md
@@ -238,7 +238,7 @@ and most other tasks are executed on the hypertable.
     Indexes:
       "page_loads_created_at_idx" btree (created_at DESC)
     Triggers:
-      ts_insert_blocker BEFORE INSERT ON page_loads FOR EACH ROW EXECUTE FUNCTION _timescaledb_internal.insert_blocker()
+      ts_insert_blocker BEFORE INSERT ON page_loads FOR EACH ROW EXECUTE FUNCTION _timescaledb_functions.insert_blocker()
     ```
 
 </Collapsible>
diff --git a/self-hosted/multinode-timescaledb/multinode-maintenance.md b/self-hosted/multinode-timescaledb/multinode-maintenance.md
index 4ae2a21edd..c0ee41d600 100644
--- a/self-hosted/multinode-timescaledb/multinode-maintenance.md
+++ b/self-hosted/multinode-timescaledb/multinode-maintenance.md
@@ -32,7 +32,7 @@ The custom maintenance job can be run as a user-defined action. For example:
 CREATE OR REPLACE PROCEDURE data_node_maintenance(job_id int, config jsonb)
 LANGUAGE SQL AS
 $$
-    SELECT _timescaledb_internal.remote_txn_heal_data_node(fs.oid)
+    SELECT _timescaledb_functions.remote_txn_heal_data_node(fs.oid)
     FROM pg_foreign_server fs, pg_foreign_data_wrapper fdw
     WHERE fs.srvfdw = fdw.oid
     AND fdw.fdwname = 'timescaledb_fdw';
diff --git a/use-timescale/troubleshoot-timescaledb.md b/use-timescale/troubleshoot-timescaledb.md
index 68774622ea..868dac5f5d 100644
--- a/use-timescale/troubleshoot-timescaledb.md
+++ b/use-timescale/troubleshoot-timescaledb.md
@@ -77,7 +77,7 @@ Your scheduled jobs might stop running for various reasons. On self-hosted
 TimescaleDB, you can fix this by restarting background workers:
 
 ```sql
-SELECT _timescaledb_internal.start_background_workers();
+SELECT _timescaledb_functions.start_background_workers();
 ```
 
 <CloudMSTRestartWorkers />