From 9642fab3d0adc564fe40019c1651a71bde876177 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 16 Jan 2023 08:58:36 +0100 Subject: [PATCH] Fix: typos (#3764) * Fix: typos Fix: typos * Fix: typos Fix: typos Co-authored-by: CoderZhi --- README.md | 4 ++-- crypto/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5fa97e86fc..9df3101f67 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,7 @@ If the dependency needs to be updated, run go get -u go mod tidy ``` -If you want learn more advanced usage about `go mod`, you can find out [here](https://github.com/golang/go/wiki/Modules). +If you want to learn more advanced usage about `go mod`, you can find out [here](https://github.com/golang/go/wiki/Modules). Run unit tests only by @@ -83,7 +83,7 @@ make docker ### Run iotex-core -Start (or resume) a standalone server to operate on an blockchain by +Start (or resume) a standalone server to operate on a blockchain by ``` make run diff --git a/crypto/README.md b/crypto/README.md index a8dcd0a0b0..1e4b2394fc 100644 --- a/crypto/README.md +++ b/crypto/README.md @@ -30,7 +30,7 @@ * ā€œ//ā€ is not a regular comment sign in CGO declaration. It starts a directive and will not be ignored by compiler. * import ā€œCā€ should be immediately preceded by //#include XXX or //#cgo. * //#include XXX indicates the use of c header files and c source code files - * //#cgo is used to indicate the use of flags like CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS etc. to tweak the behavior of C, C++ compiler. The //#cgo directive can also include a list of build constraints that limit the os and architecture. It can also indicates the C library, so that you do not have to include the source code files. + * //#cgo is used to indicate the use of flags like CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS etc. to tweak the behavior of C, C++ compiler. The //#cgo directive can also include a list of build constraints that limit the os and architecture. It can also indicate the C library, so that you do not have to include the source code files. ``` Go //#cgo darwin LDFLAGS: -L${SRCDIR}/lib -lsect283k1_macos //#cgo linux LDFLAGS: -L${SRCDIR}/lib -lsect283k1_ubuntu @@ -126,7 +126,7 @@ func (b *bls) Sign(privkey []uint32, msg []byte) (bool, []byte, error) { ``` ##### 4. Use struct defined in C * Construct a corresponding struct in Go that mimics the same struct in C. - * (Recommended) Write function to serialize and deserialize the the struct, so the information can be exposed outside independently. + * (Recommended) Write function to serialize and deserialize the struct, so the information can be exposed outside independently. ``` Go // C header file and C struct definition typedef struct