<commit_before><!DOCTYPE html>
<head>
  <title><NAME> Technical Blog</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>
<body>
  <main>
    <h1>Technical Blog</h1>
    <h2>The subtitle, if you want it</h2>
    <h4>Today's Date</h4>
  
    <section>
      <p>
        Your first paragraph goes here. I'm using Web 2.0 Ipsum to add content. Webtwo ipsum dolor sit amet, eskobo chumby doostang bebo. Nuvvo koofers oooooc voxy klout jaiku palantir flickr insala zinch napster oooj, airbnb mzinga vimeo yuntaa balihoo plickers whrrl edmodo appjet kippt. Yoono imvu hulu eduvant blekko imvu ebay voki napster skype, hipmunk zinch wesabe bubbli ning meebo bitly zlio. Fleck elgg ideeli disqus rovio zillow sifteo blyve jabber, bitly geni zoho foodzie qeyno twones klout jiglu, hipmunk jaiku balihoo plickers heekya eskobo yuntaa. Sococo whrrl plickers movity whrrl zinch voki nuvvo meebo, quora heroku unigo kno wufoo jibjab woopra, groupon yuntaa spock mzinga jumo meebo movity.
      </p>
      <p>
          Lijit groupon ning stypi eskobo blyve ning shopify oooooc, meebo groupon prezi ebay voxy bitly diigo. Spock ifttt skype hipmunk movity whrrl bebo oooj empressr, disqus insala palantir bitly dropio zimbra zinch oooooc etsy, klout spock insala quora omgpop trulia jibjab. Sifteo dogster ebay grockit geni scribd bitly ning unigo, plickers voki mzinga tumblr kaboodle mozy whrrl woopra udemy, foodzie joukuu elgg twitter shopify akismet rovio. Kosmix eduvant woopra dopplr balihoo ning bebo akismet, boxbe vimeo kosmix shopify zappos bitly geni loopt, qeyno disqus sococo squidoo wikia octopart.
      </p>
      <p>
          Kazaa meevee eduvant gsnap movity kosmix kazaa klout jumo, trulia unigo groupon wakoopa spock knewton glogster heroku oooj, ning imvu appjet eskobo zillow twitter rovio. Glogster chegg voxy greplin dopplr voki foodzie xobni weebly odeo, sococo zynga knewton loopt palantir lala blyve tumblr blekko, twones akismet plaxo kippt meebo zillow zooomr insala. Oovoo imeem napster divvyshot zinch imeem voxy shopify, fleck kazaa zinch lanyrd boxbe joost wakoopa nuvvo, orkut elgg heekya sifteo scribd napster. Yammer yoono groupon dopplr cloudera nuvvo eduvant klout, voxy groupon disqus eduvant oooj greplin.
      </p>
  
        <!-- copy and paste as many sections as you want to add paragraphs -->
      </section>
    </main>
  </body>
  </html><commit_msg>First blog post complete<commit_after><!DOCTYPE html>
<head>
  <title><NAME> Technical Blog</title>
  <meta charset="UTF-8">
  <link rel="stylesheet" type="text/css" href="your-stylesheet-link-here.css">
</head>
<body>
  <main>
    <h1>Technical Blog</h1>
    <h2>A blog, technically</h2>
    <h4>2/12/16</h4>
  
    <section>
      <p>
        Version control is an incredibly important aspect of coding, and any other technically creative endeavor. Since coding relies so heavily upon minute details and many small working parts, it necessitates a lot of tweaking and small additions and subtractions. Version control allows us to look at different save states of a given file and make small, incremental changes and then see the result. Without condensing changes into small groups, we'd either be left with a log of every single change (which would be overwhelming!) or no way to go back at all (which would be impossible). 
      </p>
      <p>
        Git helps the user keep track of these changes with a system of commits. Each commit is a save point where the latest grouping of changes is clumped together in a (hopefully) organized and well labelled manner. 
      </p>
      <p>
        GitHub is a great tool for version control and git. It offers a couple of useful features. The first is remote storage for all of your code. That means you can save it locally, as well as remotely, just in case something happens to your computer (lord knows it will). The second is a bit less simple, but just as helpful. GitHub acts as a centralized hub for multiple collaborators on any given file. That means you and I and all of our friends can simultaneously work on a project and submit our changes to a central file location. This way, we don't jumble it up or walk over each others' code, and we have an organized series of branches that we can keep clean and progressive. 
      </p>
  
        <!-- copy and paste as many sections as you want to add paragraphs -->
      </section>
    </main>
  </body>
  </html>
{'fraction_non_alphanumeric': 0.05988826815642458, 'fraction_numerical': 0.0046927374301675975, 'mean_word_length': 3.711578947368421, 'pattern_counts': {'":': 0, '<': 59, '<?xml version=': 0, '>': 59, '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': '4504751', 'n_tokens_mistral': 1517, 'n_tokens_neox': 1439, 'n_words': 639}