chore: fixup typos

Signed-off-by: Leonardo Di Donato <[email protected]>

Author: leodido

rfc3164/README.md

@@ -4,7 +4,7 @@ This package implements a parser for RFC3164 (BSD syslog) messages with extensio
 
 ## Overview
 
-RFC3164 is the original syslog protocol specification, commonly known as BSD syslog. Unlike [RFC5424](/rfc5424), RFC3164 has a loosely defined format, making it challenging to parse reliably. This parser handles the standard format plus common variations.
+RFC3164 is the original syslog protocol specification, commonly known as BSD syslog. Unlike [RFC5424](../rfc5424), RFC3164 has a loosely defined format, making it challenging to parse reliably. This parser handles the standard format plus common variations.
 
 ## Standard RFC3164 Format
 
@@ -33,9 +33,10 @@ if err != nil {
 }
 
 // Access parsed fields
-fmt.Printf("Priority: %d\n", *msg.(*SyslogMessage).Priority)
-fmt.Printf("Hostname: %s\n", *msg.(*SyslogMessage).Hostname)
-fmt.Printf("Message: %s\n", *msg.(*SyslogMessage).Message)
+m := msg.(*rfc3164.SyslogMessage)
+fmt.Printf("Priority: %d\n", *m.Priority)
+fmt.Printf("Hostname: %s\n", *m.Hostname)
+fmt.Printf("Message: %s\n", *m.Message)
 ```
 
 ## Parser Options

rfc3164/example_test.go

@@ -328,7 +328,7 @@ func ExampleParser_ciscoIOSLeadingColon() {
 // due to a mismatch between the device configuration and the parser configuration.
 //
 // The error message "expecting a sequence number" actually means:
-// "I see digits that look like a sequence number, but you haven't enabled sequence number parsin. You need to configure the parser to handle this".
+// "I see digits that look like a sequence number, but you haven't enabled sequence number parsing. You need to configure the parser to handle this".
 func ExampleParser_ciscoIOSConfigMismatch() {
 	// Device configured with both message counter and sequence number
 	i := []byte(`<189>237: 000485: *Jan  8 19:46:03.295: %SYS-5-CONFIG_I: Configured from console`)

rfc3164/machine_test.go

@@ -359,11 +359,7 @@ var testCases = []testCase{
 		// device sends msgcount+sequence, parser expects only msgcount.
 		// Parser successfully parses msgcount (269614),
 		// then fails at col 13 when it sees another number (000104) instead of timestamp.
-		//
-		// This demonstrates a known limitation: the parser cannot auto-detect which
-		// Cisco components are present because they all follow the pattern "digits/alphanum:".
-		// Users must configure the parser flags to match their Cisco device configuration.
-		// Mismatched configuration will result in parsing errors or incorrect field values.
+		// Demonstrates the known limitation that parser cannot auto-detect components.
 		opts: []syslog.MachineOption{
 			WithCiscoIOSComponents(ciscoios.DisableSequenceNumber | ciscoios.DisableHostname),
 		},