<commit_before><nav class="navbar navbar-default navbar-fixed-top" role="navigation">
    <div class="container">
        <div class="navbar-header">
            <a class="navbar-brand" href="/">WaterTOS</a>
        </div>
        {{#user}}
        <div id="navbar-loggedin" class="navbar-collapse collapse">
            <ul class="nav navbar-nav navbar-right">
                <li><a>{{_id}}</a></li>
                <li><a href="/logout">Logout</a></li>
            </ul>
        </div>
        {{/user}}
        {{^user}}
        <div id="navbar" class="navbar-collapse collapse">
            <ul class="nav navbar-nav navbar-right">
                <li><a href="/login">Login</a></li>
                <li><a href="/register">Register</a></li>
            </ul>
        </div>
        {{/user}}
    </div>
</nav>
<div class="container">
    {{#message}}
    <div class="alert alert-info alert-dismissible" role="alert">
        <button type="button" class="close" data-dismiss="alert"><span aria-hidden="true">&times;</span><span class="sr-only">Close</span></button>
        {{& message }}
    </div>
    {{/message}}
    <div class="page-header">
        <h1>About WaterTOS</h1>
    </div>
    <p>WaterTOS is a project that aims to simplify TOS documents and portray them in a creative way. We aim to make the arduous task of reading TOS documents flow like water, and in turn, fix the ignorance of legal documents</p>
    <h2>Background</h2>
    <p>Something will go here later</p>
    <h2>Why "WaterTOS"</h2>
    <p>We aim to make reading TOS documents "flow like water" and make them as transparent as possible. In all honesty, it was an accident. That story's for another time.</p>
    <h2>How does it work?</h2>
    <p>Our home-built bot crawls websites for their TOS documents on request. The service uses publicly available APIs to summarize the legal documents pulled and parse them into an easily readable format. In order to speed up the service as much as possible, we use a cache to keep commonly referenced TOS documents on file.</p>
    <p>A list of APIs we used:</p>
    <p>TODO:List APIs her</p>
</div>
<div class="text-center">
    <a href="/about"><small>About</small></a>
    <small> | </small>
    <a href="/legal"><small>Legal</small></a>
    <small> | </small>
    <small>2014 TeamShog</small>
</div><commit_msg>Update about.html<commit_after><nav class="navbar navbar-default navbar-fixed-top" role="navigation">
    <div class="container">
        <div class="navbar-header">
            <a class="navbar-brand" href="/">WaterTOS</a>
        </div>
        {{#user}}
        <div id="navbar-loggedin" class="navbar-collapse collapse">
            <ul class="nav navbar-nav navbar-right">
                <li><a>{{_id}}</a></li>
                <li><a href="/logout">Logout</a></li>
            </ul>
        </div>
        {{/user}}
        {{^user}}
        <div id="navbar" class="navbar-collapse collapse">
            <ul class="nav navbar-nav navbar-right">
                <li><a href="/login">Login</a></li>
                <li><a href="/register">Register</a></li>
            </ul>
        </div>
        {{/user}}
    </div>
</nav>
<div class="container">
    {{#message}}
    <div class="alert alert-info alert-dismissible" role="alert">
        <button type="button" class="close" data-dismiss="alert"><span aria-hidden="true">&times;</span><span class="sr-only">Close</span></button>
        {{& message }}
    </div>
    {{/message}}
    <div class="page-header">
        <h1>About WaterTOS</h1>
    </div>
    <p>WaterTOS is a project that aims to simplify TOS documents and portray them in a creative way. We aim to make the arduous task of reading TOS documents flow like water, and in turn, fix the ignorance of legal documents</p>
    <h2>Why "WaterTOS"?</h2>
    <p>We aim to make reading TOS documents "flow like water" and make them as transparent as possible. In all honesty, it was an accident. That story's for another time.</p>
    <h2>How does it work?</h2>
    <p>Our home-built bot crawls websites for their TOS documents on request. The service uses publicly available APIs to summarize the legal documents pulled and parse them into an easily readable format. In order to speed up the service as much as possible, we use a cache to keep commonly referenced TOS documents on file.</p>
    <h2>Tools we used</h2>
    <ul>
        <li>Google Search API</li>
        <li>Alyien API</li>
        <li>PHP</li>
        <li>Apache2</li>
        <li>Mustache Templates</li>
        <li></li>
    </ul>
</div>
<div class="text-center">
    <a href="/about"><small>About</small></a>
    <small> | </small>
    <a href="/legal"><small>Legal</small></a>
    <small> | </small>
    <small>2014 TeamShog</small>
</div>
{'fraction_non_alphanumeric': 0.16040310728532436, 'fraction_numerical': 0.005248792777661138, 'mean_word_length': 2.6844547563805103, 'pattern_counts': {'":': 0, '<': 171, '<?xml version=': 0, '>': 171, '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': '6133697', 'n_tokens_mistral': 1502, 'n_tokens_neox': 1444, 'n_words': 452}