Browse Source

chore(docs): Add final newline to markdown files (#19645)

Several documentation files were missing a final newline character.
This change adds them to adhere to POSIX conventions and improve
compatibility with various text-processing tools. It also helps
to create cleaner diffs in the future.
pull/19650/head
Vaibhav Gupta 5 months ago
committed by GitHub
parent
commit
f4e653a8de
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
  1. 2
      docs/api-compat.md
  2. 2
      docs/build.md
  3. 2
      docs/porting-code-from-3rd-party-sources.md

2
docs/api-compat.md

@ -29,4 +29,4 @@ API changes are validated against a **baseline version**—the reference point f
## Additional Resources ## Additional Resources
- [API Validation Tool Implementation](https://github.com/AvaloniaUI/Avalonia/pull/12072) - Pull request that introduced this feature - [API Validation Tool Implementation](https://github.com/AvaloniaUI/Avalonia/pull/12072) - Pull request that introduced this feature

2
docs/build.md

@ -108,4 +108,4 @@ It is possible to run some .NET Framework samples and tests using .NET Framework
## Building Avalonia into a local NuGet cache ## Building Avalonia into a local NuGet cache
See [Building Local NuGet Packages](nuget.md) See [Building Local NuGet Packages](nuget.md)

2
docs/porting-code-from-3rd-party-sources.md

@ -9,4 +9,4 @@ When porting code or adapting code from other projects with a MIT compatible lic
// Licensed to The Avalonia Project under MIT License, courtesy of The .NET Foundation. // Licensed to The Avalonia Project under MIT License, courtesy of The .NET Foundation.
``` ```
If the file is a port of a specific commit of file from a 3rd party source, then consider including a permalink to the source file. If the file is a port of a specific commit of file from a 3rd party source, then consider including a permalink to the source file.

Loading…
Cancel
Save