Viipiin
diff --git a/‎docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-___domain-library.md
Lines changed: 4 additions & 4 deletions b/‎docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-___domain-library.md
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
Lines changed: 8 additions & 8 deletions b/‎docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
Lines changed: 8 additions & 8 deletions
diff --git a/‎docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
Lines changed: 10 additions & 10 deletions b/‎docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
Lines changed: 10 additions & 10 deletions
diff --git a/‎docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
Lines changed: 8 additions & 8 deletions b/‎docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
Lines changed: 8 additions & 8 deletions
diff --git a/‎docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
Lines changed: 6 additions & 6 deletions b/‎docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
Lines changed: 6 additions & 6 deletions
@@ -107,7 +107,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
 
 3. Double click  **Announcements** **>** **Elements.xml**. Paste the following XML nodes as children of the  **ListInstance** element.
 
-  ```
+```
   <Data>
     <Rows>
         <Row>
@@ -120,7 +120,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
         </Row>
     </Rows>
 </Data>
-  ```
+```
 
 
 ### To add a new page that uses the cross-___domain library
@@ -158,7 +158,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
 
 
 
-  ```
+```
   
 <html>
     <head>
@@ -262,7 +262,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
         </script>
     </body>
 </html>
-  ```
+```
 
 
 ### To build and run the solution
 
@@ -73,10 +73,10 @@ In this article you add a custom content type to the Employee Orientation ShareP
 
 11. There are already  **FieldRef** elements in the file for the two columns that you added. Add **FieldRef** elements for two built-in SharePoint columns as peers of the two that are already there. The following is the markup for the elements. *You must use these same GUIDs for the ID attribute because these are built-in field types with fixed IDs.*  Add these *above*  the two **FieldRef** elements for the custom site columns.
 
-  ```
+```
   <FieldRef Name="LinkTitle" ID="{82642ec8-ef9b-478f-acf9-31f7d45fbc31}" DisplayName="Employee" />
 <FieldRef Name="Title" ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" DisplayName="Employee" />
-  ```
+```
 
 
     Note that we have given these fields a custom display name:  **Employee**.
@@ -118,25 +118,25 @@ In this article you add a custom content type to the Employee Orientation ShareP
 
 24. Still in the schema.xml file, in the  **View** element whose **BaseViewID** value is "1", find the child **ViewFields** element and then add the following two **FieldRef** elements as children of it. They may already be there, but missing an **ID** attribute. If so, add the ID attribute.
 
-  ```
+```
   <FieldRef Name="Division" ID="{GUID from the Field element}" />
 <FieldRef Name="OrientationStage" ID="{GUID from the Field element}" />
 
-  ```
+```
 
 25. Replace the two placeholder  **ID** attribute values with the GUIDs from the corresponding **Field** elements in the **ContentType** element for **NewEmployee** that is earlier in the schema.xml file. Don't forget the framing braces "{}".
 
     The  **ViewFields** for the "1" **View** should look like this. (Your GUIDs may be different.)
 
 
 
-  ```
+```
   <ViewFields>
    <FieldRef Name="LinkTitle" ID="{82642ec8-ef9b-478f-acf9-31f7d45fbc31}" DisplayName="Employee" />
    <FieldRef Name="Division" ID="{509d2d67-9a96-4596-9b3b-58449cdcc6ff}" />
    <FieldRef Name="OrientationStage" ID="{38a3b54c-acf3-4ddf-b748-55c7c28d4cc2}" />        
 </ViewFields>
-  ```
+```
 
 26. Still in the schema.xml file, find the  **View** element whose **BaseViewID** value is "0". find the **ViewFields** element with in it.
 
@@ -152,15 +152,15 @@ In this article you add a custom content type to the Employee Orientation ShareP
 
 30. Add two  **Field** elements to the first **Row** element, so that the **Row** element looks like the following.
 
-  ```
+```
   
 <Row>
   <Field Name="Title">Tom Higginbotham</Field>
   <Field Name="Division">Manufacturing</Field>
   <Field Name="OrientationStage">Tour of building</Field>
 </Row>
    
-  ```
+```
 
 31. Save and close the file.
 
 
@@ -47,28 +47,28 @@ In this article you add a help page to the Employee Orientation SharePoint Add-i
 
 3. Find the two  **asp:Content** elements in the file, and add the following third **asp:Content** markup in between them.
 
-  ```HTML
+```HTML
   <asp:Content ContentPlaceHolderID="PlaceHolderPageTitleInTitleArea" runat="server">
     Help
 </asp:Content> 
-  ```
+```
 
 4. Find the  **asp:Content** element with the ID of **PlaceholderAdditionalPageHead**, and add the following markup to it.
 
-  ```HTML
+```HTML
   <link rel="Stylesheet" type="text/css" href="../Content/App.css" />
-  ```
+```
 
 5. Find the  **asp:Content** element with the ID of **PlaceHolderMain**, and remove any child elements in it.
 
 
 6. Add the following as content to the same  **asp:Content** element.
 
