minor edits

slf4j-api/src/main/java/org/slf4j/helpers/SubstituteLogger.java

@@ -47,11 +47,11 @@ import org.slf4j.event.SubstituteLoggingEvent;
 public class SubstituteLogger implements Logger {
 
     private final String name;
-
     private volatile Logger _delegate;
+    private Boolean delegateEventAware;
+    private Method logMethodCache;
     private EventRecodingLogger eventRecodingLogger;
-    
+    private List<SubstituteLoggingEvent> eventList;
-    List<SubstituteLoggingEvent> eventList;
 
     public SubstituteLogger(String name, List<SubstituteLoggingEvent> eventList) {
         this.name = name;
@@ -346,9 +346,6 @@ public class SubstituteLogger implements Logger {
         this._delegate = delegate;
     }
 
-    Boolean delegateEventAware;
-    Method logMethodCache;
-
     public boolean isDelegateEventAware() {
         if (delegateEventAware != null)
             return delegateEventAware;

slf4j-site/src/site/pages/codes.html

@@ -428,25 +428,29 @@ class B extends A {
     previously listed item.
     </p>
 
-    <!-- ====================================================== -->
   
-    <h3 class="doAnchor" name="log4j_version">SLF4J versions 1.4.0 and
-    later requires log4j 1.2.12 or later</h3>
     
-    <p>The trace level was added to log4j in version 1.2.12 released
+   <!-- ====================================================== -->
-    on August 29, 2005. The trace level was added to the SLF4J API in
+
-    version 1.4.0 on May 16th, 2007. Thus, starting with SLF4J 1.4.0,
+    <h3 class="doAnchor" name="replay">A number (N) of logging calls
-    the log4j binding for SLF4J requires log4j version 1.2.12 or
+    during the initialization phase have been intercepted and are now
-    above.
+    being replayed. These are suject to the filtering rules of the
+    underlying logging system.
+    </h3>
+
+    <p><span class="label">since 1.7.15</span> Logging calls made
+    during the initilization phase are recorded and replayed
+    post-inititilization. Note that the replayed logging calls are
+    subject to filtering by the underlying logging system.</p>
+
+    <p>In principle, replaying only occurs for apllications which are
+    already multi-threaded at the time the first logging call occurs.
     </p>
 
-    <p>However, as reported in <a
+    <p>See also <a
-    href="http://jira.qos.ch/browse/SLF4J-59">issue 59</a>, in some
+    href="#substituteLogger">substitute loggers</a>.</p>
-    environments it may be difficult to upgrade the log4j version. To
-    accommodate such circumstances, SLF4J's
-    <code>Log4jLoggerAdapter</code> will map the TRACE level as
-    DEBUG.</p>
  
+    <!-- ====================================================== -->
 
     <h3 class="doAnchor" name="substituteLogger" >Substitute loggers
     were created during the default configuration phase of the
@@ -476,23 +480,27 @@ class B extends A {
     have been dropped.
     </p>
 
-    <h3 class="doAnchor" name="reply">A number (N) of logging calls
+    <p>See also <a href="#replay">intercepted and replayed logging
-    during the initialization phase have been intercepted and are now
+    calls</a>.</p>
-    being replayed. These are suject to the filtering rules of the
-    underlying logging system.
-    </h3>
   
-    <p><span class="label">since 1.7.15</span> As of SLF4J version
+    <!-- ====================================================== -->
-    1.7.15, logging calls made during the initilization phase are
-    recorded and replayed post-inititilization.</p>
 
-    <p>These replayed logging calls are subject to filtering by the
+    <h3 class="doAnchor" name="log4j_version">SLF4J versions 1.4.0 and
-    underlying logging system.</p>
+    later requires log4j 1.2.12 or later</h3>
 
-    <p>Replaying only occurs for apllications which are already
+    <p>The trace level was added to log4j in version 1.2.12 released
-    multi-threaded when the first logging call occurs.
+    on August 29, 2005. The trace level was added to the SLF4J API in
+    version 1.4.0 on May 16th, 2007. Thus, starting with SLF4J 1.4.0,
+    the log4j binding for SLF4J requires log4j version 1.2.12 or
+    above.
     </p>
 
+    <p>However, as reported in <a
+    href="http://jira.qos.ch/browse/SLF4J-59">issue 59</a>, in some
+    environments it may be difficult to upgrade the log4j version. To
+    accommodate such circumstances, SLF4J's
+    <code>Log4jLoggerAdapter</code> will map the TRACE level as
+    DEBUG.</p>
 
     <script src="templates/footer.js" type="text/javascript"></script>
   </div>

slf4j-site/src/site/pages/news.html

@@ -27,9 +27,23 @@
    announce</a> mailing list.
    </p>
 
+
    <hr noshade="noshade" size="1"/>
 
-   <h3>24th January, 2016 - Release of SLF4J 1.7.14</h3>
+   <h3>9th of February, 2016 - Release of SLF4J 1.7.15</h3>
+
+   <p>In previous versions of SLF4J, if the application was already
+   multi-threaded at the time the first SLF4J logger was created, logs
+   made during the SLF4J initialization phase were lost. New code
+   added in relation with <a
+   href="http://jira.qos.ch/browse/SLF4J-353">SLF4J-353</a> fixes this
+   problem by storing and replaying logging calls made during
+   initialization.
+   </p>
+
+   <hr noshade="noshade" size="1"/>
+
+   <h3>24th of January, 2016 - Release of SLF4J 1.7.14</h3>
 
    <p>The assignment of the INITIALIZATION_STATE variable in
    <code>LoggerFactory</code> is now guaranteed to be consistent for