2015-02-02-version-0.13.md fix typos and add summary

adamralph · adamralph · commit 92485ef7ff9a · 2015-01-27T21:22:44.000+01:00
diff --git a/_posts/2015-02-02-version-0.13.md b/_posts/2015-02-02-version-0.13.md
@@ -1,13 +1,13 @@
 ---
 layout: post
-title: "A new filesystem"
+title: "A new file system"
 tagline: "Playing better with .NET solutions."
 category: Releases
 tags: [changes]
 ---
 {% include JB/setup %}
 
-With script version 0.13 we decided to make some changes to help scriptcs run more smoothly together with existing .NET solutions. A problem which existed until now was the occasional inability to run scriptcs from within the folder of a regular .NET solution due to problematic assemblies in `packages` or `bin` folders. These would be assemblies which were not installed in order to be used from scriptcs, but rather from the .NET solution, and cause errors or warnings when running scriptcs. In particular, developers and users of build systems based on scriptcs, e.g. [PVC](http://pvcbuild.com/) and [Bau](https://github.com/bau-build/bau), were often tripped up by this.
+With scriptcs version 0.13 we decided to make some changes to help scriptcs run more smoothly together with existing .NET solutions. A problem which existed until now was the occasional inability to run scriptcs from within the folder of a regular .NET solution due to problematic assemblies in `packages` or `bin` folders. These would be assemblies which were not installed in order to be used from scriptcs, but rather from the .NET solution, and cause errors or warnings when running scriptcs. In particular, developers and users of build systems based on scriptcs, e.g. [PVC](http://pvcbuild.com/) and [Bau](https://github.com/bau-build/bau), were often tripped up by this.
 
 The problem occured because, until now, the file system conventions used by regular .NET and scriptcs overlapped. They both used `packages.config`, `packages/` and `nuget.config` for NuGet package management and scriptcs searched `bin/` for binaries, a folder often used for other purposes in a .NET solution.
 
@@ -45,4 +45,10 @@ Another nice effect of this changed is a potential increase in performance. When
 
 ### Hosting
 
-If you are hosting scriptcs in your own application and you want to perform automatic migration, you will need to call `scriptServices.FileSystemMigrator.Migrate()` at an appropriate place in your application.
+If you are hosting scriptcs in your own application and you want to perform automatic migration, you will need to call `scriptServices.FileSystemMigrator.Migrate()` at an appropriate place in your application.
+
+### Summary
+
+Our hope is that these changes will smooth out any friction you may have running scriptcs in environments shared with regular .NET solutions and projects. In the majority of cases, the upgrade to scriptcs 0.13 should be seamless. Migration to the new conventions is automatic and the only burden left on you is to remove any unwanted 'legacy' artifacts. If you do have any problems, please don't hesitate to let us know by [raising an issue](https://github.com/scriptcs/scriptcs/issues).
+
+By the way, the file system changes are not the only changes in scriptcs version 0.13. For full details of what is contained in this release, please see the [release notes](https://github.com/scriptcs/scriptcs/releases/tag/v0.13).
