Following points should be addressed:

• "Download the Code" and "Getting Started" sections: These could be more prominent/obvious in the VSperf OPNFV Wiki homepage.
• Downloading VSperf involves running the "git clone" command on a modified
  version of a gerrit link about half way down the VSperf homepage under the
  "Gerrit and Documentation" heading.
• VSperf documentation should mention how to actually obtain the code in the
  Installation Guide, towards the start. The only mention of this currently is the
  "Project Repository" link, which is a Gerrit link which, again, must be
  modified to download the code.
• Provide a clear reasoning behind the use of the "virtual environment" which is
  required to run VSperf. This is not necessary for other projects so if this is
  mandatory then provide statements in the documentation as to why it's needed
  and what it does.
• README file points to "docs/quickstart.md" which doesn't exist. Maybe this
  should point to "docs/configguide/installation.rst" instead?
• pre-installed_flows is supported only by p2p deployment scenario
• dummy trafficgen docs to be checked (if any) and enhanced to pinpoint enforcement of simulated values via --test-params
• check permissions of DOC files (recommended is 644/rw-rr-)