docs: Update README & docs/CONTRIBUTING

Author: eemeli

README.md

@@ -20,6 +20,8 @@ This requirement may be updated between minor versions of the library.
 
 For more information, see the project's documentation site: [**eemeli.org/yaml**](https://eemeli.org/yaml/)
 
+For build instructions and contribution guidelines, see [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md).
+
 To install:
 
 ```sh
@@ -30,26 +32,6 @@ deno add jsr:@eemeli/yaml
 
 **Note:** These docs are for `yaml@2`. For v1, see the [v1.10.0 tag](https://github.com/eemeli/yaml/tree/v1.10.0) for the source and [eemeli.org/yaml/v1](https://eemeli.org/yaml/v1/) for the documentation.
 
-The development and maintenance of this library is [sponsored](https://github.com/sponsors/eemeli) by:
-
-<p align="center" width="100%">
-  <a href="https://www.scipress.io/"
-    ><img
-      width="150"
-      align="top"
-      src="https://eemeli.org/yaml/images/scipress.svg"
-      alt="Scipress"
-  /></a>
-  &nbsp; &nbsp;
-  <a href="https://manifest.build/"
-    ><img
-      width="150"
-      align="top"
-      src="https://eemeli.org/yaml/images/manifest.svg"
-      alt="Manifest"
-  /></a>
-</p>
-
 ## API Overview
 
 The API provided by `yaml` has three layers, depending on how deep you need to go: [Parse & Stringify](https://eemeli.org/yaml/#parse-amp-stringify), [Documents](https://eemeli.org/yaml/#documents), and the underlying [Lexer/Parser/Composer](https://eemeli.org/yaml/#parsing-yaml).

docs/CONTRIBUTING.md

@@ -19,7 +19,7 @@ To that end, the order of priorities is:
    This also means that we want to simultaneously maintain compatibility with multiple versions of the spec, in particular YAML 1.1 and YAML 1.2.
 
 4. **Keep it simple**.
-   Extending the library needs to be done carefully, and keep in all of its users.
+   Extending the library needs to be done carefully, and keep in mind all of its users.
    Different applications have different needs and so are provided with different APIs.
    In particular, custom tags are supported, but aren't part of the built-in schemas.
 
@@ -67,3 +67,6 @@ Note that the CI environment runs tests in both Node.js and browsers, so using n
 
 If you're intending to contribute to the upstream repo, please make sure that your code style matches the Prettier and ESLint rules.
 The easiest way to do that is to configure your editor to do that for you, but `lint` and `prettier` npm scripts are also provided.
+
+If you use an LLM when writing pull requests, this must be explicitly declared in the pull request.
+If there is indication of undeclared LLM assistance, the pull request will be declined.