Update emergency publishing uncache comments

David Singleton · David Singleton · commit 55193bf2917d · 2015-12-14T14:42:21.000Z
To reflect the 3 layouts, and try and make the whole thing a bit
more readable.
diff --git a/campaigns.py b/campaigns.py
@@ -52,16 +52,15 @@ def template(app):
 
 def clear_static_generated_templates():
     """
-    Our various frontend applications use the wrapper.html.erb and
-    header_footer_only.html.erb templates. They get these templates
-    using the Slimmer gem. And this gem fetches these templates from
-    the static application, located using the ASSET_ROOT.
-
-    When static is deployed there are no generated wrapper.html.erb or
-    header_footer_only.html.erb templates. At the first request of
-    either of these, the application will generate the template. The
-    template will be placed in the public/template directory. From
-    that point on, the templates are served by nginx.
+    Our various frontend applications use the wrapper.html.erb,
+    header_footer_only.html.erb and core_layout.html.erb layout templates.
+    They get these templates using the Slimmer gem, which fetches
+    these templates from the static application, located using ASSET_ROOT.
+
+    When static is deployed there are no generated layout templates
+    on static At the first request to one these, static will generate
+    the template. The template will be placed in the public/template
+    directory. From that point on, the templates are served by nginx.
 
     This function clears the public/template directory to force it to
     be regenerated to include the emergency campaign.
