fresh build

docs/index.html

@@ -10,7 +10,7 @@
     </title>
     <meta
         name="description"
-        content="API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well. This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics: the API design, API patterns, maintaining backward compatibility, HTTP API & REST, SDK and UI libraries, API product management."
+        content="API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well. This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics: the API design, API patterns, maintaining backward compatibility, HTTP APIs & REST, SDKs and UI libraries, API product management."
     />
     <meta property="og:type" content="article" />
     <meta
@@ -19,7 +19,7 @@
     />
     <meta
         property="og:description"
-        content="API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well. This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics: the API design, API patterns, maintaining backward compatibility, HTTP API & REST, SDK and UI libraries, API product management."
+        content="API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well. This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics: the API design, API patterns, maintaining backward compatibility, HTTP APIs & REST, SDKs and UI libraries, API product management."
     />
     <meta property="og:image" content="assets/header.png" />
     <meta
@@ -47,8 +47,8 @@
 <ul><li>— The API design</li>
 <li>— API patterns</li>
 <li>— Backward compatibility</li>
-<li>— HTTP API & REST</li>
-<li>— SDK and UI libraries</li>
+<li>— HTTP APIs & REST architectural principles</li>
+<li>— SDKs and UI libraries</li>
 <li>— API product management.</ul>
 <p>Illustration &amp; inspiration: <a href="https://www.instagram.com/art.mari.ka/">art.mari.ka</a>.</p>
     <p>You might download ‘The API’ in <a href="API.en.pdf">PDF</a> / <a href="API.en.epub">EPUB</a> or <a href="API.en.html">read it online</a>.
@@ -107,20 +107,20 @@
                             </ul>
             </li>
 <li>
-                <h4><a href="API.en.html#section-5">[Work in Progress] Section IV. The HTTP API & REST</a></h4>
+                <h4><a href="API.en.html#section-5">[Work in Progress] Section IV. HTTP APIs & REST Architectural Principles</a></h4>
                 <ul>
                     <li><a href="API.en.html#http-api-concepts">Chapter 33. On the HTTP API Concept and Terminology</a></li>
 <li><a href="API.en.html#http-api-rest-myth">Chapter 34. The REST Myth</a></li>
 <li><a href="API.en.html#http-api-requests-semantics">Chapter 35. Components of an HTTP Request and Their Semantics</a></li>
 <li><a href="API.en.html#http-api-pros-and-cons">Chapter 36. Advantages and Disadvantages of HTTP APIs</a></li>
-<li><a href="API.en.html#chapter-37">Chapter 37. HTTP API Organization Principles</a></li>
+<li><a href="API.en.html#http-api-rest-organizing">Chapter 37. Organizing an HTTP API Based on the REST Principles</a></li>
 <li><a href="API.en.html#chapter-38">Chapter 38. Working with HTTP API Errors</a></li>
 <li><a href="API.en.html#chapter-39">Chapter 39. Organizing the HTTP API Resources and Operations</a></li>
 <li><a href="API.en.html#chapter-40">Chapter 40. Final Provisions and General Recommendations</a></li>
                             </ul>
             </li>
 <li>
-                <h4><a href="API.en.html#section-6">[Work in Progress] Section V. The SDK & UI Libraries</a></h4>
+                <h4><a href="API.en.html#section-6">[Work in Progress] Section V. SDKs & UI Libraries</a></h4>
                 <ul>
                     <li><a href="API.en.html#chapter-41">Chapter 41. On the Content of This Section</a></li>
 <li><a href="API.en.html#chapter-42">Chapter 42. The SDK: Problems and Solutions</a></li>

docs/index.ru.html

@@ -113,7 +113,7 @@
 <li><a href="API.ru.html#http-api-rest-myth">Глава 34. Мифология REST</a></li>
 <li><a href="API.ru.html#http-api-requests-semantics">Глава 35. Составляющие HTTP запросов и их семантика</a></li>
 <li><a href="API.ru.html#http-api-pros-and-cons">Глава 36. Преимущества и недостатки HTTP API</a></li>
-<li><a href="API.ru.html#chapter-37">Глава 37. Принципы организации HTTP API</a></li>
+<li><a href="API.ru.html#http-api-rest-organizing">Глава 37. Организация HTTP API согласно принципам REST</a></li>
 <li><a href="API.ru.html#chapter-38">Глава 38. Работа с ошибками в HTTP API</a></li>
 <li><a href="API.ru.html#chapter-39">Глава 39. Организация URL ресурсов и операций над ними в HTTP API</a></li>
 <li><a href="API.ru.html#chapter-40">Глава 40. Заключительные положения и общие рекомендации</a></li>