diff --git a/providers/common/io/docs/xcom_backend.rst b/providers/common/io/docs/xcom_backend.rst
index 47c1bd8a8698c..0a5442f4d71da 100644
--- a/providers/common/io/docs/xcom_backend.rst
+++ b/providers/common/io/docs/xcom_backend.rst
@@ -18,7 +18,7 @@
 Object Storage XCom Backend
 ===========================
 
-The default XCom backend is the :class:`~airflow.models.xcom.BaseXCom` class, which stores XComs in the Airflow database. This is fine for small values, but can be problematic for large values, or for large numbers of XComs.
+The default XCom backend is the :class:`~airflow.sdk.BaseXCom` class, which stores XComs in the Airflow database. This is fine for small values, but can be problematic for large values, or for large numbers of XComs.
 
 To enable storing XComs in an object store, you can set the ``xcom_backend`` configuration option to ``airflow.providers.common.io.xcom.backend.XComObjectStorageBackend``. You will also need to set ``xcom_objectstorage_path`` to the desired location. The connection
 id is obtained from the user part of the url that you will provide, e.g. ``xcom_objectstorage_path = s3://conn_id@mybucket/key``. Furthermore, ``xcom_objectstorage_threshold`` is required
diff --git a/providers/standard/docs/sensors/datetime.rst b/providers/standard/docs/sensors/datetime.rst
index 2a45ecb6bd869..3633fa01e7b09 100644
--- a/providers/standard/docs/sensors/datetime.rst
+++ b/providers/standard/docs/sensors/datetime.rst
@@ -55,7 +55,7 @@ Time will be evaluated against ``data_interval_end`` if present for the Dag run,
 DayOfWeekSensor
 ===============
 
-Use the :class:`~airflow.sensors.weekday.DayOfWeekSensor` to sense for day of week.
+Use the :class:`~airflow.providers.standard.sensors.weekday.DayOfWeekSensor` to sense for day of week.
 
 .. exampleinclude:: /../src/airflow/providers/standard/example_dags/example_sensors.py
     :language: python