anchor.diff:                                         ipg_usec = ipg_usec, 
                                          loop_count = loop_count)
   ----
  -<1> The inter stream gap in usec
  -<2> How many times to loop
  -<3> The input pcap file 
  +<1> The inter-stream gap in microseconds.
  +<2> Loop count.
  +<3> Input pcap file. 
   
   image::images/stl_tut_pcap_file1.png[title="pcap file",align="left",width={p_width}, link="images/stl_tut_pcap_file1.png"]
   
  -This figure illustrates how the streams look like for pcap file with 3 packets.
  -* Each stream is configured to burst with one packet 
  -* Each stream point to the next stream. 
  -* The last stream point to the first with action_loop=loop_count in case it was asked (>1)
  -The profile will run on one DP thread because it has burst with one packet (Split can work in this case)
  -
  -Running this example
  +This figure the streams for a pcap file with 3 packets.
  +* Each stream is configured to Burst mode, with 1 packet 
  +* Each stream triggers the next stream. 
  +* The last stream triggers the first with `action_loop=loop_count` if `loop_count` > 1.
  +The profile runs on one DP thread because it has a burst with 1 packet. (Split cannot work in this case).
  +
  +To run this example:
   
   [source,bash]
   ----
   ./stl-sim -f stl/pcap.py --yaml
   ----
   
  -will give this
  +The following output appears:
   
   [source,python]
   ----
  
positive.code:                  **kwargs)
  ----
  
  This profile gets 'direction' as a tunable and mandatory field.
  Define 4 more tunables which the profile decided about,
  And automatic values such as 'port_id' which are not tunables will be provided on kwargs.
  
  *Direction*::
  Direction is a tunable that will always be provided by the API/console when loading
  a profile, but it can be overriden by the user.
  It is used to make the traffic profile more usable such as bi-directional profile.
  However, a profile is free to ignore this parameter.
  
  As default 'direction' will be equal to port_id % 2, so the *even* ports will be
  provided with ''0'' and the *odd* ones with ''1''.
  
  [source,python]
  ----
  
negative.code: 
  ===== streams
  
  Shows the configured streams on each port, from the client cache. 
  // clarify "should"
  
  *Example*::
  
  [source,bash]
  ----
  