README.md in packet_via_dmem-0.0.5 vs README.md in packet_via_dmem-0.0.6

@@ -12,18 +12,18 @@
     MX104-ABB-0(test2nqe31-re1.dk vty)# test jnh 0 packet-via-dmem capture 0x3 0x0a0b0c0d
     MX104-ABB-0(test2nqe31-re1.dk vty)# test jnh 0 packet-via-dmem capture 0x0
     MX104-ABB-0(test2nqe31-re1.dk vty)# test jnh 0 packet-via-dmem dump
     MX104-ABB-0(test2nqe31-re1.dk vty)# test jnh 0 packet-via-dmem disable
 
+## Install
+    % gem install packet_via_dmem
 
 ## CLI
-    % ./bin/packet-via-dmem  -s 1 ~/output.txt|wc -l
+    % ./bin/packet-via-dmem --both ~/output.txt|grep Packet|wc -l
     55
-    % ./bin/packet-via-dmem ~/output.txt |wc -l
+    % ./bin/packet-via-dmem ~/output.txt|grep Packet|wc -l
     28
-    % ./bin/packet-via-dmem -r 0 ~/output.txt |wc -l
-    0
     % ./bin/packet-via-dmem ~/output.txt|text2pcap - output.pcap
     Input from: Standard input
     Output to: output.pcap
     Output format: PCAP
     Wrote packet of 66 bytes.
@@ -97,10 +97,10 @@
   * Sixth byte is perhaps source NPU? If it is zero, we get what seems to be trash (internal stuff)
 
   * value of fift+sixth seems to sometime indicate special cases
     * 0x1fff - Packet missing everything before IPv4 TTL, yet has some extra. I saw BGP from control-plane with this and also TCP/SMB2 with Seq1, it was transit, but perhaps it was via ARP resolve/punt and thus coming from control-plane?
     * 0x2000 - BFD frames from control-plane, missing L2
-    * 0x4220 - Was traffic for AE/802.1AX, no L2 included, but something extra aadded
+    * 0x4220 - Was traffic for AE/802.1AX, missing ethertype, MACs changed, 2 mystery bytes
     * 0x8000 - I need to pop 14 bytes extra
 
   * 00 (22) (33) (44) \<src\> (66)
   * 10 (22) (33) (44) \<si\> \<ze\> \<src\> (66)