From 51d4271f432de25f9294cfd67917f012800f9cf0 Mon Sep 17 00:00:00 2001 From: Martin Polanka Date: Sun, 6 Nov 2016 11:16:20 +0100 Subject: [PATCH] typos --- Coding-style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Coding-style.md b/Coding-style.md index d06af23..20d87eb 100644 --- a/Coding-style.md +++ b/Coding-style.md @@ -6,7 +6,7 @@ Every project should have some consistent coding style in which all contributors **NOTE, that C++ projects have set code linter (`cmake-format`) with custom format. To reformat code run `make format` inside `build` directory of the project (probably not working on Windows).** For quick introduction into our format, see following paragraphs. -In C++ is written worker and queue manager. Generally its used underscore style with all small letters. Inspired by [Google C++ style guide](https://google.github.io/styleguide/cppguide.html). If something is not defined than naming/formatting can be arbitrary, but should be similar to bellow-defined behaviour. +In C++ is written worker and broker. Generally it is used underscore style with all small letters. Inspired by [Google C++ style guide](https://google.github.io/styleguide/cppguide.html). If something is not defined than naming/formatting can be arbitrary, but should be similar to bellow-defined behaviour. ### Naming convention * For source codes use all lower case with underscores not dashes. Header files should end with `.h` and C++ files with `.cpp`.