Fix formatting of code in API docs (#4771)

Polymer · Aug 4, 2017 · eb406c7 · eb406c7
1 parent 06c6ea0
commit eb406c7
Showing 1 changed file with 9 additions and 9 deletions.
diff --git a/lib/mixins/property-effects.html b/lib/mixins/property-effects.html
@@ -2093,15 +2093,15 @@
        * roughly corresponds to a phase in effect processing.  The effect
        * metadata should be in the following form:
        *
-       *   {
-       *     fn: effectFunction, // Reference to function to call to perform effect
-       *     info: { ... }       // Effect metadata passed to function
-       *     trigger: {          // Optional triggering metadata; if not provided
-       *       name: string      // the property is treated as a wildcard
-       *       structured: boolean
-       *       wildcard: boolean
+       *     {
+       *       fn: effectFunction, // Reference to function to call to perform effect
+       *       info: { ... }       // Effect metadata passed to function
+       *       trigger: {          // Optional triggering metadata; if not provided
+       *         name: string      // the property is treated as a wildcard
+       *         structured: boolean
+       *         wildcard: boolean
+       *       }
        *     }
-       *   }
        *
        * Effects are called from `_propertiesChanged` in the following order by
        * type:
@@ -2114,7 +2114,7 @@
        *
        * Effect functions are called with the following signature:
        *
-       *   effectFunction(inst, path, props, oldProps, info, hasPaths)
+       *     effectFunction(inst, path, props, oldProps, info, hasPaths)
        *
        * @param {string} property Property that should trigger the effect
        * @param {string} type Effect type, from this.PROPERTY_EFFECT_TYPES