Clarify advanced gst-launch example in README

README.md

@@ -25,17 +25,17 @@ $ gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! \
    nvvidconv flip-method=0 ! 'video/x-raw,width=960, height=720' ! \
    nvvidconv ! nvegltransform ! nveglglessink -e
 
-<em><b>Note: </b>The cameras appear to report differently than show below on some Jetsons. For example:
-GST_ARGUS: Available Sensor modes :
-GST_ARGUS: 3264 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;
+Note: The cameras appear to report differently than show below on some Jetsons. You can use the simple gst-launch example above to determine the camera modes that are reported by the sensor you are using. As an example the same camera from below may report differently on a Jetson Nano B01:
 
-You should adjust accordingly, ie for 3264x2464 @ 21 fps on sensor_id 1 of a Jetson Nano B01:
+GST_ARGUS: 3264 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000 
+
+You should adjust accordingly. As an example, for 3264x2464 @ 21 fps on sensor_id 1 of a Jetson Nano B01:
 $ gst-launch-1.0 nvarguscamerasrc sensor_id=1 ! \
    'video/x-raw(memory:NVMM),width=3264, height=2464, framerate=21/1, format=NV12' ! \
-   nvvidconv flip-method=0 ! 'video/x-raw,width=816, height=616' ! \
-   nvvidconv ! nvegltransform ! nveglglessink -e</em>
-
+   nvvidconv flip-method=0 ! 'video/x-raw, width=816, height=616' ! \
+   nvvidconv ! nvegltransform ! nveglglessink -e
 
+Also, it's been noticed that the display transform is sensitive to width and height (in the above example, width=816, height=616). If you experience issues, check to see if your display width and height is the same ratio as the camera frame size selected (In the above example, 816x616 is 1/4 the size of 3264x2464).
 ```
 
 There are several examples: