Fixed some spelling mistakes.

1 files changed, 2 insertions, 2 deletions

diff --git a/Documentation/architecture/net-core-applications.md b/Documentation/architecture/net-core-applications.md
index 57a0f8496e..18c950cfed 100644
--- a/Documentation/architecture/net-core-applications.md
+++ b/Documentation/architecture/net-core-applications.md
@@ -19,10 +19,10 @@ NETStandard version supported | `netstandard1.6`
 **A:** Yes.  Most of the API supported by .NET Core application is also part of .NET Standard.  That source could be compiled as a .NET Standard library and shared with a .NET Core application and a .NET Framework application as a binary.  Alternatively, the source could be shared and cross-compiled between a .NET Core application and a .NET Framework application.
 
 **Q: Can a .NET Core application depend on more packages than just those in the `NETStandard.Library` package?**  
-**A:** Yes.  The contents of `NETStandard.Library` represent the standard library and are garunteed to be supported by all platforms, including .NET Core applications, that support standard library.  Packages outside of this set will be supported so long as their dependencies are provided and none are platform specific.
+**A:** Yes.  The contents of `NETStandard.Library` represent the standard library and are guaranteed to be supported by all platforms, including .NET Core applications, that support standard library.  Packages outside of this set will be supported so long as their dependencies are provided and none are platform specific.
 
 **Q: Can a .NET Core application depend on more packages than just those in the `Microsoft.NETCore.App` package?**  
-**A:** Yes.  The contents of `Microsoft.NETCore.App` at a particular version are garunteed to run on every platform where that version .NET Core is released.  Packages outside this set can be used but don't come with that garuntee.  For instance, if a package is not part of `Microsoft.NETCore.App` and needs to be cross-compiled speicfically for a new OS, there is no garuntee that it will be re-released when .NET Core supports that new OS.
+**A:** Yes.  The contents of `Microsoft.NETCore.App` at a particular version are guaranteed to run on every platform where that version .NET Core is released.  Packages outside this set can be used but don't come with that guarantee.  For instance, if a package is not part of `Microsoft.NETCore.App` and needs to be cross-compiled specifically for a new OS, there is no guarantee that it will be re-released when .NET Core supports that new OS.
 
 **Q: Why is there only one version of `.NETCoreApp` (1.0), but there are many of `.NETStandard`?**  
 **A:** `.NETStandard` is an abstract representation of API that covers all historical platforms that have ever supported that API.  `.NETCoreApp` represents a concrete application type with a runnable implementation.  We are shipping one version of this implementation at this point and it supports `netstandard1.6`.  As we version `.NETStandard` in the future we will update the implementation of `.NETCoreApp` to support the new API and ship a new version of `.NETCoreApp`.