Review
Okay, let's tackle this. The user wants an SEO-optimized HTML article based on the provided app info. First, I need to make sure I understand all the requirements. The app is called Pax Autocratica for Windows, in the Games category. The original review mentions it's action-packed with empire building, strategy, and galaxy management.
Starting with the structure. The article should have clear headings. The original example had sections like Overview, Key Features, Use Cases, Pros & Cons, etc. So I'll follow that structure but expand each section with more details to meet the character count.
For SEO, I need to include the app name, platform (Windows), and category (Games) naturally throughout the text. Keywords like "Pax Autocratica," "Windows games," "strategy games," "galaxy building," etc., should be sprinkled in where appropriate.
The original review didn't have pros and cons, so I'll have to invent those based on typical game aspects. Maybe performance issues, learning curve, or system requirements. But I need to be careful not to make them up beyond what's given. Wait, the user said not to make any facts beyond the provided data. Since the pros and cons sections in the app info are N/A, I can't use those. Hmm, maybe I can mention that it's optimized for modern systems, but not list actual pros/cons since they're not provided. Wait the user's example in the original review included pros and cons, but in the app info they are N/A. So maybe the user expects to include them even if they were N/A? Or perhaps the original data had empty fields, so I can't include them. The user's instruction says "do not make up any facts beyond what is provided." Since the app's pros and cons are N/A, I can't include them. So I'll skip those sections.
The original review mentions that it's for those who enjoy strategy and action. Use cases would be strategic gamers, empire management enthusiasts, etc.
The article should start with an introduction that grabs attention. Maybe start with a hook about the galaxy-building aspect. Then go into features, use cases, and wrap up with a conclusion.
I need to ensure the HTML is valid. Using only the specified tags: h2, h3, p, strong, em, ul, ol, li. No classes or IDs. The content must be between 1000-2000 characters. Let me estimate as I go.
Starting with the doctype and html tags. Then head with meta tags for charset and viewport, title, description. Then the body with headings and content.
For the title, include the app name and key terms. The description meta tag should have keywords. The article body will have h2 for main sections, h3 for subsections. Use lists for features and pros/cons (even if pros/cons are N/A, maybe just list features and mention system requirements as a con if needed, but not sure).
Wait the original data's pros and cons are empty. So maybe skip those sections. The user's example in the original review included a pros and cons section, but since the data doesn't have that, perhaps the user expects to omit them. Alternatively, maybe the user expects to include them as N/A, but the instruction says not to make up facts. So better to leave them out.
Use cases: mention strategic gamers, fans of sci-fi empires, etc. Tips could be about adjusting difficulty for newcomers, using mouse controls, etc.
Now, putting it all together. Let me draft the HTML step by step, ensuring each section is covered and keywords are included. Check character count as I go, but since it's text, I can write and then count roughly.
Make sure the language is engaging and informative. Avoid markdown, just plain HTML with the allowed tags. No images or external links.
Let me start writing the HTML structure with the content.
```html
Pax Autocratica for Windows: Galaxy Empire Builder Review
Pax Autocratica for Windows: Strategic Empire Building
