diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index ece47e757b..37619e382d 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -318,23 +318,6 @@
-
- bluetooth.bbclass
-
-
- The bluetooth class defines a variable that
- expands to the recipe (package) providing core
- bluetooth support on the platform.
-
-
-
- For details on how the class works, see the
- meta/classes/bluetooth.bbclass file in the Yocto
- Project
- Source Directory.
-
-
-
buildhistory.bbclass
diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml
index b057d2d040..44ba67cf50 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -154,27 +154,6 @@
bluetooth: Include
bluetooth support (integrated BT only).
- bluez5: Include
- BlueZ Version 5, which provides core Bluetooth layers and
- protocols support.
-
- The default value for the
- DISTRO FEATURES variable includes
- "bluetooth", which causes bluez5 to be backfilled in
- for bluetooth support.
- If you do not want bluez5 backfilled and would rather
- use bluez4, you need to use the
- DISTRO_FEATURES_BACKFILL_CONSIDERED
- variable as follows:
-
- DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5"
-
- Setting this variable tells the OpenEmbedded build
- system that you have considered but ruled
- out using the bluez5 feature and that bluez4 will be
- used.
-
- cramfs: Include CramFS
support.directfb: