Description of problem:

In the example ptpconfig boundary-ha, https://docs.openshift.com/container-platform/4.16/networking/ptp/configuring-ptp.html#ptp-configuring-linuxptp-services-as-ha-bc-for-dual-nic_configuring-ptp 

apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: boundary-ha
  namespace: openshift-ptp
  annotations:
    ran.openshift.io/ztp-deploy-wave: "10"
spec:
  profile:
    - name: "boundary-ha"
      ptp4lOpts: " "
      phc2sysOpts: "-a -r -n 24"
      ptpSchedulingPolicy: SCHED_FIFO
      ptpSchedulingPriority: 10
      ptpSettings:
        logReduce: "true"
        haProfiles: "ha-ptp-config-nic1,ha-ptp-config-nic2"
  recommend:
    - profile: "boundary-ha"
      priority: 4
      match:
        - nodeLabel: "node-role.kubernetes.io/$mcp"

1. There is a space in ptp4lOpts: " ", this will make p4ptl start on HA profile which will cause an critical error during ptp4l process startup but it should not and no interface is defined in the HA profile.
2. haProfiles: (confusing) actually it is the ptpconfig name(metadata.name) not the profile name. 
3. It is important that recommend[].priority shall be the same for all individual NIC ptpconfig and HA ptpconfig.
4. phc2SysOpts must be set in the HA ptpconfig and but set "" in the NICs ptpConfig
5. Might be good to explain the major parameters in the doc as well.

Version-Release number of selected component (if applicable):

PTP operator: 4.16.z

How reproducible:

Always

Steps to Reproduce:

1. Enable PTP dual NIC boundary clock
2. Enable HA by follow doc above

Actual results:

Different issues will happen due to misleading and missed information in the doc

Expected results:

Doc is clear and easy to follow

Additional info: