Particles module doc fixes

Fixing some uses of qdoc commands and other minor fixes

Change-Id: I965f715ad8d7833c5a7b830d644c79ad51735da5
Reviewed-by: Alan Alpert <alan.alpert@nokia.com>

1 files changed, 5 insertions, 4 deletions

diff --git a/src/particles/qquickparticleaffector.cpp b/src/particles/qquickparticleaffector.cpp
index 0ad00cebc3..29f88fb5f8 100644
--- a/src/particles/qquickparticleaffector.cpp
+++ b/src/particles/qquickparticleaffector.cpp
@@ -122,11 +122,12 @@ QT_BEGIN_NAMESPACE
 
     In the special case where an Affector has no possible effect (e.g. Affector {}), affected
     will be emitted for all particles being considered if you connect to it. This allows you to
-    execute arbitrary code in response to particles (see \l affectParticles if you want to execute
-    code which affects the particles themselves) . As this executes JS scritps per particle, it is
-    not recommended to use this signal with a high-volume particle system.
+    execute arbitrary code in response to particles (use the \l {QtQuick.Particles2::Affector::affectParticles}
+    {affectParticles} signal handler if you want to execute code which affects the particles
+    themselves). As this executes JavaScript code per particle, it is not recommended to use this
+    signal with a high-volume particle system.
 
-    x,y is the particles current position.
+    x,y is the particle's current position.
 */
 QQuickParticleAffector::QQuickParticleAffector(QQuickItem *parent) :
     QQuickItem(parent), m_needsReset(false), m_ignoresTime(false), m_onceOff(false), m_enabled(true)