         
         <p>When displaying the rating in tables, it is rounded to integers, but when calculating everything is considered real numbers.</p>
         
-        <p>Cost plate (rounded to two decimal places):</p>
-        <pre>          A B C D
+        <p>Cost table (rounded to two decimal places):</p>
+        <pre>          A            B        C         D
          1       2.50       3.14       3.95       4.97
          2       6.25       7.86       9.88
          3      15.62      19.65      24.71      31.07

    page(
        "About the \"Find a bug\" section", 
                                          String.raw"""<h1>About the "Find a bug" section</h1>
        <p>When you have passed the solution to the problem and received an "Accepted" for it, you have the opportunity to look for bugs in the decisions of other students on this problem. Namely, a link "Find an bug" appears on the task page, which opens a list of specially selected incorrect solutions to this problem.
        (Of course, the link does not appear in every task, but only in those tasks where there are such specially selected solutions.)
        There is also a section in the site menu "<a href="/findMistakeList">Find the bug</a>", where there are links to all solutions in which you can look for errors
        (not all of these solutions are available to you — solutions are available to you only for those tasks for which you received a "Accepted").</p>

        <p>About each of the solutions in which you need to find an error, it is known that the error can be corrected by making no more than 15 edits in the solution code. An edit is considered to be adding, deleting, or changing one character (i.e., the <a href="/material/p1791">Levenshnein distance</a> is actually considered). Your task is to find the error, fix it, and get OK on the task. Even with a margin, you are given the opportunity to make up to 23 edits.</p>

        <p>In the error search interface, you are immediately given a text editor in which the solution code is open. I strongly recommend looking for errors directly in this editor, without copying the code anywhere to yourself (to your IDE or editor), and accordingly not using a debugger, etc., but only looking at the code with your eyes. But in the most difficult cases, you can copy the code to yourself and understand it more thoroughly.</p>

        <p>The solutions in the "Find a bug" section are available in different programming languages. Don't be afraid to look for bugs even in languages you don't know. I try not to allow those solutions in which the error is caused by language problems to search for errors, almost always errors have more algorithmic reasons, and, accordingly, you can find them, even if you do not know the features of the language.</p>

        <p>I do not look at the solutions sent through the "find a bug" section with my eyes and do not comment (in particular, it is impossible to get "accepted" for them), and they do not affect your results in the general table. Of course, if you can't find an error, you can write to me, I will advise you something.</p>

        <p>Each solution, in addition to the problem, is also characterized by an individual number (a combination of four letters or numbers). Use this number to distinguish between solutions for finding errors for the same problem; in particular, if you want to ask me about such a solution, then specify both the name of the problem and the number of the solution (well, or just send a link to the error search page in this particular solution).</p>

        <p>So far, in principle, there are not very many solutions in which to look for errors; over time, I think there will be more of them.</p>""", {id: "about_find_mistake"})

contacts = () ->
    label("""

        <li>Telegram: <a href="https://t.me/pkalinin">@pkalinin</a></li>
        <li>Telegram channel with important announcements: <a href=\"https://t.me/algoprog_news\">@algoprog_news</a> (mainly in Russian). </li>
        <li>Telegram chat for all algoprog students: <a href="https://t.me/+Ff0fS3PMo85iNmZi">Algoprog-chat</a>.
        To join, you should first specify your telegram id in your algoprog profile.</li>
        </ul>
        <p>My contact details can be freely distributed for any questions related to the course or
        with olympiad programming in general.</p>
        <p><b>If you have any problems with working in the course, any questions, etc., write to me immediately!</b></p>
        <p>* VK friend policy: I don't mind if you add me as a friend,
        but I will only add those who have been successfully engaged for a long time.</p>
        <p>** Please call by phone only in emergency cases. If your question is not very urgent and can
        wait a few hours, write to me in any way indicated above — in VKontakte, in Telegram or by email.
