diff --git a/content/BCBestPractices/Readability/begin-as-an-afterword/index.md b/content/BCBestPractices/Readability/begin-as-an-afterword/index.md index c9db894b..6de42784 100644 --- a/content/BCBestPractices/Readability/begin-as-an-afterword/index.md +++ b/content/BCBestPractices/Readability/begin-as-an-afterword/index.md @@ -30,4 +30,4 @@ When `begin` follows `then`, `else`, `do`, it should be on the same line, preced You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/begin-end/index.md b/content/BCBestPractices/Readability/begin-end/index.md index a2bcf372..50f1af12 100644 --- a/content/BCBestPractices/Readability/begin-end/index.md +++ b/content/BCBestPractices/Readability/begin-end/index.md @@ -56,4 +56,4 @@ end else You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/binary-operator-line-start/index.md b/content/BCBestPractices/Readability/binary-operator-line-start/index.md index 4db17067..4318f5ee 100644 --- a/content/BCBestPractices/Readability/binary-operator-line-start/index.md +++ b/content/BCBestPractices/Readability/binary-operator-line-start/index.md @@ -29,4 +29,4 @@ Quantity - You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/case-actions/index.md b/content/BCBestPractices/Readability/case-actions/index.md index 15417a6d..4aa42517 100644 --- a/content/BCBestPractices/Readability/case-actions/index.md +++ b/content/BCBestPractices/Readability/case-actions/index.md @@ -33,4 +33,4 @@ A CASE action should start on a line after the possibility. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/comments-spacing/index.md b/content/BCBestPractices/Readability/comments-spacing/index.md index 87c99b20..0a7e9f15 100644 --- a/content/BCBestPractices/Readability/comments-spacing/index.md +++ b/content/BCBestPractices/Readability/comments-spacing/index.md @@ -25,4 +25,4 @@ RowNo += 1000; // Move way below the budget You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/end-else-pair/index.md b/content/BCBestPractices/Readability/end-else-pair/index.md index c654ebf0..3325d453 100644 --- a/content/BCBestPractices/Readability/end-else-pair/index.md +++ b/content/BCBestPractices/Readability/end-else-pair/index.md @@ -37,4 +37,4 @@ The `end else` pair should always appear on the same line. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/keyword-pairs-indentation/index.md b/content/BCBestPractices/Readability/keyword-pairs-indentation/index.md index 9bbae6a9..94737b14 100644 --- a/content/BCBestPractices/Readability/keyword-pairs-indentation/index.md +++ b/content/BCBestPractices/Readability/keyword-pairs-indentation/index.md @@ -27,4 +27,4 @@ The `if..then` pair, `while..do` pair, and `for..do` pair must appear on the sam You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/line-start-keywords/index.md b/content/BCBestPractices/Readability/line-start-keywords/index.md index dc758f29..7bfbafd1 100644 --- a/content/BCBestPractices/Readability/line-start-keywords/index.md +++ b/content/BCBestPractices/Readability/line-start-keywords/index.md @@ -34,4 +34,4 @@ The `end`, `if`, `repeat`, `for`, `while`, `else` and `case` statement should al You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/lonely-repeat/index.md b/content/BCBestPractices/Readability/lonely-repeat/index.md index 7b2fb09c..6b3e755b 100644 --- a/content/BCBestPractices/Readability/lonely-repeat/index.md +++ b/content/BCBestPractices/Readability/lonely-repeat/index.md @@ -25,4 +25,4 @@ The `repeat` statement should always be alone on a line. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/named-invocations/index.md b/content/BCBestPractices/Readability/named-invocations/index.md index e6c2ae03..72df4f74 100644 --- a/content/BCBestPractices/Readability/named-invocations/index.md +++ b/content/BCBestPractices/Readability/named-invocations/index.md @@ -24,4 +24,4 @@ When calling an object statically use the Object Name, not the Object Id. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/one-statement-per-line/index.md b/content/BCBestPractices/Readability/one-statement-per-line/index.md index c5085b87..70d28a12 100644 --- a/content/BCBestPractices/Readability/one-statement-per-line/index.md +++ b/content/BCBestPractices/Readability/one-statement-per-line/index.md @@ -40,4 +40,4 @@ A line of code should not have more than one statement. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/separate-if-and-else/index.md b/content/BCBestPractices/Readability/separate-if-and-else/index.md index b74acec1..f486ae5e 100644 --- a/content/BCBestPractices/Readability/separate-if-and-else/index.md +++ b/content/BCBestPractices/Readability/separate-if-and-else/index.md @@ -31,4 +31,4 @@ weight = 1050 You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/suggested-abbreviations/index.md b/content/BCBestPractices/Readability/suggested-abbreviations/index.md index 7d2bd79f..b54309c7 100644 --- a/content/BCBestPractices/Readability/suggested-abbreviations/index.md +++ b/content/BCBestPractices/Readability/suggested-abbreviations/index.md @@ -363,4 +363,4 @@ If there is no other choice, then use the suggestions below. You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/unnecessary-else/index.md b/content/BCBestPractices/Readability/unnecessary-else/index.md index ee900d0a..740f02f1 100644 --- a/content/BCBestPractices/Readability/unnecessary-else/index.md +++ b/content/BCBestPractices/Readability/unnecessary-else/index.md @@ -35,4 +35,4 @@ weight = 1270 You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/unnecessary-truefalse/index.md b/content/BCBestPractices/Readability/unnecessary-truefalse/index.md index 8dd85113..75f7e81f 100644 --- a/content/BCBestPractices/Readability/unnecessary-truefalse/index.md +++ b/content/BCBestPractices/Readability/unnecessary-truefalse/index.md @@ -37,4 +37,4 @@ Do not use `true` or `false` keywords unnecessarily if the expression is already You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file diff --git a/content/BCBestPractices/Readability/variable-naming/index.md b/content/BCBestPractices/Readability/variable-naming/index.md index 6ac4d757..7cd112fb 100644 --- a/content/BCBestPractices/Readability/variable-naming/index.md +++ b/content/BCBestPractices/Readability/variable-naming/index.md @@ -44,4 +44,4 @@ If a variable is a compound of two or more words or abbreviations, each word or You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/BCBestPractices/Readability/variables-declarations-order/index.md b/content/BCBestPractices/Readability/variables-declarations-order/index.md index 7ec97cc5..0afd6a93 100644 --- a/content/BCBestPractices/Readability/variables-declarations-order/index.md +++ b/content/BCBestPractices/Readability/variables-declarations-order/index.md @@ -43,4 +43,4 @@ Variables declarations should be ordered by type. In general, object and complex You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. diff --git a/content/Contributing/Templates/Guidelines/index.md b/content/Contributing/Templates/Guidelines/index.md index b485f566..da408a49 100644 --- a/content/Contributing/Templates/Guidelines/index.md +++ b/content/Contributing/Templates/Guidelines/index.md @@ -33,4 +33,4 @@ PutCodeblocksHere() You can find discussions on all "Best Practices" [here](https://github.com/microsoft/alguidelines/discussions/categories/bc-best-practices). -If you don't find the discussion of this guideline, please feel fee to create a new one with the same title as this article. \ No newline at end of file +If you don't find the discussion of this guideline, please feel free to create a new one with the same title as this article. \ No newline at end of file