Remove the warning about soysauce being 'extremely experimental', it isn't.  Also point at PrecompiledSoyModule which is what most people should be using.
@@ -816,14 +816,14 @@ public final class SoyFileSet {
}
/**
- * This is an <em>extremely experimental API</em> and subject to change. Not all features of soy
- * are implemented in this new backend and the features that are implemented are not necessarily
- * correct!
+ * Compiles this Soy file set into a set of java classes implementing the {@link SoySauce}
+ * interface.
*
- * <p>See com/google/template/soy/jbcsrc/README.md for background on this new backend.
- *
- * <p>Compiles this Soy file set into a set of java classes implementing the {@link
- * CompiledTemplate} interface.
+ * <p>This is useful for implementing 'edit refresh' workflows. Most production usecases should
+ * use the command line interface to 'ahead of time' compile templates to jar files and then use
+ * {@code PrecompiledSoyModule} to get access to a {@link SoySauce} object without invoking the
+ * compiler. This will allow applications to avoid invoking the soy compiler at runtime which can
+ * be relatively slow.
*
* @return A set of compiled templates
* @throws SoyCompilationException If compilation fails.
