From 370453c7655208f6256a54355b2154935386a010 Mon Sep 17 00:00:00 2001
From: Stephane Nicoll <snicoll@pivotal.io>
Date: Wed, 15 Nov 2017 09:14:01 +0100
Subject: [PATCH] Fix reference to AutoConfigurationReportLoggingInitializer in
 docs

Closes gh-11026
---
 .../src/main/asciidoc/spring-boot-features.adoc               | 4 ++--
 .../spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
index f31f98b875..acdd8a7007 100644
--- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
+++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
@@ -74,10 +74,10 @@ NOTE: Spring Boot provides numerous `FailureAnalyzer` implementations, and you c
 <<howto.adoc#howto-failure-analyzer,add your own>>.
 
 If no failure analyzers are able to handle the exception, you can still display the full
-auto-configuration report to better understand what went wrong. To do so, you need to
+conditions report to better understand what went wrong. To do so, you need to
 <<boot-features-external-config,enable the `debug` property>> or
 <<boot-features-custom-log-levels,enable `DEBUG` logging>> for
-`org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer`.
+`org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener`.
 
 For instance, if you are running your application by using `java -jar`, you can enable
 the `debug` property as follows:
diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
index 7af96a31a8..ac29245982 100644
--- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
+++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
@@ -454,7 +454,7 @@ add your own `DataSource` bean, the default embedded database support backs away
 
 If you need to find out what auto-configuration is currently being applied, and why,
 start your application with the `--debug` switch. Doing so enables debug logs for a
-selection of core loggers and logs an auto-configuration report to the console.
+selection of core loggers and logs a conditions report to the console.