From 89430a14d689830218559478f6efb4352b49067c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kende=20G=C3=B6m=C3=B6ri?= Date: Sat, 6 Dec 2025 02:31:04 +0100 Subject: [PATCH] Fix docs: typo & dead link (#8826) * Fix CHANGELOG.md * Fix broken doc link --- CHANGELOG.md | 2 +- CONTRIBUTING.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e38b0835a..d5d5d29c8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,7 +9,7 @@ necessarily listed. * flatc: `--grpc-callback-api` flag generates C++ gRPC Callback API server `CallbackService` skeletons AND client native callback/async stubs (unary + all streaming reactor forms) (opt-in, non-breaking, issue #8596). * Swift - Adds new API to reduce memory copying within swift (#8484) * Rust - Support Rust edition 2024 (#8638) -# [:C++] - Use the Google Style for clang-format without exceptions (#8706) +* [C++] - Use the Google Style for clang-format without exceptions (#8706) ## [25.2.10] (February 10 2025)(https://github.com/google/flatbuffers/releases/tag/v25.2.10) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index df4eee55e..4353a6c07 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -30,7 +30,7 @@ Some tips for good pull requests: * Write a descriptive commit message. What problem are you solving and what are the consequences? Where and what did you test? Some good tips: [here](http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message) - and [here](https://www.kernel.org/doc/Documentation/SubmittingPatches). + and [here](https://www.kernel.org/doc/Documentation/process/submitting-patches.rst). * If your PR consists of multiple commits which are successive improvements / fixes to your first commit, consider squashing them into a single commit (`git rebase -i`) such that your PR is a single commit on top of the current