Index: INSTALL.txt
===================================================================
--- INSTALL.txt	(revision 26c9b85eb05ac83c648348fc7879e08e3225ceb1)
+++ INSTALL.txt	(revision e40390eea0e5248ec96d6aba2baab577a7120218)
@@ -47,5 +47,5 @@
 More information can be found here:
 
-http://www.sasview.org/help.html
-http://www.sasview.org/faq.html
+http://www.sasview.org/help/
+http://www.sasview.org/faq/
 http://www.sasview.org/trac/wiki/DevNotes
Index: docs/sphinx-docs/source/user/RELEASE.rst
===================================================================
--- docs/sphinx-docs/source/user/RELEASE.rst	(revision 8514f8955871de6ea7af23297d51f3e052aa3fdf)
+++ docs/sphinx-docs/source/user/RELEASE.rst	(revision 2c355a2b0901cbb32a7d373dc64cef6a65c4aa7f)
@@ -156,5 +156,5 @@
 * Fixes # 784: Add 3D integral to Correlation Function analysis
 * Fixes # 786: core_shell_parallelepiped 1-D model is incorrect
-* Fixes # 818: âreport buttonâ followed by âsaveâ makes an empty pdf file???
+* Fixes # 818: "report button" followed by "save" makes an empty pdf file???
 * Fixes # 830: Check compliance of loader against NXcanSAS-1.0 release
 * Fixes # 838: Fix model download from marketplace
@@ -770,5 +770,7 @@
           that any previous versions of SasView are uninstalled prior to 
           installing the new version UNLESS you are installing SasView to 
-          versioned folders.
+          versioned folders. **We recommend you avoid using folder paths 
+          that contain spaces or characters that cannot be found on a 
+          standard keyboard (eg, characters with accents, umlauts, etc).**
 
 .. note:: The easiest approach to setting up the proper environment to
@@ -965,5 +967,5 @@
 Frequently Asked Questions
 ==========================
-http://www.sasview.org/faq.html
+http://www.sasview.org/faq/
 
 
Index: src/sas/sasgui/perspectives/fitting/media/fitting.rst
===================================================================
--- src/sas/sasgui/perspectives/fitting/media/fitting.rst	(revision c926a9787e05478bd241a391873fc259e32825d6)
+++ src/sas/sasgui/perspectives/fitting/media/fitting.rst	(revision 332c10d1c6175b2c32df6a23f58184feaef866d8)
@@ -17,6 +17,10 @@
    Smearing Functions <resolution>
 
+   Fitting Models with Structure Factors <fitting_sq>
+
+   Writing a Plugin Model <plugin>
+
    Polarisation/Magnetic Scattering <magnetism/magnetism>
-   
+
    Oriented Particles <orientation/orientation>
 
@@ -27,6 +31,4 @@
    Fitting SESANS Data <sesans/sesans_fitting>
 
-   Writing a Plugin Model <plugin>
-
    Computations with a GPU <gpu_setup>
 
Index: src/sas/sasgui/perspectives/fitting/media/fitting_help.rst
===================================================================
--- src/sas/sasgui/perspectives/fitting/media/fitting_help.rst	(revision 8b893964adb6b330d7638d1e9692c0aacf81a9b6)
+++ src/sas/sasgui/perspectives/fitting/media/fitting_help.rst	(revision b7ce5ad13cff1bb692e5cac14d5eeb68461dd835)
@@ -338,4 +338,36 @@
 These optimisers form the *Bumps* package written by P Kienzle. For more information
 on each optimiser, see the :ref:`Fitting_Documentation`.
+
+.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
+
+Fitting Integer Parameters
+--------------------------
+
+Most of the parameters in SasView models will naturally take floating point (decimal) 
+values, but there are some parameters which can only have integer values. Examples 
+include, but are not limited to, the number of shells in a multilayer vesicle, the 
+number of beads in a pearl necklace, the number of arms of a star polymer, and so on.
+Wherever possible/recognised, the integer nature of a parameter is specified in the 
+respective model documentation and/or parameter table, so read the documentation 
+carefully!
+
+Integer parameters must be fitted with care.
+
+Start with your best possible guess for the value of the parameter. And using 
+*a priori* knowledge, fix as many of the other parameters as possible.
+ 
+The SasView optimizers treat integer parameters internally as floating point 
+numbers, but the values presented to the user are truncated or rounded, as 
+appropriate.
+
+In most instances integer parameters will probably be greater than zero. A good 
+policy in such cases is to use a constraint to enforce this.
+
+Because an integer parameter should, by definition, only move in integer steps, 
+problems may be encountered if the optimizer step size is too small. Similarly, 
+be **very careful** about applying polydispersity to integer parameters.
+
+The Levenberg-Marquardt and Quasi-Newton BFGS (and other derivative-based) 
+optimizers are probably best avoided for fitting models with integer parameters.
 
 .. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
Index: src/sas/sasgui/perspectives/fitting/media/fitting_sq.rst
===================================================================
--- src/sas/sasgui/perspectives/fitting/media/fitting_sq.rst	(revision 332c10d1c6175b2c32df6a23f58184feaef866d8)
+++ src/sas/sasgui/perspectives/fitting/media/fitting_sq.rst	(revision 332c10d1c6175b2c32df6a23f58184feaef866d8)
@@ -0,0 +1,69 @@
+.. fitting_sq.rst
+
+.. Much of the following text was scraped from product.py
+
+.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
+
+.. _Product Models:
+
+Fitting Models with Structure Factors
+-------------------------------------
+
+.. note::
+
+   This help document is under development
+
+*Product models*, $P@S$ models for short, multiply the structure factor $S(q)$ by
+the form factor $P(q)$, modulated by the *effective radius* of the form factor.
+
+Many of the parameters in $P@S$ models take on specific meanings so that they
+can be handled correctly inside SasView:
+
+* *scale*:
+
+  The *scale* for $P@S$ models should usually be set to 1.0.
+
+* *volfraction*:
+
+  For hollow shapes, *volfraction* represents the volume fraction of
+  material but the $S(q)$ calculation needs the volume fraction *enclosed by*
+  *the shape.* SasView scales the user-specified volume fraction by the ratio
+  form:shell computed from the average form volume and average shell volume
+  returned from the $P(q)$ calculation (the original *volfraction* is divided
+  by *shell_volume* to compute the number density, and then $P@S$ is scaled
+  by that to get the absolute scaling on the final $I(q)$).
+
+* *radius_effective*:
+
+  If part of the $S(q)$ calculation, the value of *radius_effective* may be
+  polydisperse. If it is calculated by $P(q)$, then it will be the weighted
+  average of the effective radii computed for the polydisperse shape
+  parameters.
+
+* *structure_factor_mode*:
+
+  If the $P@S$ model supports the $\beta(q)$ *correction* [1] then
+  *structure_factor_mode* will appear in the parameter table after the $S(q)$
+  parameters. This mode may be 0 for the local monodisperse approximation:
+
+    $I = (scale / volume)$ x $P$ x $S + background$
+
+    or 1 for the beta correction:
+
+    $I = (scale$ x $volfraction / volume)$ x $( <FF>$ + $<F>^2 (S-1) ) + background$
+
+    where $F$
+
+  More options may appear here in future as more complicated operations are
+  added.
+
+References
+^^^^^^^^^^
+
+.. [#] Kotlarchyk, M.; Chen, S.-H. *J. Chem. Phys.*, 1983, 79, 2461
+
+.. ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
+
+*Document History*
+
+| 2019-03-29 Paul Kienzle & Steve King
