From dce32c5cd017ca7205848d7f7debf97747b5f6f4 Mon Sep 17 00:00:00 2001 From: Ivan Medina Date: Wed, 9 Oct 2024 02:59:02 +0200 Subject: [PATCH] Update intro.md (#215) Fix a few minor typos in intro docs --- src/docs/learn/parser_in_rust/intro.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/docs/learn/parser_in_rust/intro.md b/src/docs/learn/parser_in_rust/intro.md index 14b8e4bef0..7a65c83a08 100644 --- a/src/docs/learn/parser_in_rust/intro.md +++ b/src/docs/learn/parser_in_rust/intro.md @@ -52,12 +52,12 @@ You should also read [The Rust Performance Book](https://nnethercote.github.io/p ## Rust Source Code -Whenever the performance of an function call cannot be deduced, +Whenever the performance of a function call cannot be deduced, do not be afraid to click the "source" button on the Rust documentation and read the source code, they are easy to understand most of the time. :::info When navigating the Rust source code, searching for a definition is simply looking for -`fn function_name`, `struct struct_name`, `enum enum_name` etc. +`fn function_name`, `struct struct_name`, `enum enum_name`, etc. This is one advantage of having constant grammar in Rust (compared to JavaScript 😉). :::