-  ```HTML
+```HTML
   <H3>Having a problem with the add-in?</H3>
 <p> Call the help line for Fabrikam Add-ins:</p>
 <p>1-555-555-5555</p>
-  ```
+```
 
 7. Save and close the file.
 
@@ -78,11 +78,11 @@ In this article you add a help page to the Employee Orientation SharePoint Add-i
 
 9. Find the  **asp:Content** element with the ID of **PlaceHolderMain**, and then add the following markup to the end of it. 
 
-  ```HTML
+```HTML
   <p><asp:HyperLink runat="server" NavigateUrl="JavaScript:window.___location = _spPageContextInfo.webAbsoluteUrl + '/Pages/Help.aspx';" 
     Text="Get help for the Employee Orientation add-in" /></p>
 
-  ```
+```
 
 10. Save and close the file.
 
@@ -97,9 +97,9 @@ In this article you add a help page to the Employee Orientation SharePoint Add-i
 
 1. In  **Solution Explorer**, open the app.css file in the  **Contents** folder, and then add the following line to the file.
 
-  ```
+```
   p {color: green;}
-  ```
+```
 
 2. Save and close the file.
 
 
@@ -42,11 +42,11 @@ In this article you add a Web Part to the default page of the Employee Orientati
 
 3. Inside the same  **<asp:Content>** element, add the following **WebPartZone**. 
 
-  ```XML
+```XML
   <WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly" 
       ID="HomePage1" Title="loc:full" />
 
-  ```
+```
 
 4. Save and close the file.
 
@@ -59,7 +59,7 @@ In this article you add a Web Part to the default page of the Employee Orientati
 
 7. In the  **File** element, add a child **AllUsersWebPart** element and set its **WebPartZoneID** to the ID of the Web Part zone that you created on the page. The file's contents should now look like the following. This markup tells SharePoint to insert an **AllUsersWebPart** into the Web Part zone that is named "HomePage1".
 
-  ```
+```
   <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
   <Module Name="Pages">
     <File Path="Pages\Default.aspx" Url="Pages/Default.aspx" ReplaceContent="TRUE" >
@@ -70,23 +70,23 @@ In this article you add a Web Part to the default page of the Employee Orientati
   </Module>
 </Elements>
 
-  ```
+```
 
 8. Add a  **CDATA** element as a child of the **AllUsersWebPart**, then add a  **webParts** element as a child of the **CDATA**, as shown in the following markup. 
 
-  ```
+```
   <AllUsersWebPart WebPartZoneID="HomePage1" WebPartOrder="1">
   <![CDATA[
     <webParts>
 
     </webParts>
   ]]>
 </AllUsersWebPart>
-  ```
+```
 
 9. Add the following  **webPart** markup as a child of the **webParts** element. This markup adds an **XsltListViewWebPart** and tells the Web Part to show theNew Employees in Seattle list. Note that the **ViewContentTypeId** property value is just "0x", not the actual ID of theNewEmployee content type.
 
-  ```
+```
   
   <webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
     <metaData>
@@ -106,7 +106,7 @@ In this article you add a Web Part to the default page of the Employee Orientati
       </properties>
     </data>
   </webPart>
-  ```
+```
 
 
 ## Run and test the add-in
 
@@ -39,7 +39,7 @@ In this article we get back to coding by adding some site columns to the Employe
 
 4. In the elements.xml file for the new site column, edit the  **Field** element so that it has the attributes and values shown in the following example, except that *you should  **not** change the GUID*  for the **ID** attribute from the value that Visual Studio generated for it, *so be careful if you are using copy-and-paste*  .
 
-  ```
+```
   <Field ID="{generated GUID}" 
        Name="Division" 
        Title="Division" 
@@ -49,14 +49,14 @@ In this article we get back to coding by adding some site columns to the Employe
        Type="Text" 
        Required ="FALSE">
 </Field>
-  ```
+```
 
 5. Add another  **Site Column** to the same folder namedOrientationStage.
 
 
 6. In the elements.xml file for the new site column, edit the  **Field** element so that it has the attributes and values shown in the following example, except that you should not change the GUID for the **ID** attribute from the value that Visual Studio generated for it.
 
-  ```
+```
   <Field ID="{generated GUID}" 
        Name="OrientationStage" 
        Title="OrientationStage"
@@ -66,11 +66,11 @@ In this article we get back to coding by adding some site columns to the Employe
        Type="Choice"
        Required ="TRUE">
 </Field>
-  ```
+```
 
 7. Because this is a Choice field, you must specify the possible choices and the order in which they should appear in the drop-down list when a user is making a choice. And because it is a required field, you must specify a default value. Add the following child markup to the  **Field** element.
 
-  ```
+```
   <CHOICES>
       <CHOICE>Not Started</CHOICE>
       <CHOICE>Tour of building</CHOICE>
@@ -86,7 +86,7 @@ In this article we get back to coding by adding some site columns to the Employe
       <MAPPING Value="5">Completed</MAPPING>
 </MAPPINGS>
 <Default>Not Started</Default>
-  ```
+```
 
 8. Save all files.