,
, tags. For code tags, translate text inside? The code tags contain commands like /explain, /fix, /git, /help. Those are command names, should remain as is? Probably keep them in original form because they are literal commands. But the surrounding text can be translated. Also "bash" and "PowerShell" are proper nouns? Keep as is. "macOS, Linux, and Windows" keep as is.
Meta description: "GitHub Copilot CLI now supports slash commands like /explain and /fix, letting developers get help and fix errors faster without leaving the terminal." Translate: "GitHub Copilot CLI unterstützt jetzt Schrägstrich-Befehle wie /explain und /fix, sodass Entwickler schneller Hilfe erhalten und Fehler beheben können, ohne das Terminal zu verlassen."
Be careful with HTML: keep exact structure. Use German quotation marks? Not needed. Use appropriate terminology: "slash commands" -> "Schrägstrich-Befehle" or "Slash-Befehle"? The article uses "slash commands" in English, but in German tech context, "Slash-Befehle" is common. However, requirement says use appropriate German terminology. I'll use "Schrägstrich-Befehle" to be more German, but "Slash-Befehle" is also acceptable. I'll go with "Schrägstrich-Befehle" and also use "Schrägstrich" in description. For "command-line interface" -> "Kommandozeile" or "Befehlszeilenschnittstelle". "CLI" is often kept as is. "GitHub Copilot CLI" is proper noun, keep. "terminal" -> "Terminal". "public preview" -> "öffentliche Vorschau". "plain English" -> "einfachem Englisch". "debugging" -> "Debugging". "exploration workflows" -> "Explorations-Workflows". "friction" -> "Reibung". "flags or syntax" -> "Flags oder Syntax". "Googling" -> "Googeln" (as verb). "AI-assisted development" -> "KI-gestützte Entwicklung". "code completion" -> "Codevervollständigung". "chat in pull requests" -> "Chat in Pull Requests". "release date" -> "Veröffentlichungsdatum". "pricing changes" -> "Preisänderungen".
Also note: The original content has a after the second h2? Actually structure: ...
...
...
...
...
...
...
...
...
...
after the second h2? Actually structure: ... ... ... ... ... ... ... ......
...
