diff options
| author | Scott Freeman <gsfreema@gmail.com> | 2017-06-30 09:19:40 -0400 |
|---|---|---|
| committer | Scott Freeman <gsfreema@gmail.com> | 2017-06-30 09:19:40 -0400 |
| commit | 18ac27fa981bba7c316693ed396bd4f816658932 (patch) | |
| tree | 26e22cdc585e499d8ebd73fdbbc7c61bc90f89b6 /Documentation | |
| parent | 217ab30d021f27be6fe4f35126a88e592366acbf (diff) | |
| download | coreclr-18ac27fa981bba7c316693ed396bd4f816658932.tar.gz coreclr-18ac27fa981bba7c316693ed396bd4f816658932.tar.bz2 coreclr-18ac27fa981bba7c316693ed396bd4f816658932.zip | |
README.md link and grammar fixes
Fixing various typos, grammar mistakes, and broken links in the root README.md file.
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/botr/intro-to-clr.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/botr/intro-to-clr.md b/Documentation/botr/intro-to-clr.md index 3ba3d3b81e..2e5b8de0a2 100644 --- a/Documentation/botr/intro-to-clr.md +++ b/Documentation/botr/intro-to-clr.md @@ -47,7 +47,7 @@ The second reason this goal is so important is that **ease of use is the fundame 3. Strong consistency in the naming in the class library (e.g., requiring APIs to use whole words and consistent naming conventions) 4. Great support in the tool chain needed to create an application (e.g., Visual Studio makes building CLR applications very simple, and Intellisense makes finding the right types and methods to create the application very easy). -It is this dedication to ease of use (which goes hand in hand with simplicity of the user model) that stands out as the reason for the success of the CLR. Oddly, some of the most important ease-of-use features are also the most "boring." For example, any programming environment could apply consistent naming conventions, yet actually doing so across a large class library is quite a lot of work. Often such efforts conflict with other goals (such as retaining compatibility with existing interfaces), or they run into significant logistical concerns (such as the cost of renaming a method across a _very_ large code base). It is at times like these that we have to remind ourselves about our number-one overarching goal of the runtime and ensure that we are have our priorities straight to reach that goal. +It is this dedication to ease of use (which goes hand in hand with simplicity of the user model) that stands out as the reason for the success of the CLR. Oddly, some of the most important ease-of-use features are also the most "boring." For example, any programming environment could apply consistent naming conventions, yet actually doing so across a large class library is quite a lot of work. Often such efforts conflict with other goals (such as retaining compatibility with existing interfaces), or they run into significant logistical concerns (such as the cost of renaming a method across a _very_ large code base). It is at times like these that we have to remind ourselves about our number-one overarching goal of the runtime and ensure that we have our priorities straight to reach that goal. # Fundamental Features of the CLR |