diff --git hadoop-project/src/site/site.xml hadoop-project/src/site/site.xml
index 57cff9a2648..be48ddbac80 100644
--- hadoop-project/src/site/site.xml
+++ hadoop-project/src/site/site.xml
@@ -128,6 +128,7 @@
+
@@ -143,7 +144,6 @@
-
diff --git hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceProfiles.md hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceProfiles.md
deleted file mode 100644
index d422ab685f8..00000000000
--- hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/ResourceProfiles.md
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-Hadoop: YARN Resource Profiles
-==============================
-
-Overview
---------
-Resource profiles support in YARN helps to extend the YARN resource model to a more flexible model which makes it easier to add new countable resourcetypes. This solution also helps the users to submit jobs with ease to specify the resources they need.
-
-Resource model of YARN
------------------------
-Resource Manager will load a new configuration file named `resource-types.xml` to determine the set of resource types for which scheduling is enabled. Sample XML will look like below.
-
-```xml
-
-
- yarn.resource-types
- resource1, resource2
-
-
-
- yarn.resource-types.resource1.units
- G
-
-
-```
-
-Similarly, a new configuration file `node-resources.xml` will also be loaded by Node Manager where the resource capabilities of a node can be specified.
-
-```xml
-
-
- yarn.nodemanager.resource-type.resource1
- 5G
-
-
-
- yarn.nodemanager.resource-type.resource2
- 2m
-
-
-
-```
-
-Node Manager will use these custom resource types and will register it's capability to Resource Manager.
-
-Resource Profiles
------------------
-As per the updated resource model of YARN, specifying and configuring additional resource types for container allocation request will become more cumbersome. With the support of resource profiles, such requests could be placed by using simple profile names which has defined meaning from YARN.
-
-Admin could specify `resource-profiles.json` which indicates various profiles supported.
-
-```json
-{
- "minimum": {
- "memory-mb" : 1024,
- "vcores" : 1
- },
- "default" : {
- "memory-mb" : 2048,
- "vcores" : 2
- },
- "maximum" : {
- "memory-mb": 4096,
- "vcores" : 4
- },
- "http" : {
- "memory-mb" : 2048,
- "vcores" : 2
- }
-}
-```
-This indicates that profile named "minimum", "default", "maximum" and "http" is supported. Clients could easily use this name instead of specifying each resource details.
-
-Configurations
--------------
-
-*In `yarn-site.xml`*
-
-| Configuration Property | Description |
-|:---- |:---- |
-| `yarn.resourcemanager.resource-profiles.enabled` | *(Required)* In the server side it indicates whether resource profiles support is enabled or not. Defaults to `false`. |
-
-Please note that, `resource-types.xml` and `node-resources.xml` file also need to be placed in conf directory if new resources are to be added to YARN.
-
-*In `resource-types.xml`*
-
-| Configuration Property | Value | Description |
-|:---- |:---- |:---- |
-| `yarn.resource-types` | resource1 | Custom resource |
-| `yarn.resource-types.resource1.units` | G | Default unit for resource1 type |
-
-*In `node-resources.xml`*
-
-| Configuration Property | Value | Description |
-|:---- |:---- |:---- |
-| `yarn.nodemanager.resource-type.resource1` | 5G | Resource capability for resource named 'resource1'. |
-
-Use it
---------
-Distributed Shell is supporting this feature and user could specify a resource profile name which YARN is supporting while running a DS application.