Correcting table

Author: Kraig Brockschmidt

docs/Schema/packages-config.md

@@ -38,7 +38,7 @@ The schema is simple: following the standard XML header is a single `<packages>`
 
 | Attribute | Required | Description |
 | --- | --- | --- |
-| id | Yes | |The identifier of the package, such as Newtonsoft.json or Microsoft.AspNet.Mvc. | 
+| id | Yes | The identifier of the package, such as Newtonsoft.json or Microsoft.AspNet.Mvc. | 
 | version | Yes | The exact version of the package to install, such as 3.1.1 or 4.2.5.11-beta. A version string must have at least three numbers; a fourth is optional, as is a pre-release suffix. Ranges are not allowed. | 
 | targetFramework | No | The [target framework moniker (TFM)](Target-Frameworks.md) to apply when installing the package. This is initially set to the project's target when a package is installed. As a result, different `<package>` elements can have different TFMs. For example, if you create a project targeting .NET 4.5.2, packages installed at that point will use the TFM of net452. If you ;later retarget the project to .NET 4.6 and add more packages, those will use TFM of net46. A mismatch between the project's target and `targetFramework` attributes will generate warnings, in which case you can reinstall the affected packages. | 
 | allowedVersions | No | A range of allowed versions for this package in case the specific value in `version` cannot be found. |