From 6bd04ab0bd76e95393b1f1d0e4751293e2b0414c Mon Sep 17 00:00:00 2001
From: Lisa Toftemark <lisatoft@microsoft.com>
Date: Fri, 20 Feb 2015 09:56:41 -0800
Subject: [PATCH] Update remoteapp-appreqs.md

---
 articles/remoteapp-appreqs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/remoteapp-appreqs.md b/articles/remoteapp-appreqs.md
index 8050abab9b8..9ec2a992d52 100644
--- a/articles/remoteapp-appreqs.md
+++ b/articles/remoteapp-appreqs.md
@@ -21,7 +21,7 @@
 # App requirements
 RemoteApp supports streaming 32-bit or 64-bit Windows-based applications from a Windows Server 2012 R2 installation. Most existing 32-bit or 64-bit Windows-based applications run "as is" in RemoteApp (Remote Desktop Services or formerly known as Terminal Services) environment. However, there is a difference between running and running well - some applications function correctly and perform well, while others do not. The following information provides guidance for developing applications in a Remote Desktop Services environment and testing to ensure compatibility.
 
-## Requirements:
+## Requirements
 These three requirements, if followed, help your application run well in RemoteApp: 
 1.	Applications that meet all [Certification requirements for Windows desktop apps](https://msdn.microsoft.com/library/windows/desktop/hh749939.aspx) and adhere to [Remote Desktop Services programming guidelines](https://msdn.microsoft.com/library/aa383490(v=VS.85).aspx) will have complete compatibility with RemoteApp. 
 2.	Applications should never store data locally on the image or RemoteApp instances that can be lost.  After you create a RemoteApp collection, the instances are cloned and are stateless and should only contain applications. Store data in an external source or within the user's profile.