fixing asterisk format mistakes

Author: davidchesnut

docs/general-development/accessing-the-soap-api.md

@@ -52,7 +52,7 @@ The following table describes each element in the URL.
 
 
 
-|****URL element****|****Description****|
+|**URL element**|**Description**|
 |:-----|:-----|
 | _server_ <br/> |The name of the server on which Microsoft SharePoint Server 2010 is deployed.  <br/> |
 | _customsite_ <br/> |A custom SharePoint Server 2010 site that the server administrator creates.  <br/> |

docs/general-development/bdc-model-schema-reference-for-sharepoint.md

@@ -299,7 +299,7 @@ The following sections describe attributes, child elements, and parent elements.
 
 
 
-|****Element****|**Description**|
+|**Element**|**Description**|
 |:-----|:-----|
 | [ActionParameters Element in Action (BDCMetadata Schema)](http://msdn.microsoft.com/library/e14df901-621c-1851-db78-e99fd3cf31ae%28Office.15%29.aspx) <br/> |The **ActionParameters** element that contains this **ActionParameter**.  <br/> |
 
@@ -1032,11 +1032,11 @@ The following sections describe attributes, child elements, and parent elements.
 
 |**Attribute**|**Description**|
 |:-----|:-----|
-|**Namespace** <br/> |Required.  <br/> The namespace that this external content type belongs to.  <br/> Attribute type: **String** <br/> **Note:** The namespace should not contain the asterisk special character " *****".           |
+|**Namespace** <br/> |Required.  <br/> The namespace that this external content type belongs to.  <br/> Attribute type: **String** <br/> **Note:** The namespace should not contain the asterisk special character " **\***".           |
 |**Version** <br/> |Required.  <br/> The version number of this external content type.  <br/> Attribute type: **String** <br/> **Caution:** When the BDC model changes, you must increase the version number of the external content type. If the structure of an external content type changes, you should increase the major number. Examples of structural changes include adding a field to a **SpecificFinder** or changing an identifier field. If the change does not affect the structure of the external content type, for example, when adding a creator method, changing connection information, or when changing names of **LobSystems** and type descriptors, you should change the build number and revision number.          |
 |**EstimatedInstanceCount** <br/> |Optional.  <br/> The estimated number of external items contained by the external system.  <br/> Default value: 10000  <br/> Attribute type: **Integer** <br/> |
 |**DefaultOperationMode** <br/> |Optional.  <br/> Specifies the default behavior when interacting with the external system while creating, deleting, updating, or reading external items.  <br/> Default value: Default  <br/> The following table lists the possible values for this attribute.  <br/> <table width="50%" cellspacing="2" cellpadding="5" frame="lhs"><thead><tr><th><p>Value</p></th><th><p>Description</p></th></tr></thead><tbody><tr><td><p>Online</p></td><td><p>Bypass the cached external items for all operations and interact with the external system directly.</p></td></tr><tr><td><p>Cached</p></td><td><p>Perform <b>Create</b>, <b>Read</b>, <b>Update</b>, and <b>Delete</b> operations directly against the cached external items. For <b>Read</b> operations, if the requested external items are available in the cache, use the external items in the cache. Otherwise, bypass the cache to obtain the external items from the external system, and put it in the cache for later use.</p></td></tr><tr><td><p>Offline</p></td><td><p>Perform <b>Create</b>, <b>Read</b>, <b>Update</b>, and <b>Delete</b> operations against only the cached external items.</p></td></tr><tr><td><p>Default</p></td><td><p>Use the System default behavior. This uses Cached mode if the environment supports caching external items.</p></td></tr></tbody></table>|
-|Name  <br/> |Required.  <br/> The name of the external content type.  <br/> Attribute type: **String** <br/> **Note:** The name of an external content type should not contain the asterisk special character " *****".           |
+|Name  <br/> |Required.  <br/> The name of the external content type.  <br/> Attribute type: **String** <br/> **Note:** The name of an external content type should not contain the asterisk special character " **\***".           |
 |DefaultDisplayName  <br/> |Optional.  <br/> The default display name of the external content type.  <br/> Attribute type: **String** <br/> |
 |IsCached  <br/> |Optional.  <br/> Specifies whether this external content type will be frequently used. If set to true, Business Data Connectivity (BDC) service will cache this external content type in memory.  <br/> Default value: **true** <br/> Attribute type: **Boolean** <br/> |
 

docs/general-development/claims-based-identity-term-definitions.md

@@ -16,7 +16,7 @@ Table 1 contains definitions of key terms related to claims-based identity.
 **Table 1. Definitions of terms related to claims-based identity**
 
 
-|****Term****|****Definition****|
+|**Term**|**Definition**|
 |:-----|:-----|
 |Claim  <br/> |A statement that one subject makes about itself or another subject. For example, the statement can be about a name, identity, key, group, privilege, or capability. Claims are issued by a provider, and they are given one or more values and then packaged in security tokens that are issued by a security token service (STS). They are also defined by a claim value type and, possibly, associated metadata.  <br/> |
 |Claim name  <br/> |A user-friendly name for the claim type.  <br/> |

docs/general-development/configuration-administration-and-resources-in-sharepoint.md

@@ -75,7 +75,7 @@ The following tables list blogs, forums, and additional resources about claims-b
 **Table 1. Blogs**
 
 
-|****Blog Name****|****Links****|
+|**Blog Name**|**Links**|
 |:-----|:-----|
 |Share-n-dipity  <br/> | [Blog home page](http://blogs.technet.com/speschka/) <br/> |
 |Microsoft SharePoint Developer Team Blog  <br/> | [Blog home page](http://blogs.msdn.com/b/sharepointdev/) <br/> |
@@ -85,15 +85,15 @@ The following tables list blogs, forums, and additional resources about claims-b
 **Table 2. Forums**
 
 
-|****Forum Name****|****Links****|
+|**Forum Name**|**Links**|
 |:-----|:-----|
 |SharePoint Products and Technologies Forums  <br/> | [Forum home page](http://social.msdn.microsoft.com/Forums/en-US/category/sharepoint) <br/> |
 
 
 **Table 3. Additional resources**
 
 
-|****Additional Resources****|****Links****|
+|**Additional Resources**|**Links**|
 |:-----|:-----|
 |Claims and Security: Technical Articles Node  <br/> | [Claims and security: Technical articles and code samples on MSDN](http://msdn.microsoft.com/en-us/library/gg430136.aspx) <br/> |
 |||

docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md

@@ -177,7 +177,7 @@ The first step is preparing our SharePoint site with document libraries that our
 
 
 
-   ****
+   
 
 
 

docs/general-development/excel-services-blogs-forums-and-resources.md

@@ -17,22 +17,22 @@ The following are links to blogs, forums, and additional resources related to Ex
 
 
 
-|****Blog Name****|****Links****|
+|**Blog Name**|**Links**|
 |:-----|:-----|
 |Cum Grano Salis  <br/> | [Home page](http://blogs.msdn.com/cumgranosalis/) <br/>  [Excel Services page](http://blogs.msdn.com/cumgranosalis/archive/category/12700.aspx) <br/> |
 |Microsoft Excel 2010: The official blog of the Microsoft Excel product team  <br/> | [Home page](http://blogs.msdn.com/excel) <br/>  [Excel Online page](http://blogs.msdn.com/excel/archive/2010/01/21/collaborative-editing-using-excel-web-app.aspx) <br/> |
 |Microsoft Office Web Apps: The official blog of the Microsoft Office Online team  <br/> | [Home page](http://blogs.msdn.com/officewebapps/default.aspx) <br/> |
 
 
 
-|****Forum Name****|****Links****|
+|**Forum Name**|**Links**|
 |:-----|:-----|
 |SharePoint - Excel Services  <br/> | [Excel Services forum home page](http://social.msdn.microsoft.com/Forums/en-US/sharepointexcel/threads) <br/> |
 |SharePoint Products and Technologies  <br/> | [List of SharePoint Products and Technologies forums](http://social.msdn.microsoft.com/forums/en-US/category/sharepoint) <br/> |
 
 
 
-|****Additional Resources****|****Links****|
+|**Additional Resources**|**Links**|
 |:-----|:-----|
 |Excel Services Resource Center  <br/> | [Excel Services Resource Center on MSDN](http://msdn.microsoft.com/en-us/office/bb203828.aspx) <br/> |
 |IT Pro \\ Administration Documentation  <br/> | [TechNet](http://technet.microsoft.com/en-us/library/ee424401%28office.14%29.aspx) <br/> |

docs/general-development/excel-services-error-codes.md

@@ -30,7 +30,7 @@ The following table lists the error codes for Excel Web Services alerts and the
 
 
 
-|****Error Code****|****Message****|****Explanation****|****Resolution****|
+|**Error Code**|**Message**|**Explanation**|**Resolution**|
 |:-----|:-----|:-----|:-----|
 |ApiInvalidArgument  <br/> |Invalid value to argument: {0}  <br/> |An invalid value for an argument was passed into the API call.  <br/> 0 = name of the argument. Its value is invalid.  <br/> |Use a valid value for the argument.  <br/> |
 |ApiInvalidCoordinate  <br/> |The {0} coordinate of {1} is invalid.  <br/> |0 = coordinate name (row, column, height, width).  <br/> 1 = name of the argument, which holds the coordinate structure.  <br/> The contents of the **RangeCoordinates** class or the row\\column\\height\\width parameters on a get or set call are invalid. <br/> |Use valid coordinate values for the argument.  <br/> |

docs/general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md

@@ -69,7 +69,7 @@ The Excel Services implementation of OData supports a number of the standard ODa
 **Table 1. Excel Services OData system query options**
 
 
-|****System Query Option****|****Description****|
+|**System Query Option**|**Description**|
 |:-----|:-----|
 |/\<tableName\>  <br/> |Returns all rows for the table specified by \<tableName\>, where \<tableName\> is the name of a table in an Excel workbook that contains the rows that you want to retrieve.  <br/> **Important:** This form of OData request returns no more than 500 rows at a time. Each set of 500 rows is one page. To get rows in further pages in a table that has more than 500 rows, use the **$skiptoken** query option (see below).<br/>The following example returns all rows up to the 500th row in Table1 in the ProductSales.xlsx workbook.  <br/> |
 |**$metadata** <br/> |Returns all the available tables and the type information for all rows in each table in the specified workbook.  <br/> The following example returns the tables and type information for the tables in the ProductSales.xlsx workbook.  <br/> http://contoso1/_vti_bin/ExcelRest.aspx/Documents/ProductSales.xlsx/OData/$metadata  <br/> |

docs/general-development/resources-uri-for-excel-services-rest-api.md

@@ -77,7 +77,7 @@ Table 1 shows all the accessible resources in the Excel Services REST API. To ac
 **Table 1. Accessible resources in the Excel Services REST API**
 
 
-|****Resource Location****|****Format****|****Example****|****Notes****|
+|**Resource Location**|**Format**|**Example**|**Notes**|
 |:-----|:-----|:-----|:-----|
 |/model  <br/> |Atom (default)  <br/> |/model  <br/> |Returns an Atom feed with the resources supported by the Excel Services REST API. The supported resources are ranges, charts, tables, and PivotTables.  <br/> |
 |/model  <br/> |workbook  <br/> |/model?$format=workbook  <br/> |This is the workbook. Supported workbook formats are xlsx, xlsb, and xlsm.  <br/> |

docs/general-development/sharepoint-server-application-lifecycle-management.md

@@ -7,12 +7,12 @@ ms.assetid: caaf9a09-2e6a-49e3-a8d6-aaf7f93a842a
 
 # SharePoint Application Lifecycle Management
 Applies common application lifecycle management (ALM) concepts and practices to application development using SharePoint technologies.
- * **Provided by: *** Eric Charran, Microsoft Corporation
+ **Provided by:** Eric Charran, Microsoft Corporation
 
 
 
 
- * **Contributors:*** Vesa Juvonen, Microsoft Corporation | Steve Peschka, Microsoft Corporation
+**Contributors:** Vesa Juvonen, Microsoft Corporation | Steve Peschka, Microsoft Corporation