Skip to content

Commit 84d3fba

Browse files
mikemiles-devMichael Mileusnich
and
Michael Mileusnich
authored
chore: fix typos (#94)
Co-authored-by: Michael Mileusnich <[email protected]>
1 parent 9d6dea5 commit 84d3fba

File tree

5 files changed

+18
-17
lines changed

5 files changed

+18
-17
lines changed

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[package]
22
name = "netflow_parser"
33
description = "Parser for Netflow Cisco V5, V7, V9, IPFIX"
4-
version = "0.4.9"
4+
version = "0.5.0"
55
edition = "2021"
66
authors = ["[email protected]"]
77
license = "MIT OR Apache-2.0"

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
## Description
44

55
A Netflow Parser library for Cisco V5, V7, V9, IPFIX written in Rust.
6-
Supports chaining of multple versions in the same stream. ({v5 packet}, {v7packet}, {v5packet}, {v9packet}, etc.)
6+
Supports chaining of multiple versions in the same stream. ({v5 packet}, {v7 packet}, {v5 packet}, {v9 packet}, etc.)
77

88
## References
99
See: <https://en.wikipedia.org/wiki/NetFlow>
@@ -50,7 +50,7 @@ let v5_parsed: Vec<NetflowPacket> = parsed.into_iter().filter(|p| p.is_v5()).col
5050

5151
## Netflow Common
5252

53-
For convenience we have included a `NetflowCommon` and `NetflowCommonFlowSet` structure.
53+
We have included a `NetflowCommon` and `NetflowCommonFlowSet` structure.
5454
This will allow you to use common fields without unpacking values from specific versions.
5555
If the packet flow does not have the matching field it will simply be left as `None`.
5656

@@ -152,7 +152,7 @@ To access templates flowset of a processed V9/IPFix flowset you can find the `fl
152152

153153
## Included Examples
154154

155-
Some examples has been included mainly for those who want to use this parser to read from a Socket and parse netflow. In those cases with V9/IPFix it is best to create a new parser for each router. There are both single threaded and multi-threaded examples in the examples directory.
155+
Examples have been included mainly for those who want to use this parser to read from a Socket and parse netflow. In those cases with V9/IPFix it is best to create a new parser for each router. There are both single threaded and multi-threaded examples in the examples directory.
156156

157157
To run:
158158

RELEASES.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
# 0.5.0
2+
* Typos in documentation fixed.
3+
14
# 0.4.9
25
* Added FlowStartMilliseconds, FlowEndMilliseconds
36

@@ -34,7 +37,7 @@
3437

3538
# 0.4.0
3639
* NetflowPacketResult now simply NetflowPacket.
37-
* General parser cleanup and removal of uneeded code.
40+
* General parser cleanup and removal of unneeded code.
3841
* Small performance optimization in lib parse_bytes.
3942

4043
# 0.3.6
@@ -85,7 +88,7 @@
8588

8689
# 0.2.4
8790
* Fixes for V9 parsing. Now supports processing multiple templates.
88-
* General code cleanup/Removal of uneeded code.
91+
* General code cleanup/Removal of unneeded code.
8992

9093
# 0.2.3
9194
* Small performance improvement by not parsing netflow version twice each packet.

SECURITY.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@
33
## Supported Versions
44

55
| Version | Supported |
6-
| ------- | ------------------ |
6+
|---------| ------------------ |
7+
| 0.5.0 | :white_check_mark: |
78
| 0.4.9 | :white_check_mark: |
89
| 0.4.8 | :white_check_mark: |
910
| 0.4.7 | :white_check_mark: |
@@ -12,7 +13,4 @@
1213
| 0.4.4 | :white_check_mark: |
1314
| 0.4.3 | :white_check_mark: |
1415
| 0.4.2 | :white_check_mark: |
15-
| 0.4.1 | :white_check_mark: |
16-
| 0.4.0 | :white_check_mark: |
17-
| 0.3.6 | :white_check_mark: |
18-
| <0.3.6 | Not Supported |
16+
| <0.4.1 | Not Supported |

src/lib.rs

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
//! ## Description
44
//!
55
//! A Netflow Parser library for Cisco V5, V7, V9, IPFIX written in Rust.
6-
//! Supports chaining of multple versions in the same stream. ({v5 packet}, {v7packet}, {v5packet}, {v9packet}, etc.)
6+
//! Supports chaining of multiple versions in the same stream. ({v5 packet}, {v7 packet}, {v5 packet}, {v9 packet}, etc.)
77
//!
88
//! ## References
99
//! See: <https://en.wikipedia.org/wiki/NetFlow>
@@ -50,7 +50,7 @@
5050
//!
5151
//! ## Netflow Common
5252
//!
53-
//! For convenience we have included a `NetflowCommon` and `NetflowCommonFlowSet` structure.
53+
//! We have included a `NetflowCommon` and `NetflowCommonFlowSet` structure.
5454
//! This will allow you to use common fields without unpacking values from specific versions.
5555
//! If the packet flow does not have the matching field it will simply be left as `None`.
5656
//!
@@ -136,7 +136,7 @@
136136
//!
137137
//! ## V9/IPFix notes:
138138
//!
139-
//! Parse the data (`&[u8]` as any other versions. The parser (NetflowParser) holds onto already parsed templates, so you can just send a header/data flowset combo and it will use the cached templates.) To see cached templates simply use the parser for the correct version (v9_parser for v9, ipfix_parser for IPFix.)
139+
//! Parse the data (`&[u8]` as any other versions. The parser (NetflowParser) holds onto already parsed templates, so you can just send a header/data flowset combo, and it will use the cached templates.) To see cached templates simply use the parser for the correct version (v9_parser for v9, ipfix_parser for IPFix.)
140140
//! ```rust
141141
//! use netflow_parser::NetflowParser;
142142
//! let parser = NetflowParser::default();
@@ -150,7 +150,7 @@
150150
//! * `parse_unknown_fields` - When enabled fields not listed in this library will attempt to be parsed as a Vec of bytes and the field_number listed. When disabled an error is thrown when attempting to parse those fields. Enabled by default.
151151
//!
152152
//! ## Included Examples
153-
//! Some examples has been included mainly for those who want to use this parser to read from a Socket and parse netflow. In those cases with V9/IPFix it is best to create a new parser for each router. There are both single threaded and multi-threaded examples in the examples directory.
153+
//! Examples have been included mainly for those who want to use this parser to read from a Socket and parse netflow. In those cases with V9/IPFix it is best to create a new parser for each router. There are both single threaded and multithreaded examples in the examples directory.
154154
//!
155155
//! To run:
156156
//!
@@ -265,8 +265,8 @@ pub enum NetflowParseError {
265265
}
266266

267267
impl NetflowParser {
268-
/// Takes a Netflow packet slice and returns a vector of Parsed Netflows.
269-
/// If we reach some parse error we return what items be have.
268+
/// Takes a Netflow packet slice and returns a vector of Parsed Netflow.
269+
/// If we reach some parse error we return what items we have.
270270
///
271271
/// # Examples
272272
///

0 commit comments

Comments
 (0)