chore: whitepaper update

src/md/whitepaper.md

@@ -1,16 +1,18 @@
 ## The Problem...
 
-### Overcomplication of Modern Web Development
+### The Increasing Complexity of Modern Web Development
 
-You've probably come across posts on social networks in which the authors analyze how everything in web development used to be easy and simple, but now it has become difficult and inaccessible. When HTML was invented, it was simply a markup language for creating simple web pages and links between them.
+You may have encountered discussions on social media reflecting on the simplicity of early web development, contrasting sharply with today's complexities. Originally, HTML served as a straightforward markup language for crafting basic web pages and linking them together.
 
-Now an HTML document is more of a configuration for initializing a web application that uses many technologies besides hypertext itself. The entire evolution of the web is a story of the complication of the simple concept of hypertext to the level of a full-fledged platform for application development. On the one hand, this has opened up many opportunities for self-expression and business. On the other hand, it closed the door to the creation of web resources for people who are not web developers directly and do not devote all their time to studying web technologies in deep.
+Currently, an HTML document acts more as a configuration tool for launching a web application, incorporating numerous technologies beyond mere hypertext. The web's evolution narrates the transformation of the simple hypertext concept into a comprehensive platform for application development. While this progression has unlocked vast opportunities for creativity and business, it has simultaneously erected barriers for individuals not deeply versed in web development, preventing them from easily creating web resources.
 
-There was a time when the needs of developers were greater than what the “native” web could offer, and additional solutions had to be created for production development problems. These, for example, are JQuery, CommonJS, CSS preprocessors, bundlers, UI libraries that support their own component model only (React), and so on.
+There was a period when developers' needs surpassed the capabilities of the "native" web, necessitating additional tools for tackling development challenges. Examples include JQuery, CommonJS, CSS preprocessors, bundlers, and UI libraries with exclusive component models like React.
 
-However, now the web platform (language standards, browser APIs and node) has become much more advanced, and can do what a bunch of side artifacts were previously created for. Moreover, it can do it better: faster, safer, more convenient. The paradox is that the web industry is inert, and new features sometimes conflict with their implementation in the form of separate additional tools that have become popular earlier.
+However, the web platform, encompassing language standards, browser APIs, and Node has significantly evolved, offering solutions that obsolete many previously essential external tools. It now delivers these solutions more efficiently, securely, and user-friendly. Despite these advancements, the web industry's inertia and the potential conflict between new features and earlier, popular tools pose a paradox.
 
-If you want a simple web page, you can use simple static HTML and a simple web server. If you need several simple pages, with the same “header” and “footer” blocks, it becomes difficult for you to make changes manually in each file. If you need a block of formatted text on a page, it becomes inconvenient to format it with HTML tags, especially in comparison with the markdown format. But markdown itself is not supported by the browser, just like HTML modules. And so on. And it often happens that your tasks look very simple at first glance, but their solution begins to require you to know many additional things, such as frameworks or CMS.
+Creating a simple web page remains straightforward with basic HTML and a web server. Yet, implementing consistent "header" and "footer" parts across multiple pages complicates manual updates. Similarly, formatting text blocks becomes cumbersome with HTML tags, especially compared to markdown format.  But markdown itself is not browser-supported, and HTML modules are not supported too.
+
+Often, tasks that initially seem straightforward reveal underlying complexities, necessitating knowledge of various frameworks or CMS solutions.
 
 ### Problems of no-code systems