chore: spelling/grammar fixes

[rmfranken]

Hi there,

just want to point out some spelling/grammar. I think it would make a lot of sense for you to run this entire standard through a spellchecker or even LLM for grammatical consistency. This is what I found with just 2 minutes while trying to understand the section on types of software.

diff --git a/docs/de/schema.core.rst b/docs/de/schema.core.rst
--- docs/de/schema.core.rst
+++ docs/de/schema.core.rst
@@ -269,22 +269,21 @@
    ``"standalone/other"``, ``"addon"``, ``"library"``, ``"configurationFiles"``
 
 The keys are:
 
--  ``standalone/mobile`` - The software is a standalone, self-contained
-   The software is a native mobile app.
+-  ``standalone/mobile`` - The software is a native mobile app.
 -  ``standalone/iot`` - The software is suitable for an IoT context.
--  ``standalone/desktop`` - The software is typically installed and run in a  
+-  ``standalone/desktop`` - The software is typically installed and ran in a  
    a desktop operating system environment.
 -  ``standalone/web`` - The software represents a web application usable by
    means of a browser. 
 -  ``standalone/backend`` - The software is a backend application.
--  ``standalone/other`` - The software has a different nature from the once
+-  ``standalone/other`` - The software has a different nature from the ones
    listed above.  
 -  ``addon`` - The software is an addon, such as a plugin or a
    theme, for a more complex software (e.g. a CMS or an office suite).
 -  ``library`` - The software contains a library or an SDK to make it
-   easier to third party developers to create new products.
+   easier for third party developers to create new products.
 -  ``configurationFiles`` - The software does not contain executable
    script but a set of configuration files. They may document how to
    obtain a certain deployment. They could be in the form of plain
    configuration files, bash scripts, ansible playbooks, Dockerfiles, or

Kind regards,
Robin

[bfabio]

Thanks Robin. The main thing here is that this is docs/de/.
It reads like English only because it hasn't been translated yet, so it really be in German.

Translations aren't normative anyway, the source of truth is docs/standard/ (see governance/procedure-proposing-changes-and-voting.md). fwiw two of these are already fixed there, and run -> ran isn't right, "installed and run" is passive so "run" is correct as is.

If you want to help with either the translation, the main spec or the CI spellcheck, a PR would be welcome!