From f19e8e8b94f317d6d3c266cc7ab29c4bb010c1bd Mon Sep 17 00:00:00 2001 From: itaidagan1 Date: Sat, 20 Jun 2020 19:04:15 +0000 Subject: [PATCH] Fixed typo --- chapters/intro/dodonot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/intro/dodonot.md b/chapters/intro/dodonot.md index eef0a72..246ee3f 100644 --- a/chapters/intro/dodonot.md +++ b/chapters/intro/dodonot.md @@ -19,7 +19,7 @@ The next two lists are heavily based on the excellent gist [Effective Modern CMa * **Write a Config.cmake file**: This is what a library author should do to support clients. * **Make ALIAS targets to keep usage consistent**: Using `add_subdirectory` and `find_package` should provide the same targets and namespaces. * **Combine common functionality into clearly documented functions or macros**: Functions are better usually. -* **Use lowercase function names**: CMake functions and macros can be called lower or upper case. Always user lower case. Upper case is for variables. +* **Use lowercase function names**: CMake functions and macros can be called lower or upper case. Always use lower case. Upper case is for variables. * **Use `cmake_policy` and/or range of versions**: Policies change for a reason. Only piecemeal set OLD policies if you have to.