"haproxy" process referenced in example no longer part of release.

[kimago]

cf-onboarding/bosh_troubleshooting.prolific

Line 133 in 0f3bce8

1. Find the spec file for the job on Github. A spec file resides at `some-release/jobs/some-job-name/spec`. For instance, the spec path of the cf-release haproxy job is `https://github.com/cloudfoundry/cf-release/blob/master/jobs/haproxy/spec`.

Tracker story "Update your BOSH deployment's properties (a.k.a. let's break some stuff)" reads:

Choose a spec property where you expect to be able to tell if the value changes. An example in haproxy might be cc.allow_app_ssh_access (read the property description in the spec to learn more).

That haproxy process is no longer part of release we're told -- it should be updated with something both "real" and also "easily traceable WRT impact of messing with it". (Note this is a tough story for us n00bs, so a solid example here is very helpful.)