From 67be5c652d4b106b845a63a8f4880d001627dc1b Mon Sep 17 00:00:00 2001 From: Taemin Ha Date: Fri, 17 Mar 2023 08:04:51 -0500 Subject: [PATCH] docs/contributing: Fix typo in Coding Style page "In the future, me might..." -> "In the future, we might..." Signed-off-by : Taemin Ha --- content/en/docs/contributing/coding-style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/contributing/coding-style.md b/content/en/docs/contributing/coding-style.md index 4dc5da78..e7f70ef9 100644 --- a/content/en/docs/contributing/coding-style.md +++ b/content/en/docs/contributing/coding-style.md @@ -18,7 +18,7 @@ Most code closely follows an automatically-formatted style defined by the [.clan However, since this is an automated formatting tool, it's not perfect, and the Unikraft code can deviate from the `clang-format`'s programmatically created output (especially in the aesthetics of assignment alignments). Use `clang-format` as a helpful tool, but with a grain of salt. Again, note that some parts of the code (e.g. lib/fdt) follow different coding styles that you should follow if you change this code. -In the future, me might provide `.clang-format` files appropriate for those libraries. +In the future, we might provide `.clang-format` files appropriate for those libraries. We would also be very happy to accept `.clang-format` definitions for those. ### Code Documentation