<commit_before># RFC Links

Select text containing "RFC" + 1-4 numbers, and get a context menu to the
[IETF](http://ietf.org/)'s HTML version of the RFC.

Neat, huh?!<commit_msg>Add testing text to the README<commit_after># RFC Links

Select text containing "RFC" + 1-4 numbers, and get a context menu to the
[IETF](http://ietf.org/)'s HTML version of the RFC.

Neat, huh?!

My personal favorites (right now) are RFC2068 (HTTP/1.1 "beta"), RFC2616 (the
out of date HTTP spec), RFC 7231 (one of the 6 RFC2616 "upgrades"), and RFC3986
(the URI spec).

WHY U NO LINK THOZ?! :trollface:

'cause this is a test case. :smile_cat:
{'fraction_non_alphanumeric': 0.1187800963081862, 'fraction_numerical': 0.04333868378812199, 'mean_word_length': 4.243697478991597, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4343477', 'n_tokens_mistral': 249, 'n_tokens_neox': 220, 'n_words': 94}