From d910bc9c9ced2e1072dbcfaf182ac8455c9caab4 Mon Sep 17 00:00:00 2001
From: David Chesnut <davech@microsoft.com>
Date: Sun, 24 Sep 2017 12:04:35 -0700
Subject: [PATCH] merged changes from docs migration

---
 .openpublishing.build.ps1                     |   17 +
 .openpublishing.publish.config.json           |   54 +
 LICENSE                                       |  395 ++++++
 LICENSE-CODE                                  |   17 +
 ThirdPartyNotices                             |   15 +
 ...rations-using-sharepoint-rest-endpoints.md |   11 +-
 ...e-sharepoint-rest-service-endpoint-uris.md |   21 +-
 ...get-to-know-the-sharepoint-rest-service.md |    9 +-
 .../make-batch-requests-with-the-rest-apis.md |    7 +
 ...ructure-represented-in-the-rest-service.md |    7 +
 ...s-on-a-list-by-using-the-rest-interface.md |    9 +-
 ...sharepoint-items-using-the-rest-service.md |    7 +
 ...a-file-by-using-the-rest-api-and-jquery.md |    9 +-
 ...-operations-in-sharepoint-rest-requests.md |    9 +-
 ...orking-with-folders-and-files-with-rest.md |   21 +-
 ...ing-with-lists-and-list-items-with-rest.md |    7 +
 docs/apis/webhooks/get-started-webhooks.md    |   13 +-
 .../webhooks/lists/create-subscription.md     |    9 +-
 .../webhooks/lists/delete-subscription.md     |    7 +
 docs/apis/webhooks/lists/get-subscription.md  |    7 +
 .../overview-sharepoint-list-webhooks.md      |   17 +-
 .../webhooks/lists/update-subscription.md     |    7 +
 .../webhooks/overview-sharepoint-webhooks.md  |   11 +-
 ...arepoint-webhooks-using-azure-functions.md |   29 +-
 .../webhooks-reference-implementation.md      |   25 +-
 docs/breadcrumb/toc.yml                       |    3 +
 docs/docfx.json                               |   55 +
 ...oint-from-mobile-and-native-device-apps.md |    9 +-
 .../accessibility-in-sharepoint.md            |    7 +-
 .../general-development/accessing-a-schema.md |    5 +-
 .../accessing-the-soap-api.md                 |   13 +-
 ...ed-external-content-types-in-sharepoint.md |   23 +-
 .../add-sharepoint-capabilities.md            |   31 +-
 ...vanced-scenarios-and-additional-samples.md |    3 +-
 ...ne-sharepoint-list-application-template.md |   11 +-
 ...uthorization-and-security-in-sharepoint.md |   27 +-
 ...oups-and-the-object-model-in-sharepoint.md |   17 +-
 .../basic-uri-structure-and-path.md           |   11 +-
 ...t-object-model-reference-for-sharepoint.md |   15 +-
 .../bcs-rest-api-reference-for-sharepoint.md  |    9 +-
 ...c-model-schema-reference-for-sharepoint.md |   19 +-
 .../build-farm-solutions-in-sharepoint.md     |   13 +-
 ...phone-based-on-the-sharepoint-templates.md |    7 +-
 ...ps-for-other-platforms-using-sharepoint.md |   13 +-
 ...uild-reusable-components-for-sharepoint.md |   13 +-
 .../build-sites-for-sharepoint.md             |   31 +-
 ...ndows-phone-apps-that-access-sharepoint.md |   51 +-
 .../building-search-queries-in-sharepoint.md  |   11 +-
 ...ess-connectivity-services-in-sharepoint.md |   33 +-
 ...es-programmers-reference-for-sharepoint.md |   19 +-
 ...-in-the-bdc-model-schema-for-sharepoint.md |   15 +-
 .../choose-the-right-api-set-in-sharepoint.md |   13 +-
 ...sed-identity-and-concepts-in-sharepoint.md |    9 +-
 .../claims-based-identity-in-sharepoint.md    |   15 +-
 .../claims-based-identity-term-definitions.md |   11 +-
 .../claims-provider-in-sharepoint.md          |   15 +-
 .../code-samples-for-sharepoint.md            |    5 +-
 .../color-palettes-and-fonts-in-sharepoint.md |   15 +-
 ...ages-in-sharepoint-workflow-development.md |    9 +-
 ...inistration-and-resources-in-sharepoint.md |   13 +-
 .../configure-search-in-sharepoint.md         |   11 +-
 ...operability-services-cmis-in-sharepoint.md |   11 +-
 .../content-search-web-part-in-sharepoint.md  |    9 +-
 ...for-the-geolocation-field-in-sharepoint.md |   25 +-
 ...t-workflow-app-using-visual-studio-2012.md |   61 +-
 ...issions-by-using-the-sharepoint-workflo.md |   39 +-
 .../create-associations-in-sharepoint.md      |    7 +-
 ...hybrid-connectivity-apps-for-sharepoint.md |   11 +-
 .../create-sharepoint-no-code-solutions.md    |   11 +-
 ...arepoint-designer-and-the-sharepoint-wo.md |   15 +-
 .../cross-site-publishing-in-sharepoint.md    |    9 +-
 ...-content-enrichment-web-service-callout.md |   11 +-
 ...rimming-for-search-in-sharepoint-server.md |    9 +-
 ...stom-word-breakers-in-sharepoint-server.md |    5 +-
 ...dels-to-improve-relevance-in-sharepoint.md |   25 +-
 ...ustomizing-search-results-in-sharepoint.md |    3 +-
 .../debugging-sharepoint-server-workflows.md  |   25 +-
 ...epoint-add-ins-and-sharepoint-solutions.md |    5 +-
 .../develop-access-web-apps.md                |    7 +-
 ...harepoint-workflows-using-visual-studio.md |    9 +-
 .../develop-the-site-design-in-sharepoint.md  |   17 +-
 .../developing-with-duet-enterprise-2-0.md    |    7 +-
 .../discovery-in-excel-services-rest-api.md   |   15 +-
 .../ediscovery-in-sharepoint.md               |    7 +-
 ...bdc-model-file-for-search-in-sharepoint.md |    7 +-
 .../excel-services-alerts.md                  |   15 +-
 .../excel-services-architecture.md            |   21 +-
 .../excel-services-best-practices.md          |   17 +-
 ...cel-services-blogs-forums-and-resources.md |   17 +-
 .../excel-services-development-roadmap.md     |   33 +-
 ...-services-ecmascript-javascript-jscript.md |   11 +-
 .../excel-services-ecmascript-overview.md     |    5 +-
 .../excel-services-error-codes.md             |   15 +-
 .../excel-services-in-sharepoint.md           |   27 +-
 .../excel-services-known-issues-and-tips.md   |   27 +-
 .../excel-services-overview.md                |   33 +-
 .../excel-services-rest-api-overview.md       |    5 +-
 .../excel-services-rest-api.md                |   23 +-
 .../excel-services-user-defined-functions.md  |   19 +-
 docs/general-development/excel-web-access.md  |    9 +-
 .../general-development/excel-web-services.md |   27 +-
 ...ch-configuration-settings-in-sharepoint.md |    5 +-
 ...ort-feature-in-word-automation-services.md |    3 +-
 .../external-content-types-in-sharepoint.md   |   19 +-
 ...xternal-events-and-alerts-in-sharepoint.md |   23 +-
 ...ast-query-language-fql-syntax-reference.md |   77 +-
 .../follow-content-in-sharepoint.md           |   39 +-
 .../follow-people-in-sharepoint.md            |   39 +-
 ...ntent-rest-api-reference-for-sharepoint.md |   21 +-
 ...ked-questions-about-excel-services-udfs.md |   23 +-
 .../general-development/general-guidelines.md |   17 +-
 ...ping-with-social-features-in-sharepoint.md |   67 +-
 ...-model-with-external-data-in-sharepoint.md |   21 +-
 ...ess-connectivity-services-in-sharepoint.md |   41 +-
 ...et-started-with-workflows-in-sharepoint.md |   25 +-
 ...ner-for-workflow-in-sharepoint-designer.md |   15 +-
 ...anges-using-atom-feed-and-html-fragment.md |   17 +-
 .../getting-started-with-excel-services.md    |   15 +-
 ...cess-an-external-data-source-from-a-udf.md |   23 +-
 ...s-external-data-with-rest-in-sharepoint.md |   11 +-
 ...ice-channel-panel-snippet-in-sharepoint.md |   15 +-
 ...o-a-list-programmatically-in-sharepoint.md |   17 +-
 ...d-a-security-trim-snippet-in-sharepoint.md |    9 +-
 ...d-a-web-part-zone-snippet-in-sharepoint.md |   15 +-
 ...n-edit-mode-panel-snippet-in-sharepoint.md |   15 +-
 ...y-a-master-page-to-a-site-in-sharepoint.md |   11 +-
 ...ply-styles-to-page-fields-in-sharepoint.md |   19 +-
 ...rottled-or-blocked-in-sharepoint-online.md |   25 +-
 ...service-application-in-sharepoint-using.md |    3 +-
 ...estore-sharepoint-using-a-vss-requestor.md |    5 +-
 ...and-snippets-by-using-css-in-sharepoint.md |   17 +-
 ...uild-and-deploy-workflow-custom-actions.md |   19 +-
 ...th-the-navigation-and-event-logging-res.md |   17 +-
 .../how-to-catch-exceptions.md                |   19 +-
 ...eview-page-in-sharepoint-design-manager.md |   15 +-
 ...ications-in-sharepoint-apps-for-windows.md |   19 +-
 ...igure-item-level-security-in-sharepoint.md |    7 +-
 ...configure-msmq-for-sharepoint-workflows.md |    7 +-
 ...-external-content-type-to-tenant-scoped.md |   11 +-
 ...l-file-into-a-master-page-in-sharepoint.md |   25 +-
 ...ed-external-content-types-in-sharepoint.md |    5 +-
 ...inary-large-objects-blobs-in-sharepoint.md |    7 +-
 ...-create-a-claims-provider-in-sharepoint.md |   11 +-
 ...uses-an-embedded-workbook-and-bing-maps.md |    3 +-
 ...-master-page-preview-file-in-sharepoint.md |   23 +-
 ...ate-a-minimal-master-page-in-sharepoint.md |   21 +-
 ...oint-that-contains-data-from-an-externa.md |   25 +-
 ...w-to-create-a-page-layout-in-sharepoint.md |   21 +-
 ...o-create-a-udf-that-calls-a-web-service.md |   23 +-
 ...a-vss-requestor-for-use-with-sharepoint.md |    9 +-
 ...ate-a-windows-phone-sharepoint-list-app.md |   21 +-
 ...ped-external-content-type-in-sharepoint.md |   13 +-
 ...type-from-an-odata-source-in-sharepoint.md |   19 +-
 ...sing-an-odata-data-source-in-sharepoint.md |   19 +-
 ...ervice-for-use-as-a-bcs-external-system.md |   21 +-
 ...ve-the-social-feed-by-using-the-javascr.md |   27 +-
 ...ve-the-social-feed-by-using-the-net-cli.md |   23 +-
 ...er-workflow-forms-with-visual-studio-20.md |   35 +-
 ...tent-types-for-sql-server-in-sharepoint.md |    7 +-
 .../how-to-create-external-event-receivers.md |   17 +-
 ...performancepoint-services-in-sharepoint.md |    9 +-
 ...performancepoint-services-in-sharepoint.md |    8 +-
 ...performancepoint-services-in-sharepoint.md |    9 +-
 ...performancepoint-services-in-sharepoint.md |   11 +-
 ...rformancepoint-services-in-sharepoint-2.md |    6 +
 ...harepoint-workflows-using-visual-studio.md |   31 +-
 ...-for-performancepoint-services-in-share.md |   15 +-
 ...rs-for-performancepoint-services-in-sha.md |    9 +-
 ...-field-type-using-client-side-rendering.md |   23 +-
 ...-and-filter-data-for-windows-phone-apps.md |   15 +-
 ...-for-a-catalog-based-site-in-sharepoint.md |   49 +-
 ...of-a-sharepoint-list-app-for-windows-ph.md |   19 +-
 ...-deploy-a-claims-provider-in-sharepoint.md |   11 +-
 ...-to-deploy-a-custom-theme-in-sharepoint.md |   13 +-
 ...s-using-sharepoint-foundation-solutions.md |   21 +-
 ...-detect-the-installed-sku-of-sharepoint.md |    9 +-
 ...documents-in-posts-in-sharepoint-server.md |   17 +-
 .../general-development/how-to-enable-udfs.md |   25 +-
 ...a-document-library-list-to-a-mobile-app.md |   11 +-
 ...-field-type-using-client-side-rendering.md |   29 +-
 ...g-the-net-client-object-model-in-sharep.md |   15 +-
 ...-using-the-rest-service-in-sharepoint-2.md |   29 +-
 ...e-javascript-object-model-in-sharepoint.md |   15 +-
 ...e-net-client-object-model-in-sharepoint.md |   13 +-
 ...to-get-an-entire-workbook-or-a-snapshot.md |   17 +-
 .../how-to-get-values-from-ranges.md          |   13 +-
 ...validation-in-a-windows-phone-app-for-s.md |   21 +-
 ...-sites-and-documents-in-posts-in-sharep.md |   11 +-
 ...windows-phone-apps-and-sharepoint-lists.md |   23 +-
 ...ial-feed-by-using-the-net-client-object.md |   13 +-
 ...ial-feed-by-using-the-rest-service-in-s.md |   15 +-
 ...xcel-webui-dll-and-microsoft-office-exc.md |   11 +-
 ...custom-css-files-themable-in-sharepoint.md |   25 +-
 ...e-to-the-sharepoint-master-page-gallery.md |   13 +-
 ...-an-excel-web-access-web-part-to-a-page.md |   13 +-
 .../how-to-refresh-data.md                    |   19 +-
 ...gs-when-previewing-a-page-in-sharepoint.md |   13 +-
 ...ct-udf-code-access-security-permissions.md |   17 +-
 ...-to-retrieve-the-url-of-a-pages-library.md |    5 +-
 ...by-using-the-javascript-object-model-in.md |   19 +-
 ...by-using-the-net-client-object-model-in.md |   13 +-
 ...to-save-from-excel-client-to-the-server.md |   17 +-
 ...rver-to-prepare-for-programmatic-access.md |   21 +-
 ...at-the-web-and-farm-level-in-sharepoint.md |    9 +-
 ...r-developing-mobile-apps-for-sharepoint.md |    9 +-
 .../how-to-set-values-of-ranges.md            |   15 +-
 .../how-to-set-various-credentials.md         |   17 +-
 ...-specify-a-range-address-and-sheet-name.md |   15 +-
 ...harepoint-list-items-on-a-windows-phone.md |   19 +-
 ...oint-field-types-for-windows-phone-apps.md |   15 +-
 .../how-to-trust-a-location.md                |   13 +-
 ...er-for-sharepoint-server-search-results.md |    7 +-
 ...s-to-navigation-term-sets-in-sharepoint.md |    7 +-
 ...sharepoint-lists-in-a-windows-phone-app.md |   17 +-
 ...-sap-reporting-with-duet-enterprise-2-0.md |    9 +-
 ...e-sap-workflow-with-duet-enterprise-2-0.md |    3 +-
 ...y-to-access-external-data-in-sharepoint.md |   13 +-
 ...loseworkbook-method-call-asynchronously.md |   23 +-
 ...b-service-callout-for-sharepoint-server.md |    9 +-
 ...subcode-property-to-capture-error-codes.md |   21 +-
 ...zation-profiles-by-using-the-server-obj.md |   21 +-
 .../how-tos-for-sharepoint.md                 |  143 +-
 ...incoming-claims-signing-into-sharepoint.md |   11 +-
 ...ion-and-map-functionality-in-sharepoint.md |   19 +-
 ...ascript-user-defined-functions-overview.md |    9 +-
 ...ord-query-language-kql-syntax-reference.md |    9 +-
 ...support-for-windows-phone-in-sharepoint.md |   11 +-
 ...loop-back-soap-calls-and-direct-linking.md |   11 +-
 ...hine-translation-services-in-sharepoint.md |   13 +-
 ...d-metadata-and-navigation-in-sharepoint.md |   11 +-
 .../managed-navigation-in-sharepoint.md       |   10 +-
 ...-gallery-and-page-layouts-in-sharepoint.md |   29 +-
 ...-designer-version-with-the-farm-version.md |    7 +-
 .../minimal-download-strategy-overview.md     |   14 +-
 .../modify-sharepoint-components-for-mds.md   |   13 +-
 ...ice-and-sharepoint-application-services.md |   23 +-
 .../office-documentation-copyright-notice.md  |    3 +-
 ...optimize-page-performance-in-sharepoint.md |   23 +-
 .../optimize-sharepoint-site-accessibility.md |    7 +-
 ...verview-of-design-manager-in-sharepoint.md |   19 +-
 ...oint-and-the-volume-shadow-copy-service.md |   17 +-
 ...bile-client-authentication-object-model.md |   13 +-
 ...w-of-the-sharepoint-mobile-object-model.md |   11 +-
 .../overview-of-the-sharepoint-page-model.md  |   55 +-
 ...-application-templates-in-visual-studio.md |   15 +-
 ...performancepoint-services-in-sharepoint.md |   19 +-
 ...point-automation-services-in-sharepoint.md |    3 +-
 ...epoint-workflow-development-environment.md |   15 +-
 .../programming-models-in-sharepoint.md       |   27 +-
 ...deprecated-interface-in-sharepoint-2016.md |    3 +-
 .../publish-sharepoint-sites.md               |   11 +-
 .../query-refinement-in-sharepoint.md         |    3 +-
 ...reads-in-sharepoint-server-social-feeds.md |    7 +-
 ...g-excel-interactive-view-from-a-webpage.md |    5 +-
 ...data-from-sharepoint-server-using-odata.md |    5 +-
 ...sources-uri-for-excel-services-rest-api.md |    5 +-
 ...ggestions-using-the-search-rest-service.md |    9 +-
 ...lege-and-password-changes-in-sharepoint.md |   16 +-
 ...d-authentication-scenario-in-sharepoint.md |   16 +-
 .../sample-uri-for-excel-services-rest-api.md |    3 +-
 ...-upload-a-sharepoint-site-as-a-template.md |    7 +-
 .../search-add-ins-in-sharepoint.md           |   11 +-
 ...earch-connector-framework-in-sharepoint.md |   21 +-
 .../search-in-sharepoint.md                   |   49 +-
 ...hing-new-content-with-sharepoint-search.md |   17 +-
 ...-development-environment-for-sharepoint.md |    9 +-
 ...d-configure-sharepoint-workflow-manager.md |    5 +-
 ...pment-environment-for-bcs-in-sharepoint.md |   11 +-
 ...point-server-workflow-template-in-visio.md |   15 +-
 ...-ins-compared-with-sharepoint-solutions.md |    9 +-
 .../sharepoint-composites-handbook.md         |    3 +-
 ...anager-branding-and-design-capabilities.md |   21 +-
 ...arepoint-design-manager-design-packages.md |   15 +-
 ...arepoint-design-manager-device-channels.md |   27 +-
 ...epoint-design-manager-display-templates.md |   25 +-
 ...repoint-design-manager-image-renditions.md |   13 +-
 .../sharepoint-design-manager-snippets.md     |   13 +-
 .../sharepoint-development-overview.md        |   31 +-
 ...repoint-online-suite-navigation-control.md |    7 +-
 .../sharepoint-search-rest-api-overview.md    |   12 +-
 ...server-application-lifecycle-management.md |   39 +-
 .../sharepoint-vss-writer.md                  |   15 +-
 ...int-workflow-development-best-practices.md |   34 +-
 .../sharepoint-workflow-fundamentals.md       |   21 +-
 .../sharepoint-workflow-object-model.md       |    7 +-
 .../sharepoint-workflow-samples.md            |   11 +-
 ...nd-collaboration-features-in-sharepoint.md |   19 +-
 ...-feed-rest-api-reference-for-sharepoint.md |  117 +-
 .../sorting-search-results-in-sharepoint.md   |   20 +-
 .../step-1-creating-a-ecmascript-text-file.md |    3 +-
 ...ng-a-project-and-adding-a-udf-reference.md |   15 +-
 ...creating-the-web-service-client-project.md |   17 +-
 .../step-2-adding-a-web-reference.md          |   15 +-
 ...ent-editor-and-excel-services-web-parts.md |    5 +-
 .../step-2-creating-a-managed-code-udf.md     |   15 +-
 .../step-3-accessing-the-web-service.md       |   13 +-
 .../step-3-deploying-and-enabling-udfs.md     |   19 +-
 ...-4-building-and-testing-the-application.md |   13 +-
 ...p-4-testing-and-calling-udfs-from-cells.md |   19 +-
 .../supported-and-unsupported-features.md     |   15 +-
 ...f-interchange-file-format-in-sharepoint.md |    7 +-
 .../themes-overview-for-sharepoint.md         |   11 +-
 ...repoint-designer-and-visio-professional.md |   19 +-
 ...rigger-expressions-syntax-in-sharepoint.md |    9 +-
 ...ver-workflow-validation-errors-in-visio.md |   11 +-
 ...dination-actions-in-sharepoint-designer.md |   13 +-
 ...ctionary-actions-in-sharepoint-designer.md |   15 +-
 ...eventing-actions-in-sharepoint-designer.md |   21 +-
 .../understanding-excel-services-udfs.md      |   29 +-
 ...ckage-and-deploy-workflow-in-sharepoint.md |   19 +-
 ...ing-task-actions-in-sharepoint-designer.md |   17 +-
 ...ted-features-in-excel-services-rest-api.md |    3 +-
 ...ade-custom-themes-and-css-to-sharepoint.md |   27 +-
 ...rade-site-customizations-for-sharepoint.md |    5 +-
 .../upgrade-web-templates-for-sharepoint.md   |    5 +-
 .../urls-and-tokens-in-sharepoint.md          |    6 +-
 ...repoint-master-pages-when-upgrading-fro.md |    7 +-
 .../use-workflow-interop-for-sharepoint.md    |   21 +-
 .../user-segmentation-in-sharepoint.md        |    7 +-
 ...ess-connectivity-services-in-sharepoint.md |   21 +-
 ...-with-excel-services-rest-in-sharepoint.md |    7 +-
 ...iring-cmdlet-register-spworkflowservice.md |    3 +-
 .../using-the-sharepoint-search-query-apis.md |   11 +-
 ...visio-sharepoint-2010-workflow-platform.md |   51 +-
 ...ual-directories-in-sharepoint-solutions.md |    5 +-
 .../visio-services-in-sharepoint.md           |   19 +-
 ...a-quick-reference-guide-sharepoint-2010.md |  113 +-
 .../vss-requestors-and-sharepoint.md          |   17 +-
 ...om-application-using-excel-web-services.md |   23 +-
 ...lkthrough-developing-a-managed-code-udf.md |   19 +-
 ...oping-using-the-content-editor-web-part.md |   11 +-
 .../what-s-changed-in-sharepoint-designer.md  |    5 +-
 ...what-s-new-for-developers-in-sharepoint.md |   35 +-
 ...ollaboration-features-in-sharepoint-201.md |   13 +-
 .../what-s-new-in-access.md                   |    7 +-
 ...ess-connectivity-services-in-sharepoint.md |   21 +-
 .../what-s-new-in-excel-web-services.md       |    5 +-
 ...in-sharepoint-ediscovery-and-compliance.md |    5 +-
 ...new-in-sharepoint-search-for-developers.md |   15 +-
 ...word-automation-services-for-developers.md |    5 +-
 .../what-s-new-in-workflows-for-sharepoint.md |   23 +-
 ...-s-new-with-sharepoint-site-development.md |   43 +-
 .../work-with-social-feeds-in-sharepoint.md   |   61 +-
 .../work-with-user-profiles-in-sharepoint.md  |   29 +-
 ...and-activities-reference-for-sharepoint.md |   19 +-
 ...lable-using-the-workflow-interop-bridge.md |   13 +-
 ...rence-sharepoint-2010-workflow-platform.md |   23 +-
 ...-reference-sharepoint-workflow-platform.md |   21 +-
 ...workflow-activity-classes-in-sharepoint.md |    9 +-
 ...rence-sharepoint-2010-workflow-platform.md |   23 +-
 ...opment-in-sharepoint-designer-and-visio.md |   17 +-
 ...initiation-and-configuration-properties.md |    7 +-
 .../workflows-in-sharepoint.md                |   29 +-
 ...oint-workflows-using-visual-studio-2012.md |   41 +-
 ...-excel-services-javascript-object-model.md |    3 +-
 ...kflow-services-client-side-object-model.md |    9 +-
 ...int-workflows-using-sharepoint-designer.md |   21 +-
 ...oint-workflows-using-visual-studio-2012.md |   23 +-
 .../03780b79-aca8-44d1-b0bf-d80833d08627.PNG  |  Bin
 .../0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif  |  Bin
 .../images}/101_page_model_overview.gif       |  Bin
 {images => docs/images}/102_master_page.gif   |  Bin
 ..._master_page_with_page_layout_outlined.gif |  Bin
 .../104_master_page_preview_message.gif       |  Bin
 {images => docs/images}/105_page_layout.gif   |  Bin
 ...content_region_and_content_placeholder.gif |  Bin
 .../107_page_layout_with_page_fields.gif      |  Bin
 .../108_master_page_with_page_layout.gif      |  Bin
 .../images}/109_one_master_many_layouts.gif   |  Bin
 .../10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG  |  Bin
 .../110_page_with_authored_content.gif        |  Bin
 {images => docs/images}/111_rendered_page.gif |  Bin
 .../112_master_plus_layout_plus_page.gif      |  Bin
 ...d_layout_and_page_and_web_part_closeup.gif |  Bin
 .../115_content_search_web_part_tool_pane.gif |  Bin
 .../116_117_control_templates_1_and_2.gif     |  Bin
 .../11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif  |  Bin
 ...template_outlined_on_web_part_and_page.gif |  Bin
 ...emplates_outlined_on_web_part_and_page.gif |  Bin
 .../122_123_two_channels_two_master_pages.gif |  Bin
 .../images}/124_one_layout_many_masters.gif   |  Bin
 ...25_126_page_layout_with_channel_panels.gif |  Bin
 ...m_display_templates_with_channel_panel.gif |  Bin
 .../13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG  |  Bin
 .../14d5a820-ab44-4d12-98de-6672884bf344.PNG  |  Bin
 .../159f676e-421e-4190-94a6-cf311f7db2ca.gif  |  Bin
 .../17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF  |  Bin
 .../19126dce-b896-4623-8686-92f2fa807283.gif  |  Bin
 .../19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif  |  Bin
 .../1a814b3b-76a3-4a5c-8eef-550893728499.jpg  |  Bin
 .../1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif  |  Bin
 .../1b21d968-bd58-4f30-a019-84df6181b81a.PNG  |  Bin
 .../1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg  |  Bin
 .../1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png  |  Bin
 .../21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif  |  Bin
 .../2422936d-7ef6-4c90-a03f-30053fbb9743.PNG  |  Bin
 .../25ba5677-f530-432a-9980-64b5eb33119c.png  |  Bin
 .../2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG  |  Bin
 .../2d011e17-953f-42b1-97d3-2525372296c1.gif  |  Bin
 .../2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG  |  Bin
 .../2df9591d-a837-4130-98e4-5863d0c717e8.gif  |  Bin
 .../2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif  |  Bin
 .../31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG  |  Bin
 .../36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG  |  Bin
 .../3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg  |  Bin
 .../3b33c622-c52a-45fd-8ea1-d7f307539753.png  |  Bin
 .../3b9184db-99a4-416e-ba1e-7f8653484cee.png  |  Bin
 .../3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif  |  Bin
 .../3fbdcfae-6af9-452b-9a07-48575de7e86a.png  |  Bin
 .../3fdc6752-4184-4928-9423-0bc7c0206c62.PNG  |  Bin
 .../4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg  |  Bin
 .../43a35ca2-2c93-4323-a169-769c3a54fa38.PNG  |  Bin
 .../43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg  |  Bin
 .../44928b39-5683-4bce-8ddf-31d886243b87.gif  |  Bin
 .../477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png  |  Bin
 .../494cf01e-3e17-4092-b239-9312ac4ab258.PNG  |  Bin
 .../49a93d59-6755-4afc-a703-ca8469b6fa74.gif  |  Bin
 .../49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG  |  Bin
 .../4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif  |  Bin
 .../4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG  |  Bin
 .../4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG  |  Bin
 .../4f81174f-d875-4a9e-bff4-adea0f176f00.PNG  |  Bin
 .../558e6305-5a42-4b5c-9a70-1116ddcf6637.gif  |  Bin
 .../5950bc8a-ed73-4f14-b616-a88c14c4fe56.png  |  Bin
 .../5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg  |  Bin
 .../5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG  |  Bin
 .../60f3302e-ca9c-45be-b785-0c9f636181da.PNG  |  Bin
 .../65926095-d833-4eb2-b899-9efe40e2d540.GIF  |  Bin
 .../6a0f0a56-3184-490a-af19-b51b7545671d.PNG  |  Bin
 .../6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG  |  Bin
 .../6c119cae-adf8-42ff-9890-f3aa1e11719d.png  |  Bin
 .../6d3bbe0a-399e-4747-9e1a-01d42954ce32.png  |  Bin
 .../70d5a602-b349-4791-bf05-d61635d0fc91.gif  |  Bin
 .../7298a25b-ed54-4953-a781-26c3f633866a.jpg  |  Bin
 .../72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG  |  Bin
 .../746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg  |  Bin
 .../7639578e-3d3f-40cf-8f53-355bb19c539b.png  |  Bin
 .../7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif  |  Bin
 .../77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif  |  Bin
 .../7849d413-381f-4558-9e50-b3cc9990d3e3.png  |  Bin
 .../787df903-833d-4a12-a692-716ceaf54c10.gif  |  Bin
 .../797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG  |  Bin
 .../7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG  |  Bin
 .../7fd942de-a324-4f70-a750-f5304c993832.PNG  |  Bin
 .../833fcdcc-1755-438b-9ada-dce9646564c0.gif  |  Bin
 .../835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG  |  Bin
 .../84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG  |  Bin
 .../884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif  |  Bin
 .../89aa8c23-f8f2-410e-b021-7b0959e11586.jpg  |  Bin
 .../8a9768f4-315d-45c0-88d7-687dbf84495c.PNG  |  Bin
 .../8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif  |  Bin
 .../8dd2a25f-103a-42af-aa88-c8ec796315db.PNG  |  Bin
 .../903d3109-d567-4156-a44f-29793c42ae45.gif  |  Bin
 .../90cd4b6e-462e-442e-92de-86b2d98282d0.jpg  |  Bin
 .../9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif  |  Bin
 .../916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png  |  Bin
 .../921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif  |  Bin
 .../96681da7-ceab-40f3-8d08-441aea9b4a6f.gif  |  Bin
 .../97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif  |  Bin
 .../978d8147-cabd-422e-9d02-d8022a114bd6.jpg  |  Bin
 .../99209248-8927-4fc2-abfc-53d530376516.PNG  |  Bin
 .../99376713-6a54-4d88-9b05-068578169506.gif  |  Bin
 .../997021de-c60c-46b0-961f-7e1e63c0f619.gif  |  Bin
 .../99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif  |  Bin
 .../9a38d876-2189-418c-9314-ae493a4cab61.PNG  |  Bin
 .../9c836899-8f21-4e0f-9260-69b8171a303c.PNG  |  Bin
 .../9dc5cefe-083a-4807-bee6-473001f23db9.png  |  Bin
 .../9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif  |  Bin
 .../images}/ALMBuildDeployProcess.png         |  Bin
 .../images}/ALMChangeManagement.png           |  Bin
 {images => docs/images}/ALMCodePromotion.png  |  Bin
 .../images}/ALMDeveloperTesting.png           |  Bin
 .../images}/ALMIntegrationTesting.png         |  Bin
 .../images}/ALMIntegrationandUAT.png          |  Bin
 {images => docs/images}/ALMTestingTypes.png   |  Bin
 {images => docs/images}/ALMUATTesting.png     |  Bin
 {images => docs/images}/ALMWithTFS.png        |  Bin
 .../AppDevelopmentClientBuildComponents.png   |  Bin
 .../images}/AppDevelopmentEnvironment.png     |  Bin
 .../AppDevelopmentVirtualEnvironment.png      |  Bin
 .../images}/AppForSharePointVSTemplate.PNG    |  Bin
 .../AppParts_ConceptualArchitecture.png       |  Bin
 .../images}/AppParts_IFrameError.png          |  Bin
 .../images}/AppUXGuidelines_AppTemplate.png   |  Bin
 .../images}/AppUXGuidelines_ChromeControl.png |  Bin
 .../AppUXGuidelines_ECBcustomaction.png       |  Bin
 .../AppUXGuidelines_QuickLaunchHeading.png    |  Bin
 .../AppUXGuidelines_QuickLaunchLink.png       |  Bin
 .../AppUXGuidelines_QuickLaunchSelected.png   |  Bin
 .../images}/AppUXGuidelines_TopNav.png        |  Bin
 .../AppUXGuidelines_TopNavSelected.png        |  Bin
 .../images}/AppUXGuidelines_bgdisabled.png    |  Bin
 .../images}/AppUXGuidelines_body.png          |  Bin
 .../images}/AppUXGuidelines_dragfiles.png     |  Bin
 .../images}/AppUXGuidelines_h1.png            |  Bin
 .../images}/AppUXGuidelines_h2.png            |  Bin
 .../images}/AppUXGuidelines_h3.png            |  Bin
 .../images}/AppUXGuidelines_h4.png            |  Bin
 .../images}/AppUXGuidelines_hr.png            |  Bin
 .../images}/AppUXGuidelines_hyperlink.png     |  Bin
 .../AppUXGuidelines_md-bghoverable-normal.png |  Bin
 .../AppUXGuidelines_ms-accentlines.png        |  Bin
 .../images}/AppUXGuidelines_ms-accenttext.png |  Bin
 .../AppUXGuidelines_ms-attractmode.png        |  Bin
 .../images}/AppUXGuidelines_ms-bgfooter.png   |  Bin
 .../images}/AppUXGuidelines_ms-bgheader.png   |  Bin
 ...AppUXGuidelines_ms-bghoverable-onhover.png |  Bin
 .../images}/AppUXGuidelines_ms-bgoverlay.png  |  Bin
 .../images}/AppUXGuidelines_ms-bgselected.png |  Bin
 .../AppUXGuidelines_ms-calloutlink.png        |  Bin
 .../AppUXGuidelines_ms-commandlink.png        |  Bin
 .../AppUXGuidelines_ms-core-pagetitle.png     |  Bin
 .../images}/AppUXGuidelines_ms-disabled.png   |  Bin
 .../AppUXGuidelines_ms-disabledlines.png      |  Bin
 .../AppUXGuidelines_ms-dlg-heading.png        |  Bin
 .../images}/AppUXGuidelines_ms-emphasis.png   |  Bin
 .../AppUXGuidelines_ms-emphasisborder.png     |  Bin
 .../images}/AppUXGuidelines_ms-emptymode.png  |  Bin
 .../images}/AppUXGuidelines_ms-error.png      |  Bin
 .../images}/AppUXGuidelines_ms-helper.png     |  Bin
 .../AppUXGuidelines_ms-herocommandlink.png    |  Bin
 .../images}/AppUXGuidelines_ms-lines.png      |  Bin
 .../images}/AppUXGuidelines_ms-listlink.png   |  Bin
 .../images}/AppUXGuidelines_ms-metadata.png   |  Bin
 .../AppUXGuidelines_ms-popupborder.png        |  Bin
 ...ppUXGuidelines_ms-secondarycommandlink.png |  Bin
 .../AppUXGuidelines_ms-sidenav-selected.png   |  Bin
 .../images}/AppUXGuidelines_ms-sidenav.png    |  Bin
 .../images}/AppUXGuidelines_ms-soften.png     |  Bin
 .../AppUXGuidelines_ms-stronglines.png        |  Bin
 .../AppUXGuidelines_ms-subtleemphasis.png     |  Bin
 ...ines_ms-subtleemphasiscommand-disabled.png |  Bin
 ...pUXGuidelines_ms-subtleemphasiscommand.png |  Bin
 .../AppUXGuidelines_ms-subtlelines.png        |  Bin
 .../images}/AppUXGuidelines_ms-textlarge.png  |  Bin
 .../images}/AppUXGuidelines_ms-textsmall.png  |  Bin
 .../images}/AppUXGuidelines_ms-textxlarge.png |  Bin
 .../images}/AppUXGuidelines_ms-topbar.png     |  Bin
 .../images}/AppUXGuidelines_ms-uppercase.png  |  Bin
 .../AppUXGuidelines_ms-webpart-titletext.png  |  Bin
 .../images}/AppUXGuidelines_mspivotlink.png   |  Bin
 .../images}/AppUXGuidelines_part.png          |  Bin
 {images => docs/images}/AppUX_devhosted.png   |  Bin
 {images => docs/images}/AppUX_hostweb.png     |  Bin
 {images => docs/images}/AppUX_landscape.png   |  Bin
 .../images}/AppVSTemplateSolutionExplorer.jpg |  Bin
 .../images}/Apps_NAPA_Run_Button.png          |  Bin
 .../images}/Apps_Napa_OpenInVS.png            |  Bin
 .../images}/BCSin2013FeatureSet.jpg           |  Bin
 .../images}/BasicAppPart_gallery.jpg          |  Bin
 .../images}/BasicAppPart_result.png           |  Bin
 .../BrowserWarnings4SelfSignedCerts.png       |  Bin
 .../Buildsearch-drivenmobileappspages.gif     |  Bin
 ...rch-drivenmobileappspages_item_details.gif |  Bin
 {images => docs/images}/CBAAddButton.PNG      |  Bin
 {images => docs/images}/CBAAddDialog.PNG      |  Bin
 {images => docs/images}/CBAAddDoc.PNG         |  Bin
 {images => docs/images}/CBAAddTab.PNG         |  Bin
 {images => docs/images}/CBADocLibrary.PNG     |  Bin
 {images => docs/images}/CBADocLibrary2.PNG    |  Bin
 {images => docs/images}/CBARelationship.PNG   |  Bin
 {images => docs/images}/CBARelationship2.PNG  |  Bin
 {images => docs/images}/CBAScreenSet.PNG      |  Bin
 {images => docs/images}/CBA_IM1.PNG           |  Bin
 {images => docs/images}/CBA_IM4a.PNG          |  Bin
 {images => docs/images}/CBA_IM_10.PNG         |  Bin
 {images => docs/images}/CBA_IM_10a.PNG        |  Bin
 {images => docs/images}/CBA_IM_11.PNG         |  Bin
 {images => docs/images}/CBA_IM_11a.PNG        |  Bin
 {images => docs/images}/CBA_IM_11b.PNG        |  Bin
 {images => docs/images}/CBA_IM_11c.PNG        |  Bin
 {images => docs/images}/CBA_IM_12.PNG         |  Bin
 {images => docs/images}/CBA_IM_13.PNG         |  Bin
 {images => docs/images}/CBA_IM_14.PNG         |  Bin
 {images => docs/images}/CBA_IM_15.PNG         |  Bin
 {images => docs/images}/CBA_IM_16.PNG         |  Bin
 {images => docs/images}/CBA_IM_17.PNG         |  Bin
 {images => docs/images}/CBA_IM_18.PNG         |  Bin
 {images => docs/images}/CBA_IM_19.PNG         |  Bin
 {images => docs/images}/CBA_IM_2.PNG          |  Bin
 {images => docs/images}/CBA_IM_20.PNG         |  Bin
 {images => docs/images}/CBA_IM_20a.PNG        |  Bin
 {images => docs/images}/CBA_IM_21.PNG         |  Bin
 {images => docs/images}/CBA_IM_22.PNG         |  Bin
 {images => docs/images}/CBA_IM_23.PNG         |  Bin
 {images => docs/images}/CBA_IM_24.PNG         |  Bin
 {images => docs/images}/CBA_IM_25.PNG         |  Bin
 {images => docs/images}/CBA_IM_26.PNG         |  Bin
 {images => docs/images}/CBA_IM_27.PNG         |  Bin
 {images => docs/images}/CBA_IM_28.PNG         |  Bin
 {images => docs/images}/CBA_IM_28a.PNG        |  Bin
 {images => docs/images}/CBA_IM_29.PNG         |  Bin
 {images => docs/images}/CBA_IM_29a.PNG        |  Bin
 {images => docs/images}/CBA_IM_2a.PNG         |  Bin
 {images => docs/images}/CBA_IM_3.PNG          |  Bin
 {images => docs/images}/CBA_IM_30.PNG         |  Bin
 {images => docs/images}/CBA_IM_4.PNG          |  Bin
 {images => docs/images}/CBA_IM_5.PNG          |  Bin
 {images => docs/images}/CBA_IM_5a.PNG         |  Bin
 {images => docs/images}/CBA_IM_6.PNG          |  Bin
 {images => docs/images}/CBA_IM_7.PNG          |  Bin
 {images => docs/images}/CBA_IM_8.PNG          |  Bin
 {images => docs/images}/CBA_IM_8a.PNG         |  Bin
 {images => docs/images}/CBA_IM_8b.PNG         |  Bin
 {images => docs/images}/CBA_IM_8c.PNG         |  Bin
 {images => docs/images}/CBA_IM_8d.PNG         |  Bin
 {images => docs/images}/CBA_IM_9.PNG          |  Bin
 {images => docs/images}/CBA_IM_9a.PNG         |  Bin
 {images => docs/images}/CBAaction.PNG         |  Bin
 {images => docs/images}/CBAadd.PNG            |  Bin
 {images => docs/images}/CBAentity.PNG         |  Bin
 {images => docs/images}/CBAnewsfeed.PNG       |  Bin
 {images => docs/images}/CBAproperty.PNG       |  Bin
 {images => docs/images}/CBAscreen.PNG         |  Bin
 {images => docs/images}/CBAsocial.PNG         |  Bin
 {images => docs/images}/CBAtemplate.PNG       |  Bin
 {images => docs/images}/CFW.gif               |  Bin
 .../images}/CSRFieldType_addcolumn.png        |  Bin
 .../images}/CSRFieldType_result.png           |  Bin
 .../images}/CSRListView_result.png            |  Bin
 {images => docs/images}/Caution.gif           |  Bin
 .../images}/ChromControl_stylesheet.png       |  Bin
 .../images}/ChromeControl_manifest.PNG        |  Bin
 .../images}/ChromeControl_result.png          |  Bin
 .../images}/CloudBusinessApptemplate.PNG      |  Bin
 .../images}/ConvertAuto2ProviderFig10.jpg     |  Bin
 .../images}/ConvertAuto2ProviderFig12.jpg     |  Bin
 .../images}/ConvertAuto2ProviderFig18.png     |  Bin
 .../images}/ConvertAuto2ProviderFig20.jpg     |  Bin
 .../images}/ConvertAuto2ProviderFig21.jpg     |  Bin
 .../images}/ConvertAuto2ProviderFig22.jpg     |  Bin
 .../images}/ConvertAuto2ProviderFig3.jpg      |  Bin
 .../images}/ConvertAuto2ProviderFig4.jpg      |  Bin
 .../images}/ConvertAuto2ProviderFig5.jpg      |  Bin
 .../images}/ConvertAuto2ProviderFig6.jpg      |  Bin
 .../images}/ConvertAuto2Providerfig11.jpg     |  Bin
 .../images}/ConvertAuto2Providerfig13.jpg     |  Bin
 .../images}/ConvertAuto2Providerfig14.jpg     |  Bin
 .../images}/ConvertAuto2Providerfig17.jpg     |  Bin
 .../images}/ConvertAuto2Providerfig7.jpg      |  Bin
 .../images}/ConvertAuto2Providerfig8.jpg      |  Bin
 .../images}/ConvertAuto2Providerfig9.jpg      |  Bin
 .../CreatSharePoint2013WorkflowsFig4.png      |  Bin
 .../images}/CreateSharePoint2013Workflows.png |  Bin
 .../CreateSharePoint2013WorkflowsFig2.png     |  Bin
 .../CreateSharePoint2013WorkflowsFig5.png     |  Bin
 .../CreateSharePoint2013WorkflowsFig7.png     |  Bin
 .../CreateSharePoint2013WorkflowsFig8.png     |  Bin
 .../images}/CrossDomainReadItemsResult.png    |  Bin
 .../images}/Crosszone_loaderror.png           |  Bin
 .../images}/Crosszone_loadsuccess.png         |  Bin
 .../images}/CustomActions_target.png          |  Bin
 .../images}/CustomProxy_result.jpg            |  Bin
 .../images}/DataAccess_SharePointData.png     |  Bin
 .../images}/DesktopListView_basic.png         |  Bin
 .../images}/ExtEvtsAndAlerts_Figure2.jpg      |  Bin
 .../images}/ExtEvtsAndAlerts_Figure3.jpg      |  Bin
 .../images}/ExtEvtsAndAlrts_Figure1.jpg       |  Bin
 ...xternalEventsAndAlerts_UnsubscribeFlow.jpg |  Bin
 {images => docs/images}/GitHub-Mark-64px.png  |  Bin
 {images => docs/images}/HostWebAndAppWeb.png  |  Bin
 {images => docs/images}/ImgRendition_crop.PNG |  Bin
 {images => docs/images}/ImgRendition_orig.PNG |  Bin
 {images => docs/images}/LastChild.gif         |  Bin
 .../images}/LocSPApp_AppwebList.png           |  Bin
 .../images}/LocSPApp_AppwebPage.png           |  Bin
 .../images}/LocSPApp_TestCreatesite.png       |  Bin
 {images => docs/images}/MDS_GeneralFlow.png   |  Bin
 {images => docs/images}/MDS_SeattleMaster.png |  Bin
 .../images}/MDS_UpdateSections.png            |  Bin
 {images => docs/images}/NuGet.PNG             |  Bin
 {images => docs/images}/Octocat.png           |  Bin
 .../images}/Office365AppDevelpment.png        |  Bin
 .../images}/OfficeWebWidgetsOverview_demo.png |  Bin
 {images => docs/images}/OnPremDevSites.png    |  Bin
 .../OptimizePage_Fig01_MDSArchitecture.png    |  Bin
 .../OptimizePage_Fig02_PageStructure.png      |  Bin
 .../OptimizePage_Fig03_SingleImage.png        |  Bin
 .../images}/OptimizePage_Fig04_ImageTable.png |  Bin
 .../OptimizePage_Fig05_DevDashboard.png       |  Bin
 .../images}/PeoplePicker_HTMLHierarchy.png    |  Bin
 .../images}/PeoplePicker_basic.png            |  Bin
 .../ProviderHostedAppBuildComponents.png      |  Bin
 .../images}/REST_OverallSyntax.png            |  Bin
 .../images}/REST_RESTStructure.png            |  Bin
 .../images}/REST_parameterAliasSyntax.png     |  Bin
 .../REST_parameterDictionarySyntax.png        |  Bin
 .../images}/REST_parameterQuerySyntax.png     |  Bin
 .../images}/REST_parameterSyntax.png          |  Bin
 .../images}/REST_queryOptionSyntax.png        |  Bin
 docs/images/RegrantPermissionsToAnApp.png     |  Bin 0 -> 47344 bytes
 .../images}/S15_CalloutControlExample.png     |  Bin
 ...ildSharePointAppsForMobileDevices_Fig2.png |  Bin
 ...ildSharePointAppsForMobileDevices_Fig3.png |  Bin
 .../images}/SP15Con_CF_BCS_Overview.jpg       |  Bin
 .../images}/SP15Con_CF_ConnFrwkArch.jpg       |  Bin
 .../images}/SP15Con_CF_IndexingConnectors.jpg |  Bin
 ...eSharePointListAppsForWindowsPhoneFig3.png |  Bin
 ...eSharePointListAppsForWindowsPhoneFig4.png |  Bin
 ..._HowToAddGeolocationColumnUpdated_Fig1.png |  Bin
 .../SP15Con_HowToAddGeolocationColumn_fig.png |  Bin
 ...15Con_HowToCreateMapBasedPhoneApp_Fig1.png |  Bin
 ...15Con_HowToCreateMapBasedPhoneApp_Fig2.png |  Bin
 ...15Con_HowToCreateMapBasedPhoneApp_Fig3.png |  Bin
 ...nFieldTypeUsingClientSideRenderingFig2.png |  Bin
 ...P15Con_Remote_Event_Receivers_FAQ_fig1.png |  Bin
 ...P15Con_Remote_Event_Receivers_FAQ_fig3.png |  Bin
 ...P15Con_Remote_Event_Receivers_FAQ_fig4.PNG |  Bin
 ...Con_SharePointClientAuthenticationFig1.png |  Bin
 ...15Con_VisualStudioMobileSPListTemplate.png |  Bin
 .../images}/SP15HelloWorldSPApp_Fig01.png     |  Bin
 .../images}/SP15HighTrustLaunchNew.gif        |  Bin
 ...Buildsearch-drivenmobileappspages_home.gif |  Bin
 .../images}/SP15_CMISCapabilities.jpg         |  Bin
 .../images}/SP15_CMISObjectTypeExamples.png   |  Bin
 .../images}/SP15_CalloutLeftRight.png         |  Bin
 {images => docs/images}/SP15_CalloutMenu.png  |  Bin
 .../images}/SP15_CalloutTopBottom.png         |  Bin
 .../images}/SP15_Content_Enrichment.gif       |  Bin
 .../images}/SP15_DeveloperSiteHome_border.png |  Bin
 .../images}/SP15_FeatureReceiverVS.png        |  Bin
 .../SP15_Office365AdminInset_border.png       |  Bin
 .../images}/SP15_OnPremACSArchitecture.png    |  Bin
 ...WinPhoneSPTemplatesInVisualStudio_fig1.PNG |  Bin
 {images => docs/images}/SP15_RegisterApp.png  |  Bin
 ...gmentation_with_ContentBySearchWebPart.jpg |  Bin
 .../images}/SP15_appChooseSiteTemplate.gif    |  Bin
 .../images}/SP15_app_ChooseSiteTemplates.gif  |  Bin
 .../images}/SP15_app_ServerType.gif           |  Bin
 .../images}/SP15_basicself-hostedapp.gif      |  Bin
 .../images}/SP15_hosting_Provider.gif         |  Bin
 .../images}/SP15_hosting_SPhosted.gif         |  Bin
 .../SP15_search_app_permission_Napa.gif       |  Bin
 ...5_search_apps_permission_Visual_Studio.PNG |  Bin
 .../SPAdminCenter_newSiteCollection.png       |  Bin
 ...nCenter_newSiteCollection_provisioning.png |  Bin
 .../images}/SPCon15_BDCMobileAppDemo.png      |  Bin
 ...5_BDC_SetPermissions_ODataWebNorthWind.png |  Bin
 ...n15_CreateMapView_ChooseViewType__fig2.png |  Bin
 ...pView_DifferentPushPinsOnMapView__fig5.png |  Bin
 .../SPCon15_CreateMapView_ECB_Menu__fig1.png  |  Bin
 .../SPCon15_CreateMapView_MyMapView__fig4.png |  Bin
 ..._CreateMapView_PushPinsOnMapView__fig6.png |  Bin
 ...reateMapView_SelectFieldsForView__fig3.png |  Bin
 ...etting_BDCObjectPermission_DialogueBox.png |  Bin
 {images => docs/images}/SPD-Dictionary-1a.png |  Bin
 .../images}/SPD15-BuildADictionaryDialog.png  |  Bin
 .../images}/SPD15-CoordinationActions.png     |  Bin
 .../images}/SPD15-CoordinationActions2.png    |  Bin
 .../images}/SPD15-CoordinationActions3.png    |  Bin
 .../images}/SPD15-CorrelationActions4.png     |  Bin
 .../images}/SPD15-CountItemsInDictionary.png  |  Bin
 .../images}/SPD15-Dictionary-1b.png           |  Bin
 .../images}/SPD15-Dictionary-2.png            |  Bin
 .../images}/SPD15-EventingActions1.png        |  Bin
 .../images}/SPD15-EventingActions2.png        |  Bin
 .../images}/SPD15-EventingActions3.jpg        |  Bin
 .../images}/SPD15-EventingActions4.png        |  Bin
 .../images}/SPD15-EventingActions5.png        |  Bin
 .../images}/SPD15-GetAnItemFromDictionary.png |  Bin
 .../images}/SPD15-PackagingWorkflow1.png      |  Bin
 .../images}/SPD15-PackagingWorkflow2.png      |  Bin
 .../images}/SPD15-PackagingWorkflow3.png      |  Bin
 .../images}/SPD15-PackagingWorkflow4.png      |  Bin
 .../images}/SPD15-PackagingWorkflow5.png      |  Bin
 .../images}/SPD15-PackagingWorkflow6.png      |  Bin
 .../images}/SPD15-TaskActions2.png            |  Bin
 .../images}/SPD15-TaskActions3.png            |  Bin
 .../images}/SPD15-TaskActions4.png            |  Bin
 .../images}/SPD15-TaskActions5.png            |  Bin
 .../images}/SPD15-VisualDesigner1.png         |  Bin
 .../images}/SPD15-VisualDesigner2.png         |  Bin
 .../images}/SPD15-VisualDesigner3.png         |  Bin
 .../images}/SPD15-WFAppPermissions1.png       |  Bin
 .../images}/SPD15-WFAppPermissions10.png      |  Bin
 .../images}/SPD15-WFAppPermissions11.png      |  Bin
 .../images}/SPD15-WFAppPermissions12.png      |  Bin
 .../images}/SPD15-WFAppPermissions13.png      |  Bin
 .../images}/SPD15-WFAppPermissions14.png      |  Bin
 .../images}/SPD15-WFAppPermissions15.png      |  Bin
 .../images}/SPD15-WFAppPermissions2.png       |  Bin
 .../images}/SPD15-WFAppPermissions3.png       |  Bin
 .../images}/SPD15-WFAppPermissions4.png       |  Bin
 .../images}/SPD15-WFAppPermissions5.png       |  Bin
 .../images}/SPD15-WFAppPermissions6.png       |  Bin
 .../images}/SPD15-WFAppPermissions7.png       |  Bin
 .../images}/SPD15-WFAppPermissions8.png       |  Bin
 .../images}/SPD15-WFAppPermissions9.png       |  Bin
 .../images}/SPD15-install-connect-1.png       |  Bin
 .../images}/SPD15-install-connect-2.png       |  Bin
 .../images}/SPD15-install-connect-3.png       |  Bin
 .../images}/SPD15-install-connect-4.png       |  Bin
 {images => docs/images}/SPD15-wf-step1.png    |  Bin
 .../images}/SPF15Con_REST_OverallSyntax.png   |  Bin
 .../images}/SPF15Con_REST_RESTStructure.png   |  Bin
 .../SPF15Con_REST_parameterAliasSyntax.png    |  Bin
 ...PF15Con_REST_parameterDictionarySyntax.png |  Bin
 .../SPF15Con_REST_parameterQuerySyntax.png    |  Bin
 .../images}/SPF15Con_REST_parameterSyntax.png |  Bin
 .../SPF15Con_REST_queryOptionSyntax.png       |  Bin
 .../images}/SPS14_PerfPoint_ArchOverview.gif  |  Bin
 .../images}/SPS15CON_WAS_Architecture.png     |  Bin
 .../images}/SPS15CON_xls_JsUdfinWebApp.jpg    |  Bin
 .../SP_VS_Properties_Window_AppEvents.PNG     |  Bin
 .../SP_VS_Properties_Window_RemoteEvents.PNG  |  Bin
 .../images}/SearchComponentInteraction.jpg    |  Bin
 ...APIsetsandselectedSharePointextensions.png |  Bin
 ...SharePointServer14Con_XLSvcs_RESTModel.gif |  Bin
 .../images}/SharePointSolutionVSTemplate.png  |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_0.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_1.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_2.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_3.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_4.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_5.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_6.png |  Bin
 ...t_appsForSharePoint_3LeggedOauthFlow_7.png |  Bin
 {images => docs/images}/SharePointtab.PNG     |  Bin
 {images => docs/images}/SiteURL.PNG           |  Bin
 {images => docs/images}/Sp15_app_.png         |  Bin
 .../images}/StylesheetControl_result.png      |  Bin
 .../images}/StylesheetControl_result2.png     |  Bin
 {images => docs/images}/TFSBuildTargets.png   |  Bin
 .../images}/Top-levelprojectnode.PNG          |  Bin
 .../images}/UpdateAppOpenFeatureXML.png       |  Bin
 .../UpdatingApp_AppTileUpdateNotice.png       |  Bin
 .../UpdatingApp_ImmediateUpgradeProcess.png   |  Bin
 {images => docs/images}/WebProxy_result.png   |  Bin
 ...WorkingWithTasksSharePointWorkflowsFig.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig1.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig10.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig11.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig12.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig13.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig14.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig15.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig16.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig17.png |  Bin
 ...rkingWithTasksSharePointWorkflowsFig18.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig2.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig3.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig4.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig5.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig6.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig7.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig8.png |  Bin
 ...orkingWithTasksSharePointWorkflowsFig9.png |  Bin
 {images => docs/images}/XRANKFormula.gif      |  Bin
 .../a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG  |  Bin
 .../a3371859-e42f-49ea-8f17-48d8a248b075.PNG  |  Bin
 .../a35fd1af-7194-4c99-b298-bac97025b981.PNG  |  Bin
 .../a61afe25-9597-403f-b3fa-d3f630155021.png  |  Bin
 .../a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png  |  Bin
 .../a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg  |  Bin
 .../aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG  |  Bin
 {images => docs/images}/adm.gif               |  Bin
 {images => docs/images}/adm_arch.gif          |  Bin
 {images => docs/images}/adm_dev.gif           |  Bin
 {images => docs/images}/adm_dev_arch.gif      |  Bin
 .../aebc97ae-c886-4d50-94ff-238049a259c7.gif  |  Bin
 {images => docs/images}/alert_caution.gif     |  Bin
 {images => docs/images}/alert_note.gif        |  Bin
 {images => docs/images}/alert_security.gif    |  Bin
 .../api-aad-add-function-parameters.png       |  Bin
 .../images}/api-aad-add-function.png          |  Bin
 ...i-aad-azure-app-service-authentication.png |  Bin
 .../images}/api-aad-create-new-aad-app.png    |  Bin
 .../api-aad-create-new-function-app.png       |  Bin
 .../images}/api-aad-custom-function.png       |  Bin
 ...pi-aad-function-authentication-aad-app.png |  Bin
 .../api-aad-function-authentication-aad.png   |  Bin
 ...-aad-function-authentication-login-aad.png |  Bin
 .../api-aad-function-authentication-on.png    |  Bin
 .../api-aad-function-authentication-save.png  |  Bin
 .../api-aad-function-authentication.png       |  Bin
 .../images}/api-aad-function-code.png         |  Bin
 .../images}/api-aad-function-cors-delete.png  |  Bin
 .../images}/api-aad-function-cors-save.png    |  Bin
 .../images}/api-aad-function-cors.png         |  Bin
 .../images}/api-aad-platform-features.png     |  Bin
 {images => docs/images}/api-aad-sign-in.png   |  Bin
 ...ad-visual-studio-authentication-wizard.png |  Bin
 .../api-aad-webapi-anonymous-unauthorized.png |  Bin
 ...pi-aad-webapi-authentication-aad-login.png |  Bin
 .../api-aad-webapi-authentication-aad-ok.png  |  Bin
 .../api-aad-webapi-authentication-aad.png     |  Bin
 .../api-aad-webapi-authentication-on.png      |  Bin
 .../api-aad-webapi-authentication-save.png    |  Bin
 .../images}/api-aad-webapi-authentication.png |  Bin
 .../images}/api-aad-webapi-azure-aad.png      |  Bin
 .../api-aad-webapi-azure-app-details.png      |  Bin
 ...api-aad-webapi-azure-app-registrations.png |  Bin
 ...bapi-azure-new-app-registration-create.png |  Bin
 ...-aad-webapi-azure-new-app-registration.png |  Bin
 .../images}/api-aad-webapi-azure-sign-in.png  |  Bin
 .../api-aad-webapi-response-anonymous.png     |  Bin
 .../images}/api-aad-webapi-vs-cors-nuget.png  |  Bin
 .../api-aad-webapi-vs-create-app-service.png  |  Bin
 .../api-aad-webapi-vs-host-app-service.png    |  Bin
 .../api-aad-webapi-vs-manage-nuget.png        |  Bin
 .../api-aad-webapi-vs-no-authentication.png   |  Bin
 .../api-aad-webapi-vs-publish-settings.png    |  Bin
 .../images}/api-aad-webapi-vs-publish.png     |  Bin
 .../api-aad-webapi-vs-web-application.png     |  Bin
 .../images}/api-aad-webapi-vs-webapi.png      |  Bin
 .../images}/app-installed-your-site.png       |  Bin
 {images => docs/images}/arch.gif              |  Bin
 .../b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg  |  Bin
 .../b315cb68-ff6a-4770-a1dc-738696ab71d2.png  |  Bin
 .../b654af45-663e-425c-b7c7-b8b5524cb316.PNG  |  Bin
 .../b86ecdb8-88a7-4407-af86-07d2442235dc.gif  |  Bin
 .../b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG  |  Bin
 .../beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG  |  Bin
 .../bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif  |  Bin
 {images => docs/images}/big_adm.gif           |  Bin
 {images => docs/images}/big_arch.gif          |  Bin
 {images => docs/images}/big_dev.gif           |  Bin
 {images => docs/images}/big_kw.gif            |  Bin
 {images => docs/images}/box.gif               |  Bin
 {images => docs/images}/bullet.gif            |  Bin
 .../c046bc5c-1e31-4ac6-9cba-05482cc36915.gif  |  Bin
 .../c1230e3b-d149-413c-aa66-d258250a4512.PNG  |  Bin
 .../c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG  |  Bin
 .../cd8eb456-d883-491a-b171-38c1b9f64018.PNG  |  Bin
 .../images}/cdn-add-webpart-to-site.png       |  Bin
 .../images}/cdn-create-webpart-yo.png         |  Bin
 .../images}/cdn-helloworld-folder.png         |  Bin
 .../images}/cdn-public-origins.png            |  Bin
 .../cdn-upload-solution-to-app-catalog.png    |  Bin
 .../images}/cdn-web-part-f12-source.png       |  Bin
 .../images}/cdn-web-part-files-in-folder.png  |  Bin
 .../images}/cdn-web-part-picker.png           |  Bin
 .../images}/cdn-web-part-rendering.png        |  Bin
 .../images}/cdn-write-manifest-json.png       |  Bin
 .../ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif  |  Bin
 .../images}/chrome-load-unsafe-scripts.png    |  Bin
 {images => docs/images}/collall.gif           |  Bin
 {images => docs/images}/collapse.gif          |  Bin
 {images => docs/images}/collapse_all.gif      |  Bin
 .../images}/contribute-docs-clone-options.png |  Bin
 .../images}/contribute-docs-submit-pr.png     |  Bin
 .../images}/contribute-fork-docs-repo.png     |  Bin
 {images => docs/images}/copycode.gif          |  Bin
 {images => docs/images}/copycodeHighlight.gif |  Bin
 ...control-cascading-items-loaded-enabled.png |  Bin
 ...-cascading-lists-loaded-items-disabled.png |  Bin
 ...y-pane-control-cascading-loading-items.png |  Bin
 ...y-pane-control-cascading-loading-lists.png |  Bin
 ...e-control-cascading-selected-list-item.png |  Bin
 ...roperty-pane-control-components-folder.png |  Bin
 ...ontrol-item-property-web-part-manifest.png |  Bin
 ...ontrol-list-property-web-part-manifest.png |  Bin
 ...-property-pane-control-loading-options.png |  Bin
 ...property-pane-control-selecting-option.png |  Bin
 ...operty-pane-control-visual-studio-code.png |  Bin
 ...operty-pane-control-web-part-first-run.png |  Bin
 ...property-pane-control-web-part-imports.png |  Bin
 .../custom-property-pane-control-yeoman.png   |  Bin
 .../d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG  |  Bin
 .../d4e17424-c06b-4635-aab8-4912cee5fe35.png  |  Bin
 .../d69871f6-c503-463b-bf96-4b6d7306c313.png  |  Bin
 .../images}/datatables-sewp-filter.png        |  Bin
 {images => docs/images}/datatables-sewp.png   |  Bin
 .../datatables-spfx-list-configured.png       |  Bin
 .../datatables-spfx-listname-property.png     |  Bin
 {images => docs/images}/datatables-spfx.png   |  Bin
 {images => docs/images}/datatables-vscode.png |  Bin
 {images => docs/images}/datatables-yeoman.png |  Bin
 .../db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG  |  Bin
 .../dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG  |  Bin
 ...oy-container-create-helloworld-webpart.png |  Bin
 .../images}/deploy-create-cdn-endpoint.png    |  Bin
 .../images}/deploy-create-cdn-profile.png     |  Bin
 .../images}/deploy-create-storage-account.png |  Bin
 .../images}/deploy-option-blob-container.png  |  Bin
 .../deploy-storage-account-accesskey.png      |  Bin
 .../images}/design-manager-preview-UI.jpg     |  Bin
 .../images}/design-wp-contexual-edits.png     |  Bin
 .../images}/design-wp-item-level-edits.png    |  Bin
 .../images}/design-wp-pp-accordion-groups.png |  Bin
 .../images}/design-wp-pp-accordion.png        |  Bin
 .../images}/design-wp-pp-non-reactive.png     |  Bin
 .../images}/design-wp-pp-pages-step1.png      |  Bin
 .../images}/design-wp-pp-pages-step2.png      |  Bin
 .../images}/design-wp-pp-pages-step3.png      |  Bin
 .../images}/design-wp-pp-reactive.png         |  Bin
 .../images}/design-wp-pp-single.png           |  Bin
 {images => docs/images}/design-wp-pp.png      |  Bin
 .../design-wp-responsive-max-width.png        |  Bin
 .../design-wp-responsive-min-width.png        |  Bin
 .../images}/design-wp-todo-example.png        |  Bin
 .../design-wp-todo-fabric-animations.png      |  Bin
 .../design-wp-todo-loading-indicator.png      |  Bin
 .../images}/design-wp-todo-pp-checkbox.png    |  Bin
 .../images}/design-wp-todo-pp-description.png |  Bin
 .../images}/design-wp-todo-pp-dropdown.png    |  Bin
 .../images}/design-wp-todo-pp-slider.png      |  Bin
 {images => docs/images}/design-wp-toolbar.png |  Bin
 {images => docs/images}/design-wp-toolbox.png |  Bin
 {images => docs/images}/dev.gif               |  Bin
 {images => docs/images}/dev_arch.gif          |  Bin
 {images => docs/images}/dropdown.gif          |  Bin
 {images => docs/images}/dropdownHover.gif     |  Bin
 {images => docs/images}/drpdown.gif           |  Bin
 {images => docs/images}/drpdown_orange.gif    |  Bin
 {images => docs/images}/drpdown_orange_up.gif |  Bin
 {images => docs/images}/drpup.gif             |  Bin
 .../e2cf6848-bd29-416b-b397-a1d670bd2910.gif  |  Bin
 .../e3718687-682a-41a8-92b5-4eff9070348d.gif  |  Bin
 .../e38f9b7f-59a3-468c-bcde-a48272f1f217.gif  |  Bin
 .../e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG  |  Bin
 .../e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG  |  Bin
 .../e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG  |  Bin
 .../e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG  |  Bin
 .../e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png  |  Bin
 .../e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png  |  Bin
 .../e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif  |  Bin
 .../eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif  |  Bin
 .../eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png  |  Bin
 .../eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg  |  Bin
 .../ec60797c-d329-4922-a811-70c64598f4d5.PNG  |  Bin
 .../ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif  |  Bin
 .../images}/edit-webpart-classic-page.png     |  Bin
 .../images}/edit-webpart-modern-page.png      |  Bin
 .../enterprise-guidance-trust-spfx-dialog.png |  Bin
 {images => docs/images}/exp.gif               |  Bin
 {images => docs/images}/expall.gif            |  Bin
 {images => docs/images}/expand_all.gif        |  Bin
 .../images}/ext-app-alert-sp-page.png         |  Bin
 .../images}/ext-app-approve-cdn-address.png   |  Bin
 .../images}/ext-app-assets-folder.png         |  Bin
 .../images}/ext-app-cdn-folder-created.png    |  Bin
 .../images}/ext-app-cdn-origins-pending.png   |  Bin
 .../images}/ext-app-cdn-write-manifest.png    |  Bin
 .../ext-app-debug-manifest-message.png        |  Bin
 .../images}/ext-app-gulp-serve.png            |  Bin
 .../images}/ext-app-header-footer-visible.png |  Bin
 .../ext-app-install-solution-to-site.png      |  Bin
 .../images}/ext-app-sppkg-deploy-trust.png    |  Bin
 .../images}/ext-app-vscode-app-base.png       |  Bin
 .../images}/ext-app-vscode-manifest.png       |  Bin
 .../images}/ext-app-vscode-methods.png        |  Bin
 .../ext-app-vscode-solution-structure.png     |  Bin
 .../images}/ext-com-accept-debug-scripts.png  |  Bin
 .../images}/ext-com-assets-folder.png         |  Bin
 .../images}/ext-com-create-new-list.png       |  Bin
 .../ext-com-default-customizer-output.png     |  Bin
 .../ext-com-dialog-button-in-toolbar.png      |  Bin
 .../images}/ext-com-dialog-debug-scripts.png  |  Bin
 .../images}/ext-com-dialog-gulp-serve.png     |  Bin
 .../ext-com-dialog-oob-alert-dialog.png       |  Bin
 .../images}/ext-com-dialog-output.png         |  Bin
 .../ext-com-dialog-visible-deployment.png     |  Bin
 .../images}/ext-com-dialog-visible-dialog.png |  Bin
 .../ext-com-dialog-vs-code-initial.png        |  Bin
 .../ext-com-dialog-yeoman-complete.png        |  Bin
 .../images}/ext-com-dialog-yeoman-prompts.png |  Bin
 .../ext-com-install-solution-to-site.png      |  Bin
 .../images}/ext-com-sppkg-deploy-trust.png    |  Bin
 .../images}/ext-com-vscode-base.png           |  Bin
 .../images}/ext-com-vscode-manifest.png       |  Bin
 .../ext-com-vscode-solution-structure.png     |  Bin
 .../images}/ext-com-yeoman-complete.png       |  Bin
 .../images}/ext-com-yeoman-prompts.png        |  Bin
 .../ext-erro-loading-debug-manifests.png      |  Bin
 .../ext-field-accept-debug-scripts.png        |  Bin
 .../images}/ext-field-add-field-to-list.png   |  Bin
 .../images}/ext-field-assets-folder.png       |  Bin
 .../ext-field-create-items-to-list.png        |  Bin
 .../ext-field-create-new-list-order.png       |  Bin
 .../images}/ext-field-create-new-list.png     |  Bin
 .../ext-field-default-customizer-output.png   |  Bin
 .../images}/ext-field-gulp-serve.png          |  Bin
 .../ext-field-install-solution-to-site.png    |  Bin
 .../images}/ext-field-list-settings.png       |  Bin
 .../ext-field-new-number-field-percent.png    |  Bin
 .../images}/ext-field-new-number-field.png    |  Bin
 .../ext-field-onrender-default-solution.png   |  Bin
 .../ext-field-percent-field-graphic.png       |  Bin
 .../ext-field-render-field-without-debug.png  |  Bin
 .../images}/ext-field-sppkg-deploy-trust.png  |  Bin
 .../ext-field-vscode-customizer-base.png      |  Bin
 .../images}/ext-field-vscode-manifest.png     |  Bin
 .../ext-field-vscode-solution-structure.png   |  Bin
 .../images}/ext-field-yeoman-complete.png     |  Bin
 .../images}/ext-field-yeoman-prompts.png      |  Bin
 .../images}/ext-yeoman-app-complete.png       |  Bin
 .../images}/ext-yeoman-app-prompts.png        |  Bin
 ...pts-browser-loading-angular-from-cache.png |  Bin
 ...-browser-loading-angular-two-web-parts.png |  Bin
 ...ternal-scripts-browser-loading-angular.png |  Bin
 .../images}/external-scripts-bundle-size.png  |  Bin
 ...l-scripts-external-angular-bundle-size.png |  Bin
 ...ipts-external-angular-two-bundles-size.png |  Bin
 .../images}/external-scripts-gulp-bundle.png  |  Bin
 .../external-scripts-non-amd-deps-error.png   |  Bin
 ...external-scripts-non-amd-no-deps-error.png |  Bin
 .../external-scripts-two-bundles-size.png     |  Bin
 .../f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif  |  Bin
 .../f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG  |  Bin
 .../f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG  |  Bin
 .../f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG  |  Bin
 .../f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG  |  Bin
 .../fabric-components-doc-card-view-ex.png    |  Bin
 .../fada902b-fa38-4ac8-8566-3693b736ac35.gif  |  Bin
 .../feature-provision-project-items.png       |  Bin
 .../ff384c69-56bf-4ceb-81c3-8b874e2407f0.png  |  Bin
 {images => docs/images}/filter1a.gif          |  Bin
 {images => docs/images}/filter1c.gif          |  Bin
 {images => docs/images}/footer.gif            |  Bin
 .../images}/fullcalendar-sewp-draganddrop.png |  Bin
 {images => docs/images}/fullcalendar-sewp.png |  Bin
 .../fullcalendar-spfx-list-configured.png     |  Bin
 .../fullcalendar-spfx-listname-property.png   |  Bin
 {images => docs/images}/fullcalendar-spfx.png |  Bin
 .../images}/fullcalendar-vscode.png           |  Bin
 .../images}/fullcalendar-yeoman.png           |  Bin
 {images => docs/images}/gradient.gif          |  Bin
 {images => docs/images}/greencheck.gif        |  Bin
 {images => docs/images}/greychck.gif          |  Bin
 ...dance-governance-spfx-structure-schema.png |  Bin
 ...-productionbuilds-debug-vs-ship-bundle.png |  Bin
 ...ance-productionbuilds-import-lodash-at.png |  Bin
 ...uidance-productionbuilds-import-lodash.png |  Bin
 ...ctionbuilds-two-bundles-with-libraries.png |  Bin
 ...ctionbuilds-webpack-visualizer-angular.png |  Bin
 .../guidance-sharingdata-cookie-chrome.png    |  Bin
 ...-sharingdata-cookie-edge-first-request.png |  Bin
 ...ingdata-cookie-edge-subsequent-request.png |  Bin
 ...ce-sharingdata-loading-data-separately.png |  Bin
 ...g-data-global-variable-loading-message.png |  Bin
 ...g-data-global-variable-waiting-message.png |  Bin
 ...lp-extend-image-resize-available-tasks.png |  Bin
 .../images}/gulp-extend-image-resize-task.png |  Bin
 .../gulp-image-resize-task-available.png      |  Bin
 .../images}/gulp-tasks-available.png          |  Bin
 {images => docs/images}/gulp-upload-cdn.png   |  Bin
 {images => docs/images}/header_prev_next.jpg  |  Bin
 .../images}/header_sql_tutorial_blank.jpg     |  Bin
 .../images}/header_sql_tutorial_logo.GIF      |  Bin
 .../hello-vs-webpart-finish-wizard.PNG        |  Bin
 ...hello-vs-webpart-new-project-ts-nodejs.PNG |  Bin
 .../images}/hello-vs-webpart-npm-explorer.PNG |  Bin
 .../hello-vs-webpart-soln-explorer.PNG        |  Bin
 .../images}/hello-vs-webpart-task-runner.PNG  |  Bin
 .../hello-vs-webpart-update-properties.PNG    |  Bin
 .../hellow-vs-webpart-step1-wizard.PNG        |  Bin
 .../images}/helloworld-wp-gulp-serve.png      |  Bin
 ...helloworld-wp-vscode-project-structure.png |  Bin
 .../images}/helloworld-wp-vscode-project.png  |  Bin
 .../images}/install-app-your-site.png         |  Bin
 .../integrate-webpart-properties-schema.png   |  Bin
 .../images}/jquery-accordion-wb.png           |  Bin
 {images => docs/images}/kw.gif                |  Bin
 {images => docs/images}/kw_adm.gif            |  Bin
 {images => docs/images}/kw_adm_arch.gif       |  Bin
 {images => docs/images}/kw_adm_dev.gif        |  Bin
 {images => docs/images}/kw_adm_dev_arch.gif   |  Bin
 {images => docs/images}/kw_arch.gif           |  Bin
 {images => docs/images}/kw_dev.gif            |  Bin
 {images => docs/images}/kw_dev_arch.gif       |  Bin
 {images => docs/images}/load.gif              |  Bin
 {images => docs/images}/load_hover.gif        |  Bin
 ...ation-english-greeting-dutch-workbench.png |  Bin
 .../images}/localization-initial-changes.png  |  Bin
 .../images}/localization-intellisense.png     |  Bin
 .../images}/localization-keys-comparison.png  |  Bin
 .../images}/localization-learn-more-nl-nl.png |  Bin
 .../images}/localization-loc-folder.png       |  Bin
 .../localization-multilingual-properties.png  |  Bin
 .../localization-property-pane-nl-nl.png      |  Bin
 .../localization-standard-locale-file.png     |  Bin
 .../localization-visual-studio-code.png       |  Bin
 .../localization-web-part-body-qps-ploc.png   |  Bin
 ...zation-web-part-property-pane-qps-ploc.png |  Bin
 .../images}/localization-yo-sharepoint.png    |  Bin
 {images => docs/images}/loggingSample.png     |  Bin
 .../images}/mod_icon_badge_conoverview.png    |  Bin
 .../images}/mod_icon_badge_reference.png      |  Bin
 {images => docs/images}/mod_icon_dobox.gif    |  Bin
 .../images}/mod_icon_getstartbox.gif          |  Bin
 {images => docs/images}/mod_icon_howto.png    |  Bin
 {images => docs/images}/mod_icon_incloud.gif  |  Bin
 .../images}/mod_icon_links_samples.png        |  Bin
 .../images}/mod_icon_onpremises.gif           |  Bin
 {images => docs/images}/mod_icon_startbox.gif |  Bin
 {images => docs/images}/mod_icon_video.png    |  Bin
 .../images}/mod_logo_sharepoint.png           |  Bin
 .../images}/ng-intro-angular-config.png       |  Bin
 .../images}/ng-intro-app-folder.png           |  Bin
 .../images}/ng-intro-app-module.png           |  Bin
 .../images}/ng-intro-dataservice.png          |  Bin
 .../images}/ng-intro-hide-finished-tasks.png  |  Bin
 .../images}/ng-intro-homecontroller-event.png |  Bin
 .../images}/ng-intro-homecontroller.png       |  Bin
 .../ng-intro-injector-class-variable.png      |  Bin
 .../images}/ng-intro-manifest-property.png    |  Bin
 .../ng-intro-project-visual-studio-code.png   |  Bin
 .../images}/ng-intro-property-interface.png   |  Bin
 .../ng-intro-property-pane-toggle-browser.png |  Bin
 .../images}/ng-intro-property-pane-toggle.png |  Bin
 .../images}/ng-intro-strings-interface.png    |  Bin
 {images => docs/images}/ng-intro-strings.png  |  Bin
 .../images}/ng-intro-web-part-css.png         |  Bin
 .../ng-intro-web-part-import-angular.png      |  Bin
 .../ng-intro-web-part-render-angular.png      |  Bin
 .../ng-intro-workbench-office-ui-fabric.png   |  Bin
 .../images}/ng-intro-yeoman-generator.png     |  Bin
 ...ration-angular-ngofficeuifabric-config.png |  Bin
 ...ration-angular-ngofficeuifabric-import.png |  Bin
 ...-migration-angular-web-part-properties.png |  Bin
 .../ng-migration-app-config-web-url.png       |  Bin
 ...migration-app-files-visual-studio-code.png |  Bin
 ...igration-app-folder-visual-studio-code.png |  Bin
 .../images}/ng-migration-correct-styling.png  |  Bin
 .../ng-migration-finished-tasks-hidden.png    |  Bin
 .../images}/ng-migration-first-run.png        |  Bin
 ...ng-migration-import-propertypanetoggle.png |  Bin
 .../ng-migration-injector-property.png        |  Bin
 .../ng-migration-old-office-ui-fabric.png     |  Bin
 ...migration-original-angular-application.png |  Bin
 ...g-migration-project-visual-studio-code.png |  Bin
 .../images}/ng-migration-todo-list.png        |  Bin
 .../ng-migration-workbench-aspx-doclib.png    |  Bin
 .../images}/ng-migration-workbench-weburl.png |  Bin
 .../images}/ng-migration-yeoman-generator.png |  Bin
 .../images}/ngDebuggingSP2013Workflows.png    |  Bin
 .../images}/ngDebuggingSP2013Workflows01.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows02.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows04.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows05.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows06.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows07.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows08.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows10.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows11.png  |  Bin
 .../images}/ngDebuggingSP2013Workflows12.png  |  Bin
 {images => docs/images}/ngFormsFig10.png      |  Bin
 {images => docs/images}/ngFormsFig5.png       |  Bin
 {images => docs/images}/ngFormsFig6.png       |  Bin
 {images => docs/images}/ngFormsFig7.png       |  Bin
 {images => docs/images}/ngFormsFig8.png       |  Bin
 {images => docs/images}/ngFormsFig9.png       |  Bin
 {images => docs/images}/ngGK_Fig02.png        |  Bin
 {images => docs/images}/ngGK_Fig03.png        |  Bin
 {images => docs/images}/ngGK_Fig04.png        |  Bin
 {images => docs/images}/ngGK_Fig05.png        |  Bin
 {images => docs/images}/ngGK_Fig06.png        |  Bin
 {images => docs/images}/ngGK_Fig07.png        |  Bin
 {images => docs/images}/ngGK_Fig08.png        |  Bin
 {images => docs/images}/ngGK_Fig09.png        |  Bin
 {images => docs/images}/ngGK_Fig10.png        |  Bin
 {images => docs/images}/ngGK_Fig11.png        |  Bin
 {images => docs/images}/ngGK_Fig12.png        |  Bin
 {images => docs/images}/ngGK_Fig13.png        |  Bin
 {images => docs/images}/ngGK_Fig14.png        |  Bin
 {images => docs/images}/ngGK_Fig15.png        |  Bin
 {images => docs/images}/ngGK_Fig16.png        |  Bin
 {images => docs/images}/ngGK_Fig17.png        |  Bin
 {images => docs/images}/ngGK_Fig18.png        |  Bin
 {images => docs/images}/ngGK_Fig19.png        |  Bin
 {images => docs/images}/ngGK_Fig20.png        |  Bin
 {images => docs/images}/ngGK_Fig21.png        |  Bin
 {images => docs/images}/ngGK_Fig22.png        |  Bin
 {images => docs/images}/ngGK_Flowchart.png    |  Bin
 .../images}/ngSP2013WorkflowCSOM01.png        |  Bin
 .../images}/ngSP2013WorkflowCSOM02.png        |  Bin
 .../images}/ngWSSP2013WorkflowSPD2013.png     |  Bin
 .../images}/ngWSSP2013WorkflowSPD201302.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201303.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201304.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201305.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201306.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201307.png   |  Bin
 .../images}/ngWSSP2013WorkflowSPD201308.png   |  Bin
 .../images}/ngWSSP2013WorkflowVS201201.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201202.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201203.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201204.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201205.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201206.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201207.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201208.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201209.png    |  Bin
 .../images}/ngWSSP2013WorkflowVS201210.png    |  Bin
 {images => docs/images}/ngWfFig01.png         |  Bin
 {images => docs/images}/ngWfFig02.png         |  Bin
 {images => docs/images}/ngWfFig03.png         |  Bin
 {images => docs/images}/ngWfFig04.png         |  Bin
 {images => docs/images}/ngWfFig05.png         |  Bin
 {images => docs/images}/ngWfFig06.png         |  Bin
 {images => docs/images}/ngWfFig07.png         |  Bin
 {images => docs/images}/ngWfFig08.png         |  Bin
 {images => docs/images}/ngWfFig09.png         |  Bin
 {images => docs/images}/ngWfFig10.png         |  Bin
 {images => docs/images}/ngWfFig11.png         |  Bin
 {images => docs/images}/ng_MsmqFeature.png    |  Bin
 {images => docs/images}/ng_MsmqQueues.png     |  Bin
 {images => docs/images}/note.gif              |  Bin
 .../npm-outdated-global-packages-list.png     |  Bin
 .../images}/npm-outdated-packages-list.png    |  Bin
 .../npm-update-packagejson-versions.png       |  Bin
 ..._Office15_Access15OverviewDK2_Figure07.jpg |  Bin
 {images => docs/images}/pencil.GIF            |  Bin
 .../images}/postman-add-webhook-body.png      |  Bin
 .../images}/postman-get-new-access-token.png  |  Bin
 ...uredentries-multiple-web-parts-toolbox.png |  Bin
 ...econfiguredentries-needs-configuration.png |  Bin
 ...figuredentries-recent-documents-canvas.png |  Bin
 ...configuredentries-recent-images-canvas.png |  Bin
 ...onfiguredentries-recent-images-toolbox.png |  Bin
 ...edentries-three-configurations-toolbox.png |  Bin
 ...reconfiguredentries-visual-studio-code.png |  Bin
 .../images}/preconfiguredentries-yeoman.png   |  Bin
 {images => docs/images}/privclass.gif         |  Bin
 {images => docs/images}/privdelegate.gif      |  Bin
 {images => docs/images}/privdelicate.gif      |  Bin
 {images => docs/images}/privenum.gif          |  Bin
 {images => docs/images}/privenumeration.gif   |  Bin
 {images => docs/images}/privevent.gif         |  Bin
 {images => docs/images}/privextension.gif     |  Bin
 {images => docs/images}/privfield.gif         |  Bin
 {images => docs/images}/privinterface.gif     |  Bin
 {images => docs/images}/privmethod.gif        |  Bin
 {images => docs/images}/privproperty.gif      |  Bin
 {images => docs/images}/privstructure.gif     |  Bin
 .../images}/property-pane-example.png         |  Bin
 ...ation-description-error-apply-disabled.png |  Bin
 ...-validation-description-too-long-error.png |  Bin
 ...rty-validation-empty-description-error.png |  Bin
 ...perty-validation-empty-list-name-error.png |  Bin
 ...rty-validation-invalid-list-name-error.png |  Bin
 ...property-validation-list-name-property.png |  Bin
 ...alidation-partial-list-name-validation.png |  Bin
 .../property-validation-valid-list-name.png   |  Bin
 ...property-validation-visual-studio-code.png |  Bin
 .../property-validation-yeoman-generator.png  |  Bin
 {images => docs/images}/protclass.gif         |  Bin
 {images => docs/images}/protdelegate.gif      |  Bin
 {images => docs/images}/protdeligate.gif      |  Bin
 {images => docs/images}/protenum.gif          |  Bin
 {images => docs/images}/protenumeration.gif   |  Bin
 {images => docs/images}/protevent.gif         |  Bin
 {images => docs/images}/protextension.gif     |  Bin
 {images => docs/images}/protfield.gif         |  Bin
 {images => docs/images}/protinterface.gif     |  Bin
 {images => docs/images}/protmethod.gif        |  Bin
 {images => docs/images}/protoperator.gif      |  Bin
 {images => docs/images}/protproperty.gif      |  Bin
 {images => docs/images}/protstructure.gif     |  Bin
 {images => docs/images}/pubclass.gif          |  Bin
 {images => docs/images}/pubdelegate.gif       |  Bin
 {images => docs/images}/pubenum.gif           |  Bin
 {images => docs/images}/pubenumeration.gif    |  Bin
 {images => docs/images}/pubevent.gif          |  Bin
 {images => docs/images}/pubextension.gif      |  Bin
 {images => docs/images}/pubfield.gif          |  Bin
 {images => docs/images}/pubinterface.gif      |  Bin
 {images => docs/images}/pubmethod.gif         |  Bin
 {images => docs/images}/puboperator.gif       |  Bin
 {images => docs/images}/pubproperty.gif       |  Bin
 {images => docs/images}/pubstructure.gif      |  Bin
 ...ing-dropdowns-item-dropdown-list-items.png |  Bin
 ...pdowns-itemname-property-pane-dropdown.png |  Bin
 ...ns-itemname-property-web-part-manifest.png |  Bin
 ...ropdowns-list-dropdown-available-lists.png |  Bin
 ...-dropdowns-list-selected-item-disabled.png |  Bin
 ...pdowns-listname-property-pane-dropdown.png |  Bin
 ...ns-listname-property-web-part-manifest.png |  Bin
 ...s-loading-indicator-when-loading-items.png |  Bin
 ...ading-indicator-when-loading-list-info.png |  Bin
 ...cascading-dropdowns-visual-studio-code.png |  Bin
 ...cascading-dropdowns-web-part-first-run.png |  Bin
 ...eact-cascading-dropdowns-yo-sharepoint.png |  Bin
 {images => docs/images}/requirements1a.gif    |  Bin
 {images => docs/images}/requirements1c.gif    |  Bin
 {images => docs/images}/save.gif              |  Bin
 {images => docs/images}/save_hover.gif        |  Bin
 {images => docs/images}/security.gif          |  Bin
 {images => docs/images}/seealso1a.gif         |  Bin
 {images => docs/images}/seealso1c.gif         |  Bin
 .../images}/sp-app-deploy-trust.png           |  Bin
 .../images}/sp-app-replace-pkg.png            |  Bin
 .../images}/sp-helloworld-wp-modern-page.png  |  Bin
 .../images}/sp-lists-render-localhost.png     |  Bin
 .../images}/sp-lists-render-spsite.png        |  Bin
 .../images}/sp-lists-spsiteurl-wp.png         |  Bin
 .../images}/sp-mock-localhost-wp.png          |  Bin
 .../images}/sp-modern-page-toolbox.png        |  Bin
 .../images}/sp-modern-site-page.png           |  Bin
 .../sp-pnp-js-guide-completed-setup.png       |  Bin
 .../images}/sp-pnp-js-guide-first-open.png    |  Bin
 .../images}/sp-pnp-js-guide-first-run.png     |  Bin
 .../sp-pnp-js-guide-with-mock-data.png        |  Bin
 {images => docs/images}/sp-sample-todo-wp.png |  Bin
 .../images}/sp-workbench-helloworld-pp.png    |  Bin
 .../images}/sp-workbench-helloworld-wp.png    |  Bin
 .../sp-workbench-o365-helloworld-wp.png       |  Bin
 .../images}/sp-workbench-o365-toolbox.png     |  Bin
 .../sp-workbench-o365-unsface-scripts.png     |  Bin
 {images => docs/images}/sp-workbench-o365.png |  Bin
 .../images}/sp-workbench-toolbox.png          |  Bin
 {images => docs/images}/sp-workbench.png      |  Bin
 .../images}/sp-wp-classic-page-pp.png         |  Bin
 .../images}/sp-wp-classic-page.png            |  Bin
 .../images}/sp-wp-modern-page-pp.png          |  Bin
 {images => docs/images}/sp-wp-modern-page.png |  Bin
 ...n_CreateDisplayTemplateSP2013_Figure02.png |  Bin
 .../sp15Con_DesignPackageExp_Figure1.png      |  Bin
 .../images}/sp15Con_DeviceChannels_Fig1.png   |  Bin
 .../sp15Con_SiteMasterPage_Figure2.png        |  Bin
 {images => docs/images}/sp15_BM25_formula.gif |  Bin
 .../images}/sp15_freshness_formula.gif        |  Bin
 .../images}/sp15_linear_model_formula.gif     |  Bin
 .../images}/sp15_neural_network_formula.gif   |  Bin
 .../sp15_transform_table_ranking_model.gif    |  Bin
 .../sp15neuralnetworkinrankingmodels.gif      |  Bin
 {images => docs/images}/spd15-.JPG            |  Bin
 .../images}/spd15-AddListItemPerms-txt.JPG    |  Bin
 .../images}/spd15-AddListItemPerms-visio.JPG  |  Bin
 .../images}/spd15-AssignForm2Grp-txt.JPG      |  Bin
 .../images}/spd15-AssignForm2Grp-visio.JPG    |  Bin
 .../images}/spd15-AssignToDoItem-txt.JPG      |  Bin
 .../images}/spd15-AssignToDoItem-visio.JPG    |  Bin
 .../images}/spd15-CheckInItem-txt.JPG         |  Bin
 .../images}/spd15-CheckInItem-visio.JPG       |  Bin
 .../images}/spd15-CheckOutItem-txt.JPG        |  Bin
 .../images}/spd15-CheckOutItem-visio.JPG      |  Bin
 .../images}/spd15-ChkExactUserPerms-txt.JPG   |  Bin
 .../images}/spd15-ChkExactUserPerms-visio.JPG |  Bin
 .../images}/spd15-ChkUserPerms-txt.JPG        |  Bin
 .../images}/spd15-ChkUserPerms-visio.JPG      |  Bin
 .../images}/spd15-CollectDataFrUser-txt.JPG   |  Bin
 .../images}/spd15-CollectDataFrUser-visio.JPG |  Bin
 .../images}/spd15-CompareDataSrc-txt.JPG      |  Bin
 .../images}/spd15-CompareDataSrc-visio.JPG    |  Bin
 .../images}/spd15-CompareDocField-txt.JPG     |  Bin
 .../images}/spd15-CompareDocField-visio.JPG   |  Bin
 .../images}/spd15-CopyListItem-txt.JPG        |  Bin
 .../images}/spd15-CopyListItem-visio.JPG      |  Bin
 .../images}/spd15-CreateListItem-txt.JPG      |  Bin
 .../images}/spd15-CreateListItem-visio.JPG    |  Bin
 .../images}/spd15-CreatedBySpecPerson-txt.JPG |  Bin
 .../spd15-CreatedBySpecPerson-visio.JPG       |  Bin
 .../spd15-CreatedInSpecDateSpan-txt.JPG       |  Bin
 .../spd15-CreatedInSpecDateSpan-visio.JPG     |  Bin
 .../images}/spd15-DeleteItem-txt.JPG          |  Bin
 .../images}/spd15-DeleteItem-visio.JPG        |  Bin
 .../images}/spd15-DiscardItem-txt.JPG         |  Bin
 .../images}/spd15-DiscardItem-visio.JPG       |  Bin
 .../images}/spd15-FileIsSpecType-txt.JPG      |  Bin
 .../images}/spd15-FileIsSpecType-visio.JPG    |  Bin
 .../images}/spd15-FileSzInSpecRange-txt.JPG   |  Bin
 .../images}/spd15-FileSzInSpecRange-visio.JPG |  Bin
 .../images}/spd15-ImportFromVisio.JPG         |  Bin
 .../spd15-InheritListItemPerms-txt.JPG        |  Bin
 .../spd15-InheritListItemPerms-visio.JPG      |  Bin
 {images => docs/images}/spd15-LogHist-txt.JPG |  Bin
 .../images}/spd15-LogHist-visio.JPG           |  Bin
 .../images}/spd15-LookupMgr4User-txt.JPG      |  Bin
 .../images}/spd15-LookupMgr4User-visio.JPG    |  Bin
 .../spd15-ModifiedBySpecPerson-txt.JPG        |  Bin
 .../spd15-ModifiedBySpecPerson-visio.JPG      |  Bin
 .../spd15-ModifiedInSpecDateSpan-txt.JPG      |  Bin
 .../spd15-ModifiedInSpecDateSpan-visio.JPG    |  Bin
 .../images}/spd15-PauseDate-txt.JPG           |  Bin
 .../images}/spd15-PauseDate-visio.JPG         |  Bin
 .../images}/spd15-PauseDuration-txt.JPG       |  Bin
 .../images}/spd15-PauseDuration-visio.JPG     |  Bin
 .../spd15-ReplaceListItemPerms-txt.JPG        |  Bin
 .../spd15-ReplaceListItemPerms-visio.JPG      |  Bin
 .../images}/spd15-RmListItemPerms-txt.JPG     |  Bin
 .../images}/spd15-RmListItemPerms-visio.JPG   |  Bin
 .../images}/spd15-SendApproval4DocSet-txt.JPG |  Bin
 .../spd15-SendApproval4DocSet-visio.JPG       |  Bin
 .../images}/spd15-SendDoc2Repos-txt.JPG       |  Bin
 .../images}/spd15-SendDoc2Repos-visio.JPG     |  Bin
 .../images}/spd15-SendDocSet2Repos-txt.JPG    |  Bin
 .../images}/spd15-SendDocSet2Repos-visio.JPG  |  Bin
 .../spd15-SetContentApprStatus-visio.JPG      |  Bin
 .../spd15-SetContentApprStatus4DocSet-txt.JPG |  Bin
 .../spd15-SetContentApprovalStatus-txt.JPG    |  Bin
 .../spd15-SetContentApprovalStatus-visio.JPG  |  Bin
 .../images}/spd15-SetFieldCurrItem-txt.JPG    |  Bin
 .../images}/spd15-SetFieldCurrItem-visio.JPG  |  Bin
 .../images}/spd15-SetTimePortion-txt.JPG      |  Bin
 .../images}/spd15-SetTimePortion-visio.JPG    |  Bin
 .../images}/spd15-SetWFStatus-txt.JPG         |  Bin
 .../images}/spd15-SetWFStatus-visio.JPG       |  Bin
 .../images}/spd15-SetWFVar-txt.JPG            |  Bin
 .../images}/spd15-SetWFVar-visio.JPG          |  Bin
 .../images}/spd15-StartApprovalProc-txt.JPG   |  Bin
 .../images}/spd15-StartApprovalProc-visio.JPG |  Bin
 .../images}/spd15-StartCustomTask-txt.JPG     |  Bin
 .../images}/spd15-StartCustomTask-visio.JPG   |  Bin
 .../images}/spd15-StartFeedback-txt.JPG       |  Bin
 .../images}/spd15-StartFeedback-visio.JPG     |  Bin
 {images => docs/images}/spd15-StopWF-txt.JPG  |  Bin
 .../images}/spd15-StopWF-visio.JPG            |  Bin
 .../images}/spd15-TaskActions1.png            |  Bin
 .../images}/spd15-TitleFieldKeywords-txt.JPG  |  Bin
 .../spd15-TitleFieldKeywords-visio.JPG        |  Bin
 .../images}/spd15-UpdateListItem-txt.JPG      |  Bin
 .../images}/spd15-UpdateListItem-visio.JPG    |  Bin
 .../images}/spd15-WFStart-icon.JPG            |  Bin
 {images => docs/images}/spd15-WFStop-icon.JPG |  Bin
 .../images}/spd15-Wait4FieldChange-txt.JPG    |  Bin
 .../images}/spd15-Wait4FieldChange-visio.JPG  |  Bin
 .../images}/spd15-addcomment-txt.JPG          |  Bin
 .../images}/spd15-addcomment-visio.JPG        |  Bin
 .../images}/spd15-addtimetodate-txt.JPG       |  Bin
 .../images}/spd15-addtimetodate-visio.JPG     |  Bin
 {images => docs/images}/spd15-docalc-txt.JPG  |  Bin
 .../images}/spd15-docalc-visio.JPG            |  Bin
 {images => docs/images}/spd15-wf-PO.JPG       |  Bin
 {images => docs/images}/spd15-wf-error1.JPG   |  Bin
 {images => docs/images}/spd15-wf-error11.JPG  |  Bin
 {images => docs/images}/spd15-wf-error12.JPG  |  Bin
 {images => docs/images}/spd15-wf-error13.JPG  |  Bin
 {images => docs/images}/spd15-wf-error14.JPG  |  Bin
 {images => docs/images}/spd15-wf-error15.JPG  |  Bin
 {images => docs/images}/spd15-wf-error16.JPG  |  Bin
 {images => docs/images}/spd15-wf-error17.JPG  |  Bin
 {images => docs/images}/spd15-wf-error18.JPG  |  Bin
 {images => docs/images}/spd15-wf-error19.JPG  |  Bin
 {images => docs/images}/spd15-wf-error2.JPG   |  Bin
 {images => docs/images}/spd15-wf-error20.JPG  |  Bin
 {images => docs/images}/spd15-wf-error21.JPG  |  Bin
 {images => docs/images}/spd15-wf-error3.JPG   |  Bin
 {images => docs/images}/spd15-wf-error4.JPG   |  Bin
 {images => docs/images}/spd15-wf-error5.JPG   |  Bin
 {images => docs/images}/spd15-wf-error6.JPG   |  Bin
 {images => docs/images}/spd15-wf-error7.JPG   |  Bin
 {images => docs/images}/spd15-wf-error8.JPG   |  Bin
 {images => docs/images}/spd15-wf-error9.JPG   |  Bin
 .../images}/spd15-wf-exportToVisio.png        |  Bin
 .../images}/spd15-wf-importFromVisio.png      |  Bin
 .../images}/spd15-wf-logical-ops.JPG          |  Bin
 {images => docs/images}/spd15-wf-step1a.JPG   |  Bin
 {images => docs/images}/spd15-wf.JPG          |  Bin
 .../images}/spfx-ext-youtube-tutorial1.png    |  Bin
 .../images}/spfx-ext-youtube-tutorial2.png    |  Bin
 .../images}/spfx-ext-youtube-tutorial3.png    |  Bin
 .../images}/spfx-ext-youtube-tutorial4.png    |  Bin
 .../spfx-ext-youtube-tutorialcommand.png      |  Bin
 .../spfx-ext-youtube-tutorialfield.png        |  Bin
 ...ast-youtube-provision-feature-elements.png |  Bin
 .../images}/spfx-youtube-tutorial0.png        |  Bin
 .../images}/spfx-youtube-tutorial1.png        |  Bin
 .../images}/spfx-youtube-tutorial2.png        |  Bin
 .../images}/spfx-youtube-tutorial3.png        |  Bin
 .../images}/spfx-youtube-tutorial4.png        |  Bin
 .../images}/spfx-youtube-tutorial5.png        |  Bin
 .../images}/spfx-youtube-tutorial6.png        |  Bin
 {images => docs/images}/static.gif            |  Bin
 .../images}/tenant-deploy-app-catalog.png     |  Bin
 .../images}/tenant-deploy-yeoman.png          |  Bin
 .../images}/tenant-deploy-youtube-video.png   |  Bin
 {images => docs/images}/theme_.PNG            |  Bin
 .../themed-styles-blue-web-part-red-site.png  |  Bin
 .../images}/themed-styles-button-class.png    |  Bin
 ...emed-styles-ms-bgcolor-themedark-class.png |  Bin
 .../images}/themed-styles-row-class.png       |  Bin
 .../images}/themed-styles-side-by-side.png    |  Bin
 .../thirdpartycss-accordion-not-styled.png    |  Bin
 .../thirdpartycss-accordion-styled.png        |  Bin
 .../thirdpartycss-jquery-ui-css-size.png      |  Bin
 .../images}/thirdpartycss-libraries-cdn.png   |  Bin
 .../thirdpartycss-visual-studio-code.png      |  Bin
 .../images}/thirdpartycss-yeoman.png          |  Bin
 .../images}/toolchain-gulp-serve-task.png     |  Bin
 .../tutorial-feature-solution-add-app.png     |  Bin
 .../tutorial-feature-solution-app-details.png |  Bin
 ...tutorial-feature-solution-debug-folder.png |  Bin
 .../tutorial-feature-solution-hover-menu.png  |  Bin
 ...ial-feature-solution-initial-structure.png |  Bin
 .../tutorial-feature-solution-list-view.png   |  Bin
 .../tutorial-feature-solution-new-list.png    |  Bin
 ...torial-feature-solution-override-sppkg.png |  Bin
 ...utorial-feature-solution-provision-app.png |  Bin
 ...ial-feature-solution-trust-app-catalog.png |  Bin
 ...tutorial-feature-solution-updating-app.png |  Bin
 .../tutorial-feature-solution-version-2.png   |  Bin
 .../tutorial-sharingdata-console-log.png      |  Bin
 ...haringdata-interfaces-documentsservice.png |  Bin
 .../tutorial-sharingdata-interfaces.png       |  Bin
 ...gdata-recent-document-recent-documents.png |  Bin
 .../tutorial-sharingdata-recent-document.png  |  Bin
 .../tutorial-sharingdata-recent-documents.png |  Bin
 .../images}/tutorial-sharingdata-vscode.png   |  Bin
 ...ringdata-yo-sharepoint-recent-document.png |  Bin
 ...ingdata-yo-sharepoint-recent-documents.png |  Bin
 .../images}/tutorial-spjsom-vscode.png        |  Bin
 .../tutorial-spjsom-web-part-list-titles.png  |  Bin
 .../images}/tutorial-spjsom-yo-sharepoint.png |  Bin
 .../images}/upload-solution-app-catalog.png   |  Bin
 ...code-debugging-add-debug-configuration.png |  Bin
 ...de-debugging-adding-web-part-to-canvas.png |  Bin
 .../vscode-debugging-breakpoint-active.png    |  Bin
 ...vscode-debugging-breakpoint-configured.png |  Bin
 .../vscode-debugging-breakpoint-hit-o365.png  |  Bin
 .../vscode-debugging-breakpoint-hit.png       |  Bin
 ...ode-debugging-chrome-debug-environment.png |  Bin
 .../vscode-debugging-chrome-started.png       |  Bin
 ...de-debugging-debugger-chrome-extension.png |  Bin
 ...ng-debugger-extension-installed-reload.png |  Bin
 ...e-debugging-debugging-hosted-workbench.png |  Bin
 .../images}/vscode-debugging-gulp-serve.png   |  Bin
 .../images}/vscode-debugging-o365-login.png   |  Bin
 .../images}/vscode-debugging-vscode-debug.png |  Bin
 .../vscode-debugging-vscode-extensions.png    |  Bin
 .../images}/webhook-azure-function0.png       |  Bin
 .../images}/webhook-azure-function1.png       |  Bin
 .../images}/webhook-azure-function2.png       |  Bin
 .../images}/webhook-azure-function3.png       |  Bin
 .../images}/webhook-azure-function4.png       |  Bin
 .../images}/webhook-azure-function5.png       |  Bin
 .../images}/webhook-azure-function6.png       |  Bin
 .../images}/webhook-azure-function7.png       |  Bin
 .../images}/webhook-azure-function8.png       |  Bin
 .../images}/webhook-sample-add-process.png    |  Bin
 .../images}/webhook-sample-application.png    |  Bin
 .../webhook-sample-async-getchanges.png       |  Bin
 .../images}/webhook-sample-call-webhook.png   |  Bin
 .../webhook-sample-end-to-end-flow.png        |  Bin
 .../webpart-configure-property-pane.png       |  Bin
 .../images}/webpart-gallery-helloworld.png    |  Bin
 .../images}/wf15-eventingactions3.png         |  Bin
 .../images}/wf15-eventingactions4.png         |  Bin
 .../images}/wfAddNewItemDialog_b2.png         |  Bin
 {images => docs/images}/wfArchitecture1.png   |  Bin
 {images => docs/images}/wfInteropBridge.png   |  Bin
 .../images}/wfInteropMessaging.png            |  Bin
 {images => docs/images}/wfInterop_.png        |  Bin
 {images => docs/images}/wfInterop_Stage1.png  |  Bin
 {images => docs/images}/wfNewProject_b2.png   |  Bin
 {images => docs/images}/wfSimple.gif          |  Bin
 {images => docs/images}/wfToolbox_b2.png      |  Bin
 {images => docs/images}/wfVS_ActivityNode.jpg |  Bin
 {images => docs/images}/wfVS_NewItem.JPG      |  Bin
 .../images}/wfVS_NewProjectDialog.JPG         |  Bin
 .../images}/wfVS_WorkflowToolbox.jpg          |  Bin
 {images => docs/images}/wn_DevTools_1.png     |  Bin
 {images => docs/images}/wn_DevTools_2.png     |  Bin
 {images => docs/images}/wn_DevTools_3.png     |  Bin
 {images => docs/images}/wn_Mobility_.png      |  Bin
 {images => docs/images}/wn_Mobility_2.png     |  Bin
 {images => docs/images}/wn_Mobility_3.png     |  Bin
 {images => docs/images}/wn_Platform_1.png     |  Bin
 {images => docs/images}/wn_Platform_2.png     |  Bin
 {images => docs/images}/wn_Platform_3.png     |  Bin
 {images => docs/images}/wn_Platform_4.png     |  Bin
 {images => docs/images}/wn_Social_1.png       |  Bin
 {images => docs/images}/wn_Social_2.png       |  Bin
 {images => docs/images}/wn_Social_3.png       |  Bin
 {images => docs/images}/wn_Social_4.png       |  Bin
 {images => docs/images}/wn_WebStandards_1.png |  Bin
 {images => docs/images}/wn_WebStandards_2.png |  Bin
 {images => docs/images}/wn_WebStandards_3.png |  Bin
 {images => docs/images}/wn_WebStandards_4.png |  Bin
 {images => docs/images}/wn_appServices_1.png  |  Bin
 {images => docs/images}/wn_appServices_2.png  |  Bin
 {images => docs/images}/wn_appServices_3.png  |  Bin
 {images => docs/images}/wn_appServices_4.png  |  Bin
 {images => docs/images}/wn_bcs_1.png          |  Bin
 {images => docs/images}/wn_bcs_2.png          |  Bin
 {images => docs/images}/wn_bcs_3.png          |  Bin
 {images => docs/images}/wn_cloud_1.png        |  Bin
 {images => docs/images}/wn_cloud_2.png        |  Bin
 {images => docs/images}/wn_cloud_3.png        |  Bin
 {images => docs/images}/wn_ecm_1.png          |  Bin
 {images => docs/images}/wn_ecm_2.png          |  Bin
 {images => docs/images}/wn_ecm_3.png          |  Bin
 {images => docs/images}/wn_ecm_4.png          |  Bin
 {images => docs/images}/wn_search_1.png       |  Bin
 {images => docs/images}/wn_search_2.png       |  Bin
 {images => docs/images}/wn_search_3.png       |  Bin
 {images => docs/images}/wn_workflow_1.png     |  Bin
 {images => docs/images}/wn_workflow_2.png     |  Bin
 {images => docs/images}/wn_workflow_3.png     |  Bin
 {images => docs/images}/wn_workflow_4.png     |  Bin
 {images => docs/images}/xna.gif               |  Bin
 .../images}/yeoman-sp-cmdline-options.png     |  Bin
 .../images}/yeoman-sp-complete.png            |  Bin
 .../images}/yeoman-sp-generator.png           |  Bin
 {images => docs/images}/yeoman-sp-prompts.png |  Bin
 .../youtube-getting-started-with-webhooks.png |  Bin
 ...outube-introducing-sharepoint-webhooks.png |  Bin
 docs/index.md                                 |   39 +
 ...-add-ins-using-the-cross-domain-library.md |   33 +-
 ...to-a-sharepoint-hostedsharepoint-add-in.md |   26 +-
 ...o-a-sharepoint-hosted-sharepoint-add-in.md |   26 +-
 ...n-a-sharepoint-hosted-sharepoint-add-in.md |   23 +-
 ...o-a-sharepoint-hosted-sharepoint-add-in.md |   45 +-
 ...o-a-sharepoint-hosted-sharepoint-add-in.md |   29 +-
 ...to-a-sharepoint-hostedsharepoint-add-in.md |   25 +-
 ...run-logic-to-the-provider-hosted-add-in.md |   35 +-
 ...uthorization-policy-types-in-sharepoint.md |   23 +-
 .../add-in-permissions-in-sharepoint.md       |   31 +-
 ...perations-to-the-provider-hosted-add-in.md |   27 +-
 ...ciate-a-document-library-with-an-entity.md |   31 +-
 ...nd-authentication-of-sharepoint-add-ins.md |   25 +-
 ...-code-oauth-flow-for-sharepoint-add-ins.md |   49 +-
 ...ping-and-hosting-your-sharepoint-add-in.md |   55 +-
 ...g-javascript-library-code-in-sharepoint.md |   31 +-
 ...ns-using-sharepoint-client-library-code.md |   15 +-
 ...rations-using-sharepoint-rest-endpoints.md |   51 +-
 ...token-oauth-flow-for-sharepoint-add-ins.md |   31 +-
 ...oint-add-in-to-a-provider-hosted-add-in.md |   53 +-
 ...y-using-napa-office-365-development-too.md |   29 +-
 ...siness-add-in-that-uses-the-sap-gateway.md |   31 +-
 ...-business-add-in-with-a-social-newsfeed.md |   25 +-
 .../create-a-cloud-business-add-in.md         |   21 +-
 ...-the-cross-domain-library-in-sharepoint.md |   45 +-
 ...-in-the-host-web-of-a-sharepoint-add-in.md |   35 +-
 ...-on-an-existing-office-365-subscription.md |   15 +-
 ...-the-update-event-in-sharepoint-add-ins.md |   33 +-
 ...udes-a-custom-sharepoint-list-and-conte.md |   33 +-
 ...te-event-receiver-in-sharepoint-add-ins.md |   21 +-
 ...a-document-template-and-a-task-pane-add.md |   17 +-
 ...-to-install-with-your-sharepoint-add-in.md |   59 +-
 ...in-event-receiver-in-sharepoint-add-ins.md |   27 +-
 ...er-hosted-high-trust-sharepoint-add-ins.md |   17 +-
 .../create-cloud-business-add-ins.md          |   17 +-
 ...tions-to-deploy-with-sharepoint-add-ins.md |   47 +-
 .../create-high-trust-sharepoint-add-ins.md   |   47 +-
 ...-to-access-sap-data-by-using-the-sap-ga.md |   39 +-
 ...ate-sharepoint-add-ins-in-visual-studio.md |   23 +-
 ...ins-that-can-be-used-by-anonymous-users.md |   23 +-
 .../create-ux-components-in-sharepoint.md     |   29 +-
 ...d-ins-that-use-high-trust-authorization.md |   25 +-
 ...dd-ins-that-use-low-trust-authorization.md |   31 +-
 ...d-ins-that-use-the-cross-domain-library.md |   19 +-
 ...int-add-ins-using-client-side-rendering.md |   39 +-
 ...e-event-receiver-in-a-sharepoint-add-in.md |   19 +-
 ...l-a-sharepoint-hosted-sharepoint-add-in.md |   20 +-
 ...-sharepoint-add-ins-methods-and-options.md |   17 +-
 docs/sp-add-ins/design-sharepoint-add-ins.md  |   27 +-
 ...e-sharepoint-rest-service-endpoint-uris.md |   41 +-
 .../develop-cloud-business-add-ins.md         |   19 +-
 docs/sp-add-ins/develop-sharepoint-add-ins.md |   35 +-
 ...-a-newsfeed-for-a-cloud-business-add-in.md |   17 +-
 ...-and-the-package-of-a-sharepoint-add-in.md |   27 +-
 ...overview-of-the-sharepoint-object-model.md |   19 +-
 ...ting-provider-hosted-sharepoint-add-ins.md |   31 +-
 ...ng-sharepoint-hosted-sharepoint-add-ins.md |   35 +-
 ...arted-developing-cloud-business-add-ins.md |   15 +-
 ...get-to-know-the-sharepoint-rest-service.md |   31 +-
 ...r-identity-and-properties-in-sharepoint.md |   29 +-
 ...ted-add-in-the-sharepoint-look-and-feel.md |   33 +-
 ...in-events-in-the-provider-hosted-add-in.md |   29 +-
 .../handle-events-in-sharepoint-add-ins.md    |   35 +-
 ...em-events-in-the-provider-hosted-add-in.md |   49 +-
 ...der-hosted-low-trust-sharepoint-add-ins.md |   42 +-
 ...st-configuration-scripts-for-sharepoint.md |   14 +-
 ...onality-of-sharepoint-hosted-sharepoint.md |   20 +-
 ...and-sharepoint-components-in-sharepoint.md |   22 +-
 ...n-architecture-and-development-landscap.md |   50 +-
 ...anager-a-cloud-business-add-in-tutorial.md |   92 +-
 ...om-button-in-the-provider-hosted-add-in.md |   26 +-
 ...web-part-in-a-webpage-on-the-add-in-web.md |   14 +-
 ...d-in-part-in-the-provider-hosted-add-in.md |   26 +-
 .../sp-add-ins/localize-sharepoint-add-ins.md |   23 +-
 .../make-batch-requests-with-the-rest-apis.md |    8 +-
 ...ructure-represented-in-the-rest-service.md |   22 +-
 .../new-name-for-apps-for-sharepoint.md       |    8 +-
 ...e-web-widgetsexperimental-license-terms.md |   15 +-
 ...office-web-widgetsexperimental-overview.md |   36 +-
 ...d-publish-high-trust-sharepoint-add-ins.md |   38 +-
 ...om-button-in-the-provider-hosted-add-in.md |   32 +-
 ...ment-library-in-a-cloud-business-add-in.md |   30 +-
 ...h-a-cloud-business-add-in-to-sharepoint.md |   16 +-
 .../publish-cloud-business-add-ins.md         |   12 +-
 ...arepoint-add-ins-by-using-visual-studio.md |   14 +-
 docs/sp-add-ins/publish-sharepoint-add-ins.md |   16 +-
 ...rvice-using-the-web-proxy-in-sharepoint.md |   46 +-
 .../sp-add-ins/register-sharepoint-add-ins.md |   24 +-
 ...ng-client-secret-in-a-sharepoint-add-in.md |    8 +-
 ...nt-object-models-for-sharepoint-add-ins.md |   36 +-
 ...s-on-a-list-by-using-the-rest-interface.md |   18 +-
 ...nt-for-sharepoint-add-ins-on-office-365.md |   25 +-
 ...ment-environment-for-sharepoint-add-ins.md |   26 +-
 .../sharepoint-add-ins-update-process.md      |   30 +-
 ...sharepoint-add-ins-ux-design-guidelines.md |  155 ++-
 docs/sp-add-ins/sharepoint-add-ins.md         |   28 +-
 ...net-server-csom-jsom-and-rest-api-index.md |   14 +-
 ...sharepoint-items-using-the-rest-service.md |   22 +-
 ...eployment-scopes-for-sharepoint-add-ins.md |   18 +-
 ...rization-systems-for-sharepoint-add-ins.md |   17 +-
 ...t-design-options-for-sharepoint-add-ins.md |   30 +-
 ...ments-for-developing-sharepoint-add-ins.md |   20 +-
 .../troubleshooting-document-libraries.md     |   12 +-
 ...eshooting-high-trust-sharepoint-add-ins.md |   10 +-
 ...ate-add-in-web-components-in-sharepoint.md |   31 +-
 ...pdate-host-web-components-in-sharepoint.md |   24 +-
 ...remote-components-in-sharepoint-add-ins.md |   22 +-
 docs/sp-add-ins/update-sharepoint-add-ins.md  |   47 +-
 ...a-file-by-using-the-rest-api-and-jquery.md |   20 +-
 ...trings-and-tokens-in-sharepoint-add-ins.md |    8 +-
 ...ite-s-style-sheet-in-sharepoint-add-ins.md |   40 +-
 ...horize-provider-hosted-add-ins-on-an-on.md |   26 +-
 ...-operations-in-sharepoint-rest-requests.md |   30 +-
 ...nt-chrome-control-in-sharepoint-add-ins.md |   50 +-
 ...-in-sharepoint-hosted-sharepoint-add-in.md |   16 +-
 ...-list-view-widget-in-sharepoint-add-ins.md |   24 +-
 ...ple-picker-widget-in-sharepoint-add-ins.md |   32 +-
 ...cript-apis-to-work-with-sharepoint-data.md |   34 +-
 .../ux-design-for-sharepoint-add-ins.md       |   50 +-
 ...ffice-developer-tools-for-visual-studio.md |   10 +-
 .../work-with-external-data-in-sharepoint.md  |   18 +-
 ...-data-from-javascript-in-the-add-in-web.md |   52 +-
 ...-different-internet-explorer-security-z.md |   31 +-
 ...orking-with-folders-and-files-with-rest.md |   32 +-
 ...ing-with-lists-and-list-items-with-rest.md |   28 +-
 ...l-microsoft-graph-using-graphhttpclient.md |   11 +-
 docs/spfx/css-recommendations.md              |   11 +-
 docs/spfx/debug-in-vscode.md                  |   37 +-
 docs/spfx/enterprise-guidance.md              |   15 +-
 .../changes-between-dev-preview-and-rc.md     |   44 +-
 .../build-a-hello-world-extension.md          |  150 ++-
 .../building-simple-cmdset-with-dialog-api.md |   37 +-
 .../building-simple-field-customizer.md       |   53 +-
 .../hosting-extension-from-office365-cdn.md   |   19 +-
 .../serving-your-extension-from-sharepoint.md |   17 +-
 .../using-page-placeholder-with-extensions.md |  393 +++---
 .../using-custom-dialogs-with-spfx.md         |   23 +-
 docs/spfx/extensions/overview-extensions.md   |   15 +-
 .../spfx/known-issues-and-common-questions.md |   12 +-
 docs/spfx/roadmap.md                          |   10 +-
 docs/spfx/set-up-your-developer-tenant.md     |    9 +-
 .../set-up-your-development-environment.md    |   15 +-
 docs/spfx/sharepoint-2016-support.md          |    9 +-
 docs/spfx/sharepoint-framework-overview.md    |   13 +-
 ...sed-development-on-sharepoint-framework.md |    7 +
 docs/spfx/tenant-scoped-deployment.md         |   13 +-
 .../extending-webpack-in-build-pipeline.md    |    7 +
 .../integrate-gulp-tasks-in-build-pipeline.md |   15 +-
 .../optimize-builds-for-production.md         |   21 +-
 .../toolchain/provision-sharepoint-assets.md  |    9 +-
 ...jects-using-yeoman-sharepoint-generator.md |    9 +-
 .../sharepoint-framework-toolchain.md         |   13 +-
 docs/spfx/toolchain/update-latest-packages.md |    9 +-
 docs/spfx/tools-and-libraries.md              |   11 +-
 docs/spfx/update-latest-packages.md           |   15 +-
 ...use-theme-colors-in-your-customizations.md |   17 +-
 .../basics/add-an-external-library.md         |    7 +
 .../design-considerations-for-web-parts.md    |   51 +-
 .../basics/integrate-with-property-pane.md    |   15 +-
 .../basics/notes-on-solution-packaging.md     |    7 +
 .../basics/working-with-requestdigest.md      |    7 +
 .../add-jqueryui-accordion-to-web-part.md     |   13 +-
 .../build-a-hello-world-web-part.md           |   39 +-
 .../get-started/connect-to-sharepoint.md      |   21 +-
 .../get-started/deploy-web-part-to-cdn.md     |   29 +-
 .../hosting-webpart-from-office-365-cdn.md    |   27 +-
 .../provision-sp-assets-from-package.md       |   33 +-
 ...erve-your-web-part-in-a-sharepoint-page.md |   33 +-
 .../use-fabric-react-components.md            |   15 +-
 ...-client-side-web-parts-with-angular-1-x.md |   51 +-
 .../build-custom-property-pane-controls.md    |   39 +-
 ...call-microsoft-graph-from-your-web-part.md |    7 +
 .../connect-to-api-secured-with-aad.md        |   97 +-
 .../connect-to-sharepoint-using-jsom.md       |   19 +-
 .../guidance/governance-considerations.md     |   13 +-
 ...ate-web-part-properties-with-sharepoint.md |   13 +-
 .../web-parts/guidance/localize-web-parts.md  |   43 +-
 ...-x-applications-to-sharepoint-framework.md |   45 +-
 ...igrate-jquery-datatables-script-to-spfx.md |   37 +-
 ...rate-jquery-fullcalendar-script-to-spfx.md |   29 +-
 ...e-script-editor-web-part-customizations.md |    7 +
 .../guidance/office-ui-fabric-integration.md  |    7 +
 .../reference-third-party-css-styles.md       |   29 +-
 .../guidance/share-data-between-web-parts.md  |   27 +-
 ...ng-web-parts-with-preconfigured-entries.md |   35 +-
 ...-data-between-web-parts-global-variable.md |   71 +-
 ...cading-dropdowns-in-web-part-properties.md |   35 +-
 .../use-existing-javascript-libraries.md      |   27 +-
 .../use-sp-pnp-js-with-spfx-web-parts.md      |   15 +-
 .../validate-web-part-property-values.md      |   31 +-
 .../overview-client-side-web-parts.md         |    7 +
 docs/toc.yml                                  | 1195 +++++++++++++++++
 general-development/docfx.json                |   37 +
 images/spfx-fp2-youtube-video.png             |  Bin 65307 -> 0 bytes
 misc/SharePointDocumentationToc.xml           |  662 ---------
 misc/SharePointReferenceToc.xml               |  225 ----
 misc/SharepointBreadcrumbs.json               |   41 -
 reference/spfx/es6-collections-module.md      |   29 -
 .../interface/__new-mapconstructor.md         |   18 -
 .../interface/__new-setconstructor.md         |   18 -
 .../interface/__new-weakmapconstructor.md     |   18 -
 .../interface/__new-weaksetconstructor.md     |   18 -
 .../spfx/es6-collections/interface/add-set.md |   18 -
 .../es6-collections/interface/add-weakset.md  |   18 -
 .../es6-collections/interface/clear-map.md    |   18 -
 .../es6-collections/interface/clear-set.md    |   18 -
 .../interface/clear-weakmap.md                |   18 -
 .../interface/clear-weakset.md                |   18 -
 .../es6-collections/interface/delete-map.md   |   18 -
 .../es6-collections/interface/delete-set.md   |   18 -
 .../interface/delete-weakmap.md               |   18 -
 .../interface/delete-weakset.md               |   18 -
 .../es6-collections/interface/entries-map.md  |   18 -
 .../es6-collections/interface/entries-set.md  |   18 -
 .../interface/foreach-foreachable.md          |   18 -
 .../es6-collections/interface/foreach-map.md  |   18 -
 .../es6-collections/interface/foreach-set.md  |   18 -
 .../es6-collections/interface/foreachable.md  |   25 -
 .../spfx/es6-collections/interface/get-map.md |   18 -
 .../es6-collections/interface/get-weakmap.md  |   18 -
 .../spfx/es6-collections/interface/has-map.md |   18 -
 .../spfx/es6-collections/interface/has-set.md |   18 -
 .../es6-collections/interface/has-weakmap.md  |   18 -
 .../es6-collections/interface/has-weakset.md  |   18 -
 .../es6-collections/interface/iterator.md     |   27 -
 .../interface/iteratorresult.md               |   25 -
 .../es6-collections/interface/keys-map.md     |   18 -
 .../es6-collections/interface/keys-set.md     |   18 -
 .../spfx/es6-collections/interface/map.md     |   39 -
 .../interface/mapconstructor.md               |   31 -
 .../interface/next-iterator.md                |   18 -
 .../interface/return-iterator.md              |   18 -
 .../spfx/es6-collections/interface/set-map.md |   18 -
 .../es6-collections/interface/set-weakmap.md  |   18 -
 .../spfx/es6-collections/interface/set.md     |   38 -
 .../interface/setconstructor.md               |   31 -
 .../interface/throw-iterator.md               |   18 -
 .../es6-collections/interface/values-map.md   |   18 -
 .../es6-collections/interface/values-set.md   |   18 -
 .../spfx/es6-collections/interface/weakmap.md |   29 -
 .../interface/weakmapconstructor.md           |   31 -
 .../spfx/es6-collections/interface/weakset.md |   28 -
 .../interface/weaksetconstructor.md           |   31 -
 ...sharepoint-framework-reference-overview.md |    3 -
 reference/spfx/sp-application-base-module.md  |   29 -
 .../class/applicationcustomizercontext.md     |   25 -
 .../class/baseapplicationcustomizer.md        |   31 -
 .../class/dispose-placeholder.md              |   22 -
 .../onrender-baseapplicationcustomizer.md     |   18 -
 .../sp-application-base/class/placeholder.md  |   32 -
 .../class/placeholdercollection.md            |   31 -
 .../class/tryattach-placeholdercollection.md  |   28 -
 .../interface/iplaceholderattachoptions.md    |   24 -
 reference/spfx/sp-component-base-module.md    |   27 -
 .../sp-component-base/class/basecomponent.md  |   35 -
 .../class/basecomponentcontext.md             |   36 -
 .../getbasemanifest-basecomponentcontext.md   |   22 -
 .../class/onprovideservices-basecomponent.md  |   22 -
 .../interface/iclientsidecomponentcontext.md  |   29 -
 reference/spfx/sp-core-library-module.md      |   46 -
 .../sp-core-library/class/compare-version.md  |   23 -
 .../class/consume-servicescope.md             |   22 -
 .../class/create-servicekey.md                |   24 -
 .../class/createandprovide-servicescope.md    |   24 -
 .../class/createcustom-servicekey.md          |   23 -
 .../createdefaultandprovide-servicescope.md   |   22 -
 .../spfx/sp-core-library/class/environment.md |   24 -
 .../spfx/sp-core-library/class/equals-guid.md |   18 -
 .../sp-core-library/class/equals-version.md   |   22 -
 .../spfx/sp-core-library/class/error-log.md   |   24 -
 .../class/finish-servicescope.md              |   18 -
 .../spfx/sp-core-library/class/format-text.md |   18 -
 .../class/generate-randomnumbergenerator.md   |   18 -
 .../class/getdate-timeprovider.md             |   18 -
 .../class/getparent-servicescope.md           |   18 -
 .../class/gettimestamp-timeprovider.md        |   18 -
 .../getvalue-urlqueryparametercollection.md   |   22 -
 .../getvalues-urlqueryparametercollection.md  |   22 -
 .../class/greaterthan-version.md              |   22 -
 reference/spfx/sp-core-library/class/guid.md  |   36 -
 .../spfx/sp-core-library/class/info-log.md    |   24 -
 .../class/isnonemptystring-validate.md        |   23 -
 .../class/isnotnullorundefined-validate.md    |   23 -
 .../sp-core-library/class/istrue-validate.md  |   23 -
 .../sp-core-library/class/isvalid-guid.md     |   22 -
 .../sp-core-library/class/isvalid-version.md  |   22 -
 .../sp-core-library/class/lessthan-version.md |   22 -
 reference/spfx/sp-core-library/class/log.md   |   28 -
 .../sp-core-library/class/newguid-guid.md     |   18 -
 .../spfx/sp-core-library/class/parse-guid.md  |   26 -
 .../sp-core-library/class/parse-version.md    |   22 -
 .../class/provide-servicescope.md             |   23 -
 .../class/randomnumbergenerator.md            |   43 -
 .../class/satisfies-version.md                |   22 -
 .../spfx/sp-core-library/class/servicekey.md  |   34 -
 .../sp-core-library/class/servicescope.md     |   33 -
 .../spfx/sp-core-library/class/session.md     |   25 -
 .../class/startnewchild-servicescope.md       |   18 -
 .../class/startnewroot-servicescope.md        |   18 -
 reference/spfx/sp-core-library/class/text.md  |   25 -
 .../sp-core-library/class/timeprovider.md     |   44 -
 .../sp-core-library/class/tostring-guid.md    |   18 -
 .../sp-core-library/class/tostring-version.md |   18 -
 .../sp-core-library/class/tryparse-guid.md    |   26 -
 .../sp-core-library/class/tryparse-version.md |   22 -
 .../class/urlqueryparametercollection.md      |   38 -
 .../spfx/sp-core-library/class/validate.md    |   27 -
 .../spfx/sp-core-library/class/verbose-log.md |   24 -
 .../spfx/sp-core-library/class/version.md     |   42 -
 .../spfx/sp-core-library/class/warn-log.md    |   24 -
 .../class/whenfinished-servicescope.md        |   22 -
 .../spfx/sp-core-library/enum/displaymode.md  |    7 -
 .../sp-core-library/enum/environmenttype.md   |    9 -
 .../generate-irandomnumbergenerator.md        |   18 -
 .../interface/getdate-itimeprovider.md        |   18 -
 .../interface/gettimestamp-itimeprovider.md   |   18 -
 .../interface/irandomnumbergenerator.md       |   25 -
 .../interface/iservicecollection.md           |   28 -
 .../interface/itimeprovider.md                |   26 -
 reference/spfx/sp-dialog-module.md            |   31 -
 .../spfx/sp-dialog/class/alert-dialog.md      |   26 -
 .../sp-dialog/class/alert-secondarydialog.md  |   22 -
 reference/spfx/sp-dialog/class/basedialog.md  |   56 -
 .../spfx/sp-dialog/class/close-basedialog.md  |   18 -
 reference/spfx/sp-dialog/class/dialog.md      |   26 -
 .../sp-dialog/class/getconfig-basedialog.md   |   18 -
 .../sp-dialog/class/onclose-basedialog.md     |   18 -
 .../spfx/sp-dialog/class/onopen-basedialog.md |   22 -
 .../spfx/sp-dialog/class/prompt-dialog.md     |   27 -
 .../sp-dialog/class/prompt-secondarydialog.md |   22 -
 .../spfx/sp-dialog/class/render-basedialog.md |   22 -
 .../spfx/sp-dialog/class/secondarydialog.md   |   31 -
 .../spfx/sp-dialog/class/show-basedialog.md   |   22 -
 .../sp-dialog/class/show-secondarydialog.md   |   22 -
 .../spfx/sp-dialog/interface/ialertoptions.md |   18 -
 .../interface/idialogconfiguration.md         |   24 -
 .../interface/idialogshowingoptions.md        |   24 -
 .../sp-dialog/interface/ipromptoptions.md     |   24 -
 reference/spfx/sp-extension-base-module.md    |   20 -
 .../sp-extension-base/class/baseextension.md  |   37 -
 .../class/extensioncontext.md                 |   30 -
 .../class/ondispose-baseextension.md          |   18 -
 .../class/oninit-baseextension.md             |   18 -
 reference/spfx/sp-http-module.md              |   45 -
 .../class/arraybuffer-httpclientresponse.md   |   18 -
 .../sp-http/class/beginbatch-sphttpclient.md  |   18 -
 .../sp-http/class/blob-httpclientresponse.md  |   18 -
 .../class/clone-graphclientresponse.md        |   18 -
 .../sp-http/class/clone-httpclientresponse.md |   18 -
 .../class/clone-sphttpclientresponse.md       |   18 -
 .../sp-http/class/fetch-graphhttpclient.md    |   26 -
 .../spfx/sp-http/class/fetch-httpclient.md    |   25 -
 .../spfx/sp-http/class/fetch-sphttpclient.md  |   25 -
 .../class/formdata-httpclientresponse.md      |   18 -
 .../spfx/sp-http/class/get-graphhttpclient.md |   25 -
 .../spfx/sp-http/class/get-httpclient.md      |   25 -
 .../spfx/sp-http/class/get-sphttpclient.md    |   25 -
 .../getweburlfromrequesturl-sphttpclient.md   |   22 -
 .../spfx/sp-http/class/graphclientresponse.md |   41 -
 .../spfx/sp-http/class/graphhttpclient.md     |   46 -
 .../class/graphhttpclientconfiguration.md     |   36 -
 reference/spfx/sp-http/class/httpclient.md    |   46 -
 .../sp-http/class/httpclientconfiguration.md  |   44 -
 .../spfx/sp-http/class/httpclientresponse.md  |   47 -
 ...initializeflags-httpclientconfiguration.md |   18 -
 ...zeflags-sphttpclientcommonconfiguration.md |   18 -
 ...itializeflags-sphttpclientconfiguration.md |   18 -
 .../sp-http/class/json-httpclientresponse.md  |   18 -
 reference/spfx/sp-http/class/odataversion.md  |   33 -
 .../overridewith-httpclientconfiguration.md   |   18 -
 ...idewith-sphttpclientcommonconfiguration.md |   18 -
 .../overridewith-sphttpclientconfiguration.md |   18 -
 .../sp-http/class/post-graphhttpclient.md     |   25 -
 .../spfx/sp-http/class/post-httpclient.md     |   25 -
 .../spfx/sp-http/class/post-sphttpclient.md   |   25 -
 reference/spfx/sp-http/class/sphttpclient.md  |   48 -
 .../class/sphttpclientcommonconfiguration.md  |   46 -
 .../class/sphttpclientconfiguration.md        |   47 -
 .../sp-http/class/sphttpclientresponse.md     |   41 -
 .../sp-http/class/text-httpclientresponse.md  |   18 -
 .../sp-http/class/tostring-odataversion.md    |   18 -
 .../class/tryparsefromheaders-odataversion.md |   18 -
 .../igraphhttpclientconfiguration.md          |   18 -
 .../igraphhttpclientconfigurations.md         |   24 -
 .../interface/igraphhttpclientoptions.md      |   18 -
 .../interface/ihttpclientconfiguration.md     |   18 -
 .../interface/ihttpclientconfigurations.md    |   24 -
 .../sp-http/interface/ihttpclientoptions.md   |   18 -
 .../isphttpclientcommonconfiguration.md       |   25 -
 .../interface/isphttpclientconfiguration.md   |   26 -
 .../interface/isphttpclientconfigurations.md  |   24 -
 .../sp-http/interface/isphttpclientoptions.md |   24 -
 .../spfx/sp-listview-extensibility-module.md  |   35 -
 .../class/basefieldcustomizer.md              |   32 -
 .../class/baselistviewcommandset.md           |   32 -
 .../class/cellformatter.md                    |   25 -
 .../class/columnaccessor.md                   |   29 -
 .../class/fieldcustomizercontext.md           |   27 -
 .../class/getvalue-rowaccessor.md             |   18 -
 .../class/getvaluebyname-rowaccessor.md       |   18 -
 .../class/listviewaccessor.md                 |   24 -
 .../class/listviewcommandsetcontext.md        |   26 -
 .../ondisposecell-basefieldcustomizer.md      |   18 -
 .../class/onexecute-baselistviewcommandset.md |   18 -
 ...onrefreshcommand-baselistviewcommandset.md |   18 -
 .../class/onrendercell-basefieldcustomizer.md |   18 -
 .../class/renderastext-cellformatter.md       |   18 -
 .../class/rowaccessor.md                      |   30 -
 .../ifieldcustomizercelleventparameters.md    |   27 -
 ...istviewcommandsetexecuteeventparameters.md |   25 -
 ...istviewcommandsetrefresheventparameters.md |   28 -
 reference/spfx/sp-loader-module.md            |   27 -
 .../class/initialize-spcomponentloader.md     |   18 -
 .../class/loadcomponent-spcomponentloader.md  |   22 -
 .../class/loadcss-spcomponentloader.md        |   22 -
 .../class/loadscript-spcomponentloader.md     |   23 -
 .../spfx/sp-loader/class/spcomponentloader.md |   28 -
 .../sp-loader/interface/iloadscriptoptions.md |   24 -
 .../sp-loader/interface/ispcomponentloader.md |   27 -
 .../loadcomponent-ispcomponentloader.md       |   22 -
 .../interface/loadcss-ispcomponentloader.md   |   22 -
 .../loadscript-ispcomponentloader.md          |   23 -
 reference/spfx/sp-odata-types-module.md       |   28 -
 .../interface/iodatabasepermission.md         |   25 -
 .../interface/iodatachangetoken.md            |   24 -
 .../interface/iodatacontextwebinformation.md  |   29 -
 .../sp-odata-types/interface/iodatalist.md    |   36 -
 .../interface/iodatalistitem.md               |   27 -
 .../interface/iodatanavigationnode.md         |   30 -
 .../iodatanavigationnodecollection.md         |   25 -
 .../sp-odata-types/interface/iodatauser.md    |   30 -
 .../interface/iodatausercustomaction.md       |   41 -
 .../sp-odata-types/interface/iodataweb.md     |   41 -
 reference/spfx/sp-page-context-module.md      |   27 -
 .../spfx/sp-page-context/class/cultureinfo.md |   26 -
 .../class/hasallpermissions-sppermission.md   |   22 -
 .../class/hasanypermissions-sppermission.md   |   22 -
 .../class/haspermission-sppermission.md       |   22 -
 .../spfx/sp-page-context/class/pagecontext.md |   44 -
 .../spfx/sp-page-context/class/spfield.md     |   30 -
 .../spfx/sp-page-context/class/splist.md      |   27 -
 .../spfx/sp-page-context/class/splistitem.md  |   24 -
 .../sp-page-context/class/sppermission.md     |   81 --
 .../spfx/sp-page-context/class/spsite.md      |   33 -
 .../spfx/sp-page-context/class/spuser.md      |   29 -
 reference/spfx/sp-page-context/class/spweb.md |   32 -
 reference/spfx/sp-webpart-base-module.md      |   75 --
 .../class/baseclientsidewebpart.md            |   71 -
 .../class/clearerror-baseclientsidewebpart.md |   18 -
 ...paneconfiguration-baseclientsidewebpart.md |   18 -
 ...nafterdeserialize-baseclientsidewebpart.md |   27 -
 ...anechangesapplied-baseclientsidewebpart.md |   18 -
 ...onbeforeserialize-baseclientsidewebpart.md |   18 -
 ...isplaymodechanged-baseclientsidewebpart.md |   22 -
 .../class/ondispose-baseclientsidewebpart.md  |   18 -
 .../class/oninit-baseclientsidewebpart.md     |   18 -
 ...igurationcomplete-baseclientsidewebpart.md |   18 -
 ...onfigurationstart-baseclientsidewebpart.md |   18 -
 ...ypanefieldchanged-baseclientsidewebpart.md |   24 -
 ...pertypanerendered-baseclientsidewebpart.md |   18 -
 .../class/render-baseclientsidewebpart.md     |   18 -
 .../rendercompleted-baseclientsidewebpart.md  |   18 -
 .../rendererror-baseclientsidewebpart.md      |   22 -
 .../enum/propertypanebuttontype.md            |   11 -
 .../enum/propertypanefieldtype.md             |   17 -
 .../function/propertypanebutton.md            |   23 -
 .../function/propertypanecheckbox.md          |   23 -
 .../function/propertypanechoicegroup.md       |   23 -
 .../function/propertypanecustomfield.md       |   23 -
 .../function/propertypanedropdown.md          |   23 -
 .../function/propertypanehorizontalrule.md    |   22 -
 .../function/propertypanelabel.md             |   23 -
 .../function/propertypanelink.md              |   23 -
 .../function/propertypaneslider.md            |   23 -
 .../function/propertypanetextfield.md         |   23 -
 .../function/propertypanetoggle.md            |   23 -
 .../__index-iwebpartpropertiesmetadata.md     |   18 -
 ...rerror-iclientsidewebpartstatusrenderer.md |   22 -
 ...icator-iclientsidewebpartstatusrenderer.md |   22 -
 ...icator-iclientsidewebpartstatusrenderer.md |   24 -
 .../iclientsidewebpartstatusrenderer.md       |   28 -
 .../interface/iplaceholderspinnerprops.md     |   25 -
 .../interface/ipropertypaneaccessor.md        |   28 -
 .../interface/ipropertypanebuttonprops.md     |   31 -
 .../interface/ipropertypanecheckboxprops.md   |   26 -
 .../ipropertypanechoicegroupoption.md         |   31 -
 ...ipropertypanechoicegroupoptioniconprops.md |   24 -
 .../ipropertypanechoicegroupprops.md          |   25 -
 .../interface/ipropertypaneconfiguration.md   |   27 -
 .../ipropertypanecustomfieldprops.md          |   30 -
 .../interface/ipropertypanedropdownoption.md  |   26 -
 .../interface/ipropertypanedropdownprops.md   |   27 -
 .../interface/ipropertypanefield.md           |   27 -
 .../interface/ipropertypanegroup.md           |   26 -
 .../interface/ipropertypanelabelprops.md      |   25 -
 .../interface/ipropertypanelinkprops.md       |   28 -
 .../interface/ipropertypanepage.md            |   26 -
 .../interface/ipropertypanepageheader.md      |   25 -
 .../interface/ipropertypanesliderprops.md     |   31 -
 .../interface/ipropertypanetextfieldprops.md  |   39 -
 .../interface/ipropertypanetoggleprops.md     |   29 -
 .../iserializedserverprocesseddata.md         |   27 -
 .../interface/iserializedwebpartdata.md       |   26 -
 ...spropertypaneopen-ipropertypaneaccessor.md |   18 -
 ...renderedbywebpart-ipropertypaneaccessor.md |   18 -
 .../interface/iwebpartcontext.md              |   37 -
 .../sp-webpart-base/interface/iwebpartdata.md |   30 -
 .../interface/iwebpartpropertiesmetadata.md   |   25 -
 .../interface/open-ipropertypaneaccessor.md   |   18 -
 .../refresh-ipropertypaneaccessor.md          |   18 -
 ...rerror-iclientsidewebpartstatusrenderer.md |   23 -
 reference/spfx/web-apis-module.md             |   34 -
 reference/spfx/web-apis/class/all-promise.md  |   18 -
 .../spfx/web-apis/class/append-headers.md     |   18 -
 .../spfx/web-apis/class/arraybuffer-body.md   |   18 -
 reference/spfx/web-apis/class/blob-body.md    |   18 -
 reference/spfx/web-apis/class/body.md         |   35 -
 .../spfx/web-apis/class/catch-promise.md      |   18 -
 .../spfx/web-apis/class/clone-response.md     |   18 -
 .../spfx/web-apis/class/delete-headers.md     |   18 -
 .../spfx/web-apis/class/error-response.md     |   18 -
 .../spfx/web-apis/class/foreach-headers.md    |   18 -
 .../spfx/web-apis/class/formdata-body.md      |   18 -
 reference/spfx/web-apis/class/get-headers.md  |   18 -
 .../spfx/web-apis/class/getall-headers.md     |   18 -
 reference/spfx/web-apis/class/has-headers.md  |   18 -
 reference/spfx/web-apis/class/headers.md      |   43 -
 reference/spfx/web-apis/class/json-body.md    |   18 -
 reference/spfx/web-apis/class/promise.md      |   42 -
 reference/spfx/web-apis/class/race-promise.md |   18 -
 .../spfx/web-apis/class/redirect-response.md  |   18 -
 .../spfx/web-apis/class/reject-promise.md     |   18 -
 reference/spfx/web-apis/class/request.md      |   44 -
 .../spfx/web-apis/class/resolve-promise.md    |   18 -
 reference/spfx/web-apis/class/response.md     |   50 -
 reference/spfx/web-apis/class/set-headers.md  |   18 -
 reference/spfx/web-apis/class/text-body.md    |   18 -
 reference/spfx/web-apis/class/then-promise.md |   18 -
 .../web-apis/interface/__index-headersmap.md  |   18 -
 .../spfx/web-apis/interface/fetch-window.md   |   18 -
 .../spfx/web-apis/interface/headersmap.md     |   25 -
 .../spfx/web-apis/interface/requestinit.md    |   30 -
 .../spfx/web-apis/interface/responseinit.md   |   26 -
 .../spfx/web-apis/interface/then-thenable.md  |   18 -
 reference/spfx/web-apis/interface/thenable.md |   25 -
 reference/spfx/web-apis/interface/window.md   |   25 -
 2235 files changed, 8558 insertions(+), 14509 deletions(-)
 create mode 100644 .openpublishing.build.ps1
 create mode 100644 .openpublishing.publish.config.json
 create mode 100644 LICENSE
 create mode 100644 LICENSE-CODE
 create mode 100644 ThirdPartyNotices
 create mode 100644 docs/breadcrumb/toc.yml
 create mode 100644 docs/docfx.json
 rename {images => docs/images}/03780b79-aca8-44d1-b0bf-d80833d08627.PNG (100%)
 rename {images => docs/images}/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif (100%)
 rename {images => docs/images}/101_page_model_overview.gif (100%)
 rename {images => docs/images}/102_master_page.gif (100%)
 rename {images => docs/images}/103_master_page_with_page_layout_outlined.gif (100%)
 rename {images => docs/images}/104_master_page_preview_message.gif (100%)
 rename {images => docs/images}/105_page_layout.gif (100%)
 rename {images => docs/images}/106_content_region_and_content_placeholder.gif (100%)
 rename {images => docs/images}/107_page_layout_with_page_fields.gif (100%)
 rename {images => docs/images}/108_master_page_with_page_layout.gif (100%)
 rename {images => docs/images}/109_one_master_many_layouts.gif (100%)
 rename {images => docs/images}/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG (100%)
 rename {images => docs/images}/110_page_with_authored_content.gif (100%)
 rename {images => docs/images}/111_rendered_page.gif (100%)
 rename {images => docs/images}/112_master_plus_layout_plus_page.gif (100%)
 rename {images => docs/images}/113_114_master_and_layout_and_page_and_web_part_closeup.gif (100%)
 rename {images => docs/images}/115_content_search_web_part_tool_pane.gif (100%)
 rename {images => docs/images}/116_117_control_templates_1_and_2.gif (100%)
 rename {images => docs/images}/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif (100%)
 rename {images => docs/images}/118_119_control_template_outlined_on_web_part_and_page.gif (100%)
 rename {images => docs/images}/120_121_item_templates_outlined_on_web_part_and_page.gif (100%)
 rename {images => docs/images}/122_123_two_channels_two_master_pages.gif (100%)
 rename {images => docs/images}/124_one_layout_many_masters.gif (100%)
 rename {images => docs/images}/125_126_page_layout_with_channel_panels.gif (100%)
 rename {images => docs/images}/127_128_item_display_templates_with_channel_panel.gif (100%)
 rename {images => docs/images}/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG (100%)
 rename {images => docs/images}/14d5a820-ab44-4d12-98de-6672884bf344.PNG (100%)
 rename {images => docs/images}/159f676e-421e-4190-94a6-cf311f7db2ca.gif (100%)
 rename {images => docs/images}/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF (100%)
 rename {images => docs/images}/19126dce-b896-4623-8686-92f2fa807283.gif (100%)
 rename {images => docs/images}/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif (100%)
 rename {images => docs/images}/1a814b3b-76a3-4a5c-8eef-550893728499.jpg (100%)
 rename {images => docs/images}/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif (100%)
 rename {images => docs/images}/1b21d968-bd58-4f30-a019-84df6181b81a.PNG (100%)
 rename {images => docs/images}/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg (100%)
 rename {images => docs/images}/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png (100%)
 rename {images => docs/images}/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif (100%)
 rename {images => docs/images}/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG (100%)
 rename {images => docs/images}/25ba5677-f530-432a-9980-64b5eb33119c.png (100%)
 rename {images => docs/images}/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG (100%)
 rename {images => docs/images}/2d011e17-953f-42b1-97d3-2525372296c1.gif (100%)
 rename {images => docs/images}/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG (100%)
 rename {images => docs/images}/2df9591d-a837-4130-98e4-5863d0c717e8.gif (100%)
 rename {images => docs/images}/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif (100%)
 rename {images => docs/images}/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG (100%)
 rename {images => docs/images}/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG (100%)
 rename {images => docs/images}/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg (100%)
 rename {images => docs/images}/3b33c622-c52a-45fd-8ea1-d7f307539753.png (100%)
 rename {images => docs/images}/3b9184db-99a4-416e-ba1e-7f8653484cee.png (100%)
 rename {images => docs/images}/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif (100%)
 rename {images => docs/images}/3fbdcfae-6af9-452b-9a07-48575de7e86a.png (100%)
 rename {images => docs/images}/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG (100%)
 rename {images => docs/images}/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg (100%)
 rename {images => docs/images}/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG (100%)
 rename {images => docs/images}/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg (100%)
 rename {images => docs/images}/44928b39-5683-4bce-8ddf-31d886243b87.gif (100%)
 rename {images => docs/images}/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png (100%)
 rename {images => docs/images}/494cf01e-3e17-4092-b239-9312ac4ab258.PNG (100%)
 rename {images => docs/images}/49a93d59-6755-4afc-a703-ca8469b6fa74.gif (100%)
 rename {images => docs/images}/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG (100%)
 rename {images => docs/images}/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif (100%)
 rename {images => docs/images}/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG (100%)
 rename {images => docs/images}/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG (100%)
 rename {images => docs/images}/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG (100%)
 rename {images => docs/images}/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif (100%)
 rename {images => docs/images}/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png (100%)
 rename {images => docs/images}/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg (100%)
 rename {images => docs/images}/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG (100%)
 rename {images => docs/images}/60f3302e-ca9c-45be-b785-0c9f636181da.PNG (100%)
 rename {images => docs/images}/65926095-d833-4eb2-b899-9efe40e2d540.GIF (100%)
 rename {images => docs/images}/6a0f0a56-3184-490a-af19-b51b7545671d.PNG (100%)
 rename {images => docs/images}/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG (100%)
 rename {images => docs/images}/6c119cae-adf8-42ff-9890-f3aa1e11719d.png (100%)
 rename {images => docs/images}/6d3bbe0a-399e-4747-9e1a-01d42954ce32.png (100%)
 rename {images => docs/images}/70d5a602-b349-4791-bf05-d61635d0fc91.gif (100%)
 rename {images => docs/images}/7298a25b-ed54-4953-a781-26c3f633866a.jpg (100%)
 rename {images => docs/images}/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG (100%)
 rename {images => docs/images}/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg (100%)
 rename {images => docs/images}/7639578e-3d3f-40cf-8f53-355bb19c539b.png (100%)
 rename {images => docs/images}/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif (100%)
 rename {images => docs/images}/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif (100%)
 rename {images => docs/images}/7849d413-381f-4558-9e50-b3cc9990d3e3.png (100%)
 rename {images => docs/images}/787df903-833d-4a12-a692-716ceaf54c10.gif (100%)
 rename {images => docs/images}/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG (100%)
 rename {images => docs/images}/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG (100%)
 rename {images => docs/images}/7fd942de-a324-4f70-a750-f5304c993832.PNG (100%)
 rename {images => docs/images}/833fcdcc-1755-438b-9ada-dce9646564c0.gif (100%)
 rename {images => docs/images}/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG (100%)
 rename {images => docs/images}/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG (100%)
 rename {images => docs/images}/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif (100%)
 rename {images => docs/images}/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg (100%)
 rename {images => docs/images}/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG (100%)
 rename {images => docs/images}/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif (100%)
 rename {images => docs/images}/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG (100%)
 rename {images => docs/images}/903d3109-d567-4156-a44f-29793c42ae45.gif (100%)
 rename {images => docs/images}/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg (100%)
 rename {images => docs/images}/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif (100%)
 rename {images => docs/images}/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png (100%)
 rename {images => docs/images}/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif (100%)
 rename {images => docs/images}/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif (100%)
 rename {images => docs/images}/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif (100%)
 rename {images => docs/images}/978d8147-cabd-422e-9d02-d8022a114bd6.jpg (100%)
 rename {images => docs/images}/99209248-8927-4fc2-abfc-53d530376516.PNG (100%)
 rename {images => docs/images}/99376713-6a54-4d88-9b05-068578169506.gif (100%)
 rename {images => docs/images}/997021de-c60c-46b0-961f-7e1e63c0f619.gif (100%)
 rename {images => docs/images}/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif (100%)
 rename {images => docs/images}/9a38d876-2189-418c-9314-ae493a4cab61.PNG (100%)
 rename {images => docs/images}/9c836899-8f21-4e0f-9260-69b8171a303c.PNG (100%)
 rename {images => docs/images}/9dc5cefe-083a-4807-bee6-473001f23db9.png (100%)
 rename {images => docs/images}/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif (100%)
 rename {images => docs/images}/ALMBuildDeployProcess.png (100%)
 rename {images => docs/images}/ALMChangeManagement.png (100%)
 rename {images => docs/images}/ALMCodePromotion.png (100%)
 rename {images => docs/images}/ALMDeveloperTesting.png (100%)
 rename {images => docs/images}/ALMIntegrationTesting.png (100%)
 rename {images => docs/images}/ALMIntegrationandUAT.png (100%)
 rename {images => docs/images}/ALMTestingTypes.png (100%)
 rename {images => docs/images}/ALMUATTesting.png (100%)
 rename {images => docs/images}/ALMWithTFS.png (100%)
 rename {images => docs/images}/AppDevelopmentClientBuildComponents.png (100%)
 rename {images => docs/images}/AppDevelopmentEnvironment.png (100%)
 rename {images => docs/images}/AppDevelopmentVirtualEnvironment.png (100%)
 rename {images => docs/images}/AppForSharePointVSTemplate.PNG (100%)
 rename {images => docs/images}/AppParts_ConceptualArchitecture.png (100%)
 rename {images => docs/images}/AppParts_IFrameError.png (100%)
 rename {images => docs/images}/AppUXGuidelines_AppTemplate.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ChromeControl.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ECBcustomaction.png (100%)
 rename {images => docs/images}/AppUXGuidelines_QuickLaunchHeading.png (100%)
 rename {images => docs/images}/AppUXGuidelines_QuickLaunchLink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_QuickLaunchSelected.png (100%)
 rename {images => docs/images}/AppUXGuidelines_TopNav.png (100%)
 rename {images => docs/images}/AppUXGuidelines_TopNavSelected.png (100%)
 rename {images => docs/images}/AppUXGuidelines_bgdisabled.png (100%)
 rename {images => docs/images}/AppUXGuidelines_body.png (100%)
 rename {images => docs/images}/AppUXGuidelines_dragfiles.png (100%)
 rename {images => docs/images}/AppUXGuidelines_h1.png (100%)
 rename {images => docs/images}/AppUXGuidelines_h2.png (100%)
 rename {images => docs/images}/AppUXGuidelines_h3.png (100%)
 rename {images => docs/images}/AppUXGuidelines_h4.png (100%)
 rename {images => docs/images}/AppUXGuidelines_hr.png (100%)
 rename {images => docs/images}/AppUXGuidelines_hyperlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_md-bghoverable-normal.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-accentlines.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-accenttext.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-attractmode.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-bgfooter.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-bgheader.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-bghoverable-onhover.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-bgoverlay.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-bgselected.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-calloutlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-commandlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-core-pagetitle.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-disabled.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-disabledlines.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-dlg-heading.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-emphasis.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-emphasisborder.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-emptymode.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-error.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-helper.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-herocommandlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-lines.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-listlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-metadata.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-popupborder.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-secondarycommandlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-sidenav-selected.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-sidenav.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-soften.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-stronglines.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-subtleemphasis.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-subtleemphasiscommand.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-subtlelines.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-textlarge.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-textsmall.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-textxlarge.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-topbar.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-uppercase.png (100%)
 rename {images => docs/images}/AppUXGuidelines_ms-webpart-titletext.png (100%)
 rename {images => docs/images}/AppUXGuidelines_mspivotlink.png (100%)
 rename {images => docs/images}/AppUXGuidelines_part.png (100%)
 rename {images => docs/images}/AppUX_devhosted.png (100%)
 rename {images => docs/images}/AppUX_hostweb.png (100%)
 rename {images => docs/images}/AppUX_landscape.png (100%)
 rename {images => docs/images}/AppVSTemplateSolutionExplorer.jpg (100%)
 rename {images => docs/images}/Apps_NAPA_Run_Button.png (100%)
 rename {images => docs/images}/Apps_Napa_OpenInVS.png (100%)
 rename {images => docs/images}/BCSin2013FeatureSet.jpg (100%)
 rename {images => docs/images}/BasicAppPart_gallery.jpg (100%)
 rename {images => docs/images}/BasicAppPart_result.png (100%)
 rename {images => docs/images}/BrowserWarnings4SelfSignedCerts.png (100%)
 rename {images => docs/images}/Buildsearch-drivenmobileappspages.gif (100%)
 rename {images => docs/images}/Buildsearch-drivenmobileappspages_item_details.gif (100%)
 rename {images => docs/images}/CBAAddButton.PNG (100%)
 rename {images => docs/images}/CBAAddDialog.PNG (100%)
 rename {images => docs/images}/CBAAddDoc.PNG (100%)
 rename {images => docs/images}/CBAAddTab.PNG (100%)
 rename {images => docs/images}/CBADocLibrary.PNG (100%)
 rename {images => docs/images}/CBADocLibrary2.PNG (100%)
 rename {images => docs/images}/CBARelationship.PNG (100%)
 rename {images => docs/images}/CBARelationship2.PNG (100%)
 rename {images => docs/images}/CBAScreenSet.PNG (100%)
 rename {images => docs/images}/CBA_IM1.PNG (100%)
 rename {images => docs/images}/CBA_IM4a.PNG (100%)
 rename {images => docs/images}/CBA_IM_10.PNG (100%)
 rename {images => docs/images}/CBA_IM_10a.PNG (100%)
 rename {images => docs/images}/CBA_IM_11.PNG (100%)
 rename {images => docs/images}/CBA_IM_11a.PNG (100%)
 rename {images => docs/images}/CBA_IM_11b.PNG (100%)
 rename {images => docs/images}/CBA_IM_11c.PNG (100%)
 rename {images => docs/images}/CBA_IM_12.PNG (100%)
 rename {images => docs/images}/CBA_IM_13.PNG (100%)
 rename {images => docs/images}/CBA_IM_14.PNG (100%)
 rename {images => docs/images}/CBA_IM_15.PNG (100%)
 rename {images => docs/images}/CBA_IM_16.PNG (100%)
 rename {images => docs/images}/CBA_IM_17.PNG (100%)
 rename {images => docs/images}/CBA_IM_18.PNG (100%)
 rename {images => docs/images}/CBA_IM_19.PNG (100%)
 rename {images => docs/images}/CBA_IM_2.PNG (100%)
 rename {images => docs/images}/CBA_IM_20.PNG (100%)
 rename {images => docs/images}/CBA_IM_20a.PNG (100%)
 rename {images => docs/images}/CBA_IM_21.PNG (100%)
 rename {images => docs/images}/CBA_IM_22.PNG (100%)
 rename {images => docs/images}/CBA_IM_23.PNG (100%)
 rename {images => docs/images}/CBA_IM_24.PNG (100%)
 rename {images => docs/images}/CBA_IM_25.PNG (100%)
 rename {images => docs/images}/CBA_IM_26.PNG (100%)
 rename {images => docs/images}/CBA_IM_27.PNG (100%)
 rename {images => docs/images}/CBA_IM_28.PNG (100%)
 rename {images => docs/images}/CBA_IM_28a.PNG (100%)
 rename {images => docs/images}/CBA_IM_29.PNG (100%)
 rename {images => docs/images}/CBA_IM_29a.PNG (100%)
 rename {images => docs/images}/CBA_IM_2a.PNG (100%)
 rename {images => docs/images}/CBA_IM_3.PNG (100%)
 rename {images => docs/images}/CBA_IM_30.PNG (100%)
 rename {images => docs/images}/CBA_IM_4.PNG (100%)
 rename {images => docs/images}/CBA_IM_5.PNG (100%)
 rename {images => docs/images}/CBA_IM_5a.PNG (100%)
 rename {images => docs/images}/CBA_IM_6.PNG (100%)
 rename {images => docs/images}/CBA_IM_7.PNG (100%)
 rename {images => docs/images}/CBA_IM_8.PNG (100%)
 rename {images => docs/images}/CBA_IM_8a.PNG (100%)
 rename {images => docs/images}/CBA_IM_8b.PNG (100%)
 rename {images => docs/images}/CBA_IM_8c.PNG (100%)
 rename {images => docs/images}/CBA_IM_8d.PNG (100%)
 rename {images => docs/images}/CBA_IM_9.PNG (100%)
 rename {images => docs/images}/CBA_IM_9a.PNG (100%)
 rename {images => docs/images}/CBAaction.PNG (100%)
 rename {images => docs/images}/CBAadd.PNG (100%)
 rename {images => docs/images}/CBAentity.PNG (100%)
 rename {images => docs/images}/CBAnewsfeed.PNG (100%)
 rename {images => docs/images}/CBAproperty.PNG (100%)
 rename {images => docs/images}/CBAscreen.PNG (100%)
 rename {images => docs/images}/CBAsocial.PNG (100%)
 rename {images => docs/images}/CBAtemplate.PNG (100%)
 rename {images => docs/images}/CFW.gif (100%)
 rename {images => docs/images}/CSRFieldType_addcolumn.png (100%)
 rename {images => docs/images}/CSRFieldType_result.png (100%)
 rename {images => docs/images}/CSRListView_result.png (100%)
 rename {images => docs/images}/Caution.gif (100%)
 rename {images => docs/images}/ChromControl_stylesheet.png (100%)
 rename {images => docs/images}/ChromeControl_manifest.PNG (100%)
 rename {images => docs/images}/ChromeControl_result.png (100%)
 rename {images => docs/images}/CloudBusinessApptemplate.PNG (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig10.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig12.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig18.png (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig20.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig21.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig22.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig3.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig4.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig5.jpg (100%)
 rename {images => docs/images}/ConvertAuto2ProviderFig6.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig11.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig13.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig14.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig17.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig7.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig8.jpg (100%)
 rename {images => docs/images}/ConvertAuto2Providerfig9.jpg (100%)
 rename {images => docs/images}/CreatSharePoint2013WorkflowsFig4.png (100%)
 rename {images => docs/images}/CreateSharePoint2013Workflows.png (100%)
 rename {images => docs/images}/CreateSharePoint2013WorkflowsFig2.png (100%)
 rename {images => docs/images}/CreateSharePoint2013WorkflowsFig5.png (100%)
 rename {images => docs/images}/CreateSharePoint2013WorkflowsFig7.png (100%)
 rename {images => docs/images}/CreateSharePoint2013WorkflowsFig8.png (100%)
 rename {images => docs/images}/CrossDomainReadItemsResult.png (100%)
 rename {images => docs/images}/Crosszone_loaderror.png (100%)
 rename {images => docs/images}/Crosszone_loadsuccess.png (100%)
 rename {images => docs/images}/CustomActions_target.png (100%)
 rename {images => docs/images}/CustomProxy_result.jpg (100%)
 rename {images => docs/images}/DataAccess_SharePointData.png (100%)
 rename {images => docs/images}/DesktopListView_basic.png (100%)
 rename {images => docs/images}/ExtEvtsAndAlerts_Figure2.jpg (100%)
 rename {images => docs/images}/ExtEvtsAndAlerts_Figure3.jpg (100%)
 rename {images => docs/images}/ExtEvtsAndAlrts_Figure1.jpg (100%)
 rename {images => docs/images}/ExternalEventsAndAlerts_UnsubscribeFlow.jpg (100%)
 rename {images => docs/images}/GitHub-Mark-64px.png (100%)
 rename {images => docs/images}/HostWebAndAppWeb.png (100%)
 rename {images => docs/images}/ImgRendition_crop.PNG (100%)
 rename {images => docs/images}/ImgRendition_orig.PNG (100%)
 rename {images => docs/images}/LastChild.gif (100%)
 rename {images => docs/images}/LocSPApp_AppwebList.png (100%)
 rename {images => docs/images}/LocSPApp_AppwebPage.png (100%)
 rename {images => docs/images}/LocSPApp_TestCreatesite.png (100%)
 rename {images => docs/images}/MDS_GeneralFlow.png (100%)
 rename {images => docs/images}/MDS_SeattleMaster.png (100%)
 rename {images => docs/images}/MDS_UpdateSections.png (100%)
 rename {images => docs/images}/NuGet.PNG (100%)
 rename {images => docs/images}/Octocat.png (100%)
 rename {images => docs/images}/Office365AppDevelpment.png (100%)
 rename {images => docs/images}/OfficeWebWidgetsOverview_demo.png (100%)
 rename {images => docs/images}/OnPremDevSites.png (100%)
 rename {images => docs/images}/OptimizePage_Fig01_MDSArchitecture.png (100%)
 rename {images => docs/images}/OptimizePage_Fig02_PageStructure.png (100%)
 rename {images => docs/images}/OptimizePage_Fig03_SingleImage.png (100%)
 rename {images => docs/images}/OptimizePage_Fig04_ImageTable.png (100%)
 rename {images => docs/images}/OptimizePage_Fig05_DevDashboard.png (100%)
 rename {images => docs/images}/PeoplePicker_HTMLHierarchy.png (100%)
 rename {images => docs/images}/PeoplePicker_basic.png (100%)
 rename {images => docs/images}/ProviderHostedAppBuildComponents.png (100%)
 rename {images => docs/images}/REST_OverallSyntax.png (100%)
 rename {images => docs/images}/REST_RESTStructure.png (100%)
 rename {images => docs/images}/REST_parameterAliasSyntax.png (100%)
 rename {images => docs/images}/REST_parameterDictionarySyntax.png (100%)
 rename {images => docs/images}/REST_parameterQuerySyntax.png (100%)
 rename {images => docs/images}/REST_parameterSyntax.png (100%)
 rename {images => docs/images}/REST_queryOptionSyntax.png (100%)
 create mode 100644 docs/images/RegrantPermissionsToAnApp.png
 rename {images => docs/images}/S15_CalloutControlExample.png (100%)
 rename {images => docs/images}/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png (100%)
 rename {images => docs/images}/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png (100%)
 rename {images => docs/images}/SP15Con_CF_BCS_Overview.jpg (100%)
 rename {images => docs/images}/SP15Con_CF_ConnFrwkArch.jpg (100%)
 rename {images => docs/images}/SP15Con_CF_IndexingConnectors.jpg (100%)
 rename {images => docs/images}/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png (100%)
 rename {images => docs/images}/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png (100%)
 rename {images => docs/images}/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png (100%)
 rename {images => docs/images}/SP15Con_HowToAddGeolocationColumn_fig.png (100%)
 rename {images => docs/images}/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png (100%)
 rename {images => docs/images}/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png (100%)
 rename {images => docs/images}/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png (100%)
 rename {images => docs/images}/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png (100%)
 rename {images => docs/images}/SP15Con_Remote_Event_Receivers_FAQ_fig1.png (100%)
 rename {images => docs/images}/SP15Con_Remote_Event_Receivers_FAQ_fig3.png (100%)
 rename {images => docs/images}/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG (100%)
 rename {images => docs/images}/SP15Con_SharePointClientAuthenticationFig1.png (100%)
 rename {images => docs/images}/SP15Con_VisualStudioMobileSPListTemplate.png (100%)
 rename {images => docs/images}/SP15HelloWorldSPApp_Fig01.png (100%)
 rename {images => docs/images}/SP15HighTrustLaunchNew.gif (100%)
 rename {images => docs/images}/SP15_Buildsearch-drivenmobileappspages_home.gif (100%)
 rename {images => docs/images}/SP15_CMISCapabilities.jpg (100%)
 rename {images => docs/images}/SP15_CMISObjectTypeExamples.png (100%)
 rename {images => docs/images}/SP15_CalloutLeftRight.png (100%)
 rename {images => docs/images}/SP15_CalloutMenu.png (100%)
 rename {images => docs/images}/SP15_CalloutTopBottom.png (100%)
 rename {images => docs/images}/SP15_Content_Enrichment.gif (100%)
 rename {images => docs/images}/SP15_DeveloperSiteHome_border.png (100%)
 rename {images => docs/images}/SP15_FeatureReceiverVS.png (100%)
 rename {images => docs/images}/SP15_Office365AdminInset_border.png (100%)
 rename {images => docs/images}/SP15_OnPremACSArchitecture.png (100%)
 rename {images => docs/images}/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG (100%)
 rename {images => docs/images}/SP15_RegisterApp.png (100%)
 rename {images => docs/images}/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg (100%)
 rename {images => docs/images}/SP15_appChooseSiteTemplate.gif (100%)
 rename {images => docs/images}/SP15_app_ChooseSiteTemplates.gif (100%)
 rename {images => docs/images}/SP15_app_ServerType.gif (100%)
 rename {images => docs/images}/SP15_basicself-hostedapp.gif (100%)
 rename {images => docs/images}/SP15_hosting_Provider.gif (100%)
 rename {images => docs/images}/SP15_hosting_SPhosted.gif (100%)
 rename {images => docs/images}/SP15_search_app_permission_Napa.gif (100%)
 rename {images => docs/images}/SP15_search_apps_permission_Visual_Studio.PNG (100%)
 rename {images => docs/images}/SPAdminCenter_newSiteCollection.png (100%)
 rename {images => docs/images}/SPAdminCenter_newSiteCollection_provisioning.png (100%)
 rename {images => docs/images}/SPCon15_BDCMobileAppDemo.png (100%)
 rename {images => docs/images}/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_ChooseViewType__fig2.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_ECB_Menu__fig1.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_MyMapView__fig4.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png (100%)
 rename {images => docs/images}/SPCon15_CreateMapView_SelectFieldsForView__fig3.png (100%)
 rename {images => docs/images}/SPCon15_Setting_BDCObjectPermission_DialogueBox.png (100%)
 rename {images => docs/images}/SPD-Dictionary-1a.png (100%)
 rename {images => docs/images}/SPD15-BuildADictionaryDialog.png (100%)
 rename {images => docs/images}/SPD15-CoordinationActions.png (100%)
 rename {images => docs/images}/SPD15-CoordinationActions2.png (100%)
 rename {images => docs/images}/SPD15-CoordinationActions3.png (100%)
 rename {images => docs/images}/SPD15-CorrelationActions4.png (100%)
 rename {images => docs/images}/SPD15-CountItemsInDictionary.png (100%)
 rename {images => docs/images}/SPD15-Dictionary-1b.png (100%)
 rename {images => docs/images}/SPD15-Dictionary-2.png (100%)
 rename {images => docs/images}/SPD15-EventingActions1.png (100%)
 rename {images => docs/images}/SPD15-EventingActions2.png (100%)
 rename {images => docs/images}/SPD15-EventingActions3.jpg (100%)
 rename {images => docs/images}/SPD15-EventingActions4.png (100%)
 rename {images => docs/images}/SPD15-EventingActions5.png (100%)
 rename {images => docs/images}/SPD15-GetAnItemFromDictionary.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow1.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow2.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow3.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow4.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow5.png (100%)
 rename {images => docs/images}/SPD15-PackagingWorkflow6.png (100%)
 rename {images => docs/images}/SPD15-TaskActions2.png (100%)
 rename {images => docs/images}/SPD15-TaskActions3.png (100%)
 rename {images => docs/images}/SPD15-TaskActions4.png (100%)
 rename {images => docs/images}/SPD15-TaskActions5.png (100%)
 rename {images => docs/images}/SPD15-VisualDesigner1.png (100%)
 rename {images => docs/images}/SPD15-VisualDesigner2.png (100%)
 rename {images => docs/images}/SPD15-VisualDesigner3.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions1.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions10.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions11.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions12.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions13.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions14.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions15.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions2.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions3.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions4.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions5.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions6.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions7.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions8.png (100%)
 rename {images => docs/images}/SPD15-WFAppPermissions9.png (100%)
 rename {images => docs/images}/SPD15-install-connect-1.png (100%)
 rename {images => docs/images}/SPD15-install-connect-2.png (100%)
 rename {images => docs/images}/SPD15-install-connect-3.png (100%)
 rename {images => docs/images}/SPD15-install-connect-4.png (100%)
 rename {images => docs/images}/SPD15-wf-step1.png (100%)
 rename {images => docs/images}/SPF15Con_REST_OverallSyntax.png (100%)
 rename {images => docs/images}/SPF15Con_REST_RESTStructure.png (100%)
 rename {images => docs/images}/SPF15Con_REST_parameterAliasSyntax.png (100%)
 rename {images => docs/images}/SPF15Con_REST_parameterDictionarySyntax.png (100%)
 rename {images => docs/images}/SPF15Con_REST_parameterQuerySyntax.png (100%)
 rename {images => docs/images}/SPF15Con_REST_parameterSyntax.png (100%)
 rename {images => docs/images}/SPF15Con_REST_queryOptionSyntax.png (100%)
 rename {images => docs/images}/SPS14_PerfPoint_ArchOverview.gif (100%)
 rename {images => docs/images}/SPS15CON_WAS_Architecture.png (100%)
 rename {images => docs/images}/SPS15CON_xls_JsUdfinWebApp.jpg (100%)
 rename {images => docs/images}/SP_VS_Properties_Window_AppEvents.PNG (100%)
 rename {images => docs/images}/SP_VS_Properties_Window_RemoteEvents.PNG (100%)
 rename {images => docs/images}/SearchComponentInteraction.jpg (100%)
 rename {images => docs/images}/SharePointAPIsetsandselectedSharePointextensions.png (100%)
 rename {images => docs/images}/SharePointServer14Con_XLSvcs_RESTModel.gif (100%)
 rename {images => docs/images}/SharePointSolutionVSTemplate.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png (100%)
 rename {images => docs/images}/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png (100%)
 rename {images => docs/images}/SharePointtab.PNG (100%)
 rename {images => docs/images}/SiteURL.PNG (100%)
 rename {images => docs/images}/Sp15_app_.png (100%)
 rename {images => docs/images}/StylesheetControl_result.png (100%)
 rename {images => docs/images}/StylesheetControl_result2.png (100%)
 rename {images => docs/images}/TFSBuildTargets.png (100%)
 rename {images => docs/images}/Top-levelprojectnode.PNG (100%)
 rename {images => docs/images}/UpdateAppOpenFeatureXML.png (100%)
 rename {images => docs/images}/UpdatingApp_AppTileUpdateNotice.png (100%)
 rename {images => docs/images}/UpdatingApp_ImmediateUpgradeProcess.png (100%)
 rename {images => docs/images}/WebProxy_result.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig1.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig10.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig11.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig12.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig13.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig14.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig15.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig16.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig17.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig18.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig2.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig3.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig4.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig5.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig6.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig7.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig8.png (100%)
 rename {images => docs/images}/WorkingWithTasksSharePointWorkflowsFig9.png (100%)
 rename {images => docs/images}/XRANKFormula.gif (100%)
 rename {images => docs/images}/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG (100%)
 rename {images => docs/images}/a3371859-e42f-49ea-8f17-48d8a248b075.PNG (100%)
 rename {images => docs/images}/a35fd1af-7194-4c99-b298-bac97025b981.PNG (100%)
 rename {images => docs/images}/a61afe25-9597-403f-b3fa-d3f630155021.png (100%)
 rename {images => docs/images}/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png (100%)
 rename {images => docs/images}/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg (100%)
 rename {images => docs/images}/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG (100%)
 rename {images => docs/images}/adm.gif (100%)
 rename {images => docs/images}/adm_arch.gif (100%)
 rename {images => docs/images}/adm_dev.gif (100%)
 rename {images => docs/images}/adm_dev_arch.gif (100%)
 rename {images => docs/images}/aebc97ae-c886-4d50-94ff-238049a259c7.gif (100%)
 rename {images => docs/images}/alert_caution.gif (100%)
 rename {images => docs/images}/alert_note.gif (100%)
 rename {images => docs/images}/alert_security.gif (100%)
 rename {images => docs/images}/api-aad-add-function-parameters.png (100%)
 rename {images => docs/images}/api-aad-add-function.png (100%)
 rename {images => docs/images}/api-aad-azure-app-service-authentication.png (100%)
 rename {images => docs/images}/api-aad-create-new-aad-app.png (100%)
 rename {images => docs/images}/api-aad-create-new-function-app.png (100%)
 rename {images => docs/images}/api-aad-custom-function.png (100%)
 rename {images => docs/images}/api-aad-function-authentication-aad-app.png (100%)
 rename {images => docs/images}/api-aad-function-authentication-aad.png (100%)
 rename {images => docs/images}/api-aad-function-authentication-login-aad.png (100%)
 rename {images => docs/images}/api-aad-function-authentication-on.png (100%)
 rename {images => docs/images}/api-aad-function-authentication-save.png (100%)
 rename {images => docs/images}/api-aad-function-authentication.png (100%)
 rename {images => docs/images}/api-aad-function-code.png (100%)
 rename {images => docs/images}/api-aad-function-cors-delete.png (100%)
 rename {images => docs/images}/api-aad-function-cors-save.png (100%)
 rename {images => docs/images}/api-aad-function-cors.png (100%)
 rename {images => docs/images}/api-aad-platform-features.png (100%)
 rename {images => docs/images}/api-aad-sign-in.png (100%)
 rename {images => docs/images}/api-aad-visual-studio-authentication-wizard.png (100%)
 rename {images => docs/images}/api-aad-webapi-anonymous-unauthorized.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication-aad-login.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication-aad-ok.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication-aad.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication-on.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication-save.png (100%)
 rename {images => docs/images}/api-aad-webapi-authentication.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-aad.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-app-details.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-app-registrations.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-new-app-registration-create.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-new-app-registration.png (100%)
 rename {images => docs/images}/api-aad-webapi-azure-sign-in.png (100%)
 rename {images => docs/images}/api-aad-webapi-response-anonymous.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-cors-nuget.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-create-app-service.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-host-app-service.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-manage-nuget.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-no-authentication.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-publish-settings.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-publish.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-web-application.png (100%)
 rename {images => docs/images}/api-aad-webapi-vs-webapi.png (100%)
 rename {images => docs/images}/app-installed-your-site.png (100%)
 rename {images => docs/images}/arch.gif (100%)
 rename {images => docs/images}/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg (100%)
 rename {images => docs/images}/b315cb68-ff6a-4770-a1dc-738696ab71d2.png (100%)
 rename {images => docs/images}/b654af45-663e-425c-b7c7-b8b5524cb316.PNG (100%)
 rename {images => docs/images}/b86ecdb8-88a7-4407-af86-07d2442235dc.gif (100%)
 rename {images => docs/images}/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG (100%)
 rename {images => docs/images}/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG (100%)
 rename {images => docs/images}/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif (100%)
 rename {images => docs/images}/big_adm.gif (100%)
 rename {images => docs/images}/big_arch.gif (100%)
 rename {images => docs/images}/big_dev.gif (100%)
 rename {images => docs/images}/big_kw.gif (100%)
 rename {images => docs/images}/box.gif (100%)
 rename {images => docs/images}/bullet.gif (100%)
 rename {images => docs/images}/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif (100%)
 rename {images => docs/images}/c1230e3b-d149-413c-aa66-d258250a4512.PNG (100%)
 rename {images => docs/images}/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG (100%)
 rename {images => docs/images}/cd8eb456-d883-491a-b171-38c1b9f64018.PNG (100%)
 rename {images => docs/images}/cdn-add-webpart-to-site.png (100%)
 rename {images => docs/images}/cdn-create-webpart-yo.png (100%)
 rename {images => docs/images}/cdn-helloworld-folder.png (100%)
 rename {images => docs/images}/cdn-public-origins.png (100%)
 rename {images => docs/images}/cdn-upload-solution-to-app-catalog.png (100%)
 rename {images => docs/images}/cdn-web-part-f12-source.png (100%)
 rename {images => docs/images}/cdn-web-part-files-in-folder.png (100%)
 rename {images => docs/images}/cdn-web-part-picker.png (100%)
 rename {images => docs/images}/cdn-web-part-rendering.png (100%)
 rename {images => docs/images}/cdn-write-manifest-json.png (100%)
 rename {images => docs/images}/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif (100%)
 rename {images => docs/images}/chrome-load-unsafe-scripts.png (100%)
 rename {images => docs/images}/collall.gif (100%)
 rename {images => docs/images}/collapse.gif (100%)
 rename {images => docs/images}/collapse_all.gif (100%)
 rename {images => docs/images}/contribute-docs-clone-options.png (100%)
 rename {images => docs/images}/contribute-docs-submit-pr.png (100%)
 rename {images => docs/images}/contribute-fork-docs-repo.png (100%)
 rename {images => docs/images}/copycode.gif (100%)
 rename {images => docs/images}/copycodeHighlight.gif (100%)
 rename {images => docs/images}/custom-property-pane-control-cascading-items-loaded-enabled.png (100%)
 rename {images => docs/images}/custom-property-pane-control-cascading-lists-loaded-items-disabled.png (100%)
 rename {images => docs/images}/custom-property-pane-control-cascading-loading-items.png (100%)
 rename {images => docs/images}/custom-property-pane-control-cascading-loading-lists.png (100%)
 rename {images => docs/images}/custom-property-pane-control-cascading-selected-list-item.png (100%)
 rename {images => docs/images}/custom-property-pane-control-components-folder.png (100%)
 rename {images => docs/images}/custom-property-pane-control-item-property-web-part-manifest.png (100%)
 rename {images => docs/images}/custom-property-pane-control-list-property-web-part-manifest.png (100%)
 rename {images => docs/images}/custom-property-pane-control-loading-options.png (100%)
 rename {images => docs/images}/custom-property-pane-control-selecting-option.png (100%)
 rename {images => docs/images}/custom-property-pane-control-visual-studio-code.png (100%)
 rename {images => docs/images}/custom-property-pane-control-web-part-first-run.png (100%)
 rename {images => docs/images}/custom-property-pane-control-web-part-imports.png (100%)
 rename {images => docs/images}/custom-property-pane-control-yeoman.png (100%)
 rename {images => docs/images}/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG (100%)
 rename {images => docs/images}/d4e17424-c06b-4635-aab8-4912cee5fe35.png (100%)
 rename {images => docs/images}/d69871f6-c503-463b-bf96-4b6d7306c313.png (100%)
 rename {images => docs/images}/datatables-sewp-filter.png (100%)
 rename {images => docs/images}/datatables-sewp.png (100%)
 rename {images => docs/images}/datatables-spfx-list-configured.png (100%)
 rename {images => docs/images}/datatables-spfx-listname-property.png (100%)
 rename {images => docs/images}/datatables-spfx.png (100%)
 rename {images => docs/images}/datatables-vscode.png (100%)
 rename {images => docs/images}/datatables-yeoman.png (100%)
 rename {images => docs/images}/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG (100%)
 rename {images => docs/images}/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG (100%)
 rename {images => docs/images}/deploy-container-create-helloworld-webpart.png (100%)
 rename {images => docs/images}/deploy-create-cdn-endpoint.png (100%)
 rename {images => docs/images}/deploy-create-cdn-profile.png (100%)
 rename {images => docs/images}/deploy-create-storage-account.png (100%)
 rename {images => docs/images}/deploy-option-blob-container.png (100%)
 rename {images => docs/images}/deploy-storage-account-accesskey.png (100%)
 rename {images => docs/images}/design-manager-preview-UI.jpg (100%)
 rename {images => docs/images}/design-wp-contexual-edits.png (100%)
 rename {images => docs/images}/design-wp-item-level-edits.png (100%)
 rename {images => docs/images}/design-wp-pp-accordion-groups.png (100%)
 rename {images => docs/images}/design-wp-pp-accordion.png (100%)
 rename {images => docs/images}/design-wp-pp-non-reactive.png (100%)
 rename {images => docs/images}/design-wp-pp-pages-step1.png (100%)
 rename {images => docs/images}/design-wp-pp-pages-step2.png (100%)
 rename {images => docs/images}/design-wp-pp-pages-step3.png (100%)
 rename {images => docs/images}/design-wp-pp-reactive.png (100%)
 rename {images => docs/images}/design-wp-pp-single.png (100%)
 rename {images => docs/images}/design-wp-pp.png (100%)
 rename {images => docs/images}/design-wp-responsive-max-width.png (100%)
 rename {images => docs/images}/design-wp-responsive-min-width.png (100%)
 rename {images => docs/images}/design-wp-todo-example.png (100%)
 rename {images => docs/images}/design-wp-todo-fabric-animations.png (100%)
 rename {images => docs/images}/design-wp-todo-loading-indicator.png (100%)
 rename {images => docs/images}/design-wp-todo-pp-checkbox.png (100%)
 rename {images => docs/images}/design-wp-todo-pp-description.png (100%)
 rename {images => docs/images}/design-wp-todo-pp-dropdown.png (100%)
 rename {images => docs/images}/design-wp-todo-pp-slider.png (100%)
 rename {images => docs/images}/design-wp-toolbar.png (100%)
 rename {images => docs/images}/design-wp-toolbox.png (100%)
 rename {images => docs/images}/dev.gif (100%)
 rename {images => docs/images}/dev_arch.gif (100%)
 rename {images => docs/images}/dropdown.gif (100%)
 rename {images => docs/images}/dropdownHover.gif (100%)
 rename {images => docs/images}/drpdown.gif (100%)
 rename {images => docs/images}/drpdown_orange.gif (100%)
 rename {images => docs/images}/drpdown_orange_up.gif (100%)
 rename {images => docs/images}/drpup.gif (100%)
 rename {images => docs/images}/e2cf6848-bd29-416b-b397-a1d670bd2910.gif (100%)
 rename {images => docs/images}/e3718687-682a-41a8-92b5-4eff9070348d.gif (100%)
 rename {images => docs/images}/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif (100%)
 rename {images => docs/images}/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG (100%)
 rename {images => docs/images}/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG (100%)
 rename {images => docs/images}/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG (100%)
 rename {images => docs/images}/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG (100%)
 rename {images => docs/images}/e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png (100%)
 rename {images => docs/images}/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png (100%)
 rename {images => docs/images}/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif (100%)
 rename {images => docs/images}/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif (100%)
 rename {images => docs/images}/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png (100%)
 rename {images => docs/images}/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg (100%)
 rename {images => docs/images}/ec60797c-d329-4922-a811-70c64598f4d5.PNG (100%)
 rename {images => docs/images}/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif (100%)
 rename {images => docs/images}/edit-webpart-classic-page.png (100%)
 rename {images => docs/images}/edit-webpart-modern-page.png (100%)
 rename {images => docs/images}/enterprise-guidance-trust-spfx-dialog.png (100%)
 rename {images => docs/images}/exp.gif (100%)
 rename {images => docs/images}/expall.gif (100%)
 rename {images => docs/images}/expand_all.gif (100%)
 rename {images => docs/images}/ext-app-alert-sp-page.png (100%)
 rename {images => docs/images}/ext-app-approve-cdn-address.png (100%)
 rename {images => docs/images}/ext-app-assets-folder.png (100%)
 rename {images => docs/images}/ext-app-cdn-folder-created.png (100%)
 rename {images => docs/images}/ext-app-cdn-origins-pending.png (100%)
 rename {images => docs/images}/ext-app-cdn-write-manifest.png (100%)
 rename {images => docs/images}/ext-app-debug-manifest-message.png (100%)
 rename {images => docs/images}/ext-app-gulp-serve.png (100%)
 rename {images => docs/images}/ext-app-header-footer-visible.png (100%)
 rename {images => docs/images}/ext-app-install-solution-to-site.png (100%)
 rename {images => docs/images}/ext-app-sppkg-deploy-trust.png (100%)
 rename {images => docs/images}/ext-app-vscode-app-base.png (100%)
 rename {images => docs/images}/ext-app-vscode-manifest.png (100%)
 rename {images => docs/images}/ext-app-vscode-methods.png (100%)
 rename {images => docs/images}/ext-app-vscode-solution-structure.png (100%)
 rename {images => docs/images}/ext-com-accept-debug-scripts.png (100%)
 rename {images => docs/images}/ext-com-assets-folder.png (100%)
 rename {images => docs/images}/ext-com-create-new-list.png (100%)
 rename {images => docs/images}/ext-com-default-customizer-output.png (100%)
 rename {images => docs/images}/ext-com-dialog-button-in-toolbar.png (100%)
 rename {images => docs/images}/ext-com-dialog-debug-scripts.png (100%)
 rename {images => docs/images}/ext-com-dialog-gulp-serve.png (100%)
 rename {images => docs/images}/ext-com-dialog-oob-alert-dialog.png (100%)
 rename {images => docs/images}/ext-com-dialog-output.png (100%)
 rename {images => docs/images}/ext-com-dialog-visible-deployment.png (100%)
 rename {images => docs/images}/ext-com-dialog-visible-dialog.png (100%)
 rename {images => docs/images}/ext-com-dialog-vs-code-initial.png (100%)
 rename {images => docs/images}/ext-com-dialog-yeoman-complete.png (100%)
 rename {images => docs/images}/ext-com-dialog-yeoman-prompts.png (100%)
 rename {images => docs/images}/ext-com-install-solution-to-site.png (100%)
 rename {images => docs/images}/ext-com-sppkg-deploy-trust.png (100%)
 rename {images => docs/images}/ext-com-vscode-base.png (100%)
 rename {images => docs/images}/ext-com-vscode-manifest.png (100%)
 rename {images => docs/images}/ext-com-vscode-solution-structure.png (100%)
 rename {images => docs/images}/ext-com-yeoman-complete.png (100%)
 rename {images => docs/images}/ext-com-yeoman-prompts.png (100%)
 rename {images => docs/images}/ext-erro-loading-debug-manifests.png (100%)
 rename {images => docs/images}/ext-field-accept-debug-scripts.png (100%)
 rename {images => docs/images}/ext-field-add-field-to-list.png (100%)
 rename {images => docs/images}/ext-field-assets-folder.png (100%)
 rename {images => docs/images}/ext-field-create-items-to-list.png (100%)
 rename {images => docs/images}/ext-field-create-new-list-order.png (100%)
 rename {images => docs/images}/ext-field-create-new-list.png (100%)
 rename {images => docs/images}/ext-field-default-customizer-output.png (100%)
 rename {images => docs/images}/ext-field-gulp-serve.png (100%)
 rename {images => docs/images}/ext-field-install-solution-to-site.png (100%)
 rename {images => docs/images}/ext-field-list-settings.png (100%)
 rename {images => docs/images}/ext-field-new-number-field-percent.png (100%)
 rename {images => docs/images}/ext-field-new-number-field.png (100%)
 rename {images => docs/images}/ext-field-onrender-default-solution.png (100%)
 rename {images => docs/images}/ext-field-percent-field-graphic.png (100%)
 rename {images => docs/images}/ext-field-render-field-without-debug.png (100%)
 rename {images => docs/images}/ext-field-sppkg-deploy-trust.png (100%)
 rename {images => docs/images}/ext-field-vscode-customizer-base.png (100%)
 rename {images => docs/images}/ext-field-vscode-manifest.png (100%)
 rename {images => docs/images}/ext-field-vscode-solution-structure.png (100%)
 rename {images => docs/images}/ext-field-yeoman-complete.png (100%)
 rename {images => docs/images}/ext-field-yeoman-prompts.png (100%)
 rename {images => docs/images}/ext-yeoman-app-complete.png (100%)
 rename {images => docs/images}/ext-yeoman-app-prompts.png (100%)
 rename {images => docs/images}/external-scripts-browser-loading-angular-from-cache.png (100%)
 rename {images => docs/images}/external-scripts-browser-loading-angular-two-web-parts.png (100%)
 rename {images => docs/images}/external-scripts-browser-loading-angular.png (100%)
 rename {images => docs/images}/external-scripts-bundle-size.png (100%)
 rename {images => docs/images}/external-scripts-external-angular-bundle-size.png (100%)
 rename {images => docs/images}/external-scripts-external-angular-two-bundles-size.png (100%)
 rename {images => docs/images}/external-scripts-gulp-bundle.png (100%)
 rename {images => docs/images}/external-scripts-non-amd-deps-error.png (100%)
 rename {images => docs/images}/external-scripts-non-amd-no-deps-error.png (100%)
 rename {images => docs/images}/external-scripts-two-bundles-size.png (100%)
 rename {images => docs/images}/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif (100%)
 rename {images => docs/images}/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG (100%)
 rename {images => docs/images}/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG (100%)
 rename {images => docs/images}/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG (100%)
 rename {images => docs/images}/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG (100%)
 rename {images => docs/images}/fabric-components-doc-card-view-ex.png (100%)
 rename {images => docs/images}/fada902b-fa38-4ac8-8566-3693b736ac35.gif (100%)
 rename {images => docs/images}/feature-provision-project-items.png (100%)
 rename {images => docs/images}/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png (100%)
 rename {images => docs/images}/filter1a.gif (100%)
 rename {images => docs/images}/filter1c.gif (100%)
 rename {images => docs/images}/footer.gif (100%)
 rename {images => docs/images}/fullcalendar-sewp-draganddrop.png (100%)
 rename {images => docs/images}/fullcalendar-sewp.png (100%)
 rename {images => docs/images}/fullcalendar-spfx-list-configured.png (100%)
 rename {images => docs/images}/fullcalendar-spfx-listname-property.png (100%)
 rename {images => docs/images}/fullcalendar-spfx.png (100%)
 rename {images => docs/images}/fullcalendar-vscode.png (100%)
 rename {images => docs/images}/fullcalendar-yeoman.png (100%)
 rename {images => docs/images}/gradient.gif (100%)
 rename {images => docs/images}/greencheck.gif (100%)
 rename {images => docs/images}/greychck.gif (100%)
 rename {images => docs/images}/guidance-governance-spfx-structure-schema.png (100%)
 rename {images => docs/images}/guidance-productionbuilds-debug-vs-ship-bundle.png (100%)
 rename {images => docs/images}/guidance-productionbuilds-import-lodash-at.png (100%)
 rename {images => docs/images}/guidance-productionbuilds-import-lodash.png (100%)
 rename {images => docs/images}/guidance-productionbuilds-two-bundles-with-libraries.png (100%)
 rename {images => docs/images}/guidance-productionbuilds-webpack-visualizer-angular.png (100%)
 rename {images => docs/images}/guidance-sharingdata-cookie-chrome.png (100%)
 rename {images => docs/images}/guidance-sharingdata-cookie-edge-first-request.png (100%)
 rename {images => docs/images}/guidance-sharingdata-cookie-edge-subsequent-request.png (100%)
 rename {images => docs/images}/guidance-sharingdata-loading-data-separately.png (100%)
 rename {images => docs/images}/guidance-sharingdata-reusing-data-global-variable-loading-message.png (100%)
 rename {images => docs/images}/guidance-sharingdata-reusing-data-global-variable-waiting-message.png (100%)
 rename {images => docs/images}/gulp-extend-image-resize-available-tasks.png (100%)
 rename {images => docs/images}/gulp-extend-image-resize-task.png (100%)
 rename {images => docs/images}/gulp-image-resize-task-available.png (100%)
 rename {images => docs/images}/gulp-tasks-available.png (100%)
 rename {images => docs/images}/gulp-upload-cdn.png (100%)
 rename {images => docs/images}/header_prev_next.jpg (100%)
 rename {images => docs/images}/header_sql_tutorial_blank.jpg (100%)
 rename {images => docs/images}/header_sql_tutorial_logo.GIF (100%)
 rename {images => docs/images}/hello-vs-webpart-finish-wizard.PNG (100%)
 rename {images => docs/images}/hello-vs-webpart-new-project-ts-nodejs.PNG (100%)
 rename {images => docs/images}/hello-vs-webpart-npm-explorer.PNG (100%)
 rename {images => docs/images}/hello-vs-webpart-soln-explorer.PNG (100%)
 rename {images => docs/images}/hello-vs-webpart-task-runner.PNG (100%)
 rename {images => docs/images}/hello-vs-webpart-update-properties.PNG (100%)
 rename {images => docs/images}/hellow-vs-webpart-step1-wizard.PNG (100%)
 rename {images => docs/images}/helloworld-wp-gulp-serve.png (100%)
 rename {images => docs/images}/helloworld-wp-vscode-project-structure.png (100%)
 rename {images => docs/images}/helloworld-wp-vscode-project.png (100%)
 rename {images => docs/images}/install-app-your-site.png (100%)
 rename {images => docs/images}/integrate-webpart-properties-schema.png (100%)
 mode change 100755 => 100644
 rename {images => docs/images}/jquery-accordion-wb.png (100%)
 rename {images => docs/images}/kw.gif (100%)
 rename {images => docs/images}/kw_adm.gif (100%)
 rename {images => docs/images}/kw_adm_arch.gif (100%)
 rename {images => docs/images}/kw_adm_dev.gif (100%)
 rename {images => docs/images}/kw_adm_dev_arch.gif (100%)
 rename {images => docs/images}/kw_arch.gif (100%)
 rename {images => docs/images}/kw_dev.gif (100%)
 rename {images => docs/images}/kw_dev_arch.gif (100%)
 rename {images => docs/images}/load.gif (100%)
 rename {images => docs/images}/load_hover.gif (100%)
 rename {images => docs/images}/localization-english-greeting-dutch-workbench.png (100%)
 rename {images => docs/images}/localization-initial-changes.png (100%)
 rename {images => docs/images}/localization-intellisense.png (100%)
 rename {images => docs/images}/localization-keys-comparison.png (100%)
 rename {images => docs/images}/localization-learn-more-nl-nl.png (100%)
 rename {images => docs/images}/localization-loc-folder.png (100%)
 rename {images => docs/images}/localization-multilingual-properties.png (100%)
 rename {images => docs/images}/localization-property-pane-nl-nl.png (100%)
 rename {images => docs/images}/localization-standard-locale-file.png (100%)
 rename {images => docs/images}/localization-visual-studio-code.png (100%)
 rename {images => docs/images}/localization-web-part-body-qps-ploc.png (100%)
 rename {images => docs/images}/localization-web-part-property-pane-qps-ploc.png (100%)
 rename {images => docs/images}/localization-yo-sharepoint.png (100%)
 rename {images => docs/images}/loggingSample.png (100%)
 rename {images => docs/images}/mod_icon_badge_conoverview.png (100%)
 rename {images => docs/images}/mod_icon_badge_reference.png (100%)
 rename {images => docs/images}/mod_icon_dobox.gif (100%)
 rename {images => docs/images}/mod_icon_getstartbox.gif (100%)
 rename {images => docs/images}/mod_icon_howto.png (100%)
 rename {images => docs/images}/mod_icon_incloud.gif (100%)
 rename {images => docs/images}/mod_icon_links_samples.png (100%)
 rename {images => docs/images}/mod_icon_onpremises.gif (100%)
 rename {images => docs/images}/mod_icon_startbox.gif (100%)
 rename {images => docs/images}/mod_icon_video.png (100%)
 rename {images => docs/images}/mod_logo_sharepoint.png (100%)
 rename {images => docs/images}/ng-intro-angular-config.png (100%)
 rename {images => docs/images}/ng-intro-app-folder.png (100%)
 rename {images => docs/images}/ng-intro-app-module.png (100%)
 rename {images => docs/images}/ng-intro-dataservice.png (100%)
 rename {images => docs/images}/ng-intro-hide-finished-tasks.png (100%)
 rename {images => docs/images}/ng-intro-homecontroller-event.png (100%)
 rename {images => docs/images}/ng-intro-homecontroller.png (100%)
 rename {images => docs/images}/ng-intro-injector-class-variable.png (100%)
 rename {images => docs/images}/ng-intro-manifest-property.png (100%)
 rename {images => docs/images}/ng-intro-project-visual-studio-code.png (100%)
 rename {images => docs/images}/ng-intro-property-interface.png (100%)
 rename {images => docs/images}/ng-intro-property-pane-toggle-browser.png (100%)
 rename {images => docs/images}/ng-intro-property-pane-toggle.png (100%)
 rename {images => docs/images}/ng-intro-strings-interface.png (100%)
 rename {images => docs/images}/ng-intro-strings.png (100%)
 rename {images => docs/images}/ng-intro-web-part-css.png (100%)
 rename {images => docs/images}/ng-intro-web-part-import-angular.png (100%)
 rename {images => docs/images}/ng-intro-web-part-render-angular.png (100%)
 rename {images => docs/images}/ng-intro-workbench-office-ui-fabric.png (100%)
 rename {images => docs/images}/ng-intro-yeoman-generator.png (100%)
 rename {images => docs/images}/ng-migration-angular-ngofficeuifabric-config.png (100%)
 rename {images => docs/images}/ng-migration-angular-ngofficeuifabric-import.png (100%)
 rename {images => docs/images}/ng-migration-angular-web-part-properties.png (100%)
 rename {images => docs/images}/ng-migration-app-config-web-url.png (100%)
 rename {images => docs/images}/ng-migration-app-files-visual-studio-code.png (100%)
 rename {images => docs/images}/ng-migration-app-folder-visual-studio-code.png (100%)
 rename {images => docs/images}/ng-migration-correct-styling.png (100%)
 rename {images => docs/images}/ng-migration-finished-tasks-hidden.png (100%)
 rename {images => docs/images}/ng-migration-first-run.png (100%)
 rename {images => docs/images}/ng-migration-import-propertypanetoggle.png (100%)
 rename {images => docs/images}/ng-migration-injector-property.png (100%)
 rename {images => docs/images}/ng-migration-old-office-ui-fabric.png (100%)
 rename {images => docs/images}/ng-migration-original-angular-application.png (100%)
 rename {images => docs/images}/ng-migration-project-visual-studio-code.png (100%)
 rename {images => docs/images}/ng-migration-todo-list.png (100%)
 rename {images => docs/images}/ng-migration-workbench-aspx-doclib.png (100%)
 rename {images => docs/images}/ng-migration-workbench-weburl.png (100%)
 rename {images => docs/images}/ng-migration-yeoman-generator.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows01.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows02.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows04.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows05.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows06.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows07.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows08.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows10.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows11.png (100%)
 rename {images => docs/images}/ngDebuggingSP2013Workflows12.png (100%)
 rename {images => docs/images}/ngFormsFig10.png (100%)
 rename {images => docs/images}/ngFormsFig5.png (100%)
 rename {images => docs/images}/ngFormsFig6.png (100%)
 rename {images => docs/images}/ngFormsFig7.png (100%)
 rename {images => docs/images}/ngFormsFig8.png (100%)
 rename {images => docs/images}/ngFormsFig9.png (100%)
 rename {images => docs/images}/ngGK_Fig02.png (100%)
 rename {images => docs/images}/ngGK_Fig03.png (100%)
 rename {images => docs/images}/ngGK_Fig04.png (100%)
 rename {images => docs/images}/ngGK_Fig05.png (100%)
 rename {images => docs/images}/ngGK_Fig06.png (100%)
 rename {images => docs/images}/ngGK_Fig07.png (100%)
 rename {images => docs/images}/ngGK_Fig08.png (100%)
 rename {images => docs/images}/ngGK_Fig09.png (100%)
 rename {images => docs/images}/ngGK_Fig10.png (100%)
 rename {images => docs/images}/ngGK_Fig11.png (100%)
 rename {images => docs/images}/ngGK_Fig12.png (100%)
 rename {images => docs/images}/ngGK_Fig13.png (100%)
 rename {images => docs/images}/ngGK_Fig14.png (100%)
 rename {images => docs/images}/ngGK_Fig15.png (100%)
 rename {images => docs/images}/ngGK_Fig16.png (100%)
 rename {images => docs/images}/ngGK_Fig17.png (100%)
 rename {images => docs/images}/ngGK_Fig18.png (100%)
 rename {images => docs/images}/ngGK_Fig19.png (100%)
 rename {images => docs/images}/ngGK_Fig20.png (100%)
 rename {images => docs/images}/ngGK_Fig21.png (100%)
 rename {images => docs/images}/ngGK_Fig22.png (100%)
 rename {images => docs/images}/ngGK_Flowchart.png (100%)
 rename {images => docs/images}/ngSP2013WorkflowCSOM01.png (100%)
 rename {images => docs/images}/ngSP2013WorkflowCSOM02.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD2013.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201302.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201303.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201304.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201305.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201306.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201307.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowSPD201308.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201201.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201202.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201203.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201204.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201205.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201206.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201207.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201208.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201209.png (100%)
 rename {images => docs/images}/ngWSSP2013WorkflowVS201210.png (100%)
 rename {images => docs/images}/ngWfFig01.png (100%)
 rename {images => docs/images}/ngWfFig02.png (100%)
 rename {images => docs/images}/ngWfFig03.png (100%)
 rename {images => docs/images}/ngWfFig04.png (100%)
 rename {images => docs/images}/ngWfFig05.png (100%)
 rename {images => docs/images}/ngWfFig06.png (100%)
 rename {images => docs/images}/ngWfFig07.png (100%)
 rename {images => docs/images}/ngWfFig08.png (100%)
 rename {images => docs/images}/ngWfFig09.png (100%)
 rename {images => docs/images}/ngWfFig10.png (100%)
 rename {images => docs/images}/ngWfFig11.png (100%)
 rename {images => docs/images}/ng_MsmqFeature.png (100%)
 rename {images => docs/images}/ng_MsmqQueues.png (100%)
 rename {images => docs/images}/note.gif (100%)
 rename {images => docs/images}/npm-outdated-global-packages-list.png (100%)
 rename {images => docs/images}/npm-outdated-packages-list.png (100%)
 rename {images => docs/images}/npm-update-packagejson-versions.png (100%)
 rename {images => docs/images}/odc_Office15_Access15OverviewDK2_Figure07.jpg (100%)
 rename {images => docs/images}/pencil.GIF (100%)
 rename {images => docs/images}/postman-add-webhook-body.png (100%)
 rename {images => docs/images}/postman-get-new-access-token.png (100%)
 rename {images => docs/images}/preconfiguredentries-multiple-web-parts-toolbox.png (100%)
 rename {images => docs/images}/preconfiguredentries-needs-configuration.png (100%)
 rename {images => docs/images}/preconfiguredentries-recent-documents-canvas.png (100%)
 rename {images => docs/images}/preconfiguredentries-recent-images-canvas.png (100%)
 rename {images => docs/images}/preconfiguredentries-recent-images-toolbox.png (100%)
 rename {images => docs/images}/preconfiguredentries-three-configurations-toolbox.png (100%)
 rename {images => docs/images}/preconfiguredentries-visual-studio-code.png (100%)
 rename {images => docs/images}/preconfiguredentries-yeoman.png (100%)
 rename {images => docs/images}/privclass.gif (100%)
 rename {images => docs/images}/privdelegate.gif (100%)
 rename {images => docs/images}/privdelicate.gif (100%)
 rename {images => docs/images}/privenum.gif (100%)
 rename {images => docs/images}/privenumeration.gif (100%)
 rename {images => docs/images}/privevent.gif (100%)
 rename {images => docs/images}/privextension.gif (100%)
 rename {images => docs/images}/privfield.gif (100%)
 rename {images => docs/images}/privinterface.gif (100%)
 rename {images => docs/images}/privmethod.gif (100%)
 rename {images => docs/images}/privproperty.gif (100%)
 rename {images => docs/images}/privstructure.gif (100%)
 rename {images => docs/images}/property-pane-example.png (100%)
 rename {images => docs/images}/property-validation-description-error-apply-disabled.png (100%)
 rename {images => docs/images}/property-validation-description-too-long-error.png (100%)
 rename {images => docs/images}/property-validation-empty-description-error.png (100%)
 rename {images => docs/images}/property-validation-empty-list-name-error.png (100%)
 rename {images => docs/images}/property-validation-invalid-list-name-error.png (100%)
 rename {images => docs/images}/property-validation-list-name-property.png (100%)
 rename {images => docs/images}/property-validation-partial-list-name-validation.png (100%)
 rename {images => docs/images}/property-validation-valid-list-name.png (100%)
 rename {images => docs/images}/property-validation-visual-studio-code.png (100%)
 rename {images => docs/images}/property-validation-yeoman-generator.png (100%)
 rename {images => docs/images}/protclass.gif (100%)
 rename {images => docs/images}/protdelegate.gif (100%)
 rename {images => docs/images}/protdeligate.gif (100%)
 rename {images => docs/images}/protenum.gif (100%)
 rename {images => docs/images}/protenumeration.gif (100%)
 rename {images => docs/images}/protevent.gif (100%)
 rename {images => docs/images}/protextension.gif (100%)
 rename {images => docs/images}/protfield.gif (100%)
 rename {images => docs/images}/protinterface.gif (100%)
 rename {images => docs/images}/protmethod.gif (100%)
 rename {images => docs/images}/protoperator.gif (100%)
 rename {images => docs/images}/protproperty.gif (100%)
 rename {images => docs/images}/protstructure.gif (100%)
 rename {images => docs/images}/pubclass.gif (100%)
 rename {images => docs/images}/pubdelegate.gif (100%)
 rename {images => docs/images}/pubenum.gif (100%)
 rename {images => docs/images}/pubenumeration.gif (100%)
 rename {images => docs/images}/pubevent.gif (100%)
 rename {images => docs/images}/pubextension.gif (100%)
 rename {images => docs/images}/pubfield.gif (100%)
 rename {images => docs/images}/pubinterface.gif (100%)
 rename {images => docs/images}/pubmethod.gif (100%)
 rename {images => docs/images}/puboperator.gif (100%)
 rename {images => docs/images}/pubproperty.gif (100%)
 rename {images => docs/images}/pubstructure.gif (100%)
 rename {images => docs/images}/react-cascading-dropdowns-item-dropdown-list-items.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-itemname-property-pane-dropdown.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-itemname-property-web-part-manifest.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-list-dropdown-available-lists.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-list-selected-item-disabled.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-listname-property-pane-dropdown.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-listname-property-web-part-manifest.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-loading-indicator-when-loading-items.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-visual-studio-code.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-web-part-first-run.png (100%)
 rename {images => docs/images}/react-cascading-dropdowns-yo-sharepoint.png (100%)
 rename {images => docs/images}/requirements1a.gif (100%)
 rename {images => docs/images}/requirements1c.gif (100%)
 rename {images => docs/images}/save.gif (100%)
 rename {images => docs/images}/save_hover.gif (100%)
 rename {images => docs/images}/security.gif (100%)
 rename {images => docs/images}/seealso1a.gif (100%)
 rename {images => docs/images}/seealso1c.gif (100%)
 rename {images => docs/images}/sp-app-deploy-trust.png (100%)
 rename {images => docs/images}/sp-app-replace-pkg.png (100%)
 rename {images => docs/images}/sp-helloworld-wp-modern-page.png (100%)
 rename {images => docs/images}/sp-lists-render-localhost.png (100%)
 rename {images => docs/images}/sp-lists-render-spsite.png (100%)
 rename {images => docs/images}/sp-lists-spsiteurl-wp.png (100%)
 rename {images => docs/images}/sp-mock-localhost-wp.png (100%)
 rename {images => docs/images}/sp-modern-page-toolbox.png (100%)
 rename {images => docs/images}/sp-modern-site-page.png (100%)
 rename {images => docs/images}/sp-pnp-js-guide-completed-setup.png (100%)
 rename {images => docs/images}/sp-pnp-js-guide-first-open.png (100%)
 rename {images => docs/images}/sp-pnp-js-guide-first-run.png (100%)
 rename {images => docs/images}/sp-pnp-js-guide-with-mock-data.png (100%)
 rename {images => docs/images}/sp-sample-todo-wp.png (100%)
 rename {images => docs/images}/sp-workbench-helloworld-pp.png (100%)
 rename {images => docs/images}/sp-workbench-helloworld-wp.png (100%)
 rename {images => docs/images}/sp-workbench-o365-helloworld-wp.png (100%)
 rename {images => docs/images}/sp-workbench-o365-toolbox.png (100%)
 rename {images => docs/images}/sp-workbench-o365-unsface-scripts.png (100%)
 rename {images => docs/images}/sp-workbench-o365.png (100%)
 rename {images => docs/images}/sp-workbench-toolbox.png (100%)
 rename {images => docs/images}/sp-workbench.png (100%)
 rename {images => docs/images}/sp-wp-classic-page-pp.png (100%)
 rename {images => docs/images}/sp-wp-classic-page.png (100%)
 rename {images => docs/images}/sp-wp-modern-page-pp.png (100%)
 rename {images => docs/images}/sp-wp-modern-page.png (100%)
 rename {images => docs/images}/sp15Con_CreateDisplayTemplateSP2013_Figure02.png (100%)
 rename {images => docs/images}/sp15Con_DesignPackageExp_Figure1.png (100%)
 rename {images => docs/images}/sp15Con_DeviceChannels_Fig1.png (100%)
 rename {images => docs/images}/sp15Con_SiteMasterPage_Figure2.png (100%)
 rename {images => docs/images}/sp15_BM25_formula.gif (100%)
 rename {images => docs/images}/sp15_freshness_formula.gif (100%)
 rename {images => docs/images}/sp15_linear_model_formula.gif (100%)
 rename {images => docs/images}/sp15_neural_network_formula.gif (100%)
 rename {images => docs/images}/sp15_transform_table_ranking_model.gif (100%)
 rename {images => docs/images}/sp15neuralnetworkinrankingmodels.gif (100%)
 rename {images => docs/images}/spd15-.JPG (100%)
 rename {images => docs/images}/spd15-AddListItemPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-AddListItemPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-AssignForm2Grp-txt.JPG (100%)
 rename {images => docs/images}/spd15-AssignForm2Grp-visio.JPG (100%)
 rename {images => docs/images}/spd15-AssignToDoItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-AssignToDoItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-CheckInItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-CheckInItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-CheckOutItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-CheckOutItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-ChkExactUserPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-ChkExactUserPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-ChkUserPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-ChkUserPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-CollectDataFrUser-txt.JPG (100%)
 rename {images => docs/images}/spd15-CollectDataFrUser-visio.JPG (100%)
 rename {images => docs/images}/spd15-CompareDataSrc-txt.JPG (100%)
 rename {images => docs/images}/spd15-CompareDataSrc-visio.JPG (100%)
 rename {images => docs/images}/spd15-CompareDocField-txt.JPG (100%)
 rename {images => docs/images}/spd15-CompareDocField-visio.JPG (100%)
 rename {images => docs/images}/spd15-CopyListItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-CopyListItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-CreateListItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-CreateListItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-CreatedBySpecPerson-txt.JPG (100%)
 rename {images => docs/images}/spd15-CreatedBySpecPerson-visio.JPG (100%)
 rename {images => docs/images}/spd15-CreatedInSpecDateSpan-txt.JPG (100%)
 rename {images => docs/images}/spd15-CreatedInSpecDateSpan-visio.JPG (100%)
 rename {images => docs/images}/spd15-DeleteItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-DeleteItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-DiscardItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-DiscardItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-FileIsSpecType-txt.JPG (100%)
 rename {images => docs/images}/spd15-FileIsSpecType-visio.JPG (100%)
 rename {images => docs/images}/spd15-FileSzInSpecRange-txt.JPG (100%)
 rename {images => docs/images}/spd15-FileSzInSpecRange-visio.JPG (100%)
 rename {images => docs/images}/spd15-ImportFromVisio.JPG (100%)
 rename {images => docs/images}/spd15-InheritListItemPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-InheritListItemPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-LogHist-txt.JPG (100%)
 rename {images => docs/images}/spd15-LogHist-visio.JPG (100%)
 rename {images => docs/images}/spd15-LookupMgr4User-txt.JPG (100%)
 rename {images => docs/images}/spd15-LookupMgr4User-visio.JPG (100%)
 rename {images => docs/images}/spd15-ModifiedBySpecPerson-txt.JPG (100%)
 rename {images => docs/images}/spd15-ModifiedBySpecPerson-visio.JPG (100%)
 rename {images => docs/images}/spd15-ModifiedInSpecDateSpan-txt.JPG (100%)
 rename {images => docs/images}/spd15-ModifiedInSpecDateSpan-visio.JPG (100%)
 rename {images => docs/images}/spd15-PauseDate-txt.JPG (100%)
 rename {images => docs/images}/spd15-PauseDate-visio.JPG (100%)
 rename {images => docs/images}/spd15-PauseDuration-txt.JPG (100%)
 rename {images => docs/images}/spd15-PauseDuration-visio.JPG (100%)
 rename {images => docs/images}/spd15-ReplaceListItemPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-ReplaceListItemPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-RmListItemPerms-txt.JPG (100%)
 rename {images => docs/images}/spd15-RmListItemPerms-visio.JPG (100%)
 rename {images => docs/images}/spd15-SendApproval4DocSet-txt.JPG (100%)
 rename {images => docs/images}/spd15-SendApproval4DocSet-visio.JPG (100%)
 rename {images => docs/images}/spd15-SendDoc2Repos-txt.JPG (100%)
 rename {images => docs/images}/spd15-SendDoc2Repos-visio.JPG (100%)
 rename {images => docs/images}/spd15-SendDocSet2Repos-txt.JPG (100%)
 rename {images => docs/images}/spd15-SendDocSet2Repos-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetContentApprStatus-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetContentApprStatus4DocSet-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetContentApprovalStatus-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetContentApprovalStatus-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetFieldCurrItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetFieldCurrItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetTimePortion-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetTimePortion-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetWFStatus-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetWFStatus-visio.JPG (100%)
 rename {images => docs/images}/spd15-SetWFVar-txt.JPG (100%)
 rename {images => docs/images}/spd15-SetWFVar-visio.JPG (100%)
 rename {images => docs/images}/spd15-StartApprovalProc-txt.JPG (100%)
 rename {images => docs/images}/spd15-StartApprovalProc-visio.JPG (100%)
 rename {images => docs/images}/spd15-StartCustomTask-txt.JPG (100%)
 rename {images => docs/images}/spd15-StartCustomTask-visio.JPG (100%)
 rename {images => docs/images}/spd15-StartFeedback-txt.JPG (100%)
 rename {images => docs/images}/spd15-StartFeedback-visio.JPG (100%)
 rename {images => docs/images}/spd15-StopWF-txt.JPG (100%)
 rename {images => docs/images}/spd15-StopWF-visio.JPG (100%)
 rename {images => docs/images}/spd15-TaskActions1.png (100%)
 rename {images => docs/images}/spd15-TitleFieldKeywords-txt.JPG (100%)
 rename {images => docs/images}/spd15-TitleFieldKeywords-visio.JPG (100%)
 rename {images => docs/images}/spd15-UpdateListItem-txt.JPG (100%)
 rename {images => docs/images}/spd15-UpdateListItem-visio.JPG (100%)
 rename {images => docs/images}/spd15-WFStart-icon.JPG (100%)
 rename {images => docs/images}/spd15-WFStop-icon.JPG (100%)
 rename {images => docs/images}/spd15-Wait4FieldChange-txt.JPG (100%)
 rename {images => docs/images}/spd15-Wait4FieldChange-visio.JPG (100%)
 rename {images => docs/images}/spd15-addcomment-txt.JPG (100%)
 rename {images => docs/images}/spd15-addcomment-visio.JPG (100%)
 rename {images => docs/images}/spd15-addtimetodate-txt.JPG (100%)
 rename {images => docs/images}/spd15-addtimetodate-visio.JPG (100%)
 rename {images => docs/images}/spd15-docalc-txt.JPG (100%)
 rename {images => docs/images}/spd15-docalc-visio.JPG (100%)
 rename {images => docs/images}/spd15-wf-PO.JPG (100%)
 rename {images => docs/images}/spd15-wf-error1.JPG (100%)
 rename {images => docs/images}/spd15-wf-error11.JPG (100%)
 rename {images => docs/images}/spd15-wf-error12.JPG (100%)
 rename {images => docs/images}/spd15-wf-error13.JPG (100%)
 rename {images => docs/images}/spd15-wf-error14.JPG (100%)
 rename {images => docs/images}/spd15-wf-error15.JPG (100%)
 rename {images => docs/images}/spd15-wf-error16.JPG (100%)
 rename {images => docs/images}/spd15-wf-error17.JPG (100%)
 rename {images => docs/images}/spd15-wf-error18.JPG (100%)
 rename {images => docs/images}/spd15-wf-error19.JPG (100%)
 rename {images => docs/images}/spd15-wf-error2.JPG (100%)
 rename {images => docs/images}/spd15-wf-error20.JPG (100%)
 rename {images => docs/images}/spd15-wf-error21.JPG (100%)
 rename {images => docs/images}/spd15-wf-error3.JPG (100%)
 rename {images => docs/images}/spd15-wf-error4.JPG (100%)
 rename {images => docs/images}/spd15-wf-error5.JPG (100%)
 rename {images => docs/images}/spd15-wf-error6.JPG (100%)
 rename {images => docs/images}/spd15-wf-error7.JPG (100%)
 rename {images => docs/images}/spd15-wf-error8.JPG (100%)
 rename {images => docs/images}/spd15-wf-error9.JPG (100%)
 rename {images => docs/images}/spd15-wf-exportToVisio.png (100%)
 rename {images => docs/images}/spd15-wf-importFromVisio.png (100%)
 rename {images => docs/images}/spd15-wf-logical-ops.JPG (100%)
 rename {images => docs/images}/spd15-wf-step1a.JPG (100%)
 rename {images => docs/images}/spd15-wf.JPG (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorial1.png (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorial2.png (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorial3.png (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorial4.png (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorialcommand.png (100%)
 rename {images => docs/images}/spfx-ext-youtube-tutorialfield.png (100%)
 rename {images => docs/images}/spfx-webcast-youtube-provision-feature-elements.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial0.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial1.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial2.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial3.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial4.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial5.png (100%)
 rename {images => docs/images}/spfx-youtube-tutorial6.png (100%)
 rename {images => docs/images}/static.gif (100%)
 rename {images => docs/images}/tenant-deploy-app-catalog.png (100%)
 rename {images => docs/images}/tenant-deploy-yeoman.png (100%)
 rename {images => docs/images}/tenant-deploy-youtube-video.png (100%)
 rename {images => docs/images}/theme_.PNG (100%)
 rename {images => docs/images}/themed-styles-blue-web-part-red-site.png (100%)
 rename {images => docs/images}/themed-styles-button-class.png (100%)
 rename {images => docs/images}/themed-styles-ms-bgcolor-themedark-class.png (100%)
 rename {images => docs/images}/themed-styles-row-class.png (100%)
 rename {images => docs/images}/themed-styles-side-by-side.png (100%)
 rename {images => docs/images}/thirdpartycss-accordion-not-styled.png (100%)
 rename {images => docs/images}/thirdpartycss-accordion-styled.png (100%)
 rename {images => docs/images}/thirdpartycss-jquery-ui-css-size.png (100%)
 rename {images => docs/images}/thirdpartycss-libraries-cdn.png (100%)
 rename {images => docs/images}/thirdpartycss-visual-studio-code.png (100%)
 rename {images => docs/images}/thirdpartycss-yeoman.png (100%)
 rename {images => docs/images}/toolchain-gulp-serve-task.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-add-app.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-app-details.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-debug-folder.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-hover-menu.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-initial-structure.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-list-view.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-new-list.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-override-sppkg.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-provision-app.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-trust-app-catalog.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-updating-app.png (100%)
 rename {images => docs/images}/tutorial-feature-solution-version-2.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-console-log.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-interfaces-documentsservice.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-interfaces.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-recent-document-recent-documents.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-recent-document.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-recent-documents.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-vscode.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-yo-sharepoint-recent-document.png (100%)
 rename {images => docs/images}/tutorial-sharingdata-yo-sharepoint-recent-documents.png (100%)
 rename {images => docs/images}/tutorial-spjsom-vscode.png (100%)
 rename {images => docs/images}/tutorial-spjsom-web-part-list-titles.png (100%)
 rename {images => docs/images}/tutorial-spjsom-yo-sharepoint.png (100%)
 rename {images => docs/images}/upload-solution-app-catalog.png (100%)
 rename {images => docs/images}/vscode-debugging-add-debug-configuration.png (100%)
 rename {images => docs/images}/vscode-debugging-adding-web-part-to-canvas.png (100%)
 rename {images => docs/images}/vscode-debugging-breakpoint-active.png (100%)
 rename {images => docs/images}/vscode-debugging-breakpoint-configured.png (100%)
 rename {images => docs/images}/vscode-debugging-breakpoint-hit-o365.png (100%)
 rename {images => docs/images}/vscode-debugging-breakpoint-hit.png (100%)
 rename {images => docs/images}/vscode-debugging-chrome-debug-environment.png (100%)
 rename {images => docs/images}/vscode-debugging-chrome-started.png (100%)
 rename {images => docs/images}/vscode-debugging-debugger-chrome-extension.png (100%)
 rename {images => docs/images}/vscode-debugging-debugger-extension-installed-reload.png (100%)
 rename {images => docs/images}/vscode-debugging-debugging-hosted-workbench.png (100%)
 rename {images => docs/images}/vscode-debugging-gulp-serve.png (100%)
 rename {images => docs/images}/vscode-debugging-o365-login.png (100%)
 rename {images => docs/images}/vscode-debugging-vscode-debug.png (100%)
 rename {images => docs/images}/vscode-debugging-vscode-extensions.png (100%)
 rename {images => docs/images}/webhook-azure-function0.png (100%)
 rename {images => docs/images}/webhook-azure-function1.png (100%)
 rename {images => docs/images}/webhook-azure-function2.png (100%)
 rename {images => docs/images}/webhook-azure-function3.png (100%)
 rename {images => docs/images}/webhook-azure-function4.png (100%)
 rename {images => docs/images}/webhook-azure-function5.png (100%)
 rename {images => docs/images}/webhook-azure-function6.png (100%)
 rename {images => docs/images}/webhook-azure-function7.png (100%)
 rename {images => docs/images}/webhook-azure-function8.png (100%)
 rename {images => docs/images}/webhook-sample-add-process.png (100%)
 rename {images => docs/images}/webhook-sample-application.png (100%)
 rename {images => docs/images}/webhook-sample-async-getchanges.png (100%)
 rename {images => docs/images}/webhook-sample-call-webhook.png (100%)
 rename {images => docs/images}/webhook-sample-end-to-end-flow.png (100%)
 rename {images => docs/images}/webpart-configure-property-pane.png (100%)
 rename {images => docs/images}/webpart-gallery-helloworld.png (100%)
 rename {images => docs/images}/wf15-eventingactions3.png (100%)
 rename {images => docs/images}/wf15-eventingactions4.png (100%)
 rename {images => docs/images}/wfAddNewItemDialog_b2.png (100%)
 rename {images => docs/images}/wfArchitecture1.png (100%)
 rename {images => docs/images}/wfInteropBridge.png (100%)
 rename {images => docs/images}/wfInteropMessaging.png (100%)
 rename {images => docs/images}/wfInterop_.png (100%)
 rename {images => docs/images}/wfInterop_Stage1.png (100%)
 rename {images => docs/images}/wfNewProject_b2.png (100%)
 rename {images => docs/images}/wfSimple.gif (100%)
 rename {images => docs/images}/wfToolbox_b2.png (100%)
 rename {images => docs/images}/wfVS_ActivityNode.jpg (100%)
 rename {images => docs/images}/wfVS_NewItem.JPG (100%)
 rename {images => docs/images}/wfVS_NewProjectDialog.JPG (100%)
 rename {images => docs/images}/wfVS_WorkflowToolbox.jpg (100%)
 rename {images => docs/images}/wn_DevTools_1.png (100%)
 rename {images => docs/images}/wn_DevTools_2.png (100%)
 rename {images => docs/images}/wn_DevTools_3.png (100%)
 rename {images => docs/images}/wn_Mobility_.png (100%)
 rename {images => docs/images}/wn_Mobility_2.png (100%)
 rename {images => docs/images}/wn_Mobility_3.png (100%)
 rename {images => docs/images}/wn_Platform_1.png (100%)
 rename {images => docs/images}/wn_Platform_2.png (100%)
 rename {images => docs/images}/wn_Platform_3.png (100%)
 rename {images => docs/images}/wn_Platform_4.png (100%)
 rename {images => docs/images}/wn_Social_1.png (100%)
 rename {images => docs/images}/wn_Social_2.png (100%)
 rename {images => docs/images}/wn_Social_3.png (100%)
 rename {images => docs/images}/wn_Social_4.png (100%)
 rename {images => docs/images}/wn_WebStandards_1.png (100%)
 rename {images => docs/images}/wn_WebStandards_2.png (100%)
 rename {images => docs/images}/wn_WebStandards_3.png (100%)
 rename {images => docs/images}/wn_WebStandards_4.png (100%)
 rename {images => docs/images}/wn_appServices_1.png (100%)
 rename {images => docs/images}/wn_appServices_2.png (100%)
 rename {images => docs/images}/wn_appServices_3.png (100%)
 rename {images => docs/images}/wn_appServices_4.png (100%)
 rename {images => docs/images}/wn_bcs_1.png (100%)
 rename {images => docs/images}/wn_bcs_2.png (100%)
 rename {images => docs/images}/wn_bcs_3.png (100%)
 rename {images => docs/images}/wn_cloud_1.png (100%)
 rename {images => docs/images}/wn_cloud_2.png (100%)
 rename {images => docs/images}/wn_cloud_3.png (100%)
 rename {images => docs/images}/wn_ecm_1.png (100%)
 rename {images => docs/images}/wn_ecm_2.png (100%)
 rename {images => docs/images}/wn_ecm_3.png (100%)
 rename {images => docs/images}/wn_ecm_4.png (100%)
 rename {images => docs/images}/wn_search_1.png (100%)
 rename {images => docs/images}/wn_search_2.png (100%)
 rename {images => docs/images}/wn_search_3.png (100%)
 rename {images => docs/images}/wn_workflow_1.png (100%)
 rename {images => docs/images}/wn_workflow_2.png (100%)
 rename {images => docs/images}/wn_workflow_3.png (100%)
 rename {images => docs/images}/wn_workflow_4.png (100%)
 rename {images => docs/images}/xna.gif (100%)
 rename {images => docs/images}/yeoman-sp-cmdline-options.png (100%)
 rename {images => docs/images}/yeoman-sp-complete.png (100%)
 rename {images => docs/images}/yeoman-sp-generator.png (100%)
 rename {images => docs/images}/yeoman-sp-prompts.png (100%)
 rename {images => docs/images}/youtube-getting-started-with-webhooks.png (100%)
 rename {images => docs/images}/youtube-introducing-sharepoint-webhooks.png (100%)
 create mode 100644 docs/index.md
 create mode 100644 docs/toc.yml
 create mode 100644 general-development/docfx.json
 delete mode 100644 images/spfx-fp2-youtube-video.png
 delete mode 100644 misc/SharePointDocumentationToc.xml
 delete mode 100644 misc/SharePointReferenceToc.xml
 delete mode 100644 misc/SharepointBreadcrumbs.json
 delete mode 100644 reference/spfx/es6-collections-module.md
 delete mode 100644 reference/spfx/es6-collections/interface/__new-mapconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/__new-setconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/__new-weakmapconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/__new-weaksetconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/add-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/add-weakset.md
 delete mode 100644 reference/spfx/es6-collections/interface/clear-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/clear-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/clear-weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/clear-weakset.md
 delete mode 100644 reference/spfx/es6-collections/interface/delete-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/delete-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/delete-weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/delete-weakset.md
 delete mode 100644 reference/spfx/es6-collections/interface/entries-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/entries-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/foreach-foreachable.md
 delete mode 100644 reference/spfx/es6-collections/interface/foreach-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/foreach-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/foreachable.md
 delete mode 100644 reference/spfx/es6-collections/interface/get-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/get-weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/has-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/has-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/has-weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/has-weakset.md
 delete mode 100644 reference/spfx/es6-collections/interface/iterator.md
 delete mode 100644 reference/spfx/es6-collections/interface/iteratorresult.md
 delete mode 100644 reference/spfx/es6-collections/interface/keys-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/keys-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/map.md
 delete mode 100644 reference/spfx/es6-collections/interface/mapconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/next-iterator.md
 delete mode 100644 reference/spfx/es6-collections/interface/return-iterator.md
 delete mode 100644 reference/spfx/es6-collections/interface/set-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/set-weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/set.md
 delete mode 100644 reference/spfx/es6-collections/interface/setconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/throw-iterator.md
 delete mode 100644 reference/spfx/es6-collections/interface/values-map.md
 delete mode 100644 reference/spfx/es6-collections/interface/values-set.md
 delete mode 100644 reference/spfx/es6-collections/interface/weakmap.md
 delete mode 100644 reference/spfx/es6-collections/interface/weakmapconstructor.md
 delete mode 100644 reference/spfx/es6-collections/interface/weakset.md
 delete mode 100644 reference/spfx/es6-collections/interface/weaksetconstructor.md
 delete mode 100644 reference/spfx/sharepoint-framework-reference-overview.md
 delete mode 100644 reference/spfx/sp-application-base-module.md
 delete mode 100644 reference/spfx/sp-application-base/class/applicationcustomizercontext.md
 delete mode 100644 reference/spfx/sp-application-base/class/baseapplicationcustomizer.md
 delete mode 100644 reference/spfx/sp-application-base/class/dispose-placeholder.md
 delete mode 100644 reference/spfx/sp-application-base/class/onrender-baseapplicationcustomizer.md
 delete mode 100644 reference/spfx/sp-application-base/class/placeholder.md
 delete mode 100644 reference/spfx/sp-application-base/class/placeholdercollection.md
 delete mode 100644 reference/spfx/sp-application-base/class/tryattach-placeholdercollection.md
 delete mode 100644 reference/spfx/sp-application-base/interface/iplaceholderattachoptions.md
 delete mode 100644 reference/spfx/sp-component-base-module.md
 delete mode 100644 reference/spfx/sp-component-base/class/basecomponent.md
 delete mode 100644 reference/spfx/sp-component-base/class/basecomponentcontext.md
 delete mode 100644 reference/spfx/sp-component-base/class/getbasemanifest-basecomponentcontext.md
 delete mode 100644 reference/spfx/sp-component-base/class/onprovideservices-basecomponent.md
 delete mode 100644 reference/spfx/sp-component-base/interface/iclientsidecomponentcontext.md
 delete mode 100644 reference/spfx/sp-core-library-module.md
 delete mode 100644 reference/spfx/sp-core-library/class/compare-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/consume-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/create-servicekey.md
 delete mode 100644 reference/spfx/sp-core-library/class/createandprovide-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/createcustom-servicekey.md
 delete mode 100644 reference/spfx/sp-core-library/class/createdefaultandprovide-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/environment.md
 delete mode 100644 reference/spfx/sp-core-library/class/equals-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/equals-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/error-log.md
 delete mode 100644 reference/spfx/sp-core-library/class/finish-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/format-text.md
 delete mode 100644 reference/spfx/sp-core-library/class/generate-randomnumbergenerator.md
 delete mode 100644 reference/spfx/sp-core-library/class/getdate-timeprovider.md
 delete mode 100644 reference/spfx/sp-core-library/class/getparent-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/gettimestamp-timeprovider.md
 delete mode 100644 reference/spfx/sp-core-library/class/getvalue-urlqueryparametercollection.md
 delete mode 100644 reference/spfx/sp-core-library/class/getvalues-urlqueryparametercollection.md
 delete mode 100644 reference/spfx/sp-core-library/class/greaterthan-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/info-log.md
 delete mode 100644 reference/spfx/sp-core-library/class/isnonemptystring-validate.md
 delete mode 100644 reference/spfx/sp-core-library/class/isnotnullorundefined-validate.md
 delete mode 100644 reference/spfx/sp-core-library/class/istrue-validate.md
 delete mode 100644 reference/spfx/sp-core-library/class/isvalid-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/isvalid-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/lessthan-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/log.md
 delete mode 100644 reference/spfx/sp-core-library/class/newguid-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/parse-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/parse-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/provide-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/randomnumbergenerator.md
 delete mode 100644 reference/spfx/sp-core-library/class/satisfies-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/servicekey.md
 delete mode 100644 reference/spfx/sp-core-library/class/servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/session.md
 delete mode 100644 reference/spfx/sp-core-library/class/startnewchild-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/startnewroot-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/class/text.md
 delete mode 100644 reference/spfx/sp-core-library/class/timeprovider.md
 delete mode 100644 reference/spfx/sp-core-library/class/tostring-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/tostring-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/tryparse-guid.md
 delete mode 100644 reference/spfx/sp-core-library/class/tryparse-version.md
 delete mode 100644 reference/spfx/sp-core-library/class/urlqueryparametercollection.md
 delete mode 100644 reference/spfx/sp-core-library/class/validate.md
 delete mode 100644 reference/spfx/sp-core-library/class/verbose-log.md
 delete mode 100644 reference/spfx/sp-core-library/class/version.md
 delete mode 100644 reference/spfx/sp-core-library/class/warn-log.md
 delete mode 100644 reference/spfx/sp-core-library/class/whenfinished-servicescope.md
 delete mode 100644 reference/spfx/sp-core-library/enum/displaymode.md
 delete mode 100644 reference/spfx/sp-core-library/enum/environmenttype.md
 delete mode 100644 reference/spfx/sp-core-library/interface/generate-irandomnumbergenerator.md
 delete mode 100644 reference/spfx/sp-core-library/interface/getdate-itimeprovider.md
 delete mode 100644 reference/spfx/sp-core-library/interface/gettimestamp-itimeprovider.md
 delete mode 100644 reference/spfx/sp-core-library/interface/irandomnumbergenerator.md
 delete mode 100644 reference/spfx/sp-core-library/interface/iservicecollection.md
 delete mode 100644 reference/spfx/sp-core-library/interface/itimeprovider.md
 delete mode 100644 reference/spfx/sp-dialog-module.md
 delete mode 100644 reference/spfx/sp-dialog/class/alert-dialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/alert-secondarydialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/close-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/dialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/getconfig-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/onclose-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/onopen-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/prompt-dialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/prompt-secondarydialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/render-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/secondarydialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/show-basedialog.md
 delete mode 100644 reference/spfx/sp-dialog/class/show-secondarydialog.md
 delete mode 100644 reference/spfx/sp-dialog/interface/ialertoptions.md
 delete mode 100644 reference/spfx/sp-dialog/interface/idialogconfiguration.md
 delete mode 100644 reference/spfx/sp-dialog/interface/idialogshowingoptions.md
 delete mode 100644 reference/spfx/sp-dialog/interface/ipromptoptions.md
 delete mode 100644 reference/spfx/sp-extension-base-module.md
 delete mode 100644 reference/spfx/sp-extension-base/class/baseextension.md
 delete mode 100644 reference/spfx/sp-extension-base/class/extensioncontext.md
 delete mode 100644 reference/spfx/sp-extension-base/class/ondispose-baseextension.md
 delete mode 100644 reference/spfx/sp-extension-base/class/oninit-baseextension.md
 delete mode 100644 reference/spfx/sp-http-module.md
 delete mode 100644 reference/spfx/sp-http/class/arraybuffer-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/beginbatch-sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/blob-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/clone-graphclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/clone-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/clone-sphttpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/fetch-graphhttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/fetch-httpclient.md
 delete mode 100644 reference/spfx/sp-http/class/fetch-sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/formdata-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/get-graphhttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/get-httpclient.md
 delete mode 100644 reference/spfx/sp-http/class/get-sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/getweburlfromrequesturl-sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/graphclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/graphhttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/graphhttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/httpclient.md
 delete mode 100644 reference/spfx/sp-http/class/httpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/initializeflags-httpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/initializeflags-sphttpclientcommonconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/initializeflags-sphttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/json-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/odataversion.md
 delete mode 100644 reference/spfx/sp-http/class/overridewith-httpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/overridewith-sphttpclientcommonconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/overridewith-sphttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/post-graphhttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/post-httpclient.md
 delete mode 100644 reference/spfx/sp-http/class/post-sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/sphttpclient.md
 delete mode 100644 reference/spfx/sp-http/class/sphttpclientcommonconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/sphttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/class/sphttpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/text-httpclientresponse.md
 delete mode 100644 reference/spfx/sp-http/class/tostring-odataversion.md
 delete mode 100644 reference/spfx/sp-http/class/tryparsefromheaders-odataversion.md
 delete mode 100644 reference/spfx/sp-http/interface/igraphhttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/interface/igraphhttpclientconfigurations.md
 delete mode 100644 reference/spfx/sp-http/interface/igraphhttpclientoptions.md
 delete mode 100644 reference/spfx/sp-http/interface/ihttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/interface/ihttpclientconfigurations.md
 delete mode 100644 reference/spfx/sp-http/interface/ihttpclientoptions.md
 delete mode 100644 reference/spfx/sp-http/interface/isphttpclientcommonconfiguration.md
 delete mode 100644 reference/spfx/sp-http/interface/isphttpclientconfiguration.md
 delete mode 100644 reference/spfx/sp-http/interface/isphttpclientconfigurations.md
 delete mode 100644 reference/spfx/sp-http/interface/isphttpclientoptions.md
 delete mode 100644 reference/spfx/sp-listview-extensibility-module.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/basefieldcustomizer.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/baselistviewcommandset.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/cellformatter.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/columnaccessor.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/fieldcustomizercontext.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/getvalue-rowaccessor.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/getvaluebyname-rowaccessor.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/listviewaccessor.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/listviewcommandsetcontext.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/ondisposecell-basefieldcustomizer.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/onexecute-baselistviewcommandset.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/onrefreshcommand-baselistviewcommandset.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/onrendercell-basefieldcustomizer.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/renderastext-cellformatter.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/class/rowaccessor.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md
 delete mode 100644 reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md
 delete mode 100644 reference/spfx/sp-loader-module.md
 delete mode 100644 reference/spfx/sp-loader/class/initialize-spcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/class/loadcomponent-spcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/class/loadcss-spcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/class/loadscript-spcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/class/spcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/interface/iloadscriptoptions.md
 delete mode 100644 reference/spfx/sp-loader/interface/ispcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/interface/loadcomponent-ispcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/interface/loadcss-ispcomponentloader.md
 delete mode 100644 reference/spfx/sp-loader/interface/loadscript-ispcomponentloader.md
 delete mode 100644 reference/spfx/sp-odata-types-module.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatabasepermission.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatachangetoken.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatacontextwebinformation.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatalist.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatalistitem.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatanavigationnode.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatanavigationnodecollection.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatauser.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodatausercustomaction.md
 delete mode 100644 reference/spfx/sp-odata-types/interface/iodataweb.md
 delete mode 100644 reference/spfx/sp-page-context-module.md
 delete mode 100644 reference/spfx/sp-page-context/class/cultureinfo.md
 delete mode 100644 reference/spfx/sp-page-context/class/hasallpermissions-sppermission.md
 delete mode 100644 reference/spfx/sp-page-context/class/hasanypermissions-sppermission.md
 delete mode 100644 reference/spfx/sp-page-context/class/haspermission-sppermission.md
 delete mode 100644 reference/spfx/sp-page-context/class/pagecontext.md
 delete mode 100644 reference/spfx/sp-page-context/class/spfield.md
 delete mode 100644 reference/spfx/sp-page-context/class/splist.md
 delete mode 100644 reference/spfx/sp-page-context/class/splistitem.md
 delete mode 100644 reference/spfx/sp-page-context/class/sppermission.md
 delete mode 100644 reference/spfx/sp-page-context/class/spsite.md
 delete mode 100644 reference/spfx/sp-page-context/class/spuser.md
 delete mode 100644 reference/spfx/sp-page-context/class/spweb.md
 delete mode 100644 reference/spfx/sp-webpart-base-module.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/clearerror-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/getpropertypaneconfiguration-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onafterdeserialize-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onafterpropertypanechangesapplied-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onbeforeserialize-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/ondisplaymodechanged-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/ondispose-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/oninit-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationcomplete-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationstart-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onpropertypanefieldchanged-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/onpropertypanerendered-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/render-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/rendercompleted-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/class/rendererror-baseclientsidewebpart.md
 delete mode 100644 reference/spfx/sp-webpart-base/enum/propertypanebuttontype.md
 delete mode 100644 reference/spfx/sp-webpart-base/enum/propertypanefieldtype.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanebutton.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanecheckbox.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanechoicegroup.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanecustomfield.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanedropdown.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanehorizontalrule.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanelabel.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanelink.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypaneslider.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanetextfield.md
 delete mode 100644 reference/spfx/sp-webpart-base/function/propertypanetoggle.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/__index-iwebpartpropertiesmetadata.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/clearerror-iclientsidewebpartstatusrenderer.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/clearloadingindicator-iclientsidewebpartstatusrenderer.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/displayloadingindicator-iclientsidewebpartstatusrenderer.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iplaceholderspinnerprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypaneaccessor.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanebuttonprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanecheckboxprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoption.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypaneconfiguration.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanecustomfieldprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanedropdownoption.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanedropdownprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanefield.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanegroup.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanelabelprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanelinkprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanepage.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanepageheader.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanesliderprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanetextfieldprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ipropertypanetoggleprops.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iserializedserverprocesseddata.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iserializedwebpartdata.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/ispropertypaneopen-ipropertypaneaccessor.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/isrenderedbywebpart-ipropertypaneaccessor.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iwebpartcontext.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iwebpartdata.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/iwebpartpropertiesmetadata.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/open-ipropertypaneaccessor.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/refresh-ipropertypaneaccessor.md
 delete mode 100644 reference/spfx/sp-webpart-base/interface/rendererror-iclientsidewebpartstatusrenderer.md
 delete mode 100644 reference/spfx/web-apis-module.md
 delete mode 100644 reference/spfx/web-apis/class/all-promise.md
 delete mode 100644 reference/spfx/web-apis/class/append-headers.md
 delete mode 100644 reference/spfx/web-apis/class/arraybuffer-body.md
 delete mode 100644 reference/spfx/web-apis/class/blob-body.md
 delete mode 100644 reference/spfx/web-apis/class/body.md
 delete mode 100644 reference/spfx/web-apis/class/catch-promise.md
 delete mode 100644 reference/spfx/web-apis/class/clone-response.md
 delete mode 100644 reference/spfx/web-apis/class/delete-headers.md
 delete mode 100644 reference/spfx/web-apis/class/error-response.md
 delete mode 100644 reference/spfx/web-apis/class/foreach-headers.md
 delete mode 100644 reference/spfx/web-apis/class/formdata-body.md
 delete mode 100644 reference/spfx/web-apis/class/get-headers.md
 delete mode 100644 reference/spfx/web-apis/class/getall-headers.md
 delete mode 100644 reference/spfx/web-apis/class/has-headers.md
 delete mode 100644 reference/spfx/web-apis/class/headers.md
 delete mode 100644 reference/spfx/web-apis/class/json-body.md
 delete mode 100644 reference/spfx/web-apis/class/promise.md
 delete mode 100644 reference/spfx/web-apis/class/race-promise.md
 delete mode 100644 reference/spfx/web-apis/class/redirect-response.md
 delete mode 100644 reference/spfx/web-apis/class/reject-promise.md
 delete mode 100644 reference/spfx/web-apis/class/request.md
 delete mode 100644 reference/spfx/web-apis/class/resolve-promise.md
 delete mode 100644 reference/spfx/web-apis/class/response.md
 delete mode 100644 reference/spfx/web-apis/class/set-headers.md
 delete mode 100644 reference/spfx/web-apis/class/text-body.md
 delete mode 100644 reference/spfx/web-apis/class/then-promise.md
 delete mode 100644 reference/spfx/web-apis/interface/__index-headersmap.md
 delete mode 100644 reference/spfx/web-apis/interface/fetch-window.md
 delete mode 100644 reference/spfx/web-apis/interface/headersmap.md
 delete mode 100644 reference/spfx/web-apis/interface/requestinit.md
 delete mode 100644 reference/spfx/web-apis/interface/responseinit.md
 delete mode 100644 reference/spfx/web-apis/interface/then-thenable.md
 delete mode 100644 reference/spfx/web-apis/interface/thenable.md
 delete mode 100644 reference/spfx/web-apis/interface/window.md

diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1
new file mode 100644
index 0000000000..aadef76202
--- /dev/null
+++ b/.openpublishing.build.ps1
@@ -0,0 +1,17 @@
+param(
+    [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1",
+    [string]$parameters
+)
+# Main
+$errorActionPreference = 'Stop'
+
+# Step-1: Download buildcore script to local
+echo "download build core script to local with source url: $buildCorePowershellUrl"
+$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition
+$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1"
+Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination"
+
+# Step-2: Run build core
+echo "run build core script with parameters: $parameters"
+& "$buildCorePowershellDestination" "$parameters"
+exit $LASTEXITCODE
diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
new file mode 100644
index 0000000000..37ba77de04
--- /dev/null
+++ b/.openpublishing.publish.config.json
@@ -0,0 +1,54 @@
+{
+  "docsets_to_publish": [
+    {
+      "customized_tasks": {
+        "docset_prebuild": [
+          "_dependentPackages/CommonPlugins/tools/JoinTOC.ps1"        ]
+      },
+      "docset_name": "sharepoint-developer",
+      "build_source_folder": "docs",
+      "build_output_subfolder": "sharepoint-developer",
+      "locale": "en-us",
+      "monikers": [],
+      "moniker_ranges": [],
+      "open_to_public_contributors": false,
+      "type_mapping": {
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
+      },
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
+    }
+  ],
+  "JoinTOCPlugin": [
+    {
+      "ConceptualTOC": "/docs/toc.yml",
+      "ReferenceTOCUrl": "/javascript/api/spfx-toc/toc.json" 
+    }
+  ],
+  "dependent_packages": [
+    {
+      "path_to_root": "_dependentPackages/CommonPlugins", 
+      "target_framework": "net45", 
+      "version": "latest", 
+      "id": "Microsoft.OpenPublishing.CommonPlugins", 
+      "nuget_feed": "https://www.myget.org/F/op/api/v2"
+    }
+  ],
+  "notification_subscribers": [],
+  "branches_to_filter": [],
+  "skip_source_output_uploading": false,
+  "need_preview_pull_request": false,
+  "contribution_branch_mappings": {},
+  "dependent_repositories": [
+    {
+      "path_to_root": "_themes",
+      "url": "https://github.com/Microsoft/templates.docs.msft",
+      "branch": "master",
+      "branch_mapping": {}
+    }
+  ],
+  "branch_target_mapping": {},
+  "need_generate_pdf_url_template": false
+}
\ No newline at end of file
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000000..e056e7c3ec
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,395 @@
+Attribution 4.0 International
+
+=======================================================================
+
+Creative Commons Corporation ("Creative Commons") is not a law firm and
+does not provide legal services or legal advice. Distribution of
+Creative Commons public licenses does not create a lawyer-client or
+other relationship. Creative Commons makes its licenses and related
+information available on an "as-is" basis. Creative Commons gives no
+warranties regarding its licenses, any material licensed under their
+terms and conditions, or any related information. Creative Commons
+disclaims all liability for damages resulting from their use to the
+fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and
+conditions that creators and other rights holders may use to share
+original works of authorship and other material subject to copyright
+and certain other rights specified in the public license below. The
+following considerations are for informational purposes only, are not
+exhaustive, and do not form part of our licenses.
+
+     Considerations for licensors: Our public licenses are
+     intended for use by those authorized to give the public
+     permission to use material in ways otherwise restricted by
+     copyright and certain other rights. Our licenses are
+     irrevocable. Licensors should read and understand the terms
+     and conditions of the license they choose before applying it.
+     Licensors should also secure all rights necessary before
+     applying our licenses so that the public can reuse the
+     material as expected. Licensors should clearly mark any
+     material not subject to the license. This includes other CC-
+     licensed material, or material used under an exception or
+     limitation to copyright. More considerations for licensors:
+	wiki.creativecommons.org/Considerations_for_licensors
+
+     Considerations for the public: By using one of our public
+     licenses, a licensor grants the public permission to use the
+     licensed material under specified terms and conditions. If
+     the licensor's permission is not necessary for any reason--for
+     example, because of any applicable exception or limitation to
+     copyright--then that use is not regulated by the license. Our
+     licenses grant only permissions under copyright and certain
+     other rights that a licensor has authority to grant. Use of
+     the licensed material may still be restricted for other
+     reasons, including because others have copyright or other
+     rights in the material. A licensor may make special requests,
+     such as asking that all changes be marked or described.
+     Although not required by our licenses, you are encouraged to
+     respect those requests where reasonable. More_considerations
+     for the public: 
+	wiki.creativecommons.org/Considerations_for_licensees
+
+=======================================================================
+
+Creative Commons Attribution 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree
+to be bound by the terms and conditions of this Creative Commons
+Attribution 4.0 International Public License ("Public License"). To the
+extent this Public License may be interpreted as a contract, You are
+granted the Licensed Rights in consideration of Your acceptance of
+these terms and conditions, and the Licensor grants You such rights in
+consideration of benefits the Licensor receives from making the
+Licensed Material available under these terms and conditions.
+
+
+Section 1 -- Definitions.
+
+  a. Adapted Material means material subject to Copyright and Similar
+     Rights that is derived from or based upon the Licensed Material
+     and in which the Licensed Material is translated, altered,
+     arranged, transformed, or otherwise modified in a manner requiring
+     permission under the Copyright and Similar Rights held by the
+     Licensor. For purposes of this Public License, where the Licensed
+     Material is a musical work, performance, or sound recording,
+     Adapted Material is always produced where the Licensed Material is
+     synched in timed relation with a moving image.
+
+  b. Adapter's License means the license You apply to Your Copyright
+     and Similar Rights in Your contributions to Adapted Material in
+     accordance with the terms and conditions of this Public License.
+
+  c. Copyright and Similar Rights means copyright and/or similar rights
+     closely related to copyright including, without limitation,
+     performance, broadcast, sound recording, and Sui Generis Database
+     Rights, without regard to how the rights are labeled or
+     categorized. For purposes of this Public License, the rights
+     specified in Section 2(b)(1)-(2) are not Copyright and Similar
+     Rights.
+
+  d. Effective Technological Measures means those measures that, in the
+     absence of proper authority, may not be circumvented under laws
+     fulfilling obligations under Article 11 of the WIPO Copyright
+     Treaty adopted on December 20, 1996, and/or similar international
+     agreements.
+
+  e. Exceptions and Limitations means fair use, fair dealing, and/or
+     any other exception or limitation to Copyright and Similar Rights
+     that applies to Your use of the Licensed Material.
+
+  f. Licensed Material means the artistic or literary work, database,
+     or other material to which the Licensor applied this Public
+     License.
+
+  g. Licensed Rights means the rights granted to You subject to the
+     terms and conditions of this Public License, which are limited to
+     all Copyright and Similar Rights that apply to Your use of the
+     Licensed Material and that the Licensor has authority to license.
+
+  h. Licensor means the individual(s) or entity(ies) granting rights
+     under this Public License.
+
+  i. Share means to provide material to the public by any means or
+     process that requires permission under the Licensed Rights, such
+     as reproduction, public display, public performance, distribution,
+     dissemination, communication, or importation, and to make material
+     available to the public including in ways that members of the
+     public may access the material from a place and at a time
+     individually chosen by them.
+
+  j. Sui Generis Database Rights means rights other than copyright
+     resulting from Directive 96/9/EC of the European Parliament and of
+     the Council of 11 March 1996 on the legal protection of databases,
+     as amended and/or succeeded, as well as other essentially
+     equivalent rights anywhere in the world.
+
+  k. You means the individual or entity exercising the Licensed Rights
+     under this Public License. Your has a corresponding meaning.
+
+
+Section 2 -- Scope.
+
+  a. License grant.
+
+       1. Subject to the terms and conditions of this Public License,
+          the Licensor hereby grants You a worldwide, royalty-free,
+          non-sublicensable, non-exclusive, irrevocable license to
+          exercise the Licensed Rights in the Licensed Material to:
+
+            a. reproduce and Share the Licensed Material, in whole or
+               in part; and
+
+            b. produce, reproduce, and Share Adapted Material.
+
+       2. Exceptions and Limitations. For the avoidance of doubt, where
+          Exceptions and Limitations apply to Your use, this Public
+          License does not apply, and You do not need to comply with
+          its terms and conditions.
+
+       3. Term. The term of this Public License is specified in Section
+          6(a).
+
+       4. Media and formats; technical modifications allowed. The
+          Licensor authorizes You to exercise the Licensed Rights in
+          all media and formats whether now known or hereafter created,
+          and to make technical modifications necessary to do so. The
+          Licensor waives and/or agrees not to assert any right or
+          authority to forbid You from making technical modifications
+          necessary to exercise the Licensed Rights, including
+          technical modifications necessary to circumvent Effective
+          Technological Measures. For purposes of this Public License,
+          simply making modifications authorized by this Section 2(a)
+          (4) never produces Adapted Material.
+
+       5. Downstream recipients.
+
+            a. Offer from the Licensor -- Licensed Material. Every
+               recipient of the Licensed Material automatically
+               receives an offer from the Licensor to exercise the
+               Licensed Rights under the terms and conditions of this
+               Public License.
+
+            b. No downstream restrictions. You may not offer or impose
+               any additional or different terms or conditions on, or
+               apply any Effective Technological Measures to, the
+               Licensed Material if doing so restricts exercise of the
+               Licensed Rights by any recipient of the Licensed
+               Material.
+
+       6. No endorsement. Nothing in this Public License constitutes or
+          may be construed as permission to assert or imply that You
+          are, or that Your use of the Licensed Material is, connected
+          with, or sponsored, endorsed, or granted official status by,
+          the Licensor or others designated to receive attribution as
+          provided in Section 3(a)(1)(A)(i).
+
+  b. Other rights.
+
+       1. Moral rights, such as the right of integrity, are not
+          licensed under this Public License, nor are publicity,
+          privacy, and/or other similar personality rights; however, to
+          the extent possible, the Licensor waives and/or agrees not to
+          assert any such rights held by the Licensor to the limited
+          extent necessary to allow You to exercise the Licensed
+          Rights, but not otherwise.
+
+       2. Patent and trademark rights are not licensed under this
+          Public License.
+
+       3. To the extent possible, the Licensor waives any right to
+          collect royalties from You for the exercise of the Licensed
+          Rights, whether directly or through a collecting society
+          under any voluntary or waivable statutory or compulsory
+          licensing scheme. In all other cases the Licensor expressly
+          reserves any right to collect such royalties.
+
+
+Section 3 -- License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the
+following conditions.
+
+  a. Attribution.
+
+       1. If You Share the Licensed Material (including in modified
+          form), You must:
+
+            a. retain the following if it is supplied by the Licensor
+               with the Licensed Material:
+
+                 i. identification of the creator(s) of the Licensed
+                    Material and any others designated to receive
+                    attribution, in any reasonable manner requested by
+                    the Licensor (including by pseudonym if
+                    designated);
+
+                ii. a copyright notice;
+
+               iii. a notice that refers to this Public License;
+
+                iv. a notice that refers to the disclaimer of
+                    warranties;
+
+                 v. a URI or hyperlink to the Licensed Material to the
+                    extent reasonably practicable;
+
+            b. indicate if You modified the Licensed Material and
+               retain an indication of any previous modifications; and
+
+            c. indicate the Licensed Material is licensed under this
+               Public License, and include the text of, or the URI or
+               hyperlink to, this Public License.
+
+       2. You may satisfy the conditions in Section 3(a)(1) in any
+          reasonable manner based on the medium, means, and context in
+          which You Share the Licensed Material. For example, it may be
+          reasonable to satisfy the conditions by providing a URI or
+          hyperlink to a resource that includes the required
+          information.
+
+       3. If requested by the Licensor, You must remove any of the
+          information required by Section 3(a)(1)(A) to the extent
+          reasonably practicable.
+
+       4. If You Share Adapted Material You produce, the Adapter's
+          License You apply must not prevent recipients of the Adapted
+          Material from complying with this Public License.
+
+
+Section 4 -- Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that
+apply to Your use of the Licensed Material:
+
+  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
+     to extract, reuse, reproduce, and Share all or a substantial
+     portion of the contents of the database;
+
+  b. if You include all or a substantial portion of the database
+     contents in a database in which You have Sui Generis Database
+     Rights, then the database in which You have Sui Generis Database
+     Rights (but not its individual contents) is Adapted Material; and
+
+  c. You must comply with the conditions in Section 3(a) if You Share
+     all or a substantial portion of the contents of the database.
+
+For the avoidance of doubt, this Section 4 supplements and does not
+replace Your obligations under this Public License where the Licensed
+Rights include other Copyright and Similar Rights.
+
+
+Section 5 -- Disclaimer of Warranties and Limitation of Liability.
+
+  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
+     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
+     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
+     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
+     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
+     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
+     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
+     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
+     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
+     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
+
+  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
+     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
+     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
+     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
+     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
+     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
+     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
+     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
+     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
+
+  c. The disclaimer of warranties and limitation of liability provided
+     above shall be interpreted in a manner that, to the extent
+     possible, most closely approximates an absolute disclaimer and
+     waiver of all liability.
+
+
+Section 6 -- Term and Termination.
+
+  a. This Public License applies for the term of the Copyright and
+     Similar Rights licensed here. However, if You fail to comply with
+     this Public License, then Your rights under this Public License
+     terminate automatically.
+
+  b. Where Your right to use the Licensed Material has terminated under
+     Section 6(a), it reinstates:
+
+       1. automatically as of the date the violation is cured, provided
+          it is cured within 30 days of Your discovery of the
+          violation; or
+
+       2. upon express reinstatement by the Licensor.
+
+     For the avoidance of doubt, this Section 6(b) does not affect any
+     right the Licensor may have to seek remedies for Your violations
+     of this Public License.
+
+  c. For the avoidance of doubt, the Licensor may also offer the
+     Licensed Material under separate terms or conditions or stop
+     distributing the Licensed Material at any time; however, doing so
+     will not terminate this Public License.
+
+  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
+     License.
+
+
+Section 7 -- Other Terms and Conditions.
+
+  a. The Licensor shall not be bound by any additional or different
+     terms or conditions communicated by You unless expressly agreed.
+
+  b. Any arrangements, understandings, or agreements regarding the
+     Licensed Material not stated herein are separate from and
+     independent of the terms and conditions of this Public License.
+
+
+Section 8 -- Interpretation.
+
+  a. For the avoidance of doubt, this Public License does not, and
+     shall not be interpreted to, reduce, limit, restrict, or impose
+     conditions on any use of the Licensed Material that could lawfully
+     be made without permission under this Public License.
+
+  b. To the extent possible, if any provision of this Public License is
+     deemed unenforceable, it shall be automatically reformed to the
+     minimum extent necessary to make it enforceable. If the provision
+     cannot be reformed, it shall be severed from this Public License
+     without affecting the enforceability of the remaining terms and
+     conditions.
+
+  c. No term or condition of this Public License will be waived and no
+     failure to comply consented to unless expressly agreed to by the
+     Licensor.
+
+  d. Nothing in this Public License constitutes or may be interpreted
+     as a limitation upon, or waiver of, any privileges and immunities
+     that apply to the Licensor or You, including from the legal
+     processes of any jurisdiction or authority.
+
+
+=======================================================================
+
+Creative Commons is not a party to its public
+licenses. Notwithstanding, Creative Commons may elect to apply one of
+its public licenses to material it publishes and in those instances
+will be considered the “Licensor.” The text of the Creative Commons
+public licenses is dedicated to the public domain under the CC0 Public
+Domain Dedication. Except for the limited purpose of indicating that
+material is shared under a Creative Commons public license or as
+otherwise permitted by the Creative Commons policies published at
+creativecommons.org/policies, Creative Commons does not authorize the
+use of the trademark "Creative Commons" or any other trademark or logo
+of Creative Commons without its prior written consent including,
+without limitation, in connection with any unauthorized modifications
+to any of its public licenses or any other arrangements,
+understandings, or agreements concerning use of licensed material. For
+the avoidance of doubt, this paragraph does not form part of the
+public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
\ No newline at end of file
diff --git a/LICENSE-CODE b/LICENSE-CODE
new file mode 100644
index 0000000000..b17b032a43
--- /dev/null
+++ b/LICENSE-CODE
@@ -0,0 +1,17 @@
+The MIT License (MIT)
+Copyright (c) Microsoft Corporation
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and 
+associated documentation files (the "Software"), to deal in the Software without restriction, 
+including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, 
+and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial 
+portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT 
+NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
\ No newline at end of file
diff --git a/ThirdPartyNotices b/ThirdPartyNotices
new file mode 100644
index 0000000000..a0bd09d68f
--- /dev/null
+++ b/ThirdPartyNotices
@@ -0,0 +1,15 @@
+##Legal Notices
+Microsoft and any contributors grant you a license to the Microsoft documentation and other content
+in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode),
+see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the
+[LICENSE-CODE](LICENSE-CODE) file.
+
+Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
+may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
+The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
+Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
+
+Privacy information can be found at https://privacy.microsoft.com/en-us/
+
+Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents,
+or trademarks, whether by implication, estoppel or otherwise.
\ No newline at end of file
diff --git a/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md b/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md
index 747abe5ea8..e1a944a602 100644
--- a/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md
+++ b/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md
@@ -1,3 +1,10 @@
+---
+title: Complete basic operations using SharePoint REST endpoints
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Complete basic operations using SharePoint REST endpoints
 Learn how to perform basic create, read, update, and delete (CRUD) operations with the SharePoint REST interface.
 
@@ -5,7 +12,7 @@ Learn how to perform basic create, read, update, and delete (CRUD) operations wi
 <a name="ClientAPIs"> </a>
 You can perform basic create, read, update, and delete (CRUD) operations by using the Representational State Transfer (REST) interface provided by SharePoint. The REST interface exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don't have to add references to any SharePoint libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. See  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md) for a thorough introduction to the SharePoint REST interface and its architecture.
  
-[Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md) and [Working with folders and files with REST](working-with-folders-and-files-with-rest.md) explain in greater detail how to work with core SharePoint entities. See [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations) for a sample that shows you how to do many of these operations in the context of an ASP.NET web application written in C#.
+[Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md) and [Working with folders and files with REST](working-with-folders-and-files-with-rest.md) explain in greater detail how to work with core SharePoint entities. See [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations.md) for a sample that shows you how to do many of these operations in the context of an ASP.NET web application written in C#.
  
 For more details about the sets of APIs available on the SharePoint platform, see  [Choose the right API set in SharePoint](http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d%28Office.15%29.aspx). For information about how to use the other client APIs, see  [Complete basic operations using JavaScript library code in SharePoint](https://msdn.microsoft.com/en-us/library/office/jj163201.aspx),  [Complete basic operations using SharePoint 2013 client library code](https://msdn.microsoft.com/en-us/library/office/fp179912.aspx), and  [Build Windows Phone apps that access SharePoint 2013](https://msdn.microsoft.com/en-us/library/office/jj163228.aspx).
  
@@ -325,4 +332,4 @@ The SharePoint Online (and on-premise SharePoint 2016 and later) REST service su
 -  [Work with external data in SharePoint 2013](https://msdn.microsoft.com/en-us/library/office/fp179893.aspx)
 -  [Open Data Protocol](http://www.odata.org/)
 -  [OData: JavaScript Object Notation (JSON) Format](http://www.odata.org/documentation/odata-version-2-0/JSON-format/)
--  [Set custom permissions on a list by using the REST interface](set-custom-permissions-on-a-list-by-using-the-rest-interface.md)
\ No newline at end of file
+-  [Set custom permissions on a list by using the REST interface](set-custom-permissions-on-a-list-by-using-the-rest-interface.md)
diff --git a/docs/apis/rest/determine-sharepoint-rest-service-endpoint-uris.md b/docs/apis/rest/determine-sharepoint-rest-service-endpoint-uris.md
index 44a05206b3..6a902ff589 100644
--- a/docs/apis/rest/determine-sharepoint-rest-service-endpoint-uris.md
+++ b/docs/apis/rest/determine-sharepoint-rest-service-endpoint-uris.md
@@ -1,3 +1,10 @@
+---
+title: Determine SharePoint REST service endpoint URIs
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Determine SharePoint REST service endpoint URIs
 Learn general guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.
  
@@ -29,7 +36,7 @@ In some cases, however, the endpoint URI differs from the corresponding client o
 The following figure shows the general syntax structure of SharePoint REST URIs. 
 
 **SharePoint REST URI syntax structure**
-![SharePoint REST request syntax](../../../images/REST_OverallSyntax.png)
+![SharePoint REST request syntax](../../images/REST_OverallSyntax.png)
  
 Some endpoints for SharePoint resources deviate from this syntax structure:
 
@@ -111,7 +118,7 @@ To specify multiple parameters, include the parameter as a name-value pair, and
 The following figure shows the SharePoint REST parameter syntax.
  
 **SharePoint REST parameter syntax**
-![SharePoint REST service method parameter syntax](../../../images/REST_parameterSyntax.png)
+![SharePoint REST service method parameter syntax](../../images/REST_parameterSyntax.png)
 
 ### Complex types as parameters for the REST service
 Some methods in the client object model require a large payload as a parameter. For REST endpoints to maintain functionality parity with their corresponding client object model APIs, the endpoints must accept a complex type as a parameter. In these cases, the REST service extends the existing OData protocol to enable these REST endpoints to accept a single complex type as a parameter. This applies to  **POST** operations only, and you have to pass the complex type in [Atom](http://www.odata.org/developers/protocols/atom-format#RepresentingComplexTypesProperties) format or [JSON](http://www.odata.org/developers/protocols/json-format#RepresentingComplexTypeProperties) format, according to OData standards.
@@ -157,13 +164,13 @@ However, the SharePoint REST service does not support passing complex types via
  ```
  
 **SharePoint REST service parameter aliasing syntax**
-![SharePoint REST service parameter aliasing syntax](../../../images/REST_parameterAliasSyntax.png)
+![SharePoint REST service parameter aliasing syntax](../../images/REST_parameterAliasSyntax.png)
 
 ### Specifying dictionaries as parameter values
 For REST endpoints that correspond to methods that take  `Dictionary<String, String>` dictionaries as parameters, pass the dictionary as a series of comma delimited name-value pairs in the query string.
 
 **REST service syntax for Dictionary parameters**
-![REST service syntax for Dictionary parameters](../../../images/REST_parameterDictionarySyntax.png)
+![REST service syntax for Dictionary parameters](../../images/REST_parameterDictionarySyntax.png)
  
 A  `Dictionary<String, object>` is represented as a multi-value object, named KeyedPropertyValue, with the following string properties:
 
@@ -181,7 +188,7 @@ If your REST URI terminates in a method call, you can use query string syntax to
 the figure below shows the REST service syntax for parameters in query string. 
 
 **REST service syntax for parameters in query string**
-![REST service syntax for parameters in query string](../../../images/REST_parameterQuerySyntax.png)
+![REST service syntax for parameters in query string](../../images/REST_parameterQuerySyntax.png)
  
 ## Specifying static methods and properties as REST service URIs
 To construct URIs that correspond to static methods or properties, use the corresponding API name from the ECMAScript object model, starting with the namespace declaration and using dot notation. For example,  [SP.Utilities.Utility.getImageUrl(imageName)](http://msdn.microsoft.com/en-us/library/ee658947.aspx) in the ECMAScript client object model would have the following REST equivalent:
@@ -199,7 +206,7 @@ However, using that resource location as a parameter for a more complex URI, as
 The figure below shows the SharePoint REST service static member syntax.
 
 **SharePoint REST service static member syntax**
-![REST service syntax for parameters in query string](../../../images/REST_parameterQuerySyntax.png)
+![REST service syntax for parameters in query string](../../images/REST_parameterQuerySyntax.png)
 
 ## Next steps
 If you want to select, filter, or order the data you requested from an endpoint, the SharePoint REST service supports a wide range of OData query string operators. 
@@ -216,4 +223,4 @@ If you want to select, filter, or order the data you requested from an endpoint,
 -  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
 -  [REST API reference and samples](http://msdn.microsoft.com/library/02128c70-9d27-4388-9374-a11bce68fdb8%28Office.15%29.aspx)
 -  [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service.md)
--  [Use ETag values through the REST service to get document list item versioning](http://msdn.microsoft.com/library/use-etag-values-through-the-rest-service-to-get-document-list-item-versioning%28Office.15%29.aspx)
\ No newline at end of file
+-  [Use ETag values through the REST service to get document list item versioning](http://msdn.microsoft.com/library/use-etag-values-through-the-rest-service-to-get-document-list-item-versioning%28Office.15%29.aspx)
diff --git a/docs/apis/rest/get-to-know-the-sharepoint-rest-service.md b/docs/apis/rest/get-to-know-the-sharepoint-rest-service.md
index 298917c6ac..2a22c1e63e 100644
--- a/docs/apis/rest/get-to-know-the-sharepoint-rest-service.md
+++ b/docs/apis/rest/get-to-know-the-sharepoint-rest-service.md
@@ -1,3 +1,10 @@
+---
+title: Get to know the SharePoint REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get to know the SharePoint REST service
 Get the basics of using the SharePoint REST service to access and update SharePoint data, using the REST and OData web protocol standards.
 
@@ -28,7 +35,7 @@ The client.svc web service in SharePoint handles the HTTP request, and serves th
  
 **SharePoint REST service architecture**
 
-![SharePoint REST service architecture](../../../images/REST_RESTStructure.png)
+![SharePoint REST service architecture](../../images/REST_RESTStructure.png)
  
 Because of the functionality and ease of use that client object models provide, they remain the primary development option for communicating with SharePoint sites by using .NET Framework managed code, Silverlight, or JavaScript.
  
diff --git a/docs/apis/rest/make-batch-requests-with-the-rest-apis.md b/docs/apis/rest/make-batch-requests-with-the-rest-apis.md
index 217e3bf2c5..bacef3696c 100644
--- a/docs/apis/rest/make-batch-requests-with-the-rest-apis.md
+++ b/docs/apis/rest/make-batch-requests-with-the-rest-apis.md
@@ -1,3 +1,10 @@
+---
+title: Make batch requests with the REST APIs
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Make batch requests with the REST APIs
 Learn how to use the  `$batch` query option with the REST/OData APIs.
  
diff --git a/docs/apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md b/docs/apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
index 684507d4ff..44e59acbf6 100644
--- a/docs/apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
+++ b/docs/apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
@@ -1,3 +1,10 @@
+---
+title: Navigate the SharePoint data structure represented in the REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Navigate the SharePoint data structure represented in the REST service
 Learn how to start from a REST endpoint for a given SharePoint item, and navigate to and access related items, such as parent sites or the library structure where that item resides. 
  
diff --git a/docs/apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface.md b/docs/apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
index a54604920f..9e398d7d8c 100644
--- a/docs/apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
+++ b/docs/apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
@@ -1,3 +1,10 @@
+---
+title: Set custom permissions on a list by using the REST interface
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Set custom permissions on a list by using the REST interface
 Learn how to define custom, fine-grained permissions on a SharePoint list by using the REST interface and JavaScript.
 
@@ -32,7 +39,7 @@ You'll also need to set  **Full Control** add-in permissions at the **Web** scop
 
 The following examples represent the contents of the App.js file in a SharePoint-hosted add-in. The first example uses the JavaScript cross-domain library to build and send HTTP requests. The second example uses jQuery AJAX requests.
  
-Before you run the code, replace the placeholder values with actual values. If you're using a different language or environment, you'll need to add or change some request components. See  [How REST requests differ by environment](complete-basic-operations-using-sharepoint-2013-rest-endpoints.md#bk_HowRequestsDiffer) for more information.
+Before you run the code, replace the placeholder values with actual values. If you're using a different language or environment, you'll need to add or change some request components. See  [How REST requests differ by environment](complete-basic-operations-using-sharepoint-rest-endpoints.md#bk_HowRequestsDiffer) for more information.
  
  **Example 1: Cross-domain library requests**
  
diff --git a/docs/apis/rest/synchronize-sharepoint-items-using-the-rest-service.md b/docs/apis/rest/synchronize-sharepoint-items-using-the-rest-service.md
index 084898d1d6..cd20b2b983 100644
--- a/docs/apis/rest/synchronize-sharepoint-items-using-the-rest-service.md
+++ b/docs/apis/rest/synchronize-sharepoint-items-using-the-rest-service.md
@@ -1,3 +1,10 @@
+---
+title: Synchronize SharePoint items using the REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Synchronize SharePoint items using the REST service
 Learn how to synchronize items between SharePoint and your add-ins or services by using the  **GetListItemChangesSinceToken** resource, part of the SharePoint REST service.
 
diff --git a/docs/apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md b/docs/apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md
index da52677192..1af537994b 100644
--- a/docs/apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md
+++ b/docs/apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md
@@ -1,3 +1,10 @@
+---
+title: Upload a file by using the REST API and jQuery
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Upload a file by using the REST API and jQuery
 Learn how to upload a local file to a SharePoint folder by using the REST API and jQuery AJAX requests.
  
@@ -363,4 +370,4 @@ function onError(error) {
 -  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
 -  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
 -  [REST API reference and samples](http://msdn.microsoft.com/library/02128c70-9d27-4388-9374-a11bce68fdb8%28Office.15%29.aspx)
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library.md)
\ No newline at end of file
+-  [Access SharePoint data from add-ins using the cross-domain library](../../sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
\ No newline at end of file
diff --git a/docs/apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md b/docs/apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md
index 7c64a56826..bb0e0617c6 100644
--- a/docs/apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md
+++ b/docs/apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md
@@ -1,3 +1,10 @@
+---
+title: Use OData query operations in SharePoint REST requests
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use OData query operations in SharePoint REST requests
 Learn how to use a wide range of OData query string operators to select, filter, and order the data you request from the SharePoint REST service. 
  
@@ -65,7 +72,7 @@ The figure below shows the supported OData query options.
  
 **Supported OData query options**
 
-![SharePoint REST service query option syntax](../../../images/REST_queryOptionSyntax.png)
+![SharePoint REST service query option syntax](../../images/REST_queryOptionSyntax.png)
 
 ## Additional resources
 <a name="bk_addresources"> </a>
diff --git a/docs/apis/rest/working-with-folders-and-files-with-rest.md b/docs/apis/rest/working-with-folders-and-files-with-rest.md
index a29ec8f1c6..06044d53f3 100644
--- a/docs/apis/rest/working-with-folders-and-files-with-rest.md
+++ b/docs/apis/rest/working-with-folders-and-files-with-rest.md
@@ -1,3 +1,10 @@
+---
+title: Working with folders and files with REST
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Working with folders and files with REST
 Learn how to perform basic create, read, update, and delete (CRUD) operations on folders and files with the SharePoint 2013 REST interface.
 
@@ -161,7 +168,7 @@ headers:
 
 ## Working with large files by using REST
 <a name="LargeFiles"> </a>
-When you need to upload a binary file that is larger than 1.5 megabytes (MB), the REST interface is your only option. See  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013.md) for a code example that shows you how to upload a binary file that is smaller than 1.5 MB by using the SharePoint Javascript object model. The maximum size of a binary file that you can create with REST is 2 gigabytes (GB). The following example shows how to **create** a large binary file.
+When you need to upload a binary file that is larger than 1.5 megabytes (MB), the REST interface is your only option. See  [Complete basic operations using JavaScript library code in SharePoint](../../sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md) for a code example that shows you how to upload a binary file that is smaller than 1.5 MB by using the SharePoint Javascript object model. The maximum size of a binary file that you can create with REST is 2 gigabytes (GB). The following example shows how to **create** a large binary file.
  
  **Caution**  This approach will work only with Internet Explorer 10 and the latest versions of other browsers.
  
@@ -256,7 +263,7 @@ headers:
 ## Additional resources
 <a name="bk_addresources"> </a>
 
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
+-  [Complete basic operations using SharePoint REST endpoints](../../sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md)
 -  [Files and folders REST API reference](http://msdn.microsoft.com/library/2c3d2545-1cd7-497e-b535-12199d8edfbb%28Office.15%29.aspx)
 -  [Upload a file by using the REST API and jQuery](upload-a-file-by-using-the-rest-api-and-jquery.md)
 -  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
@@ -264,10 +271,10 @@ headers:
 -  [SharePoint 2013: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-2013-Perform-ab9c4ae5)
 -  [Making REST calls with C# and JavaScript for SharePoint 2013](http://www.microsoft.com/resources/msdn/en-us/office/media/video/video.mdl?cid=sdc&amp;from=mscomsdc&amp;VideoID=4e4cc094-ff69-405b-852f-2ac7c41293c5)
 -  [Making REST calls with C# and JavaScript for SharePoint 2013 demo](http://www.microsoft.com/resources/msdn/en-us/office/media/video/video.mdl?cid=sdc&amp;from=mscomsdc&amp;VideoID=b1e7c9c5-0f62-4a78-bb7b-8e283c86145c)
--  [Complete basic operations using SharePoint 2013 client library code](complete-basic-operations-using-sharepoint-2013-client-library-code.md)
--  [Complete basic operations using JavaScript library code in SharePoint 2013](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013.md)
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
--  [Work with external data in SharePoint 2013](work-with-external-data-in-sharepoint-2013.md)
+-  [Complete basic operations using SharePoint 2013 client library code](../../sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md)
+-  [Complete basic operations using JavaScript library code in SharePoint 2013](../../sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
+-  [Develop SharePoint Add-ins](../../sp-add-ins/develop-sharepoint-add-ins.md)
+-  [Secure data access and client object models for SharePoint Add-ins](../../sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
+-  [Work with external data in SharePoint 2013](../../sp-add-ins/work-with-external-data-in-sharepoint.md)
 -  [Open Data Protocol](http://www.odata.org/)
 -  [OData: JavaScript Object Notation (JSON) Format](http://www.odata.org/documentation/odata-version-2-0/JSON-format/)
diff --git a/docs/apis/rest/working-with-lists-and-list-items-with-rest.md b/docs/apis/rest/working-with-lists-and-list-items-with-rest.md
index 397f6c71a0..41de847b3f 100644
--- a/docs/apis/rest/working-with-lists-and-list-items-with-rest.md
+++ b/docs/apis/rest/working-with-lists-and-list-items-with-rest.md
@@ -1,3 +1,10 @@
+---
+title: Working with lists and list items with REST
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Working with lists and list items with REST
 Learn how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the SharePoint REST interface.
  
diff --git a/docs/apis/webhooks/get-started-webhooks.md b/docs/apis/webhooks/get-started-webhooks.md
index 9fe813633f..c91dad4869 100644
--- a/docs/apis/webhooks/get-started-webhooks.md
+++ b/docs/apis/webhooks/get-started-webhooks.md
@@ -1,3 +1,10 @@
+---
+title: Get started with SharePoint webhooks
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get started with SharePoint webhooks
 
 This article describes how to build an application that adds and handles SharePoint webhook requests. You will learn how to use [Postman client](https://www.getpostman.com/) to construct and execute SharePoint webhook requests quickly while interacting with a simple ASP.NET Web API as the webhook receiver.
@@ -305,7 +312,7 @@ Postman makes it really simple to work with APIs. The first step is to configure
 * Select the option to **Add token to header**.
 * Double-click the **access\_token** variable to add the token to the header for the request.
 
-![Postman get new access token](../../../images/postman-get-new-access-token.png)
+![Postman get new access token](../../images/postman-get-new-access-token.png)
 
 ### Get Documents list Id
 
@@ -354,7 +361,7 @@ Now that you have the required information, construct the query and the request
 	}
 	```
 
-	![postman add webhook body](../../../images/postman-add-webhook-body.png)
+	![postman add webhook body](../../images/postman-add-webhook-body.png)
 
 > Make sure the **expirationDateTime** is at most 6 months from today. 
 
@@ -471,4 +478,4 @@ With this data, you can construct the URL and use the [GetChanges](https://msdn.
 
 In this article, you used Postman client and a simple web API to subscribe and receive webhook notifications from SharePoint.
 
-Next, take a look at [SharePoint webhooks sample reference implementation](./webhooks-reference-implementation), which shows an end-to-end sample that uses Azure Storage Queues to process the information, get changes from SharePoint, and push those changes back into a SharePoint list.
+Next, take a look at [SharePoint webhooks sample reference implementation](./webhooks-reference-implementation.md), which shows an end-to-end sample that uses Azure Storage Queues to process the information, get changes from SharePoint, and push those changes back into a SharePoint list.
diff --git a/docs/apis/webhooks/lists/create-subscription.md b/docs/apis/webhooks/lists/create-subscription.md
index 8c2003ee4b..66bf650743 100644
--- a/docs/apis/webhooks/lists/create-subscription.md
+++ b/docs/apis/webhooks/lists/create-subscription.md
@@ -1,3 +1,10 @@
+---
+title: Create a new subscription 
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a new subscription 
 
 Creates a new webhook subscription on a SharePoint list. 
@@ -77,4 +84,4 @@ Content-Type: application/json
 
 Before a new subscription is created, SharePoint will send a request with a validation token in the body of the request to the service URL provided. Your service must respond to this request by returning the validation token.
 
-If your service fails to validate the request in this way, the subscription will not be created. See [Overview of SharePoint webhooks](../overview-sharepoint-webhooks) for more information.
+If your service fails to validate the request in this way, the subscription will not be created. See [Overview of SharePoint webhooks](../overview-sharepoint-webhooks.md) for more information.
diff --git a/docs/apis/webhooks/lists/delete-subscription.md b/docs/apis/webhooks/lists/delete-subscription.md
index cf43bc55ac..8e8360dae1 100644
--- a/docs/apis/webhooks/lists/delete-subscription.md
+++ b/docs/apis/webhooks/lists/delete-subscription.md
@@ -1,3 +1,10 @@
+---
+title: Delete a subscription
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Delete a subscription
 
 Deletes a webhook subscription from a SharePoint list. After deleting the subscription notifications will no longer be delivered.
diff --git a/docs/apis/webhooks/lists/get-subscription.md b/docs/apis/webhooks/lists/get-subscription.md
index 0d43ee9d73..f60e31eb23 100644
--- a/docs/apis/webhooks/lists/get-subscription.md
+++ b/docs/apis/webhooks/lists/get-subscription.md
@@ -1,3 +1,10 @@
+---
+title: Get subscriptions
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get subscriptions
 
 Gets one or more webhook subscriptions on a SharePoint list.
diff --git a/docs/apis/webhooks/lists/overview-sharepoint-list-webhooks.md b/docs/apis/webhooks/lists/overview-sharepoint-list-webhooks.md
index 4c239d8d79..e5d06486ff 100644
--- a/docs/apis/webhooks/lists/overview-sharepoint-list-webhooks.md
+++ b/docs/apis/webhooks/lists/overview-sharepoint-list-webhooks.md
@@ -1,3 +1,10 @@
+---
+title: SharePoint list webhooks
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint list webhooks
 
 The SharePoint list webhooks cover the events corresponding to list item changes for a given SharePoint list or a document library. SharePoint webhooks provide a simple notification pipeline so your application can be aware of changes to a SharePoint list without polling the service.
@@ -5,10 +12,10 @@ The SharePoint list webhooks cover the events corresponding to list item changes
 ## Tasks
 | Task                                                | HTTP method                                                  |
 |-----------------------------------------------------|--------------------------------------------------------------|
-| [Create a new subscription](./create-subscription) | `POST    /_api/web/lists('list-guid')/subscriptions`         |
-| [Get subscriptions](./get-subscription)          | `GET     /_api/web/lists('list-guid')/subscriptions`         |
-| [Delete a subscription](./delete-subscription)       | `DELETE  /_api/web/lists('list-guid')/subscriptions('id')`   |
-| [Update a subscription](./update-subscription)     | `PATCH   /_api/web/lists('list-guid')/subscriptions('id')`   |
+| [Create a new subscription](./create-subscription.md) | `POST    /_api/web/lists('list-guid')/subscriptions`         |
+| [Get subscriptions](./get-subscription.md)          | `GET     /_api/web/lists('list-guid')/subscriptions`         |
+| [Delete a subscription](./delete-subscription.md)       | `DELETE  /_api/web/lists('list-guid')/subscriptions('id')`   |
+| [Update a subscription](./update-subscription.md)     | `PATCH   /_api/web/lists('list-guid')/subscriptions('id')`   |
 
 ## List event types
 Notifications will be sent to your application for the following asynchronous list item events in SharePoint:
@@ -29,4 +36,4 @@ Synchronous events are not supported in webhooks.
 
 ## Additional resources
 
-* [Overview of SharePoint webhooks](../overview-sharepoint-webhooks)
+* [Overview of SharePoint webhooks](../overview-sharepoint-webhooks.md)
diff --git a/docs/apis/webhooks/lists/update-subscription.md b/docs/apis/webhooks/lists/update-subscription.md
index 198f161bf7..2f352d3547 100644
--- a/docs/apis/webhooks/lists/update-subscription.md
+++ b/docs/apis/webhooks/lists/update-subscription.md
@@ -1,3 +1,10 @@
+---
+title: Update a subscription
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Update a subscription
 
 Updates a webhook subscription on a SharePoint list.
diff --git a/docs/apis/webhooks/overview-sharepoint-webhooks.md b/docs/apis/webhooks/overview-sharepoint-webhooks.md
index 54339844dd..162227fa57 100644
--- a/docs/apis/webhooks/overview-sharepoint-webhooks.md
+++ b/docs/apis/webhooks/overview-sharepoint-webhooks.md
@@ -1,8 +1,15 @@
+---
+title: Overview of SharePoint webhooks
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Overview of SharePoint webhooks
 
 SharePoint [webhooks](http://en.wikipedia.org/wiki/Webhook) enable developers to build applications that subscribe to receive notifications on specific events that occur in SharePoint. When an event is triggered, SharePoint sends an HTTP POST payload to the subscriber. Webhooks are easier to develop and consume than Windows Communication Foundation (WCF) services used by SharePoint add-in remote event receivers. This is because webhooks are regular HTTP services (web API).
 
-Currently webhooks are only enabled for SharePoint list items. SharePoint list item webhooks cover the events corresponding to list item changes for a given SharePoint list or a document library. SharePoint webhooks provide a simple notification pipeline so your application can be aware of changes to a SharePoint list without polling the service. For more information see [SharePoint list webhooks](./lists/overview-sharepoint-list-webhooks). 
+Currently webhooks are only enabled for SharePoint list items. SharePoint list item webhooks cover the events corresponding to list item changes for a given SharePoint list or a document library. SharePoint webhooks provide a simple notification pipeline so your application can be aware of changes to a SharePoint list without polling the service. For more information see [SharePoint list webhooks](./lists/overview-sharepoint-list-webhooks.md). 
 
 ## Creating webhooks
 To create a new SharePoint webhook, you add a new subscription to the specific SharePoint resource, such as a SharePoint list. 
@@ -135,4 +142,4 @@ You need to set an expiration date when creating the subscription. The expiratio
 
 ## Retry mechanism
 
-If an event occurs in SharePoint and your service endpoint is not reachable (e.g., due to maintenance) SharePoint will retry sending the notification. SharePoint performs a retry of **5 times with a 5 minute wait time** between the attempts. If for some reason your service is down for a longer time, the next time when it's up and gets called by SharePoint, the call to the `GetChanges()` will recover the changes that were missed when your service was not available.
\ No newline at end of file
+If an event occurs in SharePoint and your service endpoint is not reachable (e.g., due to maintenance) SharePoint will retry sending the notification. SharePoint performs a retry of **5 times with a 5 minute wait time** between the attempts. If for some reason your service is down for a longer time, the next time when it's up and gets called by SharePoint, the call to the `GetChanges()` will recover the changes that were missed when your service was not available.
diff --git a/docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md b/docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md
index 4053213532..bfcc4d85b5 100644
--- a/docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md
+++ b/docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md
@@ -1,33 +1,40 @@
-# Using Azure Functions with SharePoint webhooks #
+---
+title: Using Azure Functions with SharePoint webhooks
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
+# Using Azure Functions with SharePoint webhooks
 [Azure functions](https://docs.microsoft.com/en-us/azure/azure-functions/functions-overview) offer an easy way to host your SharePoint webhooks: you can simply add your webhook C# or Javascript code via the browser and Azure will take care of the hosting and scaling of your function! This guide shows how to setup and use Azure Functions for your webhooks.
 
 ## Create a an Azure Function App
 The first step you'll need to do is creating an Azure Function App, which is a special kind of Azure Web App focused on hosting Azure Functions. Navigate to [https://portal.azure.com](https://portal.azure.com), click on the "New" and search for "Function app":
 
-![Creating an Azure Function App](../../../images/webhook-azure-function0.png)
+![Creating an Azure Function App](../../images/webhook-azure-function0.png)
 
 Select "Function App" and complete the information needed to create the Function App:
 
-![Complte Azure Function App details](../../../images/webhook-azure-function1.png)
+![Complte Azure Function App details](../../images/webhook-azure-function1.png)
 
 ## Create an Azure Function
 Now that the app to host the functions is ready you can continue with creating your first Azure Function by clicking on the "New Function" link:
 
-![Adding an Azure Function](../../../images/webhook-azure-function2.png)
+![Adding an Azure Function](../../images/webhook-azure-function2.png)
 
 This will offer you to start your function from a template, in the case of SharePoint webhooks we will need a HTTP triggered function and since we'll be writing C# code in our sample this means we're using the **HttpTrigger-CSharp** function template. Given that SharePoint webhook services need to be anonymously callable it's important to switch the **Authorization level** to **Anonymous**.
 
-![Choosing an Azure Function template](../../../images/webhook-azure-function3.png)
+![Choosing an Azure Function template](../../images/webhook-azure-function3.png)
 
 >**Note:**
 > - Using the **GenericWebHook** template currently does not yet work for SharePoint webhooks but the SharePoint product team is aware of this problem and will address it.
 > - If you get "Failed to validate the notification URL" errors when using your Azure function based webhook you might be able to resolve this by setting the Authorization level to **Function** and define your function for anonymous access
 
 The result will be a "default" Azure Function written in C#
-![The default Azure Function](../../../images/webhook-azure-function4.png)
+![The default Azure Function](../../images/webhook-azure-function4.png)
 
 In our case we want this Azure Function to behave as a SharePoint webhook service, so we'll need to implement the following in C#:
-- Return the validationtoken if specified as URL parameter to the call. This is needed as described [here](./lists/create-subscription) and SharePoint expects the reply to happen within 5 seconds. 
+- Return the validationtoken if specified as URL parameter to the call. This is needed as described [here](./lists/create-subscription.md) and SharePoint expects the reply to happen within 5 seconds. 
 - Process the JSON webhook notification. In below sample we've opted to store the JSON in a storage queue so that an Azure Web Job can pick it up and process it asynchronously. Depending on your needs you could also process the notification directly in your webhook service, but keep in mind that all webhook service calls need to complete in 5 seconds, hence using an asynchronous model is recommended
 
 You can achieve above by replacing the default code by below code (please enter your storage account connection string and update the queue name if you're using a different one):
@@ -147,21 +154,21 @@ public class SubscriptionModel
 ## Configure your Azure Function
 Since we've chosen the correct template to start from our configuration is almost complete, the only thing you need to still do is to switch the **Allowed HTTP methods** to **Selected methods** and then only allow the **POST** HTTP method. Also cross check that **Mode** is equal to **Standard** and **Authorization level** is set to **Anonymous**.
 
-![Azure Function settings](../../../images/webhook-azure-function5.png)
+![Azure Function settings](../../images/webhook-azure-function5.png)
 
 ## Test your Azure Function
 You're now all set for your first Azure Function test: navigate to the **Develop** screen. Click on the **Test** icon to pop-up the test pane at the right side, add a URL parameter "validationtoken" with a random string as value. Using this setup we're mimicking the behavior of SharePoint calling your web hook service when validating a new webhook addition. Click on **Run** to test...if everything goes well you'll see in the logs section that your service was called and that it returned the passed value with a HTTP 200 response:
 
-![Azure Function testing](../../../images/webhook-azure-function6.png)
+![Azure Function testing](../../images/webhook-azure-function6.png)
 
 ## Grab the webhook URL to use in your implementation
 We'll need to let SharePoint now what webhook URL we're using. To so let's start by copying the Azure Function URL:
 
-![Azure Function authorization codes](../../../images/webhook-azure-function8.png)
+![Azure Function authorization codes](../../images/webhook-azure-function8.png)
 
 To avoid unathorized usage of your Azure Function the caller will need to specify a code when calling your function. This code can be retreived via the **Manage** screen:
 
-![Azure Function webhook URL](../../../images/webhook-azure-function7.png)
+![Azure Function webhook URL](../../images/webhook-azure-function7.png)
 
 So in our case the webhook URL to use is the following: `https://pnp-functions.azurewebsites.net/api/spwebhookfunction?code=wyx9iAxp3o7fdGFZTbnp9Kfc5o2UhlzwgSOT/XGGM6QZcdYYa/o9aw==`
 
diff --git a/docs/apis/webhooks/webhooks-reference-implementation.md b/docs/apis/webhooks/webhooks-reference-implementation.md
index 87f7e9eed5..61a439e157 100644
--- a/docs/apis/webhooks/webhooks-reference-implementation.md
+++ b/docs/apis/webhooks/webhooks-reference-implementation.md
@@ -1,15 +1,22 @@
+---
+title: SharePoint webhooks sample reference implementation
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint webhooks sample reference implementation
 
 **Contributor(s)**: Bert Jansen (Microsoft), SharePoint PnP Core Team
 
 The SharePoint Patterns and Practices (PnP) reference implementation shows how you can use SharePoint webhooks in your application. The webhooks are implemented in an enterprise ready manner using various Microsoft Azure components such as Azure Web Jobs, Azure SQL Server, and Azure Storage Queues for asynchronous web job notification handling.
 
-The reference implementation only works with [SharePoint list webhooks](./lists/overview-sharepoint-list-webhooks). 
+The reference implementation only works with [SharePoint list webhooks](./lists/overview-sharepoint-list-webhooks.md). 
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=j3hWCAI9R20).
 
 <a href="https://www.youtube.com/watch?v=j3hWCAI9R20">
-<img src="../../../images/youtube-introducing-sharepoint-webhooks.png" alt="PnP webcast - Introducing SharePoint webhooks" />
+<img src="../../images/youtube-introducing-sharepoint-webhooks.png" alt="PnP webcast - Introducing SharePoint webhooks" />
 </a>
 
 ## Applies to
@@ -28,7 +35,7 @@ Source code and other materials for the reference implementation are available i
 
 The application will show you how to manage webhooks, specifically for a SharePoint list. It also contains a reference implementation of a webhook service endpoint which you can reuse in your webhook projects. 
 
-![SharePoint webhook reference implementation application](../../../images/webhook-sample-application.png)
+![SharePoint webhook reference implementation application](../../images/webhook-sample-application.png)
 
 The [SharePoint web hooks reference implementation - Deployment guide](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/Deployment%20guide.md) lists the deployment steps used to deploy the SharePoint Provider hosted reference implementation. To deploy the Office 365 Azure AD application use the steps described [here](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List.AzureAD/Deployment%20guide.md). The deployment guide shows you how to use a Web API function as webhook service, but if you're more interested in use Azure functions then checkout the [Azure Functions guide](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List.AzureAD/azure%20functions%20guide.md) for more details on how to use Azure Functions in this reference implementation.
 
@@ -38,7 +45,7 @@ Webhooks notify your application about changes in SharePoint that the applicatio
 
 ### Adding a webhook to your SharePoint list
 
-The reference implementation works with a SharePoint list. To add a webhook to a SharePoint list, your application first creates a webhook subscription by sending a [`POST /_api/web/lists('list-id')/subscriptions`](./lists/create-subscription) request. The request includes the following items:
+The reference implementation works with a SharePoint list. To add a webhook to a SharePoint list, your application first creates a webhook subscription by sending a [`POST /_api/web/lists('list-id')/subscriptions`](./lists/create-subscription.md) request. The request includes the following items:
 
 * A payload that identifies the list which you're adding the webhook for.
 * The location of your webhook service URL to send the notifications.
@@ -46,7 +53,7 @@ The reference implementation works with a SharePoint list. To add a webhook to a
 
 After you've requested SharePoint to add your webhook, SharePoint will validate that your webhook service endpoint exists. It sends a validation string to your service endpoint. SharePoint expects that your service endpoint returns the validation string within 5 seconds. If this process fails then the webhook creation is canceled. If you've deployed your service then this will work and SharePoint returns an HTTP 201 message on the POST request the application initially sent. The payload in the response contains the ID of the new webhook subscription.
 
-![Adding a webhook](../../../images/webhook-sample-add-process.png)
+![Adding a webhook](../../images/webhook-sample-add-process.png)
 
 Take a look at the reference implementation, and you'll see that all webhook CRUD operations are consolidated in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Adding a webhook is done using the **AddListWebHookAsync** method:
 
@@ -97,13 +104,13 @@ Property|Description
 
 When your service is called, it's important that your service replies with an HTTP 200 message in under 5 seconds. Later in this article you'll learn more about the response time, but essentially this requires that you **asynchronously** handle the notifications. In this reference implementation you'll do this by using Azure Web Jobs and Azure Storage Queues.
 
-![SharePoint calls your webhook endpoint](../../../images/webhook-sample-call-webhook.png)
+![SharePoint calls your webhook endpoint](../../images/webhook-sample-call-webhook.png)
 
 ### Grab the changes your service needs to act upon
 
 In the previous step your service endpoint was called but SharePoint only provided information about where the change happened, not what was actually changed. To understand what was changed, you'll need to use the SharePoint `GetChanges()` API, as shown in the following image.
 
-![Async GetChanges](../../../images/webhook-sample-async-getchanges.png)
+![Async GetChanges](../../images/webhook-sample-async-getchanges.png)
 
 You can learn more about the `GetChanges()` implementation in the **ProcessNotification** method in the [ChangeManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/ChangeManager.cs) class of the **SharePoint.WebHooks.Common** project. 
 
@@ -118,7 +125,7 @@ The following are some key things to note about changes:
 
 The following diagram describes the complete end-to-end webhook flow:
 
-![Webhooks reference implementation end-to-end flow](../../../images/webhook-sample-end-to-end-flow.png)
+![Webhooks reference implementation end-to-end flow](../../images/webhook-sample-end-to-end-flow.png)
 
 1. Your application creates a webhook subscription. When it does it gets the current **changeToken** from the list it created the webhook for.
 2. Your application persists the **changeToken** in a persistent storage, such as SQL Azure in this case.
@@ -144,7 +151,7 @@ Create a web job that on a weekly basis reads all the subscription IDs from the
 
 > **Note:** This web job is not part of this reference implementation.
 
-The actual renewal of a SharePoint list webhook can be done using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription) REST call. In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Updating a webhook is done using the **UpdateListWebHookAsync** method:
+The actual renewal of a SharePoint list webhook can be done using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription.md) REST call. In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Updating a webhook is done using the **UpdateListWebHookAsync** method:
 
 ```csharp
 /// <summary>
diff --git a/docs/breadcrumb/toc.yml b/docs/breadcrumb/toc.yml
new file mode 100644
index 0000000000..42f0107939
--- /dev/null
+++ b/docs/breadcrumb/toc.yml
@@ -0,0 +1,3 @@
+- name: SharePoint developer
+  tocHref: /sharepoint/dev/
+  topicHref: /sharepoint/dev/index
diff --git a/docs/docfx.json b/docs/docfx.json
new file mode 100644
index 0000000000..33361473a4
--- /dev/null
+++ b/docs/docfx.json
@@ -0,0 +1,55 @@
+{
+  "build": {
+    "content": [
+      {
+        "files": [
+          "**/*.md",
+          "**/**.yml"
+        ],
+        "exclude": [
+          "**/obj/**",
+          "**/includes/**",
+          "README.md",
+          "LICENSE",
+          "LICENSE-CODE",
+          "ThirdPartyNotices"
+        ]
+      }
+    ],
+    "resource": [
+      {
+        "files": [
+          "**/*.png",
+          "**/*.jpg",
+          "**/*.gif"
+        ],
+        "exclude": [
+          "**/obj/**",
+          "**/includes/**"
+        ]
+      }
+    ],
+    "overwrite": [],
+    "externalReference": [],
+    "globalMetadata": {
+      "extendBreadcrumb": "true",
+      "breadcrumb_path":"/sharepoint/dev/breadcrumb/toc.json",
+      "ms.suite": "office365",
+      "ms.author": "o365devx",
+      "author": "o365devx",
+      "ms.topic": "conceptual",
+      "ms.prod": "sharepoint"
+    },
+    "fileMetadata": {
+      "ms.technology":{
+        "spfx-apis/rest/**.md": "sharepoint-framework",
+        "general-development/**.md": "sharepoint-framework",
+        "spfx/**.md": "sharepoint-framework",
+        "spfx-apis/webhooks/**.md": "sharepoint-webhooks",
+        "sp-addins/**.md": "sharepoint-addins"
+      }
+    },
+    "template": [],
+    "dest": "sharepoint-developer"
+  }
+}
\ No newline at end of file
diff --git a/docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md b/docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md
index 31d8b5754a..8ee4b01ce6 100644
--- a/docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md
+++ b/docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md
@@ -1,6 +1,7 @@
 ---
 title: Access SharePoint from mobile and native device apps
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 42014171-5ee5-421d-9cde-413efc3aecef
 ---
 
@@ -13,7 +14,7 @@ SharePoint Add-ins, farm solutions, and "no code" sandboxed solutions are all ru
     
 
 
-> **Important:**
+> [!IMPORTANT]
 > To test and debug on any platform, you need a **developer account on Office 365**. More info: [Set up a development environment for SharePoint Add-ins on Office 365](http://msdn.microsoft.com/library/b22ce52a-ae9e-4831-9b68-c9210af6dc54%28Office.15%29.aspx) or [Create a developer site on an existing Office 365 subscription](http://msdn.microsoft.com/library/2ec857d5-dc6f-4cf6-ba45-adc845ef2a25%28Office.15%29.aspx). 
   
     
@@ -33,7 +34,7 @@ Non-Microsoft device apps, including mobile apps, **use SharePoint REST/OData AP
 - See  [REST API reference for SharePoint](http://msdn.microsoft.com/library/3514e753-19f9-4b41-a1ae-f35c5ffc17d2%28Office.15%29.aspx) for a complete reference.
     
   
-For more information about how to create mobile apps for any platform, see  [Build mobile apps for other platforms using SharePoint](build-mobile-apps-for-other-platforms-using-sharepoint).
+For more information about how to create mobile apps for any platform, see  [Build mobile apps for other platforms using SharePoint](build-mobile-apps-for-other-platforms-using-sharepoint.md).
   
     
     
@@ -56,7 +57,7 @@ Windows Phone apps can use one of the following:
   
     
     
-For more about creating Windows Phone apps that access SharePoint, see  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint).
+For more about creating Windows Phone apps that access SharePoint, see  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md).
   
     
     
diff --git a/docs/general-development/accessibility-in-sharepoint.md b/docs/general-development/accessibility-in-sharepoint.md
index e976fcff31..662596fc5f 100644
--- a/docs/general-development/accessibility-in-sharepoint.md
+++ b/docs/general-development/accessibility-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Accessibility in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c9106d47-c523-49c1-b9f1-cdd7420abd5e
 ---
 
@@ -112,10 +113,10 @@ SharePoint administrators and users depend on the accessibility features that we
 -  [SharePoint Add-ins UX design guidelines](http://msdn.microsoft.com/library/a4a8f53c-27d7-43dc-b6db-aa7b1f1c7d45%28Office.15%29.aspx)
     
   
--  [Develop SharePoint Add-ins](../sp-add-ins/sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](../sp-add-ins/sharepoint-add-ins.md)
     
   
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
 -  [Accessibility in Microsoft Products](http://www.microsoft.com/enable/products/default.aspx)
diff --git a/docs/general-development/accessing-a-schema.md b/docs/general-development/accessing-a-schema.md
index 8fe2f1bf09..efcd530be3 100644
--- a/docs/general-development/accessing-a-schema.md
+++ b/docs/general-development/accessing-a-schema.md
@@ -1,13 +1,14 @@
 ---
 title: Accessing a Schema
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 02613912-36f6-4edc-a915-165d12e60bc8
 ---
 
 
 # Accessing a Schema
 
-This topic shows one example of how you can access and look at a schema for the REST service in Excel Services. This topic assumes that you have read  [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api).d
+This topic shows one example of how you can access and look at a schema for the REST service in Excel Services. This topic assumes that you have read  [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api.md).d
   
     
     
diff --git a/docs/general-development/accessing-the-soap-api.md b/docs/general-development/accessing-the-soap-api.md
index 5f307b32d3..b729dbdc77 100644
--- a/docs/general-development/accessing-the-soap-api.md
+++ b/docs/general-development/accessing-the-soap-api.md
@@ -1,9 +1,10 @@
 ---
 title: Accessing the SOAP API
+ms.date: 09/25/2017
 keywords: soap
 f1_keywords:
 - soap
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 36e8e3d5-83ac-4bd3-b556-1af132add3eb
 ---
 
@@ -72,20 +73,20 @@ For more information about the WSDL format, see the World Wide Web Consortium (W
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md b/docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md
index ebafc83fab..83585f7636 100644
--- a/docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md
+++ b/docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Add-in-scoped external content types in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a34cbbba-dc38-4d3d-b796-d54b5848bdfb
 ---
 
@@ -50,7 +51,7 @@ The following are the requirements for developing external content types that ar
 - SharePoint
     
   
-For information about setting up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about setting up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -67,7 +68,7 @@ Table 1 contains some core concepts that you should be familiar with when workin
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [External content types in SharePoint](external-content-types-in-sharepoint) <br/> |Learn how to create BCS external content types.  <br/> |
+| [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |Learn how to create BCS external content types.  <br/> |
 | [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.  <br/> |
 | [Get started creating SharePoint-hosted SharePoint Add-ins](http://msdn.microsoft.com/library/1b992485-6efe-4ea4-a18c-221689b0b66f%28Office.15%29.aspx) <br/> |Learn how to create a basic SharePoint-hosted add-in by using the Office Developer Tools for Visual Studio 2012.  <br/> |
    
@@ -202,10 +203,10 @@ The following example shows how to set security credentials for an external syst
 <a name="Appscopedect_inthissection"> </a>
 
 
--  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint)
+-  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md)
     
   
--  [How to: Access external data with REST in SharePoint](how-to-access-external-data-with-rest-in-sharepoint)
+-  [How to: Access external data with REST in SharePoint](how-to-access-external-data-with-rest-in-sharepoint.md)
     
   
 
@@ -213,25 +214,25 @@ The following example shows how to set security credentials for an external syst
 <a name="Appscopedect_Addres"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
 -  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint)
+-  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/add-sharepoint-capabilities.md b/docs/general-development/add-sharepoint-capabilities.md
index 73269ba17d..28efaa603d 100644
--- a/docs/general-development/add-sharepoint-capabilities.md
+++ b/docs/general-development/add-sharepoint-capabilities.md
@@ -1,6 +1,7 @@
----
+---
 title: Add SharePoint capabilities
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 11ecb65e-6dc5-4cf1-80ca-3c16418697b6
 ---
 
@@ -32,33 +33,33 @@ The following table shows SharePoint capabilities that you can add to your app,
 
 |**Capability**|**Article title**|
 |:-----|:-----|
-|Model and automate business processes  <br/> | [Workflows in SharePoint](workflows-in-sharepoint) <br/> |
-|Communicate and collaborate with people and track content  <br/> | [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint) <br/> |
-|Add location and mapping features  <br/> | [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint) <br/> |
-|Make search results more relevant  <br/> | [Search in SharePoint](search-in-sharepoint) <br/> |
-|Access data from external data systems  <br/> | [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint) <br/> |
-|Work with data, convert file formats, and translate sites  <br/> | [Office and SharePoint application services](office-and-sharepoint-application-services) <br/> |
-|Work with user access, roles, rights, and claims.  <br/> | [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint) <br/> |
-|Discover content in electronic format for legal purposes  <br/> | [eDiscovery in SharePoint](ediscovery-in-sharepoint) <br/> |
+|Model and automate business processes  <br/> | [Workflows in SharePoint](workflows-in-sharepoint.md) <br/> |
+|Communicate and collaborate with people and track content  <br/> | [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md) <br/> |
+|Add location and mapping features  <br/> | [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md) <br/> |
+|Make search results more relevant  <br/> | [Search in SharePoint](search-in-sharepoint.md) <br/> |
+|Access data from external data systems  <br/> | [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md) <br/> |
+|Work with data, convert file formats, and translate sites  <br/> | [Office and SharePoint application services](office-and-sharepoint-application-services.md) <br/> |
+|Work with user access, roles, rights, and claims.  <br/> | [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md) <br/> |
+|Discover content in electronic format for legal purposes  <br/> | [eDiscovery in SharePoint](ediscovery-in-sharepoint.md) <br/> |
    
 
 ## Additional resources
 <a name="bk_addresources"> </a>
 
 
--  [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
--  [Accessibility in SharePoint](accessibility-in-sharepoint)
+-  [Accessibility in SharePoint](accessibility-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/advanced-scenarios-and-additional-samples.md b/docs/general-development/advanced-scenarios-and-additional-samples.md
index 2fd4a765d7..e6361b27ca 100644
--- a/docs/general-development/advanced-scenarios-and-additional-samples.md
+++ b/docs/general-development/advanced-scenarios-and-additional-samples.md
@@ -1,6 +1,7 @@
 ---
 title: Advanced Scenarios and Additional Samples
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 110bcc88-2b55-4d80-ab5c-dc3b9658e48d
 ---
 
diff --git a/docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md b/docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md
index 6dd4c65c97..ecb92a7e72 100644
--- a/docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md
+++ b/docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md
@@ -1,6 +1,7 @@
 ---
 title: Architecture of the Windows Phone SharePoint List Application template
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2c09bd02-bed0-4293-a4d4-1778692e246a
 ---
 
@@ -38,7 +39,7 @@ The three main components or layers of the MVVM pattern are the View, the Model,
   
     
     
-![Template files in MVVM pattern](../../images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif)
+![Template files in MVVM pattern](../images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif)
   
     
     
@@ -123,7 +124,7 @@ Figure 2 shows a simplified representation of the class inheritance hierarchy fo
   
     
     
-![The EditItemViewModel and EditForm classes](../../images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif)
+![The EditItemViewModel and EditForm classes](../images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif)
   
     
     
@@ -131,7 +132,7 @@ The **EditForm** class (which represents the View component from the MVVM patter
   
     
     
-Software designs based on the MVVM pattern often confine business logic and validation routines to the Model component of the pattern. In projects based on the Windows Phone SharePoint List Application template, however, some operations that are typically considered part of the Model component have been implemented in the ViewModel component to make it more convenient for developers to extend the projects, at the cost of slightly blurring the conceptual distinction between the data layer (Model) and the presentation layer (ViewModel). For example, the ViewModel classes for editing and creating list items (that is, the **EditItemViewModel** and **NewItemViewModel** classes) expose a **Validate** method that developers can override to implement validation of data entered by users. (For information on implementing data validation with these ViewModels, see [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s).)
+Software designs based on the MVVM pattern often confine business logic and validation routines to the Model component of the pattern. In projects based on the Windows Phone SharePoint List Application template, however, some operations that are typically considered part of the Model component have been implemented in the ViewModel component to make it more convenient for developers to extend the projects, at the cost of slightly blurring the conceptual distinction between the data layer (Model) and the presentation layer (ViewModel). For example, the ViewModel classes for editing and creating list items (that is, the **EditItemViewModel** and **NewItemViewModel** classes) expose a **Validate** method that developers can override to implement validation of data entered by users. (For information on implementing data validation with these ViewModels, see [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md)..md)
   
     
     
@@ -151,7 +152,7 @@ The App.xaml file and its associated code-behind file, App.xaml.cs, are standard
   
     
     
-For information about the kinds of modifications you might make to the App.xaml.cs file in your projects, see  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone) on implementing event handlers in the App.xaml.cs file to preserve application state information, and [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app) on instantiating and configuring additional **ListDataProvider** objects in App.xaml.cs.
+For information about the kinds of modifications you might make to the App.xaml.cs file in your projects, see  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md) on implementing event handlers in the App.xaml.cs file to preserve application state information, and [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md) on instantiating and configuring additional **ListDataProvider** objects in App.xaml.cs.
   
     
     
diff --git a/docs/general-development/authentication-authorization-and-security-in-sharepoint.md b/docs/general-development/authentication-authorization-and-security-in-sharepoint.md
index 4fce6b7dc5..1a2edcaa01 100644
--- a/docs/general-development/authentication-authorization-and-security-in-sharepoint.md
+++ b/docs/general-development/authentication-authorization-and-security-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Authentication, authorization, and security in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8734790c-eb75-4d78-9604-7cc23b33b693
 ---
 
@@ -66,13 +67,13 @@ SharePoint supports the following types of authentication:
 
 - **Windows:** All Internet Information Services (IIS) and Windows authentication integration options, including Basic, Digest, Certificates, Windows NT LAN Manager (NTLM), and Kerberos are supported. Windows authentication allows IIS to perform the authentication for SharePoint.
     
-    For information about signing in to SharePoint by using Windows claims mode, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint).
+    For information about signing in to SharePoint by using Windows claims mode, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md).
     
     > **Important:**
       >  For information about suspending impersonation, see [Avoid suspending impersonation of the calling user](http://msdn.microsoft.com/en-us/library/ff407852.aspx). 
 - **ASP.NET Forms:** A non-Windows identity management system that uses the pluggable ASP.NET forms-based authentication system is supported. This mode enables SharePoint to work with a variety of identity management systems, including externally defined groups or roles such as Lightweight Directory Access Protocol (LDAP) and light-weight database identity management systems. Forms authentication allows ASP.NET to perform the authentication for SharePoint, often involving a redirect to a log-on page. In SharePoint, ASP.NET forms are supported only under claims authentication. A forms provider must be registered within a web application that is configured for claims.
     
-    For information about signing in to SharePoint by using ASP.NET membership and role passive sign-in, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint).
+    For information about signing in to SharePoint by using ASP.NET membership and role passive sign-in, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md).
     
   
 
@@ -109,7 +110,7 @@ When a user signs in to SharePoint, the user's token is validated and then used
   
 
 > **Note:**
-> For more information about signing into SharePoint and the different sign-in modes, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint). 
+> For more information about signing into SharePoint and the different sign-in modes, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md). 
   
     
     
@@ -141,7 +142,7 @@ Under this model, your application makes identity-related decisions based on cla
     
 
 > **Note:**
-> For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint) and [Claims provider in SharePoint](claims-provider-in-sharepoint). 
+> For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md) and [Claims provider in SharePoint](claims-provider-in-sharepoint.md). 
   
     
     
@@ -160,7 +161,7 @@ The membership provider is responsible for validating the credential information
     
 
 > **Note:**
-> For more information about STS, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint). 
+> For more information about STS, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md). 
   
     
     
@@ -171,7 +172,7 @@ The role manager is optional. If a custom authentication system does not support
     
 
 > **Note:**
-> For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint) and [Claims provider in SharePoint](claims-provider-in-sharepoint). 
+> For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md) and [Claims provider in SharePoint](claims-provider-in-sharepoint.md). 
   
     
     
@@ -182,7 +183,7 @@ In ASP.NET membership and role passive sign-in, the sign-in happens by redirecti
     
 
 > **Note:**
-> For more information about signing into SharePoint, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint). 
+> For more information about signing into SharePoint, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md). 
   
     
     
@@ -207,19 +208,19 @@ For information about the pluggable authentication framework provided by ASP.NET
 <a name="SP15_AuthenticationAuthorizationSecurity_AdditionalResources"> </a>
 
 
--  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint)
+-  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint.md)
     
   
--  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint)
+-  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md)
     
   
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
--  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint)
+-  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md b/docs/general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md
index 5e3ae027c6..1aea96a778 100644
--- a/docs/general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md
+++ b/docs/general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Authorization, users, groups, and the object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: aacf3398-f0b5-48cb-9071-440b4c3a9dd1
 ---
 
@@ -119,7 +120,7 @@ Figure 1 shows a high-level view of the SharePoint Server security management sy
   
     
     
-![Authorization object relations](../../images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif)
+![Authorization object relations](../images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif)
   
     
     
@@ -249,19 +250,19 @@ The only way to remove a user from all scopes is to delete that user from the si
 <a name="SP15_AuthorizationUsersGroupsAndObjectModel_AdditionalResources"> </a>
 
 
--  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint)
+-  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md)
     
   
--  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint)
+-  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md)
     
   
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
--  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint)
+-  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/basic-uri-structure-and-path.md b/docs/general-development/basic-uri-structure-and-path.md
index 65dde2e1ce..0e862f9747 100644
--- a/docs/general-development/basic-uri-structure-and-path.md
+++ b/docs/general-development/basic-uri-structure-and-path.md
@@ -1,6 +1,7 @@
 ---
 title: Basic URI Structure and Path
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d73cf6c2-0677-4726-8a3e-2ad130e1a12c
 ---
 
@@ -81,7 +82,7 @@ The three parts of the REST URL are:
 
 ### Accessing by Using the Discovery User Interface
 
-You can also access the chart by using the discovery user interface. To learn how access resources like charts, tables, PivotTables, and ranges by using the discovery mechanism shown in the following screen shot, see  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api).
+You can also access the chart by using the discovery user interface. To learn how access resources like charts, tables, PivotTables, and ranges by using the discovery mechanism shown in the following screen shot, see  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api.md).
   
     
     
@@ -89,7 +90,7 @@ You can also access the chart by using the discovery user interface. To learn ho
   
     
     
-![Excel Services REST model URL](../../images/SharePointServer14Con_XLSvcs_RESTModel.gif)
+![Excel Services REST model URL](../images/SharePointServer14Con_XLSvcs_RESTModel.gif)
   
     
     
@@ -173,8 +174,8 @@ http://<ServerName>/_vti_bin/ExcelRest.aspx/Docs/Documents/sampleWorkbook.xlsx/m
   
     
     
- [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api)
+ [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api.md)
   
     
     
- [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api)
+ [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api.md)
diff --git a/docs/general-development/bcs-client-object-model-reference-for-sharepoint.md b/docs/general-development/bcs-client-object-model-reference-for-sharepoint.md
index 6a29aed6e4..b2f997fd46 100644
--- a/docs/general-development/bcs-client-object-model-reference-for-sharepoint.md
+++ b/docs/general-development/bcs-client-object-model-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: BCS client object model reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: fe7d12a3-6ea9-47f9-b69e-f66da9e661dc
 ---
 
@@ -11,7 +12,7 @@ ms.assetid: fe7d12a3-6ea9-47f9-b69e-f66da9e661dc
   
     
     
-![Class libraries and references](../../images/mod_icon_badge_reference.png)
+![Class libraries and references](../images/mod_icon_badge_reference.png)
   
     
     
@@ -493,21 +494,21 @@ The namespace is **Microsoft.BusinessData.MetadataModel**.
 <a name="bkmk_Addres"> </a>
 
 
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
 -  [.NET client API reference for SharePoint Online](http://msdn.microsoft.com/library/88e5e1b9-eab2-4f3b-a3f2-75c96b86f1f4%28Office.15%29.aspx)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
--  [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint)
+-  [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
diff --git a/docs/general-development/bcs-rest-api-reference-for-sharepoint.md b/docs/general-development/bcs-rest-api-reference-for-sharepoint.md
index bf171b2300..e92d188fd2 100644
--- a/docs/general-development/bcs-rest-api-reference-for-sharepoint.md
+++ b/docs/general-development/bcs-rest-api-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: BCS REST API reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 364fb8d7-87d9-4be7-affd-90caba3cd0c0
 ---
 
@@ -11,7 +12,7 @@ ms.assetid: 364fb8d7-87d9-4be7-affd-90caba3cd0c0
   
     
     
-![Class libraries and references](../../images/mod_icon_badge_reference.png)
+![Class libraries and references](../images/mod_icon_badge_reference.png)
   
     
     
@@ -96,7 +97,7 @@ In order to limit the amount of data returned, or make it more relevant to the u
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 -  [Complete basic operations using SharePoint REST endpoints](http://msdn.microsoft.com/library/e3000415-50a0-426e-b304-b7de18f2f7d9%28Office.15%29.aspx)
@@ -108,7 +109,7 @@ In order to limit the amount of data returned, or make it more relevant to the u
 -  [SharePoint: Perform basic data access operations by using REST in apps](http://code.msdn.microsoft.com/SharePoint-Perform-335d925b)
     
   
--  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint)
+-  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md)
     
   
 -  [Complete basic operations using JavaScript library code in SharePoint](http://msdn.microsoft.com/library/29089af8-dbc0-49b7-a1a0-9e311f49c826%28Office.15%29.aspx)
diff --git a/docs/general-development/bdc-model-schema-reference-for-sharepoint.md b/docs/general-development/bdc-model-schema-reference-for-sharepoint.md
index f6c2edf499..cee09d76d6 100644
--- a/docs/general-development/bdc-model-schema-reference-for-sharepoint.md
+++ b/docs/general-development/bdc-model-schema-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: BDC model schema reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 979a5ffc-f033-4e72-b2d1-11d8cb1b294a
 ---
 
@@ -2739,24 +2740,24 @@ None
 <a name="bkmk_Addres"> </a>
 
 
--  [Changes in the BDC model schema for SharePoint](changes-in-the-bdc-model-schema-for-sharepoint)
+-  [Changes in the BDC model schema for SharePoint](changes-in-the-bdc-model-schema-for-sharepoint.md)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
diff --git a/docs/general-development/build-farm-solutions-in-sharepoint.md b/docs/general-development/build-farm-solutions-in-sharepoint.md
index 9646db1742..3d50e8a22c 100644
--- a/docs/general-development/build-farm-solutions-in-sharepoint.md
+++ b/docs/general-development/build-farm-solutions-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Build farm solutions in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 96c32f08-ad93-49af-b8d0-9d194a48cc79
 ---
 
@@ -14,7 +15,7 @@ SharePoint has its own system for installing extensions to SharePoint administra
   
     
     
-Unlike SharePoint Add-ins, farm solutions contain code that is deployed to the SharePoint servers and makes calls to the SharePoint server object model. These assemblies always run with full trust. Moreover, the Features in farm solutions can have scope as wide as the site collection, web application, or whole farm, in addition to the website scope of Features in SharePoint Add-ins. These aspects of farm solutions sometimes make farm administrators reluctant to install them, unless they come from a well-known and trusted source. For this reason, SharePoint extensions that are primarily for use by end users should be developed as SharePoint Add-ins, not farm solutions. Farm solutions should be used for customizations of SharePoint administrative functions, such as custom timer jobs, custom Windows PowerShell cmdlets, and extensions of Central Administration. For more on the advantages of SharePoint Add-ins and the uses of farm solutions, see  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions).
+Unlike SharePoint Add-ins, farm solutions contain code that is deployed to the SharePoint servers and makes calls to the SharePoint server object model. These assemblies always run with full trust. Moreover, the Features in farm solutions can have scope as wide as the site collection, web application, or whole farm, in addition to the website scope of Features in SharePoint Add-ins. These aspects of farm solutions sometimes make farm administrators reluctant to install them, unless they come from a well-known and trusted source. For this reason, SharePoint extensions that are primarily for use by end users should be developed as SharePoint Add-ins, not farm solutions. Farm solutions should be used for customizations of SharePoint administrative functions, such as custom timer jobs, custom Windows PowerShell cmdlets, and extensions of Central Administration. For more on the advantages of SharePoint Add-ins and the uses of farm solutions, see  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md).
   
     
     
@@ -62,13 +63,13 @@ The topics in this section describe the ways in which development of SharePoint
     
     
 
--  [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering)
+-  [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md)
     
   
--  [URLs and tokens in SharePoint](urls-and-tokens-in-sharepoint)
+-  [URLs and tokens in SharePoint](urls-and-tokens-in-sharepoint.md)
     
   
--  [Virtual directories in SharePoint solutions](virtual-directories-in-sharepoint-solutions)
+-  [Virtual directories in SharePoint solutions](virtual-directories-in-sharepoint-solutions.md)
     
   
 
@@ -76,7 +77,7 @@ The topics in this section describe the ways in which development of SharePoint
 <a name="SP15buildfarm_addlresources"> </a>
 
 
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates.md b/docs/general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates.md
index cd47102ada..f513157996 100644
--- a/docs/general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates.md
+++ b/docs/general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates.md
@@ -1,13 +1,14 @@
 ---
 title: Build localized applications for Windows Phone based on the SharePoint templates
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c12d7fd4-8c6b-446b-970b-1eb0e5d0a9b2
 ---
 
 
 # Build localized applications for Windows Phone based on the SharePoint templates
 Learn how building a localizable Windows Phone app using the new SharePoint templates is different from building one using other Windows Phone templates.
-The SharePoint SDK for Windows Phone 7.1 installs Windows Phone project templates, which you can use to build Windows Phone 7.1 applications against SharePoint or SharePoint 2010. For more information, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio). 
+The SharePoint SDK for Windows Phone 7.1 installs Windows Phone project templates, which you can use to build Windows Phone 7.1 applications against SharePoint or SharePoint 2010. For more information, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md). 
   
     
     
@@ -51,7 +52,7 @@ To see a step-by-step process of how to build a localized application for Window
 <a name="bk_addresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [How to: Build a Localized Application for Windows Phone](http://msdn.microsoft.com/library/9306a6ed-6efb-4f32-b850-d2e508431eeb%28Office.15%29.aspx).
diff --git a/docs/general-development/build-mobile-apps-for-other-platforms-using-sharepoint.md b/docs/general-development/build-mobile-apps-for-other-platforms-using-sharepoint.md
index 7f9abd67df..8ea7a18e39 100644
--- a/docs/general-development/build-mobile-apps-for-other-platforms-using-sharepoint.md
+++ b/docs/general-development/build-mobile-apps-for-other-platforms-using-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Build mobile apps for other platforms using SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 017df869-44fb-4ffe-82fb-4654e01329ad
 ---
 
@@ -36,7 +37,7 @@ To use the REST capabilities that are built into SharePoint, you can construct a
   
     
     
-![SharePoint REST architecture](../../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png)
+![SharePoint REST architecture](../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png)
   
     
     
@@ -83,7 +84,7 @@ To authenticate your mobile app with SharePoint, you can use the MS-OFBA protoco
   
     
     
-When a user signs in to SharePoint, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token that is issued by an identity provider. SharePoint supports several kinds of authentication. For more information, see  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint). To authenticate a user, you can use the REST interface. The authorization process verifies that an authenticated subject (an app or a user the app is acting on behalf of) has permission to perform certain operations or to access specific resources (for example, a list or a SharePoint document folder).
+When a user signs in to SharePoint, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token that is issued by an identity provider. SharePoint supports several kinds of authentication. For more information, see  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md). To authenticate a user, you can use the REST interface. The authorization process verifies that an authenticated subject (an app or a user the app is acting on behalf of.md) has permission to perform certain operations or to access specific resources (for example, a list or a SharePoint document folder.md).
   
     
     
@@ -297,16 +298,16 @@ For more information, see  [Complete basic operations using SharePoint REST endp
 <a name="bk_addresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Using the SharePoint REST service](http://msdn.microsoft.com/library/e1ff2979-1c16-4cb0-a57e-9168dfe20a7c.aspx)
     
   
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint)
+-  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md)
     
   
 -  [Use OData query operations in SharePoint REST requests](http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
diff --git a/docs/general-development/build-reusable-components-for-sharepoint.md b/docs/general-development/build-reusable-components-for-sharepoint.md
index 64df3da67f..ab8a66751f 100644
--- a/docs/general-development/build-reusable-components-for-sharepoint.md
+++ b/docs/general-development/build-reusable-components-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Build reusable components for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bb4467e2-57f0-4cf1-91b8-4d3d8d2358cb
 ---
 
@@ -28,10 +29,10 @@ Using SharePoint, you can build a variety of components, such as lists, Web Part
 - **Custom lists** in SharePoint sites provide locations to store data. Data manipulation in SharePoint lists is a widely used practice. You can use lists to contain data that you access programmatically. For more information, see [Building Block: Lists and Document Libraries](http://msdn.microsoft.com/library/16da8f64-f53b-4490-8636-db0e4d7a6912%28Office.15%29.aspx).
     
   
-- **Workflows** enable you to codify and standardize business processes, and are one of the essential tools for implementing certain scenarios. For more information, see [Workflows in SharePoint](workflows-in-sharepoint).
+- **Workflows** enable you to codify and standardize business processes, and are one of the essential tools for implementing certain scenarios. For more information, see [Workflows in SharePoint](workflows-in-sharepoint.md).
     
   
-- **External content types** make data from outside the SharePoint deployment available to the SharePoint application. For more information, see [External content types in SharePoint](external-content-types-in-sharepoint).
+- **External content types** make data from outside the SharePoint deployment available to the SharePoint application. For more information, see [External content types in SharePoint](external-content-types-in-sharepoint.md).
     
   
 - You can define a **content type** that is a prototype of a list item. If you are using content types for a list, you can define the list so that it contains only items of one content type, or you can specify that it can contain items of one of several content types. For more information, see [Introduction to Content Types](http://msdn.microsoft.com/library/a345a6c5-7031-46ab-a2c2-37bedc3012f4%28Office.15%29.aspx).
@@ -51,13 +52,13 @@ Using SharePoint, you can build a variety of components, such as lists, Web Part
 <a name="SP15Reusecomp_AddRes"> </a>
 
 
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
 -  [Host webs, add-in webs, and SharePoint components in SharePoint](http://msdn.microsoft.com/library/b791cdf5-8aa2-47fa-bc4c-aee437354759%28Office.15%29.aspx)
diff --git a/docs/general-development/build-sites-for-sharepoint.md b/docs/general-development/build-sites-for-sharepoint.md
index 9a41312465..5b12205b0d 100644
--- a/docs/general-development/build-sites-for-sharepoint.md
+++ b/docs/general-development/build-sites-for-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Build sites for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3b372a63-7cdf-462a-abb4-750e611e967d
 ---
 
@@ -34,7 +35,7 @@ You can use the SharePoint site publishing capabilities to build, customize, and
 - **Accessibility**—you can use to improve the accessibility of your published sites.
     
   
-If you want to see a summary of what's new for designers and developers of publishing websites in SharePoint, see  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development). 
+If you want to see a summary of what's new for designers and developers of publishing websites in SharePoint, see  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md). 
   
     
     
@@ -42,7 +43,7 @@ If you want to see a summary of what's new for designers and developers of publi
 ## Authoring, design, and branding in SharePoint
 <a name="SP15_BuildSitesForSP2013_AuthoringDesignBranding"> </a>
 
-SharePoint provides a new approach for designing websites. The content-creation workflow is revised so that you can create content using any —and author great content. To brand your site without having to write custom .NET code, use the  [Design Manager](overview-of-design-manager-in-sharepoint) to import design elements. With Design Manager, you can also create an HTML-based master page to define the chrome shared by all of your site's pages and create page layouts to design templates for pages. If you choose to write custom code, you can use .NET server, .NET client (CSOM), Silverlight, and JavaScript libraries.
+SharePoint provides a new approach for designing websites. The content-creation workflow is revised so that you can create content using any —and author great content. To brand your site without having to write custom .NET code, use the  [Design Manager](overview-of-design-manager-in-sharepoint.md) to import design elements. With Design Manager, you can also create an HTML-based master page to define the chrome shared by all of your site's pages and create page layouts to design templates for pages. If you choose to write custom code, you can use .NET server, .NET client (CSOM.md), Silverlight, and JavaScript libraries.
   
     
     
@@ -62,7 +63,7 @@ You can use the new .NET client object model (CSOM) to develop SharePoint apps w
 ## Page model for publishing websites
 <a name="SP15_BuildSitesForSP2013_PageModel"> </a>
 
-SharePoint includes a page model for publishing websites. The page model includes master pages, page layouts, and other components that render your site structure, content, look and feel, and behavior. To learn more, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model).
+SharePoint includes a page model for publishing websites. The page model includes master pages, page layouts, and other components that render your site structure, content, look and feel, and behavior. To learn more, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md).
   
     
     
@@ -74,7 +75,7 @@ A master page is the main template that defines the shared structural elements o
   
     
     
-Page layouts are used by individual pages of a certain type. They are populated with arrangements of page fields. These pages define individual elements on the page. Individual pages are based on page layouts and are created in your web browser either by custom code or by how the site's users fill out the page's fields. To learn more about the page model in SharePoint, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model). 
+Page layouts are used by individual pages of a certain type. They are populated with arrangements of page fields. These pages define individual elements on the page. Individual pages are based on page layouts and are created in your web browser either by custom code or by how the site's users fill out the page's fields. To learn more about the page model in SharePoint, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md). 
   
     
     
@@ -82,7 +83,7 @@ Page layouts are used by individual pages of a certain type. They are populated
 ## Client-side rendering controls
 <a name="SP15_BuildSitesForSP2013_ClientSideRendering"> </a>
 
-All new controls in SharePoint are rendered. Data is written to the controls in a client-side JSON array, and you can display content using JavaScript, CSS, and templates. As a designer or developer, you have control over how content is rendered on the page, and you can use various design techniques to get the look and behaviors you want on your published pages by using features like the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint) and display templates.
+All new controls in SharePoint are rendered. Data is written to the controls in a client-side JSON array, and you can display content using JavaScript, CSS, and templates. As a designer or developer, you have control over how content is rendered on the page, and you can use various design techniques to get the look and behaviors you want on your published pages by using features like the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint.md) and display templates.
   
     
     
@@ -98,7 +99,7 @@ Publishing websites in SharePoint are optimized for mobile development. You can
 ## Metadata and navigation in SharePoint
 <a name="SP15_BuildSitesForSP2013_MetadataNav"> </a>
 
-Managed metadata capabilities introduced in Microsoft SharePoint Server 2010 are improved and extended in SharePoint for better performance, easier access through the user interface, and taxonomy-driven navigation—called managed navigation. You can use managed navigation or navigation based on the SharePoint website structure—called structured navigation—to build your site navigation. To learn more about managed navigation, see  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint) and [Managed navigation in SharePoint](managed-navigation-in-sharepoint).
+Managed metadata capabilities introduced in Microsoft SharePoint Server 2010 are improved and extended in SharePoint for better performance, easier access through the user interface, and taxonomy-driven navigation—called managed navigation. You can use managed navigation or navigation based on the SharePoint website structure—called structured navigation—to build your site navigation. To learn more about managed navigation, see  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint.md) and [Managed navigation in SharePoint](managed-navigation-in-sharepoint.md).
   
     
     
@@ -113,7 +114,7 @@ SharePoint offers the following new content publishing features that enable you
 
 ### Catalogs
 
-SharePoint introduces catalogs, which you can use to publish content across site collections. Cross-site publishing features depend on catalogs. You can use them to reuse content across your sites and across the boundary between your intranet sites and Internet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint).
+SharePoint introduces catalogs, which you can use to publish content across site collections. Cross-site publishing features depend on catalogs. You can use them to reuse content across your sites and across the boundary between your intranet sites and Internet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint.md).
   
     
     
@@ -127,7 +128,7 @@ SharePoint introduces a cross-site publishing feature to reuse content across mu
 
 ### Variations and multilingual sites
 
-You can use the variations feature in SharePoint to create multilingual sites or other sites where you want to vary the presentation of your content. The variations feature is constrained to one site collection. That is, you can create target language/locale "variants" of a source language/locale as current websites within the same SharePoint site collection. Variations supports friendly URLs and the ability to export or import content for translation by a third party in  [XLIFF file format](the-xliff-interchange-file-format-in-sharepoint). You can include labels, a page for translation and replication, a variety of list items (for example, document libraries), and navigation in your export packages. 
+You can use the variations feature in SharePoint to create multilingual sites or other sites where you want to vary the presentation of your content. The variations feature is constrained to one site collection. That is, you can create target language/locale "variants" of a source language/locale as current websites within the same SharePoint site collection. Variations supports friendly URLs and the ability to export or import content for translation by a third party in  [XLIFF file format](the-xliff-interchange-file-format-in-sharepoint.md). You can include labels, a page for translation and replication, a variety of list items (for example, document libraries.md), and navigation in your export packages. 
   
     
     
@@ -143,19 +144,19 @@ You can use the variations feature in SharePoint to create accessible sites or o
 <a name="SP15_BuildSitesForSP2013_AdditionalResources"> </a>
 
 
--  [Optimize SharePoint site accessibility](optimize-sharepoint-site-accessibility)
+-  [Optimize SharePoint site accessibility](optimize-sharepoint-site-accessibility.md)
     
   
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
--  [Minimal Download Strategy overview](minimal-download-strategy-overview)
+-  [Minimal Download Strategy overview](minimal-download-strategy-overview.md)
     
   
--  [Modify SharePoint components for MDS](modify-sharepoint-components-for-mds)
+-  [Modify SharePoint components for MDS](modify-sharepoint-components-for-mds.md)
     
   
 -  [SharePoint Sites and Content server class library](http://msdn.microsoft.com/library/8a93e838-234c-41d8-b990-7ac1a415dd5e%28Office.15%29.aspx)
diff --git a/docs/general-development/build-windows-phone-apps-that-access-sharepoint.md b/docs/general-development/build-windows-phone-apps-that-access-sharepoint.md
index 8eed141e8f..36b892f47a 100644
--- a/docs/general-development/build-windows-phone-apps-that-access-sharepoint.md
+++ b/docs/general-development/build-windows-phone-apps-that-access-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Build Windows Phone apps that access SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 36681335-f772-4499-8445-f94481bc18e7
 ---
 
@@ -28,7 +29,7 @@ The new mobility features offered by SharePoint are built on existing Microsoft
   
     
     
-![SharePoint list items in a Windows Phone app](../../images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif)
+![SharePoint list items in a Windows Phone app](../images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif)
   
     
     
@@ -72,7 +73,7 @@ You can build a wide variety of mobile apps using SharePoint. This section descr
 
 ### Windows Phone SharePoint Application template
 
-This is the simplest type of mobile app you can build to bring a regular list to the phone. SharePoint offers a Visual Studio template to enable you to quickly and easily create SharePoint list applications for the Windows Phone. For example, you can build a "To Do List"-type Windows Phone application that brings your task list from SharePoint into the Windows Phone and enables the you to use your phone to update the status of a task on the go. Another example is having the product catalog for an inventory list in SharePoint available on the phone for the sales people. Installing the Windows Phone SharePoint SDK makes two Windows Phone SharePoint Application templates available to you in Visual Studio 2010 or Visual Studio 2010 Express for Windows Phone. (See  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint).) Using the Windows Phone SharePoint List Application template, you can follow the steps of a wizard to create a functional Windows Phone app that can access and manipulate data in a SharePoint list.
+This is the simplest type of mobile app you can build to bring a regular list to the phone. SharePoint offers a Visual Studio template to enable you to quickly and easily create SharePoint list applications for the Windows Phone. For example, you can build a "To Do List"-type Windows Phone application that brings your task list from SharePoint into the Windows Phone and enables the you to use your phone to update the status of a task on the go. Another example is having the product catalog for an inventory list in SharePoint available on the phone for the sales people. Installing the Windows Phone SharePoint SDK makes two Windows Phone SharePoint Application templates available to you in Visual Studio 2010 or Visual Studio 2010 Express for Windows Phone. (See  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md).) Using the Windows Phone SharePoint List Application template, you can follow the steps of a wizard to create a functional Windows Phone app that can access and manipulate data in a SharePoint list.
   
     
     
@@ -83,15 +84,15 @@ SharePoint adds several new classes to both the server and client object models
   
     
     
-To enable location-aware apps, there is a new native field type class, **SPFieldGeoLocation**, along with several associated classes for structuring the value of location fields and rendering them. These classes are also callable in the SharePoint client object model for Silverlight. The new field type also has a definition added to the standard SharePoint fldtypes.xml file and new user controls for rendering the field on the Display, Edit, and New forms. For an overview, see  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint). 
+To enable location-aware apps, there is a new native field type class, **SPFieldGeoLocation**, along with several associated classes for structuring the value of location fields and rendering them. These classes are also callable in the SharePoint client object model for Silverlight. The new field type also has a definition added to the standard SharePoint fldtypes.xml file and new user controls for rendering the field on the Display, Edit, and New forms. For an overview, see  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md). 
   
     
     
-To enable SharePoint authentication for Windows Phone users, the client object model includes a new **Authenticator** class and several associated classes. For an overview, see [Overview of the SharePoint mobile client authentication object model](overview-of-the-sharepoint-mobile-client-authentication-object-model).
+To enable SharePoint authentication for Windows Phone users, the client object model includes a new **Authenticator** class and several associated classes. For an overview, see [Overview of the SharePoint mobile client authentication object model](overview-of-the-sharepoint-mobile-client-authentication-object-model.md).
   
     
     
-To enable automatic notifications to Windows Phone users of events on a SharePoint farm, the server object model includes several new classes, each of which is also callable from the client object model. These classes include methods that enable phone apps to register with SharePoint server apps for notifications about specified types of events. There are also methods that the server apps use to send notifications to registered subscribers. For an overview, see  [Create a Windows Phone SharePoint list app to receive push notifications](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows#BKMK_NotificationPhoneApp).
+To enable automatic notifications to Windows Phone users of events on a SharePoint farm, the server object model includes several new classes, each of which is also callable from the client object model. These classes include methods that enable phone apps to register with SharePoint server apps for notifications about specified types of events. There are also methods that the server apps use to send notifications to registered subscribers. For an overview, see  [Create a Windows Phone SharePoint list app to receive push notifications](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md#BKMK_NotificationPhoneApp).
   
     
     
@@ -120,7 +121,7 @@ In SharePoint Foundation 2010, the client object models provide APIs that enable
   
     
     
-![SharePoint client object model architecture](../../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png)
+![SharePoint client object model architecture](../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png)
   
     
     
@@ -145,7 +146,7 @@ To use the REST capabilities that are built into SharePoint, you can construct a
   
     
     
-![SharePoint REST architecture](../../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png)
+![SharePoint REST architecture](../images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png)
   
     
     
@@ -180,49 +181,49 @@ The following how-tos and overviews delve into the specific information you need
     
     
 
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
--  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio)
+-  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md)
     
   
--  [Architecture of the Windows Phone SharePoint List Application template](architecture-of-the-windows-phone-sharepoint-list-application-template)
+-  [Architecture of the Windows Phone SharePoint List Application template](architecture-of-the-windows-phone-sharepoint-list-application-template.md)
     
   
--  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app)
+-  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md)
     
   
--  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone)
+-  [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md)
     
   
--  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s)
+-  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md)
     
   
--  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps)
+-  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md)
     
   
--  [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps)
+-  [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md)
     
   
--  [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph)
+-  [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md)
     
   
--  [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app)
+-  [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md)
     
   
--  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows)
+-  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md)
     
   
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [How to: Create a mobile app in SharePoint that contains data from an external data source](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa)
+-  [How to: Create a mobile app in SharePoint that contains data from an external data source](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md)
     
   
--  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists)
+-  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md)
     
   
--  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res)
+-  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md)
     
   
 
@@ -234,10 +235,10 @@ The following how-tos and overviews delve into the specific information you need
     
     
 
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/building-search-queries-in-sharepoint.md b/docs/general-development/building-search-queries-in-sharepoint.md
index 2aac7ee61b..8863b2ae78 100644
--- a/docs/general-development/building-search-queries-in-sharepoint.md
+++ b/docs/general-development/building-search-queries-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Building search queries in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c4372fcc-4574-4c81-a345-a1bb282ca8f7
 ---
 
@@ -50,13 +51,13 @@ For more information about result sources and how they work, see to:  [Understan
 <a name="SP15Buildquery_support"> </a>
 
 
--  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference)
+-  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference.md)
     
   
--  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference)
+-  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference.md)
     
   
--  [Using the SharePoint search Query APIs](using-the-sharepoint-search-query-apis)
+-  [Using the SharePoint search Query APIs](using-the-sharepoint-search-query-apis.md)
     
   
 
@@ -64,7 +65,7 @@ For more information about result sources and how they work, see to:  [Understan
 <a name="SP15Buildquery_addlresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
 -  [Overview of query processing in SharePoint](http://technet.microsoft.com/en-us/library/jj219620%28v=office.15%29.aspx)
diff --git a/docs/general-development/business-connectivity-services-in-sharepoint.md b/docs/general-development/business-connectivity-services-in-sharepoint.md
index 3e2707ad33..da3d19238f 100644
--- a/docs/general-development/business-connectivity-services-in-sharepoint.md
+++ b/docs/general-development/business-connectivity-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Business Connectivity Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 64b7d032-4b83-4e9e-bc08-f0a161af5457
 ---
 
@@ -54,7 +55,7 @@ Figure 1 shows the features that are included in SharePoint and Office 2013.
   
     
     
-![Business Connectivity Services feature set](../../images/BCSin2013FeatureSet.jpg)
+![Business Connectivity Services feature set](../images/BCSin2013FeatureSet.jpg)
   
     
     
@@ -78,7 +79,7 @@ For example, consider a business entity, such as a customer. You want to be able
   
     
     
-For more information about using external content types in BCS, see  [External content types in SharePoint](external-content-types-in-sharepoint).
+For more information about using external content types in BCS, see  [External content types in SharePoint](external-content-types-in-sharepoint.md).
   
     
     
@@ -94,7 +95,7 @@ BCS empowers business users to quickly and easily address a broad array of exter
   
     
     
-For information about how to get started, see  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint).
+For information about how to get started, see  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint.md).
   
     
     
@@ -106,7 +107,7 @@ The Open Data Protocol (OData) is a web protocol that lets you expose data to th
   
     
     
-For more information, see  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint).
+For more information, see  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md).
   
     
     
@@ -115,28 +116,28 @@ For more information, see  [Using OData sources with Business Connectivity Servi
 <a name="bkmk_inthissection"> </a>
 
 
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint)
+-  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
     
   
--  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint)
+-  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint.md)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
 
@@ -144,13 +145,13 @@ For more information, see  [Using OData sources with Business Connectivity Servi
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint)
+-  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint.md)
     
   
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
 
diff --git a/docs/general-development/business-connectivity-services-programmers-reference-for-sharepoint.md b/docs/general-development/business-connectivity-services-programmers-reference-for-sharepoint.md
index ffef1c2f1a..4ff98ec5fe 100644
--- a/docs/general-development/business-connectivity-services-programmers-reference-for-sharepoint.md
+++ b/docs/general-development/business-connectivity-services-programmers-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Business Connectivity Services programmers reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: cfc9bdf8-ddf3-40e1-83d9-dbd304cebd57
 ---
 
@@ -10,7 +11,7 @@ ms.assetid: cfc9bdf8-ddf3-40e1-83d9-dbd304cebd57
   
     
     
-![Class libraries and references](../../images/mod_icon_badge_reference.png)
+![Class libraries and references](../images/mod_icon_badge_reference.png)
   
     
     
@@ -32,29 +33,29 @@ This section provides information for working with BCS programmatically using a
 ## In this section
 
 
--  [BCS REST API reference for SharePoint](bcs-rest-api-reference-for-sharepoint)
+-  [BCS REST API reference for SharePoint](bcs-rest-api-reference-for-sharepoint.md)
     
   
--  [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint)
+-  [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint.md)
     
   
--  [Changes in the BDC model schema for SharePoint](changes-in-the-bdc-model-schema-for-sharepoint)
+-  [Changes in the BDC model schema for SharePoint](changes-in-the-bdc-model-schema-for-sharepoint.md)
     
   
--  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint)
+-  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint.md)
     
   
 
 ## Additional resources
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
 -  [.NET client API reference for SharePoint Online](http://msdn.microsoft.com/library/88e5e1b9-eab2-4f3b-a3f2-75c96b86f1f4%28Office.15%29.aspx)
diff --git a/docs/general-development/changes-in-the-bdc-model-schema-for-sharepoint.md b/docs/general-development/changes-in-the-bdc-model-schema-for-sharepoint.md
index 3f2f713d83..fc1862626c 100644
--- a/docs/general-development/changes-in-the-bdc-model-schema-for-sharepoint.md
+++ b/docs/general-development/changes-in-the-bdc-model-schema-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Changes in the BDC model schema for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 882ea867-9acb-4313-99c9-865a523b72fd
 ---
 
@@ -12,7 +13,7 @@ The number of changes in the schema (BDCMetadata.xsd) for creating BDC models in
     
     
 
-For more information about the BDCMetadata schema, see  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint).
+For more information about the BDCMetadata schema, see  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint.md).
 ## Changes to complex type elements in BDCMetadata.xsd
 <a name="bkmk_ChangesToElements"> </a>
 
@@ -66,19 +67,19 @@ The following table lists the changes to the attributes of each element.
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
--  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint)
+-  [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/choose-the-right-api-set-in-sharepoint.md b/docs/general-development/choose-the-right-api-set-in-sharepoint.md
index 23dce91d35..e339a6a72d 100644
--- a/docs/general-development/choose-the-right-api-set-in-sharepoint.md
+++ b/docs/general-development/choose-the-right-api-set-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Choose the right API set in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f36645da-77c5-47f1-a2ca-13d4b62b320d
 ---
 
@@ -62,7 +63,7 @@ This topic provides an overview of the various API sets that are provided by Sha
   
     
     
-![Venn diagram of API sets and SharePoint app types](../../images/SharePointAPIsetsandselectedSharePointextensions.png)
+![Venn diagram of API sets and SharePoint app types](../images/SharePointAPIsetsandselectedSharePointextensions.png)
   
     
     
@@ -295,7 +296,7 @@ Figure 2 illustrates the relationship of the various client APIs, various types
   
     
     
-![Programming model for apps for SharePoint](../../images/Sp15_app_.png)
+![Programming model for apps for SharePoint](../images/Sp15_app_.png)
   
     
     
@@ -320,13 +321,13 @@ Two API sets are still supported in the SharePoint framework for backward compat
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
--  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions)
+-  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md)
     
   
 -  [Use OData query operations in SharePoint REST requests](http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
diff --git a/docs/general-development/claims-based-identity-and-concepts-in-sharepoint.md b/docs/general-development/claims-based-identity-and-concepts-in-sharepoint.md
index 806cc4bd84..6c00d5e378 100644
--- a/docs/general-development/claims-based-identity-and-concepts-in-sharepoint.md
+++ b/docs/general-development/claims-based-identity-and-concepts-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Claims-based identity and concepts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d96c7cf4-2e48-4223-a3c0-42368d079b74
 ---
 
@@ -145,13 +146,13 @@ Suppose that you have a web farm that consists of a server that runs an ASP.NET
 <a name="bk_addresources"> </a>
 
 
--  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint)
+-  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md)
     
   
--  [Sample delegation, federation, and authentication scenario in SharePoint](sample-delegation-federation-and-authentication-scenario-in-sharepoint)
+-  [Sample delegation, federation, and authentication scenario in SharePoint](sample-delegation-federation-and-authentication-scenario-in-sharepoint.md)
     
   
--  [Claims-based identity term definitions](claims-based-identity-term-definitions)
+-  [Claims-based identity term definitions](claims-based-identity-term-definitions.md)
     
   
 
diff --git a/docs/general-development/claims-based-identity-in-sharepoint.md b/docs/general-development/claims-based-identity-in-sharepoint.md
index bf841244f8..b7b3490486 100644
--- a/docs/general-development/claims-based-identity-in-sharepoint.md
+++ b/docs/general-development/claims-based-identity-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Claims-based identity in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 32b6af2a-72f3-4302-a6af-5f00143cbf67
 ---
 
@@ -48,19 +49,19 @@ The key concept is that a claim is not just a unique identifier that identifies
 <a name="SP15_RoleInheritance_AdditionalResources"> </a>
 
 
--  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint)
+-  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md)
     
   
--  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint)
+-  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md)
     
   
--  [Claims provider in SharePoint](claims-provider-in-sharepoint)
+-  [Claims provider in SharePoint](claims-provider-in-sharepoint.md)
     
   
--  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint)
+-  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md)
     
   
--  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint)
+-  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/claims-based-identity-term-definitions.md b/docs/general-development/claims-based-identity-term-definitions.md
index 775c2488d8..57379721b0 100644
--- a/docs/general-development/claims-based-identity-term-definitions.md
+++ b/docs/general-development/claims-based-identity-term-definitions.md
@@ -1,6 +1,7 @@
 ---
 title: Claims-based identity term definitions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0f3decb5-dcd8-432f-9bb8-533f2d01bef7
 ---
 
@@ -25,7 +26,7 @@ Table 1 contains definitions of key terms related to claims-based identity.
 |Claim value type  <br/> |The type of value in the claim. For example, if the claim value is **Contributor**, the claim type value is **String**.  <br/> |
 |Claims-aware application  <br/> |A relying-party software application that uses claims to manage identity and access for users.  <br/> |
 |Claims-based identity  <br/> |A unique identifier that represents a specific user, application, computer, or other entity. It enables that entity to gain access to multiple resources, such as applications and network resources, without entering credentials multiple times. It also enables resources to validate requests from an entity.  <br/> |
-|Claims provider  <br/> |A software component or service that can be used to issue one or more claims during sign-in operations. It is also used to display, resolve, and provide search capabilities for claims in a card selector (for example, in the people picker control in SharePoint). For more information, see  [Claims provider in SharePoint](claims-provider-in-sharepoint).  <br/> |
+|Claims provider  <br/> |A software component or service that can be used to issue one or more claims during sign-in operations. It is also used to display, resolve, and provide search capabilities for claims in a card selector (for example, in the people picker control in SharePoint). For more information, see  [Claims provider in SharePoint](claims-provider-in-sharepoint.md).  <br/> |
 |Claims provider schema  <br/> |A schema that specifies the fields that must be returned as metadata for a claim that is issued by a specific claims provider.  <br/> |
 |Claims provider - security token service  <br/> |A software component or service that is used by a claims provider that issues claims and packages them in security tokens.  <br/> |
 |Delegate  <br/> |A rich client that is authorized to impersonate another client. For example, consider a situation in which a user-facing website, **Web1**, calls an infrastructure data service, **Data2**. It might be advantageous for **Web1** to impersonate its users when it accesses **Data2**. **Web1** contacts a federation server to obtain claims that represent one of its users. When it is contacted, the federation server can determine whether **Web1** is an authorized delegate and, if so, it can allow the impersonation. If it is authorized, **Web1** accesses **Data2** while acting as the user. <br/> |
@@ -34,7 +35,7 @@ Table 1 contains definitions of key terms related to claims-based identity.
 |Relying party  <br/> |An application that relies on and uses claims in security tokens that a claims provider issues. For example, an online auction website organization might receive a security token with claims that determine whether a subject can access all or part of a relying party's application.  <br/> |
 |Relying-party application  <br/> |Software that can consume claims to make authentication and authorization decisions. The relying party application receives the claims from a claims provider.  <br/> |
 |Rich client  <br/> |A client that can use the WS-Trust protocol.  <br/> |
-|SAML passive sign-in  <br/> |SAML passive sign-in describes the process of signing in. When a sign-in for a web application is configured to accept tokens from a trusted login provider, this type of sign-in is called SAML passive sign-in. For more information, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint).  <br/> |
+|SAML passive sign-in  <br/> |SAML passive sign-in describes the process of signing in. When a sign-in for a web application is configured to accept tokens from a trusted login provider, this type of sign-in is called SAML passive sign-in. For more information, see  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md).  <br/> |
 |Security Assertion Markup Language (SAML) Security Token  <br/> |The data format for communicating claims between a claims provider and a relying party.  <br/> |
 |Security Assertion Markup Language (SAML)  <br/> |The WebSSO protocol that is defined in the SAML 2.0 Core specification. The SAML protocol specifies how to use HTTP web browser redirects to exchange assertions data. SAML is used to authenticate and authorize users across secure boundaries.  <br/> |
 |Security token  <br/> |An on-the-wire representation of claims that is cryptographically signed by the issuer of the claims, providing strong proof to any relying party as to the integrity of the claims and the identity of the issuer.  <br/> |
@@ -56,10 +57,10 @@ Table 1 contains definitions of key terms related to claims-based identity.
 -  [Web Services Federation Language (WS-Federation) Version 1.2](http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-osl#_Toc223175002)
     
   
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
--  [Sample delegation, federation, and authentication scenario in SharePoint](sample-delegation-federation-and-authentication-scenario-in-sharepoint)
+-  [Sample delegation, federation, and authentication scenario in SharePoint](sample-delegation-federation-and-authentication-scenario-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/claims-provider-in-sharepoint.md b/docs/general-development/claims-provider-in-sharepoint.md
index 98ee2d8be7..35599bae67 100644
--- a/docs/general-development/claims-provider-in-sharepoint.md
+++ b/docs/general-development/claims-provider-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Claims provider in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5918d5b6-5fd6-4f41-9473-a15b1491d056
 ---
 
@@ -19,7 +20,7 @@ A claims provider in SharePoint has two roles: augmentation and picking.
     
 
 > **Note:**
-> For information about how to create a claims provider, see  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint). 
+> For information about how to create a claims provider, see  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md). 
   
     
     
@@ -101,16 +102,16 @@ Assume a scenario where your system has some specific requirements for people pi
 <a name="bk_addresources"> </a>
 
 
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint)
+-  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md)
     
   
--  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint)
+-  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md)
     
   
--  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint)
+-  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/code-samples-for-sharepoint.md b/docs/general-development/code-samples-for-sharepoint.md
index cb16d0f487..32be991163 100644
--- a/docs/general-development/code-samples-for-sharepoint.md
+++ b/docs/general-development/code-samples-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Code samples for SharePoint
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e6b52c6c-32f8-4689-8c1a-7b50039dcbe8
 ---
 
@@ -97,7 +98,7 @@ Find and download code samples for SharePoint, including samples that demonstrat
 -  [SharePoint general development](http://msdn.microsoft.com/library/fc829689-7cef-469d-a04c-4a433e49828a%28Office.15%29.aspx)
     
   
--  [How-tos for SharePoint](how-tos-for-sharepoint)
+-  [How-tos for SharePoint](how-tos-for-sharepoint.md)
     
   
 -  [SharePoint Dev Center](http://msdn.microsoft.com/en-US/sharepoint)
diff --git a/docs/general-development/color-palettes-and-fonts-in-sharepoint.md b/docs/general-development/color-palettes-and-fonts-in-sharepoint.md
index 9ac1c1f75c..e86ed7fda8 100644
--- a/docs/general-development/color-palettes-and-fonts-in-sharepoint.md
+++ b/docs/general-development/color-palettes-and-fonts-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Color palettes and fonts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c17d375b-151f-48ae-ac32-f2ce9e68d63f
 ---
 
@@ -73,7 +74,7 @@ A color palette is the combination of colors that are used in a SharePoint site.
 ```
 
 
-  For more information, see  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+  For more information, see  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
 
@@ -407,22 +408,22 @@ Table 1 describes the available font slots and where they are used in a page.
 <a name="bk_addresources"> </a>
 
 
--  [Themes overview for SharePoint](themes-overview-for-sharepoint)
+-  [Themes overview for SharePoint](themes-overview-for-sharepoint.md)
     
   
--  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint)
+-  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md)
     
   
--  [Upgrade custom themes and CSS to SharePoint](upgrade-custom-themes-and-css-to-sharepoint)
+-  [Upgrade custom themes and CSS to SharePoint](upgrade-custom-themes-and-css-to-sharepoint.md)
     
   
--  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+-  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
 
diff --git a/docs/general-development/common-error-messages-in-sharepoint-workflow-development.md b/docs/general-development/common-error-messages-in-sharepoint-workflow-development.md
index 61e0d1235a..ec5619d310 100644
--- a/docs/general-development/common-error-messages-in-sharepoint-workflow-development.md
+++ b/docs/general-development/common-error-messages-in-sharepoint-workflow-development.md
@@ -1,6 +1,7 @@
----
+---
 title: Common error messages in SharePoint workflow development
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e9bf6878-c722-4b1f-b5b5-b302ae0ea4da
 ---
 
@@ -200,10 +201,10 @@ See  [Microsoft Support Knowledge Base article ID 2557533](http://support.micros
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices)
+-  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/configuration-administration-and-resources-in-sharepoint.md b/docs/general-development/configuration-administration-and-resources-in-sharepoint.md
index 4f99e04899..560e8a3f8d 100644
--- a/docs/general-development/configuration-administration-and-resources-in-sharepoint.md
+++ b/docs/general-development/configuration-administration-and-resources-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Configuration, administration, and resources in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e7d8c919-7aa6-466a-acb0-27366129061c
 ---
 
@@ -111,19 +112,19 @@ The following tables list blogs, forums, and additional resources about claims-b
 <a name="bk_addresources"> </a>
 
 
--  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint)
+-  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md)
     
   
--  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint)
+-  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint.md)
     
   
--  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint)
+-  [Role, inheritance, elevation of privilege, and password changes in SharePoint](role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md)
     
   
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/configure-search-in-sharepoint.md b/docs/general-development/configure-search-in-sharepoint.md
index 1ac623050f..6017078f67 100644
--- a/docs/general-development/configure-search-in-sharepoint.md
+++ b/docs/general-development/configure-search-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Configure search in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e447127c-2b11-4d65-b46e-01a18cdcdee5
 ---
 
@@ -29,10 +30,10 @@ A custom step can be added to modify managed properties in the form of an extern
 <a name="SP15ConfigSearch_customstep"> </a>
 
 
--  [Custom word breakers in SharePoint](custom-word-breakers-in-sharepoint-server)
+-  [Custom word breakers in SharePoint](custom-word-breakers-in-sharepoint-server.md)
     
   
--  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout)
+-  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md)
     
   
 
@@ -40,10 +41,10 @@ A custom step can be added to modify managed properties in the form of an extern
 <a name="SP15configsearch_addlresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
 
diff --git a/docs/general-development/content-management-interoperability-services-cmis-in-sharepoint.md b/docs/general-development/content-management-interoperability-services-cmis-in-sharepoint.md
index e8fd64c4d9..beb22a1b9c 100644
--- a/docs/general-development/content-management-interoperability-services-cmis-in-sharepoint.md
+++ b/docs/general-development/content-management-interoperability-services-cmis-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Content Management Interoperability Services (CMIS) in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a1def24c-b2db-4bf9-8d2c-02f5628832f8
 ---
 
@@ -34,7 +35,7 @@ Figure 1. CMIS 1.0 capabilities implemented in SharePoint.
   
     
     
-![CMIS capabilities in SharePoint](../../images/SP15_CMISCapabilities.jpg)
+![CMIS capabilities in SharePoint](../images/SP15_CMISCapabilities.jpg)
   
     
     
@@ -99,7 +100,7 @@ Figure 2. Examples of the CMIS document object-type and folder object-type
   
     
     
-![Examples of CMIS object-types in SharePoint](../../images/SP15_CMISObjectTypeExamples.png)
+![Examples of CMIS object-types in SharePoint](../images/SP15_CMISObjectTypeExamples.png)
   
     
     
@@ -289,7 +290,7 @@ CMIS 1.1 is not supported in SharePoint, but the newer version of the CMIS speci
 <a name="SP15CMIS_AdditionalResources"> </a>
 
 
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
 -  [Manage blocked file types](http://technet.microsoft.com/en-us/library/cc262496.aspx)
diff --git a/docs/general-development/content-search-web-part-in-sharepoint.md b/docs/general-development/content-search-web-part-in-sharepoint.md
index 0f0a8ea104..358fda6667 100644
--- a/docs/general-development/content-search-web-part-in-sharepoint.md
+++ b/docs/general-development/content-search-web-part-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Content Search Web Part in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6fb4bf41-0846-4dca-ad9e-906afdfd3d2b
 ---
 
@@ -10,7 +11,7 @@ ms.assetid: 6fb4bf41-0846-4dca-ad9e-906afdfd3d2b
   
     
     
-![Conceptual overview topic](../../images/mod_icon_badge_conoverview.png)
+![Conceptual overview topic](../images/mod_icon_badge_conoverview.png)
   
     
     
@@ -67,10 +68,10 @@ Some site collection administrators mark sites to not be indexed. Content marked
 <a name="SP15_CSWP_AdditionalResources"> </a>
 
 
--  [Managed navigation in SharePoint](managed-navigation-in-sharepoint)
+-  [Managed navigation in SharePoint](managed-navigation-in-sharepoint.md)
     
   
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
 
diff --git a/docs/general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint.md b/docs/general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint.md
index 27e8bf977a..e88e2cbb03 100644
--- a/docs/general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint.md
+++ b/docs/general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Create a map view for the Geolocation field in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0cd8ba27-3326-4b60-a2d0-d289a94f11bb
 ---
 
@@ -12,7 +13,7 @@ SharePoint introduces a new field type named **Geolocation** that enables you to
     
     
 
-To display a map view in a SharePoint list, you must use the Bing Maps services. The **Geolocation** field is not available when you create a list by using the UI. Instead, this field must be inserted programmatically. For information about how to render and work with this data type programmatically, see [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint).
+To display a map view in a SharePoint list, you must use the Bing Maps services. The **Geolocation** field is not available when you create a list by using the UI. Instead, this field must be inserted programmatically. For information about how to render and work with this data type programmatically, see [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md).
 The **Geolocation** field and the map view enable you to give spatial context to any information by integrating data from SharePoint into a mapping experience in web and mobile apps. This article does not explain how to render the **Geolocation** field or provide developer guidance for creating a location-based mobile application; it does provide instruction for creating map views programmatically and from the SharePoint UI by using Bing Maps.
   
     
@@ -69,7 +70,7 @@ The following steps demonstrate how to create a map view from the SharePoint UI.
 
   
 
-  ![Edit Control Box menu for SharePoint list](../../images/SPCon15_CreateMapView_ECB_Menu__fig1.png)
+  ![Edit Control Box menu for SharePoint list](../images/SPCon15_CreateMapView_ECB_Menu__fig1.png)
   
 
   
@@ -81,7 +82,7 @@ The following steps demonstrate how to create a map view from the SharePoint UI.
 
   
 
-  ![Choose Map View from the list of view types](../../images/SPCon15_CreateMapView_ChooseViewType__fig2.png)
+  ![Choose Map View from the list of view types](../images/SPCon15_CreateMapView_ChooseViewType__fig2.png)
   
 
   
@@ -93,7 +94,7 @@ The following steps demonstrate how to create a map view from the SharePoint UI.
 
   
 
-  ![Select fields to appear in the view](../../images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png)
+  ![Select fields to appear in the view](../images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png)
   
 
     
@@ -105,7 +106,7 @@ The following steps demonstrate how to create a map view from the SharePoint UI.
 
   
 
-  ![Completed map view](../../images/SPCon15_CreateMapView_MyMapView__fig4.png)
+  ![Completed map view](../images/SPCon15_CreateMapView_MyMapView__fig4.png)
   
 
   
@@ -210,7 +211,7 @@ A map view providesthree colors of pushpins (as shown in Figure 5), each of whic
   
     
     
-![Different colors of pushpins in a map view](../../images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png)
+![Different colors of pushpins in a map view](../images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png)
   
     
     
@@ -228,7 +229,7 @@ After you create a map view, all items appear as pushpins. The user can get more
   
     
     
-![User experience of pusphins on a map view](../../images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png)
+![User experience of pusphins on a map view](../images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png)
   
     
     
@@ -245,16 +246,16 @@ After you create a map view, all items appear as pushpins. The user can get more
 <a name="SP15CreatingMapViews_AdditionalResources"> </a>
 
 
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint)
+-  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md)
     
   
--  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint)
+-  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md)
     
   
--  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists)
+-  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md)
     
   
 -  [Use the SharePoint location field type in mobile applications](http://technet.microsoft.com/en-us/library/fp161355%28v=office.15%29.aspx)
diff --git a/docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md b/docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md
index c33bd429db..d7419004cb 100644
--- a/docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md
+++ b/docs/general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md
@@ -1,6 +1,7 @@
----
+---
 title: Create a SharePoint workflow app using Visual Studio 2012
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7923d60d-84b9-44d6-8185-e5236efaf502
 ---
 
@@ -40,7 +41,7 @@ For assistance setting up and configuring your SharePoint workflow development e
     
     
 
--  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment)
+-  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md)
     
   
 -  [Configure workflow in SharePoint](http://technet.microsoft.com/en-us/library/jj658586%28v=office.15%29)
@@ -71,7 +72,7 @@ Here's a flowchart that depicts the course of the workflow we're going to create
   
     
     
-![Flowchart depicting the document approval workflow](../../images/ngGK_Flowchart.png)
+![Flowchart depicting the document approval workflow](../images/ngGK_Flowchart.png)
   
     
     
@@ -99,7 +100,7 @@ In summary, the workflow does the following:
 
     
 > **Important:**
-> Before you start this walkthrough, ensure that you have a properly installed and configured workflow development environment. For more information, see  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment). Also, ensure that you have a SharePoint instance that you can develop your workflow against. For more information, see  [Install SharePoint](http://technet.microsoft.com/en-us/library/cc303424.aspx). 
+> Before you start this walkthrough, ensure that you have a properly installed and configured workflow development environment. For more information, see  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md). Also, ensure that you have a SharePoint instance that you can develop your workflow against. For more information, see  [Install SharePoint](http://technet.microsoft.com/en-us/library/cc303424.aspx). 
   
     
     
@@ -122,7 +123,7 @@ The first step is preparing our SharePoint site with document libraries that our
 
   
 
-  ![New project dialog in Visual Studio 2012](../../images/ngGK_Fig02.png)
+  ![New project dialog in Visual Studio 2012](../images/ngGK_Fig02.png)
   
 
   
@@ -142,7 +143,7 @@ The first step is preparing our SharePoint site with document libraries that our
 
   
 
-  ![Create new document library wizard](../../images/ngGK_Fig03.png)
+  ![Create new document library wizard](../images/ngGK_Fig03.png)
   
 
   
@@ -181,7 +182,7 @@ The first step is preparing our SharePoint site with document libraries that our
 
   
 
-  ![Set custom column properties](../../images/ngGK_Fig04.png)
+  ![Set custom column properties](../images/ngGK_Fig04.png)
   
 
   
@@ -202,7 +203,7 @@ Now we're ready to create the workflow itself.
 
   
 
-  ![Add new workflow item](../../images/ngGK_Fig05.png)
+  ![Add new workflow item](../images/ngGK_Fig05.png)
   
 
   
@@ -214,7 +215,7 @@ Now we're ready to create the workflow itself.
 
   
 
-  ![Specify workflow name and type](../../images/ngGK_Fig06.png)
+  ![Specify workflow name and type](../images/ngGK_Fig06.png)
   
 
   
@@ -226,7 +227,7 @@ Now we're ready to create the workflow itself.
 
   
 
-  ![Completing the SharePint Customization Wizard](../../images/ngGK_Fig07.png)
+  ![Completing the SharePint Customization Wizard](../images/ngGK_Fig07.png)
   
 
   
@@ -238,7 +239,7 @@ Now we're ready to create the workflow itself.
 
   
 
-  ![Set activation parameters for the workflow](../../images/ngGK_Fig08.png)
+  ![Set activation parameters for the workflow](../images/ngGK_Fig08.png)
   
 
     
@@ -249,7 +250,7 @@ Now we're ready to create the workflow itself.
 
   
 
-  ![Workflow property grid](../../images/ngGK_Fig09.png)
+  ![Workflow property grid](../images/ngGK_Fig09.png)
   
 
   
@@ -276,7 +277,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![LookupSPListItem activity selector](../../images/ngGK_Fig10.png)
+  ![LookupSPListItem activity selector](../images/ngGK_Fig10.png)
   
 
   
@@ -290,7 +291,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Setting properties for LookupSPListItem](../../images/ngGK_Fig11.png)
+  ![Setting properties for LookupSPListItem](../images/ngGK_Fig11.png)
   
 
   
@@ -310,7 +311,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Setting property values to extract](../../images/ngGK_Fig12.png)
+  ![Setting property values to extract](../images/ngGK_Fig12.png)
   
 
   
@@ -330,7 +331,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Get document status and approver properties](../../images/ngGK_Fig13.png)
+  ![Get document status and approver properties](../images/ngGK_Fig13.png)
   
 
   
@@ -347,7 +348,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Creating an If/Then clause to trigger a task](../../images/ngGK_Fig14.png)
+  ![Creating an If/Then clause to trigger a task](../images/ngGK_Fig14.png)
   
 
   
@@ -362,7 +363,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Task configuration dialog box](../../images/ngGK_Fig15.png)
+  ![Task configuration dialog box](../images/ngGK_Fig15.png)
   
 
   
@@ -392,7 +393,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Cast the "Approver" variable to string data type](../../images/ngGK_Fig16.png)
+  ![Cast the "Approver" variable to string data type](../images/ngGK_Fig16.png)
   
 
     At the present point in this walkthrough you have created and configured a workflow task that does two things: It sets a document to be reviewed, but also sends an email to the task assignee (the "Approver" in this case) notifying him or her that a task has been assigned and is waiting for actions.
@@ -410,7 +411,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Using IF activity to check the task status](../../images/ngGK_Fig17.png)
+  ![Using IF activity to check the task status](../images/ngGK_Fig17.png)
   
 
   
@@ -430,7 +431,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Specifying list item properties to update](../../images/ngGK_Fig18.png)
+  ![Specifying list item properties to update](../images/ngGK_Fig18.png)
   
 
   
@@ -445,7 +446,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Adding a CopyItem activity to the workflow](../../images/ngGK_Fig19.png)
+  ![Adding a CopyItem activity to the workflow](../images/ngGK_Fig19.png)
   
 
     Then, configure properties of the **CopyItem** activity in the property grid as depicted in Figure 20. Property values are highlighted.
@@ -455,7 +456,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Configuring properties of the CopyItem activity](../../images/ngGK_Fig20.png)
+  ![Configuring properties of the CopyItem activity](../images/ngGK_Fig20.png)
   
 
     
@@ -467,7 +468,7 @@ Now that we have our SharePoint Server set up and our basic workflow created, we
 
   
 
-  ![Configuring UpdateListItem for rejected documents](../../images/ngGK_Fig21.png)
+  ![Configuring UpdateListItem for rejected documents](../images/ngGK_Fig21.png)
   
 
   
@@ -487,7 +488,7 @@ This completes "Creating a SharePoint document approval workflow." The completed
   
     
     
-![Completed document approval workflow](../../images/ngGK_Fig22.png)
+![Completed document approval workflow](../images/ngGK_Fig22.png)
   
     
     
@@ -538,16 +539,16 @@ Following are resources that provide guidance for packaging and deploying your w
 <a name="bk_addresources"> </a>
 
 
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
--  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment)
+-  [Prepare to set up and configure a SharePoint workflow development environment](prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md)
     
   
--  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices)
+-  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md b/docs/general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md
index 5bf73b2f0d..247707b7ee 100644
--- a/docs/general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md
+++ b/docs/general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md
@@ -1,6 +1,7 @@
 ---
 title: Create a workflow with elevated permissions by using the SharePoint Workflow platform
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4656f6a0-36fd-4b7d-898e-8cd4bdbbda57
 ---
 
@@ -70,7 +71,7 @@ The first step is to allow workflow to use app permissions. You configure workfl
 
   
 
-  ![Settings menu](../../images/SPD15-WFAppPermissions1.png)
+  ![Settings menu](../images/SPD15-WFAppPermissions1.png)
   
 
   
@@ -91,7 +92,7 @@ The first step is to allow workflow to use app permissions. You configure workfl
 
   
 
-  ![Workflow can use app permissions feature](../../images/SPD15-WFAppPermissions2.png)
+  ![Workflow can use app permissions feature](../images/SPD15-WFAppPermissions2.png)
   
 
   
@@ -121,7 +122,7 @@ In order for the workflow to function properly it must be granted full control i
 
   
 
-  ![Settings menu](../../images/SPD15-WFAppPermissions1.png)
+  ![Settings menu](../images/SPD15-WFAppPermissions1.png)
   
 
   
@@ -139,7 +140,7 @@ In order for the workflow to function properly it must be granted full control i
 
   
 
-  ![Selecting App Identifier](../../images/SPD15-WFAppPermissions3.png)
+  ![Selecting App Identifier](../images/SPD15-WFAppPermissions3.png)
   
 
   
@@ -161,7 +162,7 @@ In order for the workflow to function properly it must be granted full control i
 
   
 
-  ![The appinv.aspx URL example and page.](../../images/SPD15-WFAppPermissions4.png)
+  ![The appinv.aspx URL example and page.](../images/SPD15-WFAppPermissions4.png)
   
 
   
@@ -188,7 +189,7 @@ In order for the workflow to function properly it must be granted full control i
 
   
 
-  ![Looking up an App Id.](../../images/SPD15-WFAppPermissions5.png)
+  ![Looking up an App Id.](../images/SPD15-WFAppPermissions5.png)
 
 
 8. Click **Create**.
@@ -198,7 +199,7 @@ In order for the workflow to function properly it must be granted full control i
     
   **Figure: Trust the Workflow app**
 
-  ![Trust the Workflow app.](../../images/SPD15-WFAppPermissions6.png)
+  ![Trust the Workflow app.](../images/SPD15-WFAppPermissions6.png)
   
 ### Wrapping actions inside an App Step
 
@@ -225,7 +226,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
 
   
 
-  ![Create a new List workflow.](../../images/SPD15-WFAppPermissions7.png)
+  ![Create a new List workflow.](../images/SPD15-WFAppPermissions7.png)
   
 
   
@@ -237,7 +238,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
 
   
 
-  ![Adding an App Step.](../../images/SPD15-WFAppPermissions8.png)
+  ![Adding an App Step.](../images/SPD15-WFAppPermissions8.png)
   
 
   
@@ -250,14 +251,14 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
     
   **Figure: Select Workflow lookup for a user**
 
-  ![Select Workflow lookup for a user.](../../images/SPD15-WFAppPermissions9.png)
+  ![Select Workflow lookup for a user.](../images/SPD15-WFAppPermissions9.png)
   
 
 8. Enter the **Created By** field as the lookup value, as shown in the figure.
     
   **Figure: Lookup for Person dialog box**
 
-  ![Lookup for Person dialog.](../../images/SPD15-WFAppPermissions10.png)
+  ![Lookup for Person dialog.](../images/SPD15-WFAppPermissions10.png)
   
 9. Enter Email from App Demo list in the email message body.
     
@@ -266,7 +267,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
     
   **Figure: Email action in App Step**
 
-  ![Email action in App Step.](../../images/SPD15-WFAppPermissions11.png)
+  ![Email action in App Step.](../images/SPD15-WFAppPermissions11.png)
     
 11. Click the **Workflow Settings** icon in the ribbon, as shown in the figure.
     
@@ -274,7 +275,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
 
   
 
-  ![Workflow Settings icon in ribbon.](../../images/SPD15-WFAppPermissions12.png)
+  ![Workflow Settings icon in ribbon.](../images/SPD15-WFAppPermissions12.png)
   
 
   
@@ -286,7 +287,7 @@ Finally, you need to wrap the workflow actions inside an App Step. The following
 
   
 
-  ![Clear automatic updates check mark and publish.](../../images/SPD15-WFAppPermissions13.png)
+  ![Clear automatic updates check mark and publish.](../images/SPD15-WFAppPermissions13.png)
   
 
 
@@ -305,7 +306,7 @@ To understand why elevating permissions for a workflow is required, consider tha
   
     
     
-![Permissions diagram.](../../images/SPD15-WFAppPermissions14.png)
+![Permissions diagram.](../images/SPD15-WFAppPermissions14.png)
   
     
     
@@ -338,7 +339,7 @@ The following diagram illustrates the change in permissions
   
     
     
-![Permissions matrix.](../../images/SPD15-WFAppPermissions15.png)
+![Permissions matrix.](../images/SPD15-WFAppPermissions15.png)
   
     
     
@@ -367,10 +368,10 @@ The following diagram illustrates the change in permissions
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 -  [Blog article from the SharePoint Designer team: Workflow package and deploy scenario](http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/30/packaging-list-site-and-reusable-workflow-and-how-to-deploy-the-package.aspx)
diff --git a/docs/general-development/create-associations-in-sharepoint.md b/docs/general-development/create-associations-in-sharepoint.md
index 4505848c51..aeeedabd67 100644
--- a/docs/general-development/create-associations-in-sharepoint.md
+++ b/docs/general-development/create-associations-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Create associations in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 202599e3-232e-4b3a-9da5-c11f6e972283
 ---
 
@@ -32,10 +33,10 @@ The following articles were written for SharePoint Server 2010 and SharePoint De
 ## Additional resources
 
 
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/create-hybrid-connectivity-apps-for-sharepoint.md b/docs/general-development/create-hybrid-connectivity-apps-for-sharepoint.md
index 568d4dd74f..d641d5c9c0 100644
--- a/docs/general-development/create-hybrid-connectivity-apps-for-sharepoint.md
+++ b/docs/general-development/create-hybrid-connectivity-apps-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Create hybrid connectivity apps for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 311f036e-3442-4497-b35e-442b665462d3
 ---
 
@@ -181,7 +182,7 @@ To add a BDC model or external content type to your project, do the following.
 8. Modify the  `ODataServiceUrl` property with the URL that allows access through the reverse proxy.
     
   
-For information about how to add an OData-based external content type, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint).
+For information about how to add an OData-based external content type, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md).
   
     
     
@@ -204,7 +205,7 @@ For information about deploying SharePoint Add-ins, see the following:
 -  [Publish SharePoint Add-ins by using Visual Studio](http://msdn.microsoft.com/library/8137d0fa-52e2-4771-8639-60af80f693bb%28Office.15%29.aspx)
     
   
-You can also take the BDCM file created for the external content type and extract that to be used at any level above the app. This is demonstrated in  [How to: Convert an add-in-scoped external content type to tenant-scoped](how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped).
+You can also take the BDCM file created for the external content type and extract that to be used at any level above the app. This is demonstrated in  [How to: Convert an add-in-scoped external content type to tenant-scoped](how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md).
   
     
     
@@ -216,10 +217,10 @@ You can also take the BDCM file created for the external content type and extrac
 -  [Hybrid for SharePoint](http://technet.microsoft.com/en-us/library/jj838715.aspx)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
 -  [Publish SharePoint Add-ins by using Visual Studio](http://msdn.microsoft.com/library/8137d0fa-52e2-4771-8639-60af80f693bb%28Office.15%29.aspx)
diff --git a/docs/general-development/create-sharepoint-no-code-solutions.md b/docs/general-development/create-sharepoint-no-code-solutions.md
index 61270760bd..fafb90c8c0 100644
--- a/docs/general-development/create-sharepoint-no-code-solutions.md
+++ b/docs/general-development/create-sharepoint-no-code-solutions.md
@@ -1,6 +1,7 @@
----
+---
 title: Create SharePoint no-code solutions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 9511846c-d2c6-4f23-b5de-24be4749598a
 ---
 
@@ -30,16 +31,16 @@ The following articles describe how to create no-code solutions and provide link
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [SharePoint Composites Handbook](sharepoint-composites-handbook) <br/> |Provides in-depth guidance to help you learn how to create a no-code solution.  <br/> |
+| [SharePoint Composites Handbook](sharepoint-composites-handbook.md) <br/> |Provides in-depth guidance to help you learn how to create a no-code solution.  <br/> |
 | [No-code solutions using SharePoint Composites](http://technet.microsoft.com/en-us/sharepoint/dn594430) <br/> |Provides links to many practical articles, walkthroughs, demos, virtual labs, and other formats that show how to create no-code solutions.  <br/> |
-| [Save, download, and upload a SharePoint site as a template](save-download-and-upload-a-sharepoint-site-as-a-template) <br/> |Explains how to create site templates without using code so you can easily deploy no-code solutions.  <br/> |
+| [Save, download, and upload a SharePoint site as a template](save-download-and-upload-a-sharepoint-site-as-a-template.md) <br/> |Explains how to create site templates without using code so you can easily deploy no-code solutions.  <br/> |
    
 
 ## Additional resources
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
 
diff --git a/docs/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md b/docs/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md
index 61dea20742..21de5ca736 100644
--- a/docs/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md
+++ b/docs/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md
@@ -1,6 +1,7 @@
 ---
 title: Creating a workflow by using SharePoint Designer 2013 and the SharePoint Workflow platform
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c05e0127-c6f5-48b8-b8f2-cbcc30149c8b
 ---
 
@@ -48,7 +49,7 @@ SharePoint Designer 2013 is a free download. To download and install SharePoint
   
     
     
-![The SharePoint Designer 2013 Download page.](../../images/SPD15-install-connect-1.png)
+![The SharePoint Designer 2013 Download page.](../images/SPD15-install-connect-1.png)
   
     
     
@@ -125,7 +126,7 @@ SharePoint Designer 2013 can be used for many important tasks. The navigational
   
     
     
-![SharePoint Designer 2013 - New List Workflow](../../images/SPD15-install-connect-2.png)
+![SharePoint Designer 2013 - New List Workflow](../images/SPD15-install-connect-2.png)
   
     
     
@@ -147,7 +148,7 @@ SharePoint Designer 2013 can be used for many important tasks. The navigational
   
     
     
-![Workflow Creation Dialog](../../images/SPD15-install-connect-3.png)
+![Workflow Creation Dialog](../images/SPD15-install-connect-3.png)
   
     
     
@@ -173,7 +174,7 @@ Now that the workflow is created, you can add Actions, Conditions, Stages, Steps
   
     
     
-![Workflow items in the ribbon.](../../images/SPD15-install-connect-4.png)
+![Workflow items in the ribbon.](../images/SPD15-install-connect-4.png)
   
     
     
@@ -185,7 +186,7 @@ Now that the workflow is created, you can add Actions, Conditions, Stages, Steps
     
     
 
-To learn more about the available components of workflow development, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform).
+To learn more about the available components of workflow development, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md).
   
     
     
@@ -200,7 +201,7 @@ To learn more about the available components of workflow development, see  [Work
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/cross-site-publishing-in-sharepoint.md b/docs/general-development/cross-site-publishing-in-sharepoint.md
index 3949dce639..ed09a542cb 100644
--- a/docs/general-development/cross-site-publishing-in-sharepoint.md
+++ b/docs/general-development/cross-site-publishing-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Cross-site publishing in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 33f49e69-c1d3-4a6e-8887-5df683cba022
 ---
 
@@ -32,7 +33,7 @@ Cross-site publishing was designed with some common scenarios in mind, including
 ## Catalogs
 <a name="SP15_CrossSitePublising_Catalog"> </a>
 
-Catalogs, introduced in SharePoint, include a list or library that is shared out to search for consumption on publishing sites. Catalogs enable content to be published across site collections—the cross-site publishing features depend on catalogs. You can use catalogs to really reuse content across your sites and across the boundary between your intranet sites, extranet sites, and Internet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint).
+Catalogs, introduced in SharePoint, include a list or library that is shared out to search for consumption on publishing sites. Catalogs enable content to be published across site collections—the cross-site publishing features depend on catalogs. You can use catalogs to really reuse content across your sites and across the boundary between your intranet sites, extranet sites, and Internet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint.md).
   
     
     
@@ -184,7 +185,7 @@ public CatalogConnectionSettings GetCatalogConnectionSettings(string catalogPath
 <a name="bk_addresources"> </a>
 
 
--  [Publish SharePoint sites](publish-sharepoint-sites)
+-  [Publish SharePoint sites](publish-sharepoint-sites.md)
     
   
 
diff --git a/docs/general-development/custom-content-processing-with-the-content-enrichment-web-service-callout.md b/docs/general-development/custom-content-processing-with-the-content-enrichment-web-service-callout.md
index 5dad6e2470..debd4812e7 100644
--- a/docs/general-development/custom-content-processing-with-the-content-enrichment-web-service-callout.md
+++ b/docs/general-development/custom-content-processing-with-the-content-enrichment-web-service-callout.md
@@ -1,6 +1,7 @@
 ---
 title: Custom content processing with the Content Enrichment web service callout
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bdda92c8-9c8d-416e-9a6b-4a9373686fa0
 ---
 
@@ -22,7 +23,7 @@ Search in SharePoint enables users to modify the managed properties of crawled i
   
     
     
-![Content enrichment within content processing](../../images/SP15_Content_Enrichment.gif)
+![Content enrichment within content processing](../images/SP15_Content_Enrichment.gif)
   
     
     
@@ -142,7 +143,7 @@ Table 2 lists examples of trigger conditions.
 |StartsWith(MP1, "sample") AND MP2 != 18  <br/> |Returns **true** if the value in the managed property MP1 starts with "sample" and the value of managed property MP2 is not 18. <br/> |MP1 must be of type **string** and MP2 must be a numeric type. <br/> |
 |IsDay(MP1, 2009, 12, 24)  <br/> |Checks whether the managed property MP1 contains a **DateTime** that falls on December 24, 2009. <br/> |MP1 must be of type **DateTime**.  <br/> |
    
-See  [Trigger expressions syntax in SharePoint](trigger-expressions-syntax-in-sharepoint) for the elements that can be used in a trigger expression and a list of supported functions.
+See  [Trigger expressions syntax in SharePoint](trigger-expressions-syntax-in-sharepoint.md) for the elements that can be used in a trigger expression and a list of supported functions.
   
     
     
@@ -166,10 +167,10 @@ For a basic implementation, do the following:
 <a name="bk_addresources"> </a>
 
 
--  [Configure search in SharePoint](configure-search-in-sharepoint)
+-  [Configure search in SharePoint](configure-search-in-sharepoint.md)
     
   
--  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout)
+-  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md)
     
   
 
diff --git a/docs/general-development/custom-security-trimming-for-search-in-sharepoint-server.md b/docs/general-development/custom-security-trimming-for-search-in-sharepoint-server.md
index 354c171df1..c6df5a7762 100644
--- a/docs/general-development/custom-security-trimming-for-search-in-sharepoint-server.md
+++ b/docs/general-development/custom-security-trimming-for-search-in-sharepoint-server.md
@@ -1,6 +1,7 @@
 ---
 title: Custom security trimming for Search in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: fbbf0cc4-e135-426a-9996-34eb954dbd5a
 ---
 
@@ -206,7 +207,7 @@ public void Initialize(NameValueCollection staticProperties, SearchServiceApplic
 ## Deploying the custom security trimmer component
 <a name="Deploying_the_trimmer"> </a>
 
-After you create the custom security trimmer, you must deploy it to the global assembly cache on any server in the Query role. Step 2 in  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results) describes the process for deploying the custom security trimmer to the global assembly cache.
+After you create the custom security trimmer, you must deploy it to the global assembly cache on any server in the Query role. Step 2 in  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md) describes the process for deploying the custom security trimmer to the global assembly cache.
   
     
     
@@ -238,7 +239,7 @@ The following table describes the parameters that the cmdlet uses.
 | _id_ <br/> |Required. The security trimmer identifier (ID). This value is unique; if a security trimmer is registered with an ID that is already registered for another security trimmer, the registration for the first trimmer is overwritten with the registration for the second trimmer.  <br/> |
 | _properties_ <br/> |Optional. The name-value pairs specifying the configuration properties. Must be in the following format:  `Name1~Value1~Name2~Value~???` <br/> |
    
-For an example of a basic command for registering a custom security trimmer and a sample that specifies the configuration properties, see  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results).
+For an example of a basic command for registering a custom security trimmer and a sample that specifies the configuration properties, see  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md).
   
     
     
@@ -247,7 +248,7 @@ For an example of a basic command for registering a custom security trimmer and
 <a name="bk_sectrimmer_addlresources"> </a>
 
 
--  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results)
+-  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md)
     
   
 -  [ISecurityTrimmerPre](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.Query.ISecurityTrimmerPre.aspx)
diff --git a/docs/general-development/custom-word-breakers-in-sharepoint-server.md b/docs/general-development/custom-word-breakers-in-sharepoint-server.md
index 9545a78451..d5e08ef36c 100644
--- a/docs/general-development/custom-word-breakers-in-sharepoint-server.md
+++ b/docs/general-development/custom-word-breakers-in-sharepoint-server.md
@@ -1,6 +1,7 @@
 ---
 title: Custom word breakers in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d18b48d4-987c-4228-9932-30d5b30f86a2
 ---
 
@@ -279,7 +280,7 @@ Vietnamese
 <a name="SP15wordbreakers_addresources"> </a>
 
 
--  [Configure search in SharePoint](configure-search-in-sharepoint)
+-  [Configure search in SharePoint](configure-search-in-sharepoint.md)
     
   
 -  [Implementing a Word Breaker](http://msdn.microsoft.com/en-us/library/ms693186%28v=vs.85%29.aspx)
diff --git a/docs/general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint.md b/docs/general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint.md
index 7f7ea65bc3..a3cbfd1536 100644
--- a/docs/general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint.md
+++ b/docs/general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint.md
@@ -1,13 +1,14 @@
 ---
 title: Customizing ranking models to improve relevance in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c166ecdd-7f93-4bbb-b543-2687992dd2bc
 ---
 
 
 # Customizing ranking models to improve relevance in SharePoint
 Improve search relevance by customizing ranking models to calculate rank scores (relevance rank) accurately using rank features in SharePoint.
-You can  [sort search results in SharePoint](sorting-search-results-in-sharepoint) in four ways, one of which is by rank score. When you sort search results by rank score, SharePoint places the most relevant results on top in the search result set.
+You can  [sort search results in SharePoint](sorting-search-results-in-sharepoint.md) in four ways, one of which is by rank score. When you sort search results by rank score, SharePoint places the most relevant results on top in the search result set.
   
     
     
@@ -208,7 +209,7 @@ To retrieve the rank detail, you need to be the administrator of the Search serv
     
 
 ### To retrieve the rank detail
-
+<a name="sp15_list_available_ranking_models"> </a>
 
 1. Open the SharePoint Management Shell as an Administrator.
     
@@ -292,7 +293,7 @@ The BM25 rank feature calculates the relevance rank score using the following fo
   
     
     
-![BM25 formula for the BM25 rank feature](../../images/sp15_BM25_formula.gif)
+![BM25 formula for the BM25 rank feature](../images/sp15_BM25_formula.gif)
   
     
     
@@ -446,7 +447,7 @@ Before the static rank feature can be aggregated with other rank features, each
 
     
     
-![Transform functions supported for rank features](../../images/sp15_transform_table_ranking_model.gif)
+![Transform functions supported for rank features](../images/sp15_transform_table_ranking_model.gif)
   
     
     
@@ -688,7 +689,7 @@ The freshness transform is based on the following formula:
   
     
     
-![Freshness formula for ranking models](../../images/sp15_freshness_formula.gif)
+![Freshness formula for ranking models](../images/sp15_freshness_formula.gif)
   
     
     
@@ -798,7 +799,7 @@ The rank score provided by linear models is computed using the following formula
   
     
     
-![Linear model formula for ranking models](../../images/sp15_linear_model_formula.gif)
+![Linear model formula for ranking models](../images/sp15_linear_model_formula.gif)
   
     
     
@@ -845,7 +846,7 @@ The ranking score produced by a neural network is computed using the following f
   
     
     
-![Neural network formula for ranking models](../../images/sp15_neural_network_formula.gif)
+![Neural network formula for ranking models](../images/sp15_neural_network_formula.gif)
   
     
     
@@ -900,7 +901,7 @@ The overall schema of rank score computation with a two-layer neural network is
   
     
     
-![Neural network in ranking models](../../images/sp15neuralnetworkinrankingmodels.gif)
+![Neural network in ranking models](../images/sp15neuralnetworkinrankingmodels.gif)
   
     
     
@@ -1080,13 +1081,13 @@ This ranking model with one linear stage contains these four rank features:
 <a name="bk_addresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
--  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference)
+-  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference.md)
     
   
--  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference)
+-  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference.md)
     
   
 -  [Overview of search result ranking in SharePoint](http://technet.microsoft.com/library/7c8ddec1-c8ff-4a90-afae-387b27a653f1.aspx)
diff --git a/docs/general-development/customizing-search-results-in-sharepoint.md b/docs/general-development/customizing-search-results-in-sharepoint.md
index 004699a8ac..955da8a7ab 100644
--- a/docs/general-development/customizing-search-results-in-sharepoint.md
+++ b/docs/general-development/customizing-search-results-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Customizing search results in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1b30f6df-643a-4570-ae5c-d3d8df5609b8
 ---
 
diff --git a/docs/general-development/debugging-sharepoint-server-workflows.md b/docs/general-development/debugging-sharepoint-server-workflows.md
index bce9a93114..7a16ef16da 100644
--- a/docs/general-development/debugging-sharepoint-server-workflows.md
+++ b/docs/general-development/debugging-sharepoint-server-workflows.md
@@ -1,6 +1,7 @@
 ---
 title: Debugging SharePoint workflows
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a5adf39b-8640-4871-be60-b786dcf9fafc
 ---
 
@@ -82,7 +83,7 @@ Another debugging option is to take advantage of breakpoints. Breakpoints are av
   
     
     
-![Figure 1 Starting workflow](../../images/ngDebuggingSP2013Workflows01.png)
+![Figure 1 Starting workflow](../images/ngDebuggingSP2013Workflows01.png)
   
     
     
@@ -100,7 +101,7 @@ Visual Studio will deploy the workflow to the target SharePoint environment and
   
     
     
-![Figure 2. Workflow breakpoint](../../images/ngDebuggingSP2013Workflows02.png)
+![Figure 2. Workflow breakpoint](../images/ngDebuggingSP2013Workflows02.png)
   
     
     
@@ -129,7 +130,7 @@ The introduction of Workflow Manager to the SharePoint workflow story introduces
   
     
     
-![Figure 3. WriteLine activity](../../images/ngDebuggingSP2013Workflows.png)
+![Figure 3. WriteLine activity](../images/ngDebuggingSP2013Workflows.png)
   
     
     
@@ -147,7 +148,7 @@ This activity will write the message that resembles the **System.Diagnostics.Deb
   
     
     
-![Figure 4. Messages for WriteLine activity](../../images/ngDebuggingSP2013Workflows04.png)
+![Figure 4. Messages for WriteLine activity](../images/ngDebuggingSP2013Workflows04.png)
   
     
     
@@ -305,7 +306,7 @@ The next step is to configure Fiddler to intercept encrypted traffic and decrypt
   
     
     
-![Figure 5. UI for utilizing local HOSTS file](../../images/ngDebuggingSP2013Workflows05.png)
+![Figure 5. UI for utilizing local HOSTS file](../images/ngDebuggingSP2013Workflows05.png)
   
     
     
@@ -333,7 +334,7 @@ Next, configure Fiddler's connection options.
 
   
 
-  ![Figure 6. Fiddler connection options](../../images/ngDebuggingSP2013Workflows06.png)
+  ![Figure 6. Fiddler connection options](../images/ngDebuggingSP2013Workflows06.png)
   
 
   
@@ -374,7 +375,7 @@ This process will configure Windows to trust the certificate, although SharePoin
   
     
     
-![Figure 7. HTTPS tab](../../images/ngDebuggingSP2013Workflows07.png)
+![Figure 7. HTTPS tab](../images/ngDebuggingSP2013Workflows07.png)
   
     
     
@@ -474,7 +475,7 @@ In the figure below, notice that sessions #18-36 originated from SharePoint and
   
     
     
-![Figure 8. Starting Workflow](../../images/ngDebuggingSP2013Workflows08.png)
+![Figure 8. Starting Workflow](../images/ngDebuggingSP2013Workflows08.png)
   
     
     
@@ -492,7 +493,7 @@ Notice that in session #36, SharePoint is requesting that Workflow Manager start
   
     
     
-![Figure 10. Success message](../../images/ngDebuggingSP2013Workflows10.png)
+![Figure 10. Success message](../images/ngDebuggingSP2013Workflows10.png)
   
     
     
@@ -510,7 +511,7 @@ Session #40 is where Workflow Manager is retrieving the list item ID and GUID fr
   
     
     
-![Figure 10. Retrieving list item ID and GUID](../../images/ngDebuggingSP2013Workflows11.png)
+![Figure 10. Retrieving list item ID and GUID](../images/ngDebuggingSP2013Workflows11.png)
   
     
     
@@ -528,7 +529,7 @@ Session #43 is where Workflow Manager is updating the list item in SharePoint wi
   
     
     
-![Figure 11. Updating the list item in SharePoint](../../images/ngDebuggingSP2013Workflows12.png)
+![Figure 11. Updating the list item in SharePoint](../images/ngDebuggingSP2013Workflows12.png)
   
     
     
diff --git a/docs/general-development/deciding-between-sharepoint-add-ins-and-sharepoint-solutions.md b/docs/general-development/deciding-between-sharepoint-add-ins-and-sharepoint-solutions.md
index a7f49524da..7a46d851c8 100644
--- a/docs/general-development/deciding-between-sharepoint-add-ins-and-sharepoint-solutions.md
+++ b/docs/general-development/deciding-between-sharepoint-add-ins-and-sharepoint-solutions.md
@@ -1,13 +1,14 @@
 ---
 title: Deciding between SharePoint Add-ins and SharePoint solutions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8459e265-b8fd-4bf8-911e-d63cae8bf96f
 ---
 
 
 # Deciding between SharePoint Add-ins and SharePoint solutions
 
-This content is obsolete. See  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions). 
+This content is obsolete. See  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md). 
   
     
     
diff --git a/docs/general-development/develop-access-web-apps.md b/docs/general-development/develop-access-web-apps.md
index 247b81aa65..4cf193dc43 100644
--- a/docs/general-development/develop-access-web-apps.md
+++ b/docs/general-development/develop-access-web-apps.md
@@ -1,6 +1,7 @@
 ---
 title: Develop Access web apps
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 41131b27-d750-4d11-b3c7-c17ad4d666e2
 ---
 
@@ -30,7 +31,7 @@ Access 2013 uses Microsoft SharePoint to host the front end of your application
   
     
     
-For more information about what's new in Access 2013 apps, see  [What's new in Access](what-s-new-in-access)
+For more information about what's new in Access 2013 apps, see  [What's new in Access](what-s-new-in-access.md)
   
     
     
@@ -51,7 +52,7 @@ For more information about how to develop Access 2013 apps, see  [How to: Create
 <a name="dk2_DevelopingAccess15WebApps_AdditionalResources"> </a>
 
 
--  [What's new in Access](what-s-new-in-access)
+-  [What's new in Access](what-s-new-in-access.md)
     
   
 -  [How to: Create and customize a web app in Access](http://msdn.microsoft.com/library/628745f4-82e9-4838-9726-6f3e506a654f%28Office.15%29.aspx)
diff --git a/docs/general-development/develop-sharepoint-workflows-using-visual-studio.md b/docs/general-development/develop-sharepoint-workflows-using-visual-studio.md
index af3ba1910c..ef9a93c258 100644
--- a/docs/general-development/develop-sharepoint-workflows-using-visual-studio.md
+++ b/docs/general-development/develop-sharepoint-workflows-using-visual-studio.md
@@ -1,6 +1,7 @@
----
+---
 title: Develop SharePoint workflows using Visual Studio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 28f5d3b1-6fe8-4b1f-8c4e-b11105fe6f46
 ---
 
@@ -13,7 +14,7 @@ SharePoint supports two primary workflow development environments for authoring
 
 
 > **Note:**
-> For guidance on setting up and configuring Microsoft SharePoint and the Workflow Manager Client 1.0 server, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager). 
+> For guidance on setting up and configuring Microsoft SharePoint and the Workflow Manager Client 1.0 server, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md). 
   
     
     
@@ -24,7 +25,7 @@ As with previous versions, Microsoft SharePoint provides two primary workflow de
     
 
 > **Note:**
-> As a complement to authoring workflows in SharePoint Designer, you can also use Microsoft Visio 2013 to structure your workflow logic by using Visio 2013 shapes, and then import your logic into SharePoint Designer 2013. For information about using Visio 2013 to author your workflow logic, see  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio). 
+> As a complement to authoring workflows in SharePoint Designer, you can also use Microsoft Visio 2013 to structure your workflow logic by using Visio 2013 shapes, and then import your logic into SharePoint Designer 2013. For information about using Visio 2013 to author your workflow logic, see  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md). 
   
     
     
diff --git a/docs/general-development/develop-the-site-design-in-sharepoint.md b/docs/general-development/develop-the-site-design-in-sharepoint.md
index 3ea425775f..6229a182f2 100644
--- a/docs/general-development/develop-the-site-design-in-sharepoint.md
+++ b/docs/general-development/develop-the-site-design-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Develop the site design in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4c061484-2ba5-45ea-9860-aec9d7c8f80e
 ---
 
@@ -13,16 +14,16 @@ If you want your SharePoint site to represent your organization's brand and not
     
 
 For more information about using Design Manager to customize your sites, see the following articles and their subtopics:
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint) : Get an overview of using Design Manager to brand your SharePoint site. Design Manager is a publishing feature that is available in publishing sites in both SharePoint and Office 365.
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md) : Get an overview of using Design Manager to brand your SharePoint site. Design Manager is a publishing feature that is available in publishing sites in both SharePoint and Office 365.
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model) : Learn about the revised page model—including master pages and page layouts—redesigned for SharePoint.
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md) : Learn about the revised page model—including master pages and page layouts—redesigned for SharePoint.
     
   
--  [Master pages, the Master Page Gallery, and page layouts in SharePoint](master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint) : Find links to information about using Design Manager to work with master pages, page layouts, and display templates in publishing sites in SharePoint.
+-  [Master pages, the Master Page Gallery, and page layouts in SharePoint](master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md) : Find links to information about using Design Manager to work with master pages, page layouts, and display templates in publishing sites in SharePoint.
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities) : Find links to information about using Design Manager branding and design capabilities in SharePoint.
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md) : Find links to information about using Design Manager branding and design capabilities in SharePoint.
     
   
 
@@ -30,10 +31,10 @@ For more information about using Design Manager to customize your sites, see the
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
 
diff --git a/docs/general-development/developing-with-duet-enterprise-2-0.md b/docs/general-development/developing-with-duet-enterprise-2-0.md
index 5226b3c791..c838322b40 100644
--- a/docs/general-development/developing-with-duet-enterprise-2-0.md
+++ b/docs/general-development/developing-with-duet-enterprise-2-0.md
@@ -1,6 +1,7 @@
 ---
 title: Developing with Duet Enterprise 2.0
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c3ef38aa-559e-4832-95c7-75e222c77624
 ---
 
@@ -56,7 +57,7 @@ Developing SharePoint Add-ins using Duet Enterprise 2.0, for the most part, is e
 ## Adding external content types
 <a name="AddingECT"> </a>
 
-In order to access the external data housed on the SAP system, you will have to add an external content type. Since SAP data is exposed through OData endpoints, the auto-generation tools installed in Visual Studio can be used to  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint) that is scoped at the app level.
+In order to access the external data housed on the SAP system, you will have to add an external content type. Since SAP data is exposed through OData endpoints, the auto-generation tools installed in Visual Studio can be used to  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md) that is scoped at the app level.
   
     
     
@@ -158,7 +159,7 @@ These solutions can be used to see what can be done with Duet Enterprise 2.0 and
 -  [Duet Enterprise for Microsoft SharePoint and SAP Server 2.0](http://technet.microsoft.com/en-us/library/ff972436.aspx)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
 -  [Visual Studio Developer Center](http://msdn.microsoft.com/en-us/vstudio/default)
diff --git a/docs/general-development/discovery-in-excel-services-rest-api.md b/docs/general-development/discovery-in-excel-services-rest-api.md
index b5bdc6eb25..a410217218 100644
--- a/docs/general-development/discovery-in-excel-services-rest-api.md
+++ b/docs/general-development/discovery-in-excel-services-rest-api.md
@@ -1,6 +1,7 @@
----
+---
 title: Discovery in Excel Services REST API
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e3a8e057-f803-446d-81c9-4eb8ef3691e1
 ---
 
@@ -39,7 +40,7 @@ Following is the construct of the REST URL to a specific element in a workbook:
 http://<ServerName>/_vti_bin/ExcelRest.aspx/<DocumentLibrary>/<FileName>/<ResourceLocation>
 ```
 
-As described in the  [Basic URI Structure and Path](basic-uri-structure-and-path) topic, following is the REST URL to access a workbook named **sampleWorkbook.xlsx** and further view the chart called **SampleChart**: 
+As described in the  [Basic URI Structure and Path](basic-uri-structure-and-path.md) topic, following is the REST URL to access a workbook named **sampleWorkbook.xlsx** and further view the chart called **SampleChart**: 
   
     
     
@@ -86,7 +87,7 @@ Following is a screen shot of the model page.
   
     
     
-![Excel Services REST model URL](../../images/SharePointServer14Con_XLSvcs_RESTModel.gif)
+![Excel Services REST model URL](../images/SharePointServer14Con_XLSvcs_RESTModel.gif)
   
     
     
@@ -109,7 +110,7 @@ For example, to access the chart in the workbook by using discovery, do the foll
 
   
 
-  ![Excel Services REST discovery chart list](../../images/19126dce-b896-4623-8686-92f2fa807283.gif)
+  ![Excel Services REST discovery chart list](../images/19126dce-b896-4623-8686-92f2fa807283.gif)
   
 
   
@@ -121,7 +122,7 @@ For example, to access the chart in the workbook by using discovery, do the foll
 
   
 
-  ![Viewing chart using REST](../../images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif)
+  ![Viewing chart using REST](../images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif)
   
 
   
@@ -203,4 +204,4 @@ As can be seen in the XML, the feed contains traversable elements that enable co
   
     
     
- [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api)
+ [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api.md)
diff --git a/docs/general-development/ediscovery-in-sharepoint.md b/docs/general-development/ediscovery-in-sharepoint.md
index 80709d80d0..f15d642017 100644
--- a/docs/general-development/ediscovery-in-sharepoint.md
+++ b/docs/general-development/ediscovery-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: eDiscovery in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 45cb324a-75f5-444d-a0fa-5c223df19016
 ---
 
@@ -116,7 +117,7 @@ SharePoint provides a Microsoft .NET server programming model that you can use t
 <a name="SP15_eDiscoveryInSP_AdditionalResources"> </a>
 
 
--  [What's new in SharePoint eDiscovery and compliance](what-s-new-in-sharepoint-ediscovery-and-compliance)
+-  [What's new in SharePoint eDiscovery and compliance](what-s-new-in-sharepoint-ediscovery-and-compliance.md)
     
   
 -  [Complete basic operations using SharePoint client library code](http://msdn.microsoft.com/library/5a69c9e3-73bf-4ed5-bc19-182056bdb394%28Office.15%29.aspx)
diff --git a/docs/general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint.md b/docs/general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint.md
index 7f8e81d322..377da06c40 100644
--- a/docs/general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint.md
+++ b/docs/general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Enhancing the BDC model file for Search in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3c67b1cf-5fca-4805-a1b5-c9ac1ff8aede
 ---
 
@@ -181,7 +182,7 @@ Profile pages may require that you use the Secure Store Service because of the m
 <a name="SP15enhanceBDC_addlresources"> </a>
 
 
--  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint)
+-  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md)
     
   
 -  [BDC Model Infrastructure](http://msdn.microsoft.com/library/2818ebdd-6cda-4d8f-82b2-7fde9fbf2633%28Office.15%29.aspx)
@@ -190,7 +191,7 @@ Profile pages may require that you use the Secure Store Service because of the m
 -  [Authoring BDC Models](http://msdn.microsoft.com/library/170d1cfd-cf19-4162-b79f-ba6d3b4ad23b%28Office.15%29.aspx)
     
   
--  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint)
+-  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint.md)
     
   
 -  [How to: Use SharePoint Designer to Create a BDC Model File for a Custom Connector](http://msdn.microsoft.com/library/8f239482-0c82-4b60-817d-b0c4392e7e2e%28Office.15%29.aspx)
diff --git a/docs/general-development/excel-services-alerts.md b/docs/general-development/excel-services-alerts.md
index af7245c24f..fe5c9904f3 100644
--- a/docs/general-development/excel-services-alerts.md
+++ b/docs/general-development/excel-services-alerts.md
@@ -1,9 +1,10 @@
----
+---
 title: Excel Services Alerts
+ms.date: 09/25/2017
 keywords: errors
 f1_keywords:
 - errors
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: a4e7030b-05c2-484e-b21f-46cba937b803
 ---
 
@@ -92,23 +93,23 @@ For general information about exception handling, see "Handling and Throwing Exc
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Error Codes](excel-services-error-codes)
+ [Excel Services Error Codes](excel-services-error-codes.md)
 #### Other resources
 
 
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/excel-services-architecture.md b/docs/general-development/excel-services-architecture.md
index 2297aec1ae..b652564c55 100644
--- a/docs/general-development/excel-services-architecture.md
+++ b/docs/general-development/excel-services-architecture.md
@@ -1,9 +1,10 @@
----
+---
 title: Excel Services Architecture
+ms.date: 09/25/2017
 keywords: excel services design
 f1_keywords:
 - excel services design
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: e0349b4a-2d52-46c4-a167-801e9c24eaca
 ---
 
@@ -51,7 +52,7 @@ The Excel Web Access, Excel Web Services, UDFs, JavaScript, the REST service, an
   
     
     
-![A Web front end and a back-end application server](../../images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif)
+![A Web front end and a back-end application server](../images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif)
   
     
     
@@ -103,14 +104,14 @@ Excel Web Services is the Excel Services component that provides programmatic ac
     
     
 
-For more information about Excel Web Services, see  [Excel Services Development Roadmap](excel-services-development-roadmap).
+For more information about Excel Web Services, see  [Excel Services Development Roadmap](excel-services-development-roadmap.md).
   
     
     
 
 ## User-Defined Functions (UDFs)
 
-Excel Services UDFs enable you to use formulas in a cell to call custom functions that are written in managed code and deployed to SharePoint Server 2010. For more information about UDFs in Excel Services, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs).
+Excel Services UDFs enable you to use formulas in a cell to call custom functions that are written in managed code and deployed to SharePoint Server 2010. For more information about UDFs in Excel Services, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs.md).
   
     
     
@@ -136,7 +137,7 @@ The discovery mechanisms built into the Excel Services REST API enables develope
   
     
     
-For more information about the REST API in Excel Services, see  [Excel Services REST API](excel-services-rest-api). 
+For more information about the REST API in Excel Services, see  [Excel Services REST API](excel-services-rest-api.md). 
   
     
     
@@ -168,19 +169,19 @@ Administrators can configure the load-balancing behavior.
   
     
     
- [Excel Services Overview](excel-services-overview)
+ [Excel Services Overview](excel-services-overview.md)
   
     
     
- [Excel Services Development Roadmap](excel-services-development-roadmap)
+ [Excel Services Development Roadmap](excel-services-development-roadmap.md)
   
     
     
- [Supported and Unsupported Features](supported-and-unsupported-features)
+ [Supported and Unsupported Features](supported-and-unsupported-features.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/excel-services-best-practices.md b/docs/general-development/excel-services-best-practices.md
index 982db03c3c..8a790e46e3 100644
--- a/docs/general-development/excel-services-best-practices.md
+++ b/docs/general-development/excel-services-best-practices.md
@@ -1,9 +1,10 @@
----
+---
 title: Excel Services Best Practices
+ms.date: 09/25/2017
 keywords: guidelines
 f1_keywords:
 - guidelines
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 56fa3913-c156-49da-bed0-a6a106fc129f
 ---
 
@@ -211,27 +212,27 @@ For example, use CompanyName.Hierarchichal.Namespace.ClassName instead ofNamespa
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+ [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
diff --git a/docs/general-development/excel-services-blogs-forums-and-resources.md b/docs/general-development/excel-services-blogs-forums-and-resources.md
index 5ca3676161..0f5517e1ed 100644
--- a/docs/general-development/excel-services-blogs-forums-and-resources.md
+++ b/docs/general-development/excel-services-blogs-forums-and-resources.md
@@ -1,9 +1,10 @@
 ---
 title: Excel Services Blogs, Forums, and Resources
+ms.date: 09/25/2017
 keywords: blogger
 f1_keywords:
 - blogger
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: c0b137cd-126d-4c74-a3f7-eb9debe3c35f
 ---
 
@@ -48,34 +49,34 @@ The following are links to blogs, forums, and additional resources related to Ex
   
     
     
- [Excel Services Overview](excel-services-overview)
+ [Excel Services Overview](excel-services-overview.md)
   
     
     
- [Excel Services Development Roadmap](excel-services-development-roadmap)
+ [Excel Services Development Roadmap](excel-services-development-roadmap.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
   
     
     
diff --git a/docs/general-development/excel-services-development-roadmap.md b/docs/general-development/excel-services-development-roadmap.md
index 955bbe3036..15eaf38fc2 100644
--- a/docs/general-development/excel-services-development-roadmap.md
+++ b/docs/general-development/excel-services-development-roadmap.md
@@ -1,9 +1,10 @@
----
+---
 title: Excel Services Development Roadmap
+ms.date: 09/25/2017
 keywords: roadmap
 f1_keywords:
 - roadmap
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 5c789f58-9cdb-4601-9047-9c6f83f2fbba
 ---
 
@@ -138,11 +139,11 @@ You can use Excel Web Services as:
 - A local assembly, by linking directly to **Microsoft.Office.Excel.Server.Webservices.dll**.
     
   
-For more information about when you should link directly to **Microsoft.Office.Excel.Server.Webservices.dll**, see  [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking). 
+For more information about when you should link directly to **Microsoft.Office.Excel.Server.Webservices.dll**, see  [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md). 
   
     
     
-For information about the Excel Web Services API, see the  [Microsoft.Office.Excel.Server.Webservices](https://msdn.microsoft.com/library/Microsoft.Office.Excel.Server.Webservices.aspx) namespace reference documentation. For an example of how to develop a custom application by using Excel Web Services, see [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services).
+For information about the Excel Web Services API, see the  [Microsoft.Office.Excel.Server.Webservices](https://msdn.microsoft.com/library/Microsoft.Office.Excel.Server.Webservices.aspx) namespace reference documentation. For an example of how to develop a custom application by using Excel Web Services, see [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md).
   
     
     
@@ -166,7 +167,7 @@ Excel Services supports managed-code UDFs. Excel Services UDFs give you the abil
 - Wrap calls to existing native code library functions—for example, existing Excel UDFs.
     
   
-For more information about Excel Services UDFs, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs). 
+For more information about Excel Services UDFs, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs.md). 
   
     
     
@@ -177,7 +178,7 @@ For information about Excel Services UDF definitions, see the  [Microsoft.Office
   
     
     
-For an example of how to create managed-code UDFs, see  [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf).
+For an example of how to create managed-code UDFs, see  [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md).
   
     
     
@@ -237,7 +238,7 @@ For more information about JavaScript, see the following links:
 - For more information about the JavaScript object model in Excel Services, see the  [Ewa](http://msdn.microsoft.com/library/6fe73191-3213-b986-1ad6-2c3b918a2241%28Office.15%29.aspx) namespace reference documentation.
     
   
-- For an example of how to interact with the JavaScript object model in Excel Services by using the Content Editor Web Part, see  [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part).
+- For an example of how to interact with the JavaScript object model in Excel Services by using the Content Editor Web Part, see  [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part.md).
     
   
 
@@ -255,7 +256,7 @@ Using the Atom feed provided by the REST API enables an easier way to get to the
   
     
     
-For more information, see  [Excel Services REST API](excel-services-rest-api).
+For more information, see  [Excel Services REST API](excel-services-rest-api.md).
   
     
     
@@ -267,10 +268,10 @@ For information about:
     
     
 
-- Accessing the REST service, and to view sample URIs for the REST service in Excel Services, see  [Accessing Excel Services REST API](sample-uri-for-excel-services-rest-api).
+- Accessing the REST service, and to view sample URIs for the REST service in Excel Services, see  [Accessing Excel Services REST API](sample-uri-for-excel-services-rest-api.md).
     
   
-- Accessing a schema for the REST service in Excel Services, see  [Accessing a Schema](accessing-a-schema).
+- Accessing a schema for the REST service in Excel Services, see  [Accessing a Schema](accessing-a-schema.md).
     
   
 
@@ -283,30 +284,30 @@ For information about:
   
     
     
- [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page)
+ [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Overview](excel-services-overview)
+ [Excel Services Overview](excel-services-overview.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Supported and Unsupported Features](supported-and-unsupported-features)
+ [Supported and Unsupported Features](supported-and-unsupported-features.md)
   
     
     
- [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+ [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/excel-services-ecmascript-javascript-jscript.md b/docs/general-development/excel-services-ecmascript-javascript-jscript.md
index 141f654017..efebcf73a0 100644
--- a/docs/general-development/excel-services-ecmascript-javascript-jscript.md
+++ b/docs/general-development/excel-services-ecmascript-javascript-jscript.md
@@ -1,6 +1,7 @@
 ---
 title: Excel Services ECMAScript (JavaScript, JScript)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2355ffd0-8190-4385-955c-3f72bce7efc6
 ---
 
@@ -16,21 +17,21 @@ This section contains information about ECMAScript (JavaScript, JScript) in Exce
 ## Related sections
 
 
- [Excel Services ECMAScript Overview](excel-services-ecmascript-overview)
+ [Excel Services ECMAScript Overview](excel-services-ecmascript-overview.md)
   
     
     
 > Learn about the JavaScript object model in Excel Services.
     
   
- [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part)
+ [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part.md)
   
     
     
 > Learn how to call the JavaScript object model in Excel Services by using the Content Editor Web Part.
     
   
- [JavaScript user-defined functions overview](javascript-user-defined-functions-overview)
+ [JavaScript user-defined functions overview](javascript-user-defined-functions-overview.md)
   
     
     
@@ -47,4 +48,4 @@ This section contains information about ECMAScript (JavaScript, JScript) in Exce
   
     
     
- [Excel Services Development Roadmap](excel-services-development-roadmap)
+ [Excel Services Development Roadmap](excel-services-development-roadmap.md)
diff --git a/docs/general-development/excel-services-ecmascript-overview.md b/docs/general-development/excel-services-ecmascript-overview.md
index 30d32833e8..ac41b26060 100644
--- a/docs/general-development/excel-services-ecmascript-overview.md
+++ b/docs/general-development/excel-services-ecmascript-overview.md
@@ -1,6 +1,7 @@
 ---
 title: Excel Services ECMAScript Overview
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f8c1be86-df19-44c3-a3bc-c0da2b80df10
 ---
 
@@ -50,7 +51,7 @@ For more information, see the following links:
 - For more information about the JavaScript object model in Excel Services, see the  [Ewa](http://msdn.microsoft.com/library/6fe73191-3213-b986-1ad6-2c3b918a2241%28Office.15%29.aspx) namespace reference documentation.
     
   
-- For an example of how to interact with the JavaScript object model in Excel Services by using the Content Editor Web Part, see  [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part).
+- For an example of how to interact with the JavaScript object model in Excel Services by using the Content Editor Web Part, see  [Walkthrough: Developing Using the Content Editor Web Part](walkthrough-developing-using-the-content-editor-web-part.md).
     
   
 
diff --git a/docs/general-development/excel-services-error-codes.md b/docs/general-development/excel-services-error-codes.md
index fba9e6031f..a4eef550a7 100644
--- a/docs/general-development/excel-services-error-codes.md
+++ b/docs/general-development/excel-services-error-codes.md
@@ -1,9 +1,10 @@
 ---
 title: Excel Services Error Codes
+ms.date: 09/25/2017
 keywords: alerts
 f1_keywords:
 - alerts
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: ff128d67-f3ac-4a8f-ae8e-1e19e343014e
 ---
 
@@ -15,8 +16,8 @@ Excel Services generates errors and error messages in the SOAP exception based o
     
     
 
-You use the  [SubCode](http://msdn.microsoft.com/library/frlrfSystemWebServicesProtocolsSoapExceptionClassSubCodeTopic.aspx) property of the **SoapException** class to capture the error codes. For more information about using the **SubCode** property to capture error codes, see [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes)
-For more information about Excel Services alerts, see  [Excel Services Alerts](excel-services-alerts). 
+You use the  [SubCode](http://msdn.microsoft.com/library/frlrfSystemWebServicesProtocolsSoapExceptionClassSubCodeTopic.aspx) property of the **SoapException** class to capture the error codes. For more information about using the **SubCode** property to capture error codes, see [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes.md)
+For more information about Excel Services alerts, see  [Excel Services Alerts](excel-services-alerts.md). 
   
     
     
@@ -70,19 +71,19 @@ The following table lists the error codes for Excel Web Services alerts and the
   
     
     
- [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes)
+ [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
diff --git a/docs/general-development/excel-services-in-sharepoint.md b/docs/general-development/excel-services-in-sharepoint.md
index 8a3c12a39a..4f4ede4d05 100644
--- a/docs/general-development/excel-services-in-sharepoint.md
+++ b/docs/general-development/excel-services-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Excel Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f7e13fcb-a86a-4a1e-af59-3bace98ce9d7
 ---
 
@@ -36,7 +37,7 @@ SharePoint Server 2010 introduced the REST API for use in getting and setting in
 
 
 > **Note:**
-> The Excel Interactive View feature has been disabled. For information about removing this feature from your website, see  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage). 
+> The Excel Interactive View feature has been disabled. For information about removing this feature from your website, see  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage.md). 
   
     
     
@@ -46,28 +47,28 @@ SharePoint Server 2010 introduced the REST API for use in getting and setting in
 <a name="xlsWhatsNew"> </a>
 
 
--  [Getting Started with Excel Services](getting-started-with-excel-services)
+-  [Getting Started with Excel Services](getting-started-with-excel-services.md)
     
   
--  [Excel Web Services](excel-web-services)
+-  [Excel Web Services](excel-web-services.md)
     
   
--  [Excel Services User-Defined Functions](excel-services-user-defined-functions)
+-  [Excel Services User-Defined Functions](excel-services-user-defined-functions.md)
     
   
--  [Excel Web Access](excel-web-access)
+-  [Excel Web Access](excel-web-access.md)
     
   
--  [Excel Services ECMAScript (JavaScript, JScript)](excel-services-ecmascript-javascript-jscript)
+-  [Excel Services ECMAScript (JavaScript, JScript)](excel-services-ecmascript-javascript-jscript.md)
     
   
--  [Excel Services REST API](excel-services-rest-api)
+-  [Excel Services REST API](excel-services-rest-api.md)
     
   
--  [General Guidelines](general-guidelines)
+-  [General Guidelines](general-guidelines.md)
     
   
--  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage)
+-  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage.md)
     
   
 
@@ -75,10 +76,10 @@ SharePoint Server 2010 introduced the REST API for use in getting and setting in
 <a name="bk_addresources"> </a>
 
 
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Office 2013 and SharePoint application services](office-and-sharepoint-application-services)
+-  [Office 2013 and SharePoint application services](office-and-sharepoint-application-services.md)
     
   
 
diff --git a/docs/general-development/excel-services-known-issues-and-tips.md b/docs/general-development/excel-services-known-issues-and-tips.md
index 117db830b2..c4559c63bf 100644
--- a/docs/general-development/excel-services-known-issues-and-tips.md
+++ b/docs/general-development/excel-services-known-issues-and-tips.md
@@ -1,6 +1,7 @@
----
+---
 title: Excel Services Known Issues and Tips
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b4a41437-4f00-4f88-8510-627fa0252004
 ---
 
@@ -30,7 +31,7 @@ If you do not have a custom site, you can view the WSDL by using the following U
   
     
     
-For more information, see  [Accessing the SOAP API](accessing-the-soap-api).
+For more information, see  [Accessing the SOAP API](accessing-the-soap-api.md).
   
     
     
@@ -58,7 +59,7 @@ In certain scenarios, you should link directly to Microsoft.Office.Excel.Server.
   
     
     
-For more information and guidelines on when to use direct linking, see  [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking).
+For more information and guidelines on when to use direct linking, see  [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md).
   
     
     
@@ -96,7 +97,7 @@ When you make changes to a workbook—for example, by setting values to a range
   
     
     
-If you want to save changes to a workbook, you can use the **GetWorkbook** method and then save the workbook using the API of the destination file store. For more information, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot) and [How to: Save a Workbook](http://msdn.microsoft.com/library/feb74f7a-2d8f-4672-911b-de85f8852aea%28Office.15%29.aspx).
+If you want to save changes to a workbook, you can use the **GetWorkbook** method and then save the workbook using the API of the destination file store. For more information, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md) and [How to: Save a Workbook](http://msdn.microsoft.com/library/feb74f7a-2d8f-4672-911b-de85f8852aea%28Office.15%29.aspx).
   
     
     
@@ -175,7 +176,7 @@ The workbooks you want to open in Excel Services must be placed in a trusted loc
   
     
     
-For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx).
+For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location.md) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx).
   
     
     
@@ -296,31 +297,31 @@ You should not write an application that assumes the order of strings in the sha
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Supported and Unsupported Features](supported-and-unsupported-features)
+ [Supported and Unsupported Features](supported-and-unsupported-features.md)
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+ [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
diff --git a/docs/general-development/excel-services-overview.md b/docs/general-development/excel-services-overview.md
index ec6a396aa8..47ab730175 100644
--- a/docs/general-development/excel-services-overview.md
+++ b/docs/general-development/excel-services-overview.md
@@ -1,6 +1,7 @@
----
+---
 title: Excel Services Overview
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5fa22ebb-e507-4ffc-a425-e755502feae2
 ---
 
@@ -33,14 +34,14 @@ There are four primary interfaces for Excel Services:
   
 
 > **Note:**
-> The Excel Interactive View feature has been disabled. For information about removing this feature from your website, see  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage). 
+> The Excel Interactive View feature has been disabled. For information about removing this feature from your website, see  [Removing Excel Interactive View from a webpage](removing-excel-interactive-view-from-a-webpage.md). 
   
     
     
 
 You can also extend Excel Calculation Services by using user-defined functions (UDFs).
 > **Note:**
-> For more information about Excel Calculation Services, see  [Excel Services Architecture](excel-services-architecture). 
+> For more information about Excel Calculation Services, see  [Excel Services Architecture](excel-services-architecture.md). 
   
     
     
@@ -54,7 +55,7 @@ By using Excel Services, you can view live, interactive workbooks by using only
 
 Excel Services also has a Web service. You can use Excel Web Services to load workbooks, set values in cells and ranges, refresh external data connections, calculate worksheets, and extract calculated results (including cell values, the entire calculated workbook, or a snapshot of the workbook). In SharePoint, you can also save, save a copy, and participate in collaborative editing sessions by using Excel Web Services.
 > **Note:**
-> For more information about snapshots, see  [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot). 
+> For more information about snapshots, see  [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md). 
   
     
     
@@ -91,7 +92,7 @@ Excel Services also enables you to calculate data on the server. Excel Services
   
     
     
-![Dashboard with filtering and Excel content](../../images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF)
+![Dashboard with filtering and Excel content](../images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF)
   
     
     
@@ -121,7 +122,7 @@ If you want to use certain functionalities in Excel or if you want to analyze a
   
     
     
-![Using the Parameters pane](../../images/65926095-d833-4eb2-b899-9efe40e2d540.GIF)
+![Using the Parameters pane](../images/65926095-d833-4eb2-b899-9efe40e2d540.GIF)
   
     
     
@@ -182,7 +183,7 @@ You can also use Excel Services UDFs, which enable you to use formulas in a cell
   
     
     
-For more information about UDFs in Excel Services, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs).
+For more information about UDFs in Excel Services, see  [Understanding Excel Services UDFs](understanding-excel-services-udfs.md).
   
     
     
@@ -234,7 +235,7 @@ You can use the REST API in Excel Services to access workbook parts or elements
   
     
     
-For more information about the REST API in Excel Services, see  [Excel Services REST API](excel-services-rest-api).
+For more information about the REST API in Excel Services, see  [Excel Services REST API](excel-services-rest-api.md).
   
     
     
@@ -269,28 +270,28 @@ From there you can use OData system query options to get specific information ab
 ## Additional resources
 
 
--  [Excel Services Development Roadmap](excel-services-development-roadmap)
+-  [Excel Services Development Roadmap](excel-services-development-roadmap.md)
     
   
--  [Excel Services Architecture](excel-services-architecture)
+-  [Excel Services Architecture](excel-services-architecture.md)
     
   
--  [JavaScript user-defined functions overview](javascript-user-defined-functions-overview)
+-  [JavaScript user-defined functions overview](javascript-user-defined-functions-overview.md)
     
   
--  [Using OData with Excel Services REST in SharePoint](using-odata-with-excel-services-rest-in-sharepoint)
+-  [Using OData with Excel Services REST in SharePoint](using-odata-with-excel-services-rest-in-sharepoint.md)
     
   
--  [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+-  [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
     
   
--  [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+-  [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
     
   
 -  [Unsupported Features in Excel Services](http://msdn.microsoft.com/library/5868e672-4786-4fed-9168-07ff538f6f5c%28Office.15%29.aspx)
     
   
--  [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+-  [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
     
   
 
diff --git a/docs/general-development/excel-services-rest-api-overview.md b/docs/general-development/excel-services-rest-api-overview.md
index c29ebe2595..c5d9776af1 100644
--- a/docs/general-development/excel-services-rest-api-overview.md
+++ b/docs/general-development/excel-services-rest-api-overview.md
@@ -1,6 +1,7 @@
 ---
 title: Excel Services REST API Overview
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5872f311-e180-4578-ac80-2519c1081951
 ---
 
@@ -39,4 +40,4 @@ REST services are resource-centric. With REST, data is divided into resources, e
     
     
 
-A REST API for Excel Services enables operations against Excel workbooks by using operations specified in the HTTP standard. This allows for a flexible, secure, and simpler mechanism to access and manipulate Excel Services content.The discovery mechanisms built into the Excel Services REST API also enable developers and users to explore the content of the workbook manually or programmatically by supplying an  [Atom](http://tools.ietf.org/html/rfc4287) feed that contains information about the elements that reside in a specific workbook. Some examples of the resources that you can access through the REST API are charts, PivotTables, and tables.Using the Atom feed provided by the REST API is an easier way of getting to the data that you care about. The feed contains traversable elements that enable any piece of code to discover what elements exist in a workbook. For information about accessing the REST service and obtaining sample URIs for the REST service in Excel Services, see  [Basic URI Structure and Path](basic-uri-structure-and-path) and [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api).
+A REST API for Excel Services enables operations against Excel workbooks by using operations specified in the HTTP standard. This allows for a flexible, secure, and simpler mechanism to access and manipulate Excel Services content.The discovery mechanisms built into the Excel Services REST API also enable developers and users to explore the content of the workbook manually or programmatically by supplying an  [Atom](http://tools.ietf.org/html/rfc4287) feed that contains information about the elements that reside in a specific workbook. Some examples of the resources that you can access through the REST API are charts, PivotTables, and tables.Using the Atom feed provided by the REST API is an easier way of getting to the data that you care about. The feed contains traversable elements that enable any piece of code to discover what elements exist in a workbook. For information about accessing the REST service and obtaining sample URIs for the REST service in Excel Services, see  [Basic URI Structure and Path](basic-uri-structure-and-path.md) and [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api.md).
diff --git a/docs/general-development/excel-services-rest-api.md b/docs/general-development/excel-services-rest-api.md
index e958c6a0d2..8f2fd28dad 100644
--- a/docs/general-development/excel-services-rest-api.md
+++ b/docs/general-development/excel-services-rest-api.md
@@ -1,6 +1,7 @@
----
+---
 title: Excel Services REST API
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 32033fea-873c-4781-900a-6946906066b0
 ---
 
@@ -24,63 +25,63 @@ This section contains information about the Representational State Transfer (RES
 ## Related sections
 
 
- [Excel Services REST API Overview](excel-services-rest-api-overview)
+ [Excel Services REST API Overview](excel-services-rest-api-overview.md)
   
     
     
 > Learn about the REST API in Excel Services.
     
   
- [Basic URI Structure and Path](basic-uri-structure-and-path)
+ [Basic URI Structure and Path](basic-uri-structure-and-path.md)
   
     
     
 > Learn how to construct the URI structure and path for the REST service commands in Excel Services.
     
   
- [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api)
+ [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api.md)
   
     
     
 > Learn about the discovery mechanisms built into the REST API in Excel Services.
     
   
- [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api)
+ [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api.md)
   
     
     
 > Learn the entities that you can link directly to by using the REST API in Excel Services.
     
   
- [Getting Ranges Using Atom Feed and HTML Fragment](getting-ranges-using-atom-feed-and-html-fragment)
+ [Getting Ranges Using Atom Feed and HTML Fragment](getting-ranges-using-atom-feed-and-html-fragment.md)
   
     
     
 > Learn to access ranges—Atom feeds and HTML fragments—by using the REST API in Excel Services.
     
   
- [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api)
+ [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api.md)
   
     
     
 > Provides a sample URI for the REST service commands in Excel Services.
     
   
- [Accessing a Schema](accessing-a-schema)
+ [Accessing a Schema](accessing-a-schema.md)
   
     
     
 > Learn how to access and look at a schema for the REST service in Excel Services.
     
   
- [Unsupported Features in Excel Services REST API](unsupported-features-in-excel-services-rest-api)
+ [Unsupported Features in Excel Services REST API](unsupported-features-in-excel-services-rest-api.md)
   
     
     
 > Lists some of the more important features that are currently not supported or working in the Excel Services REST API.
     
   
- [Advanced Scenarios and Additional Samples](advanced-scenarios-and-additional-samples)
+ [Advanced Scenarios and Additional Samples](advanced-scenarios-and-additional-samples.md)
   
     
     
diff --git a/docs/general-development/excel-services-user-defined-functions.md b/docs/general-development/excel-services-user-defined-functions.md
index 57a31911a1..9c9d716501 100644
--- a/docs/general-development/excel-services-user-defined-functions.md
+++ b/docs/general-development/excel-services-user-defined-functions.md
@@ -1,9 +1,10 @@
 ---
 title: Excel Services User-Defined Functions
+ms.date: 09/25/2017
 keywords: functions
 f1_keywords:
 - functions
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 27dd8024-7e00-40de-a688-afc67c880603
 ---
 
@@ -19,56 +20,56 @@ This section contains information about user-defined functions (UDFs) and how to
 ## In this section
 
 
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
   
     
     
 > Learn about managed-code UDFs, including required attributes, deployment, and security.
     
   
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
 > Get step-by-step instructions about developing Excel Services UDFs by using Microsoft Visual C#.
     
   
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
 > Find answers to the most common questions about Excel Services UDFs.
     
   
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
   
     
     
 > Learn how to enable UDFs and allow them to be called from an Excel workbook.
     
   
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
 > Learn how to call an external Web service from a UDF.
     
   
- [How to: Access an External Data Source from a UDF](how-to-access-an-external-data-source-from-a-udf)
+ [How to: Access an External Data Source from a UDF](how-to-access-an-external-data-source-from-a-udf.md)
   
     
     
 > Get an example showing how to access an external database from a UDF.
     
   
- [How to: Deploy UDFs Using SharePoint Foundation Solutions](how-to-deploy-udfs-using-sharepoint-foundation-solutions)
+ [How to: Deploy UDFs Using SharePoint Foundation Solutions](how-to-deploy-udfs-using-sharepoint-foundation-solutions.md)
   
     
     
 > Learn how to deploy a UDF by using the s solution framework.
     
   
- [How to: Restrict UDF Code Access Security Permissions](how-to-restrict-udf-code-access-security-permissions)
+ [How to: Restrict UDF Code Access Security Permissions](how-to-restrict-udf-code-access-security-permissions.md)
   
     
     
diff --git a/docs/general-development/excel-web-access.md b/docs/general-development/excel-web-access.md
index 35acdb3449..f43f69686e 100644
--- a/docs/general-development/excel-web-access.md
+++ b/docs/general-development/excel-web-access.md
@@ -1,6 +1,7 @@
 ---
 title: Excel Web Access
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: eef8991d-0844-4b35-a092-33c957102dee
 ---
 
@@ -16,14 +17,14 @@ This section describes the Excel Web Access Web Part and explains how to use it.
 ## In this section
 
 
- [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page)
+ [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md)
   
     
     
 > Learn how to programmatically add an Excel Web Access Web Part to a SharePoint page, and how to programmatically display a workbook in an Excel Web Access Web Part.
     
   
- [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc)
+ [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md)
   
     
     
@@ -51,4 +52,4 @@ This section describes the Excel Web Access Web Part and explains how to use it.
   
     
     
- [Excel Services Development Roadmap](excel-services-development-roadmap)
+ [Excel Services Development Roadmap](excel-services-development-roadmap.md)
diff --git a/docs/general-development/excel-web-services.md b/docs/general-development/excel-web-services.md
index bcef4dee7b..ef10699d6d 100644
--- a/docs/general-development/excel-web-services.md
+++ b/docs/general-development/excel-web-services.md
@@ -1,6 +1,7 @@
 ---
 title: Excel Web Services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e30ef4e3-72ff-43de-beba-b377141d4d19
 ---
 
@@ -16,35 +17,35 @@ This section contains information about Excel Web Services and explains how to u
 ## In this section
 
 
- [What's New in Excel Web Services](what-s-new-in-excel-web-services)
+ [What's New in Excel Web Services](what-s-new-in-excel-web-services.md)
   
     
     
 > Learn about the new types and members added to Excel Web Services in Microsoft SharePoint Server 2010.
     
   
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
 > Learn how to call the Web service by referencing the Excel Web Services Web Services Description Language (WSDL).
     
   
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
   
     
     
 > Learn when to link to Microsoft.Office.Excel.Server.WebServices.dll locally.
     
   
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
   
     
     
 > Get step-by-step instructions about how to create a Web service client application that accesses Excel Web Services.
     
   
- [Excel Services Error Codes](excel-services-error-codes)
+ [Excel Services Error Codes](excel-services-error-codes.md)
   
     
     
@@ -58,7 +59,7 @@ This section contains information about Excel Web Services and explains how to u
 > Learn how to set credentials for your users so that they can call Excel Web Services by using your custom applications.
     
   
- [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot)
+ [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md)
   
     
     
@@ -72,42 +73,42 @@ This section contains information about Excel Web Services and explains how to u
 > Learn about using the various libraries in the Microsoft .NET Framework to save a workbook.
     
   
- [How to: Get Values from Ranges](how-to-get-values-from-ranges)
+ [How to: Get Values from Ranges](how-to-get-values-from-ranges.md)
   
     
     
 > See examples of the four methods for getting values from an Excel workbook.
     
   
- [How to: Set Values of Ranges](how-to-set-values-of-ranges)
+ [How to: Set Values of Ranges](how-to-set-values-of-ranges.md)
   
     
     
 > Learn how to use the four methods for setting values in an Excel workbook.
     
   
- [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name)
+ [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name.md)
   
     
     
 > Learn how to specify range addresses by using range coordinates, named ranges, rows, and columns. Also learn how to specify a sheet name, and about the relationship between a sheet name and a range address.
     
   
- [How to: Use the CloseWorkbook Method Call Asynchronously](how-to-use-the-closeworkbook-method-call-asynchronously)
+ [How to: Use the CloseWorkbook Method Call Asynchronously](how-to-use-the-closeworkbook-method-call-asynchronously.md)
   
     
     
 > Find out how to close a workbook asynchronously to save some operation time.
     
   
- [How to: Refresh Data](how-to-refresh-data)
+ [How to: Refresh Data](how-to-refresh-data.md)
   
     
     
 > Learn how you can use the **Refresh** method to retrieve updated data from external data sources for an open workbook.
     
   
- [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes)
+ [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes.md)
   
     
     
diff --git a/docs/general-development/exporting-and-importing-search-configuration-settings-in-sharepoint.md b/docs/general-development/exporting-and-importing-search-configuration-settings-in-sharepoint.md
index b8a95fb6de..6c7a1665ab 100644
--- a/docs/general-development/exporting-and-importing-search-configuration-settings-in-sharepoint.md
+++ b/docs/general-development/exporting-and-importing-search-configuration-settings-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Exporting and importing search configuration settings in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d00679a3-ffa2-4281-ad8b-70fc2c4a14e2
 ---
 
@@ -62,7 +63,7 @@ private static void Import(string fileName)
 <a name="bk_addresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
 -  [Export and import customized search configuration settings in SharePoint](http://technet.microsoft.com/en-us/library/jj871675.aspx)
diff --git a/docs/general-development/extend-the-fixed-format-export-feature-in-word-automation-services.md b/docs/general-development/extend-the-fixed-format-export-feature-in-word-automation-services.md
index 53d2236d62..1d18f1ab5e 100644
--- a/docs/general-development/extend-the-fixed-format-export-feature-in-word-automation-services.md
+++ b/docs/general-development/extend-the-fixed-format-export-feature-in-word-automation-services.md
@@ -1,6 +1,7 @@
 ---
 title: Extend the fixed-format export feature in Word Automation Services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d8375505-432e-438e-971b-221a1d9bb601
 ---
 
diff --git a/docs/general-development/external-content-types-in-sharepoint.md b/docs/general-development/external-content-types-in-sharepoint.md
index 4a298c3e86..4a43e7cfa9 100644
--- a/docs/general-development/external-content-types-in-sharepoint.md
+++ b/docs/general-development/external-content-types-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: External content types in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 11d7adb5-5388-4517-ae03-beb7be1c6981
 ---
 
@@ -67,7 +68,7 @@ To get started creating external content types, you will need the following:
 - SharePoint Designer 2013
     
   
-To set up a development environment for creating external content types, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+To set up a development environment for creating external content types, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -129,27 +130,27 @@ Table 1 contains examples of tasks that illustrate working with external content
 
 |**Task**|**Description**|
 |:-----|:-----|
-| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source, and create a reusable external content type for use in SharePoint Business Connectivity Services (BCS).  <br/> |
-| [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint) <br/> |Learn how to create an external content type based on a SQL Server database.  <br/> |
+| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source, and create a reusable external content type for use in SharePoint Business Connectivity Services (BCS).  <br/> |
+| [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint.md) <br/> |Learn how to create an external content type based on a SQL Server database.  <br/> |
    
 
 ## Additional resources
 <a name="SP15ectoverview_addres"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint)
+-  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md)
     
   
--  [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint)
+-  [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/external-events-and-alerts-in-sharepoint.md b/docs/general-development/external-events-and-alerts-in-sharepoint.md
index 88b2d42c7f..f21d4637b6 100644
--- a/docs/general-development/external-events-and-alerts-in-sharepoint.md
+++ b/docs/general-development/external-events-and-alerts-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: External events and alerts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e48e4812-a185-43c5-b243-04b1d79b88ee
 ---
 
@@ -102,7 +103,7 @@ To use event receivers for external lists, you need the following:
 - Visual Studio 2012
     
   
-For more information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For more information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -178,7 +179,7 @@ In Figure 1, notice that there are three distinct steps involved when using exte
   
     
     
-![Data flow for external event notifications](../../images/ExtEvtsAndAlrts_Figure1.jpg)
+![Data flow for external event notifications](../images/ExtEvtsAndAlrts_Figure1.jpg)
   
     
     
@@ -212,7 +213,7 @@ Figure 2 demonstrates the flow of information between SharePoint and the externa
   
     
     
-![External eventing Subscribe method process flow](../../images/ExtEvtsAndAlerts_Figure2.jpg)
+![External eventing Subscribe method process flow](../images/ExtEvtsAndAlerts_Figure2.jpg)
   
     
     
@@ -408,7 +409,7 @@ Figure 3 shows the communication flow between the external system and SharePoint
   
     
     
-![External event notification process](../../images/ExtEvtsAndAlerts_Figure3.jpg)
+![External event notification process](../images/ExtEvtsAndAlerts_Figure3.jpg)
   
     
     
@@ -499,7 +500,7 @@ The **Unsubscribe** operation removes a subscription from the notifications list
   
     
     
-![External notifications unsubscribe process](../../images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg)
+![External notifications unsubscribe process](../images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg)
   
     
     
@@ -645,23 +646,23 @@ For more information about external events and alerts, see the following.
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system) <br/> |Learn how to create an Internet-addressable Windows Communication Foundation (WCF) service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
+| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md) <br/> |Learn how to create an Internet-addressable Windows Communication Foundation (WCF) service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
    
 
 ## Additional resources
 <a name="Externalevents_Addres"> </a>
 
 
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
--  [How to: Create external event receivers](how-to-create-external-event-receivers)
+-  [How to: Create external event receivers](how-to-create-external-event-receivers.md)
     
   
 
diff --git a/docs/general-development/fast-query-language-fql-syntax-reference.md b/docs/general-development/fast-query-language-fql-syntax-reference.md
index 3e8bc75ea5..82ba4a548c 100644
--- a/docs/general-development/fast-query-language-fql-syntax-reference.md
+++ b/docs/general-development/fast-query-language-fql-syntax-reference.md
@@ -1,6 +1,7 @@
 ---
 title: FAST Query Language (FQL) syntax reference
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bd98a41b-623c-41d4-a15d-26c0d4ba4311
 ---
 
@@ -317,11 +318,11 @@ Table 3 lists the types of operators supported by FQL.
 
 |**Type**|**Description**|**Operators**|
 |:-----|:-----|:-----|
-|String  <br/> |Enables you to specify query operations on a string of terms. This is the most common operator to use on text terms.  <br/> | [STRING](fast-query-language-fql-syntax-reference#fql_string_operator) <br/> |
-|Boolean  <br/> |Enables you to combine terms and sub-expressions in a query.  <br/> | [AND](fast-query-language-fql-syntax-reference#fql_and_operator),  [OR](fast-query-language-fql-syntax-reference#fql_or_operator),  [ANY](fast-query-language-fql-syntax-reference#fql_any_operator),  [ANDNOT](fast-query-language-fql-syntax-reference#fql_andnot_operator),  [NOT](fast-query-language-fql-syntax-reference#fql_not_operator),  [COUNT](fast-query-language-fql-syntax-reference#fql_count_operator),  [COUNT](fast-query-language-fql-syntax-reference#fql_count_operator) <br/> |
-|Proximity  <br/> |Enables you to specify the proximity of the query terms in a matching sequence of text.  <br/> | [NEAR](fast-query-language-fql-syntax-reference#fql_near_operator),  [ONEAR](fast-query-language-fql-syntax-reference#fql_onear_operator),  [PHRASE](fast-query-language-fql-syntax-reference#fql_phrase_operator),  [STARTS-WITH](fast-query-language-fql-syntax-reference#fql_startswith_operator),  [ENDS-WITH](fast-query-language-fql-syntax-reference#fql_endswith_operator),  [EQUALS](fast-query-language-fql-syntax-reference#fql_equals_operator) <br/> |
-|Numeric  <br/> |Enables you to specify numeric conditions in the query.  <br/> | [RANGE](fast-query-language-fql-syntax-reference#fql_range_operator) , [INT](fast-query-language-fql-syntax-reference#fql_int_operator),  [FLOAT](fast-query-language-fql-syntax-reference#fql_float_operator),  [DATETIME](fast-query-language-fql-syntax-reference#fql_datetime_operator),  [DECIMAL](#fql_decimal_operator) <br/> |
-|Relevance  <br/> |Enables you to impact the relevance evaluation of a query.  <br/> | [XRANK](fast-query-language-fql-syntax-reference#fql_xrank_operator) and  [FILTER](fast-query-language-fql-syntax-reference#fql_filter_operator) <br/> |
+|String  <br/> |Enables you to specify query operations on a string of terms. This is the most common operator to use on text terms.  <br/> | [STRING](fast-query-language-fql-syntax-reference.md#fql_string_operator) <br/> |
+|Boolean  <br/> |Enables you to combine terms and sub-expressions in a query.  <br/> | [AND](fast-query-language-fql-syntax-reference.md#fql_and_operator),  [OR](fast-query-language-fql-syntax-reference.md#fql_or_operator),  [ANY](fast-query-language-fql-syntax-reference.md#fql_any_operator),  [ANDNOT](fast-query-language-fql-syntax-reference.md#fql_andnot_operator),  [NOT](fast-query-language-fql-syntax-reference.md#fql_not_operator),  [COUNT](fast-query-language-fql-syntax-reference.md#fql_count_operator),  [COUNT](fast-query-language-fql-syntax-reference.md#fql_count_operator) <br/> |
+|Proximity  <br/> |Enables you to specify the proximity of the query terms in a matching sequence of text.  <br/> | [NEAR](fast-query-language-fql-syntax-reference.md#fql_near_operator),  [ONEAR](fast-query-language-fql-syntax-reference.md#fql_onear_operator),  [PHRASE](fast-query-language-fql-syntax-reference.md#fql_phrase_operator),  [STARTS-WITH](fast-query-language-fql-syntax-reference.md#fql_startswith_operator),  [ENDS-WITH](fast-query-language-fql-syntax-reference.md#fql_endswith_operator),  [EQUALS](fast-query-language-fql-syntax-reference.md#fql_equals_operator) <br/> |
+|Numeric  <br/> |Enables you to specify numeric conditions in the query.  <br/> | [RANGE](fast-query-language-fql-syntax-reference.md#fql_range_operator) , [INT](fast-query-language-fql-syntax-reference.md#fql_int_operator),  [FLOAT](fast-query-language-fql-syntax-reference.md#fql_float_operator),  [DATETIME](fast-query-language-fql-syntax-reference.md#fql_datetime_operator),  [DECIMAL](#fql_decimal_operator) <br/> |
+|Relevance  <br/> |Enables you to impact the relevance evaluation of a query.  <br/> | [XRANK](fast-query-language-fql-syntax-reference.md#fql_xrank_operator) and  [FILTER](fast-query-language-fql-syntax-reference.md#fql_filter_operator) <br/> |
    
 Table 4 provides a list of the supported operators.
   
@@ -333,26 +334,26 @@ Table 4 provides a list of the supported operators.
 
 |**Operator**|**Description**|**Type**|
 |:-----|:-----|:-----|
-| [AND](fast-query-language-fql-syntax-reference#fql_and_operator) <br/> |Returns only items that match all **AND** operands. <br/> |Boolean  <br/> |
-| [ANDNOT](fast-query-language-fql-syntax-reference#fql_andnot_operator) <br/> |Returns only items that match the first operand and that don't match the subsequent operands.  <br/> |Boolean  <br/> |
-| [ANY](fast-query-language-fql-syntax-reference#fql_any_operator) <br/> |Similar to the **OR** operator except that the dynamic rank (the relevance score in the result set) is affected by neither the number of operands that match nor the distance between the terms in the item. <br/> |Boolean  <br/> |
-| [COUNT](fast-query-language-fql-syntax-reference#fql_count_operator) <br/> |Enables you to specify the number of query term occurrences an item must include to be returned as a result. The operand may be a single query term, a phrase, or wildcard query term.  <br/> |Boolean  <br/> |
-| [DATETIME](fast-query-language-fql-syntax-reference#fql_datetime_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
-| [DECIMAL](fast-query-language-fql-syntax-reference#fql_decimal_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
-| [ENDS-WITH](fast-query-language-fql-syntax-reference#fql_endswith_operator) <br/> |Specifies that a word or phrase must appear in the end of a managed property.  <br/> |Proximity  <br/> |
-| [EQUALS](fast-query-language-fql-syntax-reference#fql_equals_operator) <br/> |Specifies that a word or phrase term or phrase must provide an exact token match with the managed property.  <br/> |Proximity  <br/> |
-| [FILTER](fast-query-language-fql-syntax-reference#fql_filter_operator) <br/> |Used to query metadata or other structured data.  <br/> |Relevance  <br/> |
-| [FLOAT](fast-query-language-fql-syntax-reference#fql_float_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
-| [INT](fast-query-language-fql-syntax-reference#fql_int_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
-| [NEAR](fast-query-language-fql-syntax-reference#fql_near_operator) <br/> |Restricts the result set to items that have  `N` terms within a certain distance of one another. <br/> |Proximity  <br/> |
-| [NOT](fast-query-language-fql-syntax-reference#fql_not_operator) <br/> |Returns only items that exclude the operand.  <br/> |Boolean  <br/> |
-| [ONEAR](fast-query-language-fql-syntax-reference#fql_onear_operator) <br/> |The ordered variant of **NEAR**, and requires an ordered match of the terms. The **ONEAR** operator can be used to restrict the result set to items that have `N` terms within a certain distance of Returns only items that don't match the operand. The operand may be any valid FQL expression.one another. <br/> |Proximity  <br/> |
-| [OR](fast-query-language-fql-syntax-reference#fql_or_operator) <br/> |Returns only items that match at least one of the **OR** operands. Items that match will get a higher dynamic rank (relevance score in the result set) if more of the **OR** operands match. <br/> |Boolean  <br/> |
-| [PHRASE](fast-query-language-fql-syntax-reference#fql_phrase_operator) <br/> | Returns only items that match an exact string of tokens. <br/> |Proximity  <br/> |
-| [RANGE](fast-query-language-fql-syntax-reference#fql_range_operator) <br/> | Enables range matching expressions. The **RANGE** operator is used for numeric and date/time managed properties. <br/> |Numeric  <br/> |
-| [STARTS-WITH](fast-query-language-fql-syntax-reference#fql_startswith_operator) <br/> |Specifies that a word or phrase must appear in the start of a managed property.  <br/> |Proximity  <br/> |
-| [STRING](fast-query-language-fql-syntax-reference#fql_string_operator) <br/> |Define a Boolean matching condition to a text string.  <br/> |String  <br/> |
-| [XRANK](fast-query-language-fql-syntax-reference#fql_xrank_operator) <br/> |Enables you to boost the dynamic rank of items based on certain term occurrences without changing which items match the query. A **XRANK** expression contains one component that must be matched, and one or more components that contribute only to dynamic ranking. <br/> |Relevance  <br/> |
+| [AND](fast-query-language-fql-syntax-reference.md#fql_and_operator) <br/> |Returns only items that match all **AND** operands. <br/> |Boolean  <br/> |
+| [ANDNOT](fast-query-language-fql-syntax-reference.md#fql_andnot_operator) <br/> |Returns only items that match the first operand and that don't match the subsequent operands.  <br/> |Boolean  <br/> |
+| [ANY](fast-query-language-fql-syntax-reference.md#fql_any_operator) <br/> |Similar to the **OR** operator except that the dynamic rank (the relevance score in the result set.md) is affected by neither the number of operands that match nor the distance between the terms in the item. <br/> |Boolean  <br/> |
+| [COUNT](fast-query-language-fql-syntax-reference.md#fql_count_operator) <br/> |Enables you to specify the number of query term occurrences an item must include to be returned as a result. The operand may be a single query term, a phrase, or wildcard query term.  <br/> |Boolean  <br/> |
+| [DATETIME](fast-query-language-fql-syntax-reference.md#fql_datetime_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
+| [DECIMAL](fast-query-language-fql-syntax-reference.md#fql_decimal_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
+| [ENDS-WITH](fast-query-language-fql-syntax-reference.md#fql_endswith_operator) <br/> |Specifies that a word or phrase must appear in the end of a managed property.  <br/> |Proximity  <br/> |
+| [EQUALS](fast-query-language-fql-syntax-reference.md#fql_equals_operator) <br/> |Specifies that a word or phrase term or phrase must provide an exact token match with the managed property.  <br/> |Proximity  <br/> |
+| [FILTER](fast-query-language-fql-syntax-reference.md#fql_filter_operator) <br/> |Used to query metadata or other structured data.  <br/> |Relevance  <br/> |
+| [FLOAT](fast-query-language-fql-syntax-reference.md#fql_float_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
+| [INT](fast-query-language-fql-syntax-reference.md#fql_int_operator) <br/> |Provides explicit typing of numeric values.  <br/> The explicit type conversion is optional and usually is not needed. The type of the query term is detected according to the type of the target numeric managed property.  <br/> |Numeric  <br/> |
+| [NEAR](fast-query-language-fql-syntax-reference.md#fql_near_operator) <br/> |Restricts the result set to items that have  `N` terms within a certain distance of one another. <br/> |Proximity  <br/> |
+| [NOT](fast-query-language-fql-syntax-reference.md#fql_not_operator) <br/> |Returns only items that exclude the operand.  <br/> |Boolean  <br/> |
+| [ONEAR](fast-query-language-fql-syntax-reference.md#fql_onear_operator) <br/> |The ordered variant of **NEAR**, and requires an ordered match of the terms. The **ONEAR** operator can be used to restrict the result set to items that have `N` terms within a certain distance of Returns only items that don't match the operand. The operand may be any valid FQL expression.one another. <br/> |Proximity  <br/> |
+| [OR](fast-query-language-fql-syntax-reference.md#fql_or_operator) <br/> |Returns only items that match at least one of the **OR** operands. Items that match will get a higher dynamic rank (relevance score in the result set.md) if more of the **OR** operands match. <br/> |Boolean  <br/> |
+| [PHRASE](fast-query-language-fql-syntax-reference.md#fql_phrase_operator) <br/> | Returns only items that match an exact string of tokens. <br/> |Proximity  <br/> |
+| [RANGE](fast-query-language-fql-syntax-reference.md#fql_range_operator) <br/> | Enables range matching expressions. The **RANGE** operator is used for numeric and date/time managed properties. <br/> |Numeric  <br/> |
+| [STARTS-WITH](fast-query-language-fql-syntax-reference.md#fql_startswith_operator) <br/> |Specifies that a word or phrase must appear in the start of a managed property.  <br/> |Proximity  <br/> |
+| [STRING](fast-query-language-fql-syntax-reference.md#fql_string_operator) <br/> |Define a Boolean matching condition to a text string.  <br/> |String  <br/> |
+| [XRANK](fast-query-language-fql-syntax-reference.md#fql_xrank_operator) <br/> |Enables you to boost the dynamic rank of items based on certain term occurrences without changing which items match the query. A **XRANK** expression contains one component that must be matched, and one or more components that contribute only to dynamic ranking. <br/> |Relevance  <br/> |
    
 
 > **Note:**
@@ -446,7 +447,7 @@ Not applicable.
     
     
 
-Similar to the  [OR](fast-query-language-fql-syntax-reference#fql_or_operator) operator except that the dynamic rank (the relevance score in the result set) is affected by neither the number of operands that match nor the distance between the terms in the item. The operands may be a single term or any valid FQL sub-expression.
+Similar to the  [OR](fast-query-language-fql-syntax-reference.md#fql_or_operator) operator except that the dynamic rank (the relevance score in the result set) is affected by neither the number of operands that match nor the distance between the terms in the item. The operands may be a single term or any valid FQL sub-expression.
   
     
     
@@ -557,7 +558,7 @@ The following table contains examples of managed property string values and stat
 ### DATETIME
 <a name="fql_datetime_operator"> </a>
 
-Provides explicit typing of date/time numeric values. The operand is a date/time string formatted according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference#token_expressions).
+Provides explicit typing of date/time numeric values. The operand is a date/time string formatted according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference.md#token_expressions).
   
     
     
@@ -583,7 +584,7 @@ Not applicable.
 ### DECIMAL
 <a name="fql_decimal_operator"> </a>
 
-Provides explicit typing of decimal values. The operand is a decimal value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference#token_expressions).
+Provides explicit typing of decimal values. The operand is a decimal value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference.md#token_expressions).
   
     
     
@@ -704,7 +705,7 @@ The following example will match items with the values "Adam Jones" in the "auth
 
 #### Remarks
 
-See also  [ENDS-WITH](fast-query-language-fql-syntax-reference#fql_endswith_operator).
+See also  [ENDS-WITH](fast-query-language-fql-syntax-reference.md#fql_endswith_operator).
   
     
     
@@ -788,7 +789,7 @@ If you must filter a large set of values, you should consider using numeric valu
 ### FLOAT
 <a name="fql_float_operator"> </a>
 
-Provides explicit typing of floating point numeric values. The operand is a floating point value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference#token_expressions).
+Provides explicit typing of floating point numeric values. The operand is a floating point value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference.md#token_expressions).
   
     
     
@@ -814,7 +815,7 @@ Not applicable.
 ### INT
 <a name="fql_int_operator"> </a>
 
-Provides explicit typing of integer values. The operand is an integer value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference#token_expressions).
+Provides explicit typing of integer values. The operand is an integer value according to the syntax specified in  [Token expressions in FQL](fast-query-language-fql-syntax-reference.md#token_expressions).
   
     
     
@@ -961,7 +962,7 @@ If you use **ONEAR** or **NEAR** with equal operands, the operator will work as
   
     
     
-This query will always return **true** if at least one instance of '' `a`'' appears within the context. This also means that **NEAR** cannot be used as a **COUNT** operator. For more information about counting term occurrences, see the [COUNT](fast-query-language-fql-syntax-reference#fql_count_operator) operator.
+This query will always return **true** if at least one instance of '' `a`'' appears within the context. This also means that **NEAR** cannot be used as a **COUNT** operator. For more information about counting term occurrences, see the [COUNT](fast-query-language-fql-syntax-reference.md#fql_count_operator) operator.
   
     
     
@@ -1073,7 +1074,7 @@ The following table contains examples of managed property string values, and sta
 
 #### Remarks
 
-See also  [NEAR](fast-query-language-fql-syntax-reference#fql_near_operator).
+See also  [NEAR](fast-query-language-fql-syntax-reference.md#fql_near_operator).
   
     
     
@@ -1139,7 +1140,7 @@ Not applicable.
 
 #### Remarks
 
-See also  [STRING](fast-query-language-fql-syntax-reference#fql_string_operator).
+See also  [STRING](fast-query-language-fql-syntax-reference.md#fql_string_operator).
   
     
     
@@ -1217,7 +1218,7 @@ The following expression will match items with the values "Adam Jones sr" and "A
 
 #### Remarks
 
-For additional remarks on boundary matching, see  [ENDS-WITH](fast-query-language-fql-syntax-reference#fql_endswith_operator).
+For additional remarks on boundary matching, see  [ENDS-WITH](fast-query-language-fql-syntax-reference.md#fql_endswith_operator).
   
     
     
@@ -1475,7 +1476,7 @@ Boosts the dynamic rank of items based on certain term occurrences within the  _
   
     
     
-![Formula for XRANK operator](../../images/XRANKFormula.gif)
+![Formula for XRANK operator](../images/XRANKFormula.gif)
   
     
     
@@ -1568,6 +1569,6 @@ The following advanced parameters are also available. However, typically they ar
 <a name="SP15FQL_addlresources"> </a>
 
 
--  [Building search queries in SharePoint](building-search-queries-in-sharepoint)
+-  [Building search queries in SharePoint](building-search-queries-in-sharepoint.md)
     
   
diff --git a/docs/general-development/follow-content-in-sharepoint.md b/docs/general-development/follow-content-in-sharepoint.md
index 8bd2e3d96c..de199c789c 100644
--- a/docs/general-development/follow-content-in-sharepoint.md
+++ b/docs/general-development/follow-content-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Follow content in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 30e68cd6-6e55-4cf9-afd6-7139b0a97288
 ---
 
@@ -40,7 +41,7 @@ SharePoint provides the following APIs that you can use to programmatically foll
 - Server object model
     
   
-As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, a JavaScript object model, and a REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, a JavaScript object model, and a REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -50,7 +51,7 @@ Each API includes a manager object that you use to perform core tasks for follow
     
 
 > **Note:**
-> The same APIs are used to follow people. See  [Follow people in SharePoint](follow-people-in-sharepoint) for an overview of Following People tasks.
+> The same APIs are used to follow people. See  [Follow people in SharePoint](follow-people-in-sharepoint.md) for an overview of Following People tasks.
   
     
     
@@ -71,9 +72,9 @@ Table 1 shows the manager and other key objects (or REST resources) in the APIs
 
 |**API**|**Key objects**|
 |:-----|:-----|
-|.NET client object model  <br/> See:  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep)|Manager object:            [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) , [SocialActorInfo](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorInfo.aspx) , [SocialActorType](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorType.aspx) , [SocialActorTypes](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorTypes.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll  |
+|.NET client object model  <br/> See:  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md)|Manager object:            [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) , [SocialActorInfo](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorInfo.aspx) , [SocialActorType](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorType.aspx) , [SocialActorTypes](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorTypes.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll  |
 |JavaScript object model|Manager object:            [SocialFollowingManager](http://msdn.microsoft.com/library/9ee1c0c0-b864-f0c3-f0cb-4dd4f1870dfa%28Office.15%29.aspx) <br/> Primary namespace:            [SP.Social](http://msdn.microsoft.com/library/43d47f01-c085-0e77-bd01-48bcb7d5bb35%28Office.15%29.aspx) <br/> Other key objects:            [SocialActor](http://msdn.microsoft.com/library/4e369fd5-b9b0-9804-957e-b3e39c559cd4%28Office.15%29.aspx),  [SocialActorInfo](http://msdn.microsoft.com/library/d940db32-1561-c868-bb66-0612e2031f17%28Office.15%29.aspx),  [SocialActorType](http://msdn.microsoft.com/library/fbde74da-f292-dc87-0b7e-81bc5b7a880c%28Office.15%29.aspx),  [SocialActorTypes](http://msdn.microsoft.com/library/a460c3e6-ed88-117d-6755-4c5803a154a0%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js  |
-|REST service  <br/> See  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2)|Manager resource:            [social.following](following-people-and-content-rest-api-reference-for-sharepoint) <br/> Primary namespace (OData):           **sp.social.SocialRestFollowingManager** <br/> Other key resources:           **SocialActor**, **SocialActorInfo**, **SocialActorType**, **SocialActorTypes** <br/> Access point:            `<siteUri>/_api/social.following` |
+|REST service  <br/> See  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md)|Manager resource:            [social.following](following-people-and-content-rest-api-reference-for-sharepoint.md) <br/> Primary namespace (OData):           **sp.social.SocialRestFollowingManager** <br/> Other key resources:           **SocialActor**, **SocialActorInfo**, **SocialActorType**, **SocialActorTypes** <br/> Access point:            `<siteUri>/_api/social.following` |
 |Server object model|Manager object:            [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.Office.Server.Social](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.aspx) <br/> Other key objects:            [SPSocialActor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActor.aspx) , [SPSocialActorInfo](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorInfo.aspx) , [SPSocialActorType](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorType.aspx) , [SPSocialActorTypes](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorTypes.aspx) <br/> Class library:           Microsoft.Office.Server.UserProfiles.dll  |
    
 
@@ -86,7 +87,7 @@ Table 2 shows common programming tasks for following content and the members tha
     
 
 > **Note:**
-> The same APIs are used to follow people. See  [Follow people in SharePoint](follow-people-in-sharepoint) for an overview of Following People tasks.
+> The same APIs are used to follow people. See  [Follow people in SharePoint](follow-people-in-sharepoint.md) for an overview of Following People tasks.
   
     
     
@@ -99,16 +100,16 @@ Table 2 shows common programming tasks for following content and the members tha
 |:-----|:-----|
 |Create an instance of a manager object in the context of the current user|CSOM:  [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> JSOM:  [SocialFollowingManager](http://msdn.microsoft.com/library/9ee1c0c0-b864-f0c3-f0cb-4dd4f1870dfa%28Office.15%29.aspx) <br/> REST:  `<siteUri>/_api/social.following` <br/> SSOM:  [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx)|
 |Create an instance of a manager object in the context of a specified user|CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM:  [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx) (overloaded)|
-|Have the current user start following (stop following) an item|CSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.StopFollowing.aspx) ) <br/> JSOM:  [follow](http://msdn.microsoft.com/library/40d14320-27ba-2941-b0e2-be3b5a407c89%28Office.15%29.aspx) ( [stopFollowing](http://msdn.microsoft.com/library/65b0e9be-dc5e-09fb-c57f-7a933de09a4c%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.following/Follow`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Follow) ( [`<siteUri>/_api/social.following/StopFollowing`](following-people-and-content-rest-api-reference-for-sharepoint#bk_StopFollowing))           and pass the _actor_ parameter in the request body <br/> SSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.StopFollowing.aspx) )|
-|Find out whether the current user is following a particular item|CSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.IsFollowed.aspx) <br/> JSOM:  [isFollowed](http://msdn.microsoft.com/library/2c1f62e6-fb75-ad4d-c081-36408b418c21%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.following/IsFollowed`](following-people-and-content-rest-api-reference-for-sharepoint#bk_IsFollowed) and pass the _actor_ parameter in the request body <br/> SSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.IsFollowed.aspx)|
-|Get the documents, sites, and/or tags that the current user is following|CSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowed.aspx) <br/> JSOM:  [getFollowed](http://msdn.microsoft.com/library/432a7cec-6add-fdb1-a79f-a93414ee8cd3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followed(types=2)`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Followed) (documents = **2**, sites = **4**, tags = **8**)  <br/> SSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowed.aspx)|
-|Get the count of documents, sites, and/or tags that the user is following|CSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowedCount.aspx) <br/> JSOM:  [getFollowedCount](http://msdn.microsoft.com/library/97b53b4f-481a-cf41-1854-8f3ff860b2bb%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedCount(types=2)`](following-people-and-content-rest-api-reference-for-sharepoint#bk_FollowedCount) (documents = **2**, sites = **4**, tags = **8**)  <br/> SSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowedCount.aspx)|
-|Get the URI of the site that lists the current user's followed documents|CSOM:  [FollowedDocumentsUri](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.FollowedDocumentsUri.aspx) <br/> JSOM:  [followedDocumentsUri](http://msdn.microsoft.com/library/3a70b9c7-abd7-94ff-d730-70298673d6ec%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedDocumentsUri`](following-people-and-content-rest-api-reference-for-sharepoint#bk_MyFollowedDocumentsUri) <br/> SSOM:  [FollowedDocumentsUri](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.FollowedDocumentsUri.aspx)|
-|Get the URI of the site that lists the current user's followed sites|CSOM:  [FollowedSitesUri](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.FollowedSitesUri.aspx) <br/> JSOM:  [followedSitesUri](http://msdn.microsoft.com/library/829404bc-1b3a-7545-5e95-0922df330084%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedSitesUri`](following-people-and-content-rest-api-reference-for-sharepoint#bk_MyFollowedSitesUri) <br/> SSOM:  [FollowedSitesUri](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.FollowedSitesUri.aspx)|
+|Have the current user start following (stop following) an item|CSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.StopFollowing.aspx) ) <br/> JSOM:  [follow](http://msdn.microsoft.com/library/40d14320-27ba-2941-b0e2-be3b5a407c89%28Office.15%29.aspx) ( [stopFollowing](http://msdn.microsoft.com/library/65b0e9be-dc5e-09fb-c57f-7a933de09a4c%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.following/Follow`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Follow) ( [`<siteUri>/_api/social.following/StopFollowing`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_StopFollowing))           and pass the _actor_ parameter in the request body <br/> SSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.StopFollowing.aspx) )|
+|Find out whether the current user is following a particular item|CSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.IsFollowed.aspx) <br/> JSOM:  [isFollowed](http://msdn.microsoft.com/library/2c1f62e6-fb75-ad4d-c081-36408b418c21%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.following/IsFollowed`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_IsFollowed) and pass the _actor_ parameter in the request body <br/> SSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.IsFollowed.aspx)|
+|Get the documents, sites, and/or tags that the current user is following|CSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowed.aspx) <br/> JSOM:  [getFollowed](http://msdn.microsoft.com/library/432a7cec-6add-fdb1-a79f-a93414ee8cd3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followed(types=2)`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Followed) (documents = **2**, sites = **4**, tags = **8**.md)  <br/> SSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowed.aspx)|
+|Get the count of documents, sites, and/or tags that the user is following|CSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowedCount.aspx) <br/> JSOM:  [getFollowedCount](http://msdn.microsoft.com/library/97b53b4f-481a-cf41-1854-8f3ff860b2bb%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedCount(types=2)`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_FollowedCount) (documents = **2**, sites = **4**, tags = **8**.md)  <br/> SSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowedCount.aspx)|
+|Get the URI of the site that lists the current user's followed documents|CSOM:  [FollowedDocumentsUri](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.FollowedDocumentsUri.aspx) <br/> JSOM:  [followedDocumentsUri](http://msdn.microsoft.com/library/3a70b9c7-abd7-94ff-d730-70298673d6ec%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedDocumentsUri`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_MyFollowedDocumentsUri) <br/> SSOM:  [FollowedDocumentsUri](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.FollowedDocumentsUri.aspx)|
+|Get the URI of the site that lists the current user's followed sites|CSOM:  [FollowedSitesUri](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.FollowedSitesUri.aspx) <br/> JSOM:  [followedSitesUri](http://msdn.microsoft.com/library/829404bc-1b3a-7545-5e95-0922df330084%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedSitesUri`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_MyFollowedSitesUri) <br/> SSOM:  [FollowedSitesUri](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.FollowedSitesUri.aspx)|
    
 
 > **Note:**
-> For examples that show how to use the REST service to follow content, see  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2). 
+> For examples that show how to use the REST service to follow content, see  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md). 
   
     
     
@@ -164,21 +165,21 @@ function getTagGuid() {
 <a name="bk_addResources"> </a>
 
 
--  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep)
+-  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md)
     
   
--  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2)
+-  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md)
     
   
--  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)
+-  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)
     
   
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
diff --git a/docs/general-development/follow-people-in-sharepoint.md b/docs/general-development/follow-people-in-sharepoint.md
index 27f43bdae1..b9b8bb50fa 100644
--- a/docs/general-development/follow-people-in-sharepoint.md
+++ b/docs/general-development/follow-people-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Follow people in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0fa2e235-63d0-41b1-9eed-4aeb2f59a14d
 ---
 
@@ -40,7 +41,7 @@ SharePoint provides the following APIs that you can use to programmatically foll
 - Server object model
     
   
-As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, a JavaScript object model, and a REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, a JavaScript object model, and a REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -50,7 +51,7 @@ Each API includes a manager object that you use to perform core tasks for follow
     
 
 > **Note:**
-> The same APIs are used to follow content. See  [Follow content in SharePoint](follow-content-in-sharepoint) for an overview of Following Content tasks.
+> The same APIs are used to follow content. See  [Follow content in SharePoint](follow-content-in-sharepoint.md) for an overview of Following Content tasks.
   
     
     
@@ -71,9 +72,9 @@ Table 1 shows the manager and other key objects (or REST resources) in the APIs
 
 |**API**|**Key objects**|
 |:-----|:-----|
-|.NET client object model  <br/> See:  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint)|Manager object:            [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) , [SocialActorInfo](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorInfo.aspx) , [SocialActorType](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorType.aspx) , [SocialActorTypes](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorTypes.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll |
-|JavaScript object model  <br/> See:  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint)|Manager object:            [SocialFollowingManager](http://msdn.microsoft.com/library/9ee1c0c0-b864-f0c3-f0cb-4dd4f1870dfa%28Office.15%29.aspx) <br/> Primary namespace:           **SP.Social** <br/> Other key objects:            [SocialActor](http://msdn.microsoft.com/library/4e369fd5-b9b0-9804-957e-b3e39c559cd4%28Office.15%29.aspx),  [SocialActorInfo](http://msdn.microsoft.com/library/d940db32-1561-c868-bb66-0612e2031f17%28Office.15%29.aspx),  [SocialActorType](http://msdn.microsoft.com/library/fbde74da-f292-dc87-0b7e-81bc5b7a880c%28Office.15%29.aspx),  [SocialActorTypes](http://msdn.microsoft.com/library/a460c3e6-ed88-117d-6755-4c5803a154a0%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js |
-|REST service  <br/> See:  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)|Manager resource:            [social.following](following-people-and-content-rest-api-reference-for-sharepoint) <br/> Endpoint URI:            `<siteUri>/_api/social.following` <br/> Primary namespace (OData):           **sp.social.SocialRestFollowingManager** <br/> Other key resources:           **SocialActor**, **SocialActorInfo**, **SocialActorType**, **SocialActorTypes**|
+|.NET client object model  <br/> See:  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md)|Manager object:            [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) , [SocialActorInfo](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorInfo.aspx) , [SocialActorType](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorType.aspx) , [SocialActorTypes](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActorTypes.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll |
+|JavaScript object model  <br/> See:  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md)|Manager object:            [SocialFollowingManager](http://msdn.microsoft.com/library/9ee1c0c0-b864-f0c3-f0cb-4dd4f1870dfa%28Office.15%29.aspx) <br/> Primary namespace:           **SP.Social** <br/> Other key objects:            [SocialActor](http://msdn.microsoft.com/library/4e369fd5-b9b0-9804-957e-b3e39c559cd4%28Office.15%29.aspx),  [SocialActorInfo](http://msdn.microsoft.com/library/d940db32-1561-c868-bb66-0612e2031f17%28Office.15%29.aspx),  [SocialActorType](http://msdn.microsoft.com/library/fbde74da-f292-dc87-0b7e-81bc5b7a880c%28Office.15%29.aspx),  [SocialActorTypes](http://msdn.microsoft.com/library/a460c3e6-ed88-117d-6755-4c5803a154a0%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js |
+|REST service  <br/> See:  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)|Manager resource:            [social.following](following-people-and-content-rest-api-reference-for-sharepoint.md) <br/> Endpoint URI:            `<siteUri>/_api/social.following` <br/> Primary namespace (OData.md):           **sp.social.SocialRestFollowingManager** <br/> Other key resources:           **SocialActor**, **SocialActorInfo**, **SocialActorType**, **SocialActorTypes**|
 |Server object model |Manager object:            [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx) <br/> Primary namespace:            [Microsoft.Office.Server.Social](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.aspx) <br/> Other key objects:            [SPSocialActor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActor.aspx) , [SPSocialActorInfo](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorInfo.aspx) , [SPSocialActorType](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorType.aspx) , [SPSocialActorTypes](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActorTypes.aspx) <br/> Class library:           Microsoft.Office.Server.UserProfiles.dll |
    
 
@@ -86,7 +87,7 @@ Table 2 shows common programming tasks for following people and the members that
     
 
 > **Note:**
-> The same APIs are used to follow content. See  [Follow content in SharePoint](follow-content-in-sharepoint) for an overview of Following Content tasks.
+> The same APIs are used to follow content. See  [Follow content in SharePoint](follow-content-in-sharepoint.md) for an overview of Following Content tasks.
   
     
     
@@ -103,12 +104,12 @@ The **SocialFollowingManager** object consolidates the core Following People and
 |:-----|:-----|
 |Create an instance of a manager object in the context of the current user |CSOM:  [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) <br/> JSOM: **SocialFollowingManager** <br/> REST:  `<siteUri>/_api/social.following` <br/> SSOM:  [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx)|
 |Create an instance of a manager object in the context of a particular user |CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM:  [SPSocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.aspx) (overloaded)|
-|Have the current user start following (stop following) someone |CSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.StopFollowing.aspx) ) <br/> JSOM:  [follow](http://msdn.microsoft.com/library/40d14320-27ba-2941-b0e2-be3b5a407c89%28Office.15%29.aspx) ( [stopFollowing](http://msdn.microsoft.com/library/65b0e9be-dc5e-09fb-c57f-7a933de09a4c%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.following/Follow`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Follow) ([`<siteUri>/_api/social.following/StopFollowing`](following-people-and-content-rest-api-reference-for-sharepoint#bk_StopFollowing)) and pass the  _actor_ parameter in the request body <br/> SSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.StopFollowing.aspx) )|
-|Find out whether the current user is following a particular user |CSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.IsFollowed.aspx) <br/> JSOM:  [isFollowed](http://msdn.microsoft.com/library/2c1f62e6-fb75-ad4d-c081-36408b418c21%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.following/my/IsFollowed`](following-people-and-content-rest-api-reference-for-sharepoint#bk_IsFollowed) and pass the _actor_ parameter in the request body <br/> SSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.IsFollowed.aspx)|
-|Get the people who are following the current user |CSOM:  [GetFollowers](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowers.aspx) <br/> JSOM:  [getFollowers](http://msdn.microsoft.com/library/ae4a944b-c043-05fb-c74b-101d2ce4a813%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followers`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Followers)<br/> SSOM:  [GetFollowers](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowers.aspx)|
-|Get the people who the current user is following |CSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowed.aspx) <br/> JSOM:  [getFollowed](http://msdn.microsoft.com/library/432a7cec-6add-fdb1-a79f-a93414ee8cd3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followed(types=1)`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Followed)<br/> SSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowed.aspx)|
-|Get the count of people who the current user is following |CSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowedCount.aspx) <br/> JSOM:  [getFollowedCount](http://msdn.microsoft.com/library/97b53b4f-481a-cf41-1854-8f3ff860b2bb%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedCount(types=1)`](following-people-and-content-rest-api-reference-for-sharepoint#bk_FollowedCount)<br/> SSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowedCount.aspx)|
-|Get the people who the current user might want to follow |CSOM:  [GetSuggestions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetSuggestions.aspx) <br/> JSOM:  [getSuggestions](http://msdn.microsoft.com/library/95fd9c48-6974-ec08-d3e9-00c2c76f4f79%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Suggestions`](following-people-and-content-rest-api-reference-for-sharepoint#bk_Suggestions)<br/> SSOM:  [GetSuggestions](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetSuggestions.aspx)|
+|Have the current user start following (stop following) someone |CSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.StopFollowing.aspx) ) <br/> JSOM:  [follow](http://msdn.microsoft.com/library/40d14320-27ba-2941-b0e2-be3b5a407c89%28Office.15%29.aspx) ( [stopFollowing](http://msdn.microsoft.com/library/65b0e9be-dc5e-09fb-c57f-7a933de09a4c%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.following/Follow`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Follow) ([`<siteUri>/_api/social.following/StopFollowing`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_StopFollowing)) and pass the  _actor_ parameter in the request body <br/> SSOM:  [Follow](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.Follow.aspx) ( [StopFollowing](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.StopFollowing.aspx) )|
+|Find out whether the current user is following a particular user |CSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.IsFollowed.aspx) <br/> JSOM:  [isFollowed](http://msdn.microsoft.com/library/2c1f62e6-fb75-ad4d-c081-36408b418c21%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.following/my/IsFollowed`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_IsFollowed) and pass the _actor_ parameter in the request body <br/> SSOM:  [IsFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.IsFollowed.aspx)|
+|Get the people who are following the current user |CSOM:  [GetFollowers](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowers.aspx) <br/> JSOM:  [getFollowers](http://msdn.microsoft.com/library/ae4a944b-c043-05fb-c74b-101d2ce4a813%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followers`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Followers)<br/> SSOM:  [GetFollowers](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowers.aspx)|
+|Get the people who the current user is following |CSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowed.aspx) <br/> JSOM:  [getFollowed](http://msdn.microsoft.com/library/432a7cec-6add-fdb1-a79f-a93414ee8cd3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Followed(types=1)`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Followed)<br/> SSOM:  [GetFollowed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowed.aspx)|
+|Get the count of people who the current user is following |CSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetFollowedCount.aspx) <br/> JSOM:  [getFollowedCount](http://msdn.microsoft.com/library/97b53b4f-481a-cf41-1854-8f3ff860b2bb%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/FollowedCount(types=1)`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_FollowedCount)<br/> SSOM:  [GetFollowedCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetFollowedCount.aspx)|
+|Get the people who the current user might want to follow |CSOM:  [GetSuggestions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.GetSuggestions.aspx) <br/> JSOM:  [getSuggestions](http://msdn.microsoft.com/library/95fd9c48-6974-ec08-d3e9-00c2c76f4f79%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.following/my/Suggestions`](following-people-and-content-rest-api-reference-for-sharepoint.md#bk_Suggestions)<br/> SSOM:  [GetSuggestions](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFollowingManager.GetSuggestions.aspx)|
    
 Table 3 shows the **PeopleManager** members that you can use for additional Following People functionality.
   
@@ -147,24 +148,24 @@ When a user opens the **People I'm following** page, the [PeopleManager.GetMySug
 <a name="bk_addResources"> </a>
 
 
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [Follow content in SharePoint](follow-content-in-sharepoint)
+-  [Follow content in SharePoint](follow-content-in-sharepoint.md)
     
   
 -  [User profiles REST API reference](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx)
     
   
--  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint)
+-  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md)
     
   
--  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint)
+-  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md)
     
   
--  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)
+-  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)
     
   
diff --git a/docs/general-development/following-people-and-content-rest-api-reference-for-sharepoint.md b/docs/general-development/following-people-and-content-rest-api-reference-for-sharepoint.md
index 7d56e767c4..ba1f1017ac 100644
--- a/docs/general-development/following-people-and-content-rest-api-reference-for-sharepoint.md
+++ b/docs/general-development/following-people-and-content-rest-api-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Following people and content REST API reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c05755df-846d-4a39-941d-950d066cc6d4
 ---
 
@@ -15,7 +16,7 @@ You can use the SharePoint Representational State Transfer (REST) service to do
 
 The endpoint URI for most Following tasks begins with the **SocialRestFollowingManager** resource ( `social.following`) and ends with the resource that performs the specific task. For example, you use the URI  `http://www.contoso.com/_api/social.following/follow` to make the current user start following people or content, and the URI `https://www.contoso.com/sites/devSite/_api/social.following/followed` to get the people or content the current user is following.
 > **Note:**
-> This article shows the endpoint URI and parameter components of HTTP requests. For examples of complete requests, see  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2). 
+> This article shows the endpoint URI and parameter components of HTTP requests. For examples of complete requests, see  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md). 
   
     
     
@@ -187,7 +188,7 @@ http://<siteCollection>/<site>/_api/social.following/follow(ActorType=3,TagGuid=
 }
 ```
 
-You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint#bk_getTagGuid).
+You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint.md#bk_getTagGuid).
   
     
     
@@ -363,7 +364,7 @@ http://<siteCollection>/<site>/_api/social.following/stopfollowing(ActorType=3,T
 }
 ```
 
-You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint#bk_getTagGuid).
+You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint.md#bk_getTagGuid).
   
     
     
@@ -525,7 +526,7 @@ http://<siteCollection>/<site>/_api/social.following/isfollowed(ActorType=3,TagG
 }
 ```
 
-You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint#bk_getTagGuid).
+You need the tag GUID to start following a tag. You can't get the GUID by using the REST service, but you can use the .NET client object model or the JavaScript object model. See  [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint.md#bk_getTagGuid).
   
     
     
@@ -971,7 +972,7 @@ Gets users who the current user might want to follow.
     
 
 > **Note:**
-> People Suggestions functionality depends on users' following activities, search crawls, and search analytics. See  [How People Suggestions works on SharePoint Online](follow-people-in-sharepoint#bk_PeopleSuggestions). 
+> People Suggestions functionality depends on users' following activities, search crawls, and search analytics. See  [How People Suggestions works on SharePoint Online](follow-people-in-sharepoint.md#bk_PeopleSuggestions). 
   
     
     
@@ -1015,7 +1016,7 @@ Gets users who the current user might want to follow.
     
 
 > **Note:**
-> People Suggestions functionality depends on users' following activities, search crawls, and search analytics. See  [How People Suggestions works on SharePoint Online](follow-people-in-sharepoint#bk_PeopleSuggestions). 
+> People Suggestions functionality depends on users' following activities, search crawls, and search analytics. See  [How People Suggestions works on SharePoint Online](follow-people-in-sharepoint.md#bk_PeopleSuggestions). 
   
     
     
@@ -1565,15 +1566,15 @@ The following response represents a user who is following the specified user.
 <a name="bk_addresources"> </a>
 
 
--  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2)
+-  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md)
     
   
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
 -  [SharePoint User Profiles JavaScript Reference (sp.userprofiles.js)](http://msdn.microsoft.com/library/80cf5436-6aa2-6f11-a782-66a04f6e2fb0%28Office.15%29.aspx)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
diff --git a/docs/general-development/frequently-asked-questions-about-excel-services-udfs.md b/docs/general-development/frequently-asked-questions-about-excel-services-udfs.md
index 705694021d..afcb270483 100644
--- a/docs/general-development/frequently-asked-questions-about-excel-services-udfs.md
+++ b/docs/general-development/frequently-asked-questions-about-excel-services-udfs.md
@@ -1,9 +1,10 @@
 ---
 title: Frequently Asked Questions About Excel Services UDFs
+ms.date: 09/25/2017
 keywords: faqs
 f1_keywords:
 - faqs
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 3d94d040-eecf-4f8e-a316-6d1cca95e7eb
 ---
 
@@ -56,7 +57,7 @@ The UDF method must also have a supported return type. For a list of supported d
 
 ### Can I call a Web service from a UDF assembly?
 
-Yes. For an example, see the following UDF sample code. Also see  [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service).
+Yes. For an example, see the following UDF sample code. Also see  [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md).
   
     
     
@@ -215,39 +216,39 @@ Not directly. Excel Services will load and call only managed-code UDFs. However,
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
 #### Concepts
 
 
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
diff --git a/docs/general-development/general-guidelines.md b/docs/general-development/general-guidelines.md
index 08a763b21c..c07fe92582 100644
--- a/docs/general-development/general-guidelines.md
+++ b/docs/general-development/general-guidelines.md
@@ -1,6 +1,7 @@
 ---
 title: General Guidelines
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 437541f8-5cd9-46f4-92b6-3bf9d7e62f69
 ---
 
@@ -16,49 +17,49 @@ This section contains general information related to Excel Services.
 ## In this section
 
 
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
 > Learn about the types of alerts that Excel Web Services exposes for errors that occur in the Web service and that are returned by Excel Calculation Services.
     
   
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
 > Get a list of known issues and tips for working with Excel Services.
     
   
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
   
     
     
 > Learn about best practices for mitigating threats, and for working with Excel Services user-defined functions (UDFs).
     
   
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
 > Learn how to trust a location by using the SharePoint Central Administration page.
     
   
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
   
     
     
 > Learn the steps to create a workbook with editable ranges and how to save the workbook to a SharePoint document library that is a trusted location.
     
   
- [How to: Save to the Server to Prepare for Programmatic Access](how-to-save-to-the-server-to-prepare-for-programmatic-access)
+ [How to: Save to the Server to Prepare for Programmatic Access](how-to-save-to-the-server-to-prepare-for-programmatic-access.md)
   
     
     
 > Get a workbook ready for programmatic access by creating named ranges and saving it to a trusted SharePoint library location.
     
   
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
   
     
     
diff --git a/docs/general-development/get-started-developing-with-social-features-in-sharepoint.md b/docs/general-development/get-started-developing-with-social-features-in-sharepoint.md
index 7d378cd80b..b974d372c4 100644
--- a/docs/general-development/get-started-developing-with-social-features-in-sharepoint.md
+++ b/docs/general-development/get-started-developing-with-social-features-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Get started developing with social features in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8852ce36-8309-45a7-a141-2e10ac17a123
 ---
 
@@ -10,31 +11,31 @@ ms.assetid: 8852ce36-8309-45a7-a141-2e10ac17a123
 Get started programming with SharePoint social feeds and microblog posts, following people and content (documents, sites, and tags), and working with user profiles.
 
     
- [How can I use social features in apps and solutions?](get-started-developing-with-social-features-in-sharepoint#bk_HowToUseSocialFeatures)
+ [How can I use social features in apps and solutions?](get-started-developing-with-social-features-in-sharepoint.md#bk_HowToUseSocialFeatures)
   
     
     
- [Setting up the development environment](get-started-developing-with-social-features-in-sharepoint#DevEnvironment)
+ [Setting up the development environment](get-started-developing-with-social-features-in-sharepoint.md#DevEnvironment)
   
     
     
- [Development scenarios for social features](get-started-developing-with-social-features-in-sharepoint#DevScenarios)
+ [Development scenarios for social features](get-started-developing-with-social-features-in-sharepoint.md#DevScenarios)
   
     
     
- [How-tos for programming with social features](get-started-developing-with-social-features-in-sharepoint#bk_GetStarted)
+ [How-tos for programming with social features](get-started-developing-with-social-features-in-sharepoint.md#bk_GetStarted)
   
     
     
- [APIs for programming with social features](get-started-developing-with-social-features-in-sharepoint#SocialApis)
+ [APIs for programming with social features](get-started-developing-with-social-features-in-sharepoint.md#SocialApis)
   
     
     
- [App permission requests for accessing social features](get-started-developing-with-social-features-in-sharepoint#bkmk_AppPerms)
+ [App permission requests for accessing social features](get-started-developing-with-social-features-in-sharepoint.md#bkmk_AppPerms)
   
     
     
- [Additional resources](get-started-developing-with-social-features-in-sharepoint#bk_AddResources)
+ [Additional resources](get-started-developing-with-social-features-in-sharepoint.md#bk_AddResources)
   
     
     
@@ -47,11 +48,11 @@ Social features in SharePoint apps and solutions can help people to connect, com
   
     
     
-The features described in this article align to the people, feeds, and following functionality that you find on personal sites and team sites. The forum experience and reputation model on Community Sites don't expose a specific API, so you use SharePoint site and list APIs directly to extend that functionality. For more information, see  [New Community Site feature](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201#bkmk_Collab).
+The features described in this article align to the people, feeds, and following functionality that you find on personal sites and team sites. The forum experience and reputation model on Community Sites don't expose a specific API, so you use SharePoint site and list APIs directly to extend that functionality. For more information, see  [New Community Site feature](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md#bkmk_Collab).
   
     
     
-Before you start developing, you should know where your code will run, what SharePoint environment it will run on, and what functionality it will provide. These factors help you choose the kind of app to create and which API or APIs to use. See  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint) and [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions) for information that can help you decide.
+Before you start developing, you should know where your code will run, what SharePoint environment it will run on, and what functionality it will provide. These factors help you choose the kind of app to create and which API or APIs to use. See  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md) and [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md) for information that can help you decide.
   
     
     
@@ -70,7 +71,7 @@ To get started developing with social features, you'll need:
   
 
   
-For more guidance, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint) and [Configure social computing features in SharePoint](http://technet.microsoft.com/en-us/library/fp161267%28v=office.15%29.aspx).
+For more guidance, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md) and [Configure social computing features in SharePoint](http://technet.microsoft.com/en-us/library/fp161267%28v=office.15%29.aspx).
   
     
     
@@ -87,16 +88,16 @@ The following articles describe the primary APIs and programming tasks for the p
     
     
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
--  [Follow content in SharePoint](follow-content-in-sharepoint)
+-  [Follow content in SharePoint](follow-content-in-sharepoint.md)
     
   
--  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint)
+-  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md)
     
   
 
@@ -113,19 +114,19 @@ After you set up your development environment and choose your scenario, you can
 
 |**Feature area**|**Description**|
 |:-----|:-----|
-| [How to: Learn to read and write to the social feed by using the .NET client object model in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object)|Walk through detailed steps for creating an application that reads and writes to the social feed by using the .NET client object model.|
-| [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)|Walk through detailed steps for creating an application that reads and writes to the social feed by using the REST service.|
-| [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli)|Learn how to create and delete and microblog posts and retrieve social feeds by using the .NET client object model.|
-| [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr)|Learn how to create and delete and microblog posts and retrieve social feeds by using the JavaScript object model.|
-| [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep)|Learn how to add **SocialDataItem** objects to microblog posts, which render as mentions, tags, and links in social feeds.|
-| [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server)|Learn how to add **SocialAttachment** objects to microblog posts, which render as embedded pictures, videos, and documents in social feeds.|
-| [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint)|Learn how to work with Following People features by using the .NET client object model.|
-| [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint)|Learn how to work with Following People features by using the JavaScript object model.|
-| [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep)|Learn how to work with Following Content features by using the .NET client object model.|
-| [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2)|Learn how to work with Following Content features by using the REST service.|
-| [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in)|Learn how to retrieve user profile properties by using the .NET client object model.|
-| [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in)|Learn how to retrieve user profile properties by using the JavaScript object model.|
-| [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)|Learn how to create, retrieve, and manage user profiles and properties by using the server object model.|
+| [How to: Learn to read and write to the social feed by using the .NET client object model in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md)|Walk through detailed steps for creating an application that reads and writes to the social feed by using the .NET client object model.|
+| [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)|Walk through detailed steps for creating an application that reads and writes to the social feed by using the REST service.|
+| [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md)|Learn how to create and delete and microblog posts and retrieve social feeds by using the .NET client object model.|
+| [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md)|Learn how to create and delete and microblog posts and retrieve social feeds by using the JavaScript object model.|
+| [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md)|Learn how to add **SocialDataItem** objects to microblog posts, which render as mentions, tags, and links in social feeds.|
+| [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md)|Learn how to add **SocialAttachment** objects to microblog posts, which render as embedded pictures, videos, and documents in social feeds.|
+| [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md)|Learn how to work with Following People features by using the .NET client object model.|
+| [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md)|Learn how to work with Following People features by using the JavaScript object model.|
+| [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md)|Learn how to work with Following Content features by using the .NET client object model.|
+| [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md)|Learn how to work with Following Content features by using the REST service.|
+| [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md)|Learn how to retrieve user profile properties by using the .NET client object model.|
+| [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md)|Learn how to retrieve user profile properties by using the JavaScript object model.|
+| [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)|Learn how to create, retrieve, and manage user profiles and properties by using the server object model.|
    
 
 ### APIs for programming with SharePoint social features
@@ -145,7 +146,7 @@ Although apps and solutions access SharePoint differently, after you do access S
 |Silverlight client object model|Microsoft.SharePoint.Client.UserProfiles.Silverlight.dll<br/>in %ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\TEMPLATE\\LAYOUTS\\ClientBin|
 |Mobile client object model|Microsoft.SharePoint.Client.UserProfiles.Phone.dll<br/>in %ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\TEMPLATE\\LAYOUTS\\ClientBin|
 | [JavaScript object model](http://msdn.microsoft.com/library/95cb5427-8514-4e9a-8eee-7ed4b82ec01b%28Office.15%29.aspx)|SP.UserProfiles.js<br/>in %ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\TEMPLATE\\LAYOUTS|
-|Representational State Transfer (REST) service| [`http://<site url>/_api/social.feed`](social-feed-rest-api-reference-for-sharepoint)<br/>[`http://<site url>/_api/social.following`](following-people-and-content-rest-api-reference-for-sharepoint)<br/>[`http://<site url>/_api/SP.UserProfiles.PeopleManager`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PeopleManager)|
+|Representational State Transfer (REST) service| [`http://<site url>/_api/social.feed`](social-feed-rest-api-reference-for-sharepoint.md)<br/>[`http://<site url>/_api/social.following`](following-people-and-content-rest-api-reference-for-sharepoint.md)<br/>[`http://<site url>/_api/SP.UserProfiles.PeopleManager`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx.md#bk_PeopleManager)|
 | [Server object model](http://msdn.microsoft.com/library/87c5118c-ac0e-4bd9-a75f-7452a9eb0e41%28Office.15%29.aspx)|Microsoft.Office.Server.UserProfiles.dll<br/>in %ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\ISAPI|
    
 
@@ -216,10 +217,10 @@ You should be aware of the following considerations when you specify app permiss
     
     
 
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [What's new for developers in social and collaboration features in SharePoint](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201)
+-  [What's new for developers in social and collaboration features in SharePoint](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md)
     
   
 -  [Plan for social computing and collaboration in SharePoint](http://technet.microsoft.com/en-us/library/ee662531%28v=office.15%29)
@@ -242,10 +243,10 @@ You should be aware of the following considerations when you specify app permiss
 -  [SP.UserProfiles.js JavaScript Reference](http://msdn.microsoft.com/library/80cf5436-6aa2-6f11-a782-66a04f6e2fb0%28Office.15%29.aspx)
     
   
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
--  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)
+-  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)
     
   
 -  [User profiles REST API reference](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx)
diff --git a/docs/general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint.md b/docs/general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint.md
index d78696894a..d47ef1641b 100644
--- a/docs/general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint.md
+++ b/docs/general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Get started using the client object model with external data in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8ed91929-fdb6-4fde-ba2a-7942870575f3
 ---
 
@@ -12,7 +13,7 @@ Learn how to use the SharePoint client object model to work with Business Connec
 
 The client object model for SharePoint is a set of client-based libraries that represent the server object model. They are packaged in three different DLLs to accommodate a variety of development types. The client object model includes most of the major functions of the server API. This allows access to the same types of functionality from browser scripting and also .NET web applications and Silverlight applications.  <br/> To enhance and expand the capabilities for working with external data, Business Connectivity Services (BCS) has expanded the client object model to include additional functionality.  <br/> 
 
-<a href="#BCScsom_getstarted"><img alt="Get set up" src="../../images/mod_icon_getstartbox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#BCScsom_Tasks"><img alt="Get to work" src="../../images/mod_icon_dobox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#BCScsom_Learnmore"><img alt="Learn more" src="../../images/mod_icon_startbox.gif" /></a></p>
+<a href="#BCScsom_getstarted"><img alt="Get set up" src="../images/mod_icon_getstartbox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#BCScsom_Tasks"><img alt="Get to work" src="../images/mod_icon_dobox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#BCScsom_Learnmore"><img alt="Learn more" src="../images/mod_icon_startbox.gif" /></a></p>
 
 ## Get started using the SharePoint client object model with external data
 <a name="BCScsom_getstarted"> </a>
@@ -31,7 +32,7 @@ To develop solutions using the SharePoint client object model (CSOM), you will n
 - Office Developer Tools for Visual Studio 2012
     
   
-For information about how to set up your development environment, see  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint).
+For information about how to set up your development environment, see  [Setting up a development environment for BCS in SharePoint](setting-up-a-development-environment-for-bcs-in-sharepoint.md).
   
     
     
@@ -59,9 +60,9 @@ The following articles will help you understand more about the client object mod
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [External content types in SharePoint](external-content-types-in-sharepoint) <br/> |Learn what you can do with external content types and what you need to start creating them in SharePoint.  <br/> |
-| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint) <br/> |Provides information to help get started creating external content types based on OData sources and using that data in SharePoint or Office 2013 components.  <br/> |
-| [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint) <br/> |Learn about the several sets of APIs that are provided in SharePoint, including the server object model, the various client object models, and the REST/OData web service.  <br/> |
+| [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |Learn what you can do with external content types and what you need to start creating them in SharePoint.  <br/> |
+| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md) <br/> |Provides information to help get started creating external content types based on OData sources and using that data in SharePoint or Office 2013 components.  <br/> |
+| [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md) <br/> |Learn about the several sets of APIs that are provided in SharePoint, including the server object model, the various client object models, and the REST/OData web service.  <br/> |
 | [.NET client API reference for SharePoint Online](http://msdn.microsoft.com/library/88e5e1b9-eab2-4f3b-a3f2-75c96b86f1f4%28Office.15%29.aspx) <br/> |Find information about the .NET client class libraries in SharePoint.  <br/> |
 | [JavaScript API reference for SharePoint](http://msdn.microsoft.com/library/1ead2f8d-a541-4a50-89fa-f195f2ba14e5%28Office.15%29.aspx) <br/> |Find information about the JavaScript object libraries in SharePoint.  <br/> |
    
@@ -84,7 +85,7 @@ See the articles in Table 2 for more information about what you can do with the
 |**Task**|**Description**|
 |:-----|:-----|
 | [Complete basic operations using SharePoint client library code](http://msdn.microsoft.com/library/5a69c9e3-73bf-4ed5-bc19-182056bdb394%28Office.15%29.aspx) <br/> |Learn how to write code to perform basic operations with the SharePoint client object model.  <br/> |
-| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint) <br/> |Learn how to use the SharePoint client object model to work with SharePoint BCS objects using browser-based scripting.  <br/> |
+| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md) <br/> |Learn how to use the SharePoint client object model to work with SharePoint BCS objects using browser-based scripting.  <br/> |
    
 The following are some basic examples of tasks you can accomplish using CSOM.
   
@@ -203,20 +204,20 @@ For more information about using the client object model in SharePoint, see the
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint) <br/> |Summarizes the objects available for creating client-side scripts using the SharePoint client object model to access external data exposed by BCS.  <br/> |
+| [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint.md) <br/> |Summarizes the objects available for creating client-side scripts using the SharePoint client object model to access external data exposed by BCS.  <br/> |
    
 
 ## Additional resources
 <a name="BCScsom_Learnmore"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 -  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx)
     
   
--  [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint)
+-  [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md)
     
   
 -  [Complete basic operations using SharePoint client library code](http://msdn.microsoft.com/library/5a69c9e3-73bf-4ed5-bc19-182056bdb394%28Office.15%29.aspx)
diff --git a/docs/general-development/get-started-with-business-connectivity-services-in-sharepoint.md b/docs/general-development/get-started-with-business-connectivity-services-in-sharepoint.md
index cb834cd377..40dd47dc73 100644
--- a/docs/general-development/get-started-with-business-connectivity-services-in-sharepoint.md
+++ b/docs/general-development/get-started-with-business-connectivity-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Get started with Business Connectivity Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c6bf3db0-db79-4b13-9834-891d24b2c9e5
 ---
 
@@ -12,7 +13,7 @@ Learn the basics of what Business Connectivity Services (BCS) provides to develo
 
 Business Connectivity Services (BCS) was introduced in SharePoint Server 2010 as an evolution of the Business Data Catalog released in Office SharePoint Server 2007. BCS enables SharePoint to work with data that is hosted externally. Possible sources can include databases, web services, Windows Communication Foundation (WCF) services, Open Data Protocol (OData) sources, and other proprietary data that is accessed by using custom .NET assemblies.
 
-<a href="#SP15GettingStartedBCS_WhatDoYouNeed"><img alt="Get set up" src="../../images/mod_icon_getstartbox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#SP15GettingStartedBCS_WhatCanYouDo"><img alt="Get to work" src="../../images/mod_icon_dobox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#SP15GettingStartedBCS_LearnMore"><img alt="Learn more" src="../../images/mod_icon_startbox.gif" /></a>
+<a href="#SP15GettingStartedBCS_WhatDoYouNeed"><img alt="Get set up" src="../images/mod_icon_getstartbox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#SP15GettingStartedBCS_WhatCanYouDo"><img alt="Get to work" src="../images/mod_icon_dobox.gif" /></a>&nbsp;&nbsp;&nbsp;<a href="#SP15GettingStartedBCS_LearnMore"><img alt="Learn more" src="../images/mod_icon_startbox.gif" /></a>
 
    
 In a dynamic workplace, information workers need access to data that resides in separate software worlds, for example:
@@ -53,7 +54,7 @@ To get started developing with BCS, you will need the following:
 - SharePoint Designer
     
   
-For information about how to set up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about how to set up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -75,8 +76,8 @@ The following table highlights the core concepts that you will need to be famili
 | [WCF Data Services](http://msdn.microsoft.com/en-us/data/odata.aspx) <br/> |WCF Data Services, formerly known as ADO.NET Data Services, enable the creation and consumption of OData services for the web.  <br/> |
 | [Open Data Protocol (OData)](http://www.odata.org) <br/> |OData is an industry standard protocol for accessing data through URLs. It basically sits on top of the HTTP protocol to provide read and write functions using existing HTTP verbs.  <br/> |
 | [Internet Information Services](http://www.iis.net/) <br/> |Internet Information Services (IIS) is the platform that SharePoint runs on. You should understand how to create websites, virtual directories, web services, URLs, web security, and other technologies related to IIS.  <br/> |
-| [External content types in SharePoint](external-content-types-in-sharepoint) <br/> |External content types are descriptions of the external systems that they represent. They are reusable when imported into SharePoint and can be used to create complex code-free solutions using SharePoint Designer 2013, Outlook 2013, Web Parts, external lists, and custom client applications.  <br/> |
-| [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint) <br/> |SharePoint provides the ability to access all objects through a carefully constructed URL. BCS has been extended to provide this same functionality.  <br/> |
+| [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |External content types are descriptions of the external systems that they represent. They are reusable when imported into SharePoint and can be used to create complex code-free solutions using SharePoint Designer 2013, Outlook 2013, Web Parts, external lists, and custom client applications.  <br/> |
+| [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md) <br/> |SharePoint provides the ability to access all objects through a carefully constructed URL. BCS has been extended to provide this same functionality.  <br/> |
    
 
 ## What can you do with Business Connectivity Services?
@@ -92,11 +93,11 @@ With BCS, you can bring information into SharePoint from many different sources.
 
 |**Task**|**Description**|
 |:-----|:-----|
-| [External content types in SharePoint](external-content-types-in-sharepoint) <br/> |Learn about creating Business Connectivity Services (BCS) external content types.  <br/> |
-| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint) <br/> |Find information that is needed to get started creating external content types based on OData sources and using that data in SharePoint or Office components.  <br/> |
-| [How to: Create external event receivers](how-to-create-external-event-receivers) <br/> |Learn the concepts behind creating event receivers that can be attached to external lists and will execute when the external data that the list represents is updated.  <br/> |
-| [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint) <br/> |Learn how to create external content types that are installed or scoped at the app level, enabling developers to create data-rich apps using external data sources.  <br/> |
-| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint) <br/> |Learn how to use the SharePoint client object model to work with BCS in SharePoint.  <br/> |
+| [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |Learn about creating Business Connectivity Services (BCS) external content types.  <br/> |
+| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md) <br/> |Find information that is needed to get started creating external content types based on OData sources and using that data in SharePoint or Office components.  <br/> |
+| [How to: Create external event receivers](how-to-create-external-event-receivers.md) <br/> |Learn the concepts behind creating event receivers that can be attached to external lists and will execute when the external data that the list represents is updated.  <br/> |
+| [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md) <br/> |Learn how to create external content types that are installed or scoped at the app level, enabling developers to create data-rich apps using external data sources.  <br/> |
+| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md) <br/> |Learn how to use the SharePoint client object model to work with BCS in SharePoint.  <br/> |
    
 
 ## Beyond the basics: Learn more about Business Connectivity Services
@@ -112,34 +113,34 @@ When you master the basic concepts of BCS, you can use the more advanced feature
 
 |**Topic**|**Description**|
 |:-----|:-----|
-| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system) <br/> |Learn how to create an Internet-addressable WCF service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
-| [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint) <br/> |Find reference documentation for the schema of the BDC model.  <br/> |
-| [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint) <br/> |Get a summary of the objects that are available for creating client-side scripts using the SharePoint client object model to access external data exposed by Business Connectivity Services (BCS).  <br/> |
-| [BCS REST API reference for SharePoint](bcs-rest-api-reference-for-sharepoint) <br/> |Find reference information for constructing Representational State Transfer (REST) URIs used for accessing and manipulating OData sources.  <br/> |
+| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md) <br/> |Learn how to create an Internet-addressable WCF service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
+| [BDC model schema reference for SharePoint](bdc-model-schema-reference-for-sharepoint.md) <br/> |Find reference documentation for the schema of the BDC model.  <br/> |
+| [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint.md) <br/> |Get a summary of the objects that are available for creating client-side scripts using the SharePoint client object model to access external data exposed by Business Connectivity Services (BCS).  <br/> |
+| [BCS REST API reference for SharePoint](bcs-rest-api-reference-for-sharepoint.md) <br/> |Find reference information for constructing Representational State Transfer (REST) URIs used for accessing and manipulating OData sources.  <br/> |
    
 
 ## Additional resources
 <a name="SP15GettingStartedBCS_LearnMore"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 -  [Open Data Protocol website](http://www.odata.org/)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint)
+-  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
     
   
--  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint)
+-  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint.md)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
diff --git a/docs/general-development/get-started-with-workflows-in-sharepoint.md b/docs/general-development/get-started-with-workflows-in-sharepoint.md
index 30be629e51..772c055295 100644
--- a/docs/general-development/get-started-with-workflows-in-sharepoint.md
+++ b/docs/general-development/get-started-with-workflows-in-sharepoint.md
@@ -1,9 +1,10 @@
 ---
 title: Get started with workflows in SharePoint
+ms.date: 09/25/2017
 keywords: vs.sharepointtools.workflow4.workflowlist,VS.SharePointTools.Workflow4.WorkflowName
 f1_keywords:
 - vs.sharepointtools.workflow4.workflowlist,VS.SharePointTools.Workflow4.WorkflowName
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: a2643cd7-474d-4e4c-85bb-00f0b6685a1d
 ---
 
@@ -11,7 +12,7 @@ ms.assetid: a2643cd7-474d-4e4c-85bb-00f0b6685a1d
 # Get started with workflows in SharePoint
 Learn about the newly engineered Workflow Manager Client 1.0, which provides the infrastructure for workflows in SharePoint, and how SharePoint workflows are integrated with the new model for SharePoint Add-ins.
 > **Important:**
-> For instructions on setting up and configuring SharePoint and Microsoft Azure, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager). 
+> For instructions on setting up and configuring SharePoint and Microsoft Azure, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md). 
   
     
     
@@ -34,7 +35,7 @@ Workflows in SharePoint allow you to model and automate business processes. Thes
   
     
     
-![Simple workflow](../../images/wfSimple.gif)
+![Simple workflow](../images/wfSimple.gif)
   
     
     
@@ -42,7 +43,7 @@ Workflows in SharePoint allow you to model and automate business processes. Thes
   
     
     
-SharePoint marks the introduction of Workflow Manager Client 1.0 as the powerful new foundation for Visual Studio workflows. Build on Windows Workflow Foundation 4, Workflow Manager Client 1.0 provides advantages over previous versions that reflect the commitment of SharePoint to the model for SharePoint Add-ins and cloud-based computing. For details of these changes, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint) and [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals).
+SharePoint marks the introduction of Workflow Manager Client 1.0 as the powerful new foundation for Visual Studio workflows. Build on Windows Workflow Foundation 4, Workflow Manager Client 1.0 provides advantages over previous versions that reflect the commitment of SharePoint to the model for SharePoint Add-ins and cloud-based computing. For details of these changes, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md) and [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md).
   
     
     
@@ -50,7 +51,7 @@ Perhaps most importantly for workflow authors, the way that your create workflow
   
     
     
-The key enhancements to workflows in SharePoint include the following. For a more detail overview of what's new in workflows for SharePoint, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint).
+The key enhancements to workflows in SharePoint include the following. For a more detail overview of what's new in workflows for SharePoint, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md).
   
     
     
@@ -58,7 +59,7 @@ The key enhancements to workflows in SharePoint include the following. For a mor
 - Enhanced connectivity to enable cloud-based execution of workflows. In fact, there is 100 percent parity in SharePoint between on-premises and Office 365 -based workflows.
     
   
-- There is full interoperability in SharePoint with SharePoint 2010 workflows, which is enabled by using the  [SharePoint workflow interop ](sharepoint-workflow-fundamentals#bkm_InteropBridge).
+- There is full interoperability in SharePoint with SharePoint 2010 workflows, which is enabled by using the  [SharePoint workflow interop ](sharepoint-workflow-fundamentals.md#bkm_InteropBridge).
     
   
 - Enhanced authoring expressiveness by using Visual Studio events and action, web services, and classic programming structures, all in a declarative, no-code environment.
@@ -99,7 +100,7 @@ There are two primary authoring environments for Workflow Manager Client 1.0: Sh
   
     
     
-However, the primary authoring environments are Visual Studio 2012 and SharePoint Designer 2013. To help you decide which of these best suits your needs, see the decision matrix in  [Comparing SharePoint Designer with Visual Studio](develop-sharepoint-workflows-using-visual-studio#bkm_Comparing).
+However, the primary authoring environments are Visual Studio 2012 and SharePoint Designer 2013. To help you decide which of these best suits your needs, see the decision matrix in  [Comparing SharePoint Designer with Visual Studio](develop-sharepoint-workflows-using-visual-studio.md#bkm_Comparing).
   
     
     
@@ -129,7 +130,7 @@ Visual Studio 2012 has SharePoint workflow project types built in. To create a S
 
   
 
-  ![New Project dialog box](../../images/wfNewProject_b2.png)
+  ![New Project dialog box](../images/wfNewProject_b2.png)
   
 
   
@@ -141,7 +142,7 @@ Visual Studio 2012 has SharePoint workflow project types built in. To create a S
 
   
 
-  ![Add New Item dialog box](../../images/wfAddNewItemDialog_b2.png)
+  ![Add New Item dialog box](../images/wfAddNewItemDialog_b2.png)
   
 
   
@@ -153,7 +154,7 @@ Visual Studio 2012 has SharePoint workflow project types built in. To create a S
 
   
 
-  ![Workflow toolbox](../../images/wfToolbox_b2.png)
+  ![Workflow toolbox](../images/wfToolbox_b2.png)
   
 
   
@@ -185,10 +186,10 @@ For more information about developing workflows using **Visual Studio 2012** and
     
     
 
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 For more information about Windows Workflow Foundation 4, see the following: 
diff --git a/docs/general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer.md b/docs/general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer.md
index 32307d6dfb..2139d62092 100644
--- a/docs/general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer.md
+++ b/docs/general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Getting familiar with Visual Designer for workflow in SharePoint Designer 2013
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ff9b0314-eea1-47e4-87c7-53ed4de98c30
 ---
 
@@ -31,7 +32,7 @@ SharePoint Designer 2013 includes a new workflow design surface called Visual De
   
     
     
-![Visual Designer not available without Visio](../../images/SPD15-VisualDesigner1.png)
+![Visual Designer not available without Visio](../images/SPD15-VisualDesigner1.png)
   
     
     
@@ -52,7 +53,7 @@ The **Shapes** pane on the left contains workflow shapes that you can drag to th
 
     
 > **Tip:**
-> For a complete list of shapes available in SharePoint Designer 2013, see  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio)
+> For a complete list of shapes available in SharePoint Designer 2013, see  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio.md)
   
     
     
@@ -71,7 +72,7 @@ The figure shows a workflow in Visual Designer.
   
     
     
-![Visual Designer in SharePoint Designer 2013](../../images/SPD15-VisualDesigner2.png)
+![Visual Designer in SharePoint Designer 2013](../images/SPD15-VisualDesigner2.png)
   
     
     
@@ -115,7 +116,7 @@ You can switch between **Views** in the **Manage** portion of the **Workflow** r
   
     
     
-![Switching between design views.](../../images/SPD15-VisualDesigner3.png)
+![Switching between design views.](../images/SPD15-VisualDesigner3.png)
   
     
     
@@ -137,10 +138,10 @@ A workflow can be developed in either the Text-Based Designer or the Visual Desi
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 
diff --git a/docs/general-development/getting-ranges-using-atom-feed-and-html-fragment.md b/docs/general-development/getting-ranges-using-atom-feed-and-html-fragment.md
index f18945a320..3158450642 100644
--- a/docs/general-development/getting-ranges-using-atom-feed-and-html-fragment.md
+++ b/docs/general-development/getting-ranges-using-atom-feed-and-html-fragment.md
@@ -1,6 +1,7 @@
----
+---
 title: Getting Ranges Using Atom Feed and HTML Fragment
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 45d4ef08-02d6-48dd-b0ef-a748db1a0c6a
 ---
 
@@ -27,7 +28,7 @@ The REST API in Excel Services supports two mechanisms for getting ranges. The f
   
     
     
-As described in the  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api) topic, the REST URL to the model page using discovery is:
+As described in the  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api.md) topic, the REST URL to the model page using discovery is:
   
     
     
@@ -50,7 +51,7 @@ Therefore, for a workbook with the file name **sampleWorkbook.xlsx** that is sav
 http://<ServerName>/_vti_bin/ExcelRest.aspx/Docs/Documents/sampleWorkbook.xlsx/model
 ```
 
-Using the discovery mechanism described in  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api), if you click on the **Ranges** Atom feed on the model page on the server, ( `http://` _<ServerName>_ `/_vti_bin/ExcelRest.aspx/Docs/Documents/sampleWorkbook.xlsx/model`), it displays a page that shows all the named ranges in the workbook. The sampleWorkbook.xlsx contains one named range, **SampleNamedRange**, as shown in the following screen shot: 
+Using the discovery mechanism described in  [Discovery in Excel Services REST API](discovery-in-excel-services-rest-api.md), if you click on the **Ranges** Atom feed on the model page on the server, ( `http://` _<ServerName>_ `/_vti_bin/ExcelRest.aspx/Docs/Documents/sampleWorkbook.xlsx/model`), it displays a page that shows all the named ranges in the workbook. The sampleWorkbook.xlsx contains one named range, **SampleNamedRange**, as shown in the following screen shot: 
   
     
     
@@ -78,7 +79,7 @@ Using the discovery mechanism described in  [Discovery in Excel Services REST AP
   
     
     
-![Excel Services REST named range discovery](../../images/159f676e-421e-4190-94a6-cf311f7db2ca.gif)
+![Excel Services REST named range discovery](../images/159f676e-421e-4190-94a6-cf311f7db2ca.gif)
   
     
     
@@ -108,7 +109,7 @@ Note that, in Internet Explorer, the resulting page looks like an error, as show
   
     
     
-![Excel Services REST range discovery using Atom](../../images/2d011e17-953f-42b1-97d3-2525372296c1.gif)
+![Excel Services REST range discovery using Atom](../images/2d011e17-953f-42b1-97d3-2525372296c1.gif)
   
     
     
@@ -237,7 +238,7 @@ In Internet Explorer, the page looks similar to the following figure.
   
     
     
-![Excel Services REST Discovery Get Range Using HTML](../../images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif)
+![Excel Services REST Discovery Get Range Using HTML](../images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif)
   
     
     
@@ -259,4 +260,4 @@ In Internet Explorer, the page looks similar to the following figure.
   
     
     
- [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api)
+ [Resources URI for Excel Services REST API](resources-uri-for-excel-services-rest-api.md)
diff --git a/docs/general-development/getting-started-with-excel-services.md b/docs/general-development/getting-started-with-excel-services.md
index 039aeb72a1..ff1f865b2a 100644
--- a/docs/general-development/getting-started-with-excel-services.md
+++ b/docs/general-development/getting-started-with-excel-services.md
@@ -1,6 +1,7 @@
----
+---
 title: Getting Started with Excel Services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 392e4734-5ca0-4647-8f6d-e671daa45a4d
 ---
 
@@ -16,35 +17,35 @@ This section introduces Excel Services — a server technology first introduced
 ## In this section
 
 
- [Excel Services Overview](excel-services-overview)
+ [Excel Services Overview](excel-services-overview.md)
   
     
     
 > Learn about this new technology that enables you to load, calculate, and display Excel workbooks on SharePoint Server
     
   
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
 > Learn how the three components of Excel Services communicate and work together.
     
   
- [Excel Services Development Roadmap](excel-services-development-roadmap)
+ [Excel Services Development Roadmap](excel-services-development-roadmap.md)
   
     
     
 > Learn about types of development you can do and the most common scenarios for using Excel Web Services.
     
   
- [Supported and Unsupported Features](supported-and-unsupported-features)
+ [Supported and Unsupported Features](supported-and-unsupported-features.md)
   
     
     
 > Find out which features of Excel are not supported in this first version of Excel Services.
     
   
- [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+ [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
   
     
     
diff --git a/docs/general-development/how-to-access-an-external-data-source-from-a-udf.md b/docs/general-development/how-to-access-an-external-data-source-from-a-udf.md
index 1c953ca024..48bd5e3b5b 100644
--- a/docs/general-development/how-to-access-an-external-data-source-from-a-udf.md
+++ b/docs/general-development/how-to-access-an-external-data-source-from-a-udf.md
@@ -1,9 +1,10 @@
 ---
 title: How to Access an External Data Source from a UDF
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,UDF
 f1_keywords:
 - how to,howdoi,howto,UDF
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 7a1876da-aeb5-4017-8eb6-3fed47912f70
 ---
 
@@ -160,43 +161,43 @@ End Namespace
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
   
     
     
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
diff --git a/docs/general-development/how-to-access-external-data-with-rest-in-sharepoint.md b/docs/general-development/how-to-access-external-data-with-rest-in-sharepoint.md
index f61d1f08d9..439a537a71 100644
--- a/docs/general-development/how-to-access-external-data-with-rest-in-sharepoint.md
+++ b/docs/general-development/how-to-access-external-data-with-rest-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Access external data with REST in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0663cc8c-a736-434d-9858-6ce12ce7f748
 ---
 
@@ -30,7 +31,7 @@ To access external data from SharePoint by using REST, you need the following:
 - Office Developer Tools for Visual Studio 2012
     
   
-- A functioning SharePoint Add-ins development environment: Follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+- A functioning SharePoint Add-ins development environment: Follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
     
   
 - Access to the public OData.org producers
@@ -202,7 +203,7 @@ Press F5 to deploy the app to SharePoint. Browse to the Default.aspx page in the
 <a name="bkmk_Addres"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 -  [Get to know the SharePoint REST service](http://msdn.microsoft.com/library/2de035a0-ac75-43bd-9665-5c5a59c4c590%28Office.15%29.aspx)
@@ -211,10 +212,10 @@ Press F5 to deploy the app to SharePoint. Browse to the Default.aspx page in the
 -  [Using the SharePoint REST service](http://msdn.microsoft.com/library/e1ff2979-1c16-4cb0-a57e-9168dfe20a7c.aspx)
     
   
--  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint)
+-  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint.md b/docs/general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint.md
index d51da07a55..6cc67ca52d 100644
--- a/docs/general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint.md
+++ b/docs/general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Add a Device Channel Panel snippet in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 612780a8-6267-49f6-a32d-33600bb5f6b4
 ---
 
@@ -77,7 +78,7 @@ Like all snippets, you add a Device Channel Panel snippet from the Snippet Galle
   
 10. In your HTML editor, open the mapped network drive on your computer, and then open the HTML file for the master page or page layout that you're adding the snippet to.
     
-    For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+    For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
     
   
 11. In the HTML file, paste the snippet where you want the markup to appear.
@@ -139,16 +140,16 @@ The **<div>** where `class="DefaultContentBlock"` should be replaced with whatev
 <a name="AdditionalResources"> </a>
 
 
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
--  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels)
+-  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md b/docs/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md
index 2eac118bc9..a6ec3ade84 100644
--- a/docs/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md
+++ b/docs/general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md
@@ -1,13 +1,14 @@
 ---
 title: How to Add a Geolocation column to a list programmatically in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f31a3594-c328-4731-b8eb-5da6b85103ad
 ---
 
 
 # How to: Add a Geolocation column to a list programmatically in SharePoint
 Learn how to programmatically add a Geolocation column to a list in SharePoint. Integrate location information and maps in SharePoint lists and location-based websites by using the new Geolocation field creating your own Geolocation-based field type.
-SharePoint introduces a new field type named Geolocation that enables you to annotate SharePoint lists with location information. In columns of type Geolocation, you can enter location information as a pair of latitude and longitude coordinates in decimal degrees or retrieve the coordinates of the user's current location from the browser if it implements the W3C Geolocation API. For more information about the Geolocation column, see [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint). The Geolocation column is not available by default in SharePoint lists. To add the column to a SharePoint list, you have to write code. In this article, learn how to add the Geolocation field to a list programmatically by using the SharePoint client object model.
+SharePoint introduces a new field type named Geolocation that enables you to annotate SharePoint lists with location information. In columns of type Geolocation, you can enter location information as a pair of latitude and longitude coordinates in decimal degrees or retrieve the coordinates of the user's current location from the browser if it implements the W3C Geolocation API. For more information about the Geolocation column, see [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md). The Geolocation column is not available by default in SharePoint lists. To add the column to a SharePoint list, you have to write code. In this article, learn how to add the Geolocation field to a list programmatically by using the SharePoint client object model.
   
     
     
@@ -102,7 +103,7 @@ class Program
 
   
 
-  ![Default Geolocation and Map feature](../../images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png)
+  ![Default Geolocation and Map feature](../images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png)
   
 
   
@@ -176,19 +177,19 @@ private void AddListItem()
 <a name="SP15addgeo_addlresources"> </a>
 
 
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint)
+-  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md)
     
   
--  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering)
+-  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md)
     
   
--  [Create a map view for the Geolocation field in SharePoint](create-a-map-view-for-the-geolocation-field-in-sharepoint)
+-  [Create a map view for the Geolocation field in SharePoint](create-a-map-view-for-the-geolocation-field-in-sharepoint.md)
     
   
--  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists)
+-  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md)
     
   
 -  [Use the SharePoint location field type in mobile applications](http://technet.microsoft.com/en-us/library/fp161355%28v=office.15%29.aspx)
diff --git a/docs/general-development/how-to-add-a-security-trim-snippet-in-sharepoint.md b/docs/general-development/how-to-add-a-security-trim-snippet-in-sharepoint.md
index 02e7c4f92a..bb67c96c13 100644
--- a/docs/general-development/how-to-add-a-security-trim-snippet-in-sharepoint.md
+++ b/docs/general-development/how-to-add-a-security-trim-snippet-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Add a Security Trim snippet in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4beaab08-760b-408a-b768-906312779379
 ---
 
@@ -170,13 +171,13 @@ The **<div>** where `class="DefaultContentBlock"` is what you replace with your
 -  [Understanding permission levels](http://office.microsoft.com/en-us/products/default-permission-levels-HA102772313.aspx?CTT=5&amp;origin=HA102771919)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint.md b/docs/general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint.md
index ca4a1481fc..ebb2c124bb 100644
--- a/docs/general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint.md
+++ b/docs/general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Add a Web Part zone snippet in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7583b217-200c-4569-8f88-fe975c8ebd72
 ---
 
@@ -111,7 +112,7 @@ Table 1 shows important properties to consider when you want to restrict a Web P
    
 
 > **Note:**
-> You cannot insert a Web Part zone inside a Device Channel Panel. If you want to allow authors to add Web Parts to a page, and if you are not concerned about the page weight for mobile devices, you can add a Rich Text Editor page field to a Device Channel Panel, and then instruct authors to add Web Parts there. You can add Web Parts directly to a Device Channel Panel (without a Web Part zone). For more information, see  [How to: Add a Device Channel Panel snippet in SharePoint](how-to-add-a-device-channel-panel-snippet-in-sharepoint). 
+> You cannot insert a Web Part zone inside a Device Channel Panel. If you want to allow authors to add Web Parts to a page, and if you are not concerned about the page weight for mobile devices, you can add a Rich Text Editor page field to a Device Channel Panel, and then instruct authors to add Web Parts there. You can add Web Parts directly to a Device Channel Panel (without a Web Part zone). For more information, see  [How to: Add a Device Channel Panel snippet in SharePoint](how-to-add-a-device-channel-panel-snippet-in-sharepoint.md). 
   
     
     
@@ -162,7 +163,7 @@ Like all snippets, you add this snippet from the Snippet Gallery. To navigate to
   
 10. In your HTML editor, open the mapped network drive on your computer, and then open the HTML file for the master page or page layout that you're adding the snippet to.
     
-    For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+    For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
     
   
 11. In the HTML file, paste the snippet where you want the markup to appear.
@@ -223,7 +224,7 @@ Additional properties that can be used to restrict how content authors can use z
 <a name="AdditionalResources"> </a>
 
 
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 -  [WebPartZone class](http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.webpartzone.aspx)
@@ -232,10 +233,10 @@ Additional properties that can be used to restrict how content authors can use z
 -  [WebPartZoneBase properties](http://msdn.microsoft.com/en-us/library/335sw9k3.aspx)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md b/docs/general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md
index 7d432ab5f3..681007e18d 100644
--- a/docs/general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md
+++ b/docs/general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Add an Edit Mode Panel snippet in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 39fa1e32-9129-407d-914f-96f4c6e66dc8
 ---
 
@@ -81,7 +82,7 @@ Like all snippets, you add this snippet from the Snippet Gallery. To navigate to
 9. On the left side of the Snippet Gallery, under **HTML Snippet**, choose **Copy to Clipboard**.
     
   
-10. In your HTML editor, open the mapped network drive on your computer, and then open the HTML file for the master page or page layout that you're adding the snippet to. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+10. In your HTML editor, open the mapped network drive on your computer, and then open the HTML file for the master page or page layout that you're adding the snippet to. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
     
   
 11. In the HTML file, paste the snippet where you want the markup to appear.
@@ -138,16 +139,16 @@ The **<div>** where `class="DefaultContentBlock"` is what you replace with your
 <a name="AdditionalResources"> </a>
 
 
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
--  [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint)
+-  [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint.md b/docs/general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint.md
index 7e87d6545a..3bc713866a 100644
--- a/docs/general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint.md
+++ b/docs/general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Apply a master page to a site in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 04861390-84d5-40ea-b0db-6c0748eff196
 ---
 
@@ -15,7 +16,7 @@ In SharePoint, a master page defines the shared framing elements such as the chr
     
 
 > **Note:**
-> For more information about Design Manager and master pages, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint). For more information about how to create device channels, see  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels). 
+> For more information about Design Manager and master pages, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md). For more information about how to create device channels, see  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels.md). 
   
     
     
@@ -46,13 +47,13 @@ In SharePoint, a master page defines the shared framing elements such as the chr
 <a name="bk_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
 
diff --git a/docs/general-development/how-to-apply-styles-to-page-fields-in-sharepoint.md b/docs/general-development/how-to-apply-styles-to-page-fields-in-sharepoint.md
index 385036ea00..0570f03bbd 100644
--- a/docs/general-development/how-to-apply-styles-to-page-fields-in-sharepoint.md
+++ b/docs/general-development/how-to-apply-styles-to-page-fields-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Apply styles to page fields in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e227613d-0e4d-4312-924d-bb55e1fe4293
 ---
 
@@ -61,7 +62,7 @@ In the HTML page layout, each page field is wrapped in a **\<div\>** tag. To app
 </div>
 ```
 
-For more information about where styles and style references for a page layout should go, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+For more information about where styles and style references for a page layout should go, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
   
     
     
@@ -104,7 +105,7 @@ After you configure these properties in the Snippet Gallery and then update the
     
     
 
-A RichHtmlField page field contains 28 different **Allow** properties. For more information about what specific properties control, see [RichHtmlField properties](http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.publishing.webcontrols.richhtmlfield_properties) For more information about adding and configuring snippets, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+A RichHtmlField page field contains 28 different **Allow** properties. For more information about what specific properties control, see [RichHtmlField properties](http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.publishing.webcontrols.richhtmlfield_properties) For more information about adding and configuring snippets, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
   
     
     
@@ -189,7 +190,7 @@ When you change the value of the **PrefixStyleSheet** property, none of the exis
 10. In the mapped network drive on your computer, open the HTML page layout in your HTML editor.
     
     > **Note:**
-      > For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery). 
+      > For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md). 
 11. In the HTML page layout, paste the HTML snippet inside **PlaceHolderMain**.
     
   
@@ -261,7 +262,7 @@ font-size: 16pt;
     
   
 
-    For more information about where styles for a page layout should reside, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+    For more information about where styles for a page layout should reside, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
     
   
 
@@ -269,13 +270,13 @@ font-size: 16pt;
 <a name="Additional"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 
diff --git a/docs/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md b/docs/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md
index 3d22a188f8..0a6b0a146c 100644
--- a/docs/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md
+++ b/docs/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md
@@ -1,6 +1,7 @@
 ---
 title: How to Avoid getting throttled or blocked in SharePoint Online
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 33ed8106-d850-42b1-8d7f-5ba83901149c
 ---
 
@@ -8,25 +9,25 @@ ms.assetid: 33ed8106-d850-42b1-8d7f-5ba83901149c
 # How to: Avoid getting throttled or blocked in SharePoint Online
 Find out about throttling in SharePoint Online, and learn how to avoid being throttled or blocked. Includes sample CSOM and REST code you can use to make your task easier.
 
--  [What is throttling?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Whatisthrottling)
+-  [What is throttling?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Whatisthrottling)
     
   
--  [Common throttling scenarios in SharePoint Online](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Commonthrottlingscenarios)
+-  [Common throttling scenarios in SharePoint Online](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Commonthrottlingscenarios)
     
   
--  [Why can't you just tell me the exact throttling limits?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Whycantyoujusttellmetheexactthrottlinglimits)
+-  [Why can't you just tell me the exact throttling limits?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Whycantyoujusttellmetheexactthrottlinglimits)
     
   
--  [Best practices to handle throttling](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Bestpracticestohandlethrottling)
+-  [Best practices to handle throttling](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Bestpracticestohandlethrottling)
     
   
--  [GitHub CSOM code samples: SharePoint Online Throttling](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_GitHubCSOMandRESTcodesamplesSharePointOnlineThrottling)
+-  [GitHub CSOM code samples: SharePoint Online Throttling](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_GitHubCSOMandRESTcodesamplesSharePointOnlineThrottling)
     
   
--  [What should you do if you get blocked in SharePoint Online?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Whatshouldyoudoifyougetblocked)
+-  [What should you do if you get blocked in SharePoint Online?](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Whatshouldyoudoifyougetblocked)
     
   
--  [Additional resources](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#BKMK_Additionalresources)
+-  [Additional resources](how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md#BKMK_Additionalresources)
     
   
 
@@ -51,7 +52,7 @@ That said, it is extremely rare for a user to get throttled in SharePoint Online
   
     
     
-![How throttling happens](../../images/3b9184db-99a4-416e-ba1e-7f8653484cee.png)
+![How throttling happens](../images/3b9184db-99a4-416e-ba1e-7f8653484cee.png)
   
     
     
@@ -77,7 +78,7 @@ If the offending process continues to exceed usage limits, SharePoint Online mig
   
     
     
-![The 503 Server unavailable message](../../images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png)
+![The 503 Server unavailable message](../images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png)
   
     
     
@@ -100,7 +101,7 @@ The most common causes of per-user throttling in SharePoint Online are client-si
     
   - For example, after migrating files to SharePoint Online, you run a custom CSOM or REST script to update metadata on the files. The CSOM/REST script is updating a large number of files at a very high frequency, which triggers throttling. Similarly, an autocomplete UI widget using REST services, making too many calls to lists during each end user operation, may also cause throttling, depending on what other operations are consuming resources at the same time.
     
-  ![Sporadic throttling](../../images/a61afe25-9597-403f-b3fa-d3f630155021.png)
+  ![Sporadic throttling](../images/a61afe25-9597-403f-b3fa-d3f630155021.png)
   
 
   
@@ -118,7 +119,7 @@ The most common causes of per-user throttling in SharePoint Online are client-si
   
   - You customized your team site on SharePoint Online, for example, by adding a status indicator on the Home page. This status indicator updates frequently, which causes the page to make too many calls to the SharePoint Online service - this triggered throttling.
     
-  ![Steady throttling](../../images/7849d413-381f-4558-9e50-b3cc9990d3e3.png)
+  ![Steady throttling](../images/7849d413-381f-4558-9e50-b3cc9990d3e3.png)
   
 
   
diff --git a/docs/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md b/docs/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md
index df5ab143de..877ab004f3 100644
--- a/docs/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md
+++ b/docs/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md
@@ -1,6 +1,7 @@
 ---
 title: How to Back up and restore a search service application in SharePoint using VSS
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 87ee28e6-8170-4dba-8c9d-f04ab9e632dc
 ---
 
diff --git a/docs/general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md b/docs/general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md
index ffacb91dcf..342de76dd0 100644
--- a/docs/general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md
+++ b/docs/general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md
@@ -1,6 +1,7 @@
 ---
 title: How to Back up and restore SharePoint using a VSS requestor
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: cab5ba90-bd23-4cec-82d7-529e3f86ba88
 ---
 
@@ -62,7 +63,7 @@ Also, to be hosted by the SharePoint Foundation Timer service (owstimer.exe), th
 <a name="bk_addresources"> </a>
 
 
--  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service)
+-  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service.md)
     
   
 
diff --git a/docs/general-development/how-to-brand-snippets-by-using-css-in-sharepoint.md b/docs/general-development/how-to-brand-snippets-by-using-css-in-sharepoint.md
index c3b65bd1d6..f947214163 100644
--- a/docs/general-development/how-to-brand-snippets-by-using-css-in-sharepoint.md
+++ b/docs/general-development/how-to-brand-snippets-by-using-css-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Brand snippets by using CSS in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d18d07b6-1a6b-4589-a65c-932b67cef595
 ---
 
@@ -20,7 +21,7 @@ After you copy a snippet into the HTML file in your mapped drive and then save t
     
 
 > **Note:**
-> For more information about mapping a network drive, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery). 
+> For more information about mapping a network drive, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md). 
   
     
     
@@ -331,19 +332,19 @@ Instead of using only custom styles, you may have a scenario where you want to o
 <a name="Additional"> </a>
 
 
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-build-and-deploy-workflow-custom-actions.md b/docs/general-development/how-to-build-and-deploy-workflow-custom-actions.md
index c0e2d6c3e0..5eec300224 100644
--- a/docs/general-development/how-to-build-and-deploy-workflow-custom-actions.md
+++ b/docs/general-development/how-to-build-and-deploy-workflow-custom-actions.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Build and deploy workflow custom actions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 9d2fa681-30c2-4549-9df2-ea9ed757fda9
 ---
 
@@ -81,7 +82,7 @@ Visual Studio 2012 now provides a "workflow custom activity" item type within Sh
 
   
 
-  ![New Project Dialog](../../images/wfVS_NewProjectDialog.JPG)
+  ![New Project Dialog](../images/wfVS_NewProjectDialog.JPG)
   
 
   
@@ -93,7 +94,7 @@ Visual Studio 2012 now provides a "workflow custom activity" item type within Sh
 
   
 
-  ![New Item Dialog Box](../../images/wfVS_NewItem.JPG)
+  ![New Item Dialog Box](../images/wfVS_NewItem.JPG)
   
 
     
@@ -108,7 +109,7 @@ Visual Studio 2012 now provides a "workflow custom activity" item type within Sh
 
   
 
-  ![Workflow Toolbox](../../images/wfVS_WorkflowToolbox.jpg)
+  ![Workflow Toolbox](../images/wfVS_WorkflowToolbox.jpg)
   
 
     
@@ -131,7 +132,7 @@ After you create your actions module and add your action and activity files, you
   
     
     
-![Activity node in Solution Explorer](../../images/wfVS_ActivityNode.jpg)
+![Activity node in Solution Explorer](../images/wfVS_ActivityNode.jpg)
   
     
     
@@ -174,13 +175,13 @@ Activating a custom action feature on a site collection (that is, on an **SPWeb*
 <a name="bk_addlresources"> </a>
 
 
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md b/docs/general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md
index bf6580bb4d..b38b156981 100644
--- a/docs/general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md
+++ b/docs/general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Build search-driven mobile apps with the Navigation and Event Logging REST interfaces
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5b313130-500c-4ccf-80ea-b102f30e5afb
 ---
 
@@ -47,7 +48,7 @@ Typically the **Home** page is displayed when the app starts up. The **Home** pa
   
     
     
-![Build search-driven mobile apps](../../images/SP15_Buildsearch-drivenmobileappspages_home.gif)
+![Build search-driven mobile apps](../images/SP15_Buildsearch-drivenmobileappspages_home.gif)
   
     
     
@@ -68,7 +69,7 @@ GET http://server/_api/navigation/menustate?mapprovidername='GlobalNavigationSwi
 
 ```
 
-A matching response is shown in  [Example response for a Navigation REST call for a mobile app](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res#response_navigation_rest).
+A matching response is shown in  [Example response for a Navigation REST call for a mobile app](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md#response_navigation_rest).
   
     
     
@@ -89,7 +90,7 @@ The **Category** page displays many items in a selected category. Each item list
   
     
     
-![Build search-driven mobile apps](../../images/Buildsearch-drivenmobileappspages.gif)
+![Build search-driven mobile apps](../images/Buildsearch-drivenmobileappspages.gif)
   
     
     
@@ -110,7 +111,7 @@ GET http://server/_api/search/query?querytext='owstaxidProductCatalogItemCategor
 
 ```
 
-A matching response is shown in  [Example response for a Search REST query for a mobile app](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res#response_search_rest).
+A matching response is shown in  [Example response for a Search REST query for a mobile app](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md#response_search_rest).
   
     
     
@@ -135,7 +136,7 @@ If you select an item in a category, the **Item details** page appears. On this
   
     
     
-![Build search driven](../../images/Buildsearch-drivenmobileappspages_item_details.gif)
+![Build search driven](../images/Buildsearch-drivenmobileappspages_item_details.gif)
   
     
     
@@ -316,7 +317,7 @@ The service follows standard HTTP return codes: an HTTP 200 response indicates a
 <a name="bk_addresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Use OData query operations in SharePoint REST requests](http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-catch-exceptions.md b/docs/general-development/how-to-catch-exceptions.md
index 8d5628bd23..f50dadd101 100644
--- a/docs/general-development/how-to-catch-exceptions.md
+++ b/docs/general-development/how-to-catch-exceptions.md
@@ -1,9 +1,10 @@
 ---
 title: How to Catch Exceptions
+ms.date: 09/25/2017
 keywords: errors,how to,howdoi,howto
 f1_keywords:
 - errors,how to,howdoi,howto
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: de5fdb67-201b-4d7a-90a8-99ab7e51ea4e
 ---
 
@@ -204,38 +205,38 @@ End Namespace
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
   
     
     
- [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes)
+ [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-change-the-preview-page-in-sharepoint-design-manager.md b/docs/general-development/how-to-change-the-preview-page-in-sharepoint-design-manager.md
index f390bd81a6..8c05f02899 100644
--- a/docs/general-development/how-to-change-the-preview-page-in-sharepoint-design-manager.md
+++ b/docs/general-development/how-to-change-the-preview-page-in-sharepoint-design-manager.md
@@ -1,6 +1,7 @@
 ---
 title: How to Change the preview page in SharePoint Design Manager
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e5dfd8df-65de-44fc-aa97-23b4685d33ee
 ---
 
@@ -16,7 +17,7 @@ As you interact with the page, you might do something that causes SharePoint to
   
     
     
-![The Change Preview Page and Reset Preview buttons](../../images/design-manager-preview-UI.jpg)
+![The Change Preview Page and Reset Preview buttons](../images/design-manager-preview-UI.jpg)
   
     
     
@@ -98,19 +99,19 @@ Use this procedure to return to the preview page.
 <a name="addresources"> </a>
 
 
--  [Master pages, the Master Page Gallery, and page layouts in SharePoint](master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint)
+-  [Master pages, the Master Page Gallery, and page layouts in SharePoint](master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery)
+-  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md)
     
   
--  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels)
+-  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels.md)
     
   
--  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions)
+-  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions.md)
     
   
 
diff --git a/docs/general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md b/docs/general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md
index 0e0c0005ef..cf5826efc5 100644
--- a/docs/general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md
+++ b/docs/general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Configure and use push notifications in SharePoint apps for Windows Phone
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 68fa2138-86d9-4e35-9c7c-5cd292087b80
 ---
 
@@ -648,7 +649,7 @@ In this section, you create a Windows Phone app from the Windows Phone SharePoin
   
     
     
-To follow the procedures in this section, first perform the steps in the procedure described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app) to create a Visual Studio project from the Windows Phone SharePoint List Application template, using the Jobs list created in the preceding section as the target SharePoint list for the project. For the purposes of the procedures in this section, it is assumed that the name specified for the project isSPListAppForNotifications.
+To follow the procedures in this section, first perform the steps in the procedure described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md) to create a Visual Studio project from the Windows Phone SharePoint List Application template, using the Jobs list created in the preceding section as the target SharePoint list for the project. For the purposes of the procedures in this section, it is assumed that the name specified for the project isSPListAppForNotifications.
   
     
     
@@ -1286,7 +1287,7 @@ If you compile the project and deploy the app to the Windows Phone Emulator to r
   
     
     
-![Settings page for notification registration](../../images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif)
+![Settings page for notification registration](../images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif)
   
     
     
@@ -1304,7 +1305,7 @@ If you have deployed and activated the PushNotificationsList solution (developed
   
     
     
-![Toast notification (app running)](../../images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif)
+![Toast notification (app running)](../images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif)
   
     
     
@@ -1322,7 +1323,7 @@ The message displayed when your app received a toast notification while it's run
   
     
     
-![Raw notification](../../images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif)
+![Raw notification](../images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif)
   
     
     
@@ -1340,7 +1341,7 @@ If the app is not running when the item is added to the list, the phone should s
   
     
     
-![Toast notification (app not running)](../../images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif)
+![Toast notification (app not running)](../images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif)
   
     
     
@@ -1353,13 +1354,13 @@ When you add an item to the Jobs SharePoint list, the code in the event receiver
 <a name="SP15Configurepushnot_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Push Notifications Overview for Windows Phone](http://msdn.microsoft.com/en-us/library/ff402558%28VS.92%29.aspx)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-configure-item-level-security-in-sharepoint.md b/docs/general-development/how-to-configure-item-level-security-in-sharepoint.md
index a77791c32a..6833c3a426 100644
--- a/docs/general-development/how-to-configure-item-level-security-in-sharepoint.md
+++ b/docs/general-development/how-to-configure-item-level-security-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Configure item-level security in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ffd730f2-e7b7-4707-b677-d073da7df7d7
 ---
 
@@ -190,13 +191,13 @@ unchecked((int)0xffffffffL), InheritanceFlags.None, PropagationFlags.None);
 <a name="SP15Itemlevelsec_addlresources"> </a>
 
 
--  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint)
+-  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md)
     
   
 -  [Implementing a BinarySecurityDescriptorAccessor](http://msdn.microsoft.com/library/6cf70490-dd3c-49cd-bb13-ed33e938435d%28Office.15%29.aspx)
     
   
--  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint)
+-  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-configure-msmq-for-sharepoint-workflows.md b/docs/general-development/how-to-configure-msmq-for-sharepoint-workflows.md
index 589e280914..ef3b60d479 100644
--- a/docs/general-development/how-to-configure-msmq-for-sharepoint-workflows.md
+++ b/docs/general-development/how-to-configure-msmq-for-sharepoint-workflows.md
@@ -1,6 +1,7 @@
 ---
 title: How to Configure MSMQ for SharePoint workflows
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c0e130f6-c210-44ea-83ed-b327f04551d6
 ---
 
@@ -34,7 +35,7 @@ MSMQ is provided as a "Feature" in Windows Server. To enable MSMQ, do the follow
 
   
 
-  ![Figure 1. Adding the Message Queuing feature.](../../images/ng_MsmqFeature.png)
+  ![Figure 1. Adding the Message Queuing feature.](../images/ng_MsmqFeature.png)
   
 
   
@@ -56,7 +57,7 @@ MSMQ is provided as a "Feature" in Windows Server. To enable MSMQ, do the follow
 
   
 
-  ![Figure 2. The Message Queuing feature added to Ser](../../images/ng_MsmqQueues.png)
+  ![Figure 2. The Message Queuing feature added to Ser](../images/ng_MsmqQueues.png)
   
 
     
diff --git a/docs/general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md b/docs/general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md
index 4cee7ff1b9..34c59ceffc 100644
--- a/docs/general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md
+++ b/docs/general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md
@@ -1,6 +1,7 @@
 ---
 title: How to Convert an add-in-scoped external content type to tenant-scoped
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 35c5d670-e402-4641-b3c5-6f61ae1ec69b
 ---
 
@@ -111,16 +112,16 @@ The following steps show you how to create the OData-based external content type
 <a name="bk_addresources"> </a>
 
 
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint)
+-  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
 -  [Open Data Protocol](http://www.odata.org)
diff --git a/docs/general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md b/docs/general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md
index 2fa612ca5d..38e45e34d4 100644
--- a/docs/general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md
+++ b/docs/general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Convert an HTML file into a master page in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a76ab289-3256-45de-ac63-d5112a74e3c7
 ---
 
@@ -59,7 +60,7 @@ Before you convert your HTML file, here are some best practices and guidance to
     
     
 
-- Consider the SharePoint page model. For more information, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model). As you design the HTML mockups of your site, you'll probably have several HTML files for different types of pages, such as an article page or a category page that contains Web Parts that display a category of items from a catalog. But, only one HTML file will be converted into the master page. An HTML file can be converted into a master page, but an HTML file can't be converted directly into a page layout because a page layout requires page fields.
+- Consider the SharePoint page model. For more information, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md). As you design the HTML mockups of your site, you'll probably have several HTML files for different types of pages, such as an article page or a category page that contains Web Parts that display a category of items from a catalog. But, only one HTML file will be converted into the master page. An HTML file can be converted into a master page, but an HTML file can't be converted directly into a page layout because a page layout requires page fields.
     
   
 - Make sure your HTML file is XML-compliant. For the conversion to work, the HTML file must be XML-compliant. Unfortunately, this requirement overrides some HTML 5 standards—for example, in HTML 5 you can specify the **doctype** in lowercase, but in XML the **doctype** must be uppercase. Also, you should remove any **\<form\>** tags from your HTML file. Consider running your HTML file through an external XML validator to identify XML errors before conversion.
@@ -112,7 +113,7 @@ Do not put them on the same line, like this.
 ## Convert the HTML file into a master page
 <a name="Convert"> </a>
 
-Before you convert an HTML file, you first have to upload all of your design files, including your HTML file. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+Before you convert an HTML file, you first have to upload all of your design files, including your HTML file. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
   
     
     
@@ -152,11 +153,11 @@ Before you convert an HTML file, you first have to upload all of your design fil
     
     The preview page is a live server-side preview of your master page. The top of the preview displays any warnings or errors that you may have to resolve by editing the HTML file in an HTML editor. Errors must be fixed before the preview will display the master page correctly.
     
-    For more information about resolving errors and warnings, see  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint).
+    For more information about resolving errors and warnings, see  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md).
     
-    For more information about previewing the master page with different pages, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager).
+    For more information about previewing the master page with different pages, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md).
     
-    The preview page also contains a Snippets link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing static or mockup controls in your design with dynamic SharePoint controls. For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+    The preview page also contains a Snippets link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing static or mockup controls in your design with dynamic SharePoint controls. For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 8. To fix any errors, edit the HTML file that resides directly on the server by using an HTML editor to open and edit the HTML file in the mapped drive. Each time you save the HTML file, any changes are synced to the associated .master file.
@@ -166,7 +167,7 @@ Before you convert an HTML file, you first have to upload all of your design fil
     
     This **\<div\>** is the main content block. It resides inside a content placeholder named **ContentPlaceHolderMain**. At run time, when a visitor browses your site and requests a page, this content placeholder gets filled with content from a page layout that contains content in a matching content region. You should position this **\<div\>** where you want your page layouts to appear on the master page.
     
-    If your HTML file contains static or mockup content in the body of the page, now you begin the process of removing that static content from the HTML master page and applying those styles to other elements of the SharePoint page model, such as page layouts, page field controls, snippets, and display templates. For an example, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+    If your HTML file contains static or mockup content in the body of the page, now you begin the process of removing that static content from the HTML master page and applying those styles to other elements of the SharePoint page model, such as page layouts, page field controls, snippets, and display templates. For an example, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
     
   
 
@@ -227,7 +228,7 @@ The following is a breakdown of the types of markup that are added to the HTML f
 <!--CE: End PlaceHolderMain Snippet-->
 ```
 
-- **Snippets** The **\<MS\>** and **\<ME\>** ("markup start" and "markup end") tags denote the beginning and end of a SharePoint control or a snippet. A snippet is a SharePoint control that adds SharePoint functionality to your page. You can add snippets yourself by using the Snippet Gallery. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+- **Snippets** The **\<MS\>** and **\<ME\>** ("markup start" and "markup end") tags denote the beginning and end of a SharePoint control or a snippet. A snippet is a SharePoint control that adds SharePoint functionality to your page. You can add snippets yourself by using the Snippet Gallery. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
 ```HTML
   
@@ -497,13 +498,13 @@ The following is an example of markup added to an HTML file after it is converte
 <a name="Additional"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 
diff --git a/docs/general-development/how-to-crawl-associated-external-content-types-in-sharepoint.md b/docs/general-development/how-to-crawl-associated-external-content-types-in-sharepoint.md
index 3ff46cb69e..3b04b81662 100644
--- a/docs/general-development/how-to-crawl-associated-external-content-types-in-sharepoint.md
+++ b/docs/general-development/how-to-crawl-associated-external-content-types-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Crawl associated external content types in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 187ec42e-f749-4e22-abef-1df604143063
 ---
 
@@ -117,7 +118,7 @@ To mark an association so that it is crawled as a child external content type, a
 <a name="SP15crawlects_addlresources"> </a>
 
 
--  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint)
+-  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md)
     
   
 -  [Adding Associations Between External Content Types](http://msdn.microsoft.com/library/791e95ab-9b3c-413b-be12-bd0e59962c93%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint.md b/docs/general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint.md
index e3ef3875ba..31b33bc179 100644
--- a/docs/general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint.md
+++ b/docs/general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Crawl binary large objects (BLOBs) in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 99b3dd51-1651-4300-a2de-33681f4cc258
 ---
 
@@ -166,7 +167,7 @@ with the following line of code:
 <a name="SP15Crawlblobs_addlresources"> </a>
 
 
--  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint)
+-  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md)
     
   
 -  [How to: Create External Content Types](http://msdn.microsoft.com/library/811b458c-e209-46df-ba02-8db02bc658db%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-create-a-claims-provider-in-sharepoint.md b/docs/general-development/how-to-create-a-claims-provider-in-sharepoint.md
index 22fbeb4f76..c62d7d3e8e 100644
--- a/docs/general-development/how-to-create-a-claims-provider-in-sharepoint.md
+++ b/docs/general-development/how-to-create-a-claims-provider-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create a claims provider in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8f3228ca-57fd-4253-a07d-abeb63298c58
 ---
 
@@ -158,16 +159,16 @@ protected SPClaim CreateClaim(String claimType, String value, String valueType)
 <a name="SP15_HowToCreateClaimsProvider_AdditionalResources"> </a>
 
 
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint)
+-  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md)
     
   
--  [Claims provider in SharePoint](claims-provider-in-sharepoint)
+-  [Claims provider in SharePoint](claims-provider-in-sharepoint.md)
     
   
--  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint)
+-  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps.md b/docs/general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps.md
index 729678d98f..85c7d5d9ac 100644
--- a/docs/general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps.md
+++ b/docs/general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create a mashup that uses an embedded workbook and Bing Maps
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3cfeb8d7-84b8-4673-bc92-b176cba4ac3e
 ---
 
diff --git a/docs/general-development/how-to-create-a-master-page-preview-file-in-sharepoint.md b/docs/general-development/how-to-create-a-master-page-preview-file-in-sharepoint.md
index 46d0206843..fd0fc7aaf9 100644
--- a/docs/general-development/how-to-create-a-master-page-preview-file-in-sharepoint.md
+++ b/docs/general-development/how-to-create-a-master-page-preview-file-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Create a master page preview file in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6825518d-eeb2-40b0-8a5b-897025f13796
 ---
 
@@ -12,7 +13,7 @@ The **Change the look** wizard is the entry point to the SharePoint theming expe
     
     
 
-For more information, see  [Themes overview for SharePoint](themes-overview-for-sharepoint).
+For more information, see  [Themes overview for SharePoint](themes-overview-for-sharepoint.md).
 ## Core concepts to know for working with master page preview files
 <a name="Introduction"> </a>
 
@@ -26,7 +27,7 @@ Table 1 lists articles that can help you understand the core concepts for workin
 
 |**Article Title**|**Description**|
 |:-----|:-----|
-| [Themes overview for SharePoint](themes-overview-for-sharepoint) <br/> |Learn about the theming experience in SharePoint.  <br/> |
+| [Themes overview for SharePoint](themes-overview-for-sharepoint.md) <br/> |Learn about the theming experience in SharePoint.  <br/> |
 | [Choose a theme for your publishing site](http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/choose-a-theme-for-your-publishing-site-HA102891580.aspx) <br/> |Learn how to change the look and feel of a SharePoint site by using the **Change the look** wizard. <br/> |
    
 
@@ -117,7 +118,7 @@ The miscellaneous tokens are replaced with specified height and width values in
 
 ### Color tokens
 
-Color tokens are replaced with color values in the preview image. Table 3 describes two formats for color tokens. Replace  _ColorSlot_ with the annotation name of the color slot. The color tokens must be uppercase (for example, [T_THEME_COLOR_PAGEBACKGROUND]). To see the list of available color tokens, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+Color tokens are replaced with color values in the preview image. Table 3 describes two formats for color tokens. Replace  _ColorSlot_ with the annotation name of the color slot. The color tokens must be uppercase (for example, [T_THEME_COLOR_PAGEBACKGROUND]). To see the list of available color tokens, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint.md#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -141,7 +142,7 @@ The font tokens are replaced with font values in the preview image.
 - [T_ _SlotName__FONT]
     
   
-Replace  _SlotName_ with the name of the font slot. The font tokens must be uppercase (for example, [T_BODY_FONT]).To see the list of font slots and where they are used in a page, see the [Font slots](color-palettes-and-fonts-in-sharepoint#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+Replace  _SlotName_ with the name of the font slot. The font tokens must be uppercase (for example, [T_BODY_FONT]).To see the list of font slots and where they are used in a page, see the [Font slots](color-palettes-and-fonts-in-sharepoint.md#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -184,7 +185,7 @@ The tokens listed in Table 4 are used in the HTML section of the master page pre
   
     
     
-![Preinstalled theme](../../images/theme_.PNG)
+![Preinstalled theme](../images/theme_.PNG)
   
     
     
@@ -224,7 +225,7 @@ To create a master page preview file, use an existing master page preview as a s
 5. Use the **Change the look** wizard to test the master page preview with your site content.
     
     > **Note:**
-      > You can also create a design that uses the new master page by adding an item to the Composed Looks list. The design will be available in the design gallery (the first page of the **Change the look** wizard). For more information, see the [Deploy a theme by using the user interface](how-to-deploy-a-custom-theme-in-sharepoint#section2) procedure in [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint). 
+      > You can also create a design that uses the new master page by adding an item to the Composed Looks list. The design will be available in the design gallery (the first page of the **Change the look** wizard). For more information, see the [Deploy a theme by using the user interface](how-to-deploy-a-custom-theme-in-sharepoint.md#section2) procedure in [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md). 
 6. Repeat steps 3 to 5, as necessary.
     
   
@@ -233,13 +234,13 @@ To create a master page preview file, use an existing master page preview as a s
 <a name="bk_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint)
+-  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md)
     
   
--  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint)
+-  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
diff --git a/docs/general-development/how-to-create-a-minimal-master-page-in-sharepoint.md b/docs/general-development/how-to-create-a-minimal-master-page-in-sharepoint.md
index a1f3caf0c0..14392d6757 100644
--- a/docs/general-development/how-to-create-a-minimal-master-page-in-sharepoint.md
+++ b/docs/general-development/how-to-create-a-minimal-master-page-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create a minimal master page in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 634aa471-07e1-41d6-aa80-27f7ef7e9dc8
 ---
 
@@ -14,7 +15,7 @@ With Design Manager, you can convert a typical HTML file into a SharePoint maste
   
     
     
-When you create a minimal master page, Design Manager creates both the .master file and an associated HTML file, so that you can still work with only the HTML file if you prefer. Working with a minimal master page is exactly the same as working with a master page that you convert from an HTML file. The HTML file and master page are associated, so that whenever you edit and save the HTML file, those changes are synced to the associated master page. And the HTML file contains special types of markup that make syncing with the .master file possible. For more information about this association and these types of markup, see  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint).
+When you create a minimal master page, Design Manager creates both the .master file and an associated HTML file, so that you can still work with only the HTML file if you prefer. Working with a minimal master page is exactly the same as working with a master page that you convert from an HTML file. The HTML file and master page are associated, so that whenever you edit and save the HTML file, those changes are synced to the associated master page. And the HTML file contains special types of markup that make syncing with the .master file possible. For more information about this association and these types of markup, see  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md).
   
     
     
@@ -67,16 +68,16 @@ Starting with a minimal master page is useful when:
     
     The preview page is a live server-side preview of your master page.
     
-    For more information about previewing the master page with different pages, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager).
+    For more information about previewing the master page with different pages, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md).
     
-    The preview page also contains a **Snippets** link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing static or mock-up controls in your design with dynamic SharePoint controls. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+    The preview page also contains a **Snippets** link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing static or mock-up controls in your design with dynamic SharePoint controls. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
     After your master page previews successfully, you will see a **\<div\>** tag that gets added to your HTML file. You may have to scroll to the bottom of the page to see the **\<div\>** tag.
     
     This **\<div\>** is the main content block. It resides inside a content placeholder named **ContentPlaceHolderMain**. At run time, when a visitor browses your site and requests a page, this content placeholder gets filled with content from a page layout that contains content in a matching content region. You should position this **\<div\>** where you want your page layouts to appear on the master page.
     
   
-7. You can edit the HTML file that resides directly on the server by using an HTML editor to open and edit the HTML file in a mapped drive. Each time you save the HTML file, any changes are synced to the associated .master file. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+7. You can edit the HTML file that resides directly on the server by using an HTML editor to open and edit the HTML file in a mapped drive. Each time you save the HTML file, any changes are synced to the associated .master file. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
     
   
 8. To work only with the .master file and not the HTML file, you must break the association between the two files. In Design Manager, on the Edit Master Pages page, select the HTML file, open the **Properties** menu, and then choose **Edit Properties**. On the **Edit** tab, clear the **Associated File** check box, and then choose **Save**.
@@ -88,7 +89,7 @@ Starting with a minimal master page is useful when:
 ## Understand the associated HTML file
 <a name="UnderstandHTML"> </a>
 
-When you create a minimal master page, an HTML file is created that's associated with the .master file, and this HTML file contains many lines of markup that are specific to how SharePoint works. You can safely ignore most of this markup, and most of it does not appear in the final markup of your site when you view source in the browser, but this markup is critical for syncing changes from the HTML file to the .master file that SharePoint actually uses. Each time you save a change to your HTML file, this SharePoint markup makes it possible for that same change to be made to the associated .master file in the background. For more information, see the markup samples in  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint).
+When you create a minimal master page, an HTML file is created that's associated with the .master file, and this HTML file contains many lines of markup that are specific to how SharePoint works. You can safely ignore most of this markup, and most of it does not appear in the final markup of your site when you view source in the browser, but this markup is critical for syncing changes from the HTML file to the .master file that SharePoint actually uses. Each time you save a change to your HTML file, this SharePoint markup makes it possible for that same change to be made to the associated .master file in the background. For more information, see the markup samples in  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md).
   
     
     
@@ -97,16 +98,16 @@ When you create a minimal master page, an HTML file is created that's associated
 <a name="Additional"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 
diff --git a/docs/general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md b/docs/general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md
index d8c35976c9..2e74f9eeda 100644
--- a/docs/general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md
+++ b/docs/general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create a mobile app in SharePoint that contains data from an external data source
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f1d62256-aca0-4a59-8145-0add9e68a449
 ---
 
@@ -14,7 +15,7 @@ SharePoint enables you to build mobile applications that can access external dat
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -99,7 +100,7 @@ Next you need to set permissions on the BDC model to specify who can execute the
 
   
 
-  ![Choosing permissions for BDC model](../../images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png)
+  ![Choosing permissions for BDC model](../images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png)
   
 
   
@@ -117,7 +118,7 @@ Next you need to set permissions on the BDC model to specify who can execute the
 
   
 
-  ![Setting BDC object permissions](../../images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png)
+  ![Setting BDC object permissions](../images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png)
   
 
   
@@ -148,7 +149,7 @@ Next you need to set permissions on the BDC model to specify who can execute the
 ## Step 3: Create an external list
 <a name="HowToCreateSimpleExternalListBasedPhoneApp_Step3"> </a>
 
-Now that you've uploaded the BDC model and set permissions, you can create an external list based on the external content type defined in the BDC model. In this step, you will create an external list based on the Customer external content type defined in the Northwind BDC model you uploaded in  [Step 1: Upload a BDC metadata model](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa#HowToCreateSimpleExternalListBasedPhoneApp_Step1).
+Now that you've uploaded the BDC model and set permissions, you can create an external list based on the external content type defined in the BDC model. In this step, you will create an external list based on the Customer external content type defined in the Northwind BDC model you uploaded in  [Step 1: Upload a BDC metadata model](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md#HowToCreateSimpleExternalListBasedPhoneApp_Step1).
   
     
     
@@ -181,7 +182,7 @@ Now that you've uploaded the BDC model and set permissions, you can create an ex
 ## Step 4: Create a mobile app using the Windows Phone SharePoint List Application template
 <a name="HowToCreateSimpleExternalListBasedPhoneApp_Step4"> </a>
 
-Your external list is ready and you can now create a Windows Phone 7 app that connects to the external list you created in  [Step 3: Create an external list](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa#HowToCreateSimpleExternalListBasedPhoneApp_Step3) and display Customer data from the Northwind database.
+Your external list is ready and you can now create a Windows Phone 7 app that connects to the external list you created in  [Step 3: Create an external list](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md#HowToCreateSimpleExternalListBasedPhoneApp_Step3) and display Customer data from the Northwind database.
   
     
     
@@ -201,7 +202,7 @@ Your external list is ready and you can now create a Windows Phone 7 app that co
 
   
 
-  ![SharePoint list mobile app template](../../images/SP15Con_VisualStudioMobileSPListTemplate.png)
+  ![SharePoint list mobile app template](../images/SP15Con_VisualStudioMobileSPListTemplate.png)
   
 
   
@@ -252,7 +253,7 @@ Now that the app is ready to run, you can test it using phone emulator.
 
   
 
-  ![BDC Mobile App Demo](../../images/SPCon15_BDCMobileAppDemo.png)
+  ![BDC Mobile App Demo](../images/SPCon15_BDCMobileAppDemo.png)
   
 
   
@@ -274,19 +275,19 @@ Now that the app is ready to run, you can test it using phone emulator.
     
     
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio)
+-  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md)
     
   
 -  [How to: Create External Lists in SharePoint](http://msdn.microsoft.com/en-us/library/ee558778.aspx)
     
   
--  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app)
+-  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=27570)
diff --git a/docs/general-development/how-to-create-a-page-layout-in-sharepoint.md b/docs/general-development/how-to-create-a-page-layout-in-sharepoint.md
index e54f36e148..9d712938e2 100644
--- a/docs/general-development/how-to-create-a-page-layout-in-sharepoint.md
+++ b/docs/general-development/how-to-create-a-page-layout-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Create a page layout in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5447e6a1-2f14-4667-81d0-7514b468be80
 ---
 
@@ -117,7 +118,7 @@ Before you begin, you need to know which content type and master page the page l
 
   
 
-  ![The menu that opens when the gear icon is clicked on a publishing site. One item is Design Manager.](../../images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG)
+  ![The menu that opens when the gear icon is clicked on a publishing site. One item is Design Manager.](../images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG)
   
 
   
@@ -157,11 +158,11 @@ Before you begin, you need to know which content type and master page the page l
     
     The preview page is a live server-side preview of your page layout. The top of the preview displays any warnings or errors that you may have to resolve by editing the HTML file in an HTML editor. Errors must be fixed before the preview will display the page layout correctly.
     
-    For more information about resolving errors and warnings, see  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint).
+    For more information about resolving errors and warnings, see  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md).
     
-    For more information about previewing the page layout, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager).
+    For more information about previewing the page layout, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md).
     
-    The preview page also contains a **Snippets** link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing mockup controls in your design with dynamic SharePoint controls. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+    The preview page also contains a **Snippets** link in the upper-right corner. This link opens the Snippet Gallery, where you can begin replacing mockup controls in your design with dynamic SharePoint controls. For more information, see [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 10. To fix any errors, edit the HTML file that resides directly on the server by using an HTML editor to open and edit the HTML file in the mapped drive. Each time you save the HTML file, any changes are synced to the associated .aspx file.
@@ -288,7 +289,7 @@ If you have different device channels, you likely want your page layouts to rend
 ## Understanding the markup in the HTML page layout
 <a name="UnderstandMarkup"> </a>
 
-When you create a page layout, an .aspx file gets created that SharePoint uses, and some HTML markup gets added to the HTML version of the page layout. When you edit the HTML page layout in your HTML editor, it might be helpful to understand the purpose of some of this markup. Most of it is similar to the markup that gets added to an HTML master page. For more information, see  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint).
+When you create a page layout, an .aspx file gets created that SharePoint uses, and some HTML markup gets added to the HTML version of the page layout. When you edit the HTML page layout in your HTML editor, it might be helpful to understand the purpose of some of this markup. Most of it is similar to the markup that gets added to an HTML master page. For more information, see  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md).
   
     
     
@@ -329,13 +330,13 @@ The markup that is unique to page layouts is page fields that are added to the p
 <a name="AdditionalResources"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 
diff --git a/docs/general-development/how-to-create-a-udf-that-calls-a-web-service.md b/docs/general-development/how-to-create-a-udf-that-calls-a-web-service.md
index da7458221a..f3c576666c 100644
--- a/docs/general-development/how-to-create-a-udf-that-calls-a-web-service.md
+++ b/docs/general-development/how-to-create-a-udf-that-calls-a-web-service.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Create a UDF That Calls a Web Service
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,UDF
 f1_keywords:
 - how to,howdoi,howto,UDF
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 360c5766-4b5d-4a48-9f23-8955036924ce
 ---
 
@@ -112,7 +113,7 @@ Namespace ZipCodeUdfSample
         End Sub
 ```
 
-For more information about how to test and call UDFs from cells, see  [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf).
+For more information about how to test and call UDFs from cells, see  [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md).
   
     
     
@@ -292,38 +293,38 @@ End Namespace
   
     
     
- [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference)
+ [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference.md)
   
     
     
- [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf)
+ [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md)
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells)
+ [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint.md b/docs/general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint.md
index dde4fd9303..f48b7df769 100644
--- a/docs/general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint.md
+++ b/docs/general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create a VSS requestor for use with SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 63b3145b-ece2-4acf-b58a-fd8b50303030
 ---
 
@@ -22,10 +23,10 @@ Learn how to use the requestor to back up and restore SharePoint and search appl
     
     
 
--  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor)
+-  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md)
     
   
--  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using)
+-  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md)
     
   
 
@@ -33,7 +34,7 @@ Learn how to use the requestor to back up and restore SharePoint and search appl
 <a name="bk_addresources"> </a>
 
 
--  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service)
+-  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service.md)
     
   
 
diff --git a/docs/general-development/how-to-create-a-windows-phone-sharepoint-list-app.md b/docs/general-development/how-to-create-a-windows-phone-sharepoint-list-app.md
index 57ac32164c..7e4a70aedb 100644
--- a/docs/general-development/how-to-create-a-windows-phone-sharepoint-list-app.md
+++ b/docs/general-development/how-to-create-a-windows-phone-sharepoint-list-app.md
@@ -1,17 +1,18 @@
 ---
 title: How to Create a Windows Phone SharePoint list app
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3e40c475-f4c1-4a4f-a3e5-1a55f814d272
 ---
 
 
 # How to: Create a Windows Phone SharePoint list app
 Create a Windows Phone app in Visual Studio based on the Windows Phone SharePoint List Application template.
-Installing the Windows Phone SharePoint SDK makes two Windows Phone SharePoint Application templates available to you in Visual Studio 2010 or Visual Studio 2010 Express for Windows Phone. (See  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint).) Using the Windows Phone SharePoint List Application template, you can follow the steps of a wizard to create a functional Windows Phone app that can access and manipulate data in a SharePoint list.
+Installing the Windows Phone SharePoint SDK makes two Windows Phone SharePoint Application templates available to you in Visual Studio 2010 or Visual Studio 2010 Express for Windows Phone. (See  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md).) Using the Windows Phone SharePoint List Application template, you can follow the steps of a wizard to create a functional Windows Phone app that can access and manipulate data in a SharePoint list.
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
 
 
 ## Create the Windows Phone SharePoint list application
@@ -31,7 +32,7 @@ In your Windows Phone SharePoint list app, you can access most of the lists that
   
     
     
-![Contacts list for Contoso marketing team](../../images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif)
+![Contacts list for Contoso marketing team](../images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif)
   
     
     
@@ -60,7 +61,7 @@ In your Windows Phone SharePoint list app, you can access most of the lists that
 
   
 
-  ![SPList Wizard Error](../../images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png)
+  ![SPList Wizard Error](../images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png)
   
 
     You can resolve this error by giving sufficient privileges to the account with which the developer is running the SPList wizard. Rerun **Splist wizard** after sufficient rights are given.
@@ -133,7 +134,7 @@ The deployment target for the solution is set to Windows Phone Emulator by defau
   
     
     
-![SharePoint list items in a Windows Phone app](../../images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif)
+![SharePoint list items in a Windows Phone app](../images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif)
   
     
     
@@ -151,7 +152,7 @@ While running a Windows Phone app, the authentication error shown in Figure 4 ca
   
     
     
-![Mobile App Error](../../images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png)
+![Mobile App Error](../images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png)
   
     
     
@@ -198,7 +199,7 @@ If you based your Windows Phone app on the data from a Contacts list, as shown i
   
     
     
-![DisplayForm view of a Contacts list item](../../images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif)
+![DisplayForm view of a Contacts list item](../images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif)
   
     
     
@@ -211,10 +212,10 @@ Notice the **Edit** and **Delete** buttons on the Application Bar in this page o
 <a name="SP15Createwinphoneapp_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md b/docs/general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md
index a4788c7c0a..cbbbe6068b 100644
--- a/docs/general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md
+++ b/docs/general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create an add-in-scoped external content type in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: de4b50a3-84da-48ce-9ba0-fe06571e52a8
 ---
 
@@ -27,7 +28,7 @@ To get started developing add-in-scoped external content types, you need the fol
 - A published OData service available through the Internet
     
   
-For information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -99,7 +100,7 @@ For complete steps for creating SharePoint Add-ins, see the following:
 <a name="bk_addresources"> </a>
 
 
--  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint)
+-  [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint.md)
     
   
 -  [Choose patterns for developing and hosting your SharePoint Add-in](http://msdn.microsoft.com/library/05ce5435-0a03-4ddc-976b-c33b08d03457%28Office.15%29.aspx)
@@ -108,13 +109,13 @@ For complete steps for creating SharePoint Add-ins, see the following:
 -  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md b/docs/general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md
index b8a4ccb929..798c36d0e4 100644
--- a/docs/general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md
+++ b/docs/general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create an external content type from an OData source in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bc60ea49-c44e-4531-af62-06b8cf77d35d
 ---
 
@@ -27,7 +28,7 @@ To create an external content type from an Open Data protocol (OData) source, yo
 - A published OData service available through the Internet
     
   
-For information about how to set up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about how to set up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -51,8 +52,8 @@ The following articles provide background information about OData and the OData
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint) <br/> |Get started with creating external content types based on OData sources, and learn how to use that data in SharePoint or Office components.  <br/> |
-| [External content types in SharePoint](external-content-types-in-sharepoint) <br/> |Learn about BCS external content types and what you need to start creating them in SharePoint.  <br/> |
+| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md) <br/> |Get started with creating external content types based on OData sources, and learn how to use that data in SharePoint or Office components.  <br/> |
+| [External content types in SharePoint](external-content-types-in-sharepoint.md) <br/> |Learn about BCS external content types and what you need to start creating them in SharePoint.  <br/> |
    
 
 ## Create an OData-based external content type
@@ -159,7 +160,7 @@ After you have built an external content type, you can then use it to present da
   
     
     
-For more information, see  [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint).
+For more information, see  [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md).
   
     
     
@@ -168,16 +169,16 @@ For more information, see  [How to: Create an external list using an OData data
 <a name="bkmk_Addres"> </a>
 
 
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md b/docs/general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md
index 422a3c713c..e41f24205e 100644
--- a/docs/general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md
+++ b/docs/general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create an external list using an OData data source in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 601fbfce-a0c6-43dd-8398-540d094c083c
 ---
 
@@ -30,10 +31,10 @@ The following components are needed to create an external list from an OData sou
 - Office Developer Tools for Visual Studio 2012
     
   
-- A published external content type based on an OData source: For instructions, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint).
+- A published external content type based on an OData source: For instructions, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md).
     
   
-For information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about setting up a SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -50,7 +51,7 @@ The following articles provide information about SharePoint Add-ins and other ba
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint) <br/> |Learn about Business Connectivity Services and how you can expose external data in SharePoint.  <br/> |
+| [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md) <br/> |Learn about Business Connectivity Services and how you can expose external data in SharePoint.  <br/> |
 | [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn about the new app model in SharePoint that enables you to create apps, which are small, easy-to-use solutions for end users.  <br/> |
 | [Choose patterns for developing and hosting your SharePoint Add-in](http://msdn.microsoft.com/library/05ce5435-0a03-4ddc-976b-c33b08d03457%28Office.15%29.aspx) <br/> |Learn about the different ways that you can host SharePoint Add-ins.  <br/> |
    
@@ -64,7 +65,7 @@ The following procedures will show you how to create a new external list, bind i
     
 
 > **Note:**
-> The first step assumes that you have successfully created an external content type, as described in  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint). 
+> The first step assumes that you have successfully created an external content type, as described in  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md). 
   
     
     
@@ -113,19 +114,19 @@ For testing purposes, you may want to modify the AppManifest.xml file so that th
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
 -  [How to: Create a basic autohosted app for SharePoint](http://msdn.microsoft.com/library/0572894d-c437-4b7d-8ac6-8405496e2145%28Office.15%29.aspx)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md b/docs/general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md
index 71bbba5679..6749b31a4d 100644
--- a/docs/general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md
+++ b/docs/general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create an OData data service for use as a BCS external system
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7d7b3aa6-85b7-400d-8ea5-50bebac56a1d
 ---
 
@@ -42,7 +43,7 @@ The following are required to create the OData service in this article:
 - Office Developer Tools for Visual Studio 2012
     
   
-For information about setting up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about setting up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -59,8 +60,8 @@ Table 1 lists articles that will help you understand the core concepts of buildi
 
 |**Resource**|**Description**|
 |:-----|:-----|
-| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint) <br/> |Provides information to help you start creating external content types based on OData sources and using that data in SharePoint or Office 2013 components.  <br/> |
-| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source and create a reusable external content type to use in BCS in SharePoint.  <br/> |
+| [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md) <br/> |Provides information to help you start creating external content types based on OData sources and using that data in SharePoint or Office 2013 components.  <br/> |
+| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source and create a reusable external content type to use in BCS in SharePoint.  <br/> |
 | [Open Data Protocol](http://www.odata.org) <br/> |Provides information about the Open Data protocol, including protocol definitions, architectural information and usage examples.  <br/> |
 | [WCF Data Services Overview](http://msdn.microsoft.com/en-us/library/cc668794.aspx) <br/> |WCF Data Services enables creation and consumption of data services for the web or an intranet by using OData. OData enables you to expose your data as resources that are addressable by URIs.  <br/> |
 | [Developing and Deploying WCF Data Services](http://msdn.microsoft.com/en-us/library/gg258442) <br/> |Provides information about developing and deploying WCF Data Services.  <br/> |
@@ -303,22 +304,22 @@ To notify SharePoint that changes have been made, you also need to create a serv
 <a name="bkmk_Addresources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint)
+-  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md b/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md
index 92130f8976..e4c1a68f83 100644
--- a/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md
+++ b/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e8c21960-6ea0-43c0-821e-2db2a0ecec90
 ---
 
@@ -14,7 +15,7 @@ In SharePoint, a social feed is a collection of threads that represent conversat
   
     
     
-For more information about working with  [SocialFeedManager](http://msdn.microsoft.com/library/651fdf0f-841d-88f9-1e07-fcb3ad8c9410%28Office.15%29.aspx) or for information about using other APIs to work with social feeds, see [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint).
+For more information about working with  [SocialFeedManager](http://msdn.microsoft.com/library/651fdf0f-841d-88f9-1e07-fcb3ad8c9410%28Office.15%29.aspx) or for information about using other APIs to work with social feeds, see [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md).
   
     
     
@@ -92,9 +93,9 @@ To create an application page that uses the JavaScript object model to work with
 
 11. To add the logic to work with feeds, replace the comment between the **script** tags with the code example from one of the following scenarios:
     
-  -  [Publish posts and replies to the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bkmk_PubPosts)
-  -  [Retrieve social feeds](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bkmk_GetFeeds)
-  -  [Delete posts and replies from the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bkmk_DeletePosts)
+  -  [Publish posts and replies to the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bkmk_PubPosts)
+  -  [Retrieve social feeds](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bkmk_GetFeeds)
+  -  [Delete posts and replies from the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bkmk_DeletePosts)
     
   
 12. To test the application page, on the menu bar, choose **Debug**, **Start Debugging**. If you are prompted to modify the web.config file, choose the **OK** button.
@@ -122,7 +123,7 @@ The following code example publishes a post and a reply. It shows how to:
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bk_CreateApp) procedure.
+> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bk_CreateApp) procedure.
   
     
     
@@ -195,13 +196,13 @@ The following code example retrieves feeds for the current user and a target use
 - Iterate through the feeds to find all non-reference threads and to get information about threads and posts. Reference threads represent notifications that contain information about another thread. For example, if a user mentions someone in a post, the server generates a **MentionReference**-type thread that contains the link to the original post and other metadata about the post.
     
   
-For more information about feed types, see  [Overview of feed types in the My Site Social API](work-with-social-feeds-in-sharepoint#bkmk_FeedTypes). For more information about reference threads, see  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds).
+For more information about feed types, see  [Overview of feed types in the My Site Social API](work-with-social-feeds-in-sharepoint.md#bkmk_FeedTypes). For more information about reference threads, see  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md).
   
     
     
 
 > **Note:**
-> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bk_CreateApp) procedure. Then, change the placeholder value for the **targetUser** variable before you run the code.
+> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bk_CreateApp) procedure. Then, change the placeholder value for the **targetUser** variable before you run the code.
   
     
     
@@ -333,7 +334,7 @@ The following code example deletes a post or a reply. It shows how to:
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr#bk_CreateApp) procedure. This example assumes that the current user's newsfeed contains at least one post.
+> Paste the following code between the **script** tags that you added in the [Create the application page](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md#bk_CreateApp) procedure. This example assumes that the current user's newsfeed contains at least one post.
   
     
     
@@ -425,19 +426,19 @@ function RequestFailed(sender, args) {
 <a name="bk_addResources"> </a>
 
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
 -  [SP.Social namespace (sp.userprofiles)](http://msdn.microsoft.com/library/43d47f01-c085-0e77-bd01-48bcb7d5bb35%28Office.15%29.aspx)
     
   
--  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli)
+-  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md)
     
   
--  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)
+-  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)
     
   
--  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds)
+-  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md)
     
   
 
diff --git a/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md b/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md
index c4cd8ee039..5d9d1d4886 100644
--- a/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md
+++ b/docs/general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c8d68632-1b55-454c-961a-f3ddad731bf6
 ---
 
@@ -14,7 +15,7 @@ In SharePoint, a social feed is a collection of threads that represent conversat
   
     
     
-For more information about working with  [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) or for information about using other APIs to work with social feeds, see [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint).
+For more information about working with  [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) or for information about using other APIs to work with social feeds, see [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md).
   
     
     
@@ -68,9 +69,9 @@ To create a console application that uses the .NET client object model to work w
   
 6. Replace the contents of the **Program** class with the code example from one of the following scenarios:
     
-   -  [Publish posts and replies to the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli#bkmk_PubPosts) 
-   -  [Retrieve social feeds](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli#bkmk_GetFeeds) 
-   -  [Delete posts and replies from the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli#bkmk_DeletePosts)
+   -  [Publish posts and replies to the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md#bkmk_PubPosts) 
+   -  [Retrieve social feeds](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md#bkmk_GetFeeds) 
+   -  [Delete posts and replies from the social feed](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md#bkmk_DeletePosts)
     
 7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**.
     
@@ -223,7 +224,7 @@ The following code example retrieves feeds for the current user and a target use
 - Iterate through the feeds to find all non-reference threads and to get information about threads and posts. Reference threads represent notifications that contain information about another thread. For example, if a user mentions someone in a post, the server generates a **MentionReference**-type thread that contains the link to the original post and other metadata about the post.
     
   
-For more information about feed types, see  [Overview of feed types](work-with-social-feeds-in-sharepoint#bkmk_FeedTypes). For more information about reference threads, see  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds).
+For more information about feed types, see  [Overview of feed types](work-with-social-feeds-in-sharepoint.md#bkmk_FeedTypes). For more information about reference threads, see  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md).
   
     
     
@@ -468,7 +469,7 @@ namespace SocialFeedCSOM
 ## Next steps
 <a name="bkmk_DeletePosts"> </a>
 
- [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep)
+ [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md)
   
     
     
@@ -477,16 +478,16 @@ namespace SocialFeedCSOM
 <a name="bk_addResources"> </a>
 
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
--  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr)
+-  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md)
     
   
--  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)
+-  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)
     
   
--  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds)
+-  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md)
     
   
 
diff --git a/docs/general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20.md b/docs/general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20.md
index 2aafbeae79..f031dcdb82 100644
--- a/docs/general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20.md
+++ b/docs/general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Create Custom SharePoint Workflow Forms with Visual Studio 2012
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 26873259-330c-493f-b935-297a7a5a086d
 ---
 
@@ -47,7 +48,7 @@ How does this affect workflow forms? Recall that starting in SharePoint 2010 Mic
   
     
     
-To alleviate this limitation, Microsoft extended CSOM to include an API for interacting with the workflow engine. To connect a SharePoint farm to the Workflow Manager farm, you must install the Workflow Manager Client on the SharePoint servers. This component serves as a proxy that SharePoint uses to communicate with the Workflow Manager farm. The Workflow Services CSOM API is effectively the client-side component that you use to interact with the new workflow engine. For more information about SharePoint Workflow Services CSOM, see  [Working with the SharePoint Workflow Services Client Side Object Model](working-with-the-sharepoint-workflow-services-client-side-object-model).
+To alleviate this limitation, Microsoft extended CSOM to include an API for interacting with the workflow engine. To connect a SharePoint farm to the Workflow Manager farm, you must install the Workflow Manager Client on the SharePoint servers. This component serves as a proxy that SharePoint uses to communicate with the Workflow Manager farm. The Workflow Services CSOM API is effectively the client-side component that you use to interact with the new workflow engine. For more information about SharePoint Workflow Services CSOM, see  [Working with the SharePoint Workflow Services Client Side Object Model](working-with-the-sharepoint-workflow-services-client-side-object-model.md).
   
     
     
@@ -77,7 +78,7 @@ Prior the release of SharePoint, there were three types of custom workflow forms
   
     
     
-SharePoint improves how you work with workflow tasks in that you can create custom outcome buttons for specific scenarios. You can also customize the rendering and behavior of specific columns in task items using the new Client Side Rendering (CSR), which was introduced in SharePoint. Note that CSR uses JavaScript executed in the client. These topics are covered in the article  [Working with Tasks in SharePoint Workflows using Visual Studio 2012](working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012). You can also get more information in the article  [Customize a list view in SharePoint Add-ins using client-side rendering](http://msdn.microsoft.com/library/8d5cabb2-70d0-46a0-bfe0-9e21f8d67d86%28Office.15%29.aspx).
+SharePoint improves how you work with workflow tasks in that you can create custom outcome buttons for specific scenarios. You can also customize the rendering and behavior of specific columns in task items using the new Client Side Rendering (CSR), which was introduced in SharePoint. Note that CSR uses JavaScript executed in the client. These topics are covered in the article  [Working with Tasks in SharePoint Workflows using Visual Studio 2012](working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md). You can also get more information in the article  [Customize a list view in SharePoint Add-ins using client-side rendering](http://msdn.microsoft.com/library/8d5cabb2-70d0-46a0-bfe0-9e21f8d67d86%28Office.15%29.aspx).
   
     
     
@@ -145,7 +146,7 @@ In this walkthrough we demonstrate how to create a custom association form and u
 
   
 
-  ![SharePoint Customization Wizard](../../images/CreateSharePoint2013Workflows.png)
+  ![SharePoint Customization Wizard](../images/CreateSharePoint2013Workflows.png)
   
 
   
@@ -160,7 +161,7 @@ In this walkthrough we demonstrate how to create a custom association form and u
 
   
 
-  ![The Add New Item dialog box.](../../images/CreateSharePoint2013WorkflowsFig2.png)
+  ![The Add New Item dialog box.](../images/CreateSharePoint2013WorkflowsFig2.png)
   
 
   
@@ -278,7 +279,7 @@ With the form complete, the next step is to configure the workflow to use the va
 
   
 
-  ![Creating a string variable.](../../images/CreatSharePoint2013WorkflowsFig4.png)
+  ![Creating a string variable.](../images/CreatSharePoint2013WorkflowsFig4.png)
   
 
   
@@ -290,7 +291,7 @@ With the form complete, the next step is to configure the workflow to use the va
 
   
 
-  ![Set the Result property.](../../images/CreateSharePoint2013WorkflowsFig5.png)
+  ![Set the Result property.](../images/CreateSharePoint2013WorkflowsFig5.png)
   
 
   
@@ -326,7 +327,7 @@ With the form complete, the next step is to configure the workflow to use the va
 
   
 
-  ![Figure 5. Custom workflow association form](../../images/ngFormsFig5.png)
+  ![Figure 5. Custom workflow association form](../images/ngFormsFig5.png)
   
 
   
@@ -341,7 +342,7 @@ With the form complete, the next step is to configure the workflow to use the va
 
   
 
-  ![Figure 6. Association form: Status pane](../../images/ngFormsFig6.png)
+  ![Figure 6. Association form: Status pane](../images/ngFormsFig6.png)
   
 
   
@@ -383,7 +384,7 @@ This walkthrough demonstrates creating a custom association form and using it to
 
   
 
-  ![Figure 7. Solution Explorer view of the project](../../images/ngFormsFig7.png)
+  ![Figure 7. Solution Explorer view of the project](../images/ngFormsFig7.png)
   
 
   
@@ -403,7 +404,7 @@ The workflow initiation form prompts users for two pieces of information that it
 
   
 
-  ![Figure 8. Configuring initiation form arguments](../../images/ngFormsFig8.png)
+  ![Figure 8. Configuring initiation form arguments](../images/ngFormsFig8.png)
   
 
   
@@ -423,7 +424,7 @@ The workflow initiation form prompts users for two pieces of information that it
 
   
 
-  ![Figure 9. Configuring a WriteToHistory activity](../../images/ngFormsFig9.png)
+  ![Figure 9. Configuring a WriteToHistory activity](../images/ngFormsFig9.png)
   
 
   
@@ -477,7 +478,7 @@ When you added the new initiation form to the project, Visual Studio 2012 automa
   
     
     
-![Figure 10. Code comment to disregard](../../images/ngFormsFig10.png)
+![Figure 10. Code comment to disregard](../images/ngFormsFig10.png)
   
     
     
@@ -617,7 +618,7 @@ Because the workflow definition contains a reference to an initiation form, the
   
     
     
-![Starting the workflow instance.](../../images/CreateSharePoint2013WorkflowsFig7.png)
+![Starting the workflow instance.](../images/CreateSharePoint2013WorkflowsFig7.png)
   
     
     
@@ -635,7 +636,7 @@ After starting the workflow, the page redirects the user back to the originating
   
     
     
-![The sample workflow.](../../images/CreateSharePoint2013WorkflowsFig8.png)
+![The sample workflow.](../images/CreateSharePoint2013WorkflowsFig8.png)
   
     
     
@@ -663,7 +664,7 @@ SharePoint introduced several improvements to workflows. This article detailed t
 -  [Workflow Association and Initiation Forms (SharePoint Foundation)](http://msdn.microsoft.com/en-us/library/office/ms481192%28v=office.14%29.aspx)
     
   
--  [Working with the SharePoint Workflow Services Client Side Object Model](working-with-the-sharepoint-workflow-services-client-side-object-model)
+-  [Working with the SharePoint Workflow Services Client Side Object Model](working-with-the-sharepoint-workflow-services-client-side-object-model.md)
     
   
 -  [Customize a list view in SharePoint Add-ins using client-side rendering](http://msdn.microsoft.com/library/8d5cabb2-70d0-46a0-bfe0-9e21f8d67d86%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint.md b/docs/general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint.md
index af5d6db92f..385cbb34ca 100644
--- a/docs/general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint.md
+++ b/docs/general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create external content types for SQL Server in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7fe2fbf0-546b-4a16-b02e-a0960bfb3842
 ---
 
@@ -513,13 +514,13 @@ The external content type is now available for use in SharePoint and Office 2013
 <a name="AR"> </a>
 
 
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
 -  [Deploy a Business Connectivity Services on-premises solution in SharePoint](http://msdn.microsoft.com/library/4692ebba-90eb-4d72-ac12-e90c4d4ee7ae.aspx)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
 -  [Configure the Secure Store Service in SharePoint](http://msdn.microsoft.com/library/29C0BC76-D835-401B-A2FB-ABB069E84125.aspx)
diff --git a/docs/general-development/how-to-create-external-event-receivers.md b/docs/general-development/how-to-create-external-event-receivers.md
index 5e1dae464b..2523c070dc 100644
--- a/docs/general-development/how-to-create-external-event-receivers.md
+++ b/docs/general-development/how-to-create-external-event-receivers.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create external event receivers
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c6d5f486-6247-47f9-9876-fab12f13342f
 ---
 
@@ -699,7 +700,7 @@ Office Developer Tools for Visual Studio 2013 added an autogeneration wizard tha
     
     This starts the **SharePoint Customization Wizard**, which is used to build the external content type automatically.
     
-    For more information about how to create external content types, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint).
+    For more information about how to create external content types, see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md).
     
   
 You will now modify the XML that was generated in the previous step to add a method for Subscribe. This will allow BCS to communicate with the external system when someone subscribes to be notified about external data changes.
@@ -959,22 +960,22 @@ Now you can see the app in action.
 <a name="bkmk_additionalresources"> </a>
 
 
--  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint)
+-  [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md)
     
   
--  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint)
+-  [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md b/docs/general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md
index 746ee27811..22822fef27 100644
--- a/docs/general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md
+++ b/docs/general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create filter data providers for PerformancePoint Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 25508ec6-86bf-4eea-acf0-00f88e4faa55
 ---
 
@@ -103,7 +104,7 @@ The following code example shows how a data provider retrieves values from a web
   
     
     
-Before you can compile this code example, you must configure your development environment as described in  [To create and configure the provider class](#BKMK_ConfigClass).
+Before you can compile this code example, you must configure your development environment as described in  [To create and configure the provider class](#bk_createconfig).
   
     
     
@@ -305,10 +306,10 @@ After you create a data provider and a filter editor (including its user interfa
 <a name="bk_next"> </a>
 
 
--  [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint)
+-  [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md)
     
   
--  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint)
+-  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md b/docs/general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md
index c8389d993f..2dc6385573 100644
--- a/docs/general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md
+++ b/docs/general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md
@@ -1,4 +1,8 @@
-
+---
+title: How to Create filter editors for PerformancePoint Services in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # How to: Create filter editors for PerformancePoint Services in SharePoint
@@ -343,7 +347,7 @@ The following code example creates, retrieves, and updates custom filters. This
   
     
     
-Before you can compile this code example, you must configure your development environment as described in  [Create and configure the editor class for a filter editor in PerformancePoint Services](#BKMK_ConfigFEd).
+Before you can compile this code example, you must configure your development environment as described in  [Create and configure the editor class for a filter editor in PerformancePoint Services](#bk_intro).
   
     
     
diff --git a/docs/general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md b/docs/general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md
index 20be5d9c26..f00201cc29 100644
--- a/docs/general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md
+++ b/docs/general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md
@@ -1,3 +1,8 @@
+---
+title: How to Create report editors for PerformancePoint Services in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # How to: Create report editors for PerformancePoint Services in SharePoint
@@ -470,10 +475,10 @@ After you create a report editor (including its user interface, if required) and
 <a name="bk_addResources"> </a>
 
 
--  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint)
+-  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md)
     
   
--  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint)
+-  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md b/docs/general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md
index 5b23d71512..693a210237 100644
--- a/docs/general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md
+++ b/docs/general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md
@@ -1,3 +1,8 @@
+---
+title: Create report renderers for PerformancePoint Services in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 
@@ -85,7 +90,7 @@ The class in the following code example creates a report renderer that displays
   
     
     
-Before you can compile this code example, you must configure your development environment as described in  [To create and configure the renderer class](#BKMK_ConfigRR).
+Before you can compile this code example, you must configure your development environment as described in  [To create and configure the renderer class](#BKMK_ConfigRenderer).
   
     
     
@@ -265,10 +270,10 @@ After you create a report renderer and a report editor (including its user inter
 <a name="bk_addResources"> </a>
 
 
--  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint)
+-  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md)
     
   
--  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint)
+-  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md b/docs/general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md
index 65d34189eb..7b37aacd7a 100644
--- a/docs/general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md
+++ b/docs/general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md
@@ -1,3 +1,9 @@
+---
+title: Create scorecard transforms for PerformancePoint Services in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # How to: Create scorecard transforms for PerformancePoint Services in SharePoint
 Learn how to create custom scorecard transforms for PerformancePoint Services in SharePoint.
diff --git a/docs/general-development/how-to-create-sharepoint-workflows-using-visual-studio.md b/docs/general-development/how-to-create-sharepoint-workflows-using-visual-studio.md
index 1106d1ceb8..2ef67a3846 100644
--- a/docs/general-development/how-to-create-sharepoint-workflows-using-visual-studio.md
+++ b/docs/general-development/how-to-create-sharepoint-workflows-using-visual-studio.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create SharePoint Workflows using Visual Studio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 739af178-96b3-4630-bbc0-5def02065eeb
 ---
 
@@ -71,7 +72,7 @@ The stage construct within a SharePoint Designer 2013 based workflow is based on
   
     
     
-![Figure 1. Flowchart workflow](../../images/ngWfFig01.png)
+![Figure 1. Flowchart workflow](../images/ngWfFig01.png)
   
     
     
@@ -100,7 +101,7 @@ State machine workflows, like flowchart workflows, do not typically follow a spe
   
     
     
-![Figure 2. State machine workflow](../../images/ngWfFig02.png)
+![Figure 2. State machine workflow](../images/ngWfFig02.png)
   
     
     
@@ -142,7 +143,7 @@ Before building a custom workflow, developers should have a good understanding o
   
     
     
-![Figure 3. Workflow authoring interface](../../images/ngWfFig03.png)
+![Figure 3. Workflow authoring interface](../images/ngWfFig03.png)
   
     
     
@@ -217,7 +218,7 @@ To create a custom workflow using Visual Studio 2012 or later, ensure that you h
 
   
 
-  ![Figure 4. Default designer surface](../../images/ngWfFig04.png)
+  ![Figure 4. Default designer surface](../images/ngWfFig04.png)
   
 
   
@@ -244,7 +245,7 @@ This workflow sample will illustrate this practice of segmenting your workflows.
   
     
     
-![Figure 5. Adding child sequences](../../images/ngWfFig05.png)
+![Figure 5. Adding child sequences](../images/ngWfFig05.png)
   
     
     
@@ -277,7 +278,7 @@ You can comment a given workflow activity by selecting the activity, the selecti
   
     
     
-![Figure 6. Annotation on an activity](../../images/ngWfFig06.png)
+![Figure 6. Annotation on an activity](../images/ngWfFig06.png)
   
     
     
@@ -336,7 +337,7 @@ The point, of course, is to get some values from the list item that triggered th
 
   
 
-  ![Figure 7. Extracting values from list items](../../images/ngWfFig07.png)
+  ![Figure 7. Extracting values from list items](../images/ngWfFig07.png)
   
 
   
@@ -376,7 +377,7 @@ To get user information, do the following:
 
   
 
-  ![Figure 8. Changing variable scope](../../images/ngWfFig08.png)
+  ![Figure 8. Changing variable scope](../images/ngWfFig08.png)
   
 
   
@@ -394,7 +395,7 @@ To get user information, do the following:
 
   
 
-  ![Figure 9. Updating LookupSPUser output](../../images/ngWfFig09.png)
+  ![Figure 9. Updating LookupSPUser output](../images/ngWfFig09.png)
   
 
   
@@ -406,7 +407,7 @@ To get user information, do the following:
 
   
 
-  ![Figure 10. Retrieving values from LookupSPUser](../../images/ngWfFig10.png)
+  ![Figure 10. Retrieving values from LookupSPUser](../images/ngWfFig10.png)
   
 
   
@@ -429,7 +430,7 @@ Finally, let's test the workflow. Start by adding two **WriteLine** activities.
   
     
     
-![Figure 11. Testing the workflow](../../images/ngWfFig11.png)
+![Figure 11. Testing the workflow](../images/ngWfFig11.png)
   
     
     
@@ -454,13 +455,13 @@ This article first explained the different types of workflows that can be create
 <a name="bk_addresources"> </a>
 
 
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
--  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices)
+-  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices.md)
     
   
--  [SharePoint workflow samples](sharepoint-workflow-samples)
+-  [SharePoint workflow samples](sharepoint-workflow-samples.md)
     
   
 
diff --git a/docs/general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md b/docs/general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md
index 70f1429d53..fe629bb738 100644
--- a/docs/general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md
+++ b/docs/general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md
@@ -1,6 +1,7 @@
 ---
 title: How to Create tabular data source editors for PerformancePoint Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3136420a-f8a2-4677-8b69-1d5d9705d96f
 ---
 
@@ -14,7 +15,7 @@ In PerformancePoint Services, custom data source editors enable users to set pro
   
     
     
-The following procedures and code examples are based on the **SampleDataSourceEditor** class from the [custom objects sample](http://msdn.microsoft.com/library/af021d52-7562-4e7a-9de4-e1fc5784a59d%28Office.15%29.aspx). The editor is a thin web application that enables users to modify the name and description of the data source, enter stock symbols, and to specify a proxy server address and cache file location. For the complete code for the class, see  [Code example: Retrieve and update custom tabular data sources](#BKMK_ExampleCode).
+The following procedures and code examples are based on the **SampleDataSourceEditor** class from the [custom objects sample](http://msdn.microsoft.com/library/af021d52-7562-4e7a-9de4-e1fc5784a59d%28Office.15%29.aspx). The editor is a thin web application that enables users to modify the name and description of the data source, enter stock symbols, and to specify a proxy server address and cache file location. For the complete code for the class, see  [Code example: Retrieve and update custom tabular data sources](#bk_example).
   
     
     
@@ -115,7 +116,7 @@ DataSourceRepositoryHelper = new DataSourceRepositoryHelper();
   - To create the custom data source, use the **DataSource()** constructor and then define the data source's [Name](https://msdn.microsoft.com/library/Microsoft.PerformancePoint.Scorecards.Element.Name.aspx) and [SubTypeId](https://msdn.microsoft.com/library/Microsoft.PerformancePoint.Scorecards.DataSource.SubTypeId.aspx) properties. [SubTypeId](https://msdn.microsoft.com/library/Microsoft.PerformancePoint.Scorecards.DataSource.SubTypeId.aspx) is the unique identifier for the data source, and it must match the **subType** attribute that you specify for your custom data source in the PerformancePoint Services web.config file.
     
     > **Note:**
-      > The sample data source editor does not include logic to create a data source object. For examples of creating a custom object, see  [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint) or [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint). 
+      > The sample data source editor does not include logic to create a data source object. For examples of creating a custom object, see  [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md) or [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md). 
 
 ```cs
   if (ClickOnceLaunchValues.OpenItem.Equals(action, StringComparison.OrdinalIgnoreCase))
@@ -157,7 +158,7 @@ The following code example retrieves and updates custom tabular data sources. Th
   
     
     
-Before you can compile this code example, you must configure your development environment as described in  [Create and configure the editor class for a tabular data source editor in PerformancePoint Services](#BKMK_DefineDSEd).
+Before you can compile this code example, you must configure your development environment as described in  [Create and configure the editor class for a tabular data source editor in PerformancePoint Services](#BKMK_ConfigDSEditor).
   
     
     
@@ -435,13 +436,13 @@ After you create a data source editor (including its user interface, if required
     
 
 ## Additional resources
-<a name="bk_next"> </a>
+<a name="bk_resources"> </a>
 
 
--  [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha)
+-  [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md)
     
   
--  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint)
+-  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md b/docs/general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md
index f06bb9c258..45686b170a 100644
--- a/docs/general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md
+++ b/docs/general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Create tabular data source providers for PerformancePoint Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8d734ed6-7636-40c5-a99b-bc038362cffe
 ---
 
@@ -421,10 +422,10 @@ After you create a data source provider and a data source editor (including its
 <a name="bk_addResources"> </a>
 
 
--  [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share)
+-  [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md)
     
   
--  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint)
+-  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-customize-a-field-type-using-client-side-rendering.md b/docs/general-development/how-to-customize-a-field-type-using-client-side-rendering.md
index 04c42b9101..a6a1b81b2c 100644
--- a/docs/general-development/how-to-customize-a-field-type-using-client-side-rendering.md
+++ b/docs/general-development/how-to-customize-a-field-type-using-client-side-rendering.md
@@ -1,6 +1,7 @@
 ---
 title: How to Customize a field type using client-side rendering
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 18e32537-d7ed-4fe7-90cf-b6cfab3f85a3
 ---
 
@@ -31,7 +32,7 @@ To follow the steps in this example, you need the following:
 - A SharePoint development environment
     
   
-For information about setting up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about setting up your SharePoint development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -48,7 +49,7 @@ The following table lists useful articles that can help you understand the conce
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint) <br/> |Learn about developing, packaging, and deploying administrative extensions to SharePoint using farm solutions.  <br/> |
+| [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint.md) <br/> |Learn about developing, packaging, and deploying administrative extensions to SharePoint using farm solutions.  <br/> |
 | [Custom Field Types](http://msdn.microsoft.com/en-us/library/ms446361.aspx) <br/> |Learn about creating custom field types. As you store your business information in SharePoint, there may be times when your data does not conform to the field types that are available in SharePoint FoundationOr, you might just want to customize those field types. Custom fields can include custom data validation and custom field rendering.  <br/> |
    
 
@@ -86,7 +87,7 @@ Figure 1 shows a view form with a custom-rendered field type.
   
     
     
-  ![Custom client-side rendered field in a View form](../../images/CSRFieldType_result.png)
+  ![Custom client-side rendered field in a View form](../images/CSRFieldType_result.png)
   
     
     
@@ -106,7 +107,7 @@ Figure 1 shows a view form with a custom-rendered field type.
 
   
 
-  ![SharePoint Project Visual Studio template](../../images/SharePointSolutionVSTemplate.png)
+  ![SharePoint Project Visual Studio template](../images/SharePointSolutionVSTemplate.png)
   
 
   
@@ -312,7 +313,7 @@ function favoriteColorViewTemplate(ctx) {
 
   
 
-  ![Creating a new custom field type column](../../images/CSRFieldType_addcolumn.png)
+  ![Creating a new custom field type column](../images/CSRFieldType_addcolumn.png)
   
 
   
@@ -347,18 +348,18 @@ This article demonstrated how to customize the rendering process for a custom fi
 <a name="SP15CustomizeafieldtypeusingCSR_AddResources"> </a>
 
 
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [What's new for developers in SharePoint](what???s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint)
+-  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint.md)
     
   
diff --git a/docs/general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md b/docs/general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md
index 5e6af891c2..6dc3f282c0 100644
--- a/docs/general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md
+++ b/docs/general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md
@@ -1,6 +1,7 @@
 ---
 title: How to Customize list item queries and filter data for Windows Phone apps
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 32f89b97-8274-4cb0-9164-7898735a18aa
 ---
 
@@ -14,7 +15,7 @@ With projects created from the Windows Phone SharePoint List Application templat
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -125,7 +126,7 @@ In your own projects, you can take advantage of the way the data layer is design
   
     
     
-For the following code sample, assume again that the target installation of SharePoint Server has a Product Orders list created from the Custom List template, configured with the fields and types indicated in Table 1 in the topic  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s). Create a project based on the Windows Phone SharePoint List Application template that uses a list like the Product Orders list as a source (as described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app)). For the purposes of this example, we add a custom view to the Windows Phone app (not to the list on the server) that is filtered to display only those product orders in which the quantity ordered is 100 or more.
+For the following code sample, assume again that the target installation of SharePoint Server has a Product Orders list created from the Custom List template, configured with the fields and types indicated in Table 1 in the topic  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md). Create a project based on the Windows Phone SharePoint List Application template that uses a list like the Product Orders list as a source (as described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md)). For the purposes of this example, we add a custom view to the Windows Phone app (not to the list on the server.md) that is filtered to display only those product orders in which the quantity ordered is 100 or more.
   
     
     
@@ -221,7 +222,7 @@ When you start your project (by pressing F5), the **Pivot** control for the app
   
     
     
-![All orders (list items) in a sample list](../../images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif)
+![All orders (list items) in a sample list](../images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif)
   
     
     
@@ -239,7 +240,7 @@ And the custom view, as defined in the preceding procedure, displays a filtered
   
     
     
-![Only the big orders](../../images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif)
+![Only the big orders](../images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif)
   
     
     
@@ -252,13 +253,13 @@ You can make many other customizations both to the CAML queries on which views a
 <a name="SP15Custlistitem_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Introduction to Collaborative Application Markup Language (CAML)](http://msdn.microsoft.com/en-us/library/ms426449.aspx)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md b/docs/general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md
index fb9bc29c46..67bbea3b65 100644
--- a/docs/general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md
+++ b/docs/general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Customize page layouts for a catalog-based site in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 21d8db99-73b3-4429-b6cb-04e375af9f55
 ---
 
@@ -39,15 +40,15 @@ Table 1 lists useful articles that can help you understand the concepts and step
 |**Article title**|**Description**|
 |:-----|:-----|
 | [Overview of cross-site publishing in SharePoint](http://technet.microsoft.com/en-us/library/jj635883.aspx) <br/> |Learn about how to use cross-site publishing and Search Web Parts to create adaptive SharePoint Internet, intranet, and extranet sites.  <br/> |
-| [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) <br/> |Learn about how to create page layouts in SharePoint.  <br/> |
-| [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint) <br/> |Learn about how to resolve any issues that prevent the server-side preview from rendering your page.  <br/> |
-| [SharePoint Design Manager snippets](sharepoint-design-manager-snippets) <br/> |Learn about how to use snippets to add SharePoint functionality to your HTML master page or page layout.  <br/> |
+| [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) <br/> |Learn about how to create page layouts in SharePoint.  <br/> |
+| [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md) <br/> |Learn about how to resolve any issues that prevent the server-side preview from rendering your page.  <br/> |
+| [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md) <br/> |Learn about how to use snippets to add SharePoint functionality to your HTML master page or page layout.  <br/> |
    
 
 ## Introduction to category page layouts and catalog item page layouts
 <a name="bk_introduction"> </a>
 
-Category pages and catalog item pages are page layouts that you can use to show structured catalog content consistently across a site. By default, SharePoint can automatically create one category page layout and one catalog item page layout per catalog connection. Pages based on these layouts are created in the Pages library of a publishing site when you connect the site to a catalog. For more information about page layouts, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint). For more information about features that are specific to category page layouts and catalog item page layouts, see  [Overview of cross-site publishing in SharePoint](http://technet.microsoft.com/en-us/library/jj635883.aspx).
+Category pages and catalog item pages are page layouts that you can use to show structured catalog content consistently across a site. By default, SharePoint can automatically create one category page layout and one catalog item page layout per catalog connection. Pages based on these layouts are created in the Pages library of a publishing site when you connect the site to a catalog. For more information about page layouts, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md). For more information about features that are specific to category page layouts and catalog item page layouts, see  [Overview of cross-site publishing in SharePoint](http://technet.microsoft.com/en-us/library/jj635883.aspx).
   
     
     
@@ -59,7 +60,7 @@ By default, category page layouts and catalog item page layouts are created auto
 ## Create a category page layout
 <a name="bk_createCategoryPage"> </a>
 
-Before you can create or customize a category page layout, we recommend that you create a mapped network drive that points to the **Master Page Gallery**. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+Before you can create or customize a category page layout, we recommend that you create a mapped network drive that points to the **Master Page Gallery**. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
   
     
     
@@ -81,20 +82,20 @@ The simplest way to create a category page layout is to let SharePoint create th
     
     > **Important:**
       > You must keep the Content Search Snippet markup so that the category page can display search results. 
-4. To configure and copy the HTML for any snippets you want to add to the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+4. To configure and copy the HTML for any snippets you want to add to the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 5. Make any other required changes to the markup, and then save the file.
     
   
-6. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) to check the status of the file, preview the page layout, and fix any errors.
+6. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) to check the status of the file, preview the page layout, and fix any errors.
     
   
 
 ### To create a category page layout by using Design Manager
 
 
-1. Follow step 1 through step 6 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+1. Follow step 1 through step 6 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
     
   
 2. In step 7, choose the **Article Page** content type.
@@ -142,14 +143,14 @@ The simplest way to create a category page layout is to let SharePoint create th
 8. Replace the markup inside the content placeholder that has **id="PlaceHolderMain"** with the markup that you want to use in the page layout.
     
   
-9. To configure and copy the HTML for the Content Search Snippet and any other snippets you want to add to the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+9. To configure and copy the HTML for the Content Search Snippet and any other snippets you want to add to the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
     > **Note:**
       > When you add the Content Search Snippet to the page layout, be sure to change the query to use the result source that was created when you connected the publishing site to a catalog. For more information, see  [Configure result sources for web content management in SharePoint](http://technet.microsoft.com/en-us/library/jj715262.aspx). 
 10. Make any other required changes to the markup, and then save the file.
     
   
-11. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) to check the status of the file, preview the page layout, and fix any errors.
+11. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) to check the status of the file, preview the page layout, and fix any errors.
     
   
 
@@ -233,7 +234,7 @@ WebPart="true" Height="" Width="" Title="$Resources:cms,WebPartZoneTitle_Dynamic
 ## Create a catalog item page layout
 <a name="bk_createCatItemPage"> </a>
 
-Before you can create or customize a catalog item page layout, we recommend that you create a mapped network drive that points to the Master Page Gallery. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+Before you can create or customize a catalog item page layout, we recommend that you create a mapped network drive that points to the Master Page Gallery. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
   
     
     
@@ -257,21 +258,21 @@ As with the category page layout, the simplest way to create a catalog item page
 4. Delete any snippets that you do not want to use in the page layout, and move the remaining snippets to places in the markup where you want the property values to appear.
     
     > **Caution:**
-      > By default, a Web Part Zone Snippet that contains a Catalog-Item Reuse Snippet is added to the page layout. This snippet contains the data provider that returns query results that are used by all other snippets on the page. We recommend that you keep the Catalog-Item Reuse Snippet in this default Web Part Zone Snippet. (You can move the Catalog-Item Reuse Snippet outside the Web Part Zone, and you can change the property that it displays. But, you must keep the Catalog-Item Reuse Snippet in the page layout.) For more information, see  [Page fields](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint#bk_pagefields), later in this article. 
-5. To configure and copy the HTML snippet for any snippets you want to use in the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+      > By default, a Web Part Zone Snippet that contains a Catalog-Item Reuse Snippet is added to the page layout. This snippet contains the data provider that returns query results that are used by all other snippets on the page. We recommend that you keep the Catalog-Item Reuse Snippet in this default Web Part Zone Snippet. (You can move the Catalog-Item Reuse Snippet outside the Web Part Zone, and you can change the property that it displays. But, you must keep the Catalog-Item Reuse Snippet in the page layout.) For more information, see  [Page fields](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md#bk_pagefields), later in this article. 
+5. To configure and copy the HTML snippet for any snippets you want to use in the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 6. Make any other required changes to the markup, and then save the file.
     
   
-7. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) to check the status of the file, preview the page layout, and fix any errors.
+7. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) to check the status of the file, preview the page layout, and fix any errors.
     
   
 
 ### To create a catalog item page layout by using Design Manager
 
 
-1. Follow step 1 through step 6 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+1. Follow step 1 through step 6 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
     
   
 2. In step 7, choose **Remote Catalog**, and then choose the catalog that contains the data to appear on the page.
@@ -301,14 +302,14 @@ As with the category page layout, the simplest way to create a catalog item page
 7. Delete any snippets that you do not want to use in the page layout, and move the remaining snippets to places in the markup where you want the property values to appear.
     
     > **Caution:**
-      > By default, a Web Part Zone Snippet that contains a Catalog-Item Reuse Snippet is added to the page layout. This snippet contains the data provider that returns query results that are used by all other snippets on the page. We recommend that you keep the Catalog-Item Reuse Snippet in this default Web Part Zone Snippet. (You can move the Catalog-Item Reuse Snippet outside the Web Part Zone, and you can change the property that it displays. But, you must keep the Catalog-Item Reuse Snippet in the page layout.) For more information, see  [Page fields](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint#bk_pagefields), later in this article. 
-8. To configure and copy the HTML snippet for any snippets you want to use in the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+      > By default, a Web Part Zone Snippet that contains a Catalog-Item Reuse Snippet is added to the page layout. This snippet contains the data provider that returns query results that are used by all other snippets on the page. We recommend that you keep the Catalog-Item Reuse Snippet in this default Web Part Zone Snippet. (You can move the Catalog-Item Reuse Snippet outside the Web Part Zone, and you can change the property that it displays. But, you must keep the Catalog-Item Reuse Snippet in the page layout.) For more information, see  [Page fields](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md#bk_pagefields), later in this article. 
+8. To configure and copy the HTML snippet for any snippets you want to use in the page, follow step 1 through step 11 in the "Insert a snippet from the Snippet Gallery" section of  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 9. Make any other required changes to the markup, and then save the file.
     
   
-10. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) to check the status of the file, preview the page layout, and fix any errors.
+10. Follow step 9 through step 11 in the "Create a page layout" section of  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) to check the status of the file, preview the page layout, and fix any errors.
     
   
 
@@ -601,19 +602,19 @@ __WebPartId="{22e39e9d-1b25-42c7-bf2a-7ebca37616d4}">-->
 <a name="bk_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates)
+-  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates.md)
     
   
 
diff --git a/docs/general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md b/docs/general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md
index 3368dadc3c..76a089597d 100644
--- a/docs/general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md
+++ b/docs/general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md
@@ -1,6 +1,7 @@
 ---
 title: How to Customize the user interface of a SharePoint list app for Windows Phone
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 09ed59af-5e2b-4716-a9e4-a015e4793d85
 ---
 
@@ -14,7 +15,7 @@ SharePoint list apps created from the Windows Phone SharePoint List Application
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -23,7 +24,7 @@ SharePoint list apps created from the Windows Phone SharePoint List Application
 ## Create a SharePoint list app for user interface customizations
 <a name="BKMK_CreatingSPListApp"> </a>
 
-For the following procedures, assume a server running SharePoint Server has a Product Orders list created from the Custom List template, similar to the sample Product Orders list used in  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s). For the sample Windows Phone app used in this topic, the Product Orders list on which the app is based has been modified to include additional fields. The modified Product Orders list used for the purposes of the examples in this topic has been created with the columns and field types shown in Table 1.
+For the following procedures, assume a server running SharePoint Server has a Product Orders list created from the Custom List template, similar to the sample Product Orders list used in  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md). For the sample Windows Phone app used in this topic, the Product Orders list on which the app is based has been modified to include additional fields. The modified Product Orders list used for the purposes of the examples in this topic has been created with the columns and field types shown in Table 1.
   
     
     
@@ -42,7 +43,7 @@ For the following procedures, assume a server running SharePoint Server has a Pr
 |Rush  <br/> |Boolean  <br/> |No  <br/> |
 |Contact Number  <br/> |Single line of text (Text)  <br/> |No  <br/> |
    
-Follow the procedures in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app) to use the Windows Phone SharePoint List Application template to generate a SharePoint list app as a starting point for the following UI customizations. Specify as the target SharePoint list for the app a list that has a schema similar to what is represented in Table 1.
+Follow the procedures in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md) to use the Windows Phone SharePoint List Application template to generate a SharePoint list app as a starting point for the following UI customizations. Specify as the target SharePoint list for the app a list that has a schema similar to what is represented in Table 1.
   
     
     
@@ -191,7 +192,7 @@ If you start the project (by pressing F5) to deploy it to the Windows Phone Emul
   
     
     
-![Edit form with DatePicker control](../../images/787df903-833d-4a12-a692-716ceaf54c10.gif)
+![Edit form with DatePicker control](../images/787df903-833d-4a12-a692-716ceaf54c10.gif)
   
     
     
@@ -209,7 +210,7 @@ The **DatePicker** control (highlighted for the **Order Date** field in Figure 1
   
     
     
-![Date chooser page](../../images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif)
+![Date chooser page](../images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif)
   
     
     
@@ -244,7 +245,7 @@ In the following procedures, you will:
   
 
 > **Note:**
-> For more information about field value converters, see  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps). 
+> For more information about field value converters, see  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md). 
   
     
     
@@ -509,10 +510,10 @@ For items in the Product Orders list that are already associated with a custom P
 <a name="BKMK_AddingControlsForChoiceFields"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-deploy-a-claims-provider-in-sharepoint.md b/docs/general-development/how-to-deploy-a-claims-provider-in-sharepoint.md
index da4fdea160..bdff09df7d 100644
--- a/docs/general-development/how-to-deploy-a-claims-provider-in-sharepoint.md
+++ b/docs/general-development/how-to-deploy-a-claims-provider-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Deploy a claims provider in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3a5fcedc-aa9a-4ff4-95c0-0e0a7dea9d1f
 ---
 
@@ -157,16 +158,16 @@ namespace MySample.Sample.Server.SampleClaimsProvider
 <a name="SP15_HowToDeployClaimsProvider_AdditionalResources"> </a>
 
 
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint)
+-  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md)
     
   
--  [Claims provider in SharePoint](claims-provider-in-sharepoint)
+-  [Claims provider in SharePoint](claims-provider-in-sharepoint.md)
     
   
--  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint)
+-  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-deploy-a-custom-theme-in-sharepoint.md b/docs/general-development/how-to-deploy-a-custom-theme-in-sharepoint.md
index 4d7c344686..c9d55b3c2a 100644
--- a/docs/general-development/how-to-deploy-a-custom-theme-in-sharepoint.md
+++ b/docs/general-development/how-to-deploy-a-custom-theme-in-sharepoint.md
@@ -1,13 +1,14 @@
 ---
 title: How to Deploy a custom theme in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f703df24-8e56-4e6a-bc37-95acbb3c83e8
 ---
 
 
 # How to: Deploy a custom theme in SharePoint
 Learn how to deploy a custom theme to a SharePoint site by using the user interface or by implementing a feature receiver.
-SharePoint includes preinstalled themes. You can create custom themes by creating additional color palettes, font schemes, and master pages. After the files are uploaded to the Theme Gallery and the Master Page Gallery, you can deploy a theme to a site by using the user interface or by using code. For more information about color palettes and font schemes, see  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+SharePoint includes preinstalled themes. You can create custom themes by creating additional color palettes, font schemes, and master pages. After the files are uploaded to the Theme Gallery and the Master Page Gallery, you can deploy a theme to a site by using the user interface or by using code. For more information about color palettes and font schemes, see  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -26,7 +27,7 @@ Table 1 lists articles that can help you understand the core concepts of deployi
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Themes overview for SharePoint](themes-overview-for-sharepoint) <br/> |Learn about the theming experience in SharePoint.  <br/> |
+| [Themes overview for SharePoint](themes-overview-for-sharepoint.md) <br/> |Learn about the theming experience in SharePoint.  <br/> |
 | [Feature Events](http://msdn.microsoft.com/en-us/library/ms469501.aspx) <br/> |Learn about feature events, which enable you to trap and respond to an event that occurs when a feature is installed in the server farm.  <br/> |
    
 
@@ -228,13 +229,13 @@ currentItem.Update();
 <a name="bk_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint)
+-  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md)
     
   
--  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+-  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
diff --git a/docs/general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions.md b/docs/general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions.md
index 376c63360a..89cae6c3ee 100644
--- a/docs/general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions.md
+++ b/docs/general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions.md
@@ -1,9 +1,10 @@
 ---
 title: How to Deploy UDFs Using SharePoint Foundation Solutions
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,udf list,WSS Solutions
 f1_keywords:
 - how to,howdoi,howto,udf list,WSS Solutions
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 97751a6c-ef73-4d95-a3c4-98014d84ba48
 ---
 
@@ -42,7 +43,7 @@ The procedure for creating and deploying a UDF assembly by using SharePoint Foun
   
 Each Excel Services trusted location has an **AllowUdfs** flag.
 > **Note:**
-> The **AllowUdfs** flag is denoted by the **User-defined functions allowed** option on the Excel Services Trusted File Locations page. To learn how to navigate to the Trusted File Locations page, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs). 
+> The **AllowUdfs** flag is denoted by the **User-defined functions allowed** option on the Excel Services Trusted File Locations page. To learn how to navigate to the Trusted File Locations page, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md). 
   
     
     
@@ -54,9 +55,9 @@ In order to allow UDFs to be called from a specific trusted location, you must:
 - Add the UDF assembly to the trusted UDF list to allow the UDF to be called from a workbook.
     
   
-For more information on how to enable UDFs and add UDFs to the trusted UDF list, see  [How to: Enable UDFs](how-to-enable-udfs).
+For more information on how to enable UDFs and add UDFs to the trusted UDF list, see  [How to: Enable UDFs](how-to-enable-udfs.md).
 > **Note:**
-> To avoid name collision, give your UDF assemblies and their dependencies strong names, and name them as uniquely as possible. For more information, see  [Excel Services Best Practices](excel-services-best-practices) and [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips). 
+> To avoid name collision, give your UDF assemblies and their dependencies strong names, and name them as uniquely as possible. For more information, see  [Excel Services Best Practices](excel-services-best-practices.md) and [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md). 
   
     
     
@@ -159,27 +160,27 @@ For more information on how to enable UDFs and add UDFs to the trusted UDF list,
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
   
     
     
- [How to: Restrict UDF Code Access Security Permissions](how-to-restrict-udf-code-access-security-permissions)
+ [How to: Restrict UDF Code Access Security Permissions](how-to-restrict-udf-code-access-security-permissions.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/how-to-detect-the-installed-sku-of-sharepoint.md b/docs/general-development/how-to-detect-the-installed-sku-of-sharepoint.md
index 95b5e1b987..9c1b523818 100644
--- a/docs/general-development/how-to-detect-the-installed-sku-of-sharepoint.md
+++ b/docs/general-development/how-to-detect-the-installed-sku-of-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Detect the installed SKU of SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d5d84d6f-6a8e-4ead-9296-7025baf1e154
 ---
 
@@ -100,10 +101,10 @@ namespace GetInstalledSharePointSku
 <a name="bk_SP15DetectSKUaddresources"> </a>
 
 
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
--  [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
 -  [SharePoint Developer Blog](http://blogs.msdn.com/b/sharepointdev/)
diff --git a/docs/general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md b/docs/general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md
index e020407b00..8dcf780f49 100644
--- a/docs/general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md
+++ b/docs/general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md
@@ -1,6 +1,7 @@
 ---
 title: How to Embed images, videos, and documents in posts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 9927b9e7-daea-4261-80fa-4cc25f489e22
 ---
 
@@ -14,7 +15,7 @@ In a social feed, the simplest form of post content contains only text, but you
 
 
 > **Note:**
-> To add a mention, tag, or link to a post's content, you add a  [SocialDataItem](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialDataItem.aspx) object to the [SocialPostCreationData.ContentItems](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.ContentItems.aspx) property. For more information, see [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep). 
+> To add a mention, tag, or link to a post's content, you add a  [SocialDataItem](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialDataItem.aspx) object to the [SocialPostCreationData.ContentItems](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.ContentItems.aspx) property. For more information, see [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md). 
   
     
     
@@ -47,7 +48,7 @@ To use the examples in this article, you'll need to upload an image, a video, an
   
     
     
-For instructions about how to set up your development environment and create a console application, see  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli).
+For instructions about how to set up your development environment and create a console application, see  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md).
   
     
     
@@ -146,7 +147,7 @@ The following code example publishes a post that contains an embedded video. It
 - Add the video attachment to the  [Attachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.Attachment.aspx) property of the [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) object that's used to create the post.
     
   
-This example requires the video features to be enabled on the server and the video file to be uploaded to an asset library. See the  [prerequisites for using the code examples](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server#bk_preReqs) for more information.
+This example requires the video features to be enabled on the server and the video file to be uploaded to an asset library. See the  [prerequisites for using the code examples](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md#bk_preReqs) for more information.
   
     
     
@@ -226,7 +227,7 @@ The following code example publishes a post that contains an embedded document.
 - Add the document attachment to the  [Attachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.Attachment.aspx) property of the [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) object that's used to create the post.
     
   
-To use this example in an on-premises environment, your environment must be configured to use Office Online. See the  [prerequisites for using the code examples](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server#bk_preReqs) for more information. Otherwise, you can post a link to the document as described in [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep).
+To use this example in an on-premises environment, your environment must be configured to use Office Online. See the  [prerequisites for using the code examples](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md#bk_preReqs) for more information. Otherwise, you can post a link to the document as described in [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md).
   
     
     
@@ -295,10 +296,10 @@ namespace EmbedDocumentInPost
 <a name="bk_addresources"> </a>
 
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
--  [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep)
+-  [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md)
     
   
 -  [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) and [SocialAttachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialAttachment.aspx) in the client object models
@@ -307,7 +308,7 @@ namespace EmbedDocumentInPost
 -  [SocialPostCreationData](http://msdn.microsoft.com/library/f0e1fa3e-6fc9-48e0-5570-92091abfef33%28Office.15%29.aspx) and [SocialAttachment](http://msdn.microsoft.com/library/dfdee790-a1b0-19c8-0e92-5a6e058ba4db%28Office.15%29.aspx) in the JavaScript object model
     
   
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
 -  [SPSocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialPostCreationData.aspx) and [SPSocialAttachment](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialAttachment.aspx) in the server object model
diff --git a/docs/general-development/how-to-enable-udfs.md b/docs/general-development/how-to-enable-udfs.md
index 71416a917f..4138fc7ddb 100644
--- a/docs/general-development/how-to-enable-udfs.md
+++ b/docs/general-development/how-to-enable-udfs.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Enable UDFs
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,UDF list
 f1_keywords:
 - how to,howdoi,howto,UDF list
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 8c1af2eb-bb22-45e1-82de-a2b4b53d7a26
 ---
 
@@ -84,7 +85,7 @@ To do the following steps, you need a computer that has Microsoft SharePoint Ser
 1. Open the Excel Services Add Trusted File Location page (if you are adding a new trusted location) or Excel Services Edit Trusted File Location page (if you are editing an existing trusted location). 
     
     > **Note:**
-      > For more information about trusting a location, see  [How to: Trust a Location](how-to-trust-a-location). 
+      > For more information about trusting a location, see  [How to: Trust a Location](how-to-trust-a-location.md). 
 2. Under **Allow User-Defined Functions**, select **User-defined functions allowed** to allow UDFs to be called from workbooks stored in this trusted location.
     
   
@@ -101,39 +102,39 @@ To do the following steps, you need a computer that has Microsoft SharePoint Ser
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
diff --git a/docs/general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md b/docs/general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md
index fd0ed5f5c1..ba324d1192 100644
--- a/docs/general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md
+++ b/docs/general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md
@@ -1,6 +1,7 @@
 ---
 title: How to Export the Name field in a Document Library list to a mobile app
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 901c2012-18c6-4dbd-a787-f8650a0cc7a8
 ---
 
@@ -27,7 +28,7 @@ So if you want to fetch a document, build the full URL of the document, and open
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -142,13 +143,13 @@ public string m_fileUrl;
 <a name="SP15StoreSPlist_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app)
+-  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=27570)
diff --git a/docs/general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering.md b/docs/general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering.md
index afa7626b6f..4a71996533 100644
--- a/docs/general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering.md
+++ b/docs/general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering.md
@@ -1,6 +1,7 @@
 ---
 title: How to Extend the Geolocation field type using client-side rendering
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7360633a-a7cf-4194-8bbd-8dd7c323e80b
 ---
 
@@ -8,13 +9,13 @@ ms.assetid: 7360633a-a7cf-4194-8bbd-8dd7c323e80b
 # How to: Extend the Geolocation field type using client-side rendering
 Learn how to customize the SharePoint Geolocation field type programmatically using client-side rendering.
 
-SharePoint introduces a new field type named Geolocation that enables you to annotate SharePoint lists with location information. In columns of type Geolocation, you can enter location information as a pair of latitude and longitude coordinates in decimal degrees, or retrieve the coordinates of the user's current location from the browser if it implements the W3C Geolocation API. For more information about the Geolocation field, see  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint). 
-The Geolocation field type is not available in the default content type of any list or document library in SharePoint. The Geolocation field type is included in SharePoint but isn't visible on the create column page for the list; you must add the Geolocation field type programmatically. For more information, see  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint). 
+SharePoint introduces a new field type named Geolocation that enables you to annotate SharePoint lists with location information. In columns of type Geolocation, you can enter location information as a pair of latitude and longitude coordinates in decimal degrees, or retrieve the coordinates of the user's current location from the browser if it implements the W3C Geolocation API. For more information about the Geolocation field, see  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md). 
+The Geolocation field type is not available in the default content type of any list or document library in SharePoint. The Geolocation field type is included in SharePoint but isn't visible on the create column page for the list; you must add the Geolocation field type programmatically. For more information, see  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md). 
   
     
     
 
-After you add the Geolocation field type to SharePoint, you can use it to render maps by using Bing Maps. The built-in Geolocation field can render only with Bing Maps. However, you can create a custom field by using the Geolocation field as a parent field type. Custom rendering can be provided through the **JSLink** property in the client-side rendering framework. The client-side rendering framework is introduced in SharePoint. For more information, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering). 
+After you add the Geolocation field type to SharePoint, you can use it to render maps by using Bing Maps. The built-in Geolocation field can render only with Bing Maps. However, you can create a custom field by using the Geolocation field as a parent field type. Custom rendering can be provided through the **JSLink** property in the client-side rendering framework. The client-side rendering framework is introduced in SharePoint. For more information, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md). 
 > **Note:**
 > The JSLink property is not supported on Survey or Events lists. A SharePoint calendar is an Events list. 
   
@@ -55,9 +56,9 @@ You must have the following:
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint) <br/> |Learn how to integrate location information and maps in SharePoint lists and location-based web and mobile apps by using the new Geolocation field, and by creating your own Geolocation-based field types.  <br/> |
-| [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering) <br/> |Learn more about the new client-side rendering introduced in SharePoint.  <br/> |
-| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint) <br/> |Learn how to add a Geolocation column to a list programmatically in SharePoint.  <br/> |
+| [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md) <br/> |Learn how to integrate location information and maps in SharePoint lists and location-based web and mobile apps by using the new Geolocation field, and by creating your own Geolocation-based field types.  <br/> |
+| [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md) <br/> |Learn more about the new client-side rendering introduced in SharePoint.  <br/> |
+| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md) <br/> |Learn how to add a Geolocation column to a list programmatically in SharePoint.  <br/> |
    
 
 ## Step 1: Set up the Visual Studio project
@@ -76,7 +77,7 @@ You must have the following:
 
   
 
-  ![SharePoint Project Visual Studio template](../../images/SharePointSolutionVSTemplate.png)
+  ![SharePoint Project Visual Studio template](../images/SharePointSolutionVSTemplate.png)
   
 
   
@@ -182,7 +183,7 @@ public class CustomGeolocationField : SPFieldGeolocation
         }
 ```
 
-4. Add the following override of the **JSLink** method to the class. CustomGeolocationControl.js is a JavaScript file that you create in the following step. By providing your own JavaScript file, you are overriding the default rendering of Bing Maps. If you do not override this method, the default rendering will be from Bing Maps. The **JSLink** property is introduced in SharePoint. For more information about the **JSLink** property, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering).
+4. Add the following override of the **JSLink** method to the class. CustomGeolocationControl.js is a JavaScript file that you create in the following step. By providing your own JavaScript file, you are overriding the default rendering of Bing Maps. If you do not override this method, the default rendering will be from Bing Maps. The **JSLink** property is introduced in SharePoint. For more information about the **JSLink** property, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md).
     
 ```cs
   
@@ -239,7 +240,7 @@ public override string JSLink
 ## Step 3: Create rendering for the new custom field
 <a name="CreatingCustomGeolocationStep_3"> </a>
 
-Next, you should create the JavaScript file that the **JSLink** method of the field class points to. This file should define the rendering of the custom field type using the new client-side rendering framework. For more information, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering).
+Next, you should create the JavaScript file that the **JSLink** method of the field class points to. This file should define the rendering of the custom field type using the new client-side rendering framework. For more information, see [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md).
   
     
     
@@ -525,7 +526,7 @@ After you deploy a custom field to the SharePoint server, a new custom column is
 
   
 
-  ![Creating a new custom Geolocation field type](../../images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png)
+  ![Creating a new custom Geolocation field type](../images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png)
   
 
   
@@ -536,13 +537,13 @@ After you deploy a custom field to the SharePoint server, a new custom column is
 <a name="SP15Createcustomgeo_addlresources"> </a>
 
 
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint)
+-  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md)
     
   
--  [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering)
+-  [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md)
     
   
 -  [SharePoint: Create a Geolocation field that renders maps using Nokia Maps](http://code.msdn.microsoft.com/SharePoint-Create-a-d9a91551)
diff --git a/docs/general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md b/docs/general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md
index 6d5fa23b57..2c07915319 100644
--- a/docs/general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md
+++ b/docs/general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md
@@ -1,6 +1,7 @@
 ---
 title: How to Follow documents and sites by using the .NET client object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 84366e01-4961-459d-8109-2f1d2d714353
 ---
 
@@ -33,7 +34,7 @@ The following objects are the primary APIs for Following Content tasks:
   
 
 > **Note:**
-> You also use these APIs for Following People tasks, but the **GetSuggestions** and **GetFollowers** methods available from [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) only support following people, not content. For more information about how you can use [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) , see [Follow content in SharePoint](follow-content-in-sharepoint) and [Follow people in SharePoint](follow-people-in-sharepoint). For code examples that show how to follow people, see  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint). 
+> You also use these APIs for Following People tasks, but the **GetSuggestions** and **GetFollowers** methods available from [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) only support following people, not content. For more information about how you can use [SocialFollowingManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFollowingManager.aspx) , see [Follow content in SharePoint](follow-content-in-sharepoint.md) and [Follow people in SharePoint](follow-people-in-sharepoint.md). For code examples that show how to follow people, see  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md). 
   
     
     
@@ -88,8 +89,8 @@ To create a console application that uses the .NET client object model to work w
     
 6. Replace the contents of the **Program** class with the code example from one of the following scenarios:
     
-  -  [Start and stop following content](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep#bkmk_FollowContent)  
-  -  [Get followed content for the current user](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep#bkmk_GetFollowed)
+  -  [Start and stop following content](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md#bkmk_FollowContent)  
+  -  [Get followed content for the current user](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md#bkmk_GetFollowed)
     
 7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**.
     
@@ -345,13 +346,13 @@ namespace FollowContentCSOM
 <a name="bkmk_AddtionalResources"> </a>
 
 
--  [Follow content in SharePoint](follow-content-in-sharepoint)
+-  [Follow content in SharePoint](follow-content-in-sharepoint.md)
     
   
--  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2)
+-  [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md)
     
   
--  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint)
+-  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md b/docs/general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md
index 876fdaa35d..29aa222ffa 100644
--- a/docs/general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md
+++ b/docs/general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md
@@ -1,6 +1,7 @@
 ---
 title: How to Follow documents, sites, and tags by using the REST service in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 989a5873-49f9-49e4-8d0f-439dde891cc2
 ---
 
@@ -53,7 +54,7 @@ To perform Following Content tasks by using the REST API, you send HTTP **GET**
   
 
 > **Note:**
-> You also use these endpoints for Following People tasks, but the **followers** and **suggestions** resources available from **SocialRestFollowingManager** only support following people, not content. For more information about how you can use **SocialRestFollowingManager**, see  [Follow content in SharePoint](follow-content-in-sharepoint) and [Follow people in SharePoint](follow-people-in-sharepoint). 
+> You also use these endpoints for Following People tasks, but the **followers** and **suggestions** resources available from **SocialRestFollowingManager** only support following people, not content. For more information about how you can use **SocialRestFollowingManager**, see  [Follow content in SharePoint](follow-content-in-sharepoint.md) and [Follow people in SharePoint](follow-people-in-sharepoint.md). 
   
     
     
@@ -139,10 +140,10 @@ If you're not using Napa on an Office 365 Developer Site, you'll need to meet th
   
 4. Expand the **Scripts** node, choose the App.js file and replace its contents with the code from one of the following scenarios:
     
-   -  [Start following and stop following a document](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bkmk_FollowDocs)
-   -  [Start following and stop following a site](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bkmk_FollowSites)
-   -  [Start following and stop following a tag](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bkmk_FollowTags)
-   -  [Get followed content](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bkmk_GetFollowed)
+   -  [Start following and stop following a document](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bkmk_FollowDocs)
+   -  [Start following and stop following a site](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bkmk_FollowSites)
+   -  [Start following and stop following a tag](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bkmk_FollowTags)
+   -  [Get followed content](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bkmk_GetFollowed)
   
 5. To run the app, choose the **Run Project** button at the bottom of the page.
     
@@ -171,7 +172,7 @@ The following code example represents the contents of the App.js file and shows
 - Build and send a **POST** request to the `stopfollowing` endpoint to stop following the document.
     
   
-- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) See [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bk_exampleResponses).
+- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) See [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bk_exampleResponses).
     
   
 Before you run the code, you'll need to upload a document and change the placeholder value for the **documentUrl** variable to the document's URL.
@@ -333,7 +334,7 @@ The following code example represents the contents of the App.js file and shows
 - Build and send a **POST** request to the `stopfollowing` endpoint to stop following the site.
     
   
-- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) See [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bk_exampleResponses).
+- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) See [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bk_exampleResponses).
     
   
 Before you run the code, change the placeholder value for the **siteUrl** variable to match the site that you want to follow. Use the format **http://server/siteCollection/site** for a site in a site collection. You can follow a site from any page or library in that site. If the site uses a template that doesn't support following (like the My Site host or a personal site), you'll get an **UnsupportedSite** error (error code 10).
@@ -495,10 +496,10 @@ The following code example represents the contents of the App.js file and shows
 - Build and send a **POST** request to the `stopfollowing` endpoint to stop following the tag.
     
   
-- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) For more information, see [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bk_exampleResponses).
+- Read the JSON response returned by the  `isfollowed` request and the `follow` request. (The `stopfollowing` request doesn't return anything in the response.) For more information, see [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bk_exampleResponses).
     
   
-Before you run the code, change the placeholder value for the **tagGuid** variable to the GUID of an existing tag. The taxonomy API that you use to retrieve a tag from the **HashTagsTermSet** doesn't have a REST interface, so you have to use the .NET client object model or the JavaScript object model. See [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint#bk_getTagGuid) for an example.
+Before you run the code, change the placeholder value for the **tagGuid** variable to the GUID of an existing tag. The taxonomy API that you use to retrieve a tag from the **HashTagsTermSet** doesn't have a REST interface, so you have to use the .NET client object model or the JavaScript object model. See [How to get a tag's GUID based on the tag's name by using the JavaScript object model](follow-content-in-sharepoint.md#bk_getTagGuid) for an example.
   
     
     
@@ -654,7 +655,7 @@ The following code example represents the contents of the App.js file and shows
 - Build and send a **GET** request to the `my/followed` endpoint to get the content that the current user is following.
     
   
-- Read the JSON response returned by the requests. See  [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2#bk_exampleResponses).
+- Read the JSON response returned by the requests. See  [Example JSON responses](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md#bk_exampleResponses).
     
   
 
@@ -906,13 +907,13 @@ The following response represents a count of three followed documents, sites, an
 <a name="bkmk_AddtionalResources"> </a>
 
 
--  [Follow content in SharePoint](follow-content-in-sharepoint)
+-  [Follow content in SharePoint](follow-content-in-sharepoint.md)
     
   
--  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)
+-  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)
     
   
--  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep)
+-  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md)
     
   
 
diff --git a/docs/general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md b/docs/general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md
index 42dbe64f12..d0cfa5f275 100644
--- a/docs/general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md
+++ b/docs/general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Follow people by using the JavaScript object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2643c286-47c9-4a7a-9273-7474394477d6
 ---
 
@@ -95,8 +96,8 @@ To create the farm solution that uses the JavaScript object model to work with F
 
 10. Replace the comment between the **script** tags with the code example from one of the following scenarios:
     
-  -  [Start or stop following people](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint#bk_FollowPeople)  
-  -  [Get followers and followed people](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint#bk_GetFollowers)
+  -  [Start or stop following people](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md#bk_FollowPeople)  
+  -  [Get followers and followed people](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md#bk_GetFollowers)
     
 11. To test the solution, on the menu bar, choose **Debug**, **Start Debugging**.
     
@@ -124,7 +125,7 @@ The following code example makes the current user start following or stop follow
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added in the [Create a farm solution and application page](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint#bk_CreateSolution) procedure. Then, change the placeholder value for the **targetUser** variable before you run the code.
+> Paste the following code between the **script** tags that you added in the [Create a farm solution and application page](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md#bk_CreateSolution) procedure. Then, change the placeholder value for the **targetUser** variable before you run the code.
   
     
     
@@ -220,7 +221,7 @@ The following code example gets the people who the current user is following and
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added in the [Create a farm solution and application page](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint#bk_CreateSolution) procedure.
+> Paste the following code between the **script** tags that you added in the [Create a farm solution and application page](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md#bk_CreateSolution) procedure.
   
     
     
@@ -293,10 +294,10 @@ function requestFailed(sender, args) {
 <a name="bk_AdditionalResources"> </a>
 
 
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
--  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint)
+-  [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md b/docs/general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md
index ac02ccb50c..c202ced597 100644
--- a/docs/general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md
+++ b/docs/general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Follow people by using the .NET client object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0fdb7ca5-d408-4256-b52b-886c4bc3b5b8
 ---
 
@@ -70,8 +71,8 @@ To create a console application that uses the .NET client object model to work w
   
 6. Replace the contents of the **Program** class with the code example from one of the following scenarios:
     
-  -  [Start and stop following people](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint#bkmk_FollowPeople)  
-  -  [Get followers and followed people](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint#bkmk_GetFollowednFollowers)
+  -  [Start and stop following people](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md#bkmk_FollowPeople)  
+  -  [Get followers and followed people](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md#bkmk_GetFollowednFollowers)
     
   
 7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**.
@@ -303,13 +304,13 @@ namespace FollowPeopleCSOM
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
--  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint)
+-  [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md)
     
   
--  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep)
+-  [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md)
     
   
 
diff --git a/docs/general-development/how-to-get-an-entire-workbook-or-a-snapshot.md b/docs/general-development/how-to-get-an-entire-workbook-or-a-snapshot.md
index 40005eee56..acc47c8801 100644
--- a/docs/general-development/how-to-get-an-entire-workbook-or-a-snapshot.md
+++ b/docs/general-development/how-to-get-an-entire-workbook-or-a-snapshot.md
@@ -1,9 +1,10 @@
 ---
 title: How to Get an Entire Workbook or a Snapshot
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto
 f1_keywords:
 - how to,howdoi,howto
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 39115503-8352-4589-87f4-cfa9c07260b6
 ---
 
@@ -243,34 +244,34 @@ Make sure you add a Web reference to an Excel Web Services site you have access
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-get-values-from-ranges.md b/docs/general-development/how-to-get-values-from-ranges.md
index bd30ac79e0..f621f1dbea 100644
--- a/docs/general-development/how-to-get-values-from-ranges.md
+++ b/docs/general-development/how-to-get-values-from-ranges.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Get Values from Ranges
+ms.date: 09/25/2017
 keywords: get range,how to,howdoi,howto
 f1_keywords:
 - get range,how to,howdoi,howto
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: ab2c0f60-b7df-46a1-9105-eb85ce817431
 ---
 
@@ -229,22 +230,22 @@ Next rangeResult
   
     
     
- [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name)
+ [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name.md)
   
     
     
- [How to: Set Values of Ranges](how-to-set-values-of-ranges)
+ [How to: Set Values of Ranges](how-to-set-values-of-ranges.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md b/docs/general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md
index 280bfe0224..4df70e2718 100644
--- a/docs/general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md
+++ b/docs/general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md
@@ -1,6 +1,7 @@
 ---
 title: How to Implement business logic and data validation in a Windows Phone app for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: fbbedc38-9651-4cd6-b523-d93cbf1cd39d
 ---
 
@@ -14,7 +15,7 @@ In a Windows Phone app intended for production use, you likely need to validate
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -48,7 +49,7 @@ Some of these basic validation rules are also enforced by default in a Windows P
   
     
     
-![Validation error cue in a Windows Phone app](../../images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif)
+![Validation error cue in a Windows Phone app](../images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif)
   
     
     
@@ -88,7 +89,7 @@ But some fields may not provide any notification for invalid data in the Windows
 ## Implement custom data-validation rules
 <a name="BKMK_CustomValidation"> </a>
 
-You can validate data entered by users of your Windows Phone app in several ways. A project created by using the Windows Phone SharePoint List Application template includes classes that serve as intermediaries between the forms (that is, the views) of the data in the Windows Phone app (for example, the EditForm.xaml file) and the data itself in the SharePoint list on which the app is based. These classes can be considered implementations of the ViewModel component of the  [Model-View-ViewModel design pattern](http://blogs.msdn.com/b/johngossman/archive/2005/10/08/478683.aspx) (Figure 2). (For more information about how the Windows Phone SharePoint List Application template conforms to the MVVM software design pattern, see [Architecture of the Windows Phone SharePoint List Application template](architecture-of-the-windows-phone-sharepoint-list-application-template).)
+You can validate data entered by users of your Windows Phone app in several ways. A project created by using the Windows Phone SharePoint List Application template includes classes that serve as intermediaries between the forms (that is, the views) of the data in the Windows Phone app (for example, the EditForm.xaml file) and the data itself in the SharePoint list on which the app is based. These classes can be considered implementations of the ViewModel component of the  [Model-View-ViewModel design pattern](http://blogs.msdn.com/b/johngossman/archive/2005/10/08/478683.aspx) (Figure 2). (For more information about how the Windows Phone SharePoint List Application template conforms to the MVVM software design pattern, see [Architecture of the Windows Phone SharePoint List Application template](architecture-of-the-windows-phone-sharepoint-list-application-template.md).)
   
     
     
@@ -109,7 +110,7 @@ You can validate data entered by users of your Windows Phone app in several ways
   
     
     
-![Template files in ViewModel component](../../images/2df9591d-a837-4130-98e4-5863d0c717e8.gif)
+![Template files in ViewModel component](../images/2df9591d-a837-4130-98e4-5863d0c717e8.gif)
   
     
     
@@ -167,7 +168,7 @@ Again, for the purposes of this example, assume that the following simple valida
 ### To implement custom validation rules
 
 
-1. Assuming you have created a SharePoint list based on the Custom List template that includes the columns and types specified in Table 1, create a Windows Phone app by using the Windows Phone SharePoint List Application template in Visual Studio by following the steps detailed in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app).
+1. Assuming you have created a SharePoint list based on the Custom List template that includes the columns and types specified in Table 1, create a Windows Phone app by using the Windows Phone SharePoint List Application template in Visual Studio by following the steps detailed in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md).
     
   
 2. In **Solution Explorer**, in the ViewModels folder for the project, double-click the EditItemViewModel.cs file (or choose the file and press F7) to open the file for editing.
@@ -290,7 +291,7 @@ If you build the project and deploy it to Windows Phone Emulator to run it, you
   
     
     
-![Custom validation error cues](../../images/fada902b-fa38-4ac8-8566-3693b736ac35.gif)
+![Custom validation error cues](../images/fada902b-fa38-4ac8-8566-3693b736ac35.gif)
   
     
     
@@ -298,7 +299,7 @@ The code in this sample, if it is included in the EditItemViewModel.cs file only
   
     
     
-The validation logic in this sample enforces given business rules by indicating to the user that entered data is not in a format permitted by the rules, but the entered data is not intercepted and changed by this code. To intercept and, for example, format phone numbers in a consistent way before saving the data to the SharePoint list, you can implement custom data conversion for entered phone numbers. For an explanation of custom data conversion for list item fields, see  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps).
+The validation logic in this sample enforces given business rules by indicating to the user that entered data is not in a format permitted by the rules, but the entered data is not intercepted and changed by this code. To intercept and, for example, format phone numbers in a consistent way before saving the data to the SharePoint list, you can implement custom data conversion for entered phone numbers. For an explanation of custom data conversion for list item fields, see  [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md).
   
     
     
@@ -307,13 +308,13 @@ The validation logic in this sample enforces given business rules by indicating
 <a name="SP15Implementbuslogic_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Silverlight Data Binding](http://msdn.microsoft.com/en-us/library/cc278072.aspx)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md b/docs/general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md
index 19217b09e1..e1c757817b 100644
--- a/docs/general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md
+++ b/docs/general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md
@@ -1,6 +1,7 @@
 ---
 title: How to Include mentions, tags, and links to sites and documents in posts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 975da333-372b-4bf6-a3f4-7452db369f04
 ---
 
@@ -14,7 +15,7 @@ In a social feed, the simplest form of post content contains only text, but you
 
 
 > **Note:**
-> To add embedded pictures, videos, or documents to a post's content, you add a  [SocialAttachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialAttachment.aspx) object to the [SocialPostCreationData.Attachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.Attachment.aspx) property. For more information, see [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server). 
+> To add embedded pictures, videos, or documents to a post's content, you add a  [SocialAttachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialAttachment.aspx) object to the [SocialPostCreationData.Attachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.Attachment.aspx) property. For more information, see [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md). 
   
     
     
@@ -43,7 +44,7 @@ The code examples in this article show how to add links to microblog posts. Thes
 - Microsoft.SharePoint.Client.UserProfilies
     
   
-For instructions about how to set up your development environment and create a console application, see  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli).
+For instructions about how to set up your development environment and create a console application, see  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md).
   
     
     
@@ -358,7 +359,7 @@ namespace IncludeTagInPost
 <a name="bk_addresources"> </a>
 
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
 -  [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) and [SocialDataItem](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialDataItem.aspx) in the client object models
@@ -367,7 +368,7 @@ namespace IncludeTagInPost
 -  [SocialPostCreationData](http://msdn.microsoft.com/library/f0e1fa3e-6fc9-48e0-5570-92091abfef33%28Office.15%29.aspx) and [SocialDataItem](http://msdn.microsoft.com/library/757e7b62-66a6-b03f-0ff0-769a42eb2b4a%28Office.15%29.aspx) in the JavaScript object model
     
   
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
 -  [SPSocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialPostCreationData.aspx) and [SPSocialDataItem](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialDataItem.aspx) in the server object model
diff --git a/docs/general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md b/docs/general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md
index e8f576865e..b7d7132796 100644
--- a/docs/general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md
+++ b/docs/general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md
@@ -1,6 +1,7 @@
 ---
 title: How to Integrate maps with Windows Phone apps and SharePoint lists
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7e0550bc-92d1-407f-b8ba-1371c63bd16e
 ---
 
@@ -14,7 +15,7 @@ SharePoint introduces a new field type named Geolocation that enables you to ann
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -40,7 +41,7 @@ Ensure that you have the following installed:
 - Access to a SharePoint list, with sufficient privileges to add a column
     
   
-- The Bing Maps key deployed to your server; see  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint)
+- The Bing Maps key deployed to your server; see  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md)
     
   
 
@@ -85,7 +86,7 @@ The Geolocation column is not available by default in SharePoint lists. You have
 
   
 
-  ![Adding the SharePoint list using the wizard](../../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png)
+  ![Adding the SharePoint list using the wizard](../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png)
   
 
   
@@ -241,7 +242,7 @@ In this step, you can run your app and validate it.
 
   
 
-  ![Allow privacy policy for maps](../../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png)
+  ![Allow privacy policy for maps](../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png)
   
 
     The map view is displayed, as shown in Figure 3.
@@ -251,7 +252,7 @@ In this step, you can run your app and validate it.
 
   
 
-  ![Map view on mobile app](../../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png)
+  ![Map view on mobile app](../images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png)
   
 
   
@@ -269,19 +270,19 @@ In this step, you can run your app and validate it.
 <a name="SP15Integmaps_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering)
+-  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md)
     
   
--  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint)
+-  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=27570)
diff --git a/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md b/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md
index ba30cbf7fd..212199542e 100644
--- a/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md
+++ b/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md
@@ -1,6 +1,7 @@
 ---
 title: How to Learn to read and write to the social feed by using the .NET client object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3c15ede5-8a59-47e6-a0b2-c17ec6bf4ae1
 ---
 
@@ -49,8 +50,8 @@ Table 1 contains links to articles that describe core concepts you should know b
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint) <br/> |Find out how to get started programming with social feeds and microblog posts, following people and content (documents, sites, and tags), and working with user profiles.  <br/> |
-| [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint) <br/> |Learn about common programming tasks for working with social feeds and the API that you use to perform the tasks.  <br/> |
+| [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md) <br/> |Find out how to get started programming with social feeds and microblog posts, following people and content (documents, sites, and tags.md), and working with user profiles.  <br/> |
+| [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md) <br/> |Learn about common programming tasks for working with social feeds and the API that you use to perform the tasks.  <br/> |
    
 
 ## Create the console application in Visual Studio 2012 and add references to client assemblies
@@ -291,7 +292,7 @@ To learn how to do more read tasks and write tasks with the social feed by using
     
     
 
--  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli)
+-  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md)
     
   
 
@@ -299,10 +300,10 @@ To learn how to do more read tasks and write tasks with the social feed by using
 <a name="SP15ReadWriteSocial_addlresources"> </a>
 
 
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md b/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md
index 1304358842..78dbd71597 100644
--- a/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md
+++ b/docs/general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md
@@ -1,6 +1,7 @@
 ---
 title: How to Learn to read and write to the social feed by using the REST service in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1da8d484-3666-42c3-8a8f-8b3ef93e96e9
 ---
 
@@ -57,8 +58,8 @@ The SharePoint-hosted app that you create in this article uses JavaScript to bui
 |**Article title**|**Description**|
 |:-----|:-----|
 | [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn about SharePoint Add-ins and fundamental concepts for building them.  <br/> |
-| [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint) <br/> |Find out how to start programming with social feeds and microblog posts, following people and content (documents, sites, and tags), and working with user profiles.  <br/> |
-| [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint) <br/> |Learn about common programming tasks for working with social feeds and the API that you use to perform the tasks.  <br/> |
+| [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md) <br/> |Find out how to start programming with social feeds and microblog posts, following people and content (documents, sites, and tags.md), and working with user profiles.  <br/> |
+| [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md) <br/> |Learn about common programming tasks for working with social feeds and the API that you use to perform the tasks.  <br/> |
    
 
 ## Create the SharePoint Add-in project
@@ -320,7 +321,7 @@ function feedRetrieved(data) {
 ## Next steps
 <a name="bkmk_PubPosts1"> </a>
 
-See  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint) and [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint) for other REST endpoints that you can use to access social features.
+See  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md) and [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md) for other REST endpoints that you can use to access social features.
   
     
     
@@ -329,13 +330,13 @@ See  [Social feed REST API reference for SharePoint](social-feed-rest-api-refere
 <a name="bk_addResources"> </a>
 
 
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md b/docs/general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md
index 55055669c8..9b0e65f000 100644
--- a/docs/general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md
+++ b/docs/general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md
@@ -1,9 +1,10 @@
 ---
 title: How to Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,WebUI DLL
 f1_keywords:
 - how to,howdoi,howto,WebUI DLL
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 09ad5d5e-1678-45e4-8159-23ef56f84215
 ---
 
@@ -254,19 +255,19 @@ C:\\Windows\\assembly\\GAC_MSIL\\Microsoft.Office.Excel.WebUI\\14.0.0.0__71e9bce
   
     
     
- [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page)
+ [How to: Programmatically Add an Excel Web Access Web Part to a Page](how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
diff --git a/docs/general-development/how-to-make-custom-css-files-themable-in-sharepoint.md b/docs/general-development/how-to-make-custom-css-files-themable-in-sharepoint.md
index 720d476c8a..7fc19e0be6 100644
--- a/docs/general-development/how-to-make-custom-css-files-themable-in-sharepoint.md
+++ b/docs/general-development/how-to-make-custom-css-files-themable-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Make custom CSS files themable in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b8c82c77-c836-47f9-a11e-6c9c656d436b
 ---
 
@@ -18,7 +19,7 @@ This article describes the available annotations and how to register CSS files.
   
     
     
-For more information about custom themes, see  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint) and [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint).
+For more information about custom themes, see  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md) and [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md).
   
     
     
@@ -51,7 +52,7 @@ The following shows the format for the **ReplaceColor** annotation.
 
 ```
 
-Replace  _ColorSlot_ with the annotation name of the color slot to use. To see a list of available color slots, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+Replace  _ColorSlot_ with the annotation name of the color slot to use. To see a list of available color slots, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint.md#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -101,7 +102,7 @@ The following shows the format for the **ReplaceFont** annotation.
 /* [ReplaceFont(themeFont:"FontSlot")] */
 ```
 
-Replace  _FontSlot_ with the name of the font slot to use. To see a list of available font slots, see the [Font slots](color-palettes-and-fonts-in-sharepoint#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+Replace  _FontSlot_ with the name of the font slot to use. To see a list of available font slots, see the [Font slots](color-palettes-and-fonts-in-sharepoint.md#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -152,7 +153,7 @@ The following describes the format of the **RecolorImage** annotation.
 
 ```
 
-Replace  _ColorSlot_ with the annotation name of the color slot. To see a list of available color slots, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+Replace  _ColorSlot_ with the annotation name of the color slot. To see a list of available color slots, see the [Color slot mapping](color-palettes-and-fonts-in-sharepoint.md#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
   
     
     
@@ -238,25 +239,25 @@ The following is an example of an **<SharePoint:CssRegistration>** element.
 <a name="addresources"> </a>
 
 
--  [Themes overview for SharePoint](themes-overview-for-sharepoint)
+-  [Themes overview for SharePoint](themes-overview-for-sharepoint.md)
     
   
--  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint)
+-  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md)
     
   
--  [Upgrade custom themes and CSS to SharePoint](upgrade-custom-themes-and-css-to-sharepoint)
+-  [Upgrade custom themes and CSS to SharePoint](upgrade-custom-themes-and-css-to-sharepoint.md)
     
   
--  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+-  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
--  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint)
+-  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
 
diff --git a/docs/general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md b/docs/general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md
index 6428d1a328..2303a65e8d 100644
--- a/docs/general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md
+++ b/docs/general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md
@@ -1,6 +1,7 @@
 ---
 title: How to Map a network drive to the SharePoint Master Page Gallery
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7d416f6e-2471-4d03-97ae-4e8d907784c6
 ---
 
@@ -50,19 +51,19 @@ On the computer that runs your design tool or HTML editor, map a network drive t
 <a name="bk_addresources"> </a>
 
 
--  [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint)
+-  [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels)
+-  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels.md)
     
   
--  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager)
+-  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md)
     
   
--  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions)
+-  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions.md)
     
   
 
diff --git a/docs/general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md b/docs/general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md
index 4ca0548993..9e43f743db 100644
--- a/docs/general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md
+++ b/docs/general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md
@@ -1,9 +1,10 @@
 ---
 title: How to Programmatically Add an Excel Web Access Web Part to a Page
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,webpart
 f1_keywords:
 - how to,howdoi,howto,webpart
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 858bb0f6-654a-4f12-ba0b-4776bda5ff6d
 ---
 
@@ -24,7 +25,7 @@ The following project uses Microsoft Visual Studio.
 
 
 > **Note:**
-> It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location). 
+> It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location.md). 
   
     
     
@@ -38,7 +39,7 @@ The following steps show how to locate Microsoft.Office.Excel.WebUI.dll and how
     
 
 > **Note:**
-> It is assumed that you have already copied Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll from the global assembly cache to a folder of your choice. For more information about how to locate and copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll, see  [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc). 
+> It is assumed that you have already copied Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll from the global assembly cache to a folder of your choice. For more information about how to locate and copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll, see  [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md). 
   
     
     
@@ -522,15 +523,15 @@ The Excel workbook that you are using must be in a trusted location.
   
     
     
- [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc)
+ [How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll](how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
diff --git a/docs/general-development/how-to-refresh-data.md b/docs/general-development/how-to-refresh-data.md
index db570f2b0d..8ab593d1c8 100644
--- a/docs/general-development/how-to-refresh-data.md
+++ b/docs/general-development/how-to-refresh-data.md
@@ -1,9 +1,10 @@
 ---
 title: How to Refresh Data
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto
 f1_keywords:
 - how to,howdoi,howto
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 6cfd89ff-846e-486b-8f73-a109016813ab
 ---
 
@@ -209,38 +210,38 @@ binaryWriter.Close()
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
   
     
     
- [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot)
+ [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md b/docs/general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md
index fb1d1b66d0..7d410fac6d 100644
--- a/docs/general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md
+++ b/docs/general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Resolve errors and warnings when previewing a page in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 03f72f65-b22b-4304-be92-f44ce0619372
 ---
 
@@ -14,7 +15,7 @@ After you convert an HTML file into a SharePoint master page, or after you creat
   
     
     
-The preview in Design Manager is a live server-side preview, so any snippets or controls on your page, such as a navigation control or a search-driven Web Part, use live data. Also, when you preview a master page or page layout, you can choose a generic preview of just that file, or you can choose to preview how a specific page in your site renders with that master page or page layout. The server-side preview is a highly useful tool that complements the design-time preview in an HTML editor. For more information, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager).
+The preview in Design Manager is a live server-side preview, so any snippets or controls on your page, such as a navigation control or a search-driven Web Part, use live data. Also, when you preview a master page or page layout, you can choose a generic preview of just that file, or you can choose to preview how a specific page in your site renders with that master page or page layout. The server-side preview is a highly useful tool that complements the design-time preview in an HTML editor. For more information, see  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md).
   
     
     
@@ -60,7 +61,7 @@ If you want an HTML **\<form\>** tag in the page layout, you should put the form
 <!--CE: End Create Snippets From Custom ASP.NET Markup Snippet-->
 ```
 
-You can also add the HTML Form Web Part or the InfoPath Form Web Part to your page from the Snippet Gallery. For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+You can also add the HTML Form Web Part or the InfoPath Form Web Part to your page from the Snippet Gallery. For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
   
     
     
@@ -170,13 +171,13 @@ You see this message when you aren't using a live SharePoint page with which to
 <a name="bk_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager)
+-  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md)
     
   
--  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets)
+-  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md)
     
   
 
diff --git a/docs/general-development/how-to-restrict-udf-code-access-security-permissions.md b/docs/general-development/how-to-restrict-udf-code-access-security-permissions.md
index 243c7bec6c..a97d8f4761 100644
--- a/docs/general-development/how-to-restrict-udf-code-access-security-permissions.md
+++ b/docs/general-development/how-to-restrict-udf-code-access-security-permissions.md
@@ -1,9 +1,10 @@
 ---
 title: How to Restrict UDF Code Access Security Permissions
+ms.date: 09/25/2017
 keywords: cas,how to,howdoi,howto,UDF list
 f1_keywords:
 - cas,how to,howdoi,howto,UDF list
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 4f022e0d-1fe3-4fab-b41f-82a0d628f77c
 ---
 
@@ -134,31 +135,31 @@ For more information about configuring code groups, see the following articles o
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
   
     
     
- [How to: Access an External Data Source from a UDF](how-to-access-an-external-data-source-from-a-udf)
+ [How to: Access an External Data Source from a UDF](how-to-access-an-external-data-source-from-a-udf.md)
   
     
     
- [How to: Deploy UDFs Using SharePoint Foundation Solutions](how-to-deploy-udfs-using-sharepoint-foundation-solutions)
+ [How to: Deploy UDFs Using SharePoint Foundation Solutions](how-to-deploy-udfs-using-sharepoint-foundation-solutions.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/how-to-retrieve-the-url-of-a-pages-library.md b/docs/general-development/how-to-retrieve-the-url-of-a-pages-library.md
index baadcbb759..711e647ef4 100644
--- a/docs/general-development/how-to-retrieve-the-url-of-a-pages-library.md
+++ b/docs/general-development/how-to-retrieve-the-url-of-a-pages-library.md
@@ -1,6 +1,7 @@
 ---
 title: How to Retrieve the URL of a Pages library
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d9922e4b-4948-4c4a-a8ca-1623168143a3
 ---
 
@@ -114,7 +115,7 @@ Key = vti_pageslistname, Value = {the URL to the Pages list}
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md b/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md
index a274cf03c7..4d21faa5f4 100644
--- a/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md
+++ b/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md
@@ -1,6 +1,7 @@
 ---
 title: How to Retrieve user profile properties by using the JavaScript object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c6e1ca38-134f-428a-8d21-b8b2615b161b
 ---
 
@@ -25,7 +26,7 @@ The  [PeopleManager](http://msdn.microsoft.com/library/985fd2df-0e31-6ece-b846-b
 - The  [getUserProfilePropertiesFor](http://msdn.microsoft.com/library/8674e96f-d320-4a50-1580-9a4568842ee5%28Office.15%29.aspx) method and the [getUserProfilePropertyFor](http://msdn.microsoft.com/library/da048bfa-54c6-8216-e8ef-09bd84f68d8d%28Office.15%29.aspx) method return the values of the user profile properties that you specify.
     
   
-User profile properties from client APIs are read-only (except the profile picture, which you can change by using the  [PeopleManager.setMyProfilePicture](http://msdn.microsoft.com/library/a4f8d745-f211-e750-4fd0-047091804683%28Office.15%29.aspx) method). If you want to change other user profile properties, you must use the server object model. For more information about working with user profiles, see [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint).
+User profile properties from client APIs are read-only (except the profile picture, which you can change by using the  [PeopleManager.setMyProfilePicture](http://msdn.microsoft.com/library/a4f8d745-f211-e750-4fd0-047091804683%28Office.15%29.aspx) method). If you want to change other user profile properties, you must use the server object model. For more information about working with user profiles, see [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md).
   
     
     
@@ -102,8 +103,8 @@ To create an application page that uses the JavaScript object model to retrieve
 
 10. To add logic to retrieve user profile properties, replace the comment between the **script** tags with the code example from one of the following scenarios:
     
-  -  [Retrieve user profile properties from the PersonProperties object and its userProfileProperties property](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in#bk_examplePersonPropsObj)  
-  -  [Retrieve a set of user profile properties by using the getUserProfilePropertiesFor method](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in#bk_exampleGetUPMethod)
+  -  [Retrieve user profile properties from the PersonProperties object and its userProfileProperties property](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md#bk_examplePersonPropsObj)  
+  -  [Retrieve a set of user profile properties by using the getUserProfilePropertiesFor method](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md#bk_exampleGetUPMethod)
     
   
 11. To test the application page, on the menu bar, choose **Debug**, **Start Debugging**. If you're prompted to modify the web.config file, choose the **OK** button.
@@ -129,7 +130,7 @@ The following code example shows how to get user profile properties for a target
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added to the UserProfiles.aspx file in the [Create the application page](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in#bk_CreateAppPage) procedure. Replace the `domainName\\userName` placeholder value before you run the code. (This code example does not use the code-behind class file.)
+> Paste the following code between the **script** tags that you added to the UserProfiles.aspx file in the [Create the application page](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md#bk_CreateAppPage) procedure. Replace the `domainName\\userName` placeholder value before you run the code. (This code example does not use the code-behind class file.)
   
     
     
@@ -200,7 +201,7 @@ The following code example retrieves the values for a specified set of user prof
   
 
 > **Note:**
-> Paste the following code between the **script** tags that you added to the UserProfiles.aspx file in the [Create the application page](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in#bk_CreateAppPage) procedure. Replace the `domainName\\\\userName` placeholder value before you run the code. (This code example does not use the code-behind class file.)
+> Paste the following code between the **script** tags that you added to the UserProfiles.aspx file in the [Create the application page](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md#bk_CreateAppPage) procedure. Replace the `domainName\\\\userName` placeholder value before you run the code. (This code example does not use the code-behind class file.)
   
     
     
@@ -262,13 +263,13 @@ function onRequestFail(sender, args) {
 <a name="bk_addresources"> </a>
 
 
--  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint)
+-  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md)
     
   
--  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in)
+-  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md)
     
   
--  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)
+-  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)
     
   
 -  [SP.UserProfiles namespace (sp.userprofiles)](http://msdn.microsoft.com/library/8c1fcceb-cd9a-b25c-32f4-1cfb0578278c%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md b/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md
index 07f75e1346..b9663a742d 100644
--- a/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md
+++ b/docs/general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md
@@ -1,6 +1,7 @@
 ---
 title: How to Retrieve user profile properties by using the .NET client object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 236ebaf8-f92e-4192-9b51-0a9de0210885
 ---
 
@@ -36,7 +37,7 @@ User profile properties from client APIs are read-only (except the profile pictu
     
     
 
-For more information about working with profiles, see  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint).
+For more information about working with profiles, see  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md).
   
     
     
@@ -139,7 +140,7 @@ foreach (var property in personProperties.UserProfileProperties)
 ## Code example: Retrieving all user profile properties by using the SharePoint .NET client object model
 <a name="SP15UserProf_codeexample1"> </a>
 
-The following code example shows how to retrieve and iterate through all the user profile properties of a target user, as described in the  [previous procedure](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in#bk_RetrieveProps).
+The following code example shows how to retrieve and iterate through all the user profile properties of a target user, as described in the  [previous procedure](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md#bk_RetrieveProps).
   
     
     
@@ -319,13 +320,13 @@ namespace UserProfilesCSOM
 <a name="bk_addresources"> </a>
 
 
--  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint)
+-  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md)
     
   
--  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in)
+-  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md)
     
   
--  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)
+-  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)
     
   
 -  [Microsoft.SharePoint.Client.UserProfiles](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.aspx)
diff --git a/docs/general-development/how-to-save-from-excel-client-to-the-server.md b/docs/general-development/how-to-save-from-excel-client-to-the-server.md
index 25d9ddbab0..a7bb8f34d8 100644
--- a/docs/general-development/how-to-save-from-excel-client-to-the-server.md
+++ b/docs/general-development/how-to-save-from-excel-client-to-the-server.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Save from Excel Client to the Server
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto
 f1_keywords:
 - how to,howdoi,howto
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 28716ba5-0774-44df-833b-0034d2c63319
 ---
 
@@ -22,7 +23,7 @@ This example shows you how to:
 2. Save the workbook to a SharePoint document library that is a trusted location.
     
     > **Note:**
-      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location). 
+      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location.md). 
 3. Change values in a workbook by using the parameters pane in Excel Web Access.
     
   
@@ -110,26 +111,26 @@ This example shows you how to:
   
     
     
- [How to: Save to the Server to Prepare for Programmatic Access](how-to-save-to-the-server-to-prepare-for-programmatic-access)
+ [How to: Save to the Server to Prepare for Programmatic Access](how-to-save-to-the-server-to-prepare-for-programmatic-access.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access.md b/docs/general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access.md
index 995f0b0ced..c436c6740b 100644
--- a/docs/general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access.md
+++ b/docs/general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Save to the Server to Prepare for Programmatic Access
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto
 f1_keywords:
 - how to,howdoi,howto
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 80b34a29-3d40-4d11-9ba1-b4886ffcfd42
 ---
 
@@ -22,7 +23,7 @@ This example shows how to save an Excel workbook to the server to to prepare it
 2. Save the workbook to a trusted SharePoint library location. 
     
     > **Note:**
-      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location). 
+      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information, see  [How to: Trust a Location](how-to-trust-a-location.md). 
 3. Programmatically specify values for the worksheet, named range, and cell value by using the Excel Web Services **SetCellA1** method. The values are passed in as arguments—that is, _args [1]_ and _args [2]_:
     
 ```cs
@@ -48,7 +49,7 @@ You can specify the values of  _args [1]_ and _args [2]_ by using a Web form or
 GetSnapshot.exe http://MyServer002/MyTrustedDocumentLibrary/TestMyParam.xlsx MyParam28 > MySnapshot.xlsx 
 ```
 
-In this example,  _args [1]_ is **MyParam**, **args [2]** is _28_ and _GetSnapshot.exe_ is the name of the application that you create. To find a sample program, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot).
+In this example,  _args [1]_ is **MyParam**, **args [2]** is _28_ and _GetSnapshot.exe_ is the name of the application that you create. To find a sample program, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md).
 ### To create a named range
 
 
@@ -189,7 +190,7 @@ status = xlSrv.SetCellA1(sessionId, String.Empty, args[1], args[2]);
   
 
 > **Note:**
-> For more information about snapshots, see  [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot). For more information about the **SetCellA1** method, see the Excel Web Services reference documentation. The namespace of the Web service is [Microsoft.Office.Excel.Server.WebServices](https://msdn.microsoft.com/library/Microsoft.Office.Excel.Server.WebServices.aspx) .
+> For more information about snapshots, see  [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md). For more information about the **SetCellA1** method, see the Excel Web Services reference documentation. The namespace of the Web service is [Microsoft.Office.Excel.Server.WebServices](https://msdn.microsoft.com/library/Microsoft.Office.Excel.Server.WebServices.aspx) .
   
     
     
@@ -204,7 +205,7 @@ status = xlSrv.SetCellA1(sessionId, String.Empty, args[1], args[2]);
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
 #### Reference
 
 
@@ -218,19 +219,19 @@ status = xlSrv.SetCellA1(sessionId, String.Empty, args[1], args[2]);
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md b/docs/general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md
index b30c493d1a..1bf70ee8f1 100644
--- a/docs/general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md
+++ b/docs/general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Set the Bing Maps key at the web and farm level in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 507ed9de-c349-44b5-b182-e838795dd862
 ---
 
@@ -10,7 +11,7 @@ ms.assetid: 507ed9de-c349-44b5-b182-e838795dd862
   
     
     
-![How to topic](../../images/mod_icon_howto.png)
+![How to topic](../images/mod_icon_howto.png)
   
     
     
@@ -145,10 +146,10 @@ To learn more about working with location and map functionality in SharePoint, s
     
     
 
--  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint)
+-  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md)
     
   
--  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering)
+-  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md)
     
   
 
diff --git a/docs/general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md b/docs/general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md
index 2f43a592c4..4795ec58fc 100644
--- a/docs/general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md
+++ b/docs/general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Set up an environment for developing mobile apps for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: acaf556d-e20d-478d-8c59-2efd8efb9dcb
 ---
 
@@ -71,7 +72,7 @@ To develop SharePoint Add-ins for use on Windows Phone 8, you need to set up you
 
     > **Note:**
       > The templates in the SharePoint SDK for Windows Phone are currently available for C# projects only. 
-For more information about the templates in SharePoint SDK for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio).
+For more information about the templates in SharePoint SDK for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md).
   
     
     
@@ -114,7 +115,7 @@ To develop SharePoint Add-ins for use on Windows Phone 7, you need to set up you
 
     > **Note:**
       > The templates in the SharePoint SDK for Windows Phone are currently available for C# projects only. 
-For more information about the templates in SharePoint SDK for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio).
+For more information about the templates in SharePoint SDK for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md).
   
     
     
@@ -123,7 +124,7 @@ For more information about the templates in SharePoint SDK for Windows Phone, se
 <a name="SP15Setupmobile_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-set-values-of-ranges.md b/docs/general-development/how-to-set-values-of-ranges.md
index 683bae2959..d929bab539 100644
--- a/docs/general-development/how-to-set-values-of-ranges.md
+++ b/docs/general-development/how-to-set-values-of-ranges.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Set Values of Ranges
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,set range
 f1_keywords:
 - how to,howdoi,howto,set range
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: ccc7e204-f857-45a9-81ec-3a8484e6d454
 ---
 
@@ -17,7 +18,7 @@ Excel Web Services exposes four methods for setting values into an Excel workboo
 
 
 > **Note:**
-> When you make changes to a workbook—for example, by setting values to a range using Excel Web Services—the changes to the workbook are preserved only for that particular session. The changes are not saved or persisted back to the original workbook. When the current workbook session ends (for example, when you call the **CloseWorkbook** method, or the session times out), changes you made will be lost.> If you want to save changes you make to a workbook, you can use the **GetWorkbook** method and then save the workbook using the API of the destination file store. For more information, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot) and [How to: Save a Workbook](http://msdn.microsoft.com/library/feb74f7a-2d8f-4672-911b-de85f8852aea%28Office.15%29.aspx). 
+> When you make changes to a workbook—for example, by setting values to a range using Excel Web Services—the changes to the workbook are preserved only for that particular session. The changes are not saved or persisted back to the original workbook. When the current workbook session ends (for example, when you call the **CloseWorkbook** method, or the session times out), changes you made will be lost.> If you want to save changes you make to a workbook, you can use the **GetWorkbook** method and then save the workbook using the API of the destination file store. For more information, see [How to: Get an Entire Workbook or a Snapshot](how-to-get-an-entire-workbook-or-a-snapshot.md) and [How to: Save a Workbook](http://msdn.microsoft.com/library/feb74f7a-2d8f-4672-911b-de85f8852aea%28Office.15%29.aspx). 
   
     
     
@@ -343,22 +344,22 @@ End Sub
   
     
     
- [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name)
+ [How to: Specify a Range Address and Sheet Name](how-to-specify-a-range-address-and-sheet-name.md)
   
     
     
- [How to: Get Values from Ranges](how-to-get-values-from-ranges)
+ [How to: Get Values from Ranges](how-to-get-values-from-ranges.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-set-various-credentials.md b/docs/general-development/how-to-set-various-credentials.md
index 3f0893f977..28e1469f3c 100644
--- a/docs/general-development/how-to-set-various-credentials.md
+++ b/docs/general-development/how-to-set-various-credentials.md
@@ -1,13 +1,14 @@
 ---
 title: How to Set Various Credentials
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: eb819681-5a4f-49ae-b7f4-334366c51112
 ---
 
 
 # How to: Set Various Credentials
 
-You must set credentials for your users before they can call Excel Web Services by using your custom application. You must explicitly set credentials even if you intend to use the default credentials. Excel Web Services uses the authentication schemes that Microsoft SharePoint Foundation supports. For more information about SharePoint Foundation authentication schemes, see the SharePoint Foundation documentation in this SDK and  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint).
+You must set credentials for your users before they can call Excel Web Services by using your custom application. You must explicitly set credentials even if you intend to use the default credentials. Excel Web Services uses the authentication schemes that Microsoft SharePoint Foundation supports. For more information about SharePoint Foundation authentication schemes, see the SharePoint Foundation documentation in this SDK and  [Incoming claims: Signing into SharePoint](incoming-claims-signing-into-sharepoint.md).
   
     
     
@@ -250,27 +251,27 @@ For more information about how to use the **CredentialCache** class and the **Ne
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-specify-a-range-address-and-sheet-name.md b/docs/general-development/how-to-specify-a-range-address-and-sheet-name.md
index c54dc5de02..3faab0a19d 100644
--- a/docs/general-development/how-to-specify-a-range-address-and-sheet-name.md
+++ b/docs/general-development/how-to-specify-a-range-address-and-sheet-name.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Specify a Range Address and Sheet Name
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,set range
 f1_keywords:
 - how to,howdoi,howto,set range
-ms.prod: OFFICE365
+ms.prod: sharepoint
 ms.assetid: 8bfefc48-1fbc-4b65-8156-1b7d0a8453ee
 ---
 
@@ -75,7 +76,7 @@ If you specify a sheet name, the ranges you reference must exist on the sheet yo
 
 
 > **Note:**
-> It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information about this, see  [How to: Trust a Location](how-to-trust-a-location) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx). 
+> It is assumed that you have already created a SharePoint document library and made it a trusted location. For more information about this, see  [How to: Trust a Location](how-to-trust-a-location.md) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx). 
   
     
     
@@ -264,22 +265,22 @@ Make sure you add a Web reference to an Excel Web Services site to which you hav
   
     
     
- [How to: Get Values from Ranges](how-to-get-values-from-ranges)
+ [How to: Get Values from Ranges](how-to-get-values-from-ranges.md)
   
     
     
- [How to: Set Values of Ranges](how-to-set-values-of-ranges)
+ [How to: Set Values of Ranges](how-to-set-values-of-ranges.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md b/docs/general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md
index a2357430f8..1522b5ea68 100644
--- a/docs/general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md
+++ b/docs/general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md
@@ -1,6 +1,7 @@
 ---
 title: How to Store and retrieve SharePoint list items on a Windows Phone
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 14ca37a2-5b45-430d-9004-ff3016f89834
 ---
 
@@ -14,7 +15,7 @@ One of the most important considerations in the development of Windows Phone app
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -66,7 +67,7 @@ The **Application_Launching** and **Application_Closing** handlers for these eve
 ### To implement event handlers for storing and retrieving application state
 
 
-1. Create a Windows Phone app by using the Windows Phone SharePoint List Application template in Visual Studio by following the steps in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app).
+1. Create a Windows Phone app by using the Windows Phone SharePoint List Application template in Visual Studio by following the steps in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md).
     
   
 2. In **Solution Explorer**, choose the App.xaml file.
@@ -850,7 +851,7 @@ If you start the project and deploy it to a Windows Phone Emulator, you see a **
   
     
     
-![Modified List Form with View Drafts button](../../images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif)
+![Modified List Form with View Drafts button](../images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif)
   
     
     
@@ -868,7 +869,7 @@ At first, because no drafts are saved, the page to display drafts will be empty.
   
     
     
-![Modified Edit Form with Save Draft button](../../images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif)
+![Modified Edit Form with Save Draft button](../images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif)
   
     
     
@@ -886,7 +887,7 @@ When the server becomes available again, you can choose the **View Drafts** butt
   
     
     
-![Drafts page displaying list items saved as drafts](../../images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif)
+![Drafts page displaying list items saved as drafts](../images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif)
   
     
     
@@ -904,7 +905,7 @@ If you choose an item on the Drafts page, the Draft Item Edit form (DraftItemEdi
   
     
     
-![The Draft Item Edit Form](../../images/e3718687-682a-41a8-92b5-4eff9070348d.gif)
+![The Draft Item Edit Form](../images/e3718687-682a-41a8-92b5-4eff9070348d.gif)
   
     
     
@@ -917,7 +918,7 @@ Notice the similarity between the Draft Item Edit form (Figure 4) and the standa
 <a name="SP15StoreSPlist_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Local Data Storage for Windows Phone](http://msdn.microsoft.com/library/fdf7e973-5de5-4cfa-bf63-1e65c90744cc%28Office.15%29.aspx)
@@ -932,7 +933,7 @@ Notice the similarity between the Draft Item Edit form (Figure 4) and the standa
 -  [Microsoft SharePoint SDK for Windows Phone 8](http://www.microsoft.com/en-us/download/details.aspx?id=36818)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=27570)
diff --git a/docs/general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md b/docs/general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md
index 585f40ca31..b63370dded 100644
--- a/docs/general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md
+++ b/docs/general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md
@@ -1,6 +1,7 @@
 ---
 title: How to Support and convert SharePoint field types for Windows Phone apps
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 301e6e58-5153-4ca9-a419-8ae0535ebbed
 ---
 
@@ -14,7 +15,7 @@ In projects based on the Windows Phone SharePoint List Application template, the
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -163,7 +164,7 @@ The **RegisterDisplayFieldValueConverter** method accepts a **get** function onl
   
     
     
-In  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s), a validation routine was developed to verify the format or phone numbers provided by the user of a Windows Phone app. To demonstrate custom data conversion, in the following code sample, we'll implement **get** and **set** functions to handle phone number data in a particular way and register those functions to be used in the Edit and New forms with the **Converter** class.
+In  [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md), a validation routine was developed to verify the format or phone numbers provided by the user of a Windows Phone app. To demonstrate custom data conversion, in the following code sample, we'll implement **get** and **set** functions to handle phone number data in a particular way and register those functions to be used in the Edit and New forms with the **Converter** class.
   
     
     
@@ -175,7 +176,7 @@ Assume for the purposes of the following code example that you have created a Wi
 ### To implement custom data conversion
 
 
-1. Assuming you have created a list on a SharePoint Server that includes a **Text** field named "Contact Number" (like the Product Orders sample list used in [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s)), create a Windows Phone app using the Windows Phone SharePoint List Application template in Visual Studio by following the steps detailed in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app).
+1. Assuming you have created a list on a SharePoint Server that includes a **Text** field named "Contact Number" (like the Product Orders sample list used in [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md)), create a Windows Phone app using the Windows Phone SharePoint List Application template in Visual Studio by following the steps detailed in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md).
     
   
 2. In **Solution Explorer**, choose the node representing the project (named, for example, ContosoSPListApp).
@@ -573,7 +574,7 @@ If you start the project and deploy the app to the Windows Phone Emulator to run
   
     
     
-![Displaying Guid fields](../../images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif)
+![Displaying Guid fields](../images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif)
   
     
     
@@ -605,10 +606,10 @@ Now the Identifier field is shown on the Display form as well as on the List for
 <a name="SP15Supportwinphone_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-trust-a-location.md b/docs/general-development/how-to-trust-a-location.md
index 916b4262d8..0e71face61 100644
--- a/docs/general-development/how-to-trust-a-location.md
+++ b/docs/general-development/how-to-trust-a-location.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Trust a Location
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,trusted location
 f1_keywords:
 - how to,howdoi,howto,trusted location
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 0f396c0b-f578-4d1a-9e6b-a75f352265ab
 ---
 
@@ -66,22 +67,22 @@ You can also trust a location by using Windows PowerShell. For more information,
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md b/docs/general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md
index 2fae3913e7..cb7008aba8 100644
--- a/docs/general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md
+++ b/docs/general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md
@@ -1,6 +1,7 @@
----
+---
 title: How to Use a custom security trimmer for SharePoint Server search results
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e1a8664e-fb43-45c2-83aa-9635fe1efc99
 ---
 
@@ -446,7 +447,7 @@ net restart sphostcontrollerservice
 <a name="bk_sectrimmer_addlresources"> </a>
 
 
--  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server)
+-  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server.md)
     
   
 -  [Microsoft.Office.Server.Search.Query.ISecurityTrimmerPre](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.Query.ISecurityTrimmerPre.aspx)
diff --git a/docs/general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md b/docs/general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md
index 4cbbd64226..79b74b0fc7 100644
--- a/docs/general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md
+++ b/docs/general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use code to pin terms to navigation term sets in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4a2811dc-25fd-4eb2-b0ab-1edded64c556
 ---
 
@@ -27,7 +28,7 @@ To understand pinning in SharePoint, you may want to learn about managed metadat
 |**Article title**|**Description**|
 |:-----|:-----|
 | [A Brief Introduction to Enterprise Metadata Management for Microsoft SharePoint Server 2010 Developers](http://msdn.microsoft.com/library/113a5d75-ac4d-498b-8436-725e04fb685d%28Office.15%29.aspx) <br/> |Written for SharePoint Server 2010, this article provides a basic overview of the enterprise managed metadata programming model and core concepts, such as terms and term sets.  <br/> |
-| [Managed navigation in SharePoint](managed-navigation-in-sharepoint) <br/> |An introduction to the taxonomy-driven managed navigation feature in SharePoint.  <br/> |
+| [Managed navigation in SharePoint](managed-navigation-in-sharepoint.md) <br/> |An introduction to the taxonomy-driven managed navigation feature in SharePoint.  <br/> |
    
 
 ## Use code to complete pinning tasks
@@ -142,7 +143,7 @@ using (SPSite site = new SPSite(TestConfig.ServerUrl))
 <a name="SP15_H2UseCodeToPinTerms_AdditionalResources"> </a>
 
 
--  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint)
+-  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint.md)
     
   
 -  [Microsoft.SharePoint.Publishing.Navigation](https://msdn.microsoft.com/library/Microsoft.SharePoint.Publishing.Navigation.aspx)
diff --git a/docs/general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md b/docs/general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md
index 0e39c5afa2..9a545dd16c 100644
--- a/docs/general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md
+++ b/docs/general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use multiple SharePoint lists in a Windows Phone app
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5251d35a-d659-49b3-8e0d-dfd4a7faee6b
 ---
 
@@ -14,7 +15,7 @@ You can use multiple SharePoint lists in your app in several ways. When you crea
 
 
 > **Important:**
-> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint). 
+> If you are developing an app for Windows Phone 8, you must use Visual Studio Express 2012 instead of Visual Studio 2010 Express. Except for the development environment, all information in this article applies to creating apps for both Windows Phone 8 and Windows Phone 7. > For more information, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md). 
   
     
     
@@ -396,7 +397,7 @@ In the following procedures, you create a Windows Phone app that uses both of th
 ### To create the component projects for the solution
 
 
-1. Create a Windows Phone app by using the Windows Phone SharePoint List Application template, specifying a SharePoint list defined based on the columns and field types shown in Table 2. In the procedures in this section, it is assumed that the name of the list in the project is "Customers" and the name of the project is "CustomersSPListApp". (See  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app) for information about creating an app based on the Windows Phone SharePoint List Application template.)
+1. Create a Windows Phone app by using the Windows Phone SharePoint List Application template, specifying a SharePoint list defined based on the columns and field types shown in Table 2. In the procedures in this section, it is assumed that the name of the list in the project is "Customers" and the name of the project is "CustomersSPListApp". (See  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md) for information about creating an app based on the Windows Phone SharePoint List Application template..md)
     
   
 2. In Visual Studio, choose **File**, **Add**, **New Project**. 
@@ -413,7 +414,7 @@ In the following procedures, you create a Windows Phone app that uses both of th
 5. Name the app, for example, OrdersSPListApp, and then choose **OK**.
     
   
-6. Follow the procedure described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app) to create another Windows Phone app project, specifying a SharePoint list defined based on the columns and field types show in Table 1 as the target list for the project. You should now have two projects in your solution, named "CustomersSPListApp" and "OrdersSPListApp" (if you are following the naming conventions in this procedure).
+6. Follow the procedure described in  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md) to create another Windows Phone app project, specifying a SharePoint list defined based on the columns and field types show in Table 1 as the target list for the project. You should now have two projects in your solution, named "CustomersSPListApp" and "OrdersSPListApp" (if you are following the naming conventions in this procedure).
     
   
 7. In **Solution Explorer**, choose the CustomerSPListApp project node.
@@ -847,7 +848,7 @@ If you build the solution and deploy it to the Windows Phone Emulator, the List
   
     
     
-![Customers Display form](../../images/70d5a602-b349-4791-bf05-d61635d0fc91.gif)
+![Customers Display form](../images/70d5a602-b349-4791-bf05-d61635d0fc91.gif)
   
     
     
@@ -865,7 +866,7 @@ When you choose the **Get Orders** button on this Display form, the orders for t
   
     
     
-![Orders List form](../../images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif)
+![Orders List form](../images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif)
   
     
     
@@ -878,10 +879,10 @@ From this form (the List form for the Orders list) you can add, edit, or delete
 <a name="SP15Usemultlists_addlresources"> </a>
 
 
--  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows)
+-  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0.md b/docs/general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0.md
index 58a5aceae2..5d5e19d930 100644
--- a/docs/general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0.md
+++ b/docs/general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use SAP Reporting with Duet Enterprise 2.0
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a54c6cd2-2283-440d-af55-e98e3212caa1
 ---
 
@@ -98,13 +99,13 @@ Inside an app, a developer can also create his own custom UI (using HTML/JavaScr
 <a name="bk_addresources"> </a>
 
 
--  [Developing with Duet Enterprise 2.0](developing-with-duet-enterprise-2-0)
+-  [Developing with Duet Enterprise 2.0](developing-with-duet-enterprise-2-0.md)
     
   
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
--  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint)
+-  [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0.md b/docs/general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0.md
index bc4abb475c..a7e8a98461 100644
--- a/docs/general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0.md
+++ b/docs/general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use SAP workflow with Duet Enterprise 2.0
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 816e28ed-8cea-4e33-98e5-d3d27136e2e6
 ---
 
diff --git a/docs/general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md b/docs/general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md
index 8ff012569d..81c315f98e 100644
--- a/docs/general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md
+++ b/docs/general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use the client code library to access external data in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c280ae92-c52b-4658-b0f3-805fb215ef8e
 ---
 
@@ -30,7 +31,7 @@ The following are requirements for being able to develop apps using the SharePoi
 - Office Developer Tools for Visual Studio 2012
     
   
-- A functioning SharePoint Add-ins development environment: Follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+- A functioning SharePoint Add-ins development environment: Follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
     
   
 - Access to the public OData.org producers
@@ -200,10 +201,10 @@ Press F5 to deploy the app to SharePoint. Browse to the Default.aspx page in the
 <a name="bkmk_Addresources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint)
+-  [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md)
     
   
 -  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx)
@@ -212,10 +213,10 @@ Press F5 to deploy the app to SharePoint. Browse to the Default.aspx page in the
 -  [Choose patterns for developing and hosting your SharePoint Add-in](http://msdn.microsoft.com/library/05ce5435-0a03-4ddc-976b-c33b08d03457%28Office.15%29.aspx)
     
   
--  [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint)
+-  [BCS client object model reference for SharePoint](bcs-client-object-model-reference-for-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
 -  [Complete basic operations using SharePoint client library code](http://msdn.microsoft.com/library/5a69c9e3-73bf-4ed5-bc19-182056bdb394%28Office.15%29.aspx)
diff --git a/docs/general-development/how-to-use-the-closeworkbook-method-call-asynchronously.md b/docs/general-development/how-to-use-the-closeworkbook-method-call-asynchronously.md
index b1cf4804ab..5600ab6559 100644
--- a/docs/general-development/how-to-use-the-closeworkbook-method-call-asynchronously.md
+++ b/docs/general-development/how-to-use-the-closeworkbook-method-call-asynchronously.md
@@ -1,9 +1,10 @@
----
+---
 title: How to Use the CloseWorkbook Method Call Asynchronously
+ms.date: 09/25/2017
 keywords: async,how to,howdoi,howto
 f1_keywords:
 - async,how to,howdoi,howto
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 6febe7dc-a552-4c79-aa3e-203d882286e3
 ---
 
@@ -191,42 +192,42 @@ In addition, make changes to the workbook path, sheet name, and so on, as approp
   
     
     
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
   
     
     
- [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes)
+ [How to: Use the SubCode Property to Capture Error Codes](how-to-use-the-subcode-property-to-capture-error-codes.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md b/docs/general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md
index e231e2ed39..b8ae2f1d25 100644
--- a/docs/general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md
+++ b/docs/general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md
@@ -1,6 +1,7 @@
 ---
 title: How to Use the Content Enrichment web service callout for SharePoint Server
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d4e44498-9a3d-4f2f-b5ba-6ebef9971dcb
 ---
 
@@ -56,7 +57,7 @@ These Windows PowerShell cmdlets enable an administrator to configure the follow
 - A **SendRawData** switch that sends the raw data of an item in binary form. This is useful when more metadata is required than what can be retrieved from the parsed version of the item.
     
   
-In addition, there are options for specifying size limits and timeouts. See  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout) for a full list of configurable properties.
+In addition, there are options for specifying size limits and timeouts. See  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md) for a full list of configurable properties.
   
     
     
@@ -341,10 +342,10 @@ Remove-SPEnterpriseSearchContentEnrichmentConfiguration -SearchApplication $ssa
 -  [Start, pause, resume, or stop a crawl](http://technet.microsoft.com/en-us/library/jj219814%28office.15%29.aspx)
     
   
--  [Configure search in SharePoint](configure-search-in-sharepoint)
+-  [Configure search in SharePoint](configure-search-in-sharepoint.md)
     
   
--  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout)
+-  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md)
     
   
 
diff --git a/docs/general-development/how-to-use-the-subcode-property-to-capture-error-codes.md b/docs/general-development/how-to-use-the-subcode-property-to-capture-error-codes.md
index 4824a74f65..c900e778f1 100644
--- a/docs/general-development/how-to-use-the-subcode-property-to-capture-error-codes.md
+++ b/docs/general-development/how-to-use-the-subcode-property-to-capture-error-codes.md
@@ -1,9 +1,10 @@
 ---
 title: How to Use the SubCode Property to Capture Error Codes
+ms.date: 09/25/2017
 keywords: how to,howdoi,howto,subcode
 f1_keywords:
 - how to,howdoi,howto,subcode
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 8ce4d5b2-111b-49e7-9d07-8c2c586221ec
 ---
 
@@ -22,7 +23,7 @@ The following examples show how to capture the error codes using the  [SubCode](
     
     
 
-For a list of error codes, see  [Excel Services Error Codes](excel-services-error-codes).
+For a list of error codes, see  [Excel Services Error Codes](excel-services-error-codes.md).
 ### To capture error codes when using SOAP
 
 
@@ -362,38 +363,38 @@ In addition, make changes to the workbook path, sheet name, and so on, as approp
   
     
     
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server)
+ [How to: Save from Excel Client to the Server](how-to-save-from-excel-client-to-the-server.md)
 #### Concepts
 
 
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md b/docs/general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md
index c44bc20a88..75c959bdec 100644
--- a/docs/general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md
+++ b/docs/general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md
@@ -1,6 +1,7 @@
 ---
 title: How to Work with user profiles and organization profiles by using the server object model in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 13f16dc3-f652-4fb3-996b-5f2166236d2b
 ---
 
@@ -15,7 +16,7 @@ In SharePoint, user profiles represent SharePoint users. User profile properties
     
 
 > **Note:**
-> For more information about common programming tasks for working with user profiles and the API that you use to perform the tasks, see  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint). 
+> For more information about common programming tasks for working with user profiles and the API that you use to perform the tasks, see  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md). 
   
     
     
@@ -66,11 +67,11 @@ To create a console application that uses the server object model to work with u
   
 6. Replace the contents of the **Program** class with the code example from one of the following scenarios:
     
-  -  [Create a user profile](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj#bkmk_CreateUP)
-  -  [Create a user profile property](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj#bkmk_CreateUPProp)
-  -  [Retrieve and change user profiles](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj#bkmk_GetChangeUP)
-  -  [Retrieve and change attributes for user profile properties](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj#bkmk_GetChangePropAttributes)
-  -  [Retrieve and change values for user properties](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj#bkmk_GetChangePropValues)
+  -  [Create a user profile](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_CreateUP)
+  -  [Create a user profile property](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_CreateUPProp)
+  -  [Retrieve and change user profiles](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_GetChangeUP)
+  -  [Retrieve and change attributes for user profile properties](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_GetChangePropAttributes)
+  -  [Retrieve and change values for user properties](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_GetChangePropValues)
     
   
 7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**. You can check your changes from the **Manage Profile Service** page for the User Profile Service Application in Central Administration.
@@ -498,13 +499,13 @@ namespace UserProfilesSSOM
 <a name="bk_addresources"> </a>
 
 
--  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint)
+-  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md)
     
   
--  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in)
+-  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md)
     
   
--  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in)
+-  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md)
     
   
 -  [Microsoft.Office.Server.UserProfiles](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.aspx)
diff --git a/docs/general-development/how-tos-for-sharepoint.md b/docs/general-development/how-tos-for-sharepoint.md
index 707f760578..feea04182e 100644
--- a/docs/general-development/how-tos-for-sharepoint.md
+++ b/docs/general-development/how-tos-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: How-tos for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ca78b080-0be4-4da4-b112-b86b1bde66e4
 ---
 
@@ -10,7 +11,7 @@ ms.assetid: ca78b080-0be4-4da4-b112-b86b1bde66e4
   
     
     
-![SharePoint](../../images/mod_logo_sharepoint.png)
+![SharePoint](../images/mod_logo_sharepoint.png)
   
     
     
@@ -95,8 +96,8 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Detect the installed SKU of SharePoint](how-to-detect-the-installed-sku-of-sharepoint) <br/> |If the behavior of your solutions depends on the locally installed SKU of SharePoint or Project Server 2013, use the code sample in this article to find the SKU information you need.  <br/> |
-| [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint) <br/> |Learn about the system requirements and configuring a development environment for SharePoint mobility projects.  <br/> |
+| [How to: Detect the installed SKU of SharePoint](how-to-detect-the-installed-sku-of-sharepoint.md) <br/> |If the behavior of your solutions depends on the locally installed SKU of SharePoint or Project Server 2013, use the code sample in this article to find the SKU information you need.  <br/> |
+| [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md) <br/> |Learn about the system requirements and configuring a development environment for SharePoint mobility projects.  <br/> |
    
 
 ## Customization how-tos for SharePoint
@@ -105,9 +106,9 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering) <br/> |Learn how to customize a field type by using the client-side rendering technology in SharePoint.  <br/> |
-| [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps) <br/> |Customize the data queries on which the views in a Windows Phone app are based.  <br/> |
-| [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph) <br/> |Customize the Windows Phone user interface generated by the Windows Phone SharePoint List Application template.  <br/> |
+| [How to: Customize a field type using client-side rendering](how-to-customize-a-field-type-using-client-side-rendering.md) <br/> |Learn how to customize a field type by using the client-side rendering technology in SharePoint.  <br/> |
+| [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md) <br/> |Customize the data queries on which the views in a Windows Phone app are based.  <br/> |
+| [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md) <br/> |Customize the Windows Phone user interface generated by the Windows Phone SharePoint List Application template.  <br/> |
    
 
 ## Building mobile apps how-tos for SharePoint
@@ -116,19 +117,19 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint) <br/> |Learn about the system requirements and configuring a development environment for SharePoint mobility projects.  <br/> |
-| [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app) <br/> |Create a Windows Phone app in Visual Studio based on the Windows Phone SharePoint List Application template.  <br/> |
-| [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone) <br/> |Learn about the Windows Phone application life cycle and storing network data locally.  <br/> |
-| [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s) <br/> |Implement data validation in a Windows Phone app created by using the Windows Phone SharePoint List Application template.  <br/> |
-| [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps) <br/> |Implement data-conversion logic to support SharePoint field types in Windows Phone apps.  <br/> |
-| [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps) <br/> |Customize the data queries on which the views in a Windows Phone app are based.  <br/> |
-| [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph) <br/> |Customize the Windows Phone user interface generated by the Windows Phone SharePoint List Application template.  <br/> |
-| [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app) <br/> |Create Windows Phone apps that use data from multiple SharePoint lists.  <br/> |
-| [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows) <br/> |Create a solution in SharePoint Server for sending push notifications and develop a Windows Phone app for receiving the notifications.  <br/> |
-| [How to: Create a mobile app in SharePoint that contains data from an external data source](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa) <br/> |Learn how to create a simple mobile app in SharePoint that contains data from external data source by using Business Connectivity Services (BCS) and connecting to an external list.  <br/> |
-| [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists) <br/> |Learn how to integrate location information and maps in SharePoint lists and location-based web and mobile SharePoint Add-ins, by using the new Geolocation field, and by creating your own geolocation-based field types.  <br/> |
-| [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res) <br/> |SharePoint introduces the Navigation and Event Logging REST interfaces, enabling you to create a search-driven mobile app for mobile devices such as phones and tablets that run on operating systems other than Windows???for example, Android and iOS.  <br/> |
-| [How to: Export the Name field in a Document Library list to a mobile app](how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app) <br/> |Export the Name field of a Document Library list to a mobile app by using the Visual Studio SharePoint List wizard. The Name field does not appear automatically when a user creates a mobile app for a document library in SharePoint.  <br/> |
+| [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md) <br/> |Learn about the system requirements and configuring a development environment for SharePoint mobility projects.  <br/> |
+| [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md) <br/> |Create a Windows Phone app in Visual Studio based on the Windows Phone SharePoint List Application template.  <br/> |
+| [How to: Store and retrieve SharePoint list items on a Windows Phone](how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md) <br/> |Learn about the Windows Phone application life cycle and storing network data locally.  <br/> |
+| [How to: Implement business logic and data validation in a Windows Phone app for SharePoint](how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md) <br/> |Implement data validation in a Windows Phone app created by using the Windows Phone SharePoint List Application template.  <br/> |
+| [How to: Support and convert SharePoint field types for Windows Phone apps](how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md) <br/> |Implement data-conversion logic to support SharePoint field types in Windows Phone apps.  <br/> |
+| [How to: Customize list item queries and filter data for Windows Phone apps](how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md) <br/> |Customize the data queries on which the views in a Windows Phone app are based.  <br/> |
+| [How to: Customize the user interface of a SharePoint list app for Windows Phone](how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md) <br/> |Customize the Windows Phone user interface generated by the Windows Phone SharePoint List Application template.  <br/> |
+| [How to: Use multiple SharePoint lists in a Windows Phone app](how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md) <br/> |Create Windows Phone apps that use data from multiple SharePoint lists.  <br/> |
+| [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md) <br/> |Create a solution in SharePoint Server for sending push notifications and develop a Windows Phone app for receiving the notifications.  <br/> |
+| [How to: Create a mobile app in SharePoint that contains data from an external data source](how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md) <br/> |Learn how to create a simple mobile app in SharePoint that contains data from external data source by using Business Connectivity Services (BCS) and connecting to an external list.  <br/> |
+| [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md) <br/> |Learn how to integrate location information and maps in SharePoint lists and location-based web and mobile SharePoint Add-ins, by using the new Geolocation field, and by creating your own geolocation-based field types.  <br/> |
+| [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md) <br/> |SharePoint introduces the Navigation and Event Logging REST interfaces, enabling you to create a search-driven mobile app for mobile devices such as phones and tablets that run on operating systems other than Windows???for example, Android and iOS.  <br/> |
+| [How to: Export the Name field in a Document Library list to a mobile app](how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md) <br/> |Export the Name field of a Document Library list to a mobile app by using the Visual Studio SharePoint List wizard. The Name field does not appear automatically when a user creates a mobile app for a document library in SharePoint.  <br/> |
    
 
 ## Building sites using Design Manager how-tos for SharePoint
@@ -138,19 +139,19 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Use code to pin terms to navigation term sets in SharePoint](how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint) <br/> |Learn how to use code to pin terms to navigation term sets.  <br/> |
+| [How to: Use code to pin terms to navigation term sets in SharePoint](how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md) <br/> |Learn how to use code to pin terms to navigation term sets.  <br/> |
 | [Create device channels in SharePoint](http://msdn.microsoft.com/library/339c7dba-95ee-46e0-8c76-0fe1adb6f366.aspx) <br/> |Learn how to create a device channel, change a device channel, delete a device channel, and reorder device channels in SharePoint.  <br/> |
-| [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery) <br/> |Learn how to map a network drive to the Master Page Gallery so that you can use Design Manager to upload design files in SharePoint.  <br/> |
-| [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint) <br/> |With Design Manager, you can convert an .html file into a SharePoint master page, a .master file. After the conversion, the HTML file and master page are associated, so that when you edit and save the HTML file, the changes are synced to the associated master page.  <br/> |
-| [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint) <br/> |Learn how to map a master page to a SharePoint site.  <br/> |
-| [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) <br/> |When you use Design Manager to create a page layout, two files are created: an .aspx file that SharePoint uses, and an HTML version of that page layout that you can edit in your HTML editor. The HTML file and page layout are associated, so that whenever you edit and save the HTML file, your changes are synced to the associated page layout.  <br/> |
-| [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint) <br/> |After you convert an HTML file into a SharePoint master page, or after you create a page layout, you can preview that page in the browser. But before you can preview a master page or page layout, you may have to resolve any issues that prevent the server-side preview from rendering your page.  <br/> |
-| [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager) <br/> |Learn how to set, create, and change the preview page in Design Manager in SharePoint.  <br/> |
-| [How to: Add a Device Channel Panel snippet in SharePoint](how-to-add-a-device-channel-panel-snippet-in-sharepoint) <br/> |A Device Channel Panel is a snippet that you can add to a master page or page layout to control what content is rendered for each channel that you create. The primary purpose of a Device Channel Panel is to selectively display different page fields on different channels from a single page layout.  <br/> |
-| [How to: Add an Edit Mode Panel snippet in SharePoint](how-to-add-an-edit-mode-panel-snippet-in-sharepoint) <br/> |An Edit Mode Panel is a snippet that you can use to display instructions or other content to content authors, who see the contents of that panel only when they edit a page. Conversely, this snippet can also be configured to display its contents only in regular (view) mode instead of in edit mode.  <br/> |
-| [How to: Add a Web Part zone snippet in SharePoint](how-to-add-a-web-part-zone-snippet-in-sharepoint) <br/> |A Web Part zone is a snippet that you can add to a page layout so that content authors can add, edit, or delete Web Parts in that zone.  <br/> |
-| [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint) <br/> |You can use a Security Trim snippet to display content only to specific users, based on a specific permission that those users must have and whether the users are authenticated or anonymous.  <br/> |
-| [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions) <br/> |Learn how to create, edit, or delete image renditions. An image rendition defines the dimensions that are used to display images in SharePoint publishing sites.  <br/> |
+| [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md) <br/> |Learn how to map a network drive to the Master Page Gallery so that you can use Design Manager to upload design files in SharePoint.  <br/> |
+| [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md) <br/> |With Design Manager, you can convert an .html file into a SharePoint master page, a .master file. After the conversion, the HTML file and master page are associated, so that when you edit and save the HTML file, the changes are synced to the associated master page.  <br/> |
+| [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint.md) <br/> |Learn how to map a master page to a SharePoint site.  <br/> |
+| [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) <br/> |When you use Design Manager to create a page layout, two files are created: an .aspx file that SharePoint uses, and an HTML version of that page layout that you can edit in your HTML editor. The HTML file and page layout are associated, so that whenever you edit and save the HTML file, your changes are synced to the associated page layout.  <br/> |
+| [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md) <br/> |After you convert an HTML file into a SharePoint master page, or after you create a page layout, you can preview that page in the browser. But before you can preview a master page or page layout, you may have to resolve any issues that prevent the server-side preview from rendering your page.  <br/> |
+| [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md) <br/> |Learn how to set, create, and change the preview page in Design Manager in SharePoint.  <br/> |
+| [How to: Add a Device Channel Panel snippet in SharePoint](how-to-add-a-device-channel-panel-snippet-in-sharepoint.md) <br/> |A Device Channel Panel is a snippet that you can add to a master page or page layout to control what content is rendered for each channel that you create. The primary purpose of a Device Channel Panel is to selectively display different page fields on different channels from a single page layout.  <br/> |
+| [How to: Add an Edit Mode Panel snippet in SharePoint](how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md) <br/> |An Edit Mode Panel is a snippet that you can use to display instructions or other content to content authors, who see the contents of that panel only when they edit a page. Conversely, this snippet can also be configured to display its contents only in regular (view) mode instead of in edit mode.  <br/> |
+| [How to: Add a Web Part zone snippet in SharePoint](how-to-add-a-web-part-zone-snippet-in-sharepoint.md) <br/> |A Web Part zone is a snippet that you can add to a page layout so that content authors can add, edit, or delete Web Parts in that zone.  <br/> |
+| [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint.md) <br/> |You can use a Security Trim snippet to display content only to specific users, based on a specific permission that those users must have and whether the users are authenticated or anonymous.  <br/> |
+| [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions.md) <br/> |Learn how to create, edit, or delete image renditions. An image rendition defines the dimensions that are used to display images in SharePoint publishing sites.  <br/> |
 | [Add an image rendition to a page in SharePoint](http://msdn.microsoft.com/library/ddf54c98-5ebc-4171-bcbe-927cc982bca5.aspx) <br/> |Learn how to use image renditions in a SharePoint publishing site.  <br/> |
 | [Crop an image rendition in SharePoint](http://msdn.microsoft.com/library/3a6efae9-b18f-4032-b0db-809e611ce9b7.aspx) <br/> |Learn how to specify the portion of the image to use in an image rendition.  <br/> |
    
@@ -162,7 +163,7 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Build and deploy workflow custom actions](how-to-build-and-deploy-workflow-custom-actions) <br/> |Learn how to model business processes whose requirements are not met by the existing library of workflow actions in SharePoint Designer by creating custom workflow actions in SharePoint.  <br/> |
+| [How to: Build and deploy workflow custom actions](how-to-build-and-deploy-workflow-custom-actions.md) <br/> |Learn how to model business processes whose requirements are not met by the existing library of workflow actions in SharePoint Designer by creating custom workflow actions in SharePoint.  <br/> |
    
 
 ## Social and collaboration how-tos for SharePoint
@@ -172,19 +173,19 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Learn to read and write to the social feed by using the .NET client object model in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object) <br/> |Create a console application that reads and writes to the social feed by using the SharePoint .NET client object model.  <br/> |
-| [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s) <br/> |Create a SharePoint-hosted app that uses the REST service to publish a post and get the personal feed for the current user.  <br/> |
-| [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli) <br/> |Learn how to create and delete microblog posts and retrieve social feeds by using the SharePoint .NET client object model.  <br/> |
-| [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr) <br/> |Learn how to create and delete microblog posts and retrieve social feeds by using the SharePoint JavaScript object model.  <br/> |
-| [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep) <br/> |Learn how to add  [SocialDataItem](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialDataItem.aspx) objects to microblog posts, which render as mentions, tags, or links in SharePoint social feeds. <br/> |
-| [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server) <br/> |Learn how to add  [SocialAttachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialAttachment.aspx) objects to microblog posts, which render as embedded pictures, videos, and documents in SharePoint social feeds. <br/> |
-| [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint) <br/> |Learn how to work with Following People features by using the SharePoint .NET client object model.  <br/> |
-| [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint) <br/> |Learn how to work with Following People features by using the SharePoint JavaScript object model.  <br/> |
-| [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep) <br/> |Learn how to work with Following Content features by using the SharePoint .NET client object model.  <br/> |
-| [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2) <br/> |Learn how to work with Following Content features by using the SharePoint REST service.  <br/> |
-| [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in) <br/> |Learn how to retrieve user profile properties programmatically by using the SharePoint .NET client object model.  <br/> |
-| [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in) <br/> |Learn how to retrieve user properties and user profile properties programmatically by using the SharePoint JavaScript object model.  <br/> |
-| [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj) <br/> |Learn how to create, retrieve, and change SharePoint user profiles and user profile properties programmatically by using the SharePoint server object model.  <br/> |
+| [How to: Learn to read and write to the social feed by using the .NET client object model in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md) <br/> |Create a console application that reads and writes to the social feed by using the SharePoint .NET client object model.  <br/> |
+| [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md) <br/> |Create a SharePoint-hosted app that uses the REST service to publish a post and get the personal feed for the current user.  <br/> |
+| [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md) <br/> |Learn how to create and delete microblog posts and retrieve social feeds by using the SharePoint .NET client object model.  <br/> |
+| [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md) <br/> |Learn how to create and delete microblog posts and retrieve social feeds by using the SharePoint JavaScript object model.  <br/> |
+| [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md) <br/> |Learn how to add  [SocialDataItem](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialDataItem.aspx) objects to microblog posts, which render as mentions, tags, or links in SharePoint social feeds. <br/> |
+| [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md) <br/> |Learn how to add  [SocialAttachment](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialAttachment.aspx) objects to microblog posts, which render as embedded pictures, videos, and documents in SharePoint social feeds. <br/> |
+| [How to: Follow people by using the .NET client object model in SharePoint](how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md) <br/> |Learn how to work with Following People features by using the SharePoint .NET client object model.  <br/> |
+| [How to: Follow people by using the JavaScript object model in SharePoint](how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md) <br/> |Learn how to work with Following People features by using the SharePoint JavaScript object model.  <br/> |
+| [How to: Follow documents and sites by using the .NET client object model in SharePoint](how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md) <br/> |Learn how to work with Following Content features by using the SharePoint .NET client object model.  <br/> |
+| [How to: Follow documents, sites, and tags by using the REST service in SharePoint](how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md) <br/> |Learn how to work with Following Content features by using the SharePoint REST service.  <br/> |
+| [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md) <br/> |Learn how to retrieve user profile properties programmatically by using the SharePoint .NET client object model.  <br/> |
+| [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md) <br/> |Learn how to retrieve user properties and user profile properties programmatically by using the SharePoint JavaScript object model.  <br/> |
+| [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md) <br/> |Learn how to create, retrieve, and change SharePoint user profiles and user profile properties programmatically by using the SharePoint server object model.  <br/> |
    
 
 ## Integrating location and map functionality how-tos for SharePoint
@@ -193,9 +194,9 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint) <br/> |Learn how to programmatically add a Geolocation column to a list in SharePoint. Integrate location information and maps in SharePoint lists and location-based websites by using the new Geolocation field creating your own geolocation-based field type.  <br/> |
-| [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint) <br/> |Learn how to set the Bing Maps key programmatically at the web and farm level by using the SharePoint client object model and Windows PowerShell, to enable the Bing Maps functionality in SharePoint lists and location-based web and mobile apps.  <br/> |
-| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering) <br/> |Learn how to customize the SharePoint Geolocation field type programmatically using client-side rendering.  <br/> |
+| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md) <br/> |Learn how to programmatically add a Geolocation column to a list in SharePoint. Integrate location information and maps in SharePoint lists and location-based websites by using the new Geolocation field creating your own geolocation-based field type.  <br/> |
+| [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md) <br/> |Learn how to set the Bing Maps key programmatically at the web and farm level by using the SharePoint client object model and Windows PowerShell, to enable the Bing Maps functionality in SharePoint lists and location-based web and mobile apps.  <br/> |
+| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md) <br/> |Learn how to customize the SharePoint Geolocation field type programmatically using client-side rendering.  <br/> |
    
 
 ## Search how-tos for SharePoint
@@ -205,11 +206,11 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint) <br/> |Learn how to use the search specific properties in the Business Data Connectivity (BDC) service metadata model for crawling associations, and the different user experiences that you can enable.  <br/> |
-| [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint) <br/> |Learn how to modify the BDC model file for a database BCS indexing connector to enable the Search in SharePoint crawler to crawl binary large object (BLOB) data stored in a SQL Server database.  <br/> |
-| [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint) <br/> |Learn how to configure item level security when crawling external data with BCS indexing connectors in SharePoint.  <br/> |
-| [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server) <br/> |Learn how to implement the Content Enrichment web service in SharePoint to modify the managed properties of crawled items before they are indexed.  <br/> |
-| [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results) <br/> |This how-to guides you through the steps to implement???create, deploy, and register???a custom security trimmer for Search in SharePoint by using Visual Studio 2010.  <br/> |
+| [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint.md) <br/> |Learn how to use the search specific properties in the Business Data Connectivity (BDC) service metadata model for crawling associations, and the different user experiences that you can enable.  <br/> |
+| [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint.md) <br/> |Learn how to modify the BDC model file for a database BCS indexing connector to enable the Search in SharePoint crawler to crawl binary large object (BLOB) data stored in a SQL Server database.  <br/> |
+| [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint.md) <br/> |Learn how to configure item level security when crawling external data with BCS indexing connectors in SharePoint.  <br/> |
+| [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md) <br/> |Learn how to implement the Content Enrichment web service in SharePoint to modify the managed properties of crawled items before they are indexed.  <br/> |
+| [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md) <br/> |This how-to guides you through the steps to implement???create, deploy, and register???a custom security trimmer for Search in SharePoint by using Visual Studio 2010.  <br/> |
    
 
 ## BCS how-tos for SharePoint
@@ -218,13 +219,13 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint) <br/> |Learn how to create an external content type for SQL Server in SharePoint.  <br/> |
-| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source and create a reusable external content type for use in BCS in SharePoint.  <br/> |
-| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system) <br/> |Learn how to create an Internet-addressable WCF service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
-| [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint) <br/> |Learn how to create an external list programmatically and bind it to an OData-based external content type in SharePoint.  <br/> |
-| [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint) <br/> |Learn how to create external content types that can be installed, secured, and used in an SharePoint Add-in.  <br/> |
-| [How to: Access external data with REST in SharePoint](how-to-access-external-data-with-rest-in-sharepoint) <br/> |Learn how to access external data from SharePoint by using Representational State Transfer (REST) URLs for BCS.  <br/> |
-| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint) <br/> |Learn how to use the SharePoint client object model to work with BCS objects in SharePoint using browser-based scripting.  <br/> |
+| [How to: Create external content types for SQL Server in SharePoint](how-to-create-external-content-types-for-sql-server-in-sharepoint.md) <br/> |Learn how to create an external content type for SQL Server in SharePoint.  <br/> |
+| [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md) <br/> |Learn how to use Visual Studio 2012 to discover a published OData source and create a reusable external content type for use in BCS in SharePoint.  <br/> |
+| [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md) <br/> |Learn how to create an Internet-addressable WCF service that uses OData to send notifications to SharePoint when the underlying data changes. These notifications are used to trigger events that are attached to external lists.  <br/> |
+| [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md) <br/> |Learn how to create an external list programmatically and bind it to an OData-based external content type in SharePoint.  <br/> |
+| [How to: Create an add-in-scoped external content type in SharePoint](how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md) <br/> |Learn how to create external content types that can be installed, secured, and used in an SharePoint Add-in.  <br/> |
+| [How to: Access external data with REST in SharePoint](how-to-access-external-data-with-rest-in-sharepoint.md) <br/> |Learn how to access external data from SharePoint by using Representational State Transfer (REST) URLs for BCS.  <br/> |
+| [How to: Use the client code library to access external data in SharePoint](how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md) <br/> |Learn how to use the SharePoint client object model to work with BCS objects in SharePoint using browser-based scripting.  <br/> |
    
 
 ## Office and SharePoint application services how-tos for SharePoint
@@ -234,13 +235,13 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint) <br/> |Learn how to create the renderer component in a custom report extension for PerformancePoint Services.  <br/> |
-| [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint) <br/> |Learn how to create the editor component of a custom report extension for PerformancePoint Services.  <br/> |
-| [How to: Create filter data providers for PerformancePoint Services in SharePoint](how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint) <br/> |Learn how to create the data provider component in a custom filter extension for PerformancePoint Services.  <br/> |
-| [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint) <br/> |Learn how to create the editor component of a custom filter extension for PerformancePoint Services.  <br/> |
-| [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha) <br/> |Learn how to create the data source provider component in a custom tabular data source extension for PerformancePoint Services.  <br/> |
-| [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share) <br/> |Learn how to create the editor component of a custom tabular data source extension for PerformancePoint Services.  <br/> |
-| [How to: Create scorecard transforms for PerformancePoint Services in SharePoint](how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2) <br/> |Learn how to create custom scorecard transforms for PerformancePoint Services in SharePoint.  <br/> |
+| [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md) <br/> |Learn how to create the renderer component in a custom report extension for PerformancePoint Services.  <br/> |
+| [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md) <br/> |Learn how to create the editor component of a custom report extension for PerformancePoint Services.  <br/> |
+| [How to: Create filter data providers for PerformancePoint Services in SharePoint](how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md) <br/> |Learn how to create the data provider component in a custom filter extension for PerformancePoint Services.  <br/> |
+| [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md) <br/> |Learn how to create the editor component of a custom filter extension for PerformancePoint Services.  <br/> |
+| [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md) <br/> |Learn how to create the data source provider component in a custom tabular data source extension for PerformancePoint Services.  <br/> |
+| [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md) <br/> |Learn how to create the editor component of a custom tabular data source extension for PerformancePoint Services.  <br/> |
+| [How to: Create scorecard transforms for PerformancePoint Services in SharePoint](how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md) <br/> |Learn how to create custom scorecard transforms for PerformancePoint Services in SharePoint.  <br/> |
    
 
 ## Authentication, authorization, and security how-tos in SharePoint
@@ -250,8 +251,8 @@ Find how-to articles and related code examples that show how to perform basic de
 
 |**Title**|**Summary**|
 |:-----|:-----|
-| [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint) <br/> |Learn how to create and implement a SharePoint claims provider that fulfills the requirements for claims augmentation and claims picking.  <br/> |
-| [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint) <br/> |Learn how to deploy a SharePoint claims provider by using the features infrastructure and creating a class that inherits from  [SPClaimProviderFeatureReceiver](https://msdn.microsoft.com/library/Microsoft.SharePoint.Administration.Claims.SPClaimProviderFeatureReceiver.aspx) . <br/> |
+| [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md) <br/> |Learn how to create and implement a SharePoint claims provider that fulfills the requirements for claims augmentation and claims picking.  <br/> |
+| [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint.md) <br/> |Learn how to deploy a SharePoint claims provider by using the features infrastructure and creating a class that inherits from  [SPClaimProviderFeatureReceiver](https://msdn.microsoft.com/library/Microsoft.SharePoint.Administration.Claims.SPClaimProviderFeatureReceiver.aspx) . <br/> |
    
 
 ## Additional resources
@@ -261,7 +262,7 @@ Find how-to articles and related code examples that show how to perform basic de
 -  [SharePoint general development](http://msdn.microsoft.com/library/fc829689-7cef-469d-a04c-4a433e49828a%28Office.15%29.aspx)
     
   
--  [Code samples for SharePoint](code-samples-for-sharepoint)
+-  [Code samples for SharePoint](code-samples-for-sharepoint.md)
     
   
 -  [SharePoint Dev Center](http://msdn.microsoft.com/en-US/sharepoint)
diff --git a/docs/general-development/incoming-claims-signing-into-sharepoint.md b/docs/general-development/incoming-claims-signing-into-sharepoint.md
index c9476b1b6a..f0d9a1eb5d 100644
--- a/docs/general-development/incoming-claims-signing-into-sharepoint.md
+++ b/docs/general-development/incoming-claims-signing-into-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Incoming claims Signing into SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 08c687aa-e485-4269-aea8-4333da3588a5
 ---
 
@@ -95,16 +96,16 @@ SharePoint Server then does claims augmentation. Win32 clients must support the
 <a name="bk_addresources"> </a>
 
 
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Claims provider in SharePoint](claims-provider-in-sharepoint)
+-  [Claims provider in SharePoint](claims-provider-in-sharepoint.md)
     
   
--  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint)
+-  [How to: Create a claims provider in SharePoint](how-to-create-a-claims-provider-in-sharepoint.md)
     
   
--  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint)
+-  [How to: Deploy a claims provider in SharePoint](how-to-deploy-a-claims-provider-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/integrating-location-and-map-functionality-in-sharepoint.md b/docs/general-development/integrating-location-and-map-functionality-in-sharepoint.md
index 926de86b83..859c96f682 100644
--- a/docs/general-development/integrating-location-and-map-functionality-in-sharepoint.md
+++ b/docs/general-development/integrating-location-and-map-functionality-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Integrating location and map functionality in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 10d4a904-ed27-4513-8c20-d2098aebf22c
 ---
 
@@ -32,7 +33,7 @@ SharePoint introduces a new field type named Geolocation that enables you to ann
   
     
     
-![Default location and map features](../../images/SP15Con_HowToAddGeolocationColumn_fig.png)
+![Default location and map features](../images/SP15Con_HowToAddGeolocationColumn_fig.png)
   
     
     
@@ -58,25 +59,25 @@ The location and map features in SharePoint provide unique opportunities for dev
 
 |**Task**|**Description**|
 |:-----|:-----|
-| [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint) <br/> |SharePoint uses Bings Maps to render the map of the location. To be able to use the Bing Maps feature, you need to create a Bing Maps key and set the key at the web or farm level. The article shows the various ways you can set the key in SharePoint and when to choose which option. You see an error message on the map if you do not use a valid Bing Maps key or if a key is not set at the web that contains the list or at the farm level.  <br/> |
-| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint) <br/> |The Geolocation column is not available in SharePoint lists for users, by default. To add the column to a SharePoint list, you need to write code. In this topic, learn how to add the Geolocation field to a list programmatically.  <br/> |
-| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering) <br/> |You can provide your own rendering to default user interface (UI), logic, and behavior of the Geolocation field by creating custom field types that derive from the Geolocation field. SharePoint simplifies the creation of custom field types by enabling you to run JavaScript by providing a new JSLink property in the Geolocation field class, which points to a custom .js file that renders the field.  <br/> **Note:** The JSLink property is not supported on Survey or Events lists. A SharePoint calendar is an Events list.           |
+| [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md) <br/> |SharePoint uses Bings Maps to render the map of the location. To be able to use the Bing Maps feature, you need to create a Bing Maps key and set the key at the web or farm level. The article shows the various ways you can set the key in SharePoint and when to choose which option. You see an error message on the map if you do not use a valid Bing Maps key or if a key is not set at the web that contains the list or at the farm level.  <br/> |
+| [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md) <br/> |The Geolocation column is not available in SharePoint lists for users, by default. To add the column to a SharePoint list, you need to write code. In this topic, learn how to add the Geolocation field to a list programmatically.  <br/> |
+| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md) <br/> |You can provide your own rendering to default user interface (UI.md), logic, and behavior of the Geolocation field by creating custom field types that derive from the Geolocation field. SharePoint simplifies the creation of custom field types by enabling you to run JavaScript by providing a new JSLink property in the Geolocation field class, which points to a custom .js file that renders the field.  <br/> **Note:** The JSLink property is not supported on Survey or Events lists. A SharePoint calendar is an Events list.           |
    
 
 ## Additional resources
 <a name="SP15Integrateloc_addlresources"> </a>
 
 
--  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint)
+-  [How to: Add a Geolocation column to a list programmatically in SharePoint](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md)
     
   
--  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint)
+-  [How to: Set the Bing Maps key at the web and farm level in SharePoint](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md)
     
   
--  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering)
+-  [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md)
     
   
--  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists)
+-  [How to: Integrate maps with Windows Phone apps and SharePoint lists](how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md)
     
   
 -  [Use the SharePoint location field type in mobile applications](http://technet.microsoft.com/en-us/library/fp161355%28v=office.15%29.aspx)
diff --git a/docs/general-development/javascript-user-defined-functions-overview.md b/docs/general-development/javascript-user-defined-functions-overview.md
index e4d9f4e749..50ccd86272 100644
--- a/docs/general-development/javascript-user-defined-functions-overview.md
+++ b/docs/general-development/javascript-user-defined-functions-overview.md
@@ -1,6 +1,7 @@
 ---
 title: JavaScript user-defined functions overview
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: fee38837-1985-4319-ba4e-b99c6ec66336
 ---
 
@@ -14,7 +15,7 @@ A user-defined function (UDF) is a function that you can create yourself and the
   
     
     
-Excel Services already allows you to create UDFs using managed code, so if you have worked with the existing Excel Services UDFs, JavaScript UDFs should look familiar to you. For more information about creating UDFs using managed code, see  [Excel Services User-Defined Functions](excel-services-user-defined-functions).
+Excel Services already allows you to create UDFs using managed code, so if you have worked with the existing Excel Services UDFs, JavaScript UDFs should look familiar to you. For more information about creating UDFs using managed code, see  [Excel Services User-Defined Functions](excel-services-user-defined-functions.md).
   
     
     
@@ -80,7 +81,7 @@ You could then call the JavaScript UDF, StockInfo, in a formula from a cell insi
   
     
     
-![JavaScript UDF being invoked in Excel Online](../../images/SPS15CON_xls_JsUdfinWebApp.jpg)
+![JavaScript UDF being invoked in Excel Online](../images/SPS15CON_xls_JsUdfinWebApp.jpg)
   
     
     
@@ -116,7 +117,7 @@ You can create and use JavaScript UDFs either on workbooks displayed in SharePoi
 <a name="bk_addresources"> </a>
 
 
--  [Excel Services in SharePoint](excel-services-in-sharepoint)
+-  [Excel Services in SharePoint](excel-services-in-sharepoint.md)
     
   
 -  [What's new in Excel Services for developers](http://msdn.microsoft.com/library/09e96c8b-cb55-4fd1-a797-b50fbf0f9296.aspx)
diff --git a/docs/general-development/keyword-query-language-kql-syntax-reference.md b/docs/general-development/keyword-query-language-kql-syntax-reference.md
index 9026531a05..d5ab11e442 100644
--- a/docs/general-development/keyword-query-language-kql-syntax-reference.md
+++ b/docs/general-development/keyword-query-language-kql-syntax-reference.md
@@ -1,6 +1,7 @@
----
+---
 title: Keyword Query Language (KQL) syntax reference
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d8489f59-522f-433c-b9c1-69e597be51c7
 ---
 
@@ -594,7 +595,7 @@ The **XRANK** operator's dynamic ranking calculation is based on this formula:
   
     
     
-![Formula for XRANK operator](../../images/XRANKFormula.gif)
+![Formula for XRANK operator](../images/XRANKFormula.gif)
   
     
     
@@ -688,6 +689,6 @@ You can combine different parts of a keyword query by using the opening parenthe
 <a name="SP15KQL_addlresources"> </a>
 
 
--  [Building search queries in SharePoint](building-search-queries-in-sharepoint)
+-  [Building search queries in SharePoint](building-search-queries-in-sharepoint.md)
     
   
diff --git a/docs/general-development/language-support-for-windows-phone-in-sharepoint.md b/docs/general-development/language-support-for-windows-phone-in-sharepoint.md
index ba69b7455e..49b57c0a01 100644
--- a/docs/general-development/language-support-for-windows-phone-in-sharepoint.md
+++ b/docs/general-development/language-support-for-windows-phone-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Language support for Windows Phone in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2c396a91-0fc1-4e25-942b-fffad49bd2c6
 ---
 
@@ -13,12 +14,12 @@ To develop your mobile application for more than one language, you need to globa
     
 
 The Windows Phone SDK includes Visual Studio 2010 Express for Windows Phone, Windows Phone Emulator, XNA Game Studio, and Expression Blend. To get started, install the  [Windows Phone SDK 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=27570) for Windows Phone development. Then install the [Microsoft SharePoint SDK for Windows Phone 7.1](http://www.microsoft.com/en-us/download/details.aspx?id=30476) to install the SharePoint templates for Windows Phone.
-After you set up your development environment and install the SharePoint SDK for Windows Phone, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint).
+After you set up your development environment and install the SharePoint SDK for Windows Phone, see  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md).
   
     
     
 
-For more information about the SharePoint templates for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio).
+For more information about the SharePoint templates for Windows Phone, see  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md).
 ## Templates and libraries installed by the SharePoint SDK for Windows Phone
 <a name="LanguageSupportForWindowsPhoneForSharePoint2013_TemplatesInstalledBySharePointSDKForWindowsPhone"> </a>
 
@@ -117,10 +118,10 @@ Although you have programmatic access to nine languages, you can run your ShareP
 <a name="bk_addresources"> </a>
 
 
--  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio)
+-  [Overview of Windows Phone SharePoint application templates in Visual Studio](overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md)
     
   
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/loop-back-soap-calls-and-direct-linking.md b/docs/general-development/loop-back-soap-calls-and-direct-linking.md
index 00f9ccc364..430456b10c 100644
--- a/docs/general-development/loop-back-soap-calls-and-direct-linking.md
+++ b/docs/general-development/loop-back-soap-calls-and-direct-linking.md
@@ -1,6 +1,7 @@
 ---
 title: Loop-Back SOAP Calls and Direct Linking
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bffc6565-636f-40d4-ba17-2511070ba5db
 ---
 
@@ -54,19 +55,19 @@ To link directly to Microsoft.Office.Excel.Server.WebServices.dll in your projec
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/machine-translation-services-in-sharepoint.md b/docs/general-development/machine-translation-services-in-sharepoint.md
index 620bb69df3..790ac3035d 100644
--- a/docs/general-development/machine-translation-services-in-sharepoint.md
+++ b/docs/general-development/machine-translation-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Machine Translation Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 15a81428-da94-40b8-8ed4-6a12f05661e2
 ---
 
@@ -66,7 +67,7 @@ Using the server object model, you can submit requests to the Machine Translatio
   
     
     
-![Related code snippets and sample apps](../../images/mod_icon_links_samples.png)
+![Related code snippets and sample apps](../images/mod_icon_links_samples.png)
   
     
     
@@ -270,7 +271,7 @@ For the .NET managed CSOM, get a **ClientContext** instance (located in the **Mi
   
     
     
-![Related code snippets and sample apps](../../images/mod_icon_links_samples.png)
+![Related code snippets and sample apps](../images/mod_icon_links_samples.png)
   
     
     
@@ -286,7 +287,7 @@ For the Silverlight CSOM, get a **ClientContext** instance (located in the **Mic
   
     
     
-![Related code snippets and sample apps](../../images/mod_icon_links_samples.png)
+![Related code snippets and sample apps](../images/mod_icon_links_samples.png)
   
     
     
@@ -488,7 +489,7 @@ For the JavaScript CSOM, get an **SP.ClientContext** instance, and then use the
   
     
     
-![Related code snippets and sample apps](../../images/mod_icon_links_samples.png)
+![Related code snippets and sample apps](../images/mod_icon_links_samples.png)
   
     
     
@@ -801,7 +802,7 @@ SharePoint Machine Translation Service uses the paragraph language as the Source
 <a name="TranslationSvc_AR"> </a>
 
 
--  [Office 2013 and SharePoint application services](office-and-sharepoint-application-services)
+-  [Office 2013 and SharePoint application services](office-and-sharepoint-application-services.md)
     
   
 
diff --git a/docs/general-development/managed-metadata-and-navigation-in-sharepoint.md b/docs/general-development/managed-metadata-and-navigation-in-sharepoint.md
index 135b8dbd78..b1f3ab45aa 100644
--- a/docs/general-development/managed-metadata-and-navigation-in-sharepoint.md
+++ b/docs/general-development/managed-metadata-and-navigation-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Managed metadata and navigation in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b66d4ec1-a2ef-49cc-8ca5-a6b516bff02e
 ---
 
@@ -10,7 +11,7 @@ ms.assetid: b66d4ec1-a2ef-49cc-8ca5-a6b516bff02e
   
     
     
-![Conceptual overview topic](../../images/mod_icon_badge_conoverview.png)
+![Conceptual overview topic](../images/mod_icon_badge_conoverview.png)
   
     
     
@@ -164,7 +165,7 @@ You can use the following code examples to complete basic operations with the ta
 ## Pinning
 <a name="SP15_ManagedMetadataAndNav_Pinning"> </a>
 
-In Microsoft SharePoint Server 2010, users could reuse terms (and all terms nested under the reused terms) in other locations in the term hierarchy. After these terms were reused, they could be modified and changes would be seen everywhere the terms were reused. SharePoint introduces term pinning. A pinned term is just like a term that is reused, except it is read only and cannot be changed in the locations where the term is reused. For an example, see  [How to: Use code to pin terms to navigation term sets in SharePoint](how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint).
+In Microsoft SharePoint Server 2010, users could reuse terms (and all terms nested under the reused terms) in other locations in the term hierarchy. After these terms were reused, they could be modified and changes would be seen everywhere the terms were reused. SharePoint introduces term pinning. A pinned term is just like a term that is reused, except it is read only and cannot be changed in the locations where the term is reused. For an example, see  [How to: Use code to pin terms to navigation term sets in SharePoint](how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md).
   
     
     
@@ -234,10 +235,10 @@ A term store manager can enhance and expand term usage models based on more flex
 <a name="SP15_ManagedMetadataAndNav_AdditionalResources"> </a>
 
 
--  [Managed navigation in SharePoint](managed-navigation-in-sharepoint)
+-  [Managed navigation in SharePoint](managed-navigation-in-sharepoint.md)
     
   
--  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint)
+-  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/managed-navigation-in-sharepoint.md b/docs/general-development/managed-navigation-in-sharepoint.md
index b7cb5b396b..ea333e9908 100644
--- a/docs/general-development/managed-navigation-in-sharepoint.md
+++ b/docs/general-development/managed-navigation-in-sharepoint.md
@@ -1,10 +1,16 @@
+---
+title: Managed navigation in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Managed navigation in SharePoint
 
   
     
     
-![Conceptual overview topic](../../images/mod_icon_badge_conoverview.png)
+![Conceptual overview topic](../images/mod_icon_badge_conoverview.png)
   
     
     
@@ -244,7 +250,7 @@ using (SPSite site = new SPSite(TestConfig.ServerUrl))
 <a name="SP15_ManagedNav_AdditionalResources"> </a>
 
 
--  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint)
+-  [Content Search Web Part in SharePoint](content-search-web-part-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md b/docs/general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md
index e686966cde..dcefdf90e2 100644
--- a/docs/general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md
+++ b/docs/general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Master pages, the Master Page Gallery, and page layouts in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 80b9a360-bc2e-46c6-b0ca-1bc487b73db6
 ---
 
@@ -13,31 +14,31 @@ Design Manager is a feature in SharePoint that makes it easier to create a fully
     
 
 For more information about using Design Manager to work with master pages, page layouts, and display templates, see the following articles:
--  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery) : Learn how to map a network drive so that you can work with design files in your SharePoint site as if they were local files.
+-  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md) : Learn how to map a network drive so that you can work with design files in your SharePoint site as if they were local files.
     
   
--  [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint) : Learn how to map a master page to a SharePoint site.
+-  [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint.md) : Learn how to map a master page to a SharePoint site.
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint) : Learn how to create a page layout.
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md) : Learn how to create a page layout.
     
   
--  [How to: Customize page layouts for a catalog-based site in SharePoint](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint) : Learn how to create and customize category page and catalog-item page layouts for a SharePoint cross-site publishing site.
+-  [How to: Customize page layouts for a catalog-based site in SharePoint](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md) : Learn how to create and customize category page and catalog-item page layouts for a SharePoint cross-site publishing site.
     
   
--  [How to: Apply styles to page fields in SharePoint](how-to-apply-styles-to-page-fields-in-sharepoint) : In a page layout, you can apply styles to a page field, and those styles are applied to any content added by content authors when they create a page from that page layout. Also, you have further options to control how content in a RichHtmlField page field is styled.
+-  [How to: Apply styles to page fields in SharePoint](how-to-apply-styles-to-page-fields-in-sharepoint.md) : In a page layout, you can apply styles to a page field, and those styles are applied to any content added by content authors when they create a page from that page layout. Also, you have further options to control how content in a RichHtmlField page field is styled.
     
   
--  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint) : When you use Design Manager to see a live preview of a master page or page layout, you may need to resolve some common preview errors.
+-  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md) : When you use Design Manager to see a live preview of a master page or page layout, you may need to resolve some common preview errors.
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint) : Learn how to create a master page by converting a typical HTML file into the .master file required by SharePoint.
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md) : Learn how to create a master page by converting a typical HTML file into the .master file required by SharePoint.
     
   
--  [How to: Create a minimal master page in SharePoint](how-to-create-a-minimal-master-page-in-sharepoint) : A minimal master page contains only those page elements that are required by SharePointto render the page correctly in the browser. With Design Manager, you can quickly create a minimal master page without first having to design and convert an HTML file.
+-  [How to: Create a minimal master page in SharePoint](how-to-create-a-minimal-master-page-in-sharepoint.md) : A minimal master page contains only those page elements that are required by SharePointto render the page correctly in the browser. With Design Manager, you can quickly create a minimal master page without first having to design and convert an HTML file.
     
   
--  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager) : Learn how to set, create, and change the preview page in Design Manager in SharePoint.
+-  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md) : Learn how to set, create, and change the preview page in Design Manager in SharePoint.
     
   
 
@@ -45,16 +46,16 @@ For more information about using Design Manager to work with master pages, page
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates)
+-  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
 
diff --git a/docs/general-development/matching-the-sharepoint-designer-version-with-the-farm-version.md b/docs/general-development/matching-the-sharepoint-designer-version-with-the-farm-version.md
index 906766d36f..14e79f2ae8 100644
--- a/docs/general-development/matching-the-sharepoint-designer-version-with-the-farm-version.md
+++ b/docs/general-development/matching-the-sharepoint-designer-version-with-the-farm-version.md
@@ -1,6 +1,7 @@
 ---
 title: Matching the SharePoint Designer version with the farm version
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6ea44d3f-0b05-43d4-99ae-98886b6909f0
 ---
 
@@ -16,7 +17,7 @@ SharePoint Designer is tool used to connect to and work with a SharePoint site.
     
 
 > **Note:**
-> The latest version of the product is SharePoint Designer 2013. To learn how to find and install SharePoint Designer 2013, see  [Creating a workflow by using SharePoint Designer 2013 and the SharePoint Workflow platform](creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo). If you already have an older version of SharePoint Designer installed on your computer we recommend that you uninstall it before installing the new version. 
+> The latest version of the product is SharePoint Designer 2013. To learn how to find and install SharePoint Designer 2013, see  [Creating a workflow by using SharePoint Designer 2013 and the SharePoint Workflow platform](creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md). If you already have an older version of SharePoint Designer installed on your computer we recommend that you uninstall it before installing the new version. 
   
     
     
@@ -40,7 +41,7 @@ Trying to use a version of SharePoint Designer that does not match with the Shar
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/minimal-download-strategy-overview.md b/docs/general-development/minimal-download-strategy-overview.md
index e355a23b28..280eea7d75 100644
--- a/docs/general-development/minimal-download-strategy-overview.md
+++ b/docs/general-development/minimal-download-strategy-overview.md
@@ -1,3 +1,9 @@
+---
+title: Minimal Download Strategy overview
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Minimal Download Strategy overview
 Learn about Minimal Download Strategy (MDS), a new feature in SharePoint that reduces page load time by sending only the differences when users navigate to a new page.
@@ -16,7 +22,7 @@ Minimal Download Strategy (MDS) is a new technology in SharePoint that reduces t
   
     
     
-![Page processed with MDS](../../images/MDS_UpdateSections.png)
+![Page processed with MDS](../images/MDS_UpdateSections.png)
   
     
     
@@ -104,7 +110,7 @@ The basic mechanics of MDS are pretty simple. The main components of MDS are two
   
     
     
-![MDS flow when a user navigates the site](../../images/MDS_GeneralFlow.png)
+![MDS flow when a user navigates the site](../images/MDS_GeneralFlow.png)
   
     
     
@@ -204,10 +210,10 @@ Thanks to the failover mechanism, your controls work seamlessly whether or not M
 -  [EnableMinimalDownload](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Web.EnableMinimalDownload.aspx)
     
   
--  [Modify SharePoint components for MDS](modify-sharepoint-components-for-mds)
+-  [Modify SharePoint components for MDS](modify-sharepoint-components-for-mds.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/modify-sharepoint-components-for-mds.md b/docs/general-development/modify-sharepoint-components-for-mds.md
index 24a02e2393..50da850fc6 100644
--- a/docs/general-development/modify-sharepoint-components-for-mds.md
+++ b/docs/general-development/modify-sharepoint-components-for-mds.md
@@ -1,13 +1,14 @@
 ---
 title: Modify SharePoint components for MDS
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c967be7c-f29f-481a-9ce2-915ead315dcd
 ---
 
 
 # Modify SharePoint components for MDS
 Learn how to modify the components in your SharePoint project to take advantage of Minimal Download Strategy (MDS) in SharePoint.
-Minimal Download Strategy (MDS) improves the user experience by returning from the server only the portions of a page required to render it properly in the browser. Because the fully-rendered page is not returned to the client, the server must be able to accurately identify the portions that are required to render the page. You might need to modify the components in your SharePoint project so that they are identified as MDS-compliant and can work with the MDS engine. Learn more about MDS in  [Minimal Download Strategy overview](minimal-download-strategy-overview).
+Minimal Download Strategy (MDS) improves the user experience by returning from the server only the portions of a page required to render it properly in the browser. Because the fully-rendered page is not returned to the client, the server must be able to accurately identify the portions that are required to render the page. You might need to modify the components in your SharePoint project so that they are identified as MDS-compliant and can work with the MDS engine. Learn more about MDS in  [Minimal Download Strategy overview](minimal-download-strategy-overview.md).
   
     
     
@@ -16,7 +17,7 @@ Minimal Download Strategy (MDS) improves the user experience by returning from t
 ## Why modify SharePoint components?
 <a name="bk_whymodify"> </a>
 
-As explained in  [Minimal Download Strategy overview](minimal-download-strategy-overview), SharePoint controls work whether or not you modify them to take full advantage of MDS. However, when your components are not MDS compliant, the MDS engine issues a failover. In a failover, the MDS engine takes an extra round trip to redirect the browser to the full version of the new page, which takes time. Users have the best experience when you modify components to work with MDS and avoid a failover every time they browse to a new page in SharePoint. You usually need to modify master pages, ASP.NET pages, controls, and Web Parts. 
+As explained in  [Minimal Download Strategy overview](minimal-download-strategy-overview.md), SharePoint controls work whether or not you modify them to take full advantage of MDS. However, when your components are not MDS compliant, the MDS engine issues a failover. In a failover, the MDS engine takes an extra round trip to redirect the browser to the full version of the new page, which takes time. Users have the best experience when you modify components to work with MDS and avoid a failover every time they browse to a new page in SharePoint. You usually need to modify master pages, ASP.NET pages, controls, and Web Parts. 
   
     
     
@@ -42,7 +43,7 @@ The master page provides a template that lets MDS identify the content regions t
   
     
     
-![Components that require updates in master page](../../images/MDS_SeattleMaster.png)
+![Components that require updates in master page](../images/MDS_SeattleMaster.png)
   
     
     
@@ -250,10 +251,10 @@ Your controls and Web Parts can also use XSLT files to control the rendering pro
 <a name="bk_addresources"> </a>
 
 
--  [Minimal Download Strategy overview](minimal-download-strategy-overview)
+-  [Minimal Download Strategy overview](minimal-download-strategy-overview.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/office-and-sharepoint-application-services.md b/docs/general-development/office-and-sharepoint-application-services.md
index 5f6294b761..b7e0a99bc6 100644
--- a/docs/general-development/office-and-sharepoint-application-services.md
+++ b/docs/general-development/office-and-sharepoint-application-services.md
@@ -1,6 +1,7 @@
 ---
 title: Office 2013 and SharePoint application services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f962922c-2967-492f-9a89-5ad10a1a6dd3
 ---
 
@@ -66,13 +67,13 @@ Use the links in Table 2 to learn more about developing with the Office and Shar
 
 |**Service**|**Description**|
 |:-----|:-----|
-|Access Services  <br/> See  [Develop Access web apps](develop-access-web-apps) <br/> |Enables users to create, deploy, and manage collaborative web-based Access applications.  <br/> |
-|Excel Services  <br/> See  [Excel Services in SharePoint](excel-services-in-sharepoint) <br/> |Enables users to load, calculate, and display Excel workbooks on SharePoint sites.  <br/> |
-|Machine Translation Service  <br/> See  [Machine Translation Services in SharePoint](machine-translation-services-in-sharepoint) <br/> |Provides automatic machine translation of sites, documents, and sites.  <br/> |
-|PerformancePoint Services  <br/> See  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint) <br/> |Creates and publishes dashboards that contain interactive data visualizations (such as scorecards and reports) that enable people to monitor and analyze their business performance.  <br/> |
-|PowerPoint Automation Services  <br/>  [PowerPoint Automation Services in SharePoint](powerpoint-automation-services-in-sharepoint) <br/> |Provides unattended, server-side conversion of PowerPoint presentations into other formats.  <br/> |
-|Visio Services  <br/> See  [Visio Services in SharePoint](visio-services-in-sharepoint) <br/> |Enables users to view and interact with Visio drawings stored on SharePoint sites.  <br/> |
-|Word Automation Services  <br/> See  [What's new in Word Automation Services for developers](what-s-new-in-word-automation-services-for-developers) <br/> |Provides unattended, server-side conversion of documents that are supported by Word.  <br/> |
+|Access Services  <br/> See  [Develop Access web apps](develop-access-web-apps.md) <br/> |Enables users to create, deploy, and manage collaborative web-based Access applications.  <br/> |
+|Excel Services  <br/> See  [Excel Services in SharePoint](excel-services-in-sharepoint.md) <br/> |Enables users to load, calculate, and display Excel workbooks on SharePoint sites.  <br/> |
+|Machine Translation Service  <br/> See  [Machine Translation Services in SharePoint](machine-translation-services-in-sharepoint.md) <br/> |Provides automatic machine translation of sites, documents, and sites.  <br/> |
+|PerformancePoint Services  <br/> See  [PerformancePoint Services in SharePoint](performancepoint-services-in-sharepoint.md) <br/> |Creates and publishes dashboards that contain interactive data visualizations (such as scorecards and reports.md) that enable people to monitor and analyze their business performance.  <br/> |
+|PowerPoint Automation Services  <br/>  [PowerPoint Automation Services in SharePoint](powerpoint-automation-services-in-sharepoint.md) <br/> |Provides unattended, server-side conversion of PowerPoint presentations into other formats.  <br/> |
+|Visio Services  <br/> See  [Visio Services in SharePoint](visio-services-in-sharepoint.md) <br/> |Enables users to view and interact with Visio drawings stored on SharePoint sites.  <br/> |
+|Word Automation Services  <br/> See  [What's new in Word Automation Services for developers](what-s-new-in-word-automation-services-for-developers.md) <br/> |Provides unattended, server-side conversion of documents that are supported by Word.  <br/> |
    
 Not all services and scenarios are represented in this section. For links to developer documentation for other services, see  [Additional resources](#bkmk_Resources).
   
@@ -83,13 +84,13 @@ Not all services and scenarios are represented in this section. For links to dev
 <a name="bkmk_Resources"> </a>
 
 
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
 -  [Install SQL Server BI Features with SharePoint (PowerPivot and Reporting Services)](http://msdn.microsoft.com/en-us/library/hh231671)
diff --git a/docs/general-development/office-documentation-copyright-notice.md b/docs/general-development/office-documentation-copyright-notice.md
index e63b88f5a4..39d7bcac96 100644
--- a/docs/general-development/office-documentation-copyright-notice.md
+++ b/docs/general-development/office-documentation-copyright-notice.md
@@ -1,6 +1,7 @@
 ---
 title: Office 2013 documentation copyright notice
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a9c2f3d9-cea2-49a3-b709-40dc614b9f86
 ---
 
diff --git a/docs/general-development/optimize-page-performance-in-sharepoint.md b/docs/general-development/optimize-page-performance-in-sharepoint.md
index e2b0ecfd0d..04b803505b 100644
--- a/docs/general-development/optimize-page-performance-in-sharepoint.md
+++ b/docs/general-development/optimize-page-performance-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Optimize page performance in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 262caeef-64fd-4e02-b947-d772faf01159
 ---
 
@@ -49,7 +50,7 @@ Both AJAX and MDS are technologies that request only sections of the page to min
   
     
     
-![MDS architecture](../../images/OptimizePage_Fig01_MDSArchitecture.png)
+![MDS architecture](../images/OptimizePage_Fig01_MDSArchitecture.png)
   
     
     
@@ -67,7 +68,7 @@ The MDS framework assumes that a master page defines a chrome and content region
   
     
     
-![Page chrome and regions in a SharePoint page](../../images/OptimizePage_Fig02_PageStructure.png)
+![Page chrome and regions in a SharePoint page](../images/OptimizePage_Fig02_PageStructure.png)
   
     
     
@@ -446,7 +447,7 @@ You should categorize page optimization techniques into one of two categories: f
 - Use consolidated images and files; for example, combine multiple CSS files into one. Combine images into an image strip or cluster.
     
   
-- Use compression (crunch) techniques. For more information, see  [Compress (crunch) JavaScript and CSS files](optimize-page-performance-in-sharepoint#OptimizingPagePerformance_Crunch).
+- Use compression (crunch) techniques. For more information, see  [Compress (crunch) JavaScript and CSS files](optimize-page-performance-in-sharepoint.md#OptimizingPagePerformance_Crunch).
     
   
 - Verify that you are referencing the production version of common JavaScript libraries, such as jQuery, instead of the debug versions.
@@ -589,7 +590,7 @@ You should minimize the number of images in your site. To help with that effort,
   
     
     
-![Single image file that contains multiple images](../../images/OptimizePage_Fig03_SingleImage.png)
+![Single image file that contains multiple images](../images/OptimizePage_Fig03_SingleImage.png)
   
     
     
@@ -607,7 +608,7 @@ Figure 4 shows how the image file is subsequently changed to display as individu
   
     
     
-![Multiple images displayed in a table](../../images/OptimizePage_Fig04_ImageTable.png)
+![Multiple images displayed in a table](../images/OptimizePage_Fig04_ImageTable.png)
   
     
     
@@ -772,7 +773,7 @@ Figure 5 shows the Developer Dashboard.
   
     
     
-![Developer dashboard](../../images/OptimizePage_Fig05_DevDashboard.png)
+![Developer dashboard](../images/OptimizePage_Fig05_DevDashboard.png)
   
     
     
@@ -793,15 +794,15 @@ Much of the guidance for SharePoint 2010 page performance optimization applies t
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions)
+-  [SharePoint Design Manager image renditions](sharepoint-design-manager-image-renditions.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
diff --git a/docs/general-development/optimize-sharepoint-site-accessibility.md b/docs/general-development/optimize-sharepoint-site-accessibility.md
index efa9dd96b8..a812dc8cd8 100644
--- a/docs/general-development/optimize-sharepoint-site-accessibility.md
+++ b/docs/general-development/optimize-sharepoint-site-accessibility.md
@@ -1,6 +1,7 @@
 ---
 title: Optimize SharePoint site accessibility
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0a3fbfb3-1a0b-4902-9317-525cf2f63d98
 ---
 
@@ -38,10 +39,10 @@ Alternative text is required for screen readers to read non-text content on the
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Accessibility in SharePoint](accessibility-in-sharepoint)
+-  [Accessibility in SharePoint](accessibility-in-sharepoint.md)
     
   
 -  [Microsoft Accessibility](https://www.microsoft.com/enable)
diff --git a/docs/general-development/overview-of-design-manager-in-sharepoint.md b/docs/general-development/overview-of-design-manager-in-sharepoint.md
index 9ed32b5022..7d767c1808 100644
--- a/docs/general-development/overview-of-design-manager-in-sharepoint.md
+++ b/docs/general-development/overview-of-design-manager-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Overview of Design Manager in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 29834b3f-3815-4347-91d3-296387663114
 ---
 
@@ -27,7 +28,7 @@ At a high level, the designer will perform the following tasks:
     
     
 
-- Understand core SharePoint design concepts. For more information, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model).
+- Understand core SharePoint design concepts. For more information, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md).
     
   
 - Create a mock-up of the design in HTML and CSS. Creating the design is a core skill of a web designer, and is not covered in this article.
@@ -116,7 +117,7 @@ After you map a network drive, you can upload your design to SharePoint simply b
   
     
     
-For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
   
     
     
@@ -186,7 +187,7 @@ After you convert your master page and successfully preview it, you are ready to
   
 3. Preview and style snippets by using CSS.
     
-For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+For more information, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
     
   
 
@@ -266,7 +267,7 @@ When you design a page layout, your basic task is to position and style the page
   
     
     
-For more information, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint).
+For more information, see  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md).
   
     
     
@@ -319,13 +320,13 @@ A design package is a .wsp file, a SharePoint solution file, which is basically
 <a name="Additional"> </a>
 
 
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service.md b/docs/general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service.md
index 535848d121..df18c679f6 100644
--- a/docs/general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service.md
+++ b/docs/general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service.md
@@ -1,6 +1,7 @@
 ---
 title: Overview of SharePoint and the Volume Shadow Copy Service
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d1cb6653-bfc0-4af2-b221-d7d30cb40d84
 ---
 
@@ -23,7 +24,7 @@ The following figure shows the main components in the system: Microsoft Windows
   
     
     
-![SharePoint to VSS Relationships](../../images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif)
+![SharePoint to VSS Relationships](../images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif)
   
     
     
@@ -46,7 +47,7 @@ During a recovery, the backup/restore application instructs the SPF-VSS Writer t
 
     
 > **Note:**
-> See "Restoring" in  [VSS requestors and SharePoint](vss-requestors-and-sharepoint) for important information about restorations.
+> See "Restoring" in  [VSS requestors and SharePoint](vss-requestors-and-sharepoint.md) for important information about restorations.
   
     
     
@@ -95,19 +96,19 @@ The following is the high-level sequence of events during backup or restore oper
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint VSS Writer](sharepoint-vss-writer)
+-  [SharePoint VSS Writer](sharepoint-vss-writer.md)
     
   
--  [VSS requestors and SharePoint](vss-requestors-and-sharepoint)
+-  [VSS requestors and SharePoint](vss-requestors-and-sharepoint.md)
     
   
--  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint)
+-  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint.md)
     
   
--  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor)
+-  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md)
     
   
--  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using)
+-  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md)
     
   
 -  [Starting and Configuring the WSS Writer Service](http://msdn.microsoft.com/library/c9243dd6-e61e-4783-9fef-48d0122f1c09.aspx)
diff --git a/docs/general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md b/docs/general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md
index a95d9e89d5..987b9bad34 100644
--- a/docs/general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md
+++ b/docs/general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md
@@ -1,6 +1,7 @@
 ---
 title: Overview of the SharePoint mobile client authentication object model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 00ee657f-a32a-495e-80b4-83ac0f60df44
 ---
 
@@ -16,7 +17,7 @@ The process of authenticating a SharePoint user on a Windows Phone 7.5 is a litt
     
 
 > **Note:**
-> For more information about the APIs that are discussed in this section, see  [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model). For more information about the SharePoint client object model for Silverlight, see  [Managed Client Object Model](http://msdn.microsoft.com/en-us/library/ee537247.aspx) and [Using the Silverlight Object Model](http://msdn.microsoft.com/en-us/library/ee538971.aspx). 
+> For more information about the APIs that are discussed in this section, see  [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model.md). For more information about the SharePoint client object model for Silverlight, see  [Managed Client Object Model](http://msdn.microsoft.com/en-us/library/ee537247.aspx) and [Using the Silverlight Object Model](http://msdn.microsoft.com/en-us/library/ee538971.aspx). 
   
     
     
@@ -106,7 +107,7 @@ If the SharePoint URL has basic or forms-based authentication support, the **Exe
   
     
     
-![SharePointClientAuthentication](../../images/SP15Con_SharePointClientAuthenticationFig1.png)
+![SharePointClientAuthentication](../images/SP15Con_SharePointClientAuthenticationFig1.png)
   
     
     
@@ -304,7 +305,7 @@ ClientContext ctx = new ClientContext("SiteUrl");
 ## Cookie caching
 <a name="SP15Mobileclientauth_cookie"> </a>
 
-The **Authenticator** class also includes members that you can use to enable and manage caching of cookies or credentials or both. For information about these members of the **Authenticator** class and their uses, see [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model).
+The **Authenticator** class also includes members that you can use to enable and manage caching of cookies or credentials or both. For information about these members of the **Authenticator** class and their uses, see [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model.md).
   
     
     
@@ -313,10 +314,10 @@ The **Authenticator** class also includes members that you can use to enable and
 <a name="SP15Mobileclientauth_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model)
+-  [Overview of the SharePoint mobile object model](overview-of-the-sharepoint-mobile-object-model.md)
     
   
 
diff --git a/docs/general-development/overview-of-the-sharepoint-mobile-object-model.md b/docs/general-development/overview-of-the-sharepoint-mobile-object-model.md
index 2872daa76a..9197fb3d11 100644
--- a/docs/general-development/overview-of-the-sharepoint-mobile-object-model.md
+++ b/docs/general-development/overview-of-the-sharepoint-mobile-object-model.md
@@ -1,6 +1,7 @@
 ---
 title: Overview of the SharePoint mobile object model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 72319846-d02d-49e7-b830-48eb8f5715cb
 ---
 
@@ -2268,16 +2269,16 @@ public string MessageId
 <a name="SP15MobileOM_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows)
+-  [How to: Configure and use push notifications in SharePoint apps for Windows Phone](how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md)
     
   
--  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint)
+-  [Integrating location and map functionality in SharePoint](integrating-location-and-map-functionality-in-sharepoint.md)
     
   
--  [Overview of the SharePoint mobile client authentication object model](overview-of-the-sharepoint-mobile-client-authentication-object-model)
+-  [Overview of the SharePoint mobile client authentication object model](overview-of-the-sharepoint-mobile-client-authentication-object-model.md)
     
   
 
diff --git a/docs/general-development/overview-of-the-sharepoint-page-model.md b/docs/general-development/overview-of-the-sharepoint-page-model.md
index 0b707e8689..a2f4aba406 100644
--- a/docs/general-development/overview-of-the-sharepoint-page-model.md
+++ b/docs/general-development/overview-of-the-sharepoint-page-model.md
@@ -1,6 +1,7 @@
----
+---
 title: Overview of the SharePoint page model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 808b1af3-89ab-4f02-89cc-ea86cb1f9a6e
 ---
 
@@ -42,7 +43,7 @@ SharePoint uses templates to define and render the pages that a site displays. T
   
     
     
-![Master page, page layout, and page](../../images/101_page_model_overview.gif)
+![Master page, page layout, and page](../images/101_page_model_overview.gif)
   
     
     
@@ -63,7 +64,7 @@ A master page defines the chrome (the shared framing elements) of your site. The
   
     
     
-![Master page](../../images/102_master_page.gif)
+![Master page](../images/102_master_page.gif)
   
     
     
@@ -81,7 +82,7 @@ A master page also defines regions called content placeholders that are filled i
   
     
     
-![Master page with page layout outlined](../../images/103_master_page_with_page_layout_outlined.gif)
+![Master page with page layout outlined](../images/103_master_page_with_page_layout_outlined.gif)
   
     
     
@@ -99,7 +100,7 @@ When you preview a master page in Design Manager, you see the following message.
   
     
     
-![Master page preview message](../../images/104_master_page_preview_message.gif)
+![Master page preview message](../images/104_master_page_preview_message.gif)
   
     
     
@@ -128,7 +129,7 @@ A page layout is a template for a specific type of page in your site, such as an
   
     
     
-![Page layout](../../images/105_page_layout.gif)
+![Page layout](../images/105_page_layout.gif)
   
     
     
@@ -146,7 +147,7 @@ Page layouts define regions or content areas that map to content placeholders on
   
     
     
-![Content region and content placeholder](../../images/106_content_region_and_content_placeholder.gif)
+![Content region and content placeholder](../images/106_content_region_and_content_placeholder.gif)
   
     
     
@@ -179,7 +180,7 @@ With a page field control, you can define the styles used by the content. Author
   
     
     
-![Page layout with page field controls](../../images/107_page_layout_with_page_fields.gif)
+![Page layout with page field controls](../images/107_page_layout_with_page_fields.gif)
   
     
     
@@ -204,7 +205,7 @@ Together, a master page and a page layout create a content page.
   
     
     
-![Master page with page layout](../../images/108_master_page_with_page_layout.gif)
+![Master page with page layout](../images/108_master_page_with_page_layout.gif)
   
     
     
@@ -222,7 +223,7 @@ The master page defines the chrome for all pages in the site so, often many page
   
     
     
-![One master page tied to three page layouts](../../images/109_one_master_many_layouts.gif)
+![One master page tied to three page layouts](../images/109_one_master_many_layouts.gif)
   
     
     
@@ -251,7 +252,7 @@ Authors can create pages and add content to the page fields, and they can add We
   
     
     
-![Page with authored content](../../images/110_page_with_authored_content.gif)
+![Page with authored content](../images/110_page_with_authored_content.gif)
   
     
     
@@ -269,7 +270,7 @@ The rendered page is what site visitors see. When a page is requested by the bro
   
     
     
-![Rendered page in browser](../../images/111_rendered_page.gif)
+![Rendered page in browser](../images/111_rendered_page.gif)
   
     
     
@@ -283,7 +284,7 @@ The rendered page is what site visitors see. When a page is requested by the bro
   
     
     
-![Master page, page layout, and page](../../images/112_master_plus_layout_plus_page.gif)
+![Master page, page layout, and page](../images/112_master_plus_layout_plus_page.gif)
   
     
     
@@ -343,7 +344,7 @@ In the search-driven pages scenario, a SharePoint page contains these main eleme
   
     
     
-![Master page, page layout, and page with Web Part](../../images/113_114_master_and_layout_and_page_and_web_part_closeup.gif)
+![Master page, page layout, and page with Web Part](../images/113_114_master_and_layout_and_page_and_web_part_closeup.gif)
   
     
     
@@ -368,7 +369,7 @@ SharePoint includes several ready-to-use display templates such as lists and sli
   
     
     
-![Tool pane of Content Search Web Part](../../images/115_content_search_web_part_tool_pane.gif)
+![Tool pane of Content Search Web Part](../images/115_content_search_web_part_tool_pane.gif)
   
     
     
@@ -386,7 +387,7 @@ Content Search Web Parts use two types of display templates, control and item. A
   
     
     
-![Two diagrams of Content Search Web Parts](../../images/116_117_control_templates_1_and_2.gif)
+![Two diagrams of Content Search Web Parts](../images/116_117_control_templates_1_and_2.gif)
   
     
     
@@ -419,7 +420,7 @@ The control template also includes functionality common to all the search result
   
     
     
-![Control template outlined on Web Part and webpage](../../images/118_119_control_template_outlined_on_web_part_and_page.gif)
+![Control template outlined on Web Part and webpage](../images/118_119_control_template_outlined_on_web_part_and_page.gif)
   
     
     
@@ -452,7 +453,7 @@ The item display template also determines which managed properties and values ar
   
     
     
-![Item templates outlined on Web Part and webpage](../../images/120_121_item_templates_outlined_on_web_part_and_page.gif)
+![Item templates outlined on Web Part and webpage](../images/120_121_item_templates_outlined_on_web_part_and_page.gif)
   
     
     
@@ -510,7 +511,7 @@ When you create a device channel, you specify the user agent substrings for the
   
     
     
-![Two device channels with separate master pages](../../images/122_123_two_channels_two_master_pages.gif)
+![Two device channels with separate master pages](../images/122_123_two_channels_two_master_pages.gif)
   
     
     
@@ -539,7 +540,7 @@ This is one of the primary benefits of device channels: the design changes (the
   
     
     
-![One page layout working with two master pages](../../images/124_one_layout_many_masters.gif)
+![One page layout working with two master pages](../images/124_one_layout_many_masters.gif)
   
     
     
@@ -572,7 +573,7 @@ Perhaps the most common scenario for using channel panels is to selectively incl
   
     
     
-![Page layout with channel panels](../../images/125_126_page_layout_with_channel_panels.gif)
+![Page layout with channel panels](../images/125_126_page_layout_with_channel_panels.gif)
   
     
     
@@ -594,7 +595,7 @@ Or, you can use a channel panel inside the item display template of a Content Se
   
     
     
-![Page layout and item templates with channel panels](../../images/127_128_item_display_templates_with_channel_panel.gif)
+![Page layout and item templates with channel panels](../images/127_128_item_display_templates_with_channel_panel.gif)
   
     
     
@@ -611,16 +612,16 @@ Or, you can use a channel panel inside the item display template of a Content Se
 <a name="bk_AdditionalResources"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates)
+-  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates.md)
     
   
--  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels)
+-  [SharePoint Design Manager device channels](sharepoint-design-manager-device-channels.md)
     
   
 
diff --git a/docs/general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md b/docs/general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md
index ee13993201..04257eab34 100644
--- a/docs/general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md
+++ b/docs/general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md
@@ -1,6 +1,7 @@
----
+---
 title: Overview of Windows Phone SharePoint application templates in Visual Studio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6ae27957-fa41-4e6f-92e3-db11dae1f6c2
 ---
 
@@ -76,7 +77,7 @@ If you create a Visual Studio project based on the Windows Phone Empty SharePoin
   
     
     
-![Windows Phone Empty SharePoint Application project](../../images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG)
+![Windows Phone Empty SharePoint Application project](../images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG)
   
     
     
@@ -116,7 +117,7 @@ The files generated for a Visual Studio project using the Windows Phone SharePoi
   
     
     
-![Windows Phone SharePoint List Application project](../../images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif)
+![Windows Phone SharePoint List Application project](../images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif)
   
     
     
@@ -146,7 +147,7 @@ The project files for are described in Table 1.
 |ListViewModel.cs  <br/> |Serves as the data source for the List.xaml file.  <br/> |
 |NewItemViewModel.cs  <br/> |Serves as the data source for the NewForm.xaml file. You write code in this file to validate data entered by users when adding a new list item.  <br/> |
    
-For the details of the steps involved in creating a Windows Phone app by using the Windows Phone SharePoint List Application template, see  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app).
+For the details of the steps involved in creating a Windows Phone app by using the Windows Phone SharePoint List Application template, see  [How to: Create a Windows Phone SharePoint list app](how-to-create-a-windows-phone-sharepoint-list-app.md).
   
     
     
@@ -155,10 +156,10 @@ For the details of the steps involved in creating a Windows Phone app by using t
 <a name="SP15winphoneover_addlresources"> </a>
 
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint)
+-  [How to: Set up an environment for developing mobile apps for SharePoint](how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md)
     
   
 -  [Windows Phone SDK 8.0](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
diff --git a/docs/general-development/performancepoint-services-in-sharepoint.md b/docs/general-development/performancepoint-services-in-sharepoint.md
index fb106e454c..84e0c0429f 100644
--- a/docs/general-development/performancepoint-services-in-sharepoint.md
+++ b/docs/general-development/performancepoint-services-in-sharepoint.md
@@ -1,9 +1,10 @@
 ---
 title: PerformancePoint Services in SharePoint
+ms.date: 09/25/2017
 keywords: accessing fco definitions in SharePoint,bi in SharePoint using performancepoint services,business intelligence in SharePoint,business intelligence using performancepoint services in SharePoint,create scorecard transforms using performancepoint in SharePoint,custom filter control in SharePoint,custom performancepoint extensions,customize performancepoint in sharepoint,data source creation in SharePoint,dlls used for performancepoint development,extending performancepoint services for sharepoint,fcos in sharepoint performancepoint,filter creation in SharePoint,filters as fcos in pps performancepoint,getting started with performancepoint services,integration of performancepoint services in sharepoint,performancepoint assemblies used in development,performancepoint custom data sources,performancepoint custom filters,performancepoint custom reports,performancepoint custom scorecard transforms,performancepoint development scenarios,performancepoint services development,performancepoint services development scenarios,performancepoint services programming,performancepoint services sdk,pps custom dashboards in SharePoint,pps development,pps programming,pps sdk,report creation in SharePoint,report renderer in SharePoint,SharePoint service application PerformancePoint
 f1_keywords:
 - accessing fco definitions in SharePoint,bi in SharePoint using performancepoint services,business intelligence in SharePoint,business intelligence using performancepoint services in SharePoint,create scorecard transforms using performancepoint in SharePoint,custom filter control in SharePoint,custom performancepoint extensions,customize performancepoint in sharepoint,data source creation in SharePoint,dlls used for performancepoint development,extending performancepoint services for sharepoint,fcos in sharepoint performancepoint,filter creation in SharePoint,filters as fcos in pps performancepoint,getting started with performancepoint services,integration of performancepoint services in sharepoint,performancepoint assemblies used in development,performancepoint custom data sources,performancepoint custom filters,performancepoint custom reports,performancepoint custom scorecard transforms,performancepoint development scenarios,performancepoint services development,performancepoint services development scenarios,performancepoint services programming,performancepoint services sdk,pps custom dashboards in SharePoint,pps development,pps programming,pps sdk,report creation in SharePoint,report renderer in SharePoint,SharePoint service application PerformancePoint
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: fb159708-d6b4-40c1-b5cc-4bb2071a7930
 ---
 
@@ -48,13 +49,13 @@ For more information, see the following topics about creating renderers and prov
     
     
 
--  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint)
+-  [How to: Create report renderers for PerformancePoint Services in SharePoint](how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md)
     
   
--  [How to: Create filter data providers for PerformancePoint Services in SharePoint](how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint)
+-  [How to: Create filter data providers for PerformancePoint Services in SharePoint](how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md)
     
   
--  [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha)
+-  [How to: Create tabular data source providers for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md)
     
   
 
@@ -69,13 +70,13 @@ For more information about creating editors, see the following topics:
     
     
 
--  [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint)
+-  [How to: Create report editors for PerformancePoint Services in SharePoint](how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md)
     
   
--  [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint)
+-  [How to: Create filter editors for PerformancePoint Services in SharePoint](how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md)
     
   
--  [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share)
+-  [How to: Create tabular data source editors for PerformancePoint Services in SharePoint](how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md)
     
   
 
@@ -108,7 +109,7 @@ Transforms change the appearance, contents, or functionality of scorecards befor
   
     
     
-For more information about scorecard transforms, see  [How to: Create scorecard transforms for PerformancePoint Services in SharePoint](how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2).
+For more information about scorecard transforms, see  [How to: Create scorecard transforms for PerformancePoint Services in SharePoint](how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md).
   
     
     
@@ -137,7 +138,7 @@ Supported extensions run within a PerformancePoint Services application instance
   
     
     
-![PerformancePoint Services extensibility points](../../images/SPS14_PerfPoint_ArchOverview.gif)
+![PerformancePoint Services extensibility points](../images/SPS14_PerfPoint_ArchOverview.gif)
   
     
     
diff --git a/docs/general-development/powerpoint-automation-services-in-sharepoint.md b/docs/general-development/powerpoint-automation-services-in-sharepoint.md
index a68153705a..842eb5f706 100644
--- a/docs/general-development/powerpoint-automation-services-in-sharepoint.md
+++ b/docs/general-development/powerpoint-automation-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: PowerPoint Automation Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 168c7dc0-fbdc-41a2-84db-65d211d3d673
 ---
 
diff --git a/docs/general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md b/docs/general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md
index a072c37d7b..87e113236b 100644
--- a/docs/general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md
+++ b/docs/general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md
@@ -1,6 +1,7 @@
 ---
 title: Prepare to set up and configure a SharePoint workflow development environment
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b6a3321f-4131-4a8e-9cb7-7a1b4ab9e26b
 ---
 
@@ -26,7 +27,7 @@ Although workflows have been a part of SharePoint since early versions, workflow
 - SharePoint workflows integrate with the new app model, which means you can now implement workflows in SharePoint Add-ins.
     
   
-- You can also develop SharePoint workflows using SharePoint Designer 2013. For more information, see  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio).
+- You can also develop SharePoint workflows using SharePoint Designer 2013. For more information, see  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md).
     
   
 
@@ -42,8 +43,8 @@ First off, get acquainted with the new app model and the concepts underlying Sha
 | [SharePoint for developers](http://msdn.microsoft.com/en-us/sharepoint) <br/> |Portal to the SharePoint developer site, where the emphasis is on apps for SharePoint.  <br/> |
 | [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx) <br/> |Learn what apps for SharePoint are, why you should build them, and the concepts that are fundamental to building them in SharePoint.  <br/> |
 | [New name for apps for SharePoint](http://msdn.microsoft.com/library/05b07b04-6c8b-4b7e-bd86-e32c589dfead%28Office.15%29.aspx) <br/> |Portal to a developer site devoted to building apps for Office and apps for SharePoint.  <br/> |
-| [SharePoint development overview](sharepoint-development-overview) <br/> |SharePoint is a development platform for apps for SharePoint and farm solutions. Get acquainted with the capabilities and features of SharePoint to start your development.  <br/> |
-| [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals) <br/> |Provides a high-level overview of the workflow infrastructure in SharePoint, including a view of the platform architecture and the workflow interop bridge.  <br/> |
+| [SharePoint development overview](sharepoint-development-overview.md) <br/> |SharePoint is a development platform for apps for SharePoint and farm solutions. Get acquainted with the capabilities and features of SharePoint to start your development.  <br/> |
+| [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md) <br/> |Provides a high-level overview of the workflow infrastructure in SharePoint, including a view of the platform architecture and the workflow interop bridge.  <br/> |
    
 Your next step is to ensure that you have an up-to-date workflow development environment installed. You don't need to develop on the SharePoint server machine, but of course you do need a SharePoint Server installation to develop against.
   
@@ -136,13 +137,13 @@ Here is a summary of changes that require you to update your workflow projects:
 -  [Set up an on-premises development environment for SharePoint Add-ins](http://msdn.microsoft.com/library/b0878c12-27c9-4eea-ae3b-7e79e5a8838d%28Office.15%29.aspx)
     
   
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/programming-models-in-sharepoint.md b/docs/general-development/programming-models-in-sharepoint.md
index 0b00e923d1..f5a8737817 100644
--- a/docs/general-development/programming-models-in-sharepoint.md
+++ b/docs/general-development/programming-models-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Programming models in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 061985ec-6129-4e91-991b-a72488ce1d34
 ---
 
@@ -37,7 +38,7 @@ A SharePoint Add-in is similar to an add-in on a mobile device. It is a stand-al
   
     
     
-For an introduction to the model for SharePoint Add-ins, see  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx). For more information, see  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions), and  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+For an introduction to the model for SharePoint Add-ins, see  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx). For more information, see  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md), and  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -45,7 +46,7 @@ For an introduction to the model for SharePoint Add-ins, see  [SharePoint Add-in
 ## SharePoint publishing sites
 <a name="ECM"> </a>
 
-SharePoint publishing sites provide large-scale content publishing with a high degree of maintainability and regulation compliance. They also provide management of documents, records, taxonomy, and content types. For more information, see  [Build sites for SharePoint](build-sites-for-sharepoint).
+SharePoint publishing sites provide large-scale content publishing with a high degree of maintainability and regulation compliance. They also provide management of documents, records, taxonomy, and content types. For more information, see  [Build sites for SharePoint](build-sites-for-sharepoint.md).
   
     
     
@@ -53,7 +54,7 @@ SharePoint publishing sites provide large-scale content publishing with a high d
 ## SharePoint farm solutions
 <a name="Solutions"> </a>
 
-SharePoint farm solutions are trusted SharePoint extensions whose custom logic calls the SharePoint server object model and runs with full trust on the SharePoint servers. These solutions are primarily for custom administrative extensions of SharePoint, such as timer jobs, custom Windows PowerShell commands, and extensions of Central Administration. Farm solutions are distributed as SharePoint solution packages that farm administrators upload to a farm-wide storage location from which they can be deployed. Components in farm solutions can have farm, web application, site collection, or website scope. For more information, see  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint).
+SharePoint farm solutions are trusted SharePoint extensions whose custom logic calls the SharePoint server object model and runs with full trust on the SharePoint servers. These solutions are primarily for custom administrative extensions of SharePoint, such as timer jobs, custom Windows PowerShell commands, and extensions of Central Administration. Farm solutions are distributed as SharePoint solution packages that farm administrators upload to a farm-wide storage location from which they can be deployed. Components in farm solutions can have farm, web application, site collection, or website scope. For more information, see  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint.md).
   
     
     
@@ -61,7 +62,7 @@ SharePoint farm solutions are trusted SharePoint extensions whose custom logic c
 ## Mobile add-ins for SharePoint
 <a name="Mobile"> </a>
 
-Windows Phone apps, and apps built on non-Microsoft mobile platforms, can access SharePoint websites and data. Tools for building Windows Phone apps that interact with SharePoint are available for installation on Visual Studio 2010 and Visual Studio 2012. A SharePoint client managed API just for use on Windows Phone devices is available. Mobile devices, including non-Microsoft devices, can also access SharePoint data through SharePoint REST/OData endpoints. For more information, see  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint).
+Windows Phone apps, and apps built on non-Microsoft mobile platforms, can access SharePoint websites and data. Tools for building Windows Phone apps that interact with SharePoint are available for installation on Visual Studio 2010 and Visual Studio 2012. A SharePoint client managed API just for use on Windows Phone devices is available. Mobile devices, including non-Microsoft devices, can also access SharePoint data through SharePoint REST/OData endpoints. For more information, see  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md).
   
     
     
@@ -69,7 +70,7 @@ Windows Phone apps, and apps built on non-Microsoft mobile platforms, can access
 ## Reusable components for SharePoint
 <a name="Reuse"> </a>
 
-The SharePoint platform and Visual Studio 2012 enable encapsulation and reuse of application elements, including elements created with code, script, and XML markup. For more information, see  [Build reusable components for SharePoint](build-reusable-components-for-sharepoint).
+The SharePoint platform and Visual Studio 2012 enable encapsulation and reuse of application elements, including elements created with code, script, and XML markup. For more information, see  [Build reusable components for SharePoint](build-reusable-components-for-sharepoint.md).
   
     
     
@@ -78,16 +79,16 @@ The SharePoint platform and Visual Studio 2012 enable encapsulation and reuse of
 <a name="Reuse"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint)
+-  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint.md)
     
   
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [Build reusable components for SharePoint](build-reusable-components-for-sharepoint)
+-  [Build reusable components for SharePoint](build-reusable-components-for-sharepoint.md)
     
   
 
@@ -95,12 +96,12 @@ The SharePoint platform and Visual Studio 2012 enable encapsulation and reuse of
 <a name="SP15devinSP_addlresources"> </a>
 
 
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Accessibility in SharePoint](accessibility-in-sharepoint)
+-  [Accessibility in SharePoint](accessibility-in-sharepoint.md)
     
   
diff --git a/docs/general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md b/docs/general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md
index efccadf4c1..74de3c1e2f 100644
--- a/docs/general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md
+++ b/docs/general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md
@@ -1,6 +1,7 @@
 ---
 title: Protocol handler error due to deprecated interface in SharePoint 2016
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c80cb77c-89db-4c78-b576-f63d39ca330a
 ---
 
diff --git a/docs/general-development/publish-sharepoint-sites.md b/docs/general-development/publish-sharepoint-sites.md
index fef2e5ddd4..66cd49e301 100644
--- a/docs/general-development/publish-sharepoint-sites.md
+++ b/docs/general-development/publish-sharepoint-sites.md
@@ -1,6 +1,7 @@
----
+---
 title: Publish SharePoint sites
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 46b5a79c-962f-4a07-8316-d5005eabd0e0
 ---
 
@@ -15,7 +16,7 @@ After you design or develop site components and content, you can deploy them to
 
 ## Cross-site publishing
 
-Learn about  [cross-site publishing](cross-site-publishing-in-sharepoint) and how it affects how you plan and publish sites and their content and associated design elements.
+Learn about  [cross-site publishing](cross-site-publishing-in-sharepoint.md) and how it affects how you plan and publish sites and their content and associated design elements.
   
     
     
@@ -55,10 +56,10 @@ Different markets have different tastes. The variations feature helps accommodat
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
 
diff --git a/docs/general-development/query-refinement-in-sharepoint.md b/docs/general-development/query-refinement-in-sharepoint.md
index f37bf581cc..2e6f1ff6c2 100644
--- a/docs/general-development/query-refinement-in-sharepoint.md
+++ b/docs/general-development/query-refinement-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Query Refinement in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ec31782e-1bc5-4dc3-8df7-c29cd5f7f05c
 ---
 
diff --git a/docs/general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md b/docs/general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md
index 3c813ecc21..a060754d24 100644
--- a/docs/general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md
+++ b/docs/general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md
@@ -1,6 +1,7 @@
----
+---
 title: Reference threads and digest threads in SharePoint social feeds
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 58e68fb2-ba40-4861-912f-355e119a1c41
 ---
 
@@ -83,7 +84,7 @@ To optimize performance, when a thread contains more than two replies, the serve
 <a name="bk_addresources"> </a>
 
 
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
 -  [SocialThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialThread.aspx) in the .NET client object model
diff --git a/docs/general-development/removing-excel-interactive-view-from-a-webpage.md b/docs/general-development/removing-excel-interactive-view-from-a-webpage.md
index bd3e606ad2..98b7aadc9f 100644
--- a/docs/general-development/removing-excel-interactive-view-from-a-webpage.md
+++ b/docs/general-development/removing-excel-interactive-view-from-a-webpage.md
@@ -1,6 +1,7 @@
 ---
 title: Removing Excel Interactive View from a webpage
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 407b3aa3-7286-462b-905f-811a3b7f3f1c
 ---
 
@@ -39,7 +40,7 @@ We encourage you to  [embed Excel into your web pages ](https://support.office.c
 <a name="bk_addresources"> </a>
 
 
--  [Excel Services in SharePoint](excel-services-in-sharepoint)
+-  [Excel Services in SharePoint](excel-services-in-sharepoint.md)
     
   
 -  [Embed an Excel workbook on your blog](https://support.office.com/en-au/article/Share-it-Embed-an-Excel-workbook-on-your-blog-804e1845-5662-487e-9b38-f96307144081?ui=en-US&amp;rs=en-AU&amp;ad=AU)
diff --git a/docs/general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md b/docs/general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md
index 3859f50ac9..16d0783b1b 100644
--- a/docs/general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md
+++ b/docs/general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md
@@ -1,6 +1,7 @@
 ---
 title: Requesting Excel workbook data from SharePoint Server using OData
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2f846e96-6c9e-4ed2-9602-4081ad0ab135
 ---
 
@@ -87,7 +88,7 @@ The Excel Services implementation of OData supports a number of the standard ODa
 <a name="xlsAdditionalResources"> </a>
 
 
--  [Using OData with Excel Services REST in SharePoint](using-odata-with-excel-services-rest-in-sharepoint)
+-  [Using OData with Excel Services REST in SharePoint](using-odata-with-excel-services-rest-in-sharepoint.md)
     
   
 -  [What's new in Excel Services for developers](http://msdn.microsoft.com/library/09e96c8b-cb55-4fd1-a797-b50fbf0f9296.aspx)
diff --git a/docs/general-development/resources-uri-for-excel-services-rest-api.md b/docs/general-development/resources-uri-for-excel-services-rest-api.md
index 2c8f568e06..445b4864b3 100644
--- a/docs/general-development/resources-uri-for-excel-services-rest-api.md
+++ b/docs/general-development/resources-uri-for-excel-services-rest-api.md
@@ -1,6 +1,7 @@
 ---
 title: Resources URI for Excel Services REST API
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 79f95305-ec9e-4842-b937-85f66ced98e4
 ---
 
@@ -110,4 +111,4 @@ Table 1 shows all the accessible resources in the Excel Services REST API. To ac
   
     
     
- [Basic URI Structure and Path](basic-uri-structure-and-path)
+ [Basic URI Structure and Path](basic-uri-structure-and-path.md)
diff --git a/docs/general-development/retrieving-query-suggestions-using-the-search-rest-service.md b/docs/general-development/retrieving-query-suggestions-using-the-search-rest-service.md
index c09bdc6e05..bff0f4c19c 100644
--- a/docs/general-development/retrieving-query-suggestions-using-the-search-rest-service.md
+++ b/docs/general-development/retrieving-query-suggestions-using-the-search-rest-service.md
@@ -1,6 +1,7 @@
 ---
 title: Retrieving query suggestions using the Search REST service
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a64c5bec-64a8-4752-9c72-433d1c864aed
 ---
 
@@ -232,16 +233,16 @@ http:// _server_/_api/search/suggest?querytext='sharepoint'&amp;fprefixmatchallt
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview)
+-  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview.md)
     
   
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
 -  [SharePoint: Using the search REST service from an app for SharePoint](http://code.msdn.microsoft.com/sharepoint/SharePoint-Perform-a-1bf3e87d)
     
   
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
 -  [Use OData query operations in SharePoint REST requests](http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
diff --git a/docs/general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md b/docs/general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md
index db76fcaf52..3fba6a44ec 100644
--- a/docs/general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md
+++ b/docs/general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md
@@ -1,3 +1,9 @@
+---
+title: Role, inheritance, elevation of privilege, and password changes in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Role, inheritance, elevation of privilege, and password changes in SharePoint
 
@@ -208,19 +214,19 @@ For more information about the managed account API, see the following links:
 <a name="SP15_RoleInheritance_AdditionalResources"> </a>
 
 
--  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint)
+-  [Authentication, authorization, and security in SharePoint](authentication-authorization-and-security-in-sharepoint.md)
     
   
--  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint)
+-  [Authorization, users, groups, and the object model in SharePoint](authorization-users-groups-and-the-object-model-in-sharepoint.md)
     
   
--  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint)
+-  [Claims-based identity in SharePoint](claims-based-identity-in-sharepoint.md)
     
   
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
--  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint)
+-  [Configuration, administration, and resources in SharePoint](configuration-administration-and-resources-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint.md b/docs/general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint.md
index 53292fae6f..1a3a05ee37 100644
--- a/docs/general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint.md
+++ b/docs/general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint.md
@@ -1,3 +1,9 @@
+---
+title: Sample delegation, federation, and authentication scenario in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Sample delegation, federation, and authentication scenario in SharePoint
 This article provides sample scenarios for identity delegation and identity federation.
@@ -48,7 +54,7 @@ Figure 1 shows a typical identity delegation scenario in which a Fabrikam employ
   
     
     
-![Claims identity delegation scenario](../../images/44928b39-5683-4bce-8ddf-31d886243b87.gif)
+![Claims identity delegation scenario](../images/44928b39-5683-4bce-8ddf-31d886243b87.gif)
   
     
     
@@ -110,7 +116,7 @@ Federated authentication allows a security token service (STS) in one trust doma
   
     
     
-![Claims federation authentication](../../images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif)
+![Claims federation authentication](../images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif)
   
     
     
@@ -147,7 +153,7 @@ This scenario describes a sign-on experience for a partner employee when she tri
   
     
     
-![Claims federation scenario](../../images/903d3109-d567-4156-a44f-29793c42ae45.gif)
+![Claims federation scenario](../images/903d3109-d567-4156-a44f-29793c42ae45.gif)
   
     
     
@@ -190,10 +196,10 @@ As shown in Figure 3, the flow in this scenario is:
 <a name="SP15_SampleDelegation_AdditionalResources"> </a>
 
 
--  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint)
+-  [Claims-based identity and concepts in SharePoint](claims-based-identity-and-concepts-in-sharepoint.md)
     
   
--  [Claims-based identity term definitions](claims-based-identity-term-definitions)
+-  [Claims-based identity term definitions](claims-based-identity-term-definitions.md)
     
   
 
diff --git a/docs/general-development/sample-uri-for-excel-services-rest-api.md b/docs/general-development/sample-uri-for-excel-services-rest-api.md
index a99aa22ec4..f557bd9c21 100644
--- a/docs/general-development/sample-uri-for-excel-services-rest-api.md
+++ b/docs/general-development/sample-uri-for-excel-services-rest-api.md
@@ -1,6 +1,7 @@
 ---
 title: Sample URI For Excel Services REST API
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4ebe1da2-9861-416f-bef1-4a62599efe2e
 ---
 
diff --git a/docs/general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md b/docs/general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md
index 4155998c70..f6ea022f70 100644
--- a/docs/general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md
+++ b/docs/general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md
@@ -1,6 +1,7 @@
----
+---
 title: Save, download, and upload a SharePoint site as a template
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2e637172-ddac-4a70-bd77-55a1645a3db1
 ---
 
@@ -57,7 +58,7 @@ Most of the objects in a site are included and supported by the template. Howeve
 - **Unsupported** Customized permissions, running workflow instances, list item version history, workflow tasks associated with running workflows, people or group field values, taxonomy field values, publishing pages and publishing sites, My Sites, stapled features, SharePoint Add-ins, and remote event receivers.
     
     > **Note:**
-      > For publishing sites, you can use site definition templates. For more information, see  [Additional resources](save-download-and-upload-a-sharepoint-site-as-a-template#bkmk_additionalresources) at the end of this topic.
+      > For publishing sites, you can use site definition templates. For more information, see  [Additional resources](save-download-and-upload-a-sharepoint-site-as-a-template.md#bkmk_additionalresources) at the end of this topic.
 
 ### What can you do with SharePoint templates?
 
diff --git a/docs/general-development/search-add-ins-in-sharepoint.md b/docs/general-development/search-add-ins-in-sharepoint.md
index 91bb959c76..bbf07a1b2f 100644
--- a/docs/general-development/search-add-ins-in-sharepoint.md
+++ b/docs/general-development/search-add-ins-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Search add-ins in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 21682e45-dd78-4f3c-8f1e-cdd48de3bde2
 ---
 
@@ -48,7 +49,7 @@ To create a search add-in, use one of these two environments:
 - Napa Office 365 Development Tools
     
   
-With Visual Studio 2013 and later, you can publish your search add-ins to both on-premises or in Office 365. For more information about the development environments and how to use them to create search add-ins, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+With Visual Studio 2013 and later, you can publish your search add-ins to both on-premises or in Office 365. For more information about the development environments and how to use them to create search add-ins, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -175,7 +176,7 @@ Search add-ins send query requests to the Search service application (SSA), and
   
     
     
-![Search app permission configuration with VS](../../images/SP15_search_apps_permission_Visual_Studio.PNG)
+![Search app permission configuration with VS](../images/SP15_search_apps_permission_Visual_Studio.PNG)
   
     
     
@@ -197,7 +198,7 @@ Search add-ins send query requests to the Search service application (SSA), and
   
     
     
-![Search app permission configuration through Napa](../../images/SP15_search_app_permission_Napa.gif)
+![Search app permission configuration through Napa](../images/SP15_search_app_permission_Napa.gif)
   
     
     
@@ -246,7 +247,7 @@ The add-in manifest file is in XML format and can be edited directly. To get per
 -  [Add search capabilities to your add-ins for SharePoint](http://blogs.msdn.com/b/officeapps/archive/2013/05/30/add-search-capabilities-to-your-apps-for-sharepoint.aspx)
     
   
--  [Exporting and importing search configuration settings in SharePoint](exporting-and-importing-search-configuration-settings-in-sharepoint)
+-  [Exporting and importing search configuration settings in SharePoint](exporting-and-importing-search-configuration-settings-in-sharepoint.md)
     
   
 -  [Export and import customized search configuration settings in SharePoint (TechNet)](http://technet.microsoft.com/en-us/library/jj871675.aspx)
diff --git a/docs/general-development/search-connector-framework-in-sharepoint.md b/docs/general-development/search-connector-framework-in-sharepoint.md
index a9cd9630ad..3f04407269 100644
--- a/docs/general-development/search-connector-framework-in-sharepoint.md
+++ b/docs/general-development/search-connector-framework-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: Search connector framework in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 38560a3b-69c6-4a56-97ca-3625bbd5755e
 ---
 
@@ -68,7 +69,7 @@ Figure 1 provides a high-level overview of the SharePoint indexing connector sto
   
     
     
-![SharePoint indexing connectors](../../images/SP15Con_CF_IndexingConnectors.jpg)
+![SharePoint indexing connectors](../images/SP15Con_CF_IndexingConnectors.jpg)
   
     
     
@@ -102,7 +103,7 @@ BCS is the umbrella of tools and infrastructure that enables you to connect to e
   
     
     
-![BCS architecture](../../images/SP15Con_CF_BCS_Overview.jpg)
+![BCS architecture](../images/SP15Con_CF_BCS_Overview.jpg)
   
     
     
@@ -193,7 +194,7 @@ Figure 3 shows a high-level view of the search connector framework architecture.
   
     
     
-![Search connector framework architecture](../../images/SP15Con_CF_ConnFrwkArch.jpg)
+![Search connector framework architecture](../images/SP15Con_CF_ConnFrwkArch.jpg)
   
     
     
@@ -307,22 +308,22 @@ The connector framework also provides improved exception capturing and logging t
 <a name="SP15searchconnect_addlresources"> </a>
 
 
--  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint)
+-  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint.md)
     
   
 -  [SharePoint: MyFileConnector custom BCS indexing connector sample](http://code.msdn.microsoft.com/SharePoint-MyFileConne-79d2ea26)
     
   
--  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint)
+-  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint.md)
     
   
--  [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint)
+-  [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint.md)
     
   
--  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint)
+-  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint.md)
     
   
--  [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint)
+-  [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/search-in-sharepoint.md b/docs/general-development/search-in-sharepoint.md
index 99047d2780..f0cb107ec9 100644
--- a/docs/general-development/search-in-sharepoint.md
+++ b/docs/general-development/search-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Search in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 59220f81-0e5e-4945-8056-cf0a116446cb
 ---
 
@@ -14,16 +15,16 @@ Search in SharePoint enables users to find relevant information more quickly and
     
 
 See the following articles for a good introduction to general SharePoint development concepts; you may find it helpful to review these before proceeding:
--  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint)
+-  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md)
     
   
--  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint)
+-  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md)
     
   
--  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions)
+-  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md)
     
   
--  [Deciding between SharePoint Add-ins and SharePoint solutions](deciding-between-sharepoint-add-ins-and-sharepoint-solutions)
+-  [Deciding between SharePoint Add-ins and SharePoint solutions](deciding-between-sharepoint-add-ins-and-sharepoint-solutions.md)
     
   
 
@@ -63,7 +64,7 @@ These areas consist of components and databases that work cohesively to perform
   
     
     
-![Search Component Interaction](../../images/SearchComponentInteraction.jpg)
+![Search Component Interaction](../images/SearchComponentInteraction.jpg)
   
     
     
@@ -193,14 +194,14 @@ The Search in SharePoint architecture provides several extensibility points to s
 
 ### Connector framework
 
-The crawl component crawls content by invoking connectors or protocol handlers that interact with content sources to retrieve data. Search in SharePoint includes a connector framework that you can use to customize and build connectors to crawl new content sources. For detailed information about the connector framework architecture and how to extend it, see  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint).
+The crawl component crawls content by invoking connectors or protocol handlers that interact with content sources to retrieve data. Search in SharePoint includes a connector framework that you can use to customize and build connectors to crawl new content sources. For detailed information about the connector framework architecture and how to extend it, see  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md).
   
     
     
 
 ### Custom content processing
 
-Within the content processing component, you can use the Content Enrichment web service callout to modify the managed properties of crawled items before they are added to the search index. This web service callout calls out to any external content enrichment web service that you create. For more information, see  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout). For a step-by-step implementation of a content enrichment web service, see  [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server). The blog post  [Customize the SharePoint search experience with a Content Enrichment web service](http://blogs.msdn.com/b/sharepointdev/archive/2012/11/13/customize-the-sharepoint-search-experience-with-a-content-enrichment-web-service.aspx) is also a good resource
+Within the content processing component, you can use the Content Enrichment web service callout to modify the managed properties of crawled items before they are added to the search index. This web service callout calls out to any external content enrichment web service that you create. For more information, see  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md). For a step-by-step implementation of a content enrichment web service, see  [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md). The blog post  [Customize the SharePoint search experience with a Content Enrichment web service](http://blogs.msdn.com/b/sharepointdev/archive/2012/11/13/customize-the-sharepoint-search-experience-with-a-content-enrichment-web-service.aspx) is also a good resource
   
     
     
@@ -227,7 +228,7 @@ Table 1 shows the APIs that you can use to program Search in SharePoint and wher
 |Representational State Transfer (REST) service endpoints  <br/> |http://server/_api/search/query <br/>http://server/_api/search/suggest  <br/> |
 |Server object model  <br/> |Microsoft.Office.Server.Search.dll <br/>%ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\ISAPI  <br/> |
    
-For more information, see  [Using the SharePoint search Query APIs](using-the-sharepoint-search-query-apis).
+For more information, see  [Using the SharePoint search Query APIs](using-the-sharepoint-search-query-apis.md).
   
     
     
@@ -241,7 +242,7 @@ To help identify and surface the content that users consider to be the most usef
 
 ### Custom ranking models
 
-Search results can be ordered in various ways, one of which is by rank score. Rank scores are calculated by the search engine using ranking models. SharePoint provides fourteen ranking models by default. However, if you are not satisfied with the way your search results are ordered, you can use a custom ranking model. To learn more about the process of creating a custom ranking model and tuning it, see  [Customizing ranking models to improve relevance in SharePoint](customizing-ranking-models-to-improve-relevance-in-sharepoint).
+Search results can be ordered in various ways, one of which is by rank score. Rank scores are calculated by the search engine using ranking models. SharePoint provides fourteen ranking models by default. However, if you are not satisfied with the way your search results are ordered, you can use a custom ranking model. To learn more about the process of creating a custom ranking model and tuning it, see  [Customizing ranking models to improve relevance in SharePoint](customizing-ranking-models-to-improve-relevance-in-sharepoint.md).
   
     
     
@@ -252,21 +253,21 @@ Search in SharePoint performs security trimming of search results that are based
   
     
     
-The pre-trimmer interface ( **ISecurityTrimmerPre**) carries out pre-query evaluation, where the search query is rewritten to add security information before the search query is matched to the search index. In contrast, the post-trimmer interface ( **ISecurityTrimmerPost**) carries out post-query evaluation, where the search results are pruned before they are returned to the user. For more information about the two interfaces, see  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server). For step-by-step information on how to implement a security trimmer interface, see  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results).
+The pre-trimmer interface ( **ISecurityTrimmerPre**) carries out pre-query evaluation, where the search query is rewritten to add security information before the search query is matched to the search index. In contrast, the post-trimmer interface ( **ISecurityTrimmerPost**) carries out post-query evaluation, where the search results are pruned before they are returned to the user. For more information about the two interfaces, see  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server.md). For step-by-step information on how to implement a security trimmer interface, see  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md).
   
     
     
 
 ### Content Search Web Part
 
-The Content Search Web Part is a Web Part that can display dynamic content that was previously crawled and added to the search index. Each instance of the Web Part is associated with a search query and shows the results for that particular search query. When users browse to a page that contains a Content Search Web Part, a search query is automatically issued, and the corresponding search results are returned from the search index. You can use the Content Search Web Part whenever you want to display content that is populated by automatically generated search queries. In some cases, you may want to extend the Content Search Web Part, which is exposed through the  [Microsoft.Office.Server.Search.WebControls](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.aspx) namespace as [ContentBySearchWebPart](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart.aspx) . To learn about how to extend the [ContentBySearchWebPart](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart.aspx) so that the Web Part understands custom properties, see [User segmentation in SharePoint](user-segmentation-in-sharepoint).
+The Content Search Web Part is a Web Part that can display dynamic content that was previously crawled and added to the search index. Each instance of the Web Part is associated with a search query and shows the results for that particular search query. When users browse to a page that contains a Content Search Web Part, a search query is automatically issued, and the corresponding search results are returned from the search index. You can use the Content Search Web Part whenever you want to display content that is populated by automatically generated search queries. In some cases, you may want to extend the Content Search Web Part, which is exposed through the  [Microsoft.Office.Server.Search.WebControls](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.aspx) namespace as [ContentBySearchWebPart](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart.aspx) . To learn about how to extend the [ContentBySearchWebPart](https://msdn.microsoft.com/library/Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart.aspx) so that the Web Part understands custom properties, see [User segmentation in SharePoint](user-segmentation-in-sharepoint.md).
   
     
     
 
 ### Search-driven mobile apps using the Navigation and Event Logging REST interfaces
 
-SharePoint provides two new REST interfaces: Navigation and Event Logging. You can use them to create search-driven mobile apps for mobile devices, such as phones and tablets, that run on operating systems other than Windows. This feature lets you display the product catalog on a mobile device in an alternate way, instead of using a mobile channel. See  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res) for a detailed example of how to create such an app.
+SharePoint provides two new REST interfaces: Navigation and Event Logging. You can use them to create search-driven mobile apps for mobile devices, such as phones and tablets, that run on operating systems other than Windows. This feature lets you display the product catalog on a mobile device in an alternate way, instead of using a mobile channel. See  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md) for a detailed example of how to create such an app.
   
     
     
@@ -274,34 +275,34 @@ SharePoint provides two new REST interfaces: Navigation and Event Logging. You c
 ## In this section
 
 
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
--  [Searching new content with SharePoint Search](searching-new-content-with-sharepoint-search)
+-  [Searching new content with SharePoint Search](searching-new-content-with-sharepoint-search.md)
     
   
--  [Configure search in SharePoint](configure-search-in-sharepoint)
+-  [Configure search in SharePoint](configure-search-in-sharepoint.md)
     
   
--  [Building search queries in SharePoint](building-search-queries-in-sharepoint)
+-  [Building search queries in SharePoint](building-search-queries-in-sharepoint.md)
     
   
--  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview)
+-  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview.md)
     
   
--  [Customizing search results in SharePoint](customizing-search-results-in-sharepoint)
+-  [Customizing search results in SharePoint](customizing-search-results-in-sharepoint.md)
     
   
--  [Sorting search results in SharePoint](sorting-search-results-in-sharepoint)
+-  [Sorting search results in SharePoint](sorting-search-results-in-sharepoint.md)
     
   
--  [Customizing ranking models to improve relevance in SharePoint](customizing-ranking-models-to-improve-relevance-in-sharepoint)
+-  [Customizing ranking models to improve relevance in SharePoint](customizing-ranking-models-to-improve-relevance-in-sharepoint.md)
     
   
--  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server)
+-  [Custom security trimming for Search in SharePoint](custom-security-trimming-for-search-in-sharepoint-server.md)
     
   
--  [Exporting and importing search configuration settings in SharePoint](exporting-and-importing-search-configuration-settings-in-sharepoint)
+-  [Exporting and importing search configuration settings in SharePoint](exporting-and-importing-search-configuration-settings-in-sharepoint.md)
     
   
 
@@ -314,6 +315,6 @@ SharePoint provides two new REST interfaces: Navigation and Event Logging. You c
 -  [Technical Diagrams -- Search](http://technet.microsoft.com/en-us/library/cc263199.aspx#search)
     
   
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
diff --git a/docs/general-development/searching-new-content-with-sharepoint-search.md b/docs/general-development/searching-new-content-with-sharepoint-search.md
index 0f63fb22a5..ffcd2a156d 100644
--- a/docs/general-development/searching-new-content-with-sharepoint-search.md
+++ b/docs/general-development/searching-new-content-with-sharepoint-search.md
@@ -1,6 +1,7 @@
----
+---
 title: Searching new content with SharePoint Search
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2a3a7d23-775a-4d95-9066-ebbd18c92ad4
 ---
 
@@ -51,21 +52,21 @@ Search in SharePoint provides two approaches for processing queries to return se
 ## In this section
 
 
--  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint)
+-  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md)
     
-  -  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint)
+  -  [Enhancing the BDC model file for Search in SharePoint](enhancing-the-bdc-model-file-for-search-in-sharepoint.md)
     
   
-  -  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint)
+  -  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint.md)
     
   
-  -  [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint)
+  -  [How to: Crawl binary large objects (BLOBs) in SharePoint](how-to-crawl-binary-large-objects-blobs-in-sharepoint.md)
     
   
-  -  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint)
+  -  [How to: Crawl associated external content types in SharePoint](how-to-crawl-associated-external-content-types-in-sharepoint.md)
     
   
-  -  [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint)
+  -  [How to: Configure item-level security in SharePoint](how-to-configure-item-level-security-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/set-up-a-general-development-environment-for-sharepoint.md b/docs/general-development/set-up-a-general-development-environment-for-sharepoint.md
index 1bfbdfbaf2..4a1526bdb6 100644
--- a/docs/general-development/set-up-a-general-development-environment-for-sharepoint.md
+++ b/docs/general-development/set-up-a-general-development-environment-for-sharepoint.md
@@ -1,9 +1,10 @@
 ---
 title: Set up a general development environment for SharePoint
+ms.date: 09/25/2017
 keywords: install SharePoint,set up SharePoint,setup SharePoint
 f1_keywords:
 - install SharePoint,set up SharePoint,setup SharePoint
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 08e4e4e1-d960-43fa-85df-f3c279ed6927
 ---
 
@@ -90,7 +91,7 @@ SharePoint requires your operating system to have certain prerequisites installe
 
   
 
-  ![SharePoint Installation Server Type](../../images/SP15_app_ServerType.gif)
+  ![SharePoint Installation Server Type](../images/SP15_app_ServerType.gif)
   
 
   
@@ -114,7 +115,7 @@ dir /od *.log
 
   
 
-  ![SharePoint site templates](../../images/SP15_app_ChooseSiteTemplates.gif)
+  ![SharePoint site templates](../images/SP15_app_ChooseSiteTemplates.gif)
   
 
   
@@ -157,7 +158,7 @@ The registry path will change in future versions of Visual Studio.
 ## Next steps
 <a name="SP15_bk_devenvazure"> </a>
 
-If you will be creating workflows, continue with  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager).
+If you will be creating workflows, continue with  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md).
   
     
     
diff --git a/docs/general-development/set-up-and-configure-sharepoint-workflow-manager.md b/docs/general-development/set-up-and-configure-sharepoint-workflow-manager.md
index d296650441..ab860b38fe 100644
--- a/docs/general-development/set-up-and-configure-sharepoint-workflow-manager.md
+++ b/docs/general-development/set-up-and-configure-sharepoint-workflow-manager.md
@@ -1,6 +1,7 @@
 ---
 title: Set up and configure SharePoint Workflow Manager
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4cd68a3e-9c3b-4fb9-bb66-e96cf0faec69
 ---
 
@@ -32,7 +33,7 @@ Instructions for installing and configuring SharePoint workflow components are m
 -  [Workflow Resource Center](http://technet.microsoft.com/en-US/sharepoint/jj556245)
     
   
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/setting-up-a-development-environment-for-bcs-in-sharepoint.md b/docs/general-development/setting-up-a-development-environment-for-bcs-in-sharepoint.md
index 7b648d01c9..5f5ff6c3c3 100644
--- a/docs/general-development/setting-up-a-development-environment-for-bcs-in-sharepoint.md
+++ b/docs/general-development/setting-up-a-development-environment-for-bcs-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Setting up a development environment for BCS in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d83c8a43-49dd-47eb-94d4-23aa2cf71a9a
 ---
 
@@ -31,7 +32,7 @@ The environment that you use for developing apps with BCS is the same as for dev
   
     
     
-To learn how to install the components of a development environment, including the operating system, SharePoint, Visual Studio 2012, and Office Developer Tools for Visual Studio 2012, follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+To learn how to install the components of a development environment, including the operating system, SharePoint, Visual Studio 2012, and Office Developer Tools for Visual Studio 2012, follow the instructions in  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -55,13 +56,13 @@ Because these solutions don't require code, you can use SharePoint Designer 2013
 -  [Set up an on-premises development environment for SharePoint Add-ins](http://msdn.microsoft.com/library/b0878c12-27c9-4eea-ae3b-7e79e5a8838d%28Office.15%29.aspx)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
 
diff --git a/docs/general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio.md b/docs/general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio.md
index c48718b151..cc60590182 100644
--- a/docs/general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio.md
+++ b/docs/general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio.md
@@ -1,6 +1,7 @@
 ---
 title: Shapes in the SharePoint Server workflow template in Visio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f35bdf5d-c102-4e2d-8a23-1d2df17155b9
 ---
 
@@ -17,7 +18,7 @@ This article lists the shapes contained in the SharePoint Workflow template in V
     
 
 > **Important:**
-> The following is a reference for workflow actions that are supported in SharePoint Designer 2013. Most of these actions are available in SharePoint Designer 2010, although one of those (Wait for List Item Event) has been revised and enhanced in the present version. Twelve new actions are introduced in the present version, and 25 actions have been removed. (To see a list of actions, conditions, and blocks that have been removed, see  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge).) 
+> The following is a reference for workflow actions that are supported in SharePoint Designer 2013. Most of these actions are available in SharePoint Designer 2010, although one of those (Wait for List Item Event) has been revised and enhanced in the present version. Twelve new actions are introduced in the present version, and 25 actions have been removed. (To see a list of actions, conditions, and blocks that have been removed, see  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge.md)..md) 
   
     
     
@@ -112,10 +113,10 @@ The following table shows a list of all the shapes that are contained in the Sha
 |**Shape in Visio 2013 and SharePoint Designer 2013 Visual Designer**|**Action in the SharePoint Designer 2013 Declarative Designer**|**Properties in SharePoint Designer 2013 Visual Designer**|**Description**|
 |:-----|:-----|:-----|:-----|
 |Start  <br/> |NA  <br/> |NA  <br/> |Begins the workflow. Every SharePoint workflow diagram must have only one Start shape.  <br/> |
-|Stage  <br/> |**Stage** <br/> |NA  <br/> |Contains any number of shapes and may include branching. All actions in the workflow must be contained by a stage. Stage shapes are visualized by using container shapes. A Stage shape requires that an Enter and an Exit shape be added to the edges of the container to define the paths in and out of the stage.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio).  <br/> |
-|Step  <br/> |**Step** <br/> |NA  <br/> |Represents a grouped series of sequential actions. Steps must be contained by a stage. A step shape must also have an Enter and Exit shape, which are added when the shape is dropped onto the canvas.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio).  <br/> |
+|Stage  <br/> |**Stage** <br/> |NA  <br/> |Contains any number of shapes and may include branching. All actions in the workflow must be contained by a stage. Stage shapes are visualized by using container shapes. A Stage shape requires that an Enter and an Exit shape be added to the edges of the container to define the paths in and out of the stage.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md).  <br/> |
+|Step  <br/> |**Step** <br/> |NA  <br/> |Represents a grouped series of sequential actions. Steps must be contained by a stage. A step shape must also have an Enter and Exit shape, which are added when the shape is dropped onto the canvas.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md).  <br/> |
 |Simple Stage  <br/> |**Stage** <br/> |NA  <br/> |Adds new stages to the top level of the workflow when in Stage View in Visio 2013.  <br/> |
-|Loop n Times  <br/> |**Loop n Times** <br/> |**Loop Count** <br/> |Defines a series of connected shapes that will execute as a loop, returning from the last shape in the series to the first, until the loop has executed a specified amount of times. Like stages, loops are represented by a container shape that includes an Enter and Exit shape.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio).  <br/> |
+|Loop n Times  <br/> |**Loop n Times** <br/> |**Loop Count** <br/> |Defines a series of connected shapes that will execute as a loop, returning from the last shape in the series to the first, until the loop has executed a specified amount of times. Like stages, loops are represented by a container shape that includes an Enter and Exit shape.  <br/> For more information, see the section titled "Stages, loops, and steps" in the article  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md).  <br/> |
 |Loop with condition  <br/> |**Loop with Condition** <br/> |**Loop Count** <br/> |Loops until a specific condition is met.  <br/> |
 |Start Parallel Action  <br/> |**Parallel Block** <br/> |NA  <br/> ||
 |End Parallel Action  <br/> |**Parallel Block** <br/> |NA  <br/> ||
@@ -125,10 +126,10 @@ The following table shows a list of all the shapes that are contained in the Sha
 <a name="VSSPD_Additional"> </a>
 
 
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 -  [SharePoint Workflow template shapes guide](http://office.microsoft.com/en-us/visio-help/sharepoint-workflow-template-shapes-guide-HA101903894.aspx)
diff --git a/docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md b/docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md
index f3cd95df4f..f447a3ea3a 100644
--- a/docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md
+++ b/docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Add-ins compared with SharePoint solutions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0e9efadb-aaf2-4c0d-afd5-d6cf25c4e7a8
 ---
 
@@ -70,7 +71,7 @@ SharePoint Add-ins and NCSSs use one of the SharePoint client object models or R
   
     
     
-The server object model also has APIs for create, read, update, and delete (CRUD) operations on lists, libraries, and websites, and for operations on other SharePoint components. This means that the server object model can be used for extensions that are intended for end users, but for reasons given in the previous section, farm solutions are not usually the best choice for such extensions. Thus, it is no surprise that farm solutions cannot be installed on Microsoft SharePoint Online. Because Microsoft handles all the management of SharePoint Online, there is no need for administrative extensions. For more information about the different sets of APIs in SharePoint and where they overlap, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+The server object model also has APIs for create, read, update, and delete (CRUD) operations on lists, libraries, and websites, and for operations on other SharePoint components. This means that the server object model can be used for extensions that are intended for end users, but for reasons given in the previous section, farm solutions are not usually the best choice for such extensions. Thus, it is no surprise that farm solutions cannot be installed on Microsoft SharePoint Online. Because Microsoft handles all the management of SharePoint Online, there is no need for administrative extensions. For more information about the different sets of APIs in SharePoint and where they overlap, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -104,7 +105,7 @@ For information about how to expand the possibilities of SharePoint Add-ins, see
 ## Doing things the add-in way
 <a name="Questions"> </a>
 
-As noted earlier, custom code that runs on the SharePoint servers is not allowed in SharePoint Add-ins. This is  *not*  a significant limitation. It simply means that your custom business logic moves either "down" to the client device or "up" to the cloud. In either case, you can use the [SharePoint REST/OData service](http://msdn.microsoft.com/library/f60ed19e-9840-4f39-911e-4676751a2f6b%28Office.15%29.aspx) to accessSharePoint sites, lists, and other data. You can also remotely access SharePoint data through the [SharePoint JavaScript, Silverlight, or .NET Framework client object models](http://msdn.microsoft.com/library/8c086b11-2b8b-41ec-82ae-cd4fef0aeac6%28Office.15%29.aspx). Finally, on Windows Phones, you can access SharePoint through the SharePointWindows Phone object model. For more information about the various sets of APIs in SharePoint, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As noted earlier, custom code that runs on the SharePoint servers is not allowed in SharePoint Add-ins. This is  *not*  a significant limitation. It simply means that your custom business logic moves either "down" to the client device or "up" to the cloud. In either case, you can use the [SharePoint REST/OData service](http://msdn.microsoft.com/library/f60ed19e-9840-4f39-911e-4676751a2f6b%28Office.15%29.aspx) to accessSharePoint sites, lists, and other data. You can also remotely access SharePoint data through the [SharePoint JavaScript, Silverlight, or .NET Framework client object models](http://msdn.microsoft.com/library/8c086b11-2b8b-41ec-82ae-cd4fef0aeac6%28Office.15%29.aspx). Finally, on Windows Phones, you can access SharePoint through the SharePointWindows Phone object model. For more information about the various sets of APIs in SharePoint, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -187,7 +188,7 @@ Another way to use the SharePoint client object model -- or its REST APIs -- to
 <a name="bk_addresources"> </a>
 
 
--  [Programming models in SharePoint](programming-models-in-sharepoint)
+-  [Programming models in SharePoint](programming-models-in-sharepoint.md)
     
   
 -  [Using Solutions in SharePoint Foundation](http://msdn.microsoft.com/library/0da0518c-24eb-48e0-89bd-21282fdeef94%28Office.15%29.aspx)
diff --git a/docs/general-development/sharepoint-composites-handbook.md b/docs/general-development/sharepoint-composites-handbook.md
index 93fbc0782f..db8514a429 100644
--- a/docs/general-development/sharepoint-composites-handbook.md
+++ b/docs/general-development/sharepoint-composites-handbook.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Composites Handbook
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0989bf64-ff2a-4ad4-b0da-43901040da98
 ---
 
diff --git a/docs/general-development/sharepoint-design-manager-branding-and-design-capabilities.md b/docs/general-development/sharepoint-design-manager-branding-and-design-capabilities.md
index 82c8ea0319..b1dfb64598 100644
--- a/docs/general-development/sharepoint-design-manager-branding-and-design-capabilities.md
+++ b/docs/general-development/sharepoint-design-manager-branding-and-design-capabilities.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Design Manager branding and design capabilities
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2f81acbb-1263-4f9d-8865-36eb7a3f907b
 ---
 
@@ -13,22 +14,22 @@ Design Manager in SharePoint provides a new approach for designing websites. Sev
     
 
 See these articles for more information about the design and support capabilities included in Design Manager:
--  [Design packages](sharepoint-design-manager-design-packages): Learn how to build and export the visual design of a SharePoint site collection as a package.
+-  [Design packages](sharepoint-design-manager-design-packages.md): Learn how to build and export the visual design of a SharePoint site collection as a package.
     
   
--  [Device channels](sharepoint-design-manager-device-channels): With device channels in SharePoint, you can render a single publishing site in multiple ways by using different designs that target different devices. Learn how to create a device channel, change a device channel, delete a device channel, and reorder device channels in SharePoint.
+-  [Device channels](sharepoint-design-manager-device-channels.md): With device channels in SharePoint, you can render a single publishing site in multiple ways by using different designs that target different devices. Learn how to create a device channel, change a device channel, delete a device channel, and reorder device channels in SharePoint.
     
   
--  [Display templates](sharepoint-design-manager-display-templates): Learn about display templates, including how they relate to Search Web Parts, how the templates are structured, how to map properties and use variables and jQuery, and how to create a custom display template in SharePoint.
+-  [Display templates](sharepoint-design-manager-display-templates.md): Learn about display templates, including how they relate to Search Web Parts, how the templates are structured, how to map properties and use variables and jQuery, and how to create a custom display template in SharePoint.
     
   
--  [Image renditions](sharepoint-design-manager-image-renditions): Learn how to create, edit, or delete image renditions. An image rendition defines the dimensions that are used to display images in SharePoint publishing sites.
+-  [Image renditions](sharepoint-design-manager-image-renditions.md): Learn how to create, edit, or delete image renditions. An image rendition defines the dimensions that are used to display images in SharePoint publishing sites.
     
   
--  [Snippets](sharepoint-design-manager-snippets): A snippet is an HTML representation of a SharePoint component or control such as a navigation bar or a Web Part. By using the Snippet Gallery in Design Manager, you can quickly add SharePoint functionality to your HTML master page or page layout.
+-  [Snippets](sharepoint-design-manager-snippets.md): A snippet is an HTML representation of a SharePoint component or control such as a navigation bar or a Web Part. By using the Snippet Gallery in Design Manager, you can quickly add SharePoint functionality to your HTML master page or page layout.
     
   
--  [Themes](themes-overview-for-sharepoint): Learn about the theming experience in SharePoint and how you can use themes to customize the look and feel of sites.
+-  [Themes](themes-overview-for-sharepoint.md): Learn about the theming experience in SharePoint and how you can use themes to customize the look and feel of sites.
     
   
 
@@ -36,13 +37,13 @@ See these articles for more information about the design and support capabilitie
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
 
diff --git a/docs/general-development/sharepoint-design-manager-design-packages.md b/docs/general-development/sharepoint-design-manager-design-packages.md
index 901ff194c3..97d3d9405c 100644
--- a/docs/general-development/sharepoint-design-manager-design-packages.md
+++ b/docs/general-development/sharepoint-design-manager-design-packages.md
@@ -1,6 +1,7 @@
----
+---
 title: SharePoint Design Manager design packages
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 85ad1993-4d75-4806-9097-b934865a899a
 ---
 
@@ -48,7 +49,7 @@ Figure 1 shows the option in Design Manager for naming and creating the design p
   
     
     
-![Exporting a design package](../../images/sp15Con_DesignPackageExp_Figure1.png)
+![Exporting a design package](../images/sp15Con_DesignPackageExp_Figure1.png)
   
     
     
@@ -59,7 +60,7 @@ Alternatively, you can import a design package from another SharePoint site coll
 
     
 > **Note:**
-> For more information about Design Manager and the publishing process, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint). 
+> For more information about Design Manager and the publishing process, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md). 
   
     
     
@@ -164,12 +165,12 @@ When importing a design package, an alternate CSS URL is not set, even if one wa
 <a name="addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
diff --git a/docs/general-development/sharepoint-design-manager-device-channels.md b/docs/general-development/sharepoint-design-manager-device-channels.md
index 7158cc4e63..96bc96e187 100644
--- a/docs/general-development/sharepoint-design-manager-device-channels.md
+++ b/docs/general-development/sharepoint-design-manager-device-channels.md
@@ -1,6 +1,7 @@
----
+---
 title: SharePoint Design Manager device channels
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a924bd7b-a5e3-41bf-b0a7-3e43945fa951
 ---
 
@@ -15,7 +16,7 @@ Browsing the web on a mobile device is now so common that a SharePoint site must
   
     
     
-Device channels are available only for SharePoint publishing sites. Before you implement device channels, you should already have a general understanding of the parts of a SharePoint site, how a SharePoint page is put together, and a general understanding of design manager. For more information about the SharePoint page model, including master page and page layouts, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model). For more information about design manager, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint).
+Device channels are available only for SharePoint publishing sites. Before you implement device channels, you should already have a general understanding of the parts of a SharePoint site, how a SharePoint page is put together, and a general understanding of design manager. For more information about the SharePoint page model, including master page and page layouts, see  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md). For more information about design manager, see  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md).
   
     
     
@@ -35,7 +36,7 @@ Figure 1. Using device channels across different device platforms
   
     
     
-![Using device channels across device platforms](../../images/sp15Con_DeviceChannels_Fig1.png)
+![Using device channels across device platforms](../images/sp15Con_DeviceChannels_Fig1.png)
   
     
     
@@ -62,7 +63,7 @@ You can create and configure a device channel from the **Site Settings** menu un
 
     
 > **Note:**
-> For more information and steps for creating a device channel, see the  [Create a device channel](sharepoint-design-manager-device-channels#create) section of this article.
+> For more information and steps for creating a device channel, see the  [Create a device channel](sharepoint-design-manager-device-channels.md#create) section of this article.
   
     
     
@@ -81,7 +82,7 @@ After a device channel is created and activated, device redirection to a specifi
   
     
     
-![Setting master pages for mobile device and desktop](../../images/sp15Con_SiteMasterPage_Figure2.png)
+![Setting master pages for mobile device and desktop](../images/sp15Con_SiteMasterPage_Figure2.png)
   
     
     
@@ -114,7 +115,7 @@ In the **Device Inclusion Rules** field, you add just the substring value or val
     
 
 > **Important:**
-> User agent substring values differ from device manufacturer to device manufacturer, and possibly throughout a set of similarly branded devices, as seen above with Windows Phone. To achieve successful traffic redirection to a specific pool, you must provide a unique identifier for the user agent substring. For more information about how to isolate a substring across different devices, see the  [Planning your device channels experience](sharepoint-design-manager-device-channels#plan) section of this article.
+> User agent substring values differ from device manufacturer to device manufacturer, and possibly throughout a set of similarly branded devices, as seen above with Windows Phone. To achieve successful traffic redirection to a specific pool, you must provide a unique identifier for the user agent substring. For more information about how to isolate a substring across different devices, see the  [Planning your device channels experience](sharepoint-design-manager-device-channels.md#plan) section of this article.
   
     
     
@@ -125,7 +126,7 @@ After they are created, device channels are ordered and stored in a list. It is
     
 
 > **Note:**
-> For more information about how to reorder device channels see the  [Create a device channel](sharepoint-design-manager-device-channels#create) section of this article.
+> For more information about how to reorder device channels see the  [Create a device channel](sharepoint-design-manager-device-channels.md#create) section of this article.
   
     
     
@@ -146,7 +147,7 @@ If you choose Order 1, where the device inclusion rule substring is set to **Win
     
 
 > **Note:**
-> For more information and steps for ordering device channels, see the  [Change the order of device channels](sharepoint-design-manager-device-channels#reorder) section of this article.
+> For more information and steps for ordering device channels, see the  [Change the order of device channels](sharepoint-design-manager-device-channels.md#reorder) section of this article.
   
     
     
@@ -184,7 +185,7 @@ This paragraph of content shows up only in the default channel, which means that
 </div>
 ```
 
-If you want the content to be displayed on more than one channel, the aliases should be separated by commas within the quotation marks:  `IncludedChannels="alias1, alias2"` For more information about the device channel panel container, see [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model). For more information about using Design Manager snippets, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets).
+If you want the content to be displayed on more than one channel, the aliases should be separated by commas within the quotation marks:  `IncludedChannels="alias1, alias2"` For more information about the device channel panel container, see [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md). For more information about using Design Manager snippets, see  [SharePoint Design Manager snippets](sharepoint-design-manager-snippets.md).
   
     
     
@@ -434,12 +435,12 @@ Use this procedure to change the order of device channels.
 <a name="PlanDeviceChannels_addresources"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model)
+-  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md)
     
   
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
diff --git a/docs/general-development/sharepoint-design-manager-display-templates.md b/docs/general-development/sharepoint-design-manager-display-templates.md
index 6922d8320d..10181f39e4 100644
--- a/docs/general-development/sharepoint-design-manager-display-templates.md
+++ b/docs/general-development/sharepoint-design-manager-display-templates.md
@@ -1,6 +1,7 @@
----
+---
 title: SharePoint Design Manager display templates
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1a782bac-48ee-4baf-8751-0f943a306e0f
 ---
 
@@ -26,7 +27,7 @@ You can view existing display templates in Design Manager, but you don't create
     
     
 
-- Open your  [mapped network drive to the Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+- Open your  [mapped network drive to the Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
     
   
 - Open one of the four folders in the **Display Templates** folder.
@@ -97,7 +98,7 @@ After you add a Search Web Part (such as the Content Search Web Part) to a page,
   
     
     
-![Tool pane of Content Search Web Part](../../images/115_content_search_web_part_tool_pane.gif)
+![Tool pane of Content Search Web Part](../images/115_content_search_web_part_tool_pane.gif)
   
     
     
@@ -123,11 +124,11 @@ When used together in this way, the control display template and the item displa
   
     
     
-![Combined HTML output of a control display template and item display template](../../images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png)
+![Combined HTML output of a control display template and item display template](../images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png)
   
     
     
-For more information about display templates, see the "Search-driven Web Parts and display templates" section in  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model).
+For more information about display templates, see the "Search-driven Web Parts and display templates" section in  [Overview of the SharePoint page model](overview-of-the-sharepoint-page-model.md).
   
     
     
@@ -326,7 +327,7 @@ You can use jQuery with your display templates. But, be aware of two important f
 ## Create a display template
 <a name="bk_createDT"> </a>
 
-Before you can create a display template by using the following procedure, you must have a mapped network drive that points to the **Master Page Gallery**. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery).
+Before you can create a display template by using the following procedure, you must have a mapped network drive that points to the **Master Page Gallery**. For more information, see  [How to: Map a network drive to the SharePoint Master Page Gallery](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md).
   
     
     
@@ -373,19 +374,19 @@ Before you can create a display template by using the following procedure, you m
 <a name="bk_addresources"> </a>
 
 
--  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint)
+-  [Overview of Design Manager in SharePoint](overview-of-design-manager-in-sharepoint.md)
     
   
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
 
diff --git a/docs/general-development/sharepoint-design-manager-image-renditions.md b/docs/general-development/sharepoint-design-manager-image-renditions.md
index 6ddd18aa96..b3275c0c35 100644
--- a/docs/general-development/sharepoint-design-manager-image-renditions.md
+++ b/docs/general-development/sharepoint-design-manager-image-renditions.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Design Manager image renditions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d08a74c0-5674-4f26-8646-11ea1f081c85
 ---
 
@@ -213,7 +214,7 @@ By default, an image rendition is generated from the center of the image. You ca
   
     
     
-![Original image rendition](../../images/ImgRendition_orig.PNG)
+![Original image rendition](../images/ImgRendition_orig.PNG)
   
     
     
@@ -227,7 +228,7 @@ By default, an image rendition is generated from the center of the image. You ca
   
     
     
-![Cropped image rendition](../../images/ImgRendition_crop.PNG)
+![Cropped image rendition](../images/ImgRendition_crop.PNG)
   
     
     
@@ -353,13 +354,13 @@ When an image rendition is deleted, that image rendition is no longer generated
 <a name="Additional"> </a>
 
 
--  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint)
+-  [Develop the site design in SharePoint](develop-the-site-design-in-sharepoint.md)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/sharepoint-design-manager-snippets.md b/docs/general-development/sharepoint-design-manager-snippets.md
index 894ee80468..30a3af2d2a 100644
--- a/docs/general-development/sharepoint-design-manager-snippets.md
+++ b/docs/general-development/sharepoint-design-manager-snippets.md
@@ -1,6 +1,7 @@
----
+---
 title: SharePoint Design Manager snippets
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 68caef4c-5941-4a88-b34b-f88122801cef
 ---
 
@@ -404,16 +405,16 @@ Here is a breakdown of the types of markup that are included in a snippet.
 <a name="Resources"> </a>
 
 
--  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint)
+-  [How to: Convert an HTML file into a master page in SharePoint](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md)
     
   
--  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint)
+-  [How to: Create a page layout in SharePoint](how-to-create-a-page-layout-in-sharepoint.md)
     
   
--  [How to: Add an Edit Mode Panel snippet in SharePoint](how-to-add-an-edit-mode-panel-snippet-in-sharepoint)
+-  [How to: Add an Edit Mode Panel snippet in SharePoint](how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md)
     
   
--  [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint)
+-  [How to: Add a Security Trim snippet in SharePoint](how-to-add-a-security-trim-snippet-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/sharepoint-development-overview.md b/docs/general-development/sharepoint-development-overview.md
index b82db68d30..575ca2fae9 100644
--- a/docs/general-development/sharepoint-development-overview.md
+++ b/docs/general-development/sharepoint-development-overview.md
@@ -1,6 +1,7 @@
----
+---
 title: SharePoint development overview
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f86e2695-4d7a-4fc5-bc23-689de96c4b06
 ---
 
@@ -31,14 +32,14 @@ The following article can help you get acquainted with SharePoint Add-ins and de
     
     
 
--  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions)
+-  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md)
     
   
  **For SharePoint solutions and add-ins for mobility features development**
   
     
     
-If you want to develop farm solutions, you can take advantage of many new capabilities, including features for social applications, integration with remote data stores (Business Connectivity Services), and mobile development. Start with our guidance in  [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint).
+If you want to develop farm solutions, you can take advantage of many new capabilities, including features for social applications, integration with remote data stores (Business Connectivity Services), and mobile development. Start with our guidance in  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md).
   
     
     
@@ -47,10 +48,10 @@ The following sections describe how to create mobile solutions for SharePoint.
     
     
 
--  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint)
+-  [Build Windows Phone apps that access SharePoint](build-windows-phone-apps-that-access-sharepoint.md)
     
   
--  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res)
+-  [How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces](how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md)
     
   
 The following sections provide information about SharePoint features that are available for farm solutions. 
@@ -58,10 +59,10 @@ The following sections provide information about SharePoint features that are av
     
     
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
 
@@ -86,11 +87,11 @@ Table 1 shows the resources for setting up a development environment and beginni
 
 |**Topic**|**Description**|
 |:-----|:-----|
-| [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint) <br/> |Contains step-by-step instructions on how to install the components of a SharePoint development environment.  <br/> |
-| [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint) <br/> |Describes the several sets of APIs that are provided in SharePoint, including the server object model and the various client-side object models, and the REST/OData web service.  <br/> |
-| [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint) <br/> |Provides a gateway to detailed information about new features and functionality in SharePoint.  <br/> |
-| [Programming models in SharePoint](programming-models-in-sharepoint) <br/> |Provides a quick overview of the different kinds of SharePoint development projects that you can create with SharePoint.  <br/> |
-| [Add SharePoint capabilities](add-sharepoint-capabilities) <br/> |Provides a gateway to detailed information about using the capabilities of SharePoint in your solutions.  <br/> |
+| [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md) <br/> |Contains step-by-step instructions on how to install the components of a SharePoint development environment.  <br/> |
+| [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md) <br/> |Describes the several sets of APIs that are provided in SharePoint, including the server object model and the various client-side object models, and the REST/OData web service.  <br/> |
+| [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md) <br/> |Provides a gateway to detailed information about new features and functionality in SharePoint.  <br/> |
+| [Programming models in SharePoint](programming-models-in-sharepoint.md) <br/> |Provides a quick overview of the different kinds of SharePoint development projects that you can create with SharePoint.  <br/> |
+| [Add SharePoint capabilities](add-sharepoint-capabilities.md) <br/> |Provides a gateway to detailed information about using the capabilities of SharePoint in your solutions.  <br/> |
    
  **For SharePoint Add-ins development**
   
@@ -121,10 +122,10 @@ When you know the kinds of SharePoint Add-in that you want to create, we provide
 <a name="bk_additionalresources"> </a>
 
 
--  [Accessibility in SharePoint](accessibility-in-sharepoint)
+-  [Accessibility in SharePoint](accessibility-in-sharepoint.md)
     
   
--  [Protocol handler error due to deprecated interface in SharePoint 2016](protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016)
+-  [Protocol handler error due to deprecated interface in SharePoint 2016](protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md)
     
   
 -  [.NET server API reference for SharePoint](http://msdn.microsoft.com/library/fb8a82f1-9239-49ae-89f3-ce1385fb28b5%28Office.15%29.aspx)
diff --git a/docs/general-development/sharepoint-online-suite-navigation-control.md b/docs/general-development/sharepoint-online-suite-navigation-control.md
index 01113f8d8b..7d532b0c5c 100644
--- a/docs/general-development/sharepoint-online-suite-navigation-control.md
+++ b/docs/general-development/sharepoint-online-suite-navigation-control.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Online Suite Navigation control
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ba93e5c0-e591-48d0-a716-a08ec7ef6cea
 ---
 
@@ -303,10 +304,10 @@ var g_navBarHelpDefaultKey = "HelpHome";
 <a name="bk_addresources"> </a>
 
 
--  [Build sites for SharePoint](build-sites-for-sharepoint)
+-  [Build sites for SharePoint](build-sites-for-sharepoint.md)
     
   
--  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development)
+-  [What's new with SharePoint site development](what-s-new-with-sharepoint-site-development.md)
     
   
 -  [Menu control overview (ASP.NET)](http://msdn.microsoft.com/en-us/library/ecs0x9w5%28v=vs.90%29.aspx.aspx)
diff --git a/docs/general-development/sharepoint-search-rest-api-overview.md b/docs/general-development/sharepoint-search-rest-api-overview.md
index ada1c72810..bd4977b093 100644
--- a/docs/general-development/sharepoint-search-rest-api-overview.md
+++ b/docs/general-development/sharepoint-search-rest-api-overview.md
@@ -1,3 +1,9 @@
+---
+title: SharePoint Search REST API overview
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # SharePoint Search REST API overview
 Add search functionality to client and mobile applications using the Search REST service in SharePoint and any technology that supports REST web requests.
@@ -1641,7 +1647,7 @@ When an anonymous Search REST query is submitted, the query object is constructe
 ## In this section
 <a name="bk_AnonymousREST"> </a>
 
--  [Retrieving query suggestions using the Search REST service](retrieving-query-suggestions-using-the-search-rest-service)
+-  [Retrieving query suggestions using the Search REST service](retrieving-query-suggestions-using-the-search-rest-service.md)
     
   
 
@@ -1649,13 +1655,13 @@ When an anonymous Search REST query is submitted, the query object is constructe
 <a name="bk_addresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
 -  [SharePoint: Using the search REST service from an app for SharePoint](http://code.msdn.microsoft.com/sharepoint/SharePoint-Perform-a-1bf3e87d)
     
   
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
 -  [Use OData query operations in SharePoint REST requests](http://msdn.microsoft.com/library/d4b5c277-ed50-420c-8a9b-860342284b72%28Office.15%29.aspx)
diff --git a/docs/general-development/sharepoint-server-application-lifecycle-management.md b/docs/general-development/sharepoint-server-application-lifecycle-management.md
index 4b08fa7e33..8666949ba6 100644
--- a/docs/general-development/sharepoint-server-application-lifecycle-management.md
+++ b/docs/general-development/sharepoint-server-application-lifecycle-management.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint Application Lifecycle Management
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: caaf9a09-2e6a-49e3-a8d6-aaf7f93a842a
 ---
 
@@ -36,7 +37,7 @@ Additionally, Microsoft advises customers to evaluate the technologies used when
   
     
     
-For more information about the new flexible development technologies for applications on SharePoint, see  [SharePoint development overview](sharepoint-development-overview).
+For more information about the new flexible development technologies for applications on SharePoint, see  [SharePoint development overview](sharepoint-development-overview.md).
   
     
     
@@ -89,7 +90,7 @@ The selection of a development environment should be made based on multiple fact
 
 
     
- [![The app development environment can include Office 365, Visual Studio, and virtual machines.](../../images/AppDevelopmentEnvironment.png)
+ [![The app development environment can include Office 365, Visual Studio, and virtual machines.](../images/AppDevelopmentEnvironment.png)
   
     
     
@@ -123,7 +124,7 @@ Figure 2 shows how developers can use Office 365 as a development environment an
   
     
     
- [![Build apps for SharePoint with Office 365, Visual Studio, and "Napa."](../../images/Office365AppDevelpment.png)
+ [![Build apps for SharePoint with Office 365, Visual Studio, and "Napa."](../images/Office365AppDevelpment.png)
   
     
     
@@ -181,7 +182,7 @@ For organizations or developers who choose not to use Office 365 developer sites
   
     
     
- [![Build apps for SharePoint in an on-premises deployment of SharePoint with the developer site template](../../images/OnPremDevSites.png)
+ [![Build apps for SharePoint in an on-premises deployment of SharePoint with the developer site template](../images/OnPremDevSites.png)
   
     
     
@@ -221,7 +222,7 @@ Figure 4 shows the types of applications that can be created using an on-premise
   
     
     
- [![Build apps for SharePoint in a virtual on-premises environment](../../images/AppDevelopmentVirtualEnvironment.png)
+ [![Build apps for SharePoint in a virtual on-premises environment](../images/AppDevelopmentVirtualEnvironment.png)
   
     
     
@@ -301,7 +302,7 @@ When planning build processes for SharePoint application development, developers
   
     
     
-![Visual Studio builds work with app manifests, pages, and supporting files.](../../images/AppDevelopmentClientBuildComponents.png)
+![Visual Studio builds work with app manifests, pages, and supporting files.](../images/AppDevelopmentClientBuildComponents.png)
   
     
     
@@ -319,7 +320,7 @@ The illustration in Figure 5 is a logical representation of a SharePoint applica
   
     
     
-![Provider-hosted apps contain both SharePoint app packages and cloud-hosted components.](../../images/ProviderHostedAppBuildComponents.png)
+![Provider-hosted apps contain both SharePoint app packages and cloud-hosted components.](../images/ProviderHostedAppBuildComponents.png)
   
     
     
@@ -337,7 +338,7 @@ Figure 6 shows a SharePoint cloud-hosted application (that is, autohosted or pro
   
     
     
-![TFS can be configured to conduct build and deployment activities with a SharePoint application through build definitions.](../../images/ALMWithTFS.png)
+![TFS can be configured to conduct build and deployment activities with a SharePoint application through build definitions.](../images/ALMWithTFS.png)
   
     
     
@@ -355,7 +356,7 @@ Figure 7 shows TFS as the ALM platform. Teams will use TFS to store code and con
   
     
     
-![Scripts executed by a TFS build definition will deploy the SharePoint application components to SharePoint Online and on-premises SharePoint.](../../images/TFSBuildTargets.png)
+![Scripts executed by a TFS build definition will deploy the SharePoint application components to SharePoint Online and on-premises SharePoint.](../images/TFSBuildTargets.png)
   
     
     
@@ -397,7 +398,7 @@ Figure 9 shows a standard process for SharePoint application builds and deployme
   
     
     
- [![TFS build services execute the steps defined by the SharePoint application build definition.](../../images/ALMBuildDeployProcess.png)
+ [![TFS build services execute the steps defined by the SharePoint application build definition.](../images/ALMBuildDeployProcess.png)
   
     
     
@@ -428,7 +429,7 @@ Note that for cloud-hosted (auto and provider) applications, developers can depl
   
     
     
- [![As developers make changes to the solution that represents the SharePoint application, there may be circumstances where changes are made to the projects within the solution that do not apply to the SharePoint application project itself.](../../images/ALMChangeManagement.png)
+ [![As developers make changes to the solution that represents the SharePoint application, there may be circumstances where changes are made to the projects within the solution that do not apply to the SharePoint application project itself.](../images/ALMChangeManagement.png)
   
     
     
@@ -459,7 +460,7 @@ Figure 11 shows the types of testing approaches that are best used with SharePoi
   
     
     
- [![Coded UI tests should be leveraged against SharePoint-hosted applications where the business logic and the user experience reside in the same layer.](../../images/ALMTestingTypes.png)
+ [![Coded UI tests should be leveraged against SharePoint-hosted applications where the business logic and the user experience reside in the same layer.](../images/ALMTestingTypes.png)
   
    
     
@@ -534,7 +535,7 @@ Developer testing can occur in the environment where the developers are creating
   
     
     
- [![Developers will execute tests from Visual Studio against the solution components deployed in their own Office 365 or on-premises developer site.](../../images/ALMDeveloperTesting.png)
+ [![Developers will execute tests from Visual Studio against the solution components deployed in their own Office 365 or on-premises developer site.](../images/ALMDeveloperTesting.png)
   
     
     
@@ -565,7 +566,7 @@ In order to test the application, all of the development components should be as
   
     
     
- [![TFS will build and deploy the SharePoint application and any required components to the target environments.](../../images/ALMIntegrationTesting.png)
+ [![TFS will build and deploy the SharePoint application and any required components to the target environments.](../images/ALMIntegrationTesting.png)
   
     
     
@@ -587,7 +588,7 @@ For user acceptance testing (UAT), organizations often have separate environment
   
     
     
- [![Users assigned to conduct acceptance testing or organizational testing resources conduct test scripts in a stable environment that is focused on a well-publicized build version of the application.](../../images/ALMUATTesting.png)
+ [![Users assigned to conduct acceptance testing or organizational testing resources conduct test scripts in a stable environment that is focused on a well-publicized build version of the application.](../images/ALMUATTesting.png)
   
     
     
@@ -606,7 +607,7 @@ For cloud-hosted infrastructure, deployment into a Microsoft Azure subscription
   
     
     
- [![Deployment into a Microsoft Azure subscription that is shared with the integration/systems test environment is possible if the services are named and configured to be deployed side by side as different services or databases.](../../images/ALMIntegrationandUAT.png)
+ [![Deployment into a Microsoft Azure subscription that is shared with the integration/systems test environment is possible if the services are named and configured to be deployed side by side as different services or databases.](../images/ALMIntegrationandUAT.png)
   
    
     
@@ -625,7 +626,7 @@ The code promotion process between the development and testing environments as w
   
     
     
- [![Following a check-in to TFS, an automated build procedure will compile and deploy the solution to the target environment where build verification tests will be executed as part of the build definition in TFS.](../../images/ALMCodePromotion.png)
+ [![Following a check-in to TFS, an automated build procedure will compile and deploy the solution to the target environment where build verification tests will be executed as part of the build definition in TFS.](../images/ALMCodePromotion.png)
   
    
     
@@ -672,7 +673,7 @@ The information in  [SharePoint Add-ins update process](http://msdn.microsoft.co
 -  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](http://msdn.microsoft.com/library/2f65ba3f-b246-4064-b4fb-ad18399d387a%28Office.15%29.aspx)
     
   
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
 -  [What is the Open Data Protocol?](http://www.odata.org/)
diff --git a/docs/general-development/sharepoint-vss-writer.md b/docs/general-development/sharepoint-vss-writer.md
index 215950a283..dcf7f0437a 100644
--- a/docs/general-development/sharepoint-vss-writer.md
+++ b/docs/general-development/sharepoint-vss-writer.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint VSS Writer
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f83577e4-ebb8-44e5-8dec-a3ca5878b7fd
 ---
 
@@ -47,7 +48,7 @@ Following are the SharePoint Foundation VSS solution features and characteristic
 - **Full rollback.** The SPF-VSS Writer handles all components within a SharePoint Foundation deployment, including the configuration database and the content databases and the Search database and index. As mentioned previously, the writer also has a dependency on the Search writer, which handles all the Search index files for backup and recovery. At the time of recovery, the writer can roll back the entire SharePoint Foundation deployment by restoring a previous farm backup. (The IIS configuration store is not included. It must be backed up and restored separately.)
     
     > **Note:**
-      > See "Restoring" in  [VSS requestors and SharePoint](vss-requestors-and-sharepoint) for important information about restorations.
+      > See "Restoring" in  [VSS requestors and SharePoint](vss-requestors-and-sharepoint.md) for important information about restorations.
 - **Post-restore synchronization of databases.** To ensure that all databases are synchronized with the farm after a restore operation is complete, each of the databases are automatically detached and reattached to the farm post recovery. Administrators do not need to run additional procedures to resynchronize the restored databases.
     
   
@@ -75,7 +76,7 @@ The SPF-VSS Writer performs the following functions:
     
   
 
-  ![SharePoint and Volume Shadow Copy Service](../../images/99376713-6a54-4d88-9b05-068578169506.gif)
+  ![SharePoint and Volume Shadow Copy Service](../images/99376713-6a54-4d88-9b05-068578169506.gif)
   
 
   
@@ -87,7 +88,7 @@ The SPF-VSS Writer performs the following functions:
     
   
 
-  ![SharePoint and Volume Shadow Copy Service](../../images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif)
+  ![SharePoint and Volume Shadow Copy Service](../images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif)
   
 
   
@@ -102,7 +103,7 @@ The SPF-VSS Writer performs the following functions:
     
   
 
-  ![SharePoint and Volume Shadow Copy Service](../../images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif)
+  ![SharePoint and Volume Shadow Copy Service](../images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif)
   
 
   
@@ -117,7 +118,7 @@ Learn how to create and use a VSS requestor for SharePoint:
     
     
 
--  [VSS requestors and SharePoint](vss-requestors-and-sharepoint)
+-  [VSS requestors and SharePoint](vss-requestors-and-sharepoint.md)
     
   
 
@@ -125,7 +126,7 @@ Learn how to create and use a VSS requestor for SharePoint:
 <a name="bk_addresources"> </a>
 
 
--  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service)
+-  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service.md)
     
   
 
diff --git a/docs/general-development/sharepoint-workflow-development-best-practices.md b/docs/general-development/sharepoint-workflow-development-best-practices.md
index d0b092f1e2..c7030027e0 100644
--- a/docs/general-development/sharepoint-workflow-development-best-practices.md
+++ b/docs/general-development/sharepoint-workflow-development-best-practices.md
@@ -1,3 +1,9 @@
+---
+title: SharePoint VSS Writer
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # SharePoint workflow development best practices
 Provides a collection of best practices for developers using Visual Studio to create workflows in SharePoint.
@@ -8,34 +14,34 @@ To develop error-free workflows for SharePoint, it is best to follow some genera
     
     
 
--  [Apps for SharePoint that contain integrated workflows must edit a tag in the workflowmanifest.xml file](sharepoint-workflow-development-best-practices#bkm_00)
+-  [Apps for SharePoint that contain integrated workflows must edit a tag in the workflowmanifest.xml file](sharepoint-workflow-development-best-practices.md#bkm_00)
     
   
--  [When you use the Log To History List action, more information is better](sharepoint-workflow-development-best-practices#bkm_01)
+-  [When you use the Log To History List action, more information is better](sharepoint-workflow-development-best-practices.md#bkm_01)
     
   
--  [Write the value of every string and variable that you construct to the history list](sharepoint-workflow-development-best-practices#bkm_02)
+-  [Write the value of every string and variable that you construct to the history list](sharepoint-workflow-development-best-practices.md#bkm_02)
     
   
--  [Output a trace log before and after each step or important unit of work in the workflow](sharepoint-workflow-development-best-practices#bkm_03)
+-  [Output a trace log before and after each step or important unit of work in the workflow](sharepoint-workflow-development-best-practices.md#bkm_03)
     
   
--  [Verify that variables are non-null and contain expected values](sharepoint-workflow-development-best-practices#bkm_04)
+-  [Verify that variables are non-null and contain expected values](sharepoint-workflow-development-best-practices.md#bkm_04)
     
   
--  [Ensure that strings in workflow text fields do not exceed 255 characters](sharepoint-workflow-development-best-practices#bkm_05)
+-  [Ensure that strings in workflow text fields do not exceed 255 characters](sharepoint-workflow-development-best-practices.md#bkm_05)
     
   
--  [Use elevated permissions on a neutral account when using impersonation](sharepoint-workflow-development-best-practices#bkm_06)
+-  [Use elevated permissions on a neutral account when using impersonation](sharepoint-workflow-development-best-practices.md#bkm_06)
     
   
--  [In reusable workflows, use Association columns to ensure error-free list fields](sharepoint-workflow-development-best-practices#bkm_07)
+-  [In reusable workflows, use Association columns to ensure error-free list fields](sharepoint-workflow-development-best-practices.md#bkm_07)
     
   
--  [Workflow design: Model a business process in a single workflow](sharepoint-workflow-development-best-practices#bkm_08)
+-  [Workflow design: Model a business process in a single workflow](sharepoint-workflow-development-best-practices.md#bkm_08)
     
   
--  [Workflow design: Using the Approval action effectively](sharepoint-workflow-development-best-practices#bkm_09)
+-  [Workflow design: Using the Approval action effectively](sharepoint-workflow-development-best-practices.md#bkm_09)
     
   
 
@@ -144,7 +150,7 @@ When using impersonation steps in a workflow, you should author the workflow usi
   
     
     
-For more information, see  [Create a workflow with elevated permissions by using the SharePoint Workflow platform](create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo).
+For more information, see  [Create a workflow with elevated permissions by using the SharePoint Workflow platform](create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md).
   
     
     
@@ -177,13 +183,13 @@ Where possible, instead of creating multiple **Approval** actions, it is more ef
 <a name="bk_addresources"> </a>
 
 
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/sharepoint-workflow-fundamentals.md b/docs/general-development/sharepoint-workflow-fundamentals.md
index f5b7ed53cb..f135149741 100644
--- a/docs/general-development/sharepoint-workflow-fundamentals.md
+++ b/docs/general-development/sharepoint-workflow-fundamentals.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint workflow fundamentals
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1e622296-f78b-4e3a-a1e7-8effa24111a8
 ---
 
@@ -56,7 +57,7 @@ Workflow Manager Client 1.0, SharePoint, and SharePoint Designer 2013 each provi
 ## Platform architecture
 <a name="bkm_Architecture"> </a>
 
-Figure 1 depicts a high-level view of the SharePoint workflow framework. Notice, first, how the new workflow infrastructure introduces Workflow Manager Client 1.0 as the new workflow execution host. Whereas in previous versions workflow execution was hosted in SharePoint itself, this has changed in SharePoint. Workflow Manager Client 1.0 is external to SharePoint and communicates using common protocols over the Microsoft Azure service bus, mediated by OAuth. Otherwise, SharePoint includes the feature that you would expect to see: content items, events, apps, and so on. But notice that there is also an implementation of the SharePoint 2010 workflow host (that is, the Windows Workflow Foundation 3 engine) for backward compatibility. You can read more about this in  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint).
+Figure 1 depicts a high-level view of the SharePoint workflow framework. Notice, first, how the new workflow infrastructure introduces Workflow Manager Client 1.0 as the new workflow execution host. Whereas in previous versions workflow execution was hosted in SharePoint itself, this has changed in SharePoint. Workflow Manager Client 1.0 is external to SharePoint and communicates using common protocols over the Microsoft Azure service bus, mediated by OAuth. Otherwise, SharePoint includes the feature that you would expect to see: content items, events, apps, and so on. But notice that there is also an implementation of the SharePoint 2010 workflow host (that is, the Windows Workflow Foundation 3 engine) for backward compatibility. You can read more about this in  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint.md).
   
     
     
@@ -70,7 +71,7 @@ Figure 1 depicts a high-level view of the SharePoint workflow framework. Notice,
   
     
     
-![High-level workflow architecture](../../images/wfArchitecture1.png)
+![High-level workflow architecture](../images/wfArchitecture1.png)
   
     
     
@@ -229,7 +230,7 @@ This is important because you may have SharePoint 2010 that you may use to reuse
   
     
     
-For a full discussion of SharePoint workflow interop, see  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint).
+For a full discussion of SharePoint workflow interop, see  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint.md).
   
     
     
@@ -238,22 +239,22 @@ For a full discussion of SharePoint workflow interop, see  [Use workflow interop
 <a name="bk_additional"> </a>
 
 
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
--  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint)
+-  [Use workflow interop for SharePoint](use-workflow-interop-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/sharepoint-workflow-object-model.md b/docs/general-development/sharepoint-workflow-object-model.md
index 0d8c125d7c..92cf21cdc2 100644
--- a/docs/general-development/sharepoint-workflow-object-model.md
+++ b/docs/general-development/sharepoint-workflow-object-model.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint workflow object model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: be615a89-3201-4cd8-bbc7-15f3abf9f668
 ---
 
@@ -115,10 +116,10 @@ Reference content for SharePoint schemas is contained in the reference node enti
 -  [Windows Workflow Foundation (WF) Screencasts](http://msdn.microsoft.com/en-us/netframework/dd733248)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/sharepoint-workflow-samples.md b/docs/general-development/sharepoint-workflow-samples.md
index 30e5bc4296..9eccbccfc6 100644
--- a/docs/general-development/sharepoint-workflow-samples.md
+++ b/docs/general-development/sharepoint-workflow-samples.md
@@ -1,6 +1,7 @@
 ---
 title: SharePoint workflow samples
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ffaccd6b-426d-4ca0-b62f-bc7b14641a49
 ---
 
@@ -74,16 +75,16 @@ You can locate the sample code here:  [SharePoint workflow: Workflow OM in a Sha
 <a name="bkm_additional"> </a>
 
 
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager)
+-  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md)
     
   
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
 -  [SharePoint Add-ins](http://msdn.microsoft.com/library/cd1eda9e-8e54-4223-93a9-a6ea0d18df70%28Office.15%29.aspx)
diff --git a/docs/general-development/social-and-collaboration-features-in-sharepoint.md b/docs/general-development/social-and-collaboration-features-in-sharepoint.md
index 02d9fb8103..618e67dcc5 100644
--- a/docs/general-development/social-and-collaboration-features-in-sharepoint.md
+++ b/docs/general-development/social-and-collaboration-features-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Social and collaboration features in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5060f676-9aaa-41fe-88ef-e862ee2e1c52
 ---
 
@@ -17,7 +18,7 @@ The social and collaboration features on My Sites, team sites, and Community Sit
 ### My Site and team site features in SharePoint
 <a name="bkmk_Social"> </a>
 
-On My Site and team sites, the interactive newsfeed can help users keep current with people and content through real-time microblog messages and status updates. My Site also acts as a central location where users can track their tasks and access the documents and sites they are following. See  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint) to learn about SharePoint APIs that you can use to develop with My Site features.
+On My Site and team sites, the interactive newsfeed can help users keep current with people and content through real-time microblog messages and status updates. My Site also acts as a central location where users can track their tasks and access the documents and sites they are following. See  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md) to learn about SharePoint APIs that you can use to develop with My Site features.
   
     
     
@@ -25,7 +26,7 @@ On My Site and team sites, the interactive newsfeed can help users keep current
 ### Community Site features in SharePoint
 <a name="bkmk_Collab"> </a>
 
-People can use the rich, forum-like experience in Community Sites to find and share information and ideas, find people with similar interests, and build reputation. You use SharePoint site and list APIs directly to extend Community Site features because the Community Site feature doesn't expose a specific API. We describe development scenarios for Community Sites in  [What's new for developers in social and collaboration features](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201#bkmk_Collab).
+People can use the rich, forum-like experience in Community Sites to find and share information and ideas, find people with similar interests, and build reputation. You use SharePoint site and list APIs directly to extend Community Site features because the Community Site feature doesn't expose a specific API. We describe development scenarios for Community Sites in  [What's new for developers in social and collaboration features](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md#bkmk_Collab).
   
     
     
@@ -34,22 +35,22 @@ People can use the rich, forum-like experience in Community Sites to find and sh
 <a name="bkmk_InThisSection"> </a>
 
 
--  [What's new for developers in social and collaboration features in SharePoint](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201)
+-  [What's new for developers in social and collaboration features in SharePoint](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
--  [Follow content in SharePoint](follow-content-in-sharepoint)
+-  [Follow content in SharePoint](follow-content-in-sharepoint.md)
     
   
--  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint)
+-  [Work with user profiles in SharePoint](work-with-user-profiles-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/social-feed-rest-api-reference-for-sharepoint.md b/docs/general-development/social-feed-rest-api-reference-for-sharepoint.md
index 344b3b8bd6..3e925a4226 100644
--- a/docs/general-development/social-feed-rest-api-reference-for-sharepoint.md
+++ b/docs/general-development/social-feed-rest-api-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Social feed REST API reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f1cb914f-1e91-4e23-bf53-d2ab323eac13
 ---
 
@@ -20,33 +21,33 @@ The endpoint URIs for most feed tasks begin with the **SocialRestFeedManager** r
 - The  `post` resource represents a specific thread or post. When used inline in the endpoint URI, it sets the context of the request to the specified thread or post. For example, `http://contoso.com/_api/social.feed/post/lock` locks the specified thread.
     
   
-If the resource endpoint takes a parameter, the parameter metadata is specified in the URI or in the request body. By default, the REST service returns responses formatted in the Atom protocol, but you can request the JSON format by using HTTP **Accept** headers. See [Example REST requests for feed tasks](social-feed-rest-api-reference-for-sharepoint#bk_exampleRequests) for examples of complete requests.
+If the resource endpoint takes a parameter, the parameter metadata is specified in the URI or in the request body. By default, the REST service returns responses formatted in the Atom protocol, but you can request the JSON format by using HTTP **Accept** headers. See [Example REST requests for feed tasks](social-feed-rest-api-reference-for-sharepoint.md#bk_exampleRequests) for examples of complete requests.
 ## Resource endpoints for feed tasks
 <a name="bk_Overview"> </a>
 
 
 |**Endpoint**|**Description**|
 |:-----|:-----|
-| [My](social-feed-rest-api-reference-for-sharepoint#bk_my)|Gets information about the current user.|
-| [My/Feed/Post](social-feed-rest-api-reference-for-sharepoint#bk_myFeedPost)|Creates a root post in the current user's feed.|
-| [My/Feed](social-feed-rest-api-reference-for-sharepoint#bk_myFeed)|Gets the feed of activity by the current user.|
-| [My/News](social-feed-rest-api-reference-for-sharepoint#bk_myNews)|Gets the feed of activity by the current user and by people and content the user is following.|
-| [My/TimelineFeed](social-feed-rest-api-reference-for-sharepoint#bk_myTimelineFeed)|Gets the feed of activity by the current user and by people and content the user is following, sorted by created date.|
-| [My/Likes](social-feed-rest-api-reference-for-sharepoint#bk_myLikes)|Gets the feed of posts that the current user likes.|
-| [My/MentionFeed](social-feed-rest-api-reference-for-sharepoint#bk_myMentionFeed)|Gets the feed of posts that mention the current user.|
-| [My/MentionFeed/ClearUnreadMentionCount](social-feed-rest-api-reference-for-sharepoint#bk_myMentionFeedClearUnreadMentionCount)|Gets the feed of posts that mention the current user and clears the unread mention count.|
-| [My/UnreadMentionCount](social-feed-rest-api-reference-for-sharepoint#bk_myUnreadMentionCount)|Gets the count of unread mentions for the current user.|
-| [Actor](social-feed-rest-api-reference-for-sharepoint#bk_actor)|Gets information about the specified user and the current user.|
-| [Actor/Feed](social-feed-rest-api-reference-for-sharepoint#bk_actorFeed)|Gets the feed of activity by the specified user.|
-| [Actor/Feed/Post](social-feed-rest-api-reference-for-sharepoint#bk_actorFeedPost)|Creates a root post in the specified site feed.|
-| [Post](social-feed-rest-api-reference-for-sharepoint#bk_post)|Gets a full thread that contains the specified post.|
-| [Post/Reply](social-feed-rest-api-reference-for-sharepoint#bk_postReply)|Posts a reply to the specified post.|
-| [Post/Delete](social-feed-rest-api-reference-for-sharepoint#bk_postDelete)|Deletes the specified post.|
-| [Post/Like](social-feed-rest-api-reference-for-sharepoint#bk_postLike)|Makes the current user a liker of the specified post.|
-| [Post/Unlike](social-feed-rest-api-reference-for-sharepoint#bk_postUnlike)|Removes the current user from the list of likers for the specified post.|
-| [Post/Likers](social-feed-rest-api-reference-for-sharepoint#bk_postLikers)|Gets the users who like the specified post.|
-| [Post/Lock](social-feed-rest-api-reference-for-sharepoint#bk_postLock)|Locks the specified thread.|
-| [Post/Unlock](social-feed-rest-api-reference-for-sharepoint#bk_postUnlock)|Unlocks the specified thread.|
+| [My](social-feed-rest-api-reference-for-sharepoint.md#bk_my)|Gets information about the current user.|
+| [My/Feed/Post](social-feed-rest-api-reference-for-sharepoint.md#bk_myFeedPost)|Creates a root post in the current user's feed.|
+| [My/Feed](social-feed-rest-api-reference-for-sharepoint.md#bk_myFeed)|Gets the feed of activity by the current user.|
+| [My/News](social-feed-rest-api-reference-for-sharepoint.md#bk_myNews)|Gets the feed of activity by the current user and by people and content the user is following.|
+| [My/TimelineFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_myTimelineFeed)|Gets the feed of activity by the current user and by people and content the user is following, sorted by created date.|
+| [My/Likes](social-feed-rest-api-reference-for-sharepoint.md#bk_myLikes)|Gets the feed of posts that the current user likes.|
+| [My/MentionFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_myMentionFeed)|Gets the feed of posts that mention the current user.|
+| [My/MentionFeed/ClearUnreadMentionCount](social-feed-rest-api-reference-for-sharepoint.md#bk_myMentionFeedClearUnreadMentionCount)|Gets the feed of posts that mention the current user and clears the unread mention count.|
+| [My/UnreadMentionCount](social-feed-rest-api-reference-for-sharepoint.md#bk_myUnreadMentionCount)|Gets the count of unread mentions for the current user.|
+| [Actor](social-feed-rest-api-reference-for-sharepoint.md#bk_actor)|Gets information about the specified user and the current user.|
+| [Actor/Feed](social-feed-rest-api-reference-for-sharepoint.md#bk_actorFeed)|Gets the feed of activity by the specified user.|
+| [Actor/Feed/Post](social-feed-rest-api-reference-for-sharepoint.md#bk_actorFeedPost)|Creates a root post in the specified site feed.|
+| [Post](social-feed-rest-api-reference-for-sharepoint.md#bk_post)|Gets a full thread that contains the specified post.|
+| [Post/Reply](social-feed-rest-api-reference-for-sharepoint.md#bk_postReply)|Posts a reply to the specified post.|
+| [Post/Delete](social-feed-rest-api-reference-for-sharepoint.md#bk_postDelete)|Deletes the specified post.|
+| [Post/Like](social-feed-rest-api-reference-for-sharepoint.md#bk_postLike)|Makes the current user a liker of the specified post.|
+| [Post/Unlike](social-feed-rest-api-reference-for-sharepoint.md#bk_postUnlike)|Removes the current user from the list of likers for the specified post.|
+| [Post/Likers](social-feed-rest-api-reference-for-sharepoint.md#bk_postLikers)|Gets the users who like the specified post.|
+| [Post/Lock](social-feed-rest-api-reference-for-sharepoint.md#bk_postLock)|Locks the specified thread.|
+| [Post/Unlock](social-feed-rest-api-reference-for-sharepoint.md#bk_postUnlock)|Unlocks the specified thread.|
    
 
 > **Note:**
@@ -84,7 +85,7 @@ None.
 
 ### Response
 
-Type:  [SP.Social.SocialRestActor](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestActor)
+Type:  [SP.Social.SocialRestActor](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestActor)
   
     
     
@@ -144,7 +145,7 @@ Creates a root post in the current user's feed.
   
     
     
-You can post only in the context of the current user. You cannot create a root post in a different user's feed, but you can reply to another user's post. See  [Post/Reply](social-feed-rest-api-reference-for-sharepoint#bk_postReply).
+You can post only in the context of the current user. You cannot create a root post in a different user's feed, but you can reply to another user's post. See  [Post/Reply](social-feed-rest-api-reference-for-sharepoint.md#bk_postReply).
   
     
     
@@ -169,7 +170,7 @@ You can post only in the context of the current user. You cannot create a root p
   
     
     
-Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestPostCreationData)
+Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestPostCreationData)
   
     
     
@@ -198,7 +199,7 @@ A **null** ID and the properties of the new post, as shown in the following exam
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -309,7 +310,7 @@ Gets the feed of activity by the current user ( **Personal** feed type).
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -324,7 +325,7 @@ You can use an **@** alias to pass special characters. For example, `<siteUri>/_
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -664,7 +665,7 @@ Gets the feed of activity by the current user and by people and content the user
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -679,7 +680,7 @@ You can use an **@** alias to pass special characters. For example, `<siteUri>/_
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -897,7 +898,7 @@ Gets the feed of activity by the current user and by people and content the user
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -912,7 +913,7 @@ You can use an **@** alias to pass special characters. For example, `<siteUri>/_
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -1066,7 +1067,7 @@ The following response example represents the current user's timeline feed, whic
 ## My/Likes
 <a name="bk_myLikes"> </a>
 
-Gets the feed of microblog posts that the current user likes, represented by **LikeReference** thread types. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds).
+Gets the feed of microblog posts that the current user likes, represented by **LikeReference** thread types. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md).
   
     
     
@@ -1088,7 +1089,7 @@ Gets the feed of microblog posts that the current user likes, represented by **L
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -1103,7 +1104,7 @@ You can optionally specify retrieval options in the query string. You can use an
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -1267,7 +1268,7 @@ The following response example represents a reference to a post that the current
 ## My/MentionFeed
 <a name="bk_myMentionFeed"> </a>
 
-Gets the feed of microblog posts that mention the current user, represented by **MentionReference** thread types. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds).
+Gets the feed of microblog posts that mention the current user, represented by **MentionReference** thread types. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md).
   
     
     
@@ -1289,7 +1290,7 @@ Gets the feed of microblog posts that mention the current user, represented by *
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -1304,7 +1305,7 @@ You can use an **@** alias to pass special characters. For example, `<siteUri>/_
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -1461,7 +1462,7 @@ The following response example represents one thread that mentions the current u
 ## My/MentionFeed/ClearUnreadMentionCount
 <a name="bk_myMentionFeedClearUnreadMentionCount"> </a>
 
-Gets the feed of microblog posts that mention the current user, represented by **MentionReference** thread types, and sets the user's unread mention count to 0. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds).
+Gets the feed of microblog posts that mention the current user, represented by **MentionReference** thread types, and sets the user's unread mention count to 0. See [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md).
   
     
     
@@ -1479,7 +1480,7 @@ Gets the feed of microblog posts that mention the current user, represented by *
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -1500,7 +1501,7 @@ This parameter must be sent as an empty string in the **data** attribute of the
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -1746,7 +1747,7 @@ You send the  _item_ parameter in the query string. You can use an **@** alias t
 
 ### Response
 
-Type:  [SP.Social.SocialRestActor](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestActor)
+Type:  [SP.Social.SocialRestActor](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestActor)
   
     
     
@@ -1850,7 +1851,7 @@ Gets the feed of activity by the specified user ( **Personal** feed type) or get
   
     
     
-Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions)
+Type:  [SP.Social.SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions)
   
     
     
@@ -1865,7 +1866,7 @@ You can use an **@** alias to pass special characters. For example, `<siteUri>/_
 
 ### Response
 
-Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed)
+Type:  [SP.Social.SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed)
   
     
     
@@ -2059,7 +2060,7 @@ Creates a root post in the specified site feed.
   
     
     
-You can post only in the context of the current user. You cannot create a root post in a different user's feed, but you can reply to another user's post. See  [Post/Reply](social-feed-rest-api-reference-for-sharepoint#bk_postReply).
+You can post only in the context of the current user. You cannot create a root post in a different user's feed, but you can reply to another user's post. See  [Post/Reply](social-feed-rest-api-reference-for-sharepoint.md#bk_postReply).
   
     
     
@@ -2084,7 +2085,7 @@ You can post only in the context of the current user. You cannot create a root p
   
     
     
-Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestPostCreationData)
+Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestPostCreationData)
   
     
     
@@ -2113,7 +2114,7 @@ A **null** ID and the properties of the new post, as shown in the following exam
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -2256,7 +2257,7 @@ The unique identifier of the post, as shown in the following example.
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -2401,7 +2402,7 @@ Posts a reply to the specified post.
   
     
     
-Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestPostCreationData)
+Type:  [SP.Social.SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestPostCreationData)
   
     
     
@@ -2430,7 +2431,7 @@ The ID of the post to reply to and the properties of the reply, as shown in the
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -2626,7 +2627,7 @@ The ID of the post to like, as shown in the following example.
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -2774,7 +2775,7 @@ The ID of the post to stop liking, as shown in the following example.
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -3006,7 +3007,7 @@ The ID of the thread to lock, as shown in the following example.
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -3155,7 +3156,7 @@ The ID of the thread to unlock, as shown in the following example.
 
 ### Response
 
-Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread)
+Type:  [SP.Social.SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread)
   
     
     
@@ -3571,16 +3572,16 @@ The following properties belong to the **SocialThread** object.
 <a name="bk_addresources"> </a>
 
 
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)
+-  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)
     
   
--  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint)
+-  [Work with social feeds in SharePoint](work-with-social-feeds-in-sharepoint.md)
     
   
--  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint)
+-  [Following people and content REST API reference for SharePoint](following-people-and-content-rest-api-reference-for-sharepoint.md)
     
   
 - To see the members in the **SP.Social** OData schema used by the SharePoint REST service, browse to `http://<siteUri>/_api/$metadata`.
diff --git a/docs/general-development/sorting-search-results-in-sharepoint.md b/docs/general-development/sorting-search-results-in-sharepoint.md
index 5fabc15986..557f404908 100644
--- a/docs/general-development/sorting-search-results-in-sharepoint.md
+++ b/docs/general-development/sorting-search-results-in-sharepoint.md
@@ -1,4 +1,8 @@
-
+---
+title: Sorting search results in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 
@@ -7,7 +11,7 @@
   
     
     
-![Conceptual overview topic](../../images/mod_icon_badge_conoverview.png)
+![Conceptual overview topic](../images/mod_icon_badge_conoverview.png)
   
     
     
@@ -67,7 +71,7 @@ If you have multiple values in  [SortList](https://msdn.microsoft.com/library/Mi
   
     
     
-Apart from the Query object model, SharePoint also provides a Search REST service that you can use to query the search index with your client or mobile applications. The Search REST service supports both HTTP POST and HTTP GET requests. For more information on how to construct URIs for these requests, see  [Querying with the Search REST service](sharepoint-search-rest-api-overview#bk_queryrest).
+Apart from the Query object model, SharePoint also provides a Search REST service that you can use to query the search index with your client or mobile applications. The Search REST service supports both HTTP POST and HTTP GET requests. For more information on how to construct URIs for these requests, see  [Querying with the Search REST service](sharepoint-search-rest-api-overview.md#bk_queryrest).
   
     
     
@@ -84,7 +88,7 @@ You can also influence the rank calculation in the query string, in one of two w
     
     
 
-- By using the **XRANK** operator available in [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference) and [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference). You can use **XRANK** to apply a conditional rank boosting if a specific query condition is met.
+- By using the **XRANK** operator available in [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference.md) and [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference.md). You can use **XRANK** to apply a conditional rank boosting if a specific query condition is met.
     
   
 - By choosing a relevance weight for dynamic ranking. When using FQL, you can specify an individual relevance weight for each **STRING** operator.
@@ -579,16 +583,16 @@ using (var context = new ClientContext("http://localhost"))
 <a name="bk_addresources"> </a>
 
 
--  [Search in SharePoint](search-in-sharepoint)
+-  [Search in SharePoint](search-in-sharepoint.md)
     
   
--  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference)
+-  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference.md)
     
   
--  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference)
+-  [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference.md)
     
   
--  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview)
+-  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview.md)
     
   
 -  [Overview of crawled and managed properties in SharePoint](http://technet.microsoft.com/en-us/library/jj219630%28office.15%29.aspx)
diff --git a/docs/general-development/step-1-creating-a-ecmascript-text-file.md b/docs/general-development/step-1-creating-a-ecmascript-text-file.md
index 7d47beaee0..bc6bd6d2ad 100644
--- a/docs/general-development/step-1-creating-a-ecmascript-text-file.md
+++ b/docs/general-development/step-1-creating-a-ecmascript-text-file.md
@@ -1,6 +1,7 @@
 ---
 title: Step 1 Creating a ECMAScript Text File
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f1c2b359-5b0d-467d-a863-6732e23863b9
 ---
 
diff --git a/docs/general-development/step-1-creating-a-project-and-adding-a-udf-reference.md b/docs/general-development/step-1-creating-a-project-and-adding-a-udf-reference.md
index 484b0660af..9d2e14cd3d 100644
--- a/docs/general-development/step-1-creating-a-project-and-adding-a-udf-reference.md
+++ b/docs/general-development/step-1-creating-a-project-and-adding-a-udf-reference.md
@@ -1,6 +1,7 @@
 ---
 title: Step 1 Creating a Project and Adding a UDF Reference
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4c6f1279-28df-45af-8488-42a6573d526d
 ---
 
@@ -112,27 +113,27 @@ The following steps show how to locate Microsoft.Office.Excel.Server.Udf.dll and
   
     
     
- [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf)
+ [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md)
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells)
+ [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells.md)
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/step-1-creating-the-web-service-client-project.md b/docs/general-development/step-1-creating-the-web-service-client-project.md
index 2e3ceeeae1..b9a7ffa918 100644
--- a/docs/general-development/step-1-creating-the-web-service-client-project.md
+++ b/docs/general-development/step-1-creating-the-web-service-client-project.md
@@ -1,6 +1,7 @@
 ---
 title: Step 1 Creating the Web Service Client Project
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1f0fc9fc-0db4-47bb-8204-a06777b84e76
 ---
 
@@ -65,31 +66,31 @@ In **Solution Explorer**, a file with the default name of Class1.cs has been add
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
 #### Other resources
 
 
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/step-2-adding-a-web-reference.md b/docs/general-development/step-2-adding-a-web-reference.md
index 9e7d35b229..2414384413 100644
--- a/docs/general-development/step-2-adding-a-web-reference.md
+++ b/docs/general-development/step-2-adding-a-web-reference.md
@@ -1,6 +1,7 @@
 ---
 title: Step 2 Adding a Web Reference
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e9175863-ddb4-4750-847d-d53cb59b33cb
 ---
 
@@ -38,7 +39,7 @@ Your application must have a means to communicate with the Web service and to lo
 5. Visual Studio downloads the service description and generates a proxy class to interface between your application and Excel Web Services. 
     
   
-6. For more information, see  [Accessing the SOAP API](accessing-the-soap-api).
+6. For more information, see  [Accessing the SOAP API](accessing-the-soap-api.md).
     
   
 
@@ -51,23 +52,23 @@ Your application must have a means to communicate with the Web service and to lo
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/step-2-adding-the-content-editor-and-excel-services-web-parts.md b/docs/general-development/step-2-adding-the-content-editor-and-excel-services-web-parts.md
index 9a41744d6c..4f214e0007 100644
--- a/docs/general-development/step-2-adding-the-content-editor-and-excel-services-web-parts.md
+++ b/docs/general-development/step-2-adding-the-content-editor-and-excel-services-web-parts.md
@@ -1,6 +1,7 @@
 ---
 title: Step 2 Adding the Content Editor and Excel Services Web Parts
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c9c66843-fd77-4a0d-a512-d936d15d4429
 ---
 
@@ -22,7 +23,7 @@ Next, display a workbook by using the Excel Services Web Part that you added to
 2. Add a Content Editor Web Part to the Web Parts Page that you just created.
     
   
-3. Feed the URL for the text file that you created in  [Step 1: Creating a ECMAScript Text File](step-1-creating-a-ecmascript-text-file) to the Content Editor Web Part. You do this by adding the URL for the text file that you uploaded to a trusted document library in [Step 1: Creating a ECMAScript Text File](step-1-creating-a-ecmascript-text-file). 
+3. Feed the URL for the text file that you created in  [Step 1: Creating a ECMAScript Text File](step-1-creating-a-ecmascript-text-file.md) to the Content Editor Web Part. You do this by adding the URL for the text file that you uploaded to a trusted document library in [Step 1: Creating a ECMAScript Text File](step-1-creating-a-ecmascript-text-file.md). 
     
     For example: 
     
diff --git a/docs/general-development/step-2-creating-a-managed-code-udf.md b/docs/general-development/step-2-creating-a-managed-code-udf.md
index 93c34e76a7..324a2320c6 100644
--- a/docs/general-development/step-2-creating-a-managed-code-udf.md
+++ b/docs/general-development/step-2-creating-a-managed-code-udf.md
@@ -1,9 +1,10 @@
 ---
 title: Step 2 Creating a Managed-Code UDF
+ms.date: 09/25/2017
 keywords: soap
 f1_keywords:
 - soap
-ms.prod: SHAREPOINT
+ms.prod: sharepoint
 ms.assetid: 3c9edf82-ee2d-41f0-9d66-e88e8dc0cc69
 ---
 
@@ -182,27 +183,27 @@ End Namespace
   
     
     
- [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference)
+ [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference.md)
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells)
+ [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells.md)
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/step-3-accessing-the-web-service.md b/docs/general-development/step-3-accessing-the-web-service.md
index e3777630d8..5968219a6a 100644
--- a/docs/general-development/step-3-accessing-the-web-service.md
+++ b/docs/general-development/step-3-accessing-the-web-service.md
@@ -1,6 +1,7 @@
 ---
 title: Step 3 Accessing the Web Service
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d27f654d-242f-4f34-8385-be857c170532
 ---
 
@@ -350,26 +351,26 @@ End Namespace
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
   
     
     
diff --git a/docs/general-development/step-3-deploying-and-enabling-udfs.md b/docs/general-development/step-3-deploying-and-enabling-udfs.md
index 449d50cb3f..28e0deea14 100644
--- a/docs/general-development/step-3-deploying-and-enabling-udfs.md
+++ b/docs/general-development/step-3-deploying-and-enabling-udfs.md
@@ -1,6 +1,7 @@
 ---
 title: Step 3 Deploying and Enabling UDFs
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1e5e2a0a-041a-481c-a18b-578562a60e24
 ---
 
@@ -13,7 +14,7 @@ In this step, you will:
     
 
 
-1. Deploy SampleUdf.dll, which you created in  [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf), to a folder on a computer that has Microsoft SharePoint Server 2010 installed.
+1. Deploy SampleUdf.dll, which you created in  [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md), to a folder on a computer that has Microsoft SharePoint Server 2010 installed.
     
   
 2. Allow user-defined functions (UDFs) to be called from a specific trusted location, for example, trusted Shared Documents location. 
@@ -128,7 +129,7 @@ If you change the **AllowUdfs** value to **true** after a session has started, t
   
     
     
-For more information about resetting IIS, see  [How to: Enable UDFs](how-to-enable-udfs).
+For more information about resetting IIS, see  [How to: Enable UDFs](how-to-enable-udfs.md).
   
     
     
@@ -142,27 +143,27 @@ For more information about resetting IIS, see  [How to: Enable UDFs](how-to-enab
   
     
     
- [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference)
+ [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference.md)
   
     
     
- [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf)
+ [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md)
   
     
     
- [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells)
+ [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells.md)
   
     
     
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/step-4-building-and-testing-the-application.md b/docs/general-development/step-4-building-and-testing-the-application.md
index fa6587ffba..d0ac75aa1d 100644
--- a/docs/general-development/step-4-building-and-testing-the-application.md
+++ b/docs/general-development/step-4-building-and-testing-the-application.md
@@ -1,6 +1,7 @@
 ---
 title: Step 4 Building and Testing the Application
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f2feeecb-1b4c-4049-be4e-11d414f13d9f
 ---
 
@@ -144,26 +145,26 @@ Console.ReadLine();
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
   
     
     
diff --git a/docs/general-development/step-4-testing-and-calling-udfs-from-cells.md b/docs/general-development/step-4-testing-and-calling-udfs-from-cells.md
index f7a0f83097..1d2784b546 100644
--- a/docs/general-development/step-4-testing-and-calling-udfs-from-cells.md
+++ b/docs/general-development/step-4-testing-and-calling-udfs-from-cells.md
@@ -1,6 +1,7 @@
----
+---
 title: Step 4 Testing and Calling UDFs from Cells
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: d3e6aa72-2eb8-4b4b-a0eb-273486890d00
 ---
 
@@ -19,7 +20,7 @@ In this step, you will test the SampleUdf.dll assembly you created, deployed, an
 2. Save the workbook to a SharePoint document library that is a trusted location.
     
     > **Note:**
-      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For information about how to trust a location, see the "Trusting a Location" section in  [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs). 
+      > It is assumed that you have already created a SharePoint document library and made it a trusted location. For information about how to trust a location, see the "Trusting a Location" section in  [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md). 
 3. Change parameters to recalculate the workbook.
     
   
@@ -116,27 +117,27 @@ In this step, you will test the SampleUdf.dll assembly you created, deployed, an
   
     
     
- [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference)
+ [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference.md)
   
     
     
- [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf)
+ [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md)
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
diff --git a/docs/general-development/supported-and-unsupported-features.md b/docs/general-development/supported-and-unsupported-features.md
index a013e4552f..4ff5ca2255 100644
--- a/docs/general-development/supported-and-unsupported-features.md
+++ b/docs/general-development/supported-and-unsupported-features.md
@@ -1,6 +1,7 @@
 ---
 title: Supported and Unsupported Features
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6e4acad6-7665-493c-94cc-d38684b2842f
 ---
 
@@ -134,7 +135,7 @@ In the following figure, clicking **Learn more about unsupported features** prov
   
     
     
-![Unsupported feature error message for VBA](../../images/aebc97ae-c886-4d50-94ff-238049a259c7.gif)
+![Unsupported feature error message for VBA](../images/aebc97ae-c886-4d50-94ff-238049a259c7.gif)
   
     
     
@@ -181,7 +182,7 @@ All other unsupported features continue to behave as they do in Office SharePoin
   
     
     
-![Unsupported feature error message for XML maps](../../images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif)
+![Unsupported feature error message for XML maps](../images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif)
   
     
     
@@ -199,19 +200,19 @@ Unlike workbooks with external links, charts with external links are blocked fro
   
     
     
- [Excel Services Overview](excel-services-overview)
+ [Excel Services Overview](excel-services-overview.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources)
+ [Excel Services Blogs, Forums, and Resources](excel-services-blogs-forums-and-resources.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md b/docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md
index 1fb4be60e6..bab1fe6df4 100644
--- a/docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md
+++ b/docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: The XLIFF interchange file format in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 660c0f07-7030-4576-957e-b9f2cd0fa895
 ---
 
@@ -94,13 +95,13 @@ The following example of an XML document in XLIFF interchange file format demons
 <a name="bk_addresources"> </a>
 
 
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
 - Code sample:  [SharePoint: Extract and insert bin-unit elements in XLIFF files](http://code.msdn.microsoft.com/SharePoint-Extract-fe686878)
     
   
--  [Machine Translation Services in SharePoint](machine-translation-services-in-sharepoint)
+-  [Machine Translation Services in SharePoint](machine-translation-services-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/themes-overview-for-sharepoint.md b/docs/general-development/themes-overview-for-sharepoint.md
index 309a7957de..1feb9a872f 100644
--- a/docs/general-development/themes-overview-for-sharepoint.md
+++ b/docs/general-development/themes-overview-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Themes overview for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ae585dd3-82fe-46bb-ac93-065edc0a16f4
 ---
 
@@ -116,16 +117,16 @@ You can create new designs by creating new list items in the Composed Looks list
 <a name="section4"> </a>
 
 
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
--  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+-  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
--  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint)
+-  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md)
     
   
--  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint)
+-  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
diff --git a/docs/general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional.md b/docs/general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional.md
index 37d51969a6..1f61aef030 100644
--- a/docs/general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional.md
+++ b/docs/general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional.md
@@ -1,6 +1,7 @@
----
+---
 title: Transfer a workflow between SharePoint Designer 2013 and Visio Professional 2013 (SharePoint 2010 Workflow platform)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: dbe6f019-b4f2-480f-a8e7-bcb8842ab924
 ---
 
@@ -18,7 +19,7 @@ Business analysts and process analysts who are already familiar with flowchartin
   
     
     
-![Translate business logic to workflow rules](../../images/spd15-wf-importFromVisio.png)
+![Translate business logic to workflow rules](../images/spd15-wf-importFromVisio.png)
   
     
     
@@ -63,7 +64,7 @@ You can visualize workflows in SharePoint Designer in two ways:
   
     
     
-![Workflow diagrams can be exported to Visio](../../images/spd15-wf-exportToVisio.png)
+![Workflow diagrams can be exported to Visio](../images/spd15-wf-exportToVisio.png)
   
     
     
@@ -89,7 +90,7 @@ To import a SharePoint workflow, do the following:
   
 2. On the **Workflows** tab, in the **Manage** group, click **Import from Visio**.
     
-  ![Import workflow](../../images/spd15-ImportFromVisio.JPG)
+  ![Import workflow](../images/spd15-ImportFromVisio.JPG)
   
 
   
@@ -117,7 +118,7 @@ The imported workflow appears in the SharePoint Designer full-screen workflow ed
   
     
     
-![Imported workflow](../../images/spd15-wf-PO.JPG)
+![Imported workflow](../images/spd15-wf-PO.JPG)
   
     
     
@@ -159,13 +160,13 @@ To export a workflow, do the following:
 <a name="bk_addresources"> </a>
 
 
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/trigger-expressions-syntax-in-sharepoint.md b/docs/general-development/trigger-expressions-syntax-in-sharepoint.md
index c4e82f1b73..eb3338cf56 100644
--- a/docs/general-development/trigger-expressions-syntax-in-sharepoint.md
+++ b/docs/general-development/trigger-expressions-syntax-in-sharepoint.md
@@ -1,3 +1,8 @@
+---
+title: Trigger expressions syntax in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 
@@ -242,10 +247,10 @@ There are two sets of constants that can be used with specific functions: **Date
 <a name="SP15triggerex_addresources"> </a>
 
 
--  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout)
+-  [Custom content processing with the Content Enrichment web service callout](custom-content-processing-with-the-content-enrichment-web-service-callout.md)
     
   
--  [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server)
+-  [How to: Use the Content Enrichment web service callout for SharePoint Server](how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md)
     
   
 
diff --git a/docs/general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md b/docs/general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md
index 3461e4710a..9f981bbc91 100644
--- a/docs/general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md
+++ b/docs/general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md
@@ -1,6 +1,7 @@
 ---
 title: Troubleshooting SharePoint Server workflow validation errors in Visio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c21cc3e2-45bd-4d34-a57d-dd0954436bd8
 ---
 
@@ -35,7 +36,7 @@ The following table lists all of the validation issues that can appear in the Is
 |A stage cannot be nested within any other shape.  <br/> |Stages are top-level shapes in SharePoint workflow diagrams. You cannot place a shape within any other container shape, including steps, loops, or other stages.  <br/> If possible, move the stage so that it is outside of all other container shapes and reconnect the stage. If you want to create a logical grouping of actions and conditions within a stage or loop, use a Step shape instead.  <br/> |
 |A stage can only be connected to another stage, condition shape, or a terminator.  <br/> |Stages can be connected only to other top-level shapes, including conditions, terminators, or other stages. A stage cannot be connected to actions, steps, or loops at the top level. Rearrange the workflow diagram so that the stage is connected only to other top-level shapes.  <br/> |
 |Stage, step, and loop containers cannot be overlapped.  <br/> |The boundaries of container shapes, such as stages, steps, and loops, cannot touch or overlap. If you want to include one container shape within another (for example, include a loop within a stage), be sure that the contained shape is entirely within the bounds of the container. If you do not want one container shape to be contained by the other, space out the shapes in your diagram so that the bounds of the container shapes no longer cross or touch each other.  <br/> |
-|Workflow shapes from other templates/versions are not valid workflow shapes.  <br/> |You can use shapes only from the SharePoint Workflow Actions, SharePoint Workflow Conditions, and SharePoint Workflow Terminators stencils, and connectors that are created with AutoConnect or the Connector tool associated with the template in a Microsoft SharePoint Workflow diagram. All other shapes are not valid connections within the workflow validation rules. You can place other shapes on the design canvas as long as they are not connected to the Workflow.  <br/> If you need to include an action or condition that is not represented with a shape in one of the stencils associated with the Microsoft SharePoint Workflow template, consider creating a custom workflow action. Custom workflow actions can be created in Microsoft Visual Studio 2012 and incorporated into SharePoint workflows in SharePoint Designer 2013. For more information about how to create custom actions in Visual Studio 2012, see the article  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio).  <br/> |
+|Workflow shapes from other templates/versions are not valid workflow shapes.  <br/> |You can use shapes only from the SharePoint Workflow Actions, SharePoint Workflow Conditions, and SharePoint Workflow Terminators stencils, and connectors that are created with AutoConnect or the Connector tool associated with the template in a Microsoft SharePoint Workflow diagram. All other shapes are not valid connections within the workflow validation rules. You can place other shapes on the design canvas as long as they are not connected to the Workflow.  <br/> If you need to include an action or condition that is not represented with a shape in one of the stencils associated with the Microsoft SharePoint Workflow template, consider creating a custom workflow action. Custom workflow actions can be created in Microsoft Visual Studio 2012 and incorporated into SharePoint workflows in SharePoint Designer 2013. For more information about how to create custom actions in Visual Studio 2012, see the article  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md).  <br/> |
 |A shape cannot be connected outside of the start/end path of the current shape's container.  <br/> |All shapes contained within a stage, loop, or step must be entirely contained within that container shape. Shapes cannot connect to any shapes that are not contained in the same container. Rearrange the workflow diagram so that all actions, conditions, loops, and steps within the container shape connect to other shapes in the container.  <br/> If the shape must connect to an activity outside of the container, connect the shape to the Exit shape associated with the container.  <br/> |
 |Invalid transition shape.  <br/> |When a non-condition or non-stage shape is added at the base level of the workflow. Only stages and conditions may exist at the base level of a workflow. Any other shapes that are added to this level will cause this error. You should encapsulate non-condition and non-stage shapes in a condition or stage shape.  <br/> |
 |Stages, steps, and loops may have only one incoming and one outgoing connection.  <br/> |All container shapes can have only one incoming connector to the Enter shape that is associated with them. Similarly, container shapes can have only one outgoing connector from their Exit shape. Rearrange the diagram so that each container has a single incoming and outgoing path. You may need to add additional stages or Junction shapes to the workflow to fix this error.  <br/> |
@@ -48,13 +49,13 @@ The following table lists all of the validation issues that can appear in the Is
 <a name="VSSPD_Trouble_Additional"> </a>
 
 
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio)
+-  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 -  [Create, import, and export SharePoint workflows in Visio 2010](http://office.microsoft.com/en-us/visio-help/create-import-and-export-sharepoint-workflows-in-visio-HA101888007.aspx)
diff --git a/docs/general-development/understanding-coordination-actions-in-sharepoint-designer.md b/docs/general-development/understanding-coordination-actions-in-sharepoint-designer.md
index 63d80e0ce2..3b2a17bc00 100644
--- a/docs/general-development/understanding-coordination-actions-in-sharepoint-designer.md
+++ b/docs/general-development/understanding-coordination-actions-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Understanding Coordination actions in SharePoint Designer 2013
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 33fbcf91-0a5d-47ab-85a9-9d2d556a204d
 ---
 
@@ -38,7 +39,7 @@ Coordination Actions appear in the **Actions** drop-down menu when you build a w
   
     
     
-![Coordination Actions in SharePoint Designer](../../images/SPD15-CoordinationActions.png)
+![Coordination Actions in SharePoint Designer](../images/SPD15-CoordinationActions.png)
   
     
     
@@ -76,7 +77,7 @@ A Coordination Action includes three editable regions, as shown in the figure.
   
     
     
-![Start a List Workflow coordination action](../../images/SPD15-CoordinationActions2.png)
+![Start a List Workflow coordination action](../images/SPD15-CoordinationActions2.png)
   
     
     
@@ -108,7 +109,7 @@ Click an editable link to enter information. For example, to select the 2010 wor
   
     
     
-![Selecting a workflow based on the 2010 platform](../../images/SPD15-CoordinationActions3.png)
+![Selecting a workflow based on the 2010 platform](../images/SPD15-CoordinationActions3.png)
   
     
     
@@ -138,7 +139,7 @@ The SharePoint 2010 Workflow platform workflow instances that are coordinated fr
   
     
     
-![The workflow status page lists the subworkflows.](../../images/SPD15-CorrelationActions4.png)
+![The workflow status page lists the subworkflows.](../images/SPD15-CorrelationActions4.png)
   
     
     
@@ -161,7 +162,7 @@ The SharePoint 2010 Workflow platform workflow instances that are coordinated fr
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer)
+-  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer.md)
     
   
 
diff --git a/docs/general-development/understanding-dictionary-actions-in-sharepoint-designer.md b/docs/general-development/understanding-dictionary-actions-in-sharepoint-designer.md
index e3ecc45cf2..2520080260 100644
--- a/docs/general-development/understanding-dictionary-actions-in-sharepoint-designer.md
+++ b/docs/general-development/understanding-dictionary-actions-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Understanding Dictionary actions in SharePoint Designer 2013
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 73df233e-bad8-4ea1-b05d-61ecab597924
 ---
 
@@ -31,7 +32,7 @@ When you create a variable you need to tell the workflow engine what type of dat
   
     
     
-![A String variable](../../images/SPD-Dictionary-1a.png)
+![A String variable](../images/SPD-Dictionary-1a.png)
   
     
     
@@ -53,7 +54,7 @@ The figure illustrates the concept.
   
     
     
-![A Dictionary variable](../../images/SPD15-Dictionary-1b.png)
+![A Dictionary variable](../images/SPD15-Dictionary-1b.png)
   
     
     
@@ -101,7 +102,7 @@ The workflow actions for the Dictionary variable type can be found on the **Acti
   
     
     
-![Dictionary actions](../../images/SPD15-Dictionary-2.png)
+![Dictionary actions](../images/SPD15-Dictionary-2.png)
   
     
     
@@ -126,7 +127,7 @@ The figure shows the **Build a Dictionary** dialog box. Notice that three variab
   
     
     
-![Build a Dictionary dialog box](../../images/SPD15-BuildADictionaryDialog.png)
+![Build a Dictionary dialog box](../images/SPD15-BuildADictionaryDialog.png)
   
     
     
@@ -201,7 +202,7 @@ The figure shows the **Count Items in a Dictionary** workflow action.
   
     
     
-![Count items in a Dictionary.](../../images/SPD15-CountItemsInDictionary.png)
+![Count items in a Dictionary.](../images/SPD15-CountItemsInDictionary.png)
   
     
     
@@ -234,7 +235,7 @@ The figure shows the **Get an Item from a Dictionary** workflow action. Notice t
   
     
     
-![Get an item from a Dictionary.](../../images/SPD15-GetAnItemFromDictionary.png)
+![Get an item from a Dictionary.](../images/SPD15-GetAnItemFromDictionary.png)
   
     
     
diff --git a/docs/general-development/understanding-eventing-actions-in-sharepoint-designer.md b/docs/general-development/understanding-eventing-actions-in-sharepoint-designer.md
index 1b82b32e48..4979586d08 100644
--- a/docs/general-development/understanding-eventing-actions-in-sharepoint-designer.md
+++ b/docs/general-development/understanding-eventing-actions-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Understanding Eventing Actions in SharePoint Designer 2013
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: fe4ad8cf-2c6f-488d-8b33-6bf4357018ac
 ---
 
@@ -45,7 +46,7 @@ The Eventing actions are accessed in the **Action** drop-down menu of the ShareP
   
     
     
-![Eventing Actions in SharePoint Designer 2013](../../images/SPD15-EventingActions1.png)
+![Eventing Actions in SharePoint Designer 2013](../images/SPD15-EventingActions1.png)
   
     
     
@@ -59,7 +60,7 @@ The Eventing actions are accessed in the **Action** drop-down menu of the ShareP
   
     
     
-![Wait for Project Event action](../../images/SPD15-EventingActions4.png)
+![Wait for Project Event action](../images/SPD15-EventingActions4.png)
   
     
     
@@ -73,7 +74,7 @@ The Eventing actions are accessed in the **Action** drop-down menu of the ShareP
   
     
     
-![Selecting Wait for Field Change in Current Item.](../../images/wf15-eventingactions3.png)
+![Selecting Wait for Field Change in Current Item.](../images/wf15-eventingactions3.png)
   
     
     
@@ -114,7 +115,7 @@ The **Wait for Event in List Item** action contains two editable regions, as sho
   
     
     
-![Wait for event action in SharePoint Designer 2013](../../images/SPD15-EventingActions2.png)
+![Wait for event action in SharePoint Designer 2013](../images/SPD15-EventingActions2.png)
   
     
     
@@ -151,7 +152,7 @@ Clicking the **this item event** link opens the **Choose List Item Event** dialo
   
     
     
-![Choose List Item Event dialog](../../images/SPD15-EventingActions3.jpg)
+![Choose List Item Event dialog](../images/SPD15-EventingActions3.jpg)
   
     
     
@@ -184,7 +185,7 @@ The **Wait for Project Event** action contains one editable region, as shown in
   
     
     
-![Wait for Project Event in workflow](../../images/SPD15-EventingActions5.png)
+![Wait for Project Event in workflow](../images/SPD15-EventingActions5.png)
   
     
     
@@ -229,7 +230,7 @@ The **Wait for Field Change in Current Item** action contains two editable regio
   
     
     
-![Screenshot of eventing action.](../../images/wf15-eventingactions4.png)
+![Screenshot of eventing action.](../images/wf15-eventingactions4.png)
   
     
     
@@ -270,10 +271,10 @@ Once a field has changed the workflow continues.
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 
diff --git a/docs/general-development/understanding-excel-services-udfs.md b/docs/general-development/understanding-excel-services-udfs.md
index 9be4e15f48..2f77bdf322 100644
--- a/docs/general-development/understanding-excel-services-udfs.md
+++ b/docs/general-development/understanding-excel-services-udfs.md
@@ -1,6 +1,7 @@
----
+---
 title: Understanding Excel Services UDFs
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a1567278-fac4-4b3b-a814-56f2376c1217
 ---
 
@@ -119,7 +120,7 @@ Each Excel Services trusted location has an **AllowUdfs** flag.
     
 
 > **Note:**
-> The **AllowUdfs** flag is denoted by the **User-defined functions allowed** option on the Excel Services Trusted File Locations page. To learn how to navigate to the Trusted File Locations page, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs). 
+> The **AllowUdfs** flag is denoted by the **User-defined functions allowed** option on the Excel Services Trusted File Locations page. To learn how to navigate to the Trusted File Locations page, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md). 
   
     
     
@@ -152,7 +153,7 @@ To reload a UDF assembly, you can run **iisreset** or restart the Excel Calculat
     
 
 > **Caution:**
-> Resetting IIS will end all current sessions. > For more information, see  [How to: Enable UDFs](how-to-enable-udfs). 
+> Resetting IIS will end all current sessions. > For more information, see  [How to: Enable UDFs](how-to-enable-udfs.md). 
   
     
     
@@ -200,43 +201,43 @@ For more information about configuring code groups, as well as the **RequestMini
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
   
     
     
- [How to: Catch Exceptions](how-to-catch-exceptions)
+ [How to: Catch Exceptions](how-to-catch-exceptions.md)
   
     
     
- [How to: Enable UDFs](how-to-enable-udfs)
+ [How to: Enable UDFs](how-to-enable-udfs.md)
 #### Concepts
 
 
   
     
     
- [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf)
+ [Walkthrough: Developing a Managed-Code UDF](walkthrough-developing-a-managed-code-udf.md)
   
     
     
- [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs)
+ [Frequently Asked Questions About Excel Services UDFs](frequently-asked-questions-about-excel-services-udfs.md)
   
     
     
- [Excel Services Architecture](excel-services-architecture)
+ [Excel Services Architecture](excel-services-architecture.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Excel Services Best Practices](excel-services-best-practices)
+ [Excel Services Best Practices](excel-services-best-practices.md)
diff --git a/docs/general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint.md b/docs/general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint.md
index 829245b86d..787ed27c2f 100644
--- a/docs/general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint.md
+++ b/docs/general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Understanding how to package and deploy workflow in SharePoint
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 545b4930-ac05-4c9d-9980-5818cb800cf1
 ---
 
@@ -60,7 +61,7 @@ The process for packaging a workflow involves saving the workflow to a template
 
   
 
-  ![Packaging workflow in SPD 2013](../../images/SPD15-PackagingWorkflow1.png)
+  ![Packaging workflow in SPD 2013](../images/SPD15-PackagingWorkflow1.png)
   
 
   
@@ -75,7 +76,7 @@ The process for packaging a workflow involves saving the workflow to a template
 
   
 
-  ![Workflow template in Site Assets.](../../images/SPD15-PackagingWorkflow2.png)
+  ![Workflow template in Site Assets.](../images/SPD15-PackagingWorkflow2.png)
   
 
   
@@ -131,7 +132,7 @@ Before you can deploy a workflow you must first export the workflow template fro
 
   
 
-  ![Export workflow file from SPD.](../../images/SPD15-PackagingWorkflow3.png)
+  ![Export workflow file from SPD.](../images/SPD15-PackagingWorkflow3.png)
   
 
   
@@ -161,7 +162,7 @@ To deploy a workflow package follow this procedure.
 
   
 
-  ![Upload solution button.](../../images/SPD15-PackagingWorkflow4.png)
+  ![Upload solution button.](../images/SPD15-PackagingWorkflow4.png)
   
 
   
@@ -173,7 +174,7 @@ To deploy a workflow package follow this procedure.
 
   
 
-  ![Activate solution after upload.](../../images/SPD15-PackagingWorkflow5.png)
+  ![Activate solution after upload.](../images/SPD15-PackagingWorkflow5.png)
   
 
   
@@ -206,7 +207,7 @@ After a workflow solution has been activated for a site collection, it is availa
   
     
     
-![Activate site feature.](../../images/SPD15-PackagingWorkflow6.png)
+![Activate site feature.](../images/SPD15-PackagingWorkflow6.png)
   
     
     
@@ -232,10 +233,10 @@ After a workflow solution has been activated for a site collection, it is availa
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 -  [Blog article from the SharePoint Designer team: Workflow package and deploy scenario](http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/30/packaging-list-site-and-reusable-workflow-and-how-to-deploy-the-package.aspx)
diff --git a/docs/general-development/understanding-task-actions-in-sharepoint-designer.md b/docs/general-development/understanding-task-actions-in-sharepoint-designer.md
index e485d1b649..b40283aa46 100644
--- a/docs/general-development/understanding-task-actions-in-sharepoint-designer.md
+++ b/docs/general-development/understanding-task-actions-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Understanding Task Actions in SharePoint Designer 2013
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 6fd69e94-ebe1-4d5d-98db-b2f3ce16f098
 ---
 
@@ -44,7 +45,7 @@ The Task Actions are accessed in the **Action** drop-down menu of the SharePoint
   
     
     
-![Task Actions are available from the Action drop-down menu of the SharePoint Designer 2013 Preview ribbon](../../images/spd15-TaskActions1.png)
+![Task Actions are available from the Action drop-down menu of the SharePoint Designer 2013 Preview ribbon](../images/spd15-TaskActions1.png)
   
     
     
@@ -85,7 +86,7 @@ The **Assign a task** action is shown in the figure.
   
     
     
-!["Assign a task" action in SharePoint Designer 2013.](../../images/SPD15-TaskActions2.png)
+!["Assign a task" action in SharePoint Designer 2013.](../images/SPD15-TaskActions2.png)
   
     
     
@@ -121,7 +122,7 @@ The **Assign a task** action takes three inputs: the user to assign a task, the
   
     
     
-![Use the "Assign a task" dialog box to set the participant, task title, description, due date, task options, email options, and outcome options.](../../images/SPD15-TaskActions3.png)
+![Use the "Assign a task" dialog box to set the participant, task title, description, due date, task options, email options, and outcome options.](../images/SPD15-TaskActions3.png)
   
     
     
@@ -150,7 +151,7 @@ The **Start a task process** action is shown in the figure.
   
     
     
-![The "Start a task process" action takes two inputs: "users" and an "outcome" variable](../../images/SPD15-TaskActions4.png)
+![The "Start a task process" action takes two inputs: "users" and an "outcome" variable](../images/SPD15-TaskActions4.png)
   
     
     
@@ -183,7 +184,7 @@ The **Start a task process** action takes two inputs: the users that will partic
   
     
     
-![Use the "Start a Task Process" dialog box to set the participants, task title, description, due date, task options, email options, and outcome options.](../../images/SPD15-TaskActions5.png)
+![Use the "Start a Task Process" dialog box to set the participants, task title, description, due date, task options, email options, and outcome options.](../images/SPD15-TaskActions5.png)
   
     
     
@@ -206,10 +207,10 @@ The **Start a task process** action takes two inputs: the users that will partic
 -  [Getting started with SharePoint workflow](http://msdn.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8.aspx)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 
diff --git a/docs/general-development/unsupported-features-in-excel-services-rest-api.md b/docs/general-development/unsupported-features-in-excel-services-rest-api.md
index 2875c0a409..b810e9341a 100644
--- a/docs/general-development/unsupported-features-in-excel-services-rest-api.md
+++ b/docs/general-development/unsupported-features-in-excel-services-rest-api.md
@@ -1,6 +1,7 @@
 ---
 title: Unsupported Features in Excel Services REST API
-ms.prod: OFFICE365
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4139901f-255b-4556-b8c8-3d986a07c587
 ---
 
diff --git a/docs/general-development/upgrade-custom-themes-and-css-to-sharepoint.md b/docs/general-development/upgrade-custom-themes-and-css-to-sharepoint.md
index 93904d7a7c..8cba43d009 100644
--- a/docs/general-development/upgrade-custom-themes-and-css-to-sharepoint.md
+++ b/docs/general-development/upgrade-custom-themes-and-css-to-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Upgrade custom themes and CSS to SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8d1a4e3a-ae6f-41a5-bd80-3398ba541207
 ---
 
@@ -25,7 +26,7 @@ This article describes the issues that may occur when you try to use custom Shar
     
     
 
-For more information about themes, see  [Themes overview for SharePoint](themes-overview-for-sharepoint).
+For more information about themes, see  [Themes overview for SharePoint](themes-overview-for-sharepoint.md).
   
     
     
@@ -41,7 +42,7 @@ You cannot upgrade a THMX file from SharePoint 2010 to SharePoint. If you applie
   
     
     
-For more information about creating themes customizations, see  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint) and [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint). You can also use the SharePoint color palette tool to help you create SharePoint designs. You can  [ download the SharePoint color palette tool](http://www.microsoft.com/en-us/download/details.aspx?id=38182) from the Microsoft Download Center.
+For more information about creating themes customizations, see  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md) and [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md). You can also use the SharePoint color palette tool to help you create SharePoint designs. You can  [ download the SharePoint color palette tool](http://www.microsoft.com/en-us/download/details.aspx?id=38182) from the Microsoft Download Center.
   
     
     
@@ -60,7 +61,7 @@ You can also decide to use one of the preinstalled SharePoint themes. For more i
 ## Upgrading customized master pages
 <a name="MasterPages"> </a>
 
-When you upgrade a SharePoint 2010 site to SharePoint, the site is configured to use the default master page for SharePoint. If you had a custom master page for your SharePoint 2010 site, it still resides in the site and you can apply it to the SharePoint site. You can use the SharePoint user interface or the **SPWeb** class to apply the custom master page to the upgraded site. For more information about how to change the master page, see [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint).
+When you upgrade a SharePoint 2010 site to SharePoint, the site is configured to use the default master page for SharePoint. If you had a custom master page for your SharePoint 2010 site, it still resides in the site and you can apply it to the SharePoint site. You can use the SharePoint user interface or the **SPWeb** class to apply the custom master page to the upgraded site. For more information about how to change the master page, see [How to: Apply a master page to a site in SharePoint](how-to-apply-a-master-page-to-a-site-in-sharepoint.md).
   
     
     
@@ -71,7 +72,7 @@ Consider the following before you decide whether to apply the SharePoint 2010 cu
 
 - **If the custom master page depends on custom CSS files:** Applying the custom master page to the upgraded site should return the site to its original 2010 experience. But, you will be unable to apply a SharePoint theme to the site.
     
-    If you want to use the custom master page and custom CSS files together with the SharePoint theming experience, you must update the CSS files to use the new SharePoint color slots. If you want to access the custom master page from the themes user interface, you also have to create a master page preview file. For more information, see  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint).
+    If you want to use the custom master page and custom CSS files together with the SharePoint theming experience, you must update the CSS files to use the new SharePoint color slots. If you want to access the custom master page from the themes user interface, you also have to create a master page preview file. For more information, see  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md).
     
   
 - **If the custom master page depends on SharePoint 2010 CSS files:** CSS files have changed significantly from SharePoint 2010 to SharePoint. In many cases, you will have to rework the master page so that it can work with new classes before you can successfully apply it to the upgraded site. For more information about CSS classes, see the **Using the host web CSS in apps for SharePoint** section in [SharePoint Add-ins UX design guidelines](http://msdn.microsoft.com/library/a4a8f53c-27d7-43dc-b6db-aa7b1f1c7d45%28Office.15%29.aspx).
@@ -86,13 +87,13 @@ Unmodified SharePoint 2010 CSS files and custom CSS files cannot be used on Shar
     
     
 
-- **Color slots**. The number of available color slots has increased significantly in SharePoint. You must update the color slots in SharePoint 2010 CSS files before they can be used in the new theming experience. For more information, see the  [Color slot mapping](color-palettes-and-fonts-in-sharepoint#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+- **Color slots**. The number of available color slots has increased significantly in SharePoint. You must update the color slots in SharePoint 2010 CSS files before they can be used in the new theming experience. For more information, see the  [Color slot mapping](color-palettes-and-fonts-in-sharepoint.md#colorSlots) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
     
   
-- **Font slots**. You should review the list of available font slots and verify that the CSS files you want to use in SharePoint are using the correct font slots. For more information, see the  [Font slots](color-palettes-and-fonts-in-sharepoint#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint).
+- **Font slots**. You should review the list of available font slots and verify that the CSS files you want to use in SharePoint are using the correct font slots. For more information, see the  [Font slots](color-palettes-and-fonts-in-sharepoint.md#fontSlot) section in [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md).
     
   
-- **New annotation**. SharePoint has a new annotation that lets you replace the background image. For more information, see  [How to: Make custom CSS files themable in SharePoint](how-to-make-custom-css-files-themable-in-sharepoint).
+- **New annotation**. SharePoint has a new annotation that lets you replace the background image. For more information, see  [How to: Make custom CSS files themable in SharePoint](how-to-make-custom-css-files-themable-in-sharepoint.md).
     
   
 - **New classes**. You may have to update CSS files to work with the new classes in SharePoint. For more information about CSS classes (also referred to as CSS styles), see the **Using the host web CSS in apps for SharePoint** section in [SharePoint Add-ins UX design guidelines](http://msdn.microsoft.com/library/a4a8f53c-27d7-43dc-b6db-aa7b1f1c7d45%28Office.15%29.aspx).
@@ -103,22 +104,22 @@ Unmodified SharePoint 2010 CSS files and custom CSS files cannot be used on Shar
 <a name="addresources"> </a>
 
 
--  [Themes overview for SharePoint](themes-overview-for-sharepoint)
+-  [Themes overview for SharePoint](themes-overview-for-sharepoint.md)
     
   
--  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint)
+-  [How to: Create a master page preview file in SharePoint](how-to-create-a-master-page-preview-file-in-sharepoint.md)
     
   
--  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint)
+-  [How to: Deploy a custom theme in SharePoint](how-to-deploy-a-custom-theme-in-sharepoint.md)
     
   
--  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint)
+-  [Color palettes and fonts in SharePoint](color-palettes-and-fonts-in-sharepoint.md)
     
   
 -  [SharePoint Team Blog: Show off your style with SharePoint theming](http://blogs.office.com/b/sharepoint/archive/2012/10/29/show-off-your-style-with-sharepoint-theming.aspx)
     
   
--  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities)
+-  [SharePoint Design Manager branding and design capabilities](sharepoint-design-manager-branding-and-design-capabilities.md)
     
   
 
diff --git a/docs/general-development/upgrade-site-customizations-for-sharepoint.md b/docs/general-development/upgrade-site-customizations-for-sharepoint.md
index c579aa3153..def2e9d508 100644
--- a/docs/general-development/upgrade-site-customizations-for-sharepoint.md
+++ b/docs/general-development/upgrade-site-customizations-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Upgrade site customizations for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 4b515860-69ae-4af8-8013-cd071c0ddca6
 ---
 
@@ -34,7 +35,7 @@ Table 1 lists the possible after-upgrade problems for custom components and info
 |:-----|:-----|
 |CSS styles  <br/> |During upgrade, your site will revert to the CSS files referred to in the default.master page. As a result, any customizations you have made to the appearance of your pages will change, and pages will render with the default styles found in a default installation.  <br/> |
 |Themes  <br/> |For SharePoint 2010, you may have created custom themes that define a corporate branding for an entire site. You create these as .thmx files that can be uploaded to the site collection and applied by the administrator.  <br/> In SharePoint, the theming engine has been completely redesigned to be more flexible and powerful and to provide for easier future upgrades. As a result of this redesign, upgrading from SharePoint 2010 to SharePoint themes is not supported and will require you to re-create them for SharePoint.  <br/> |
-|Web templates  <br/> |Web templates were introduced in SharePoint 2010 to provide a way to package features, layouts, styles, and other components that you can then use to create new webs. They are similar in function to creating site definitions, but with web templates, you can add publishing features.  <br/> Due to the changes made in SharePoint, your customized web templates will not work immediately after upgrade.  <br/> To see what changes have been made to web templates and to fix issues resulting from this, see  [Upgrade web templates for SharePoint](upgrade-web-templates-for-sharepoint) for recommendations and best practices. <br/> |
+|Web templates  <br/> |Web templates were introduced in SharePoint 2010 to provide a way to package features, layouts, styles, and other components that you can then use to create new webs. They are similar in function to creating site definitions, but with web templates, you can add publishing features.  <br/> Due to the changes made in SharePoint, your customized web templates will not work immediately after upgrade.  <br/> To see what changes have been made to web templates and to fix issues resulting from this, see  [Upgrade web templates for SharePoint](upgrade-web-templates-for-sharepoint.md) for recommendations and best practices. <br/> |
 |Master pages  <br/> |During upgrade, any references to custom master pages you have created are reverted back to the default.master page. This may cause errors in SharePoint due to references on the custom page to missing components.  <br/> To fix this, you have to change the references to any custom master pages.  <br/> |
    
 
diff --git a/docs/general-development/upgrade-web-templates-for-sharepoint.md b/docs/general-development/upgrade-web-templates-for-sharepoint.md
index fc542c76b4..00074f0d20 100644
--- a/docs/general-development/upgrade-web-templates-for-sharepoint.md
+++ b/docs/general-development/upgrade-web-templates-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Upgrade web templates for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 69048e4c-6d6d-4e4e-b74c-7c72ae444354
 ---
 
@@ -141,7 +142,7 @@ To add the default functionality back to the template, you must modify the Onet.
 <a name="bk_addresources"> </a>
 
 
--  [Upgrade site customizations for SharePoint](upgrade-site-customizations-for-sharepoint)
+-  [Upgrade site customizations for SharePoint](upgrade-site-customizations-for-sharepoint.md)
     
   
 -  [SharePoint 2010 and web templates](http://blogs.msdn.com/b/vesku/archive/2010/10/14/sharepoint-2010-and-web-templates.aspx)
diff --git a/docs/general-development/urls-and-tokens-in-sharepoint.md b/docs/general-development/urls-and-tokens-in-sharepoint.md
index 6769fde99f..12cd8461d6 100644
--- a/docs/general-development/urls-and-tokens-in-sharepoint.md
+++ b/docs/general-development/urls-and-tokens-in-sharepoint.md
@@ -1,4 +1,8 @@
-
+---
+title: URLs and tokens in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 
diff --git a/docs/general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md b/docs/general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md
index a878d8eba4..fcb719bd60 100644
--- a/docs/general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md
+++ b/docs/general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md
@@ -1,6 +1,7 @@
 ---
 title: Use Feature upgrade to apply new SharePoint master pages when upgrading from SharePoint 2010
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: de3169f1-715e-4f80-bfbf-caea744e2a0b
 ---
 
@@ -77,7 +78,7 @@ In either case, during upgrade any custom master pages you've created will rever
 
   
 
-  ![After you create an event receiver to your feature, a code file appears under the feature.](../../images/SP15_FeatureReceiverVS.png)
+  ![After you create an event receiver to your feature, a code file appears under the feature.](../images/SP15_FeatureReceiverVS.png)
   
 
     This file contains a commented and empty  `FeatureUpgrading` method. You'll use this method in the following step.
@@ -137,7 +138,7 @@ Once you're done with the upgrade, you'll want to think about the future and lon
 -  [Deploy custom features to upgraded site collections in SharePoint](http://technet.microsoft.com/en-us/library/dn673579%28v=office.15%29.aspx)
     
   
--  [Upgrade site customizations for SharePoint](upgrade-site-customizations-for-sharepoint)
+-  [Upgrade site customizations for SharePoint](upgrade-site-customizations-for-sharepoint.md)
     
   
 -  [Upgrade to SharePoint](http://technet.microsoft.com/en-us/library/cc303420%28v=office.15%29.aspx)
diff --git a/docs/general-development/use-workflow-interop-for-sharepoint.md b/docs/general-development/use-workflow-interop-for-sharepoint.md
index 2bb44d8f90..335c354456 100644
--- a/docs/general-development/use-workflow-interop-for-sharepoint.md
+++ b/docs/general-development/use-workflow-interop-for-sharepoint.md
@@ -1,3 +1,8 @@
+---
+title: Use workflow interop for SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # Use workflow interop for SharePoint
@@ -9,7 +14,7 @@ Provides a discussion of using SharePoint workflow Interop in the Visual Studio
 
 
 > **Important:**
-> To learn about using SharePoint workflow interop functionality in SharePoint Designer 2013, see  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer). 
+> To learn about using SharePoint workflow interop functionality in SharePoint Designer 2013, see  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer.md). 
   
     
     
@@ -36,7 +41,7 @@ SharePoint workflow interop enables SharePoint 2010 workflows (built on Windows
   
     
     
-![Workflow interop bridge](../../images/wfInteropBridge.png)
+![Workflow interop bridge](../images/wfInteropBridge.png)
   
     
     
@@ -62,7 +67,7 @@ Let's walk through the process depicted in Figure 1. Use the letters to referenc
 
   
 
-  ![Start a 2010 workflow](../../images/wfInterop_Stage1.png)
+  ![Start a 2010 workflow](../images/wfInterop_Stage1.png)
   
 
     
@@ -85,7 +90,7 @@ Let's walk through the process depicted in Figure 1. Use the letters to referenc
 
   
 
-  ![Setting properties on a Start Workflow activity](../../images/wfInterop_.png)
+  ![Setting properties on a Start Workflow activity](../images/wfInterop_.png)
   
 
   
@@ -140,7 +145,7 @@ The activity is in fact a sequence of messages that take place between the Workf
   
     
     
-![Workflow interop messaging](../../images/wfInteropMessaging.png)
+![Workflow interop messaging](../images/wfInteropMessaging.png)
   
     
     
@@ -157,13 +162,13 @@ The activity is in fact a sequence of messages that take place between the Workf
 <a name="bk_addresources"> </a>
 
 
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer)
+-  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer.md)
     
   
 -  [WorkflowInteropService](https://msdn.microsoft.com/library/Microsoft.SharePoint.WorkflowServices.WorkflowInteropService.aspx)
diff --git a/docs/general-development/user-segmentation-in-sharepoint.md b/docs/general-development/user-segmentation-in-sharepoint.md
index bcb27bf9f2..af9f4ab909 100644
--- a/docs/general-development/user-segmentation-in-sharepoint.md
+++ b/docs/general-development/user-segmentation-in-sharepoint.md
@@ -1,3 +1,8 @@
+---
+title: User segmentation in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 
@@ -55,7 +60,7 @@ Figure 1 shows the basic steps to add user segmentation functionality to your Sh
   
     
     
-![Steps to add user segmentation functionality](../../images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg)
+![Steps to add user segmentation functionality](../images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg)
   
     
     
diff --git a/docs/general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md b/docs/general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md
index 4e8b4a2719..5d2ff6e3b2 100644
--- a/docs/general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md
+++ b/docs/general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Using OData sources with Business Connectivity Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7a87e5bf-4428-4055-b113-7665a93e7326
 ---
 
@@ -81,7 +82,7 @@ To develop OData-based external content types, you will need the following:
 - Office Developer Tools for Visual Studio 2012
     
   
-For information about how to set up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint).
+For information about how to set up your development environment, see  [Set up a general development environment for SharePoint](set-up-a-general-development-environment-for-sharepoint.md).
   
     
     
@@ -93,7 +94,7 @@ For SharePoint to use the data exposed by a specific OData producer, an external
   
     
     
-Creating an external content type that uses an OData data source is similar to creating any external content type. You can use Visual Studio 2012 to automatically generate OData external content types. You merely provide the Representational State Transfer (REST) endpoint of the OData source when you create the external content type. For more information see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint).
+Creating an external content type that uses an OData data source is similar to creating any external content type. You can use Visual Studio 2012 to automatically generate OData external content types. You merely provide the Representational State Transfer (REST) endpoint of the OData source when you create the external content type. For more information see  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md).
   
     
     
@@ -102,13 +103,13 @@ Creating an external content type that uses an OData data source is similar to c
 <a name="SP15GetstartedOdata_inthissect"> </a>
 
 
--  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint)
+-  [How to: Create an external content type from an OData source in SharePoint](how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md)
     
   
--  [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system)
+-  [How to: Create an OData data service for use as a BCS external system](how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md)
     
   
--  [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint)
+-  [How to: Create an external list using an OData data source in SharePoint](how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md)
     
   
 
@@ -116,16 +117,16 @@ Creating an external content type that uses an OData data source is similar to c
 <a name="SP15GetstartedOdata_addres"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [External content types in SharePoint](external-content-types-in-sharepoint)
+-  [External content types in SharePoint](external-content-types-in-sharepoint.md)
     
   
--  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint)
+-  [What's new in Business Connectivity Services in SharePoint](what-s-new-in-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
 
diff --git a/docs/general-development/using-odata-with-excel-services-rest-in-sharepoint.md b/docs/general-development/using-odata-with-excel-services-rest-in-sharepoint.md
index 6ab90516fa..2f110eb9c9 100644
--- a/docs/general-development/using-odata-with-excel-services-rest-in-sharepoint.md
+++ b/docs/general-development/using-odata-with-excel-services-rest-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Using OData with Excel Services REST in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 8a20225a-323c-4420-bbb4-eef60aed4b42
 ---
 
@@ -50,7 +51,7 @@ http://\<serverName\>/_vti_bin/ExcelRest.aspx/Documents/ProductSales.xlsx/OData/
   
     
     
-For more information about how to use OData to request information from an Excel workbook stored on SharePoint Server, see  [Requesting Excel workbook data from SharePoint Server using OData](requesting-excel-workbook-data-from-sharepoint-server-using-odata).
+For more information about how to use OData to request information from an Excel workbook stored on SharePoint Server, see  [Requesting Excel workbook data from SharePoint Server using OData](requesting-excel-workbook-data-from-sharepoint-server-using-odata.md).
   
     
     
@@ -119,7 +120,7 @@ OData provides a simple way to get data from Excel workbooks that are stored on
 -  [What's new in Excel Services for developers](http://msdn.microsoft.com/library/09e96c8b-cb55-4fd1-a797-b50fbf0f9296.aspx)
     
   
--  [Requesting Excel workbook data from SharePoint Server using OData](requesting-excel-workbook-data-from-sharepoint-server-using-odata)
+-  [Requesting Excel workbook data from SharePoint Server using OData](requesting-excel-workbook-data-from-sharepoint-server-using-odata.md)
     
   
 -  [OData specification documentation](http://www.odata.org)
diff --git a/docs/general-development/using-the-pairing-cmdlet-register-spworkflowservice.md b/docs/general-development/using-the-pairing-cmdlet-register-spworkflowservice.md
index 462a295ac9..75ba895688 100644
--- a/docs/general-development/using-the-pairing-cmdlet-register-spworkflowservice.md
+++ b/docs/general-development/using-the-pairing-cmdlet-register-spworkflowservice.md
@@ -1,6 +1,7 @@
 ---
 title: Using the pairing cmdlet Register-SPWorkflowService
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 91fca6c2-60ca-4177-8560-2b310dac0e2c
 ---
 
diff --git a/docs/general-development/using-the-sharepoint-search-query-apis.md b/docs/general-development/using-the-sharepoint-search-query-apis.md
index 5a84a9efe2..c25fc5b208 100644
--- a/docs/general-development/using-the-sharepoint-search-query-apis.md
+++ b/docs/general-development/using-the-sharepoint-search-query-apis.md
@@ -1,6 +1,7 @@
 ---
 title: Using the SharePoint search Query APIs
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ae9d73ed-1140-430b-9287-01dbbe8ae7d1
 ---
 
@@ -45,7 +46,7 @@ Table 1 shows the APIs that you can use to program search queries and the path t
 |REST service endpoints  <br/> |http://server/_api/search/query <br/>http://server/_api/search/suggest  <br/> |
 |Server object model  <br/> |Microsoft.Office.Server.Search.dll <br/>%ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\ISAPI  <br/> |
    
-As a best practice in SharePoint development, use client APIs when you can. Client APIs include the .NET, Silverlight, Phone, and JavaScript client object models, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As a best practice in SharePoint development, use client APIs when you can. Client APIs include the .NET, Silverlight, Phone, and JavaScript client object models, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -126,7 +127,7 @@ The following is the access point for the service:  `http://server/_api/search/`
   
     
     
-See  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview) and [Retrieving query suggestions using the Search REST service](retrieving-query-suggestions-using-the-search-rest-service) for more information.
+See  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview.md) and [Retrieving query suggestions using the Search REST service](retrieving-query-suggestions-using-the-search-rest-service.md) for more information.
   
     
     
@@ -172,10 +173,10 @@ To download an example, see the following code sample posted by SharePoint MVP
 <a name="bk_addresources"> </a>
 
 
--  [Building search queries in SharePoint](building-search-queries-in-sharepoint)
+-  [Building search queries in SharePoint](building-search-queries-in-sharepoint.md)
     
   
--  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview)
+-  [SharePoint Search REST API overview](sharepoint-search-rest-api-overview.md)
     
   
 -  [SharePoint: Using the search REST service from an app for SharePoint](http://code.msdn.microsoft.com/sharepoint/SharePoint-Perform-a-1bf3e87d)
diff --git a/docs/general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform.md b/docs/general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform.md
index 5ac974b252..677ba7f44d 100644
--- a/docs/general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform.md
+++ b/docs/general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform.md
@@ -1,6 +1,7 @@
 ---
 title: Validation issues in Visio (SharePoint 2010 Workflow platform)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 416c8269-3c4e-40f4-bc20-a625f07a4dac
 ---
 
@@ -44,7 +45,7 @@ Example:
   
     
     
-![A custom action cannot be added.](../../images/spd15-wf-error1.JPG)
+![A custom action cannot be added.](../images/spd15-wf-error1.JPG)
   
     
     
@@ -76,7 +77,7 @@ Example:
   
     
     
-![A custom condition cannot be added](../../images/spd15-wf-error2.JPG)
+![A custom condition cannot be added](../images/spd15-wf-error2.JPG)
   
     
     
@@ -108,7 +109,7 @@ Example:
   
     
     
-![A compound condition cannot be manually added](../../images/spd15-wf-error3.JPG)
+![A compound condition cannot be manually added](../images/spd15-wf-error3.JPG)
   
     
     
@@ -140,7 +141,7 @@ Example:
   
     
     
-![Duplicate connections exist between shapes](../../images/spd15-wf-error4.JPG)
+![Duplicate connections exist between shapes](../images/spd15-wf-error4.JPG)
   
     
     
@@ -172,7 +173,7 @@ Example:
   
     
     
-![Loop back to parent shape is not allowed](../../images/spd15-wf-error5.JPG)
+![Loop back to parent shape is not allowed](../images/spd15-wf-error5.JPG)
   
     
     
@@ -204,7 +205,7 @@ Example:
   
     
     
-![Parallel activities that are also sequential](../../images/spd15-wf-error6.JPG)
+![Parallel activities that are also sequential](../images/spd15-wf-error6.JPG)
   
     
     
@@ -224,7 +225,7 @@ Example:
   
     
     
-![Avoid pointing to an activity from multiple paths](../../images/spd15-wf-error7.JPG)
+![Avoid pointing to an activity from multiple paths](../images/spd15-wf-error7.JPG)
   
     
     
@@ -240,7 +241,7 @@ To avoid having connectors point to the same activity from multiple paths, try d
   
     
     
-![Parallel activities that are also sequential](../../images/spd15-wf-error8.JPG)
+![Parallel activities that are also sequential](../images/spd15-wf-error8.JPG)
   
     
     
@@ -252,7 +253,7 @@ Example:
   
     
     
-![Parallel activities that are also sequential](../../images/spd15-wf-error9.JPG)
+![Parallel activities that are also sequential](../images/spd15-wf-error9.JPG)
   
     
     
@@ -268,7 +269,7 @@ If dealing with parallel blocks in sequential steps (usually found in workflows
   
     
     
-![Parallel activities that are also sequential](../../images/spd15-wf.JPG)
+![Parallel activities that are also sequential](../images/spd15-wf.JPG)
   
     
     
@@ -300,7 +301,7 @@ Example:
   
     
     
-![Condition shape does not have yes/no connections](../../images/spd15-wf-error11.JPG)
+![Condition shape does not have yes/no connections](../images/spd15-wf-error11.JPG)
   
     
     
@@ -332,7 +333,7 @@ Example:
   
     
     
-![Condition shape must have an outgoing connection](../../images/spd15-wf-error12.JPG)
+![Condition shape must have an outgoing connection](../images/spd15-wf-error12.JPG)
   
     
     
@@ -364,7 +365,7 @@ Example:
   
     
     
-![Ensure the correct connector is used](../../images/spd15-wf-error13.JPG)
+![Ensure the correct connector is used](../images/spd15-wf-error13.JPG)
   
     
     
@@ -396,7 +397,7 @@ Example:
   
     
     
-![Connector must be connected to two workflow shapes](../../images/spd15-wf-error14.JPG)
+![Connector must be connected to two workflow shapes](../images/spd15-wf-error14.JPG)
   
     
     
@@ -428,7 +429,7 @@ Example:
   
     
     
-![Diagram must only have one workflow and one start](../../images/spd15-wf-error15.JPG)
+![Diagram must only have one workflow and one start](../images/spd15-wf-error15.JPG)
   
     
     
@@ -460,7 +461,7 @@ Example:
   
     
     
-![The shape is not a SharePoint workflow shape](../../images/spd15-wf-error16.JPG)
+![The shape is not a SharePoint workflow shape](../images/spd15-wf-error16.JPG)
   
     
     
@@ -492,7 +493,7 @@ Example:
   
     
     
-![The start shape must not have incoming connections](../../images/spd15-wf-error17.JPG)
+![The start shape must not have incoming connections](../images/spd15-wf-error17.JPG)
   
     
     
@@ -524,7 +525,7 @@ Example:
   
     
     
-![Terminate shape must not have outgoing connections](../../images/spd15-wf-error18.JPG)
+![Terminate shape must not have outgoing connections](../images/spd15-wf-error18.JPG)
   
     
     
@@ -556,7 +557,7 @@ Example:
   
     
     
-![The workflow must have a start shape](../../images/spd15-wf-error19.JPG)
+![The workflow must have a start shape](../images/spd15-wf-error19.JPG)
   
     
     
@@ -588,7 +589,7 @@ Example:
   
     
     
-![Workflow shape is not connected to a terminate](../../images/spd15-wf-error20.JPG)
+![Workflow shape is not connected to a terminate](../images/spd15-wf-error20.JPG)
   
     
     
@@ -620,7 +621,7 @@ Example:
   
     
     
-![Workflow shape is not connected to the workflow](../../images/spd15-wf-error21.JPG)
+![Workflow shape is not connected to the workflow](../images/spd15-wf-error21.JPG)
   
     
     
@@ -657,13 +658,13 @@ Visio Professional 2013 can recognize a maximum of 10 levels of nested workflow
 <a name="bk_addresources"> </a>
 
 
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/virtual-directories-in-sharepoint-solutions.md b/docs/general-development/virtual-directories-in-sharepoint-solutions.md
index 82852395e3..680ec4662b 100644
--- a/docs/general-development/virtual-directories-in-sharepoint-solutions.md
+++ b/docs/general-development/virtual-directories-in-sharepoint-solutions.md
@@ -1,6 +1,7 @@
 ---
 title: Virtual directories in SharePoint solutions
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: c26c4160-31be-4358-89cf-082b8a1e6a6c
 ---
 
@@ -33,7 +34,7 @@ If you need to make your solution compatible with site collections of either mod
 <a name="bk_addresources"> </a>
 
 
--  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint)
+-  [Build farm solutions in SharePoint](build-farm-solutions-in-sharepoint.md)
     
   
 -  [Planning Deployment of Farm Solutions for SharePoint](http://blogs.technet.com/b/mspfe/archive/2013/02/04/planning-deployment-of-farm-solutions-for-sharepoint.aspx)
diff --git a/docs/general-development/visio-services-in-sharepoint.md b/docs/general-development/visio-services-in-sharepoint.md
index a80adf7d3f..72427cc298 100644
--- a/docs/general-development/visio-services-in-sharepoint.md
+++ b/docs/general-development/visio-services-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Visio Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ed8c5d12-e17d-4ceb-b195-601c26824370
 ---
 
@@ -22,7 +23,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|Visio 2013 introduces a new file format (.vsdx), based on the Open Packaging Conventions (OPC) standard (ISO 29500, Part 2) and the XML elements from the previous Visio XML file format (.vdx). It is a zipped, XML-based file format similar to the file formats used in other applications.  <br/> With the new file format, you can save a Visio 2013 drawing directly to a SharePoint Server or SharePoint Online library, without having to publish the file as a Visio Web Drawing (.vdw). Even so, Visio Services can still read and display Visio Web Drawing files.  <br/> Visio Services retains the ability to display the Visio Web Drawing (.vdw) format in the browser. It now also renders the new Visio drawing (.vsdx) and Visio macro-enabled drawing (.vsdm) formats.  <br/> The Visio ServicesECMAScript (JavaScript, JScript) object model contains a new API to support the new file format: the  [Vwa.VwaControl.getDiagramFileType Method](http://msdn.microsoft.com/library/fd8ca95f-a3be-4000-bce8-3aaf1f48148c%28Office.15%29.aspx). The methods returns a value from the  [Vwa.DiagramFileType Enumeration](http://msdn.microsoft.com/library/dd2f8a5d-a54b-44bd-a458-02efdcba0201%28Office.15%29.aspx) that indicates whether the file displayed in the Visio Web Access Web Part is a Visio drawing (.vsdx) or a Visio Web Drawing (.vdw). <br/> For more information about the new file format in Visio 2013, see  [Introduction to the Visio file format (.vsdx)](http://msdn.microsoft.com/library/69736f40-8f67-46c2-abf6-82dffecb2274%28Office.15%29.aspx).  <br/> **Note:** The new Visio files (.vsdx and .vsdm) are only displayed in raster format on Visio Services. Visio Web Drawings (.vdw) can still be displayed using Silverlight.           |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|Visio 2013 introduces a new file format (.vsdx), based on the Open Packaging Conventions (OPC) standard (ISO 29500, Part 2) and the XML elements from the previous Visio XML file format (.vdx). It is a zipped, XML-based file format similar to the file formats used in other applications.  <br/> With the new file format, you can save a Visio 2013 drawing directly to a SharePoint Server or SharePoint Online library, without having to publish the file as a Visio Web Drawing (.vdw). Even so, Visio Services can still read and display Visio Web Drawing files.  <br/> Visio Services retains the ability to display the Visio Web Drawing (.vdw) format in the browser. It now also renders the new Visio drawing (.vsdx) and Visio macro-enabled drawing (.vsdm) formats.  <br/> The Visio ServicesECMAScript (JavaScript, JScript) object model contains a new API to support the new file format: the  [Vwa.VwaControl.getDiagramFileType Method](http://msdn.microsoft.com/library/fd8ca95f-a3be-4000-bce8-3aaf1f48148c%28Office.15%29.aspx). The methods returns a value from the  [Vwa.DiagramFileType Enumeration](http://msdn.microsoft.com/library/dd2f8a5d-a54b-44bd-a458-02efdcba0201%28Office.15%29.aspx) that indicates whether the file displayed in the Visio Web Access Web Part is a Visio drawing (.vsdx) or a Visio Web Drawing (.vdw). <br/> For more information about the new file format in Visio 2013, see  [Introduction to the Visio file format (.vsdx)](http://msdn.microsoft.com/library/69736f40-8f67-46c2-abf6-82dffecb2274%28Office.15%29.aspx).  <br/> **Note:** The new Visio files (.vsdx and .vsdm) are only displayed in raster format on Visio Services. Visio Web Drawings (.vdw) can still be displayed using Silverlight.           |
    
 
 ### Support for Business Connectivity Services (BCS) data
@@ -31,7 +32,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|Visio 2013 diagrams can now be connected to external lists created using Microsoft Business Connectivity Services (BCS) on SharePoint servers and in SharePoint Online. Visio Services supports the ability to refresh the Visio diagrams as the data updates.  <br/> **Note:** Visio Services does not support SQL, SQL Azure, OLEDC, ODBC, and custom data providers as data sources in SharePoint Online.           |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|Visio 2013 diagrams can now be connected to external lists created using Microsoft Business Connectivity Services (BCS) on SharePoint servers and in SharePoint Online. Visio Services supports the ability to refresh the Visio diagrams as the data updates.  <br/> **Note:** Visio Services does not support SQL, SQL Azure, OLEDC, ODBC, and custom data providers as data sources in SharePoint Online.           |
    
 
 ### Commenting
@@ -40,7 +41,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|Visio 2013 includes a new commenting framework. Comments can now be associated with a particular shape or page. Visio Services includes JavaScript APIs to retrieve the comments from a diagram.  <br/> For more information about the commenting APIs in the Visio ServicesJavaScript object model, see the topics  [VwaPage.getPageComments Method](http://msdn.microsoft.com/library/d1e7740c-e0fa-4823-b2b6-14551bb84c36%28Office.15%29.aspx) and [VwaShape.getComments Method](http://msdn.microsoft.com/library/fcdec9c2-a503-4315-b048-033cd5ac09dd%28Office.15%29.aspx).  <br/> |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|Visio 2013 includes a new commenting framework. Comments can now be associated with a particular shape or page. Visio Services includes JavaScript APIs to retrieve the comments from a diagram.  <br/> For more information about the commenting APIs in the Visio ServicesJavaScript object model, see the topics  [VwaPage.getPageComments Method](http://msdn.microsoft.com/library/d1e7740c-e0fa-4823-b2b6-14551bb84c36%28Office.15%29.aspx) and [VwaShape.getComments Method](http://msdn.microsoft.com/library/fcdec9c2-a503-4315-b048-033cd5ac09dd%28Office.15%29.aspx).  <br/> |
    
 
 ### Expanded recalculation
@@ -49,7 +50,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|Visio Services can now recalculate formulas in the ShapeSheet. In addition to refreshing Data Graphics, Visio Services can refresh all shapes with data and visuals that depend upon data. Most ShapeSheet functions are supported for recalculation.  <br/> |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|Visio Services can now recalculate formulas in the ShapeSheet. In addition to refreshing Data Graphics, Visio Services can refresh all shapes with data and visuals that depend upon data. Most ShapeSheet functions are supported for recalculation.  <br/> |
    
 
 ### Improved error handling
@@ -58,7 +59,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|When a data refresh error occurs in a Visio drawing displayed in Visio Services, the display now falls back to a static image of the diagram. Visio Services also provides more actionable information in error messages.  <br/> |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|When a data refresh error occurs in a Visio drawing displayed in Visio Services, the display now falls back to a static image of the diagram. Visio Services also provides more actionable information in error messages.  <br/> |
    
 
 ### Secure Store Authentication
@@ -67,7 +68,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|Previously, Authentication Settings for external data sources (a SQL database, for example) could only be configured through a utility in Microsoft Excel. With Visio 2013, users can now configure their data connected diagrams directly from the Visio client, which allows data sources to be refreshed in Visio Services.  <br/> |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|Previously, Authentication Settings for external data sources (a SQL database, for example) could only be configured through a utility in Microsoft Excel. With Visio 2013, users can now configure their data connected diagrams directly from the Visio client, which allows data sources to be refreshed in Visio Services.  <br/> |
    
 
 ## Visio Services JavaScript Object Model
@@ -76,7 +77,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![In the cloud behavior note](../../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../../images/mod_icon_onpremises.gif)|The  [Vwa namespace](http://msdn.microsoft.com/library/b67939fa-d3db-41ff-8864-eabd318ba7c4%28Office.15%29.aspx) in the JavaScript object model in Visio Services gives you programmatic access to Visio drawings displayed in the Visio Web Access Web Part. Using the JavaScript object model, you can access data about diagrams, pages, and shapes; shape hyperlinks; and shape bounding box properties. With this access, you can create mashups that highlight shapes, place overlays on the diagram, respond to diagram and mouse events, and change the panning and zooming properties of the viewport. <br/> For information about adding a Visio Web Access Web Part to a SharePoint page and programming that page by using the JavaScript APIs in Visio 2013, see  [Customizing Visio Web Drawings in the Visio Web Access Web Part](http://msdn.microsoft.com/en-us/library/ff394649.aspx).  <br/> |
+|![In the cloud behavior note](../images/mod_icon_incloud.gif)           <br/> ![On-premises behavior note](../images/mod_icon_onpremises.gif)|The  [Vwa namespace](http://msdn.microsoft.com/library/b67939fa-d3db-41ff-8864-eabd318ba7c4%28Office.15%29.aspx) in the JavaScript object model in Visio Services gives you programmatic access to Visio drawings displayed in the Visio Web Access Web Part. Using the JavaScript object model, you can access data about diagrams, pages, and shapes; shape hyperlinks; and shape bounding box properties. With this access, you can create mashups that highlight shapes, place overlays on the diagram, respond to diagram and mouse events, and change the panning and zooming properties of the viewport. <br/> For information about adding a Visio Web Access Web Part to a SharePoint page and programming that page by using the JavaScript APIs in Visio 2013, see  [Customizing Visio Web Drawings in the Visio Web Access Web Part](http://msdn.microsoft.com/en-us/library/ff394649.aspx).  <br/> |
    
 
 ## Visio Services Class Library
@@ -85,7 +86,7 @@ Visio Services in Microsoft SharePoint and in Microsoft SharePoint Online includ
 
 |||
 |:-----|:-----|
-|![On-premises behavior note](../../images/mod_icon_onpremises.gif)|You can use the Visio Services class library, in the  [Microsoft.Office.Visio.Server](https://msdn.microsoft.com/library/Microsoft.Office.Visio.Server.aspx) namespace, to build custom Visio Services data providers. These data providers permit you to programmatically refresh data derived from custom data sources in Visio 2013 diagrams hosted on a SharePoint site. <br/> For more information about creating a custom data provider and to work through a complete end-to-end solution, see  [Creating a Custom Data Provider with Visio Services](http://msdn.microsoft.com/en-us/library/ff394595.aspx).  <br/> |
+|![On-premises behavior note](../images/mod_icon_onpremises.gif)|You can use the Visio Services class library, in the  [Microsoft.Office.Visio.Server](https://msdn.microsoft.com/library/Microsoft.Office.Visio.Server.aspx) namespace, to build custom Visio Services data providers. These data providers permit you to programmatically refresh data derived from custom data sources in Visio 2013 diagrams hosted on a SharePoint site. <br/> For more information about creating a custom data provider and to work through a complete end-to-end solution, see  [Creating a Custom Data Provider with Visio Services](http://msdn.microsoft.com/en-us/library/ff394595.aspx).  <br/> |
    
 
 ## Additional Resources
diff --git a/docs/general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md b/docs/general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md
index 1b5d0ddeeb..92f9fe5df9 100644
--- a/docs/general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md
+++ b/docs/general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md
@@ -1,6 +1,7 @@
 ---
 title: Visio shapes in SharePoint Designer 2013 A quick reference guide (SharePoint 2010 Workflow platform)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 51bc37fd-37de-4ad0-a75a-bdf7333bc80c
 ---
 
@@ -20,19 +21,19 @@ The actions in this list are organized in categories based on their area of appl
     
     
 
--  [Core actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010#section1a) These are the most commonly used actions in a workflow.
+-  [Core actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md#section1a) These are the most commonly used actions in a workflow.
     
   
--  [Document set actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010#section1e) Typically, these actions are used in workflows that are associated with a document library or the document content type.
+-  [Document set actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md#section1e) Typically, these actions are used in workflows that are associated with a document library or the document content type.
     
   
--  [List actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010#section1b) These actions perform operations on list items.
+-  [List actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md#section1b) These actions perform operations on list items.
     
   
--  [Relational actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010#section1d) The single action in this category looks up a user's manager and stores that information in a variable.
+-  [Relational actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md#section1d) The single action in this category looks up a user's manager and stores that information in a variable.
     
   
--  [Task actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010#section1c) These actions are associated with approval, feedback, and form operations.
+-  [Task actions](visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md#section1c) These actions are associated with approval, feedback, and form operations.
     
   
 
@@ -52,16 +53,16 @@ These are the most commonly-used actions and can be used in any type of workflow
 
 |**Visio Action Shape**|**Corresponding action in SharePoint Designer**|**Action description**|
 |:-----|:-----|:-----|
-|![Add a comment](../../images/spd15-addcomment-visio.JPG)|This Visio action is the same as the **Add a Comment** action in SharePoint Designer 2013 and appears as: <br/> ![Add comment](../../images/spd15-addcomment-txt.JPG)  <br/>  **Note:** Comments remain visible when the workflow is exported to Visio.           |**Add a comment** <br/> Use this action to leave informative comments in the workflow designer for reference purposes. This is especially helpful when there are other users co-authoring the workflow. For example, if a variable in the current workflow doesn't have a user-friendly name, you use this action to add a comment to indicate what the variable does in the workflow.  <br/> |
-|![Add time to date](../../images/spd15-addtimetodate-visio.JPG)|This Visio action is the same as the **Add Time to Date** action in SharePoint Designer 2013 and appears as: <br/> ![Add time to date](../../images/spd15-addtimetodate-txt.JPG)|**Add time to date** <br/> Use this action to add a specific time in minutes, hours, days, months, or years to a date, and store the output value as a variable. The date can be a current date, specific date, or a lookup.  <br/> |
-|![Do calculation](../../images/spd15-docalc-visio.JPG)|This Visio action is the same as the **Do Calculation** action in SharePoint Designer 2013 and appears as: <br/> ![Do calculation](../../images/spd15-docalc-txt.JPG)|**Do calculation** <br/> Use this action to perform a calculation, such as add, subtract, multiply, or divide two values, and stores the output value in a variable.  <br/> |
-|![Log to history list](../../images/spd15-LogHist-visio.JPG)|This Visio action is the same as the **Log to History List** action in SharePoint Designer 2013 and appears as: <br/> ![Log to history list](../../images/spd15-LogHist-txt.JPG)|**Log to history list** <br/> Use this action to log a message about the workflow into its history list. A message can be a summary of a workflow event, or anything significant about the workflow. The workflow history list can be helpful in troubleshooting issues with the workflow.  <br/> |
-|![Pause for duration](../../images/spd15-PauseDuration-visio.JPG)|This Visio action is the same as the **Pause for Duration** action in SharePoint Designer 2013 and appears as: <br/> ![Pause for duration](../../images/spd15-PauseDuration-txt.JPG)|**Pause for duration** <br/> Use this action to pause the workflow for a specific duration in days, hours, or minutes.  <br/> **Note:** The delay time is effected by the timer job interval, which has a default value of five minutes.           |
-|![Pause until date](../../images/spd15-PauseDate-visio.JPG)|This Visio action is the same as the **Pause Until Date** action in SharePoint Designer 2013 and appears as: <br/> ![Pause until date](../../images/spd15-PauseDate-txt.JPG)|**Pause until date** <br/> Use this action to pause the workflow until a particular date. You can add a current date, a specific date, or a lookup.  <br/> |
-|![Set time portion of date-time field](../../images/spd15-SetTimePortion-visio.JPG)|This Visio action is the same as the **Set Time Portion of Date/Time Field** action in SharePoint Designer 2013 and appears as: <br/> ![Set time portion of date-time field](../../images/spd15-SetTimePortion-txt.JPG)|**Set time portion of date/time field** <br/> Use this action to create a timestamp, and stores the output value in a variable. You can set the time in hours and minutes and add a current date, specific date or a lookup.  <br/> |
-|![Set workflow status](../../images/spd15-SetWFStatus-visio.JPG)| This Visio action is the same as the **Set Workflow Status** action in SharePoint Designer 2013 and appears as: <br/> ![Set workflow status](../../images/spd15-SetWFStatus-txt.JPG) You cannot rename or delete a status value once it has been created. However, you do not have to use it. <br/>  A custom status is applicable to the current workflow only, and cannot be used in another workflow <br/>  A workflow cannot use custom status values that you define in the action if the action is used inside an impersonation step. <br/> |**Set workflow status** <br/> Use this action to set the status of the workflow. The default options are **Canceled**, **Approved**, and **Rejected**.  <br/> You can enter a new status value in the dropdown in the action. Once you enter a status value, the entry is automatically added to the dropdown list.  <br/> If the **Set Workflow Status** action is the last step in your workflow where you have also used a custom value, you can see your custom value in the **Status** column in the list upon workflow pausing or completion. <br/> |
-|![Set workflow variable](../../images/spd15-SetWFVar-visio.JPG)|This Visio action is the same as the **Set Workflow Variable** action in SharePoint Designer 2013 and appears as: <br/> ![Set workflow variable](../../images/spd15-SetWFVar-txt.JPG)|**Set workflow variable** <br/> Use this action to set a workflow variable to a value. Use this action when you want the workflow to assign data to a variable.  <br/> |
-|![Stop workflow](../../images/spd15-StopWF-visio.JPG)|This Visio action is the same as the **Stop workflow** action in SharePoint Designer 2013 and appears as: <br/> ![Stop workflow](../../images/spd15-StopWF-txt.JPG)|**Stop workflow** <br/> Use this action to stop the current instance of the workflow and log a message to the **Workflow History** list. The message that you specify in the action will appear in the **Description** column in the Workflow History upon workflow completion. <br/> |
+|![Add a comment](../images/spd15-addcomment-visio.JPG)|This Visio action is the same as the **Add a Comment** action in SharePoint Designer 2013 and appears as: <br/> ![Add comment](../images/spd15-addcomment-txt.JPG)  <br/>  **Note:** Comments remain visible when the workflow is exported to Visio.           |**Add a comment** <br/> Use this action to leave informative comments in the workflow designer for reference purposes. This is especially helpful when there are other users co-authoring the workflow. For example, if a variable in the current workflow doesn't have a user-friendly name, you use this action to add a comment to indicate what the variable does in the workflow.  <br/> |
+|![Add time to date](../images/spd15-addtimetodate-visio.JPG)|This Visio action is the same as the **Add Time to Date** action in SharePoint Designer 2013 and appears as: <br/> ![Add time to date](../images/spd15-addtimetodate-txt.JPG)|**Add time to date** <br/> Use this action to add a specific time in minutes, hours, days, months, or years to a date, and store the output value as a variable. The date can be a current date, specific date, or a lookup.  <br/> |
+|![Do calculation](../images/spd15-docalc-visio.JPG)|This Visio action is the same as the **Do Calculation** action in SharePoint Designer 2013 and appears as: <br/> ![Do calculation](../images/spd15-docalc-txt.JPG)|**Do calculation** <br/> Use this action to perform a calculation, such as add, subtract, multiply, or divide two values, and stores the output value in a variable.  <br/> |
+|![Log to history list](../images/spd15-LogHist-visio.JPG)|This Visio action is the same as the **Log to History List** action in SharePoint Designer 2013 and appears as: <br/> ![Log to history list](../images/spd15-LogHist-txt.JPG)|**Log to history list** <br/> Use this action to log a message about the workflow into its history list. A message can be a summary of a workflow event, or anything significant about the workflow. The workflow history list can be helpful in troubleshooting issues with the workflow.  <br/> |
+|![Pause for duration](../images/spd15-PauseDuration-visio.JPG)|This Visio action is the same as the **Pause for Duration** action in SharePoint Designer 2013 and appears as: <br/> ![Pause for duration](../images/spd15-PauseDuration-txt.JPG)|**Pause for duration** <br/> Use this action to pause the workflow for a specific duration in days, hours, or minutes.  <br/> **Note:** The delay time is effected by the timer job interval, which has a default value of five minutes.           |
+|![Pause until date](../images/spd15-PauseDate-visio.JPG)|This Visio action is the same as the **Pause Until Date** action in SharePoint Designer 2013 and appears as: <br/> ![Pause until date](../images/spd15-PauseDate-txt.JPG)|**Pause until date** <br/> Use this action to pause the workflow until a particular date. You can add a current date, a specific date, or a lookup.  <br/> |
+|![Set time portion of date-time field](../images/spd15-SetTimePortion-visio.JPG)|This Visio action is the same as the **Set Time Portion of Date/Time Field** action in SharePoint Designer 2013 and appears as: <br/> ![Set time portion of date-time field](../images/spd15-SetTimePortion-txt.JPG)|**Set time portion of date/time field** <br/> Use this action to create a timestamp, and stores the output value in a variable. You can set the time in hours and minutes and add a current date, specific date or a lookup.  <br/> |
+|![Set workflow status](../images/spd15-SetWFStatus-visio.JPG)| This Visio action is the same as the **Set Workflow Status** action in SharePoint Designer 2013 and appears as: <br/> ![Set workflow status](../images/spd15-SetWFStatus-txt.JPG) You cannot rename or delete a status value once it has been created. However, you do not have to use it. <br/>  A custom status is applicable to the current workflow only, and cannot be used in another workflow <br/>  A workflow cannot use custom status values that you define in the action if the action is used inside an impersonation step. <br/> |**Set workflow status** <br/> Use this action to set the status of the workflow. The default options are **Canceled**, **Approved**, and **Rejected**.  <br/> You can enter a new status value in the dropdown in the action. Once you enter a status value, the entry is automatically added to the dropdown list.  <br/> If the **Set Workflow Status** action is the last step in your workflow where you have also used a custom value, you can see your custom value in the **Status** column in the list upon workflow pausing or completion. <br/> |
+|![Set workflow variable](../images/spd15-SetWFVar-visio.JPG)|This Visio action is the same as the **Set Workflow Variable** action in SharePoint Designer 2013 and appears as: <br/> ![Set workflow variable](../images/spd15-SetWFVar-txt.JPG)|**Set workflow variable** <br/> Use this action to set a workflow variable to a value. Use this action when you want the workflow to assign data to a variable.  <br/> |
+|![Stop workflow](../images/spd15-StopWF-visio.JPG)|This Visio action is the same as the **Stop workflow** action in SharePoint Designer 2013 and appears as: <br/> ![Stop workflow](../images/spd15-StopWF-txt.JPG)|**Stop workflow** <br/> Use this action to stop the current instance of the workflow and log a message to the **Workflow History** list. The message that you specify in the action will appear in the **Description** column in the Workflow History upon workflow completion. <br/> |
    
 
 ### List actions
@@ -76,20 +77,20 @@ These actions are used on list items.
 
 |**VISIO ACTION SHAPE**|**CORRESPONDING ACTION IN SHAREPOINT DESIGNER**|**ACTION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Add list item permissions](../../images/spd15-AddListItemPerms-visio.JPG)|This Visio action is the same as the **Add List Item Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Add permissions to item](../../images/spd15-AddListItemPerms-txt.JPG)    **Note:** This action is only available within an impersonation step.           |**Add list item permissions** <br/> This action grants specific permission levels for an item to specific users.  <br/> |
-|![Check in item](../../images/spd15-CheckInItem-visio.JPG)|This Visio action is the same as the **Check In Item** action in SharePoint Designer 2013 and appears as: <br/> ![Check in item](../../images/spd15-CheckInItem-txt.JPG)|**Check in item** <br/> This action checks in an item that is checked out.  <br/> **Note:** You can only check in items from a document library.           |
-|![Check out item](../../images/spd15-CheckOutItem-visio.JPG)|This Visio action is the same as the **Check Out Item** action in SharePoint Designer 2013 and appears as: <br/> ![Check out item](../../images/spd15-CheckOutItem-txt.JPG)|**Check out item** <br/> Use this action to check out an item. The workflow verifies if the item is checked in, before it checks out a document.  <br/> **Note:** You can only check out items from a library in your site.           |
-|![Copy list item](../../images/spd15-CopyListItem-visio.JPG)|This Visio action is the same as the **Copy List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Copy list item](../../images/spd15-CopyListItem-txt.JPG)|**Copy list item** <br/> Use this action to copy a list item to another list. If there is a document in the list item, the workflow also copies the document to the destination list.  <br/> **Important:** You must have at least one column similar in both the source and destination lists.           |
-|![Create list item](../../images/spd15-CreateListItem-visio.JPG)|This Visio action is the same as the **Create List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Create list item](../../images/spd15-CreateListItem-txt.JPG)|**Create list item** <br/> Use this action to create a new list item in the list that you specify. You can supply the fields and values in the new item.  <br/> You can use this action whenever you want a new item to be created with specific information.  <br/> **Note:** The output variable is the ID of the item created in the list.           |
-|![Delete item](../../images/spd15-DeleteItem-visio.JPG)|This Visio action is the same as the **Delete Item** action in SharePoint Designer 2013 and appears as: <br/> ![Delete item](../../images/spd15-DeleteItem-txt.JPG)|**Delete item** <br/> Use this action to delete an item.  <br/> |
-|![Discard check out item](../../images/spd15-DiscardItem-visio.JPG)|This Visio action is the same as the **Discard Check Out Item** action in SharePoint Designer 2013 and appears as: <br/> ![Discard check out item](../../images/spd15-DiscardItem-txt.JPG)|**Discard check out item** <br/> Use this action if an item is checked out, changes have been made to it, and you want to discard the changes and check the item back in.  <br/> |
-|![Inherit list item permissions](../../images/spd15-InheritListItemPerms-visio.JPG)|This Visio action is the same as the **Inherit List Item Parent Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Inherit list item permissions](../../images/spd15-InheritListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Inherit list item permissions** <br/> If your item has unique permissions, you can use this action to make the item inherit the parent permissions from the list.  <br/> |
-|![Remove list item permissions](../../images/spd15-RmListItemPerms-visio.JPG)|This Visio action is the same as the **Remove List Item Permission**s action in SharePoint Designer 2013 and appears as:  <br/> ![Remove list item permissions](../../images/spd15-RmListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Remove list item permissions** <br/> This action removes permissions from an item for specific users.  <br/> |
-|![Replace list item permissions](../../images/spd15-ReplaceListItemPerms-visio.JPG)|This Visio action is the same as the **Replace List Item Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Replace list item permissions](../../images/spd15-ReplaceListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Replace list item permissions** <br/> It replaces an item's current permissions with the new permissions that you specify in the action.  <br/> |
-|![Set content approval status](../../images/spd15-SetContentApprovalStatus-visio.JPG)|This Visio action is the same as the **Set Content Approval Status** action in SharePoint Designer 2013 and appears as: <br/> ![Set content approval status](../../images/spd15-SetContentApprovalStatus-txt.JPG)    **Note:** Content approval must be enabled in the list in order to use this action.|**Set content approval status** <br/> If you have content approval enabled in your list, use this action to set the content approval status field to a value such as Approved, Rejected, or Pending. You can type a custom status in the action.  <br/> **Note:** The **Set Content Approval Status** action works on the current item that the workflow is acting upon, therefore the action is not available in a site workflow.          |
-|![Set field in current item](../../images/spd15-SetFieldCurrItem-visio.JPG)|This Visio action is the same as the **Set Field in Current Item** action in SharePoint Designer 2013 and appears as: <br/> ![Set field in current item](../../images/spd15-SetFieldCurrItem-txt.JPG)|**Set field in current item** <br/> Use the action to set a field in the current item to a value.  <br/> **Note:** If you want to pause the workflow until it changes the value of the field, use the **Wait for Field Change in Current Item** action instead.          The **Set Field in Current Item** action should not be used in a site workflow. <br/> |
-|![Update list item](../../images/spd15-UpdateListItem-visio.JPG)|This Visio action is the same as the **Update List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Update list item](../../images/spd15-UpdateListItem-txt.JPG)|**Update list item** <br/> Use this action to update a list item. You can specify the fields and the new values in those fields.  <br/> |
-|![Wait for field change in current item](../../images/spd15-Wait4FieldChange-visio.JPG)|This Visio action is the same as the **Wait for Field Change in Current Item** action in SharePoint Designer 2013 and appears as: <br/> ![Wait for field change](../../images/spd15-Wait4FieldChange-txt.JPG)|**Wait for field change in current item** <br/> This action pauses the workflow until the field in the current item has changed to a new value.  <br/> **Note:** If you want the workflow to change the value of the field, rather than have the workflow wait for the field to change, use the **Set Field in Current Item** action instead.          |
+|![Add list item permissions](../images/spd15-AddListItemPerms-visio.JPG)|This Visio action is the same as the **Add List Item Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Add permissions to item](../images/spd15-AddListItemPerms-txt.JPG)    **Note:** This action is only available within an impersonation step.           |**Add list item permissions** <br/> This action grants specific permission levels for an item to specific users.  <br/> |
+|![Check in item](../images/spd15-CheckInItem-visio.JPG)|This Visio action is the same as the **Check In Item** action in SharePoint Designer 2013 and appears as: <br/> ![Check in item](../images/spd15-CheckInItem-txt.JPG)|**Check in item** <br/> This action checks in an item that is checked out.  <br/> **Note:** You can only check in items from a document library.           |
+|![Check out item](../images/spd15-CheckOutItem-visio.JPG)|This Visio action is the same as the **Check Out Item** action in SharePoint Designer 2013 and appears as: <br/> ![Check out item](../images/spd15-CheckOutItem-txt.JPG)|**Check out item** <br/> Use this action to check out an item. The workflow verifies if the item is checked in, before it checks out a document.  <br/> **Note:** You can only check out items from a library in your site.           |
+|![Copy list item](../images/spd15-CopyListItem-visio.JPG)|This Visio action is the same as the **Copy List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Copy list item](../images/spd15-CopyListItem-txt.JPG)|**Copy list item** <br/> Use this action to copy a list item to another list. If there is a document in the list item, the workflow also copies the document to the destination list.  <br/> **Important:** You must have at least one column similar in both the source and destination lists.           |
+|![Create list item](../images/spd15-CreateListItem-visio.JPG)|This Visio action is the same as the **Create List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Create list item](../images/spd15-CreateListItem-txt.JPG)|**Create list item** <br/> Use this action to create a new list item in the list that you specify. You can supply the fields and values in the new item.  <br/> You can use this action whenever you want a new item to be created with specific information.  <br/> **Note:** The output variable is the ID of the item created in the list.           |
+|![Delete item](../images/spd15-DeleteItem-visio.JPG)|This Visio action is the same as the **Delete Item** action in SharePoint Designer 2013 and appears as: <br/> ![Delete item](../images/spd15-DeleteItem-txt.JPG)|**Delete item** <br/> Use this action to delete an item.  <br/> |
+|![Discard check out item](../images/spd15-DiscardItem-visio.JPG)|This Visio action is the same as the **Discard Check Out Item** action in SharePoint Designer 2013 and appears as: <br/> ![Discard check out item](../images/spd15-DiscardItem-txt.JPG)|**Discard check out item** <br/> Use this action if an item is checked out, changes have been made to it, and you want to discard the changes and check the item back in.  <br/> |
+|![Inherit list item permissions](../images/spd15-InheritListItemPerms-visio.JPG)|This Visio action is the same as the **Inherit List Item Parent Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Inherit list item permissions](../images/spd15-InheritListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Inherit list item permissions** <br/> If your item has unique permissions, you can use this action to make the item inherit the parent permissions from the list.  <br/> |
+|![Remove list item permissions](../images/spd15-RmListItemPerms-visio.JPG)|This Visio action is the same as the **Remove List Item Permission**s action in SharePoint Designer 2013 and appears as:  <br/> ![Remove list item permissions](../images/spd15-RmListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Remove list item permissions** <br/> This action removes permissions from an item for specific users.  <br/> |
+|![Replace list item permissions](../images/spd15-ReplaceListItemPerms-visio.JPG)|This Visio action is the same as the **Replace List Item Permissions** action in SharePoint Designer 2013 and appears as: <br/> ![Replace list item permissions](../images/spd15-ReplaceListItemPerms-txt.JPG)    **Note:** This action is only available in an impersonation step.           |**Replace list item permissions** <br/> It replaces an item's current permissions with the new permissions that you specify in the action.  <br/> |
+|![Set content approval status](../images/spd15-SetContentApprovalStatus-visio.JPG)|This Visio action is the same as the **Set Content Approval Status** action in SharePoint Designer 2013 and appears as: <br/> ![Set content approval status](../images/spd15-SetContentApprovalStatus-txt.JPG)    **Note:** Content approval must be enabled in the list in order to use this action.|**Set content approval status** <br/> If you have content approval enabled in your list, use this action to set the content approval status field to a value such as Approved, Rejected, or Pending. You can type a custom status in the action.  <br/> **Note:** The **Set Content Approval Status** action works on the current item that the workflow is acting upon, therefore the action is not available in a site workflow.          |
+|![Set field in current item](../images/spd15-SetFieldCurrItem-visio.JPG)|This Visio action is the same as the **Set Field in Current Item** action in SharePoint Designer 2013 and appears as: <br/> ![Set field in current item](../images/spd15-SetFieldCurrItem-txt.JPG)|**Set field in current item** <br/> Use the action to set a field in the current item to a value.  <br/> **Note:** If you want to pause the workflow until it changes the value of the field, use the **Wait for Field Change in Current Item** action instead.          The **Set Field in Current Item** action should not be used in a site workflow. <br/> |
+|![Update list item](../images/spd15-UpdateListItem-visio.JPG)|This Visio action is the same as the **Update List Item** action in SharePoint Designer 2013 and appears as: <br/> ![Update list item](../images/spd15-UpdateListItem-txt.JPG)|**Update list item** <br/> Use this action to update a list item. You can specify the fields and the new values in those fields.  <br/> |
+|![Wait for field change in current item](../images/spd15-Wait4FieldChange-visio.JPG)|This Visio action is the same as the **Wait for Field Change in Current Item** action in SharePoint Designer 2013 and appears as: <br/> ![Wait for field change](../images/spd15-Wait4FieldChange-txt.JPG)|**Wait for field change in current item** <br/> This action pauses the workflow until the field in the current item has changed to a new value.  <br/> **Note:** If you want the workflow to change the value of the field, rather than have the workflow wait for the field to change, use the **Set Field in Current Item** action instead.          |
    
 
 ### Task actions
@@ -105,12 +106,12 @@ Actions in this category pertain to task items. These actions apply only to Shar
 
 |**VISIO ACTION SHAPE**|**CORRESPONDING ACTION IN SHAREPOINT DESIGNER**|**ACTION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Assign a form to a group](../../images/spd15-AssignForm2Grp-visio.JPG)|This Visio action is the same as the **Assign a Form to a Group** action in SharePoint Designer 2013 and appears as: <br/> ![Assign a form to a group](../../images/spd15-AssignForm2Grp-txt.JPG)|**Assign a form to a group** <br/> Use this action to enable you to create a custom task form with customized fields.  <br/> You can use this action to assign a task to one or more participants or groups prompting them to perform their tasks. Participants provide their responses it the fields of the custom task form and, when they are done with the task, click **Complete Task** on the form. <br/> |
-|![Assign a to-do item](../../images/spd15-AssignToDoItem-visio.JPG)|This Visio action is the same as the **Assign a To-do Item** action in SharePoint Designer 2013 and appears as: <br/> ![Assign a to-do item](../../images/spd15-AssignToDoItem-txt.JPG)|**Assign a to-do item** <br/> Use this action to assign a task to each of the participants, prompting them to perform their tasks and then, when they are done, to click the **Complete Task** button on their task form. <br/> |
-|![Collect data from a user](../../images/spd15-CollectDataFrUser-visio.JPG)|This Visio action is the same as the **Collect Data from a User** action in SharePoint Designer 2013 and appears as: <br/> ![Collect data from a user](../../images/spd15-CollectDataFrUser-txt.JPG)|**Collect data from a user** <br/> Use this action to assign a task to the participant, prompting them to provide the needed information in a custom task form, and then click the **Complete Task** button on the task form. <br/> This action has an output clause??? meaning, the workflow stores the information returned by the action in a corresponding variable. The list item ID of the completed task item from the action is stored in the collect variable.  <br/> |
-|![Start approval process](../../images/spd15-StartApprovalProc-visio.JPG)|This Visio action is the same as the **Start Approval Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start approval process for document set](../../images/spd15-StartApprovalProc-txt.JPG)|**Start approval process** <br/> Use this action to route a document for approval. Approvers can approve or reject the document, reassign the approval task, or request changes.  <br/> You can assign tasks to both internal and external participants in the action. An external participant can be an employee in your organization who isn't a user in the site collection, or anyone outside your organization.  <br/> |
-|![Start feedback process](../../images/spd15-StartFeedback-visio.JPG)|This Visio action is the same as the **Start Feedback Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start feedback process](../../images/spd15-StartFeedback-txt.JPG)|**Start feedback process** <br/> Use this action to assign task items for feedback to users in a specific order???serial or parallel. The default is parallel. Users or task participants can also reassign a task to other users. When the users are done, they can click the **Submit Feedback** button to indicate task completion. <br/> You can assign tasks to both internal and external participants in the action. An external participant can be an employee in your organization who isn't a user in the site collection, or anyone outside your organization.  <br/> |
-|![Start custom task process](../../images/spd15-StartCustomTask-visio.JPG)|This Visio action is the same as the **Start Custom Task Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start custom task process](../../images/spd15-StartCustomTask-txt.JPG)|**Start custom task process** <br/> The **Start Custom Task Process** action is an approval process template that you can use if other approval actions do not meet your needs. <br/> |
+|![Assign a form to a group](../images/spd15-AssignForm2Grp-visio.JPG)|This Visio action is the same as the **Assign a Form to a Group** action in SharePoint Designer 2013 and appears as: <br/> ![Assign a form to a group](../images/spd15-AssignForm2Grp-txt.JPG)|**Assign a form to a group** <br/> Use this action to enable you to create a custom task form with customized fields.  <br/> You can use this action to assign a task to one or more participants or groups prompting them to perform their tasks. Participants provide their responses it the fields of the custom task form and, when they are done with the task, click **Complete Task** on the form. <br/> |
+|![Assign a to-do item](../images/spd15-AssignToDoItem-visio.JPG)|This Visio action is the same as the **Assign a To-do Item** action in SharePoint Designer 2013 and appears as: <br/> ![Assign a to-do item](../images/spd15-AssignToDoItem-txt.JPG)|**Assign a to-do item** <br/> Use this action to assign a task to each of the participants, prompting them to perform their tasks and then, when they are done, to click the **Complete Task** button on their task form. <br/> |
+|![Collect data from a user](../images/spd15-CollectDataFrUser-visio.JPG)|This Visio action is the same as the **Collect Data from a User** action in SharePoint Designer 2013 and appears as: <br/> ![Collect data from a user](../images/spd15-CollectDataFrUser-txt.JPG)|**Collect data from a user** <br/> Use this action to assign a task to the participant, prompting them to provide the needed information in a custom task form, and then click the **Complete Task** button on the task form. <br/> This action has an output clause??? meaning, the workflow stores the information returned by the action in a corresponding variable. The list item ID of the completed task item from the action is stored in the collect variable.  <br/> |
+|![Start approval process](../images/spd15-StartApprovalProc-visio.JPG)|This Visio action is the same as the **Start Approval Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start approval process for document set](../images/spd15-StartApprovalProc-txt.JPG)|**Start approval process** <br/> Use this action to route a document for approval. Approvers can approve or reject the document, reassign the approval task, or request changes.  <br/> You can assign tasks to both internal and external participants in the action. An external participant can be an employee in your organization who isn't a user in the site collection, or anyone outside your organization.  <br/> |
+|![Start feedback process](../images/spd15-StartFeedback-visio.JPG)|This Visio action is the same as the **Start Feedback Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start feedback process](../images/spd15-StartFeedback-txt.JPG)|**Start feedback process** <br/> Use this action to assign task items for feedback to users in a specific order???serial or parallel. The default is parallel. Users or task participants can also reassign a task to other users. When the users are done, they can click the **Submit Feedback** button to indicate task completion. <br/> You can assign tasks to both internal and external participants in the action. An external participant can be an employee in your organization who isn't a user in the site collection, or anyone outside your organization.  <br/> |
+|![Start custom task process](../images/spd15-StartCustomTask-visio.JPG)|This Visio action is the same as the **Start Custom Task Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start custom task process](../images/spd15-StartCustomTask-txt.JPG)|**Start custom task process** <br/> The **Start Custom Task Process** action is an approval process template that you can use if other approval actions do not meet your needs. <br/> |
    
 
 ### Relational actions
@@ -126,7 +127,7 @@ The single action in this category looks up a user's manager and stores that inf
 
 |**VISIO ACTION SHAPE**|**CORRESPONDING ACTION IN SHAREPOINT DESIGNER**|**ACTION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Lookup manager of a user](../../images/spd15-LookupMgr4User-visio.JPG)|This Visio action is the same as the **Lookup Manager of a User** action in SharePoint Designer 2013 and appears as: <br/> ![Lookup manager of a user](../../images/spd15-LookupMgr4User-txt.JPG)|**Lookup manager of a user** <br/> Use this action to look up a user's manager. The output value is then stored in a variable.  <br/> **Note:** For this action to work properly, the User Profile service must be running in SharePoint.           |
+|![Lookup manager of a user](../images/spd15-LookupMgr4User-visio.JPG)|This Visio action is the same as the **Lookup Manager of a User** action in SharePoint Designer 2013 and appears as: <br/> ![Lookup manager of a user](../images/spd15-LookupMgr4User-txt.JPG)|**Lookup manager of a user** <br/> Use this action to look up a user's manager. The output value is then stored in a variable.  <br/> **Note:** For this action to work properly, the User Profile service must be running in SharePoint.           |
    
 
 ### Document set actions
@@ -142,10 +143,10 @@ Some workflow actions are only available when the workflow is associated to a do
 
 |**VISIO ACTION SHAPE**|**CORRESPONDING ACTION IN SHAREPOINT DESIGNER**|**ACTION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Send approval for document set](../../images/spd15-SendApproval4DocSet-visio.JPG)|This Visio action is the same as the **Start Document Set Approval Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start approval process for document set](../../images/spd15-SendApproval4DocSet-txt.JPG)|**Send approval for document set** <br/> Use this action to begin the approval process for a document set.  <br/> |
-|![Send document set to repository](../../images/spd15-SendDocSet2Repos-visio.JPG)|This Visio action is the same as the **Send Document Set to Repository** action in SharePoint Designer 2013 and appears as: <br/> ![Send document set to repository](../../images/spd15-SendDocSet2Repos-txt.JPG)|**Send document set to repository** <br/> Use this action to allow you to move or copy the document set to a document repository. A document repository can be a library in your SharePoint site, or a site on its own like the Document Center, that routes records to a specific destination based on rules that you define.  <br/> |
-|![Send document to repository](../../images/spd15-SendDoc2Repos-visio.JPG)|This Visio action is the same as the **Send Document to Repository** action in SharePoint Designer 2013 and appears as: <br/> ![Send document to repository](../../images/spd15-SendDoc2Repos-txt.JPG)|**Send document to repository** <br/> Use this action to allow you to move or copy a document to a document repository. A document repository can be a library in your SharePoint site, or a site on its own like the Document Center, that routes records to a specific destination based on rules that you define.  <br/> |
-|![Set content approval status for document set](../../images/spd15-SetContentApprStatus-visio.JPG)|This Visio action is the same as the **Set Content Approval Status for the Document Set** action in SharePoint Designer 2013 and appears as: <br/> ![Set content approval status for document set](../../images/spd15-SetContentApprStatus4DocSet-txt.JPG)|**Set content approval status for the document set** <br/> Use this action to set content approval of a document set to **Approved**, **Rejected**, or **Pending**.  <br/> |
+|![Send approval for document set](../images/spd15-SendApproval4DocSet-visio.JPG)|This Visio action is the same as the **Start Document Set Approval Process** action in SharePoint Designer 2013 and appears as: <br/> ![Start approval process for document set](../images/spd15-SendApproval4DocSet-txt.JPG)|**Send approval for document set** <br/> Use this action to begin the approval process for a document set.  <br/> |
+|![Send document set to repository](../images/spd15-SendDocSet2Repos-visio.JPG)|This Visio action is the same as the **Send Document Set to Repository** action in SharePoint Designer 2013 and appears as: <br/> ![Send document set to repository](../images/spd15-SendDocSet2Repos-txt.JPG)|**Send document set to repository** <br/> Use this action to allow you to move or copy the document set to a document repository. A document repository can be a library in your SharePoint site, or a site on its own like the Document Center, that routes records to a specific destination based on rules that you define.  <br/> |
+|![Send document to repository](../images/spd15-SendDoc2Repos-visio.JPG)|This Visio action is the same as the **Send Document to Repository** action in SharePoint Designer 2013 and appears as: <br/> ![Send document to repository](../images/spd15-SendDoc2Repos-txt.JPG)|**Send document to repository** <br/> Use this action to allow you to move or copy a document to a document repository. A document repository can be a library in your SharePoint site, or a site on its own like the Document Center, that routes records to a specific destination based on rules that you define.  <br/> |
+|![Set content approval status for document set](../images/spd15-SetContentApprStatus-visio.JPG)|This Visio action is the same as the **Set Content Approval Status for the Document Set** action in SharePoint Designer 2013 and appears as: <br/> ![Set content approval status for document set](../images/spd15-SetContentApprStatus4DocSet-txt.JPG)|**Set content approval status for the document set** <br/> Use this action to set content approval of a document set to **Approved**, **Rejected**, or **Pending**.  <br/> |
    
 
 ## Workflow conditions
@@ -175,13 +176,13 @@ This section describes the conditions that are available in SharePoint Designer
 
 |**VISIO CONDITION SHAPE**|**CORRESPONDING CONDITION IN SHAREPOINT DESIGNER**|**CONDITION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Compare data source](../../images/spd15-CompareDataSrc-visio.JPG)|This Visio condition is the same as the **If any value equals value** condition in SharePoint Designer 2013 and appears as: <br/> ![If value equals value](../../images/spd15-CompareDataSrc-txt.JPG)|**Compare data source** <br/> This condition compares two values. You can specify whether the values should be equal or not equal.  <br/> |
-|![Compare document field](../../images/spd15-CompareDocField-visio.JPG)|This Visio condition is the same as the **If current item field equals value** condition in SharePoint Designer 2013 and appears as: <br/> ![If current item field equals value](../../images/spd15-CompareDocField-txt.JPG)|**Compare document field** <br/> This condition checks a field against a value that you specify. You can specify whether the values should be equal or not equal.  <br/> |
-|![Created by a specified person](../../images/spd15-CreatedBySpecPerson-visio.JPG)|This Visio condition is the same as the **Created by a specific person** condition in SharePoint Designer 2013 and appears as: <br/> ![If created by specific person](../../images/spd15-CreatedBySpecPerson-txt.JPG)|**Created by a specified person** <br/> This condition checks if an item was created by a specific user. The user can be specified as an e-mail address, such as olivier@contoso.com, or selected from SharePoint, Exchange, or Active Directory users.  <br/> **Note:** The user name and e-mail address are case sensitive. It is recommended that you select a user name or e-mail address to help ensure that you use the correct case. If you type a user name or e-mail address, you must match the case of the account. For example, If created by contoso\\molly will not evaluate as true if the user account is Contoso\\Molly.           |
-|![Created in specific data span](../../images/spd15-CreatedInSpecDateSpan-visio.JPG)|This Visio condition is the same as the **Created in a specific date span** condition in SharePoint Designer 2013 and appears as: <br/> ![If created in a specific date span](../../images/spd15-CreatedInSpecDateSpan-txt.JPG)|**Created in specific date span** <br/> This condition checks if the item was created between the specified dates. You can use the current date, a specific date, or a lookup.  <br/> |
-|![Modified by a specific person](../../images/spd15-ModifiedBySpecPerson-visio.JPG)|This Visio condition is the same as the **Modified by a specific person** condition in SharePoint Designer 2013 and appears as: <br/> ![If modified by a specific person](../../images/spd15-ModifiedBySpecPerson-txt.JPG)|**Modified by a specific person** <br/> Use this condition to check if an item was modified by a specified user. The user can be specified as an e-mail address, such as olivier@contoso.com, or selected from SharePoint, Exchange, or Active Directory users.  <br/> **Note:** The user name and e-mail address are case sensitive. It is recommended that you select a user name or e-mail address to help ensure that you use the correct case. If you type a user name or e-mail address, you must match the case of the account. For example, If modified by contoso\\molly will not evaluate as true if the user account is Contoso\\Molly.           |
-|![Modified in a specific date span](../../images/spd15-ModifiedInSpecDateSpan-visio.JPG)|This Visio condition is the same as the **Modified in a specific date span** condition in SharePoint Designer 2013 and appears as: <br/> ![If modified in a specific date span](../../images/spd15-ModifiedInSpecDateSpan-txt.JPG)|**Modified in a specific date span** <br/> This condition checks if an item was modified between the specified dates. You can use the current date, a specific date, or a lookup.  <br/> |
-|![Title field contains keywords](../../images/spd15-TitleFieldKeywords-visio.JPG)|This Visio condition is the same as the **Title field contains keywords** condition in SharePoint Designer 2013 and appears as: <br/> ![If title field contains keywords](../../images/spd15-TitleFieldKeywords-txt.JPG)|**Title field contains keywords** <br/> This condition checks if the **Title** field for an item contains a specific word. You can either specify the keyword in the String Builder???which can be a static value or a dynamic string or a combination ??? or insert a lookup to a field or variable. <br/> **Note:** You cannot search for more than one keyword in the **Title field contains keywords** condition. However, you can use logical operators such as**||**( or) or **&amp;&amp;** (and.          |
+|![Compare data source](../images/spd15-CompareDataSrc-visio.JPG)|This Visio condition is the same as the **If any value equals value** condition in SharePoint Designer 2013 and appears as: <br/> ![If value equals value](../images/spd15-CompareDataSrc-txt.JPG)|**Compare data source** <br/> This condition compares two values. You can specify whether the values should be equal or not equal.  <br/> |
+|![Compare document field](../images/spd15-CompareDocField-visio.JPG)|This Visio condition is the same as the **If current item field equals value** condition in SharePoint Designer 2013 and appears as: <br/> ![If current item field equals value](../images/spd15-CompareDocField-txt.JPG)|**Compare document field** <br/> This condition checks a field against a value that you specify. You can specify whether the values should be equal or not equal.  <br/> |
+|![Created by a specified person](../images/spd15-CreatedBySpecPerson-visio.JPG)|This Visio condition is the same as the **Created by a specific person** condition in SharePoint Designer 2013 and appears as: <br/> ![If created by specific person](../images/spd15-CreatedBySpecPerson-txt.JPG)|**Created by a specified person** <br/> This condition checks if an item was created by a specific user. The user can be specified as an e-mail address, such as olivier@contoso.com, or selected from SharePoint, Exchange, or Active Directory users.  <br/> **Note:** The user name and e-mail address are case sensitive. It is recommended that you select a user name or e-mail address to help ensure that you use the correct case. If you type a user name or e-mail address, you must match the case of the account. For example, If created by contoso\\molly will not evaluate as true if the user account is Contoso\\Molly.           |
+|![Created in specific data span](../images/spd15-CreatedInSpecDateSpan-visio.JPG)|This Visio condition is the same as the **Created in a specific date span** condition in SharePoint Designer 2013 and appears as: <br/> ![If created in a specific date span](../images/spd15-CreatedInSpecDateSpan-txt.JPG)|**Created in specific date span** <br/> This condition checks if the item was created between the specified dates. You can use the current date, a specific date, or a lookup.  <br/> |
+|![Modified by a specific person](../images/spd15-ModifiedBySpecPerson-visio.JPG)|This Visio condition is the same as the **Modified by a specific person** condition in SharePoint Designer 2013 and appears as: <br/> ![If modified by a specific person](../images/spd15-ModifiedBySpecPerson-txt.JPG)|**Modified by a specific person** <br/> Use this condition to check if an item was modified by a specified user. The user can be specified as an e-mail address, such as olivier@contoso.com, or selected from SharePoint, Exchange, or Active Directory users.  <br/> **Note:** The user name and e-mail address are case sensitive. It is recommended that you select a user name or e-mail address to help ensure that you use the correct case. If you type a user name or e-mail address, you must match the case of the account. For example, If modified by contoso\\molly will not evaluate as true if the user account is Contoso\\Molly.           |
+|![Modified in a specific date span](../images/spd15-ModifiedInSpecDateSpan-visio.JPG)|This Visio condition is the same as the **Modified in a specific date span** condition in SharePoint Designer 2013 and appears as: <br/> ![If modified in a specific date span](../images/spd15-ModifiedInSpecDateSpan-txt.JPG)|**Modified in a specific date span** <br/> This condition checks if an item was modified between the specified dates. You can use the current date, a specific date, or a lookup.  <br/> |
+|![Title field contains keywords](../images/spd15-TitleFieldKeywords-visio.JPG)|This Visio condition is the same as the **Title field contains keywords** condition in SharePoint Designer 2013 and appears as: <br/> ![If title field contains keywords](../images/spd15-TitleFieldKeywords-txt.JPG)|**Title field contains keywords** <br/> This condition checks if the **Title** field for an item contains a specific word. You can either specify the keyword in the String Builder???which can be a static value or a dynamic string or a combination ??? or insert a lookup to a field or variable. <br/> **Note:** You cannot search for more than one keyword in the **Title field contains keywords** condition. However, you can use logical operators such as**||**( or) or **&amp;&amp;** (and.          |
    
 
 ### Document set conditions
@@ -194,8 +195,8 @@ Some workflow conditions are only available when the workflow is associated to a
 
 |**VISIO CONDITION SHAPE**|**CORRESPONDING CONDITION IN SHAREPOINT DESIGNER**|**CONDITION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![File size is in a specific range](../../images/spd15-FileSzInSpecRange-visio.JPG)|This Visio condition is the same as the **The file size in a specific range kilobytes** condition in SharePoint Designer 2013 and appears as: <br/> ![File size is in a specific range](../../images/spd15-FileSzInSpecRange-txt.JPG)|**File size is in a specific range** <br/> This condition checks if the file size of a document is between the specified sizes, in kilobytes. The condition does not include the specified sizes in the evaluation. You can enter a number or use a lookup for the first or the second size in the condition.  <br/> |
-|![File is a specific type](../../images/spd15-FileIsSpecType-visio.JPG)|This Visio condition is the same as the **The file type is a specific type** condition in SharePoint Designer 2013 and appears as: <br/> ![File is a specific type](../../images/spd15-FileIsSpecType-txt.JPG)|**File is a specific type** <br/> This condition checks if the file type of the current item is of the specified type, such as docx. You can enter the file type as a string or use a lookup.  <br/> |
+|![File size is in a specific range](../images/spd15-FileSzInSpecRange-visio.JPG)|This Visio condition is the same as the **The file size in a specific range kilobytes** condition in SharePoint Designer 2013 and appears as: <br/> ![File size is in a specific range](../images/spd15-FileSzInSpecRange-txt.JPG)|**File size is in a specific range** <br/> This condition checks if the file size of a document is between the specified sizes, in kilobytes. The condition does not include the specified sizes in the evaluation. You can enter a number or use a lookup for the first or the second size in the condition.  <br/> |
+|![File is a specific type](../images/spd15-FileIsSpecType-visio.JPG)|This Visio condition is the same as the **The file type is a specific type** condition in SharePoint Designer 2013 and appears as: <br/> ![File is a specific type](../images/spd15-FileIsSpecType-txt.JPG)|**File is a specific type** <br/> This condition checks if the file type of the current item is of the specified type, such as docx. You can enter the file type as a string or use a lookup.  <br/> |
    
 
 ### List conditions
@@ -210,14 +211,14 @@ Some workflow conditions are only available when the workflow is associated to a
 
 |**VISIO CONDITION SHAPE**|**CORRESPONDING CONDITION IN SHAREPOINT DESIGNER**|**CONDITION DESCRIPTION**|
 |:-----|:-----|:-----|
-|![Check exact user permissions](../../images/spd15-ChkExactUserPerms-visio.JPG)|This Visio condition is the same as the **Check list item permission levels** condition in SharePoint Designer 2013 and appears as: <br/> ![Check list item permission levels](../../images/spd15-ChkExactUserPerms-txt.JPG)|**Check exact user permissions** <br/> This condition checks that the specified user has the minimum necessary permission level.  <br/> |
-|![Check user permissions](../../images/spd15-ChkUserPerms-visio.JPG)|This Visio condition is the same as the **Check list item permissions** condition in SharePoint Designer 2013 and appears as: <br/> ![Check list item permissions](../../images/spd15-ChkUserPerms-txt.JPG)|**Check user permission** <br/> This condition checks if the specified user has the minimum necessary permissions.  <br/> |
+|![Check exact user permissions](../images/spd15-ChkExactUserPerms-visio.JPG)|This Visio condition is the same as the **Check list item permission levels** condition in SharePoint Designer 2013 and appears as: <br/> ![Check list item permission levels](../images/spd15-ChkExactUserPerms-txt.JPG)|**Check exact user permissions** <br/> This condition checks that the specified user has the minimum necessary permission level.  <br/> |
+|![Check user permissions](../images/spd15-ChkUserPerms-visio.JPG)|This Visio condition is the same as the **Check list item permissions** condition in SharePoint Designer 2013 and appears as: <br/> ![Check list item permissions](../images/spd15-ChkUserPerms-txt.JPG)|**Check user permission** <br/> This condition checks if the specified user has the minimum necessary permissions.  <br/> |
    
 
 ## Workflow terminators
 <a name="section3"> </a>
 
-In Visio, each workflow must begin with a Start terminator (![Start](../../images/spd15-WFStart-icon.JPG)) and end with a Stop terminator (![Stop](../../images/spd15-WFStop-icon.JPG)). Only one of each type of terminator can be used in a given workflow. Terminators are necessary when you create a SharePoint workflow in Visio so that the workflow can pass validation and can be exported. Workflow terminators are not used in SharePoint Designer.
+In Visio, each workflow must begin with a Start terminator (![Start](../images/spd15-WFStart-icon.JPG)) and end with a Stop terminator (![Stop](../images/spd15-WFStop-icon.JPG)). Only one of each type of terminator can be used in a given workflow. Terminators are necessary when you create a SharePoint workflow in Visio so that the workflow can pass validation and can be exported. Workflow terminators are not used in SharePoint Designer.
   
     
     
@@ -226,13 +227,13 @@ In Visio, each workflow must begin with a Start terminator (![Start](../../image
 <a name="bk_addresources"> </a>
 
 
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/vss-requestors-and-sharepoint.md b/docs/general-development/vss-requestors-and-sharepoint.md
index 70f9463cbb..7c989a797a 100644
--- a/docs/general-development/vss-requestors-and-sharepoint.md
+++ b/docs/general-development/vss-requestors-and-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: VSS requestors and SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0b2e5a4e-40f0-4ccf-a21a-7274921f2169
 ---
 
@@ -82,13 +83,13 @@ Learn how to create and use a VSS requestor for SharePoint:
     
     
 
--  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint)
+-  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint.md)
     
   
--  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor)
+-  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md)
     
   
--  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using)
+-  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md)
     
   
 
@@ -96,16 +97,16 @@ Learn how to create and use a VSS requestor for SharePoint:
 <a name="bk_addresources"> </a>
 
 
--  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service)
+-  [Overview of SharePoint and the Volume Shadow Copy Service](overview-of-sharepoint-and-the-volume-shadow-copy-service.md)
     
   
--  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint)
+-  [How to: Create a VSS requestor for use with SharePoint](how-to-create-a-vss-requestor-for-use-with-sharepoint.md)
     
   
--  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor)
+-  [How to: Back up and restore SharePoint using a VSS requestor](how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md)
     
   
--  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using)
+-  [How to: Back up and restore a search service application in SharePoint using VSS](how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md)
     
   
 
diff --git a/docs/general-development/walkthrough-developing-a-custom-application-using-excel-web-services.md b/docs/general-development/walkthrough-developing-a-custom-application-using-excel-web-services.md
index 727b22125d..8722778f00 100644
--- a/docs/general-development/walkthrough-developing-a-custom-application-using-excel-web-services.md
+++ b/docs/general-development/walkthrough-developing-a-custom-application-using-excel-web-services.md
@@ -1,6 +1,7 @@
----
+---
 title: Walkthrough Developing a Custom Application Using Excel Web Services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 2f9bf243-281a-4d70-917e-9eaf0b867631
 ---
 
@@ -49,7 +50,7 @@ In order to complete this walkthrough, you will need:
 - A trusted location to store the workbooks that you want to access using Excel Web Services. If the workbooks are not stored in a trusted location, the Excel Web Services calls to open the workbook will fail. This walkthrough assumes the workbook is present on the local computer. 
     
     > **Note:**
-      > For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx). 
+      > For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location.md) and [How to: Trust Workbook Locations Using Script](http://msdn.microsoft.com/library/79ab6ced-7a0c-4275-b852-bb246fc6be57%28Office.15%29.aspx). 
 - To create the workbook using Excel.
     
   
@@ -84,35 +85,35 @@ The workbook used in this example has a worksheet named "Sheet1". The worksheet
   
     
     
- [Accessing the SOAP API](accessing-the-soap-api)
+ [Accessing the SOAP API](accessing-the-soap-api.md)
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
   
     
     
- [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking)
+ [Loop-Back SOAP Calls and Direct Linking](loop-back-soap-calls-and-direct-linking.md)
 #### Other resources
 
 
   
     
     
- [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project)
+ [Step 1: Creating the Web Service Client Project](step-1-creating-the-web-service-client-project.md)
   
     
     
- [Step 2: Adding a Web Reference](step-2-adding-a-web-reference)
+ [Step 2: Adding a Web Reference](step-2-adding-a-web-reference.md)
   
     
     
- [Step 3: Accessing the Web Service](step-3-accessing-the-web-service)
+ [Step 3: Accessing the Web Service](step-3-accessing-the-web-service.md)
   
     
     
- [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application)
+ [Step 4: Building and Testing the Application](step-4-building-and-testing-the-application.md)
diff --git a/docs/general-development/walkthrough-developing-a-managed-code-udf.md b/docs/general-development/walkthrough-developing-a-managed-code-udf.md
index 5983eeab31..be28b90c2c 100644
--- a/docs/general-development/walkthrough-developing-a-managed-code-udf.md
+++ b/docs/general-development/walkthrough-developing-a-managed-code-udf.md
@@ -1,6 +1,7 @@
 ---
 title: Walkthrough Developing a Managed-Code UDF
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e6a00833-0606-4a7d-91c3-b89a6e340348
 ---
 
@@ -65,7 +66,7 @@ In order to complete this walkthrough, you will need:
 - To save the workbook as an .xlsx or .xlsb file.
     
     > **Note:**
-      > For more information about how to trust a location, how to enable UDFs, and how to set the **AllowUdfs** flag, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs). 
+      > For more information about how to trust a location, how to enable UDFs, and how to set the **AllowUdfs** flag, see [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md). 
 
 ## See also
 
@@ -76,34 +77,34 @@ In order to complete this walkthrough, you will need:
   
     
     
- [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference)
+ [Step 1: Creating a Project and Adding a UDF Reference](step-1-creating-a-project-and-adding-a-udf-reference.md)
   
     
     
- [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf)
+ [Step 2: Creating a Managed-Code UDF](step-2-creating-a-managed-code-udf.md)
   
     
     
- [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs)
+ [Step 3: Deploying and Enabling UDFs](step-3-deploying-and-enabling-udfs.md)
   
     
     
- [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells)
+ [Step 4: Testing and Calling UDFs from Cells](step-4-testing-and-calling-udfs-from-cells.md)
   
     
     
- [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service)
+ [How to: Create a UDF That Calls a Web Service](how-to-create-a-udf-that-calls-a-web-service.md)
 #### Concepts
 
 
   
     
     
- [Understanding Excel Services UDFs](understanding-excel-services-udfs)
+ [Understanding Excel Services UDFs](understanding-excel-services-udfs.md)
 #### Other resources
 
 
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/walkthrough-developing-using-the-content-editor-web-part.md b/docs/general-development/walkthrough-developing-using-the-content-editor-web-part.md
index f0aeb4ddb8..643a6a8904 100644
--- a/docs/general-development/walkthrough-developing-using-the-content-editor-web-part.md
+++ b/docs/general-development/walkthrough-developing-using-the-content-editor-web-part.md
@@ -1,6 +1,7 @@
 ---
 title: Walkthrough Developing Using the Content Editor Web Part
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 0b5e74b7-405c-43c5-b2dd-1dff77280856
 ---
 
@@ -24,7 +25,7 @@ During this walkthrough, you will learn how to:
   
 
 > **Note:**
-> For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location). 
+> For information about how to trust a location, see  [How to: Trust a Location](how-to-trust-a-location.md). 
   
     
     
@@ -39,18 +40,18 @@ During this walkthrough, you will learn how to:
   
     
     
- [How to: Trust a Location](how-to-trust-a-location)
+ [How to: Trust a Location](how-to-trust-a-location.md)
 #### Concepts
 
 
   
     
     
- [Excel Services Alerts](excel-services-alerts)
+ [Excel Services Alerts](excel-services-alerts.md)
   
     
     
- [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips)
+ [Excel Services Known Issues and Tips](excel-services-known-issues-and-tips.md)
 #### Other resources
 
 
diff --git a/docs/general-development/what-s-changed-in-sharepoint-designer.md b/docs/general-development/what-s-changed-in-sharepoint-designer.md
index a4bb7b0165..25559b7472 100644
--- a/docs/general-development/what-s-changed-in-sharepoint-designer.md
+++ b/docs/general-development/what-s-changed-in-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: What's changed in SharePoint Designer 2013
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f1cd30c9-9a73-428d-9151-f1813b43b020
 ---
 
@@ -175,7 +176,7 @@ If you want to visually design or brand your site, and you want a WYSIWYG ("what
 <a name="WhatsChangedSharePointDesigner2013_AdditionalResources"> </a>
 
 
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 -  [Changes from SharePoint 2010 to SharePoint](http://technet.microsoft.com/en-us/library/ff607742%28v=office.15%29.aspx)
diff --git a/docs/general-development/what-s-new-for-developers-in-sharepoint.md b/docs/general-development/what-s-new-for-developers-in-sharepoint.md
index 00ee67df96..0c92c618dd 100644
--- a/docs/general-development/what-s-new-for-developers-in-sharepoint.md
+++ b/docs/general-development/what-s-new-for-developers-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: What's new for developers in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 068d0b99-1762-42de-b6c9-acb1cffc6e31
 ---
 
@@ -12,7 +13,7 @@ Learn about new features and functionality in SharePoint, including the new Clou
 
 SharePoint introduces a Cloud Add-in Model that enables you to create add-ins. SharePoint Add-ins are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An add-in may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint. An add-in has few or no dependencies on any other software on the device or platform where it is installed, other than what is built into the platform. This characteristic enables add-ins to be installed simply and uninstalled cleanly. Add-ins have no custom code that runs on the SharePoint servers. Instead, all custom logic moves "up" to the cloud or "down" to client computers. Additionally, SharePoint introduces an innovative delivery model for SharePoint Add-ins that includes components like the Office Store and the Add-in Catalog.
 
-<a href="../sp-add-ins/sharepoint-add-ins"><img alt="SharePoint Add-ins" src="../../images/wn_cloud_1.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in"><img alt="SharePoint Store" src="../../images/wn_cloud_2.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in"><img alt="Add-ins Catalog" src="../../images/wn_cloud_3.png" /></a>
+<a href="../sp-add-ins/sharepoint-add-ins.md"><img alt="SharePoint Add-ins" src="../images/wn_cloud_1.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md"><img alt="SharePoint Store" src="../images/wn_cloud_2.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md"><img alt="Add-ins Catalog" src="../images/wn_cloud_3.png" /></a>
 
 ## Familiar programming model using web standards
 <a name="bmWebStandards"> </a>
@@ -20,7 +21,7 @@ SharePoint introduces a Cloud Add-in Model that enables you to create add-ins. S
 SharePoint makes it easy for any web developer, including those who work on non-Microsoft platform stacks, to create SharePoint solutions. What makes this possible is that SharePoint is based on common web standards like HTML, CSS, and JavaScript. Furthermore, implementation relies on established protocols like the Open Data protocol (OData), and OAuth.
   
 
-  <a href="../sp-add-ins/sharepoint-add-ins"><img alt="HTML/JavaScript" src="../../images/wn_WebStandards_1.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/using-odata-sources-with-business-connectivity-services-in-sharepoint"><img alt="OData" src="../../images/wn_WebStandards_2.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/get-to-know-the-sharepoint-rest-service" target="_blank"><img alt="REST" src="../../images/wn_WebStandards_3.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins"><img alt="OAuth" src="../../images/wn_WebStandards_4.png" /></a>
+  <a href="../sp-add-ins/sharepoint-add-ins.md"><img alt="HTML/JavaScript" src="../images/wn_WebStandards_1.png" /></a>&nbsp;&nbsp;<a href="using-odata-sources-with-business-connectivity-services-in-sharepoint.md"><img alt="OData" src="../images/wn_WebStandards_2.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/get-to-know-the-sharepoint-rest-service.md" target="_blank"><img alt="REST" src="../images/wn_WebStandards_3.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md"><img alt="OAuth" src="../images/wn_WebStandards_4.png" /></a>
 
 
 ## Development tools
@@ -28,14 +29,14 @@ SharePoint makes it easy for any web developer, including those who work on non-
 
 The current release reflects enormous strides in optimizing the existing development tools like Visual Studio and SharePoint Designer, in addition to providing the release of newly developed web-based tool Napa Office 365 Development Tools for developing add-ins. The new unified project system in Visual Studio lets you develop SharePoint Add-ins, Office Add-ins, SharePoint Add-ins that include Office Add-ins, or Office Add-ins that are hosted by SharePoint. In addition to the SharePoint project templates that were provided in earlier versions, Visual Studio 2012 now includes a new add-in project template in the Add-ins folder named Add-ins for SharePoint. Several new properties have been added to the Properties window and Properties pages to support SharePoint Add-in projects. Other improvements include full support for development against the Cloud Add-in Model, including OData and OAuth support, and full support for development against the Workflow Manager Client 1.0 platform.
 
-<a href="https://dev.office.com/docs/add-ins/overview/office-add-ins" target="_blank"><img alt="Napa Office 365 Development Tools" src="../../images/wn_DevTools_1.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio"><img alt="Visual Studio" src="../../images/wn_DevTools_2.png" /></a>&nbsp;&nbsp;<a href="workflow-development-in-sharepoint-designer-and-visio"><img alt="SharePoint Designer" src="../../images/wn_DevTools_3.png" /></a>
+<a href="https://dev.office.com/docs/add-ins/overview/office-add-ins" target="_blank"><img alt="Napa Office 365 Development Tools" src="../images/wn_DevTools_1.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md"><img alt="Visual Studio" src="../images/wn_DevTools_2.png" /></a>&nbsp;&nbsp;<a href="workflow-development-in-sharepoint-designer-and-visio.md"><img alt="SharePoint Designer" src="../images/wn_DevTools_3.png" /></a>
 
 ## Core platform enhancements
 <a name="bmPlatformEnhance"> </a>
 
 On a broader scale, SharePoint has been improved and enhanced to support the new cloud-based architecture and app-driven development framework. From the SharePoint APIs at the lowest level to connectivity to social media integration, SharePoint is designed and executed to support a rich application development experience. In addition to the use of Representational State Transfer (REST) endpoints for web services, there is a broad new API for both server and client development. Remote event receivers and now supported in addition to client-side rendering. 
   
-<a href="https://msdn.microsoft.com/library/fp161347.aspx" target="_blank"><img alt="REST endpoints" src="../../images/wn_Platform_1.png" /></a>&nbsp;&nbsp;<a href="choose-the-right-api-set-in-sharepoint"><img alt="New client and server APIs" src="../../images/wn_Platform_2.png" /></a>&nbsp;&nbsp;<a href="how-to-customize-a-field-type-using-client-side-rendering"><img alt="Client-side rendering" src="../../images/wn_Platform_3.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/handle-events-in-sharepoint-add-ins"><img alt="Remote event receivers" src="../../images/wn_Platform_4.png" /></a>
+<a href="https://msdn.microsoft.com/library/fp161347.aspx" target="_blank"><img alt="REST endpoints" src="../images/wn_Platform_1.png" /></a>&nbsp;&nbsp;<a href="choose-the-right-api-set-in-sharepoint.md"><img alt="New client and server APIs" src="../images/wn_Platform_2.png" /></a>&nbsp;&nbsp;<a href="how-to-customize-a-field-type-using-client-side-rendering.md"><img alt="Client-side rendering" src="../images/wn_Platform_3.png" /></a>&nbsp;&nbsp;<a href="../sp-add-ins/handle-events-in-sharepoint-add-ins.md"><img alt="Remote event receivers" src="../images/wn_Platform_4.png" /></a>
 
     
     
@@ -46,68 +47,68 @@ On a broader scale, SharePoint has been improved and enhanced to support the new
 
 With SharePoint, you can combine Windows Phone 7 applications with on-premises SharePoint services and applications, or with remote SharePoint services and applications that run in the cloud (such as those that use SharePoint Online), to create powerful applications that extend functionality beyond the traditional desktop or laptop and into a truly portable and much more accessible environment. The new mobility features in SharePoint are built on existing Microsoft tools and technologies, such as SharePoint, Windows Phone 7, Visual Studio, and Microsoft Silverlight. You can create SharePoint-powered mobile applications for Windows Phone using the new SharePoint phone application wizard template in Visual Studio, which lets you create simple list-based mobile applications. You can integrate new features introduced in SharePoint, such as the Geolocation field type and "push" notifications from SharePoint Server, into your mobile applications.
 
-<a href="overview-of-windows-phone-sharepoint-application-templates-in-visual-studio"><img alt="Visual Studio app templates" src="../../images/wn_Mobility_.png" /></a>&nbsp;&nbsp;<a href="how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows"><img alt="Push notifications" src="../../images/wn_Mobility_2.png" /></a>&nbsp;&nbsp;<a href="integrating-location-and-map-functionality-in-sharepoint"><img alt="Location and maps" src="../../images/wn_Mobility_3.png" /></a>
+<a href="overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md"><img alt="Visual Studio app templates" src="../images/wn_Mobility_.png" /></a>&nbsp;&nbsp;<a href="how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md"><img alt="Push notifications" src="../images/wn_Mobility_2.png" /></a>&nbsp;&nbsp;<a href="integrating-location-and-map-functionality-in-sharepoint.md"><img alt="Location and maps" src="../images/wn_Mobility_3.png" /></a>
 
 ## Social and collaboration
 <a name="bmSocial"> </a>
 
 New and improved social and collaboration features make it easy for users to communicate and to stay engaged and informed. The improved My Site social feed helps users keep up to date with the people and content that they care about. The new Community Site feature provides a rich community experience that lets users easily find and share information and find people who have similar interests.
 
-<a href="work-with-social-feeds-in-sharepoint"><img alt="Interactive feed" src="../../images/wn_Social_1.png" /></a>&nbsp;&nbsp;<a href="what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201#bkmk_Collab"><img alt="Community site" src="../../images/wn_Social_2.png" /></a>&nbsp;&nbsp;<a href="follow-people-in-sharepoint"><img alt="Follow people" src="../../images/wn_Social_3.png" /></a>&nbsp;&nbsp;<a href="follow-content-in-sharepoint"><img alt="Follow sites" src="../../images/wn_Social_4.png" /></a>
+<a href="work-with-social-feeds-in-sharepoint.md"><img alt="Interactive feed" src="../images/wn_Social_1.png" /></a>&nbsp;&nbsp;<a href="what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md#bkmk_Collab"><img alt="Community site" src="../images/wn_Social_2.png" /></a>&nbsp;&nbsp;<a href="follow-people-in-sharepoint.md"><img alt="Follow people" src="../images/wn_Social_3.png" /></a>&nbsp;&nbsp;<a href="follow-content-in-sharepoint.md"><img alt="Follow sites" src="../images/wn_Social_4.png" /></a>
 
 ## Search
 <a name="bmSearch"> </a>
 
 Search functionality in SharePoint includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Additionally, there have been significant enhancements made to the keyword query language (KQL).
 
-<a href="custom-content-processing-with-the-content-enrichment-web-service-callout"><img alt="Consolidated search platform" src="../../images/wn_search_1.png" /></a>&nbsp;&nbsp;<a href="what-s-new-in-sharepoint-search-for-developers"><img alt="Rich results framework" src="../../images/wn_search_2.png" /></a>&nbsp;&nbsp;<a href="building-search-queries-in-sharepoint"><img alt="KQL enhnacements" src="../../images/wn_search_3.png" /></a>
+<a href="custom-content-processing-with-the-content-enrichment-web-service-callout.md"><img alt="Consolidated search platform" src="../images/wn_search_1.png" /></a>&nbsp;&nbsp;<a href="what-s-new-in-sharepoint-search-for-developers.md"><img alt="Rich results framework" src="../images/wn_search_2.png" /></a>&nbsp;&nbsp;<a href="building-search-queries-in-sharepoint.md"><img alt="KQL enhnacements" src="../images/wn_search_3.png" /></a>
 
 ## Workflows
 <a name="bmWorkflow"> </a>
 
 Workflow Manager Client 1.0 is a redesigned workflow infrastructure that is built on Windows Workflow Foundation 4 and brings new power and flexibility to workflow authoring in SharePoint. A fully declarative authoring environment enables information workers to use SharePoint Designer 2013 to author powerful workflows, and a new set of Visual Studio 2012 workflow project templates let developers access more sophisticated features like custom actions. Perhaps most importantly, Workflow Manager Client 1.0 is fully integrated with the model for SharePoint Add-ins. In addition, workflows execute in the cloud, not in SharePoint, which provides enormous flexibility in designing workflow-based SharePoint Add-ins.
 
-<a href="what-s-new-in-workflows-for-sharepoint"><img alt="Execute in the cloud" src="../../images/wn_workflow_1.png" /></a>&nbsp;&nbsp;<a href="sharepoint-workflow-fundamentals"><img alt="Workflow 4-based infrastructure" src="../../images/wn_workflow_2.png" /></a>&nbsp;&nbsp;<a href="workflow-development-in-sharepoint-designer-and-visio"><img alt="Declarative authoring" src="../../images/wn_workflow_3.png" /></a>&nbsp;&nbsp;<a href="develop-sharepoint-workflows-using-visual-studio"><img alt="Designer and project templates" src="../../images/wn_workflow_4.png" /></a>
+<a href="what-s-new-in-workflows-for-sharepoint.md"><img alt="Execute in the cloud" src="../images/wn_workflow_1.png" /></a>&nbsp;&nbsp;<a href="sharepoint-workflow-fundamentals.md"><img alt="Workflow 4-based infrastructure" src="../images/wn_workflow_2.png" /></a>&nbsp;&nbsp;<a href="workflow-development-in-sharepoint-designer-and-visio.md"><img alt="Declarative authoring" src="../images/wn_workflow_3.png" /></a>&nbsp;&nbsp;<a href="develop-sharepoint-workflows-using-visual-studio.md"><img alt="Designer and project templates" src="../images/wn_workflow_4.png" /></a>
 
 ## Enterprise Content Management
 <a name="bmECM"> </a>
 
 In SharePoint, you can now use .NET client, Silverlight, Windows Phone, and JavaScript APIs, in addition to the newly expanded set of .NET server managed APIs, to customize Enterprise Content Management (ECM) experiences and behavior.
 
-<a href="what-s-new-with-sharepoint-site-development"><img alt="Design Manager" src="../../images/wn_ecm_1.png" /></a>&nbsp;&nbsp;<a href="managed-navigation-in-sharepoint"><img alt="Managed navigation" src="../../images/wn_ecm_2.png" /></a>&nbsp;&nbsp;<a href="cross-site-publishing-in-sharepoint"><img alt="Cross-site publishing" src="../../images/wn_ecm_3.png" /></a>&nbsp;&nbsp;<a href="ediscovery-in-sharepoint"><img alt="EDiscovery" src="../../images/wn_ecm_4.png" /></a>
+<a href="what-s-new-with-sharepoint-site-development.md"><img alt="Design Manager" src="../images/wn_ecm_1.png" /></a>&nbsp;&nbsp;<a href="managed-navigation-in-sharepoint.md"><img alt="Managed navigation" src="../images/wn_ecm_2.png" /></a>&nbsp;&nbsp;<a href="cross-site-publishing-in-sharepoint.md"><img alt="Cross-site publishing" src="../images/wn_ecm_3.png" /></a>&nbsp;&nbsp;<a href="ediscovery-in-sharepoint.md"><img alt="EDiscovery" src="../images/wn_ecm_4.png" /></a>
 
 ## Business Connectivity Services
 <a name="bmBCS"> </a>
 
 Business Connectivity Services (BCS) enables SharePoint to access data from external data systems such as SAP, ERP, and CRM, in addition to other data-driven applications that are exposed through WCF services or OData endpoints. BCS in SharePoint has been improved and enhanced in many ways, including OData connectivity, external events, external data in add-ins, filtering and sorting, support for REST, and others.
 
-<a href="using-odata-sources-with-business-connectivity-services-in-sharepoint"><img alt="OData connector" src="../../images/wn_bcs_1.png" /></a>&nbsp;&nbsp;<a href="add-in-scoped-external-content-types-in-sharepoint"><img alt="External data in apps" src="../../images/wn_bcs_2.png" /></a>&nbsp;&nbsp;<a href="external-events-and-alerts-in-sharepoint"><img alt="External events in SharePoint" src="../../images/wn_bcs_3.png" /></a>
+<a href="using-odata-sources-with-business-connectivity-services-in-sharepoint.md"><img alt="OData connector" src="../images/wn_bcs_1.png" /></a>&nbsp;&nbsp;<a href="add-in-scoped-external-content-types-in-sharepoint.md"><img alt="External data in apps" src="../images/wn_bcs_2.png" /></a>&nbsp;&nbsp;<a href="external-events-and-alerts-in-sharepoint.md"><img alt="External events in SharePoint" src="../images/wn_bcs_3.png" /></a>
 
 ## Application services
 <a name="bmSpServices"> </a>
 
 SharePoint includes several services for working with data in your SharePoint sites. New for SharePoint is the Machine Translation Service, which translates sites, documents, and streams for multilingual support. SharePoint also includes Access Services and a new data access model. For converting files and streams to other formats, SharePoint has Word Automation Services and PowerPoint Automation Services (a new feature for SharePoint). SharePoint also provides data analysis tools, like PerformancePoint Services and Visio Services, that enable business intelligence, and powerful new features in Excel Services.
 
-<a href="external-events-and-alerts-in-sharepoint"><img alt="Translation Services" src="../../images/wn_appServices_1.png" /></a>&nbsp;&nbsp;<a href="powerpoint-automation-services-in-sharepoint"><img alt="PowerPoint Automation Services" src="../../images/wn_appServices_2.png" /></a>&nbsp;&nbsp;<a href="what-s-new-in-access"><img alt="Enhanced Access Services" src="../../images/wn_appServices_3.png" /></a>&nbsp;&nbsp;<a href="https://msdn.microsoft.com/library/fp161347.aspx" target="_blank"><img alt="Enhanced Excel Services" src="../../images/wn_appServices_4.png" /></a>
+<a href="external-events-and-alerts-in-sharepoint.md"><img alt="Translation Services" src="../images/wn_appServices_1.png" /></a>&nbsp;&nbsp;<a href="powerpoint-automation-services-in-sharepoint.md"><img alt="PowerPoint Automation Services" src="../images/wn_appServices_2.png" /></a>&nbsp;&nbsp;<a href="what-s-new-in-access.md"><img alt="Enhanced Access Services" src="../images/wn_appServices_3.png" /></a>&nbsp;&nbsp;<a href="https://msdn.microsoft.com/library/fp161347.aspx" target="_blank"><img alt="Enhanced Excel Services" src="../images/wn_appServices_4.png" /></a>
 
 
 ## Additional resources
 <a name="bm_Addres"> </a>
 
 
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
--  [Develop SharePoint Add-ins](../sp-add-ins/sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](../sp-add-ins/sharepoint-add-ins.md)
     
   
--  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions)
+-  [SharePoint Add-ins compared with SharePoint solutions](sharepoint-add-ins-compared-with-sharepoint-solutions.md)
     
   
--  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint)
+-  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md)
     
   
--  [Accessibility in SharePoint](accessibility-in-sharepoint)
+-  [Accessibility in SharePoint](accessibility-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md b/docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md
index 2b7fd9da42..01311065fa 100644
--- a/docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md
+++ b/docs/general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md
@@ -1,6 +1,7 @@
 ---
 title: What's new for developers in social and collaboration features in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 65365b1d-cde5-47cd-8b04-1b76be0e3490
 ---
 
@@ -12,7 +13,7 @@ Social and collaboration features in SharePoint make it easy for users to commun
     
     
 
-For an in-depth overview of the new social and collaboration features in SharePoint, see  [What's new in social computing in SharePoint](http://technet.microsoft.com/en-us/library/jj219766%28v=office.15%29) on TechNet. For more information about programming with social and collaboration features, see [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint).
+For an in-depth overview of the new social and collaboration features in SharePoint, see  [What's new in social computing in SharePoint](http://technet.microsoft.com/en-us/library/jj219766%28v=office.15%29) on TechNet. For more information about programming with social and collaboration features, see [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md).
 ## New and changed My Site features in SharePoint
 <a name="bkmk_Social"> </a>
 
@@ -49,7 +50,7 @@ Not all server-side functionality in the Microsoft.Office.Server.UserProfiles as
   
     
     
-For information about how to access the My Site Social client APIs, see  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint). For more information about the API sets in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+For information about how to access the My Site Social client APIs, see  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md). For more information about the API sets in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -293,13 +294,13 @@ while (retries <= 10)
 <a name="SP15NewSocial_addlresources"> </a>
 
 
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [What's new for developers in SharePoint](what???s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
 -  [What's new in social computing in SharePoint](http://technet.microsoft.com/en-us/library/jj219766%28v=office.15%29)
diff --git a/docs/general-development/what-s-new-in-access.md b/docs/general-development/what-s-new-in-access.md
index adfa4f9e6b..ddcb0e402d 100644
--- a/docs/general-development/what-s-new-in-access.md
+++ b/docs/general-development/what-s-new-in-access.md
@@ -1,6 +1,7 @@
----
+---
 title: What's new in Access
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 625bc1d0-55db-4420-a02e-aee04028b215
 ---
 
@@ -40,7 +41,7 @@ Figure 1 provides an overview of Access 2013 architecture.
   
     
     
-![Access 2013 architecture](../../images/odc_Office15_Access15OverviewDK2_Figure07.jpg)
+![Access 2013 architecture](../images/odc_Office15_Access15OverviewDK2_Figure07.jpg)
   
     
     
diff --git a/docs/general-development/what-s-new-in-business-connectivity-services-in-sharepoint.md b/docs/general-development/what-s-new-in-business-connectivity-services-in-sharepoint.md
index 50f25df1d3..29a8de316e 100644
--- a/docs/general-development/what-s-new-in-business-connectivity-services-in-sharepoint.md
+++ b/docs/general-development/what-s-new-in-business-connectivity-services-in-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: What's new in Business Connectivity Services in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 3c96be6a-a8ff-43ad-8361-999293aff71f
 ---
 
@@ -26,26 +27,26 @@ BCS is improved and enhanced for SharePoint, including the new functionality lis
 
 |**New feature**|**For more information**|
 |:-----|:-----|
-|SharePoint can now connect to OData sources.  <br/> | [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint) <br/> |
-|SharePoint can receive events from external systems.  <br/> | [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint) <br/> |
-|External content types can now be scoped at the application level.  <br/> | [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint) <br/> |
-|Support for Representational State Transfer (REST) and the client object model is enhanced.  <br/> | [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint) <br/> |
+|SharePoint can now connect to OData sources.  <br/> | [Using OData sources with Business Connectivity Services in SharePoint](using-odata-sources-with-business-connectivity-services-in-sharepoint.md) <br/> |
+|SharePoint can receive events from external systems.  <br/> | [External events and alerts in SharePoint](external-events-and-alerts-in-sharepoint.md) <br/> |
+|External content types can now be scoped at the application level.  <br/> | [Add-in-scoped external content types in SharePoint](add-in-scoped-external-content-types-in-sharepoint.md) <br/> |
+|Support for Representational State Transfer (REST) and the client object model is enhanced.  <br/> | [Get started using the client object model with external data in SharePoint](get-started-using-the-client-object-model-with-external-data-in-sharepoint.md) <br/> |
    
 
 ## Additional resources
 <a name="SP15whatsnewBCS_addresources"> </a>
 
 
--  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint)
+-  [Business Connectivity Services in SharePoint](business-connectivity-services-in-sharepoint.md)
     
   
--  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint)
+-  [Get started with Business Connectivity Services in SharePoint](get-started-with-business-connectivity-services-in-sharepoint.md)
     
   
--  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint)
+-  [Business Connectivity Services programmers reference for SharePoint](business-connectivity-services-programmers-reference-for-sharepoint.md)
     
   
--  [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/what-s-new-in-excel-web-services.md b/docs/general-development/what-s-new-in-excel-web-services.md
index 967542a9ab..60e2bd8c16 100644
--- a/docs/general-development/what-s-new-in-excel-web-services.md
+++ b/docs/general-development/what-s-new-in-excel-web-services.md
@@ -1,6 +1,7 @@
 ---
 title: What's New in Excel Web Services
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: cb342e94-0308-4608-b027-b73ebe8107b0
 ---
 
@@ -119,4 +120,4 @@ The following are new types added to Excel Web Services, in alphabetical order:
   
     
     
- [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services)
+ [Walkthrough: Developing a Custom Application Using Excel Web Services](walkthrough-developing-a-custom-application-using-excel-web-services.md)
diff --git a/docs/general-development/what-s-new-in-sharepoint-ediscovery-and-compliance.md b/docs/general-development/what-s-new-in-sharepoint-ediscovery-and-compliance.md
index f84d58726e..8dd12c9039 100644
--- a/docs/general-development/what-s-new-in-sharepoint-ediscovery-and-compliance.md
+++ b/docs/general-development/what-s-new-in-sharepoint-ediscovery-and-compliance.md
@@ -1,6 +1,7 @@
 ---
 title: What's new in SharePoint eDiscovery and compliance
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 39a1cc3f-c78d-478f-8c15-928b96386a52
 ---
 
@@ -94,7 +95,7 @@ Sites, and other large objects, sometimes require that their users comply with a
 <a name="bk_addresources"> </a>
 
 
--  [eDiscovery in SharePoint](ediscovery-in-sharepoint)
+-  [eDiscovery in SharePoint](ediscovery-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/what-s-new-in-sharepoint-search-for-developers.md b/docs/general-development/what-s-new-in-sharepoint-search-for-developers.md
index dea791227e..59f65e4cbb 100644
--- a/docs/general-development/what-s-new-in-sharepoint-search-for-developers.md
+++ b/docs/general-development/what-s-new-in-sharepoint-search-for-developers.md
@@ -1,6 +1,7 @@
 ---
 title: What's new in SharePoint search for developers
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b8d69685-3612-421e-b011-50b4d580d461
 ---
 
@@ -30,7 +31,7 @@ The Search CSOM returns the search results data from the server in JavaScript Ob
 ## SQL Syntax Support Removed
 <a name="SP15Searchnew_support"> </a>
 
-Custom search solutions in SharePoint do not support  [SQL syntax](http://msdn.microsoft.com/en-us/library/ee558869). Search in SharePoint supports FQL syntax and KQL syntax for custom search solutions. You cannot use SQL syntax in custom search solutions using any technologies, including the Query server object model, the client object model, and the Search REST service. Custom search solutions that use SQL syntax with the Query server object model and the Query web service that were created in earlier versions of SharePoint Server will not work when you upgrade them to SharePoint. Queries submitted via these applications will return an error. For more information about using FQL syntax and KQL syntax, see  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference) and [FAST Query Language (FQL) syntax reference](fast-query-language-fql-syntax-reference).
+Custom search solutions in SharePoint do not support  [SQL syntax](http://msdn.microsoft.com/en-us/library/ee558869). Search in SharePoint supports FQL syntax and KQL syntax for custom search solutions. You cannot use SQL syntax in custom search solutions using any technologies, including the Query server object model, the client object model, and the Search REST service. Custom search solutions that use SQL syntax with the Query server object model and the Query web service that were created in earlier versions of SharePoint Server will not work when you upgrade them to SharePoint. Queries submitted via these applications will return an error. For more information about using FQL syntax and KQL syntax, see  [Keyword Query Language (KQL) syntax reference](keyword-query-language-kql-syntax-reference.md) and [FAST Query Language (FQL.md) syntax reference](fast-query-language-fql-syntax-reference.md).
   
     
     
@@ -245,7 +246,7 @@ SharePoint Search enables you to retrieve claims information for content stored
   
     
     
-The connector framework also provides improved exception capturing and logging to help you troubleshoot errors encountered when crawling content sources using custom connectors that are built on top of the connector framework. For information about the connector framework, see  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint).
+The connector framework also provides improved exception capturing and logging to help you troubleshoot errors encountered when crawling content sources using custom connectors that are built on top of the connector framework. For information about the connector framework, see  [Search connector framework in SharePoint](search-connector-framework-in-sharepoint.md).
   
     
     
@@ -254,16 +255,16 @@ The connector framework also provides improved exception capturing and logging t
 <a name="bk_addresources"> </a>
 
 
--  [Searching new content with SharePoint Search](searching-new-content-with-sharepoint-search)
+-  [Searching new content with SharePoint Search](searching-new-content-with-sharepoint-search.md)
     
   
--  [Configure search in SharePoint](configure-search-in-sharepoint)
+-  [Configure search in SharePoint](configure-search-in-sharepoint.md)
     
   
--  [Building search queries in SharePoint](building-search-queries-in-sharepoint)
+-  [Building search queries in SharePoint](building-search-queries-in-sharepoint.md)
     
   
--  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results)
+-  [How to: Use a custom security trimmer for SharePoint Server search results](how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md)
     
   
 
diff --git a/docs/general-development/what-s-new-in-word-automation-services-for-developers.md b/docs/general-development/what-s-new-in-word-automation-services-for-developers.md
index 5e3e73c692..914c9e3f9f 100644
--- a/docs/general-development/what-s-new-in-word-automation-services-for-developers.md
+++ b/docs/general-development/what-s-new-in-word-automation-services-for-developers.md
@@ -1,6 +1,7 @@
 ---
 title: What's new in Word Automation Services for developers
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 00d2cf8d-93b0-4aab-8e76-31a6bb2f0dcb
 ---
 
@@ -32,7 +33,7 @@ One way to think about the difference between on demand file conversion requests
   
     
     
-![Word Automation Services 2013 architecture](../../images/SPS15CON_WAS_Architecture.png)
+![Word Automation Services 2013 architecture](../images/SPS15CON_WAS_Architecture.png)
   
     
     
diff --git a/docs/general-development/what-s-new-in-workflows-for-sharepoint.md b/docs/general-development/what-s-new-in-workflows-for-sharepoint.md
index 0b20dc7fee..12619e87b3 100644
--- a/docs/general-development/what-s-new-in-workflows-for-sharepoint.md
+++ b/docs/general-development/what-s-new-in-workflows-for-sharepoint.md
@@ -1,6 +1,7 @@
----
+---
 title: What's new in workflows for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 1d51421b-61ac-46b6-a865-52f968ddc5b3
 ---
 
@@ -20,7 +21,7 @@ SharePoint workflows are powered by Windows Workflow Foundation 4 (WF), which wa
   
     
     
-Perhaps the most prominent feature of the new workflow infrastructure is the introduction of Microsoft Azure as the new workflow execution host. The workflow execution engine now lives outside of SharePoint, in Microsoft Azure. Figure 1 provides a generalized, high-level view of the new workflow infrastructure. For a more thorough discussion of the concepts presented in Figure 1, see  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals).
+Perhaps the most prominent feature of the new workflow infrastructure is the introduction of Microsoft Azure as the new workflow execution host. The workflow execution engine now lives outside of SharePoint, in Microsoft Azure. Figure 1 provides a generalized, high-level view of the new workflow infrastructure. For a more thorough discussion of the concepts presented in Figure 1, see  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md).
   
     
     
@@ -34,7 +35,7 @@ Perhaps the most prominent feature of the new workflow infrastructure is the int
   
     
     
-![High-level workflow architecture](../../images/wfArchitecture1.png)
+![High-level workflow architecture](../images/wfArchitecture1.png)
   
     
     
@@ -70,7 +71,7 @@ In short, the needs of both the information worker (the "power user") and the de
 ## Visual Studio 2012 workflow project type support
 <a name="SP15Whatsnewinworflow_VSworkflow"> </a>
 
-To make collaboration easier between information worker and software developer, Visual Studio 2012 provides SharePoint workflow project types and a workflow custom action-item type. For more information about developing workflows by using Visual Studio 2012, and for information about differentiating between SharePoint Designer 2013 and Visual Studio 2012 in workflow development, see  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio).
+To make collaboration easier between information worker and software developer, Visual Studio 2012 provides SharePoint workflow project types and a workflow custom action-item type. For more information about developing workflows by using Visual Studio 2012, and for information about differentiating between SharePoint Designer 2013 and Visual Studio 2012 in workflow development, see  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md).
   
     
     
@@ -78,7 +79,7 @@ To make collaboration easier between information worker and software developer,
 ## Support for creating custom actions
 <a name="SP15Whatsnewinworflow_customactions"> </a>
 
-A lot of effort has gone into anticipating the business requirements of workflow authors in the providing of workflow templates, actions, and activities in SharePoint Designer 2013 and in Visual Studio 2012. However, we also know that we cannot anticipate each person's specific needs. For this reason, Visual Studio 2012 provides a workflow custom action-item type that lets developers create custom actions. For more information about workflow custom actions, see  [How to: Build and deploy workflow custom actions](how-to-build-and-deploy-workflow-custom-actions).
+A lot of effort has gone into anticipating the business requirements of workflow authors in the providing of workflow templates, actions, and activities in SharePoint Designer 2013 and in Visual Studio 2012. However, we also know that we cannot anticipate each person's specific needs. For this reason, Visual Studio 2012 provides a workflow custom action-item type that lets developers create custom actions. For more information about workflow custom actions, see  [How to: Build and deploy workflow custom actions](how-to-build-and-deploy-workflow-custom-actions.md).
   
     
     
@@ -94,7 +95,7 @@ Visual Studio 2012 provides templates and support for creating workflows on the
 ## New workflow actions
 <a name="SP15Whatsnewinworflow_Newwfactions"> </a>
 
-Following are new workflow actions that are provided in SharePoint. For a full detailing of both new and deprecated actions, see  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint). New to workflows in SharePoint are a set of workflow actions that allow you to integrate with Project 2013 and let you create Project-based workflows.
+Following are new workflow actions that are provided in SharePoint. For a full detailing of both new and deprecated actions, see  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md). New to workflows in SharePoint are a set of workflow actions that allow you to integrate with Project 2013 and let you create Project-based workflows.
   
     
     
@@ -129,16 +130,16 @@ Following are new workflow actions that are provided in SharePoint. For a full d
 <a name="SP15Whatsnewinworflow_Addresources"> </a>
 
 
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [What's new for developers in SharePoint](what’s-new-for-developers-in-sharepoint)
+-  [What's new for developers in SharePoint](what-s-new-for-developers-in-sharepoint.md)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
 
diff --git a/docs/general-development/what-s-new-with-sharepoint-site-development.md b/docs/general-development/what-s-new-with-sharepoint-site-development.md
index cced8d5f34..ae4b4f1aa4 100644
--- a/docs/general-development/what-s-new-with-sharepoint-site-development.md
+++ b/docs/general-development/what-s-new-with-sharepoint-site-development.md
@@ -1,6 +1,7 @@
----
+---
 title: What's new with SharePoint site development
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: ac1e9891-5ce9-4707-84e5-6e2fc02fda6b
 ---
 
@@ -47,15 +48,15 @@ SharePoint includes features and APIs that you can use to author, design, brand,
 
 ### Design Manager
 
-In previous versions of SharePoint, branding a site required specific technical expertise about things like what content placeholders are required on a master page, or how a master page implements certain classes of styles. SharePoint introduces  [Design Manager](overview-of-design-manager-in-sharepoint)—a new interface and central hub for managing all aspects of branding your SharePoint site. You can find the Design Manager in the top-level site for your site collection. It is a part of the Publishing Portal site collection template in SharePoint.
+In previous versions of SharePoint, branding a site required specific technical expertise about things like what content placeholders are required on a master page, or how a master page implements certain classes of styles. SharePoint introduces  [Design Manager](overview-of-design-manager-in-sharepoint.md)—a new interface and central hub for managing all aspects of branding your SharePoint site. You can find the Design Manager in the top-level site for your site collection. It is a part of the Publishing Portal site collection template in SharePoint.
   
     
     
-Design Manager enables a step-by-step approach for creating design assets that you can use to brand sites. Upload design assets—images, HTML, CSS, and so on—and then create your master pages and page layouts. You can preview how your design looks either in a client-side code editor or on the server as you are designing it. You can add custom SharePoint components and ribbon elements by using the Design Manager UI. The Design Manager generates HTML  [snippets](sharepoint-design-manager-snippets) that can be used by any web design tool—it renders HTML and ignores ASP.NET and SharePoint markup (while SharePoint renders only ASP.NET and SharePoint markup and ignores HTML).
+Design Manager enables a step-by-step approach for creating design assets that you can use to brand sites. Upload design assets—images, HTML, CSS, and so on—and then create your master pages and page layouts. You can preview how your design looks either in a client-side code editor or on the server as you are designing it. You can add custom SharePoint components and ribbon elements by using the Design Manager UI. The Design Manager generates HTML  [snippets](sharepoint-design-manager-snippets.md) that can be used by any web design tool—it renders HTML and ignores ASP.NET and SharePoint markup (while SharePoint renders only ASP.NET and SharePoint markup and ignores HTML.md).
   
     
     
-You can use your expertise in HTML, CSS, and JavaScript to design master pages in HTML, and design HTML page layouts in the HTML editor of your choice. To connect your favorite authoring and design tool to your SharePoint site,  [map a network drive](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery) and then edit the SharePoint file as if it were a local file. When your site design is ready, upload the HTML and supporting files and use Design Manager to [convert the HTML file into an ASP.NET master page (.master) file](how-to-convert-an-html-file-into-a-master-page-in-sharepoint). Now,  [apply the master page](how-to-apply-a-master-page-to-a-site-in-sharepoint) to your SharePoint site. Use Design Manager to [create a new page layout](how-to-create-a-page-layout-in-sharepoint), and the HTML version of it is automatically associated with the corresponding ASP.NET page (.aspx file) that SharePoint interprets. 
+You can use your expertise in HTML, CSS, and JavaScript to design master pages in HTML, and design HTML page layouts in the HTML editor of your choice. To connect your favorite authoring and design tool to your SharePoint site,  [map a network drive](how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md) and then edit the SharePoint file as if it were a local file. When your site design is ready, upload the HTML and supporting files and use Design Manager to [convert the HTML file into an ASP.NET master page (.master.md) file](how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md). Now,  [apply the master page](how-to-apply-a-master-page-to-a-site-in-sharepoint.md) to your SharePoint site. Use Design Manager to [create a new page layout](how-to-create-a-page-layout-in-sharepoint.md), and the HTML version of it is automatically associated with the corresponding ASP.NET page (.aspx file.md) that SharePoint interprets. 
   
     
     
@@ -93,7 +94,7 @@ Design Manager generates HTML snippets that can be used by any web design tool
 
 ### Device channels
 
-In Design Manager, you create  [device channels](sharepoint-design-manager-device-channels), and then you map them to mobile devices or browsers by using substrings of each incoming device's user agent string. A device can belong to multiple channels, so channels can be ranked. For example, if you create device channels for "smart phones" and "Windows Phone 8", you can rank the channels so that devices running Windows Phone 8 get the channel specifically assigned to them, while all other smart phones get content associated with the "smart phones" channel.
+In Design Manager, you create  [device channels](sharepoint-design-manager-device-channels.md), and then you map them to mobile devices or browsers by using substrings of each incoming device's user agent string. A device can belong to multiple channels, so channels can be ranked. For example, if you create device channels for "smart phones" and "Windows Phone 8", you can rank the channels so that devices running Windows Phone 8 get the channel specifically assigned to them, while all other smart phones get content associated with the "smart phones" channel.
   
     
     
@@ -128,7 +129,7 @@ There are three contexts when you may want to use display templates with search
   
     
     
-To learn more about display templates, see  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates).
+To learn more about display templates, see  [SharePoint Design Manager display templates](sharepoint-design-manager-display-templates.md).
   
     
     
@@ -136,7 +137,7 @@ To learn more about display templates, see  [SharePoint Design Manager display t
 ### Image renditions
 <a name="SP15_BuildSitesForSP2013_DisplayTemplates"> </a>
 
-You can use  [image renditions](sharepoint-design-manager-image-renditions) to display uploaded images in predefined sizes, widths, and crops. You can create more than one rendition of a source image file, which means that you can set the display characteristics once and apply them to any number of images. For example, a rendition named **Article_image** displays a full-sized image in an article, while the rendition named **Thumbnail_small** displays a smaller version of the image in a context that you define.
+You can use  [image renditions](sharepoint-design-manager-image-renditions.md) to display uploaded images in predefined sizes, widths, and crops. You can create more than one rendition of a source image file, which means that you can set the display characteristics once and apply them to any number of images. For example, a rendition named **Article_image** displays a full-sized image in an article, while the rendition named **Thumbnail_small** displays a smaller version of the image in a context that you define.
   
     
     
@@ -155,7 +156,7 @@ Enterprise managed metadata (EMM) capabilities introduced in are improved and ex
 
 ### Managed navigation
 
-Managed navigation is the taxonomy-based alternative to the traditional SharePoint navigation feature—called structured navigation—that is based on the structure of SharePoint. The  [managed navigation](managed-navigation-in-sharepoint) feature enables you to design a site navigation that is driven by managed metadata. Managed navigation creates SEO-friendly URLs that are derived from the managed navigation structure. Because managed navigation is driven by taxonomy, you can use it to design site navigation around important business concepts without changing the structure of your sites or site components.
+Managed navigation is the taxonomy-based alternative to the traditional SharePoint navigation feature—called structured navigation—that is based on the structure of SharePoint. The  [managed navigation](managed-navigation-in-sharepoint.md) feature enables you to design a site navigation that is driven by managed metadata. Managed navigation creates SEO-friendly URLs that are derived from the managed navigation structure. Because managed navigation is driven by taxonomy, you can use it to design site navigation around important business concepts without changing the structure of your sites or site components.
   
     
     
@@ -163,7 +164,7 @@ Managed navigation is the taxonomy-based alternative to the traditional SharePoi
 ### Content Search Web Part
 <a name="SP15_BuildSitesForSP2013_ContentSearchWebPart"> </a>
 
-You can use the  [Content Search Web Part (CSWP)](content-search-web-part-in-sharepoint) to display search data on your pages. It serves a function similar to that of the Content Query Web Part, but it serves different site design goals. CSWP styles are easier to customize than Content Query Web Part styles. CSWP returns client-side results in JSON format. On the server, you can customize results by using display templates.
+You can use the  [Content Search Web Part (CSWP)](content-search-web-part-in-sharepoint.md) to display search data on your pages. It serves a function similar to that of the Content Query Web Part, but it serves different site design goals. CSWP styles are easier to customize than Content Query Web Part styles. CSWP returns client-side results in JSON format. On the server, you can customize results by using display templates.
   
     
     
@@ -171,7 +172,7 @@ You can use the  [Content Search Web Part (CSWP)](content-search-web-part-in-sha
 ### Other managed metadata improvements for sites
 <a name="SP15_BuildSitesForSP2013_ContentSearchWebPart"> </a>
 
-SharePoint introduces several improvements to the managed metadata UI and functionality. To learn more, see  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint).
+SharePoint introduces several improvements to the managed metadata UI and functionality. To learn more, see  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint.md).
   
     
     
@@ -190,7 +191,7 @@ If you're a professional web designer, you may want to create and test a design
   
     
     
-In previous versions of SharePoint, if you wanted to reuse a design, you had to use Visual Studio to create a SharePoint Solution Package (.wsp file). Then, in the destination site, you would upload the package to the Solutions Gallery and execute it. Now, in SharePoint, after you finish designing your site, you can choose **Export Package** in Design Manager to export a single .wsp file called a [design package](sharepoint-design-manager-design-packages). When you export a design package, SharePoint automatically packages all of the contents that you have added or changed in the Master Page Gallery, Style Library, Theme Gallery, the Device Channels list, and Page content types into a design package. 
+In previous versions of SharePoint, if you wanted to reuse a design, you had to use Visual Studio to create a SharePoint Solution Package (.wsp file). Then, in the destination site, you would upload the package to the Solutions Gallery and execute it. Now, in SharePoint, after you finish designing your site, you can choose **Export Package** in Design Manager to export a single .wsp file called a [design package](sharepoint-design-manager-design-packages.md). When you export a design package, SharePoint automatically packages all of the contents that you have added or changed in the Master Page Gallery, Style Library, Theme Gallery, the Device Channels list, and Page content types into a design package. 
   
     
     
@@ -212,7 +213,7 @@ When you import a design package, the design assets in the package overwrite any
 
 ### Catalogs
 
-SharePoint site publishing introduces catalogs, which enable you to incorporate lists into your publishing sites. Catalogs enable content to be published across site collections—the cross-site publishing features depend on catalogs. You can use catalogs to truly reuse content across your sites and across the boundary between your intranet sites, Internet sites, and extranet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part (CSWP)](content-search-web-part-in-sharepoint). You can write custom code to populate catalogs, connect a product catalog to a site, and curate individual pages with custom page layouts, Web Parts, and HTML content that appears only in the defined context.
+SharePoint site publishing introduces catalogs, which enable you to incorporate lists into your publishing sites. Catalogs enable content to be published across site collections—the cross-site publishing features depend on catalogs. You can use catalogs to truly reuse content across your sites and across the boundary between your intranet sites, Internet sites, and extranet sites. For predefined search queries, catalogs are flagged in search. You can surface content stored in catalogs across site collections by using the  [Content Search Web Part (CSWP)](content-search-web-part-in-sharepoint.md). You can write custom code to populate catalogs, connect a product catalog to a site, and curate individual pages with custom page layouts, Web Parts, and HTML content that appears only in the defined context.
   
     
     
@@ -234,7 +235,7 @@ Use the topic pages feature to customize the landing page experience for content
   
     
     
-To learn more about cross-site publishing, see  [Scenario: Create SharePoint sites by using cross-site publishing in SharePoint](http://technet.microsoft.com/en-us/sharepoint/jj872721). To learn more about development options for cross-site publishing, see  [Cross-site publishing in SharePoint](cross-site-publishing-in-sharepoint).
+To learn more about cross-site publishing, see  [Scenario: Create SharePoint sites by using cross-site publishing in SharePoint](http://technet.microsoft.com/en-us/sharepoint/jj872721). To learn more about development options for cross-site publishing, see  [Cross-site publishing in SharePoint](cross-site-publishing-in-sharepoint.md).
   
     
     
@@ -267,7 +268,7 @@ Analytics makes data anonymous and rolls it up every 15 days. Analytics purges e
 
 ### Variations and multilingual sites
 
-You can use the variations feature in SharePoint to create multilingual sites or other sites where you want to vary the presentation of your content. The variations feature is constrained to one site collection. That is, you can create target language/locale "variants" of a source language/locale as current websites within the same SharePoint site collection. Variations supports friendly URLs and the ability to export or import content for translation by a third party in  [XLIFF file format](the-xliff-interchange-file-format-in-sharepoint). You can include labels, a page for translation and replication, a variety of list items (for example, document libraries), and navigation in your export packages. 
+You can use the variations feature in SharePoint to create multilingual sites or other sites where you want to vary the presentation of your content. The variations feature is constrained to one site collection. That is, you can create target language/locale "variants" of a source language/locale as current websites within the same SharePoint site collection. Variations supports friendly URLs and the ability to export or import content for translation by a third party in  [XLIFF file format](the-xliff-interchange-file-format-in-sharepoint.md). You can include labels, a page for translation and replication, a variety of list items (for example, document libraries.md), and navigation in your export packages. 
   
     
     
@@ -282,22 +283,22 @@ You can use the variations feature in SharePoint to create multilingual sites or
 -  [Complete basic operations using JavaScript library code in SharePoint](http://msdn.microsoft.com/library/29089af8-dbc0-49b7-a1a0-9e311f49c826%28Office.15%29.aspx)
     
   
--  [How to: Customize page layouts for a catalog-based site in SharePoint](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint)
+-  [How to: Customize page layouts for a catalog-based site in SharePoint](how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md)
     
   
--  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager)
+-  [How to: Change the preview page in SharePoint Design Manager](how-to-change-the-preview-page-in-sharepoint-design-manager.md)
     
   
--  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint)
+-  [How to: Resolve errors and warnings when previewing a page in SharePoint](how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md)
     
   
--  [Themes overview for SharePoint](themes-overview-for-sharepoint)
+-  [Themes overview for SharePoint](themes-overview-for-sharepoint.md)
     
   
--  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint)
+-  [Managed metadata and navigation in SharePoint](managed-metadata-and-navigation-in-sharepoint.md)
     
   
--  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers)
+-  [What's new in SharePoint search for developers](what-s-new-in-sharepoint-search-for-developers.md)
     
   
 
diff --git a/docs/general-development/work-with-social-feeds-in-sharepoint.md b/docs/general-development/work-with-social-feeds-in-sharepoint.md
index b890e89407..765122bd2f 100644
--- a/docs/general-development/work-with-social-feeds-in-sharepoint.md
+++ b/docs/general-development/work-with-social-feeds-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Work with social feeds in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 39f2163e-15cc-43bc-b131-041d5afdcd90
 ---
 
@@ -40,7 +41,7 @@ SharePoint provides the following APIs that you can use to programmatically work
 - Server object model
     
   
-As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, the JavaScript object model, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As a best practice in SharePoint development, use client APIs when you can. Client APIs include the client object models, the JavaScript object model, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -60,9 +61,9 @@ Each API includes a manager object that you use to perform core feed-related tas
 
 |**API**|**Key objects**|
 |:-----|:-----|
-|.NET client object model  <br/> See:  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli)|Manager object:            [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialFeed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeed.aspx) , [SocialThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialThread.aspx) , [SocialPost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPost.aspx) , [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) , [SocialFeedOptions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedOptions.aspx) , [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll|
-|JavaScript object model  <br/> See  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr)|Manager object:            [SocialFeedManager](http://msdn.microsoft.com/library/651fdf0f-841d-88f9-1e07-fcb3ad8c9410%28Office.15%29.aspx) <br/> Primary namespace:            [SP.Social](http://msdn.microsoft.com/library/43d47f01-c085-0e77-bd01-48bcb7d5bb35%28Office.15%29.aspx) <br/> Other key objects:            [SocialFeed](http://msdn.microsoft.com/library/356c5475-2fd6-a655-c271-5d7f21af45e2%28Office.15%29.aspx),  [SocialThread](http://msdn.microsoft.com/library/46aa4beb-d708-f20e-471e-626c8a7efab7%28Office.15%29.aspx),  [SocialPost](http://msdn.microsoft.com/library/a761ce71-d3d7-420a-1e06-962674124dfa%28Office.15%29.aspx),  [SocialPostCreationData](http://msdn.microsoft.com/library/f0e1fa3e-6fc9-48e0-5570-92091abfef33%28Office.15%29.aspx),  [SocialFeedOptions](http://msdn.microsoft.com/library/65caf283-6e7a-50dc-ef8e-a4e12bd237ac%28Office.15%29.aspx),  [SocialActor](http://msdn.microsoft.com/library/4e369fd5-b9b0-9804-957e-b3e39c559cd4%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js|
-|REST service  <br/> See  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)|Manager resource:            [social.feed](social-feed-rest-api-reference-for-sharepoint) (SocialRestFeedManager) <br/> Primary namespace (OData):           **SP.Social** <br/> Other key resources:           SocialFeed,  [SocialRestFeed](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestFeed), SocialThread,  [SocialRestThread](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestThread), SocialPost, SocialPostCreationData,  [SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestPostCreationData),  [SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint#bk_SocialFeedOptions), SocialActor,  [SociaRestActor](social-feed-rest-api-reference-for-sharepoint#bk_SocialRestActor) <br/> Access point:            `<siteUri>/_api/social.feed`|
+|.NET client object model  <br/> See:  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md)|Manager object:            [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.Social](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.aspx) <br/> Other key objects:            [SocialFeed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeed.aspx) , [SocialThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialThread.aspx) , [SocialPost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPost.aspx) , [SocialPostCreationData](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialPostCreationData.aspx) , [SocialFeedOptions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedOptions.aspx) , [SocialActor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialActor.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll|
+|JavaScript object model  <br/> See  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md)|Manager object:            [SocialFeedManager](http://msdn.microsoft.com/library/651fdf0f-841d-88f9-1e07-fcb3ad8c9410%28Office.15%29.aspx) <br/> Primary namespace:            [SP.Social](http://msdn.microsoft.com/library/43d47f01-c085-0e77-bd01-48bcb7d5bb35%28Office.15%29.aspx) <br/> Other key objects:            [SocialFeed](http://msdn.microsoft.com/library/356c5475-2fd6-a655-c271-5d7f21af45e2%28Office.15%29.aspx),  [SocialThread](http://msdn.microsoft.com/library/46aa4beb-d708-f20e-471e-626c8a7efab7%28Office.15%29.aspx),  [SocialPost](http://msdn.microsoft.com/library/a761ce71-d3d7-420a-1e06-962674124dfa%28Office.15%29.aspx),  [SocialPostCreationData](http://msdn.microsoft.com/library/f0e1fa3e-6fc9-48e0-5570-92091abfef33%28Office.15%29.aspx),  [SocialFeedOptions](http://msdn.microsoft.com/library/65caf283-6e7a-50dc-ef8e-a4e12bd237ac%28Office.15%29.aspx),  [SocialActor](http://msdn.microsoft.com/library/4e369fd5-b9b0-9804-957e-b3e39c559cd4%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js|
+|REST service  <br/> See  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)|Manager resource:            [social.feed](social-feed-rest-api-reference-for-sharepoint.md) (SocialRestFeedManager) <br/> Primary namespace (OData):           **SP.Social** <br/> Other key resources:           SocialFeed,  [SocialRestFeed](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestFeed), SocialThread,  [SocialRestThread](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestThread), SocialPost, SocialPostCreationData,  [SocialRestPostCreationData](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestPostCreationData),  [SocialFeedOptions](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialFeedOptions), SocialActor,  [SociaRestActor](social-feed-rest-api-reference-for-sharepoint.md#bk_SocialRestActor) <br/> Access point:            `<siteUri>/_api/social.feed`|
 |Server object model <br/>Note: Code that uses the server object model to access feed data and runs remotely must use an  [SPServiceContextScope](https://msdn.microsoft.com/library/Microsoft.SharePoint.SPServiceContextScope.aspx) object.|Manager object:            [SPSocialFeedManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.aspx) <br/> Primary namespace:            [Microsoft.Office.Server.Social](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.aspx) <br/> Other key objects:            [SPSocialFeed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeed.aspx) , [SPSocialThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialThread.aspx) , [SPSocialPost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialPost.aspx) , [SPSocialFeedOptions](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedOptions.aspx) , [SPSocialActor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialActor.aspx) <br/> Class library:           Microsoft.Office.Server.UserProfiles.dll|
    
 If you're using the server object model to access feed content and your code isn't running in a SharePoint instance (in other words, if your extension is not installed in the LAYOUTS folder on the application server), use an  [SPServiceContextScope](https://msdn.microsoft.com/library/Microsoft.SharePoint.SPServiceContextScope.aspx) object in your code. The following code example shows one way to incorporate the [SPServiceContextScope](https://msdn.microsoft.com/library/Microsoft.SharePoint.SPServiceContextScope.aspx) object into your code.
@@ -98,26 +99,26 @@ Table 2 shows common programming tasks for working with social feeds and the mem
 
 |**Task**|**Members**|
 |:-----|:-----|
-|Create an instance of the manager object in the context of the current user|CSOM:  [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) <br/> JSOM:  [SocialFeedManager](http://msdn.microsoft.com/library/f7cf172f-970b-6b71-9eb4-b9a8bb7a0001%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed`](social-feed-rest-api-reference-for-sharepoint) <br/> SSOM:  [SPSocialFeedManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.aspx)|
+|Create an instance of the manager object in the context of the current user|CSOM:  [SocialFeedManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.aspx) <br/> JSOM:  [SocialFeedManager](http://msdn.microsoft.com/library/f7cf172f-970b-6b71-9eb4-b9a8bb7a0001%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed`](social-feed-rest-api-reference-for-sharepoint.md) <br/> SSOM:  [SPSocialFeedManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.aspx)|
 |Create an instance of the manager object in the context of a particular user|CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM:  [SPSocialFeedManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.aspx)|
-|Get the user for the current context|CSOM:  [Owner](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.Owner.aspx) <br/> JSOM:  [owner](http://msdn.microsoft.com/library/0307264e-d733-77f0-edae-f5468e58d0b7%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my`](social-feed-rest-api-reference-for-sharepoint#bk_my) <br/> SSOM:  [Owner](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.Owner.aspx)|
-|Get the feed for the current user  <br/> (specify the feed type)|CSOM:  [GetFeed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeed.aspx) <br/> JSOM:  [getFeed](http://msdn.microsoft.com/library/cddaccd8-28da-6798-d8cb-4e9351efddf3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/Feed`](social-feed-rest-api-reference-for-sharepoint#bk_myFeed) (personal feed), [`<siteUri>/_api/social.feed/my/News`](social-feed-rest-api-reference-for-sharepoint#bk_myNews),  [`<siteUri>/_api/social.feed/my/TimelineFeed`](social-feed-rest-api-reference-for-sharepoint#bk_myTimelineFeed), or  [`<siteUri>/_api/social.feed/my/Likes`](social-feed-rest-api-reference-for-sharepoint#bk_myLikes) <br/> SSOM:  [GetFeed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeed.aspx)|
-|Get the personal feed for a particular user|CSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeedFor.aspx) <br/> JSOM:  [getFeedFor](http://msdn.microsoft.com/library/074ed255-9393-448d-1f7e-720fdeb05f48%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/actor(item='domain\\user')/Feed`](social-feed-rest-api-reference-for-sharepoint#bk_actorFeed) <br/> SSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeedFor.aspx)|
-|Get the site feed for a team site  <br/> (specify the URL of the site feed as the actor (example: http://<siteCollection>/<teamSite>/newsfeed.aspx))|CSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeedFor.aspx) <br/> JSOM:  [getFeedFor](http://msdn.microsoft.com/library/074ed255-9393-448d-1f7e-720fdeb05f48%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/actor(item=@v)/Feed?@v='http://<siteCollection>/<teamSite>/newsfeed.aspx'`](social-feed-rest-api-reference-for-sharepoint#bk_actorFeed) <br/> SSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeedFor.aspx)|
-|Publish a root post to the current user's feed  <br/> (specify **null** for the target)|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/my/Feed/Post`](social-feed-rest-api-reference-for-sharepoint#bk_myFeedPost) and pass the _restCreationData_ parameter in the request body <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
-|Publish a post to a site feed  <br/> (specify the URL of the site feed as the target (example: http://<siteCollection>/teamSite>/newsfeed.aspx))|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/actor(item=@av)/feed/post/?@av='<teamSiteUri>/newsfeed.aspx'`](social-feed-rest-api-reference-for-sharepoint#bk_actorFeedPost) and pass the _restCreationData_ parameter in the request body (specify **null** for the _ID_ parameter) <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
-|Publish a reply to a post  <br/> (specify the ID of the target thread)|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Reply`](social-feed-rest-api-reference-for-sharepoint#bk_postReply) and pass the _restCreationData_ parameter in the request body <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
-|Delete a post, reply, or thread in the current user's feed (deleting a root post deletes the whole thread)|CSOM:  [DeletePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.DeletePost.aspx) <br/> JSOM:  [deletePost](http://msdn.microsoft.com/library/06e03f87-c97d-8634-a02b-f7812eb7beeb%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Delete`](social-feed-rest-api-reference-for-sharepoint#bk_postDelete) and pass the _ID_ parameter in the request body <br/> SSOM:  [DeletePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.DeletePost.aspx)|
-|Get a thread (a root post and all its replies) from the user's feed|CSOM:  [GetFullThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFullThread.aspx) <br/> JSOM:  [getFullThread](http://msdn.microsoft.com/library/6bb384f3-9474-581f-e18d-e8c4f44c3cdf%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post`](social-feed-rest-api-reference-for-sharepoint#bk_post) and pass the _ID_ parameter in the request body <br/> SSOM:  [GetFullThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFullThread.aspx)|
-|Have the user like (unlike) a post or reply|CSOM:  [LikePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.LikePost.aspx) ( [UnlikePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.UnlikePost.aspx) ) <br/> JSOM:  [likePost](http://msdn.microsoft.com/library/f401a584-1712-50af-ee08-2999a16388d6%28Office.15%29.aspx) ( [unlikePost](http://msdn.microsoft.com/library/c778bd7d-91e5-15dc-eeb8-b571957e8338%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Like`](social-feed-rest-api-reference-for-sharepoint#bk_postLike) ( [`<siteUri>/_api/social.feed/Post/Unlike`](social-feed-rest-api-reference-for-sharepoint#bk_postUnlike)) and pass the  _ID_ parameter in the request body <br/> SSOM:  [LikePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.LikePost.aspx) ( [UnlikePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.UnlikePost.aspx) )|
-|Get all likers for a post|CSOM:  [GetAllLikers](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetAllLikers.aspx) <br/> JSOM:  [getAllLikers](http://msdn.microsoft.com/library/76286fdc-002f-2b13-dc26-53097eb2e3a2%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Likers`](social-feed-rest-api-reference-for-sharepoint#bk_postLikers) and pass the _ID_ parameter in the request body <br/> SSOM:  [GetAllLikers](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetAllLikers.aspx)|
-|Get the posts that mention a user|CSOM:  [GetMentions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetMentions.aspx) <br/> JSOM:  [getMentions](http://msdn.microsoft.com/library/78f064c3-5b96-373e-e7f0-8603aedc5ded%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/MentionFeed`](social-feed-rest-api-reference-for-sharepoint#bk_myMentionFeed) <br/> SSOM:  [GetMentions](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetMentions.aspx)|
-|Get the number of unread mentions for the current user|CSOM:  [GetUnreadMentionCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetUnreadMentionCount.aspx) <br/> JSOM:  [getUnreadMentionCount](http://msdn.microsoft.com/library/18dde16a-f78f-f65e-0644-4eb737b1ae00%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/UnreadMentionCount`](social-feed-rest-api-reference-for-sharepoint#bk_myUnreadMentionCount) <br/> SSOM:  [GetUnreadMentionCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetUnreadMentionCount.aspx)|
-|Lock (unlock) a thread in the current user's feed|CSOM:  [LockThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.LockThread.aspx) ( [UnlockThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.UnlockThread.aspx) ) <br/> JSOM:  [lockThread](http://msdn.microsoft.com/library/cc696bb7-e7fd-7a57-5db5-736c3733589e%28Office.15%29.aspx) ( [unlockThread](http://msdn.microsoft.com/library/ee9288d6-ace0-1ec2-ea7c-0ee300b6e1ea%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Lock`](social-feed-rest-api-reference-for-sharepoint#bk_postLock) ( [`<siteUri>/_api/social.feed/Post/Unlock`](social-feed-rest-api-reference-for-sharepoint#bk_postUnlock)) and pass the  _ID_ parameter in the request body <br/> SSOM:  [LockThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.LockThread.aspx) ( [UnlockThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.UnlockThread.aspx) )|
+|Get the user for the current context|CSOM:  [Owner](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.Owner.aspx) <br/> JSOM:  [owner](http://msdn.microsoft.com/library/0307264e-d733-77f0-edae-f5468e58d0b7%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my`](social-feed-rest-api-reference-for-sharepoint.md#bk_my) <br/> SSOM:  [Owner](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.Owner.aspx)|
+|Get the feed for the current user  <br/> (specify the feed type)|CSOM:  [GetFeed](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeed.aspx) <br/> JSOM:  [getFeed](http://msdn.microsoft.com/library/cddaccd8-28da-6798-d8cb-4e9351efddf3%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/Feed`](social-feed-rest-api-reference-for-sharepoint.md#bk_myFeed) (personal feed.md), [`<siteUri>/_api/social.feed/my/News`](social-feed-rest-api-reference-for-sharepoint.md#bk_myNews),  [`<siteUri>/_api/social.feed/my/TimelineFeed`](social-feed-rest-api-reference-for-sharepoint.md#bk_myTimelineFeed), or  [`<siteUri>/_api/social.feed/my/Likes`](social-feed-rest-api-reference-for-sharepoint.md#bk_myLikes) <br/> SSOM:  [GetFeed](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeed.aspx)|
+|Get the personal feed for a particular user|CSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeedFor.aspx) <br/> JSOM:  [getFeedFor](http://msdn.microsoft.com/library/074ed255-9393-448d-1f7e-720fdeb05f48%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/actor(item='domain\\user')/Feed`](social-feed-rest-api-reference-for-sharepoint.md#bk_actorFeed) <br/> SSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeedFor.aspx)|
+|Get the site feed for a team site  <br/> (specify the URL of the site feed as the actor (example: http://<siteCollection>/<teamSite>/newsfeed.aspx))|CSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFeedFor.aspx) <br/> JSOM:  [getFeedFor](http://msdn.microsoft.com/library/074ed255-9393-448d-1f7e-720fdeb05f48%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/actor(item=@v)/Feed?@v='http://<siteCollection>/<teamSite>/newsfeed.aspx'`](social-feed-rest-api-reference-for-sharepoint.md#bk_actorFeed) <br/> SSOM:  [GetFeedFor](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFeedFor.aspx)|
+|Publish a root post to the current user's feed  <br/> (specify **null** for the target)|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/my/Feed/Post`](social-feed-rest-api-reference-for-sharepoint.md#bk_myFeedPost) and pass the _restCreationData_ parameter in the request body <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
+|Publish a post to a site feed  <br/> (specify the URL of the site feed as the target (example: http://<siteCollection>/teamSite>/newsfeed.aspx))|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/actor(item=@av)/feed/post/?@av='<teamSiteUri>/newsfeed.aspx'`](social-feed-rest-api-reference-for-sharepoint.md#bk_actorFeedPost) and pass the _restCreationData_ parameter in the request body (specify **null** for the _ID_ parameter) <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
+|Publish a reply to a post  <br/> (specify the ID of the target thread)|CSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.CreatePost.aspx) <br/> JSOM:  [createPost](http://msdn.microsoft.com/library/e9ad06a1-831d-8ed0-c76e-8b049f14216f%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Reply`](social-feed-rest-api-reference-for-sharepoint.md#bk_postReply) and pass the _restCreationData_ parameter in the request body <br/> SSOM:  [CreatePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.CreatePost.aspx)|
+|Delete a post, reply, or thread in the current user's feed (deleting a root post deletes the whole thread)|CSOM:  [DeletePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.DeletePost.aspx) <br/> JSOM:  [deletePost](http://msdn.microsoft.com/library/06e03f87-c97d-8634-a02b-f7812eb7beeb%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Delete`](social-feed-rest-api-reference-for-sharepoint.md#bk_postDelete) and pass the _ID_ parameter in the request body <br/> SSOM:  [DeletePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.DeletePost.aspx)|
+|Get a thread (a root post and all its replies) from the user's feed|CSOM:  [GetFullThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetFullThread.aspx) <br/> JSOM:  [getFullThread](http://msdn.microsoft.com/library/6bb384f3-9474-581f-e18d-e8c4f44c3cdf%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post`](social-feed-rest-api-reference-for-sharepoint.md#bk_post) and pass the _ID_ parameter in the request body <br/> SSOM:  [GetFullThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetFullThread.aspx)|
+|Have the user like (unlike) a post or reply|CSOM:  [LikePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.LikePost.aspx) ( [UnlikePost](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.UnlikePost.aspx) ) <br/> JSOM:  [likePost](http://msdn.microsoft.com/library/f401a584-1712-50af-ee08-2999a16388d6%28Office.15%29.aspx) ( [unlikePost](http://msdn.microsoft.com/library/c778bd7d-91e5-15dc-eeb8-b571957e8338%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Like`](social-feed-rest-api-reference-for-sharepoint.md#bk_postLike) ( [`<siteUri>/_api/social.feed/Post/Unlike`](social-feed-rest-api-reference-for-sharepoint.md#bk_postUnlike)) and pass the  _ID_ parameter in the request body <br/> SSOM:  [LikePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.LikePost.aspx) ( [UnlikePost](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.UnlikePost.aspx) )|
+|Get all likers for a post|CSOM:  [GetAllLikers](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetAllLikers.aspx) <br/> JSOM:  [getAllLikers](http://msdn.microsoft.com/library/76286fdc-002f-2b13-dc26-53097eb2e3a2%28Office.15%29.aspx) <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Likers`](social-feed-rest-api-reference-for-sharepoint.md#bk_postLikers) and pass the _ID_ parameter in the request body <br/> SSOM:  [GetAllLikers](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetAllLikers.aspx)|
+|Get the posts that mention a user|CSOM:  [GetMentions](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetMentions.aspx) <br/> JSOM:  [getMentions](http://msdn.microsoft.com/library/78f064c3-5b96-373e-e7f0-8603aedc5ded%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/MentionFeed`](social-feed-rest-api-reference-for-sharepoint.md#bk_myMentionFeed) <br/> SSOM:  [GetMentions](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetMentions.aspx)|
+|Get the number of unread mentions for the current user|CSOM:  [GetUnreadMentionCount](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.GetUnreadMentionCount.aspx) <br/> JSOM:  [getUnreadMentionCount](http://msdn.microsoft.com/library/18dde16a-f78f-f65e-0644-4eb737b1ae00%28Office.15%29.aspx) <br/> REST: **GET** [`<siteUri>/_api/social.feed/my/UnreadMentionCount`](social-feed-rest-api-reference-for-sharepoint.md#bk_myUnreadMentionCount) <br/> SSOM:  [GetUnreadMentionCount](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.GetUnreadMentionCount.aspx)|
+|Lock (unlock) a thread in the current user's feed|CSOM:  [LockThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.LockThread.aspx) ( [UnlockThread](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.Social.SocialFeedManager.UnlockThread.aspx) ) <br/> JSOM:  [lockThread](http://msdn.microsoft.com/library/cc696bb7-e7fd-7a57-5db5-736c3733589e%28Office.15%29.aspx) ( [unlockThread](http://msdn.microsoft.com/library/ee9288d6-ace0-1ec2-ea7c-0ee300b6e1ea%28Office.15%29.aspx))  <br/> REST: **POST** [`<siteUri>/_api/social.feed/Post/Lock`](social-feed-rest-api-reference-for-sharepoint.md#bk_postLock) ( [`<siteUri>/_api/social.feed/Post/Unlock`](social-feed-rest-api-reference-for-sharepoint.md#bk_postUnlock)) and pass the  _ID_ parameter in the request body <br/> SSOM:  [LockThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.LockThread.aspx) ( [UnlockThread](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.SPSocialFeedManager.UnlockThread.aspx) .md)|
    
 
 > **Note:**
-> The  _domain\\user_ placeholder value in the REST example should be replaced with the account name of an actual user. To see how to pass a REST parameter in a request body, see the [examples](social-feed-rest-api-reference-for-sharepoint#bk_exampleRequests) in the Social feed REST API reference.
+> The  _domain\\user_ placeholder value in the REST example should be replaced with the account name of an actual user. To see how to pass a REST parameter in a request body, see the [examples](social-feed-rest-api-reference-for-sharepoint.md#bk_exampleRequests) in the Social feed REST API reference.
   
     
     
@@ -173,28 +174,28 @@ If a thread contains more than two replies, the server returns a digest of the t
 - **Conceptual and how-to articles**
     
   
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli)
+-  [How to: Create and delete posts and retrieve the social feed by using the .NET client object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md)
     
   
--  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr)
+-  [How to: Create and delete posts and retrieve the social feed by using the JavaScript object model in SharePoint](how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md)
     
   
--  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s)
+-  [How to: Learn to read and write to the social feed by using the REST service in SharePoint](how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md)
     
   
--  [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep)
+-  [How to: Include mentions, tags, and links to sites and documents in posts in SharePoint](how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md)
     
   
--  [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server)
+-  [How to: Embed images, videos, and documents in posts in SharePoint](how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md)
     
   
--  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds)
+-  [Reference threads and digest threads in SharePoint social feeds](reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md)
     
   
 - **API reference documentation**
@@ -206,7 +207,7 @@ If a thread contains more than two replies, the server returns a digest of the t
 -  [SP.Social namespace](http://msdn.microsoft.com/library/43d47f01-c085-0e77-bd01-48bcb7d5bb35%28Office.15%29.aspx) (JavaScript object model)
     
   
--  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint)
+-  [Social feed REST API reference for SharePoint](social-feed-rest-api-reference-for-sharepoint.md)
     
   
 -  [Microsoft.Office.Server.Social](https://msdn.microsoft.com/library/Microsoft.Office.Server.Social.aspx) (server object model)
diff --git a/docs/general-development/work-with-user-profiles-in-sharepoint.md b/docs/general-development/work-with-user-profiles-in-sharepoint.md
index 0e32cd96f0..db92d923d3 100644
--- a/docs/general-development/work-with-user-profiles-in-sharepoint.md
+++ b/docs/general-development/work-with-user-profiles-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Work with user profiles in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7437a7a8-85cb-4233-84af-1eec30dd54b2
 ---
 
@@ -36,7 +37,7 @@ User profiles and user profile properties provide information about SharePoint u
 - Server object model
     
   
-As a best practice in SharePoint development, use client APIs when you can. Client APIs include the .NET client object model, the JavaScript object model, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint).
+As a best practice in SharePoint development, use client APIs when you can. Client APIs include the .NET client object model, the JavaScript object model, and the REST service. For more information about the APIs in SharePoint and when to use them, see  [Choose the right API set in SharePoint](choose-the-right-api-set-in-sharepoint.md).
   
     
     
@@ -63,10 +64,10 @@ Each API includes a manager object that you use to perform core profile-related
 
 |**API**|**Key object**|
 |:-----|:-----|
-|.NET client object model  <br/> See:  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in)|Manager object:            [PeopleManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PeopleManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.UserProfiles](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.aspx) <br/> Other key objects:            [PersonProperties](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PersonProperties.aspx) , [ProfileLoader](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.ProfileLoader.aspx) , [UserProfile](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.UserProfile.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll |
-|JavaScript object model  <br/> See:  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in)|Manager object:            [PeopleManager](http://msdn.microsoft.com/library/985fd2df-0e31-6ece-b846-ba2ccb156d00%28Office.15%29.aspx) <br/> Primary namespace:            [SP.UserProfiles](http://msdn.microsoft.com/library/8c1fcceb-cd9a-b25c-32f4-1cfb0578278c%28Office.15%29.aspx) <br/> Other key objects:            [PersonProperties](http://msdn.microsoft.com/library/0274d97f-b697-f436-2aaf-f5bcf9b70df8%28Office.15%29.aspx),  [ProfileLoader](http://msdn.microsoft.com/library/c8dd9919-66a9-fffc-1100-14472d2ec2cb%28Office.15%29.aspx),  [UserProfile](http://msdn.microsoft.com/library/f8c4a219-fbaa-2e50-1bd5-fdc80051b33d%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js |
+|.NET client object model  <br/> See:  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md)|Manager object:            [PeopleManager](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PeopleManager.aspx) <br/> Primary namespace:            [Microsoft.SharePoint.Client.UserProfiles](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.aspx) <br/> Other key objects:            [PersonProperties](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PersonProperties.aspx) , [ProfileLoader](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.ProfileLoader.aspx) , [UserProfile](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.UserProfile.aspx) <br/> Class library:           Microsoft.SharePoint.Client.UserProfiles.dll |
+|JavaScript object model  <br/> See:  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md)|Manager object:            [PeopleManager](http://msdn.microsoft.com/library/985fd2df-0e31-6ece-b846-ba2ccb156d00%28Office.15%29.aspx) <br/> Primary namespace:            [SP.UserProfiles](http://msdn.microsoft.com/library/8c1fcceb-cd9a-b25c-32f4-1cfb0578278c%28Office.15%29.aspx) <br/> Other key objects:            [PersonProperties](http://msdn.microsoft.com/library/0274d97f-b697-f436-2aaf-f5bcf9b70df8%28Office.15%29.aspx),  [ProfileLoader](http://msdn.microsoft.com/library/c8dd9919-66a9-fffc-1100-14472d2ec2cb%28Office.15%29.aspx),  [UserProfile](http://msdn.microsoft.com/library/f8c4a219-fbaa-2e50-1bd5-fdc80051b33d%28Office.15%29.aspx) <br/> Class library:           SP.UserProfiles.js |
 |REST service  <br/> See:  [User profiles REST API reference](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx)|Manager resource:            [PeopleManager](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PeopleManager) <br/> Endpoint URI:            `http://<siteUri>/_api/SP.UserProfiles.PeopleManager` <br/> Primary namespace:           **SP.UserProfiles** <br/> Other key resources:            [PersonProperties](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PersonProperties),  [ProfileLoader](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_ProfileLoader),  [UserProfile](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_UserProfile)|
-|Server object model  <br/> See:  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)|Manager objects:            [UserProfileManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.aspx) , [PeopleManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.PeopleManager.aspx) <br/> Primary namespace:            [Microsoft.Office.Server.UserProfiles](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.aspx) <br/> Other key objects:            [UserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfile.aspx) , [CorePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.CorePropertyManager.aspx) , [ProfilePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfilePropertyManager.aspx) , [ProfileSubtypeManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileSubtypeManager.aspx) , [ProfileSubtypePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileSubtypePropertyManager.aspx) , [ProfileTypePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileTypePropertyManager.aspx) <br/> Class library:           Microsoft.Office.Server.UserProfiles.dll |
+|Server object model  <br/> See:  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)|Manager objects:            [UserProfileManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.aspx) , [PeopleManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.PeopleManager.aspx) <br/> Primary namespace:            [Microsoft.Office.Server.UserProfiles](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.aspx) <br/> Other key objects:            [UserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfile.aspx) , [CorePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.CorePropertyManager.aspx) , [ProfilePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfilePropertyManager.aspx) , [ProfileSubtypeManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileSubtypeManager.aspx) , [ProfileSubtypePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileSubtypePropertyManager.aspx) , [ProfileTypePropertyManager](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.ProfileTypePropertyManager.aspx) <br/> Class library:           Microsoft.Office.Server.UserProfiles.dll |
    
 
 ## Common programming tasks for working with user profiles in SharePoint
@@ -88,12 +89,12 @@ Table 2 shows common programming tasks for working with user profiles and the me
 |Get a particular user's properties |CSOM:  [GetPropertiesFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PeopleManager.GetPropertiesFor.aspx) <br/> JSOM:  [getPropertiesFor](http://msdn.microsoft.com/library/097464db-2630-4c7a-fd0c-0f333680b5a4%28Office.15%29.aspx) <br/> REST: **GET** [`http://<siteUri>/_api/SP.UserProfiles.PeopleManager/GetPropertiesFor(accountName=@v)?@v='domain\\user'`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PeopleManagerGetPropertiesFor) <br/> SSOM:  [GetUserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile.aspx) (overloaded) or [GetPropertiesFor](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.PeopleManager.GetPropertiesFor.aspx)|
 |Get the user profile properties for a particular user |CSOM:  [GetUserProfilePropertiesFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PeopleManager.GetUserProfilePropertiesFor.aspx) <br/> JSOM:  [getUserProfilePropertiesFor](http://msdn.microsoft.com/library/8674e96f-d320-4a50-1580-9a4568842ee5%28Office.15%29.aspx) <br/> REST: not implemented. Call [GetPropertiesFor](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PeopleManagerGetPropertiesFor) and then get the user profile properties from the **UserProfileProperties** property of the returned **PersonProperties** object. <br/> SSOM:  [GetEnumerator](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfile.GetEnumerator.aspx)|
 |Get a specific user profile property for a user |CSOM:  [GetUserProfilePropertyFor](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.PeopleManager.GetUserProfilePropertyFor.aspx) <br/> JSOM:  [getUserProfilePropertyFor](http://msdn.microsoft.com/library/da048bfa-54c6-8216-e8ef-09bd84f68d8d%28Office.15%29.aspx) <br/> REST: **GET** [`http://<siteUri>/_api/SP.UserProfiles.PeopleManager/GetUserProfilePropertyFor(accountName=@v,propertyName='PreferredName')?@v='domain\\user'`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_PeopleManagerGetUserProfilePropertyFor) <br/> SSOM:  [UserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfile.aspx) (overloaded) and specify the property name in the indexer|
-|Get a user profile |CSOM:  [GetUserProfile](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.ProfileLoader.GetUserProfile.aspx) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint#bkmk_NewUserObjects) for the current user only) <br/> JSOM:  [getUserProfile](http://msdn.microsoft.com/library/8e30e811-5da1-b6d0-a8b5-befea9b22496%28Office.15%29.aspx) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint#bkmk_NewUserObjects) for the current user only) <br/> REST: **POST** [`http://<siteUri>/_api/SP.UserProfiles.ProfileLoader.GetProfileLoader/GetUserProfile`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_ProfileLoaderGetProfileLoader) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint#bkmk_NewUserObjects) for the current user only) <br/> SSOM:  [GetUserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile.aspx) (overloaded)|
+|Get a user profile |CSOM:  [GetUserProfile](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.ProfileLoader.GetUserProfile.aspx) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint.md#bkmk_NewUserObjects) for the current user only) <br/> JSOM:  [getUserProfile](http://msdn.microsoft.com/library/8e30e811-5da1-b6d0-a8b5-befea9b22496%28Office.15%29.aspx) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint.md#bkmk_NewUserObjects) for the current user only) <br/> REST: **POST** [`http://<siteUri>/_api/SP.UserProfiles.ProfileLoader.GetProfileLoader/GetUserProfile`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx.md#bk_ProfileLoaderGetProfileLoader) (returns the [client-side user profile](work-with-user-profiles-in-sharepoint.md#bkmk_NewUserObjects) for the current user only) <br/> SSOM:  [GetUserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile.aspx) (overloaded)|
 |Find out whether a user account exists |CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM:  [UserExists](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.UserExists.aspx)|
-|Create or change user profiles and user profile properties and attributes  <br/> (Client APIs can change the profile picture. See the "Change the user's profile picture" task in this table.) |CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM: multiple???see  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)|
+|Create or change user profiles and user profile properties and attributes  <br/> (Client APIs can change the profile picture. See the "Change the user's profile picture" task in this table.) |CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM: multiple???see  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)|
 |Delete a user profile |CSOM: not implemented  <br/> JSOM: not implemented  <br/> REST: not implemented  <br/> SSOM:  [RemoveProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.RemoveProfile.aspx) or [RemoveUserProfile](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfileManager.RemoveUserProfile.aspx) (overloaded)|
 |Provision a user's personal site |CSOM:  [CreatePersonalSiteEnque](https://msdn.microsoft.com/library/Microsoft.SharePoint.Client.UserProfiles.UserProfile.CreatePersonalSiteEnque.aspx) (overloaded) <br/> JSOM:  [createPersonalSiteEnque](http://msdn.microsoft.com/library/f4bcb82d-4048-0b29-9bc6-ce70ead49988%28Office.15%29.aspx) (overloaded) <br/> REST: **POST** [`http://<siteUri>/_api/SP.UserProfiles.ProfileLoader.GetProfileLoader/GetUserProfile/CreatePersonalSiteEnqueue`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_UserProfileCreatePersonalSiteEnque) <br/> SSOM:  [CreatePersonalSite()](https://msdn.microsoft.com/library/Microsoft.Office.Server.UserProfiles.UserProfile.CreatePersonalSite.aspx) (overloaded)|
-|Provision one or more users' personal sites  <br/> Available for My Site Host administrators on SharePoint Online only |CSOM:  [CreatePersonalSiteEnqueueBulk](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201#bk_CreatePersonalSiteEnqueueBulk) <br/> JSOM: **createPersonalSiteEnqueueBulk** <br/> REST: **POST** [`https://<domain>-admin.sharepoint.com/_api/SP.UserProfiles.ProfileLoader.GetProfileLoader/CreatePersonalSiteEnqueueBulk`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx#bk_ProfileLoaderCreatePersonalSiteEnqueueBulk) and pass a string array of email addresses for the _emailIDs_ parameter (200 characters maximum) in the request body (example: `{'emailIDs':['usera@contoso.onmicrosoft.com','userb@contoso.onmicrosoft.com']}`).  <br/> SSOM: **CreatePersonalSiteEnqueueBulk**|
+|Provision one or more users' personal sites  <br/> Available for My Site Host administrators on SharePoint Online only |CSOM:  [CreatePersonalSiteEnqueueBulk](what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md#bk_CreatePersonalSiteEnqueueBulk) <br/> JSOM: **createPersonalSiteEnqueueBulk** <br/> REST: **POST** [`https://<domain>-admin.sharepoint.com/_api/SP.UserProfiles.ProfileLoader.GetProfileLoader/CreatePersonalSiteEnqueueBulk`](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx.md#bk_ProfileLoaderCreatePersonalSiteEnqueueBulk) and pass a string array of email addresses for the _emailIDs_ parameter (200 characters maximum) in the request body (example: `{'emailIDs':['usera@contoso.onmicrosoft.com','userb@contoso.onmicrosoft.com']}`).  <br/> SSOM: **CreatePersonalSiteEnqueueBulk**|
    
 
 ## New objects for users and user properties in SharePoint
@@ -125,24 +126,24 @@ SharePoint includes the following new objects that represent users and user prop
 <a name="bkmk_AdditionalResources"> </a>
 
 
--  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint)
+-  [Social and collaboration features in SharePoint](social-and-collaboration-features-in-sharepoint.md)
     
   
--  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint)
+-  [Get started developing with social features in SharePoint](get-started-developing-with-social-features-in-sharepoint.md)
     
   
--  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in)
+-  [How to: Retrieve user profile properties by using the .NET client object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md)
     
   
--  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in)
+-  [How to: Retrieve user profile properties by using the JavaScript object model in SharePoint](how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md)
     
   
 -  [User profiles REST API reference](http://msdn.microsoft.com/library/10757ed1-6e86-474f-89e0-6dec6aa66a2b%28Office.15%29.aspx)
     
   
--  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj)
+-  [How to: Work with user profiles and organization profiles by using the server object model in SharePoint](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md)
     
   
--  [Follow people in SharePoint](follow-people-in-sharepoint)
+-  [Follow people in SharePoint](follow-people-in-sharepoint.md)
     
   
diff --git a/docs/general-development/workflow-actions-and-activities-reference-for-sharepoint.md b/docs/general-development/workflow-actions-and-activities-reference-for-sharepoint.md
index e0b4d1d522..5dbef64292 100644
--- a/docs/general-development/workflow-actions-and-activities-reference-for-sharepoint.md
+++ b/docs/general-development/workflow-actions-and-activities-reference-for-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow actions and activities reference for SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 88e09f75-480f-4a68-87a6-b496350345cc
 ---
 
@@ -14,7 +15,7 @@ Workflow activities represent the code-level objects that handle method calls to
   
     
     
-For a list of available activities, see  [Workflow activity classes in SharePoint](workflow-activity-classes-in-sharepoint).
+For a list of available activities, see  [Workflow activity classes in SharePoint](workflow-activity-classes-in-sharepoint.md).
   
     
     
@@ -22,7 +23,7 @@ On the other hand, workflow actions are wrapper objects that encapsulate these u
   
     
     
-For a list of available workflow actions, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform) and [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge).
+For a list of available workflow actions, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md) and [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge.md).
   
     
     
@@ -43,13 +44,13 @@ The WF 4.0 activity classes provide some useful features that you may not find i
 <a name="bkm_inthissection"> </a>
 
 
--  [Workflow activity classes in SharePoint](workflow-activity-classes-in-sharepoint)
+-  [Workflow activity classes in SharePoint](workflow-activity-classes-in-sharepoint.md)
     
   
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
--  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge)
+-  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge.md)
     
   
 
@@ -57,13 +58,13 @@ The WF 4.0 activity classes provide some useful features that you may not find i
 <a name="bkm_addlres"> </a>
 
 
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
 
diff --git a/docs/general-development/workflow-actions-available-using-the-workflow-interop-bridge.md b/docs/general-development/workflow-actions-available-using-the-workflow-interop-bridge.md
index 011ad07f91..3e118aec40 100644
--- a/docs/general-development/workflow-actions-available-using-the-workflow-interop-bridge.md
+++ b/docs/general-development/workflow-actions-available-using-the-workflow-interop-bridge.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow actions available using the workflow interop bridge
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: a8903440-ff8f-41a4-8c2a-5dbe12c07cfb
 ---
 
@@ -10,7 +11,7 @@ Contains a concise list of workflow actions in SharePoint 2010 that are availabl
 ## Workflow actions for the interop bridge
 <a name="bkm_wfactions"> </a>
 
-The SharePoint workflow infrastructure is built on Windows Workflow Foundation (WF) 4 and therefore executes workflows in Microsoft Azure. For this reason, some actions from SharePoint 2010 workflows are available in SharePoint only when using the  [SharePoint workflow interop ](sharepoint-workflow-fundamentals#bkm_InteropBridge). 
+The SharePoint workflow infrastructure is built on Windows Workflow Foundation (WF) 4 and therefore executes workflows in Microsoft Azure. For this reason, some actions from SharePoint 2010 workflows are available in SharePoint only when using the  [SharePoint workflow interop ](sharepoint-workflow-fundamentals.md#bkm_InteropBridge). 
   
     
     
@@ -110,16 +111,16 @@ The following actions are available only when you use the workflow interop bridg
 <a name="bkm_addlresources"> </a>
 
 
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
--  [SharePoint workflow interop ](sharepoint-workflow-fundamentals#bkm_InteropBridge)
+-  [SharePoint workflow interop ](sharepoint-workflow-fundamentals.md#bkm_InteropBridge)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager)
+-  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md)
     
   
 
diff --git a/docs/general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md b/docs/general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md
index 2652395e86..8e5954174f 100644
--- a/docs/general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md
+++ b/docs/general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md
@@ -1,13 +1,14 @@
 ---
 title: Workflow actions quick reference (SharePoint 2010 Workflow platform)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: b033f79f-2179-4cfd-9d1c-7c04f83d4a4b
 ---
 
 
 
 # Workflow actions quick reference (SharePoint 2010 Workflow platform)
-Learn about the workflow actions that are available in the SharePoint 2010 Workflow Platform in Microsoft SharePoint Designer 2013.Use this article  *only*  if you are working in SharePoint Designer 2013, but want to continue to use the SharePoint 2010 Workflow Platform.If instead you want to use the SharePoint Workflow Platform, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform), along with other articles (mentioned in the "Additional resources" section) about new features that are available in the newer platform.To begin creating a workflow by using the 2010 Workflow Platform, select **SharePoint 2010 Workflow** in the **Platform Type** box in the **Create Workflow** dialog box.
+Learn about the workflow actions that are available in the SharePoint 2010 Workflow Platform in Microsoft SharePoint Designer 2013.Use this article  *only*  if you are working in SharePoint Designer 2013, but want to continue to use the SharePoint 2010 Workflow Platform.If instead you want to use the SharePoint Workflow Platform, see  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md), along with other articles (mentioned in the "Additional resources" section.md) about new features that are available in the newer platform.To begin creating a workflow by using the 2010 Workflow Platform, select **SharePoint 2010 Workflow** in the **Platform Type** box in the **Create Workflow** dialog box.
 ## Where to find the workflow actions
 <a name="section1"> </a>
 
@@ -25,7 +26,7 @@ While you are editing inside a workflow step, do one of the following:
   
 - Double-click inside the workflow step. In the search box that appears, type text that appears in the name of the action that you want (such as "add"), and then press Enter. Actions and conditions that contain the text that you typed appear below the text box.
     
-  ![Enter keywords to see list of related actions.](../../images/SPD15-wf-step1.png)
+  ![Enter keywords to see list of related actions.](../images/SPD15-wf-step1.png)
   
 
   
@@ -89,7 +90,7 @@ General actions are actions that display in the Actions list in all workflow con
 |Set Time Portion of Date/Time Field  <br/> | This action is initially displayed in a workflow step as **Set time as 00:00 for date (Output to Variable: date1)**. Use this action to create a timestamp and to store the output value in a variable. You can set the time in hours and minutes and add the current date, a specified date, or the result of a lookup. For example, suppose you want to add a timestamp to any new customer order that is added to an orders list. Instead of using the current time when the order was actually received in the timestamp, you want to add a specific time so that you can have your workflow perform any operation (such as routing orders to the warehouse) on all new items that have the same timestamp. Another example: Suppose that you have a presentation scheduled for 9 a.m. on a particular day, and you want to receive an email reminder. You can use this action to add the time to the date, pause the workflow till the day before the presentation, and then have the workflow send you the reminder.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Set time as <u>00</u>: <u>00</u> for <u>Current Item:Modified</u> (Output to <u>Modified time variable set to midnight</u>)  <br/> |
 |Set Workflow Status  <br/> | This action is initially displayed in a workflow step as **Set workflow status to Canceled**. Use this action to set the status of the workflow. The default options are Canceled, Approved, and Rejected.  <br/>  If you type a new status value in the dropdown list in the action, your new status is automatically added to the dropdown list for subsequent use. For example, you can add a custom status that is more user-friendly and informative than **Completed** or **Canceled**, such as **Expense Report Approved**.  <br/> **Note:** <br/> - You cannot rename or delete a custom status value once it has been created. However, you do not ever have to use it. <br/> - A custom status is applicable to the current workflow only, and cannot be used in another workflow.<br/> - A workflow cannot use custom status values that you define in the action if the action is used inside an impersonation step. <br/>If the **Set Workflow Status** action is the last step in a workflow where you have also used a custom value, you can see your custom value in the **Status** column in the list when the workflow pauses or completes. <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Set workflow status to <u>Specification status: Ready for Design Review</u> <br/> |
 |Set Workflow Variable  <br/> | This action is initially displayed in a workflow step as **Set workflow variable to value**. Use this action to direct the workflow to assign value data to a workflow variable.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Set <u>Variable: Expense report total</u> to  <u>Current Item:Total</u> <br/> |
-|<u>**List Actions**</u> <br/> |Actions in this category perform operations on list items.  <br/> **Note:** Some actions in this category appear in some but not all workflow contexts. For example, some list actions only appear when you click inside an impersonation step in your workflow, while some appear only when your workflow is attached to a document library or document content type. For more information, see  [Actions available only within an impersonation step](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section7a) and [Actions available when the workflow is associated to a document library or document content type](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section6) later in this article.          |
+|<u>**List Actions**</u> <br/> |Actions in this category perform operations on list items.  <br/> **Note:** Some actions in this category appear in some but not all workflow contexts. For example, some list actions only appear when you click inside an impersonation step in your workflow, while some appear only when your workflow is attached to a document library or document content type. For more information, see  [Actions available only within an impersonation step](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section7a) and [Actions available when the workflow is associated to a document library or document content type](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section6) later in this article.          |
 |Check In Item  <br/> | This action is initially displayed in a workflow step as **Check in item in this list with comment: comment**. Use this action to check in an item that is currently checked out.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Check in item in <u>Expense Reports</u> with comment: <u>Expense report approved</u> <br/> **Note:**  You can check in items only in document libraries.          |
 |Check Out Item  <br/> | This action is initially displayed in a workflow step as **Check out item in this list**. Use this action to check out an item that is currently checked in.  <br/>  Following is an example of what the action might look like in a workflow step: <br/>  - Check out item in <u>Current Item</u> <br/> **Note:** <br/> - You can check out items only from a library in your site.<br/> - Before checking the item out, the workflow first verifies that the item is currently checked in.          |
 |Copy List Item  <br/> | This action is initially displayed in a workflow step as **Copy item in this list to this list**. Use this action to copy a list item to another list. (If there is a document in the list item, the workflow also copies the document to the destination list.)  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Copy item in <u>Current Item</u> to <u>Archive Requests</u> <br/> **Important:**  There must be at least one column similar in both the source list and the destination list.          |
@@ -130,7 +131,7 @@ Actions such as **Start Approval Process**, **Declare Record**, and **Lookup Man
 |Capture a version of the Document Set  <br/> | This action is initially displayed in workflow steps as **Capture a version of this Document Set that includes the type versions of the contents with comment: comment**. Use this action to lock the version of the Document Set that contains the version of documents, major or minor, that you specify in the action.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Capture a version of this Document Set that includes the <u>last major</u> versions of the contents with comment: <u>Last major version of the Bill of Material</u> <br/> |
 |Send Document Set to Repository  <br/> | This action is initially displayed in workflow steps as **Submit Document Set using this action to this destination content organizer with this explanation (Output to Variable: submit file result)**. Use this action to move or copy a Document Set to a document repository. A document repository can be a library in your SharePoint site, or an entire site (like the Document Center), that routes records to a specific destination by using rules that you define.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Submit Document Set using <u>Copy</u> to <u>DocumentRepository:GUID</u> with <u>Copy final bill of Material to repository</u> (Output to <u>Variable: Copy Document Set to repository</u>)  <br/> **Note:**  Before you can define rules and route documents, you must enable the **Content Organizer** site feature in your SharePoint site. For more information, see the Configure the content organizer to route records topic in the See Also section.          |
 |Set Content Approval Status of the Document Set  <br/> | This action is initially displayed in workflow steps as **Set content approval status for the contents of this Document Set to this status with comments**. Use this action to set content approval of a Document Set to **Approved**, **Rejected**, or **Pending**.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Set content approval status for the contents of this Document Set to <u>Approved</u> with The bill of materials is approved <br/> **Note:**  Content approval must be enabled in the list before you can use this action.          |
-|<u>**Task Actions**</u> <br/> |Actions in this category are used in approval scenarios. There are two pre-built workflow actions in this category: **Start Approval Process** and **Start Feedback Process**. Pre-built actions work sort of like sub-workflows, meaning that the workflow logic is already defined in the actions. All you need to do is supply the appropriate information.  <br/> These actions are used in the globally reusable workflows **Approval-SharePoint** and **Collect Feedback-SharePoint** that are included with SharePoint. For information about when to use these workflows and when to use the actions, see the [When should you use the approval and feedback actions?](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section5) section of this article. <br/> Also available is the **Start Custom Task Process**, which also has built-in logic, but which (unlike the previous two actions) does not come pre-built with what the workflow should be doing at each phase.  <br/> A category of actions called **Task Behavior Actions** appear in the Actions list only when you customize the behavior of an approval action such as **Assign Item for Approval** or **Assign Item for Feedback**. For more information on **Task Behavior Actions**, see the  [Actions available within task actions](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section4) section of this article. <br/> |
+|<u>**Task Actions**</u> <br/> |Actions in this category are used in approval scenarios. There are two pre-built workflow actions in this category: **Start Approval Process** and **Start Feedback Process**. Pre-built actions work sort of like sub-workflows, meaning that the workflow logic is already defined in the actions. All you need to do is supply the appropriate information.  <br/> These actions are used in the globally reusable workflows **Approval-SharePoint** and **Collect Feedback-SharePoint** that are included with SharePoint. For information about when to use these workflows and when to use the actions, see the [When should you use the approval and feedback actions?](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section5) section of this article. <br/> Also available is the **Start Custom Task Process**, which also has built-in logic, but which (unlike the previous two actions.md) does not come pre-built with what the workflow should be doing at each phase.  <br/> A category of actions called **Task Behavior Actions** appear in the Actions list only when you customize the behavior of an approval action such as **Assign Item for Approval** or **Assign Item for Feedback**. For more information on **Task Behavior Actions**, see the  [Actions available within task actions](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section4) section of this article. <br/> |
 |Start Approval Process  <br/> | This action is initially displayed in a workflow step as **Start Approval process on Current Item with these users**. Use this action to route a document for approval. Approvers can approve or reject the document, reassign the approval task, or request changes to the document.  <br/>  The **Start Approval Process** action behaves like a pre-built workflow: the logic is already defined in the action. The action has distinct phases built in to define task behaviors, task process behaviors, logging to the History Log, e-mail notifications, and completion conditions. Although the action comes with this pre-built logic, it still needs information from you???such as who the reviewers are, whether the approval tasks are assigned one at a time ("in serial", the default) or all at once ("in parallel"), and the due dates or permitted durations for task completion. <br/>  You can assign tasks to both internal and external participants. An external participant can be either an employee in your organization who isn't a user in the site collection or anyone outside of your organization. <br/>  Following is an example of what the action might look like in a workflow step: <br/>  -Start <u>Specification Approval</u> process on <u>Current Item</u> with <u>Variable: Approvers</u> <br/> |
 |Start Feedback Process  <br/> | This action is initially displayed in a workflow step as **Start Feedback process on Current Item with these users**. Use this action to route a document for feedback. Reviewers can submit feedback or reassign the feedback task.  <br/>  The **Start Feedback Process** action behaves like a pre-built workflow: the logic is already defined in the action. The action has distinct phases built in to define task behaviors, task process behaviors, logging to the History Log, e-mail notifications, and completion conditions. Although the approval action comes with this pre-built logic, it still needs information from your end???such as who the reviewers are, whether the approval tasks are assigned one at a time ("in serial", the default) or all at once ("in parallel"), and the due dates or permitted durations for task completion. <br/>  You can assign tasks to both internal and external participants. An external participant can be either an employee in your organization who isn't a user in the site collection, or anyone outside of your organization. <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Start <u>Specification Feedback</u> process on <u>Current Item</u> with <u>Variable: Reviewers</u> <br/> |
 |Start Custom Task Process  <br/> | This action is initially displayed in a workflow step as **Start Task process on Current Item with these users**. Use the **Start Custom Task Process** action (an approval process template) if neither of the two preceding approval actions meets your needs. The **Start Custom Task Process** also allows logic to be built inside of it; but unlike the other two approval actions, it does not come pre-built with every action that the workflow needs in each of its phases. You can specify your own actions and conditions in task behaviors or completion conditions. <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Start <u>Video Lesson Approval</u> process on <u>Current Item</u> with <u>Variable: Approvers</u> <br/> |
@@ -238,7 +239,7 @@ Some workflow actions (such as **Shared Documents**) are available only when the
 |:-----|:-----|
 |<u>**Core Actions**</u> <br/> ||
 |Send Document to Repository  <br/> | This action is initially displayed in a workflow step as **Submit File using this action to this destination router with this explanation (Output to Variable: submit file result)**. Use this action to move or copy the document associated to the list item to a document repository. A document repository can be a library in your SharePoint site, or an entire site (like the Document Center), that routes records to a specific destination by using rules that you define.  <br/>  Following is an example of what the action might look like in a workflow step: <br/> - Submit File using <u>Move</u> to <u>Archive:DocumentID Value</u> with <u>The file is ready for archival</u> (Output to <u>Variable: Submit file for archival</u>)  <br/> |
-|<u>**Document Set Actions**</u> <br/> |Actions in this category pertain to a Document Set. A Document Set is a folder in which documents are stored. In a workflow, a Document Set and all of the documents that it contains are treated as a single item.  <br/> **Note:**<br/> - To be able to use Document Sets in your library, you must add the Document Set content type from your Library Settings page in your SharePoint site.<br/> - Document Sets are a feature of SharePoint. <br/>For more information about Document Sets Actions, see the  [Actions available when your SharePoint site is running SharePoint](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section3) section of this article. <br/> |
+|<u>**Document Set Actions**</u> <br/> |Actions in this category pertain to a Document Set. A Document Set is a folder in which documents are stored. In a workflow, a Document Set and all of the documents that it contains are treated as a single item.  <br/> **Note:**<br/> - To be able to use Document Sets in your library, you must add the Document Set content type from your Library Settings page in your SharePoint site.<br/> - Document Sets are a feature of SharePoint. <br/>For more information about Document Sets Actions, see the  [Actions available when your SharePoint site is running SharePoint](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section3) section of this article. <br/> |
 |<u>**List Actions**</u> <br/> |This category of actions performs operations on list items.  <br/> |
 |Delete Drafts  <br/> |This action is displayed in a workflow step as **Delete all drafts (minor versions) of the item**. Use this action to delete all existing draft or minor versions of the current item. There are no variables to set for this action.  <br/> **Note:** Versioning with minor versions must be enabled on the SharePoint list for this action to function.           |
 |Delete Previous Versions  <br/> |This action is displayed in a workflow step as **Delete all previous versions of the item**. Use this action to delete all existing previous versions of the current item. There are no variables to set for this action.  <br/> **Note:** Versioning must be enabled on the SharePoint list for this action to function.           |
@@ -271,7 +272,7 @@ Some list actions are available only inside an impersonation step in. Impersonat
 ## Actions within a site workflow
 <a name="section8"> </a>
 
-A site workflow operates at a site-level and is not attached to any more specific object (such as an individual item or content type). When you are working inside a site workflow, actions that work on a current item, such as **Set Content Approval Status** and **Set Field in Current Item**, are not available to you. For more information about these actions, see the  [General actions](workflow-actions-quick-reference-sharepoint-2010-workflow-platform#section2) section of this article.
+A site workflow operates at a site-level and is not attached to any more specific object (such as an individual item or content type). When you are working inside a site workflow, actions that work on a current item, such as **Set Content Approval Status** and **Set Field in Current Item**, are not available to you. For more information about these actions, see the  [General actions](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md#section2) section of this article.
   
     
     
@@ -280,16 +281,16 @@ A site workflow operates at a site-level and is not attached to any more specifi
 <a name="bk_addresources"> </a>
 
 
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/workflow-actions-quick-reference-sharepoint-workflow-platform.md b/docs/general-development/workflow-actions-quick-reference-sharepoint-workflow-platform.md
index a6d2936bff..8429363f41 100644
--- a/docs/general-development/workflow-actions-quick-reference-sharepoint-workflow-platform.md
+++ b/docs/general-development/workflow-actions-quick-reference-sharepoint-workflow-platform.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow actions quick reference (SharePoint Workflow platform)
-ms.prod: SHAREPOINTDESIGNER
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: eb3434e5-bc75-4474-8873-4980062fd29c
 ---
 
@@ -11,7 +12,7 @@ This reference lists the workflow actions that are supported in the current buil
 ## Workflow actions in SharePoint Designer 2013
 <a name="bkm_WorkflowActions"> </a>
 
-The following is a reference for workflow actions available for the SharePoint Workflow platform. In addition to the SharePoint Workflow platform, SharePoint Designer 2013 also supports the SharePoint 2010 Workflow platform. To view workflow actions for the 2010 platform, see  [Workflow actions quick reference (SharePoint 2010 Workflow platform)](workflow-actions-quick-reference-sharepoint-2010-workflow-platform)
+The following is a reference for workflow actions available for the SharePoint Workflow platform. In addition to the SharePoint Workflow platform, SharePoint Designer 2013 also supports the SharePoint 2010 Workflow platform. To view workflow actions for the 2010 platform, see  [Workflow actions quick reference (SharePoint 2010 Workflow platform)](workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md)
   
     
     
@@ -31,8 +32,8 @@ Core actions are those that are most commonly performed, and they are grouped to
 |:-----|:-----|
 |Add a Comment  <br/> |Enables you to leave informative comments in the workflow designer for reference purposes. This is especially helpful when there are other users collaborating on the workflow.  <br/> |
 |Add Time to Date  <br/> |Adds a specific time in minutes, hours, days, or months to a date (Year is not supported), and stores the output value as a variable. The date can be a current data, specific date, or a lookup. The 'Current Date' value returns UTC midnight.  <br/> |
-|Build Dictionary  <br/> |Builds a Dictionary variable of key/value pairs.  <br/> **Note:** The Dictionary uses JSON notation to store data.           For more information on the Dictionary variable, see  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer) <br/> |
-|Call HTTP Web Service  <br/> |Functions as a method call to an HTTP web service and returns data using the JSON format. Basic authentication is supported through the RequestHeader.  <br/> For more information on the Dictionary variable, see  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer) <br/> |
+|Build Dictionary  <br/> |Builds a Dictionary variable of key/value pairs.  <br/> **Note:** The Dictionary uses JSON notation to store data.           For more information on the Dictionary variable, see  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer.md) <br/> |
+|Call HTTP Web Service  <br/> |Functions as a method call to an HTTP web service and returns data using the JSON format. Basic authentication is supported through the RequestHeader.  <br/> For more information on the Dictionary variable, see  [Understanding Dictionary actions in SharePoint Designer 2013](understanding-dictionary-actions-in-sharepoint-designer.md) <br/> |
 |Count Items in a Dictionary  <br/> |Returns a count of the number of items in a specified dictionary.  <br/> |
 |Do Calculation  <br/> |Performs an arithmetic calculation and stores the output value in a variable.  <br/> **Note:** For SharePoint, this action supports only the **Double** numeric type. Integers are not supported. Use of the "+" operator (concatenation) for strings is not supported.          |
 |Get an Item from a Dictionary  <br/> |Returns a particular item from a dictionary variable.  <br/> |
@@ -49,7 +50,7 @@ Core actions are those that are most commonly performed, and they are grouped to
 ### Coordination actions
 <a name="bkm_CoreActions"> </a>
 
-Coordination actions are used to invoke a workflow based on the SharePoint 2010 Workflow platform. For more information on Coordination actions, see  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer)
+Coordination actions are used to invoke a workflow based on the SharePoint 2010 Workflow platform. For more information on Coordination actions, see  [Understanding Coordination actions in SharePoint Designer 2013](understanding-coordination-actions-in-sharepoint-designer.md)
   
     
     
@@ -153,7 +154,7 @@ Utility actions are actions that manipulate strings or find the interval between
 ## Workflow actions that are deprecated in SharePoint
 <a name="bkm_NotAvailable"> </a>
 
-For a list of actions from SharePoint 2010 that are deprecated and will not appear in SharePoint, see  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge).
+For a list of actions from SharePoint 2010 that are deprecated and will not appear in SharePoint, see  [Workflow actions available using the workflow interop bridge](workflow-actions-available-using-the-workflow-interop-bridge.md).
   
     
     
@@ -162,15 +163,15 @@ For a list of actions from SharePoint 2010 that are deprecated and will not appe
 <a name="bkm_addlresource"> </a>
 
 
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
diff --git a/docs/general-development/workflow-activity-classes-in-sharepoint.md b/docs/general-development/workflow-activity-classes-in-sharepoint.md
index 3bbab6e0fe..83bb5b8c3b 100644
--- a/docs/general-development/workflow-activity-classes-in-sharepoint.md
+++ b/docs/general-development/workflow-activity-classes-in-sharepoint.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow activity classes in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 70d5ca8d-520d-40a9-b24e-52bb31bd6c22
 ---
 
@@ -84,13 +85,13 @@ The palette of activity classes has been revised for SharePoint. Table 1 lists t
 <a name="bkm_addlresource"> </a>
 
 
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager)
+-  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md)
     
   
 
diff --git a/docs/general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md b/docs/general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md
index af4084352a..ec17f107a9 100644
--- a/docs/general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md
+++ b/docs/general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md
@@ -1,12 +1,13 @@
 ---
 title: Workflow conditions quick reference (SharePoint 2010 Workflow platform)
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 71fab25b-d4f3-4871-b9ad-08d3537098fc
 ---
 
 
 # Workflow conditions quick reference (SharePoint 2010 Workflow platform)
-Learn about the workflow conditions that are available in the SharePoint 2010 Workflow Platform in Microsoft SharePoint Designer 2013.Use this article  *only*  if you are working in SharePoint Designer 2013, but want to continue to use the SharePoint 2010 Workflow Platform.If instead you want to use the SharePoint Workflow Platform, see  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint), and other articles listed in the "Additional resources" section, which describe new features that are available in the newer platform.To begin creating a workflow by using the 2010 Workflow Platform, select **SharePoint 2010 Workflow** in the **Platform Type** box in the **Create Workflow** dialog box.
+Learn about the workflow conditions that are available in the SharePoint 2010 Workflow Platform in Microsoft SharePoint Designer 2013.Use this article  *only*  if you are working in SharePoint Designer 2013, but want to continue to use the SharePoint 2010 Workflow Platform.If instead you want to use the SharePoint Workflow Platform, see  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md), and other articles listed in the "Additional resources" section, which describe new features that are available in the newer platform.To begin creating a workflow by using the 2010 Workflow Platform, select **SharePoint 2010 Workflow** in the **Platform Type** box in the **Create Workflow** dialog box.
 ## Where to find the workflow conditions
 <a name="section1"> </a>
 
@@ -29,7 +30,7 @@ While you are editing inside a workflow step, do one of the following:
   
     
     
-![Enter keywords to see list of related conditions.](../../images/spd15-wf-step1a.JPG)
+![Enter keywords to see list of related conditions.](../images/spd15-wf-step1a.JPG)
   
     
     
@@ -41,7 +42,7 @@ Which conditions are available to you while you are creating or modifying a work
   
     
     
-![Available conditions in SharePoint Designer 2013](../../images/spd15-.JPG)
+![Available conditions in SharePoint Designer 2013](../images/spd15-.JPG)
   
     
     
@@ -113,7 +114,7 @@ Following are examples of what the condition might look like in a workflow step:
 - If Variable: Specification Namecontains (ignoring case)SharePoint Designer || SPD
     
   
-The **If any value equals value** condition is one of only two conditions available when you are working in a site workflow, the other being **Person is a valid SharePoint user**. For more information about site workflows, see the  [Conditions available within a site workflow](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform#section5) section of this article.
+The **If any value equals value** condition is one of only two conditions available when you are working in a site workflow, the other being **Person is a valid SharePoint user**. For more information about site workflows, see the  [Conditions available within a site workflow](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md#section5) section of this article.
   
     
     
@@ -251,7 +252,7 @@ Following is an example of what the condition might look like in a workflow step
 - If Molly Clark is a valid SharePoint user
     
   
-The **Person is a valid SharePoint user** condition is one of only two conditions available when you are working in a site workflow, the other being **If any value equals value**. For more information about site workflows, see the  [Conditions available within a site workflow](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform#section5) section in this article.
+The **Person is a valid SharePoint user** condition is one of only two conditions available when you are working in a site workflow, the other being **If any value equals value**. For more information about site workflows, see the  [Conditions available within a site workflow](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md#section5) section in this article.
   
     
     
@@ -268,7 +269,7 @@ This condition is initially displayed in a workflow step as **If title field con
   
     
     
-![Logical operators  used to search for keywords](../../images/spd15-wf-logical-ops.JPG)
+![Logical operators  used to search for keywords](../images/spd15-wf-logical-ops.JPG)
   
     
     
@@ -441,7 +442,7 @@ From within an impersonation step in a site workflow:
 - **Person is a valid SharePoint user**
     
   
-For more information about conditions, see the  [General conditions](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform#section2) section of this article.
+For more information about conditions, see the  [General conditions](workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md#section2) section of this article.
   
     
     
@@ -450,13 +451,13 @@ For more information about conditions, see the  [General conditions](workflow-co
 <a name="bk_addresources"> </a>
 
 
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
 
diff --git a/docs/general-development/workflow-development-in-sharepoint-designer-and-visio.md b/docs/general-development/workflow-development-in-sharepoint-designer-and-visio.md
index ad56a6b369..3e27736cc7 100644
--- a/docs/general-development/workflow-development-in-sharepoint-designer-and-visio.md
+++ b/docs/general-development/workflow-development-in-sharepoint-designer-and-visio.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow development in SharePoint Designer and Visio
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 496780d5-47d6-4a43-bf14-70aefb8d820c
 ---
 
@@ -154,7 +155,7 @@ To open the SharePoint Workflow template in Visio 2013, do the following:
     The template opens and the drawing canvas is prepopulated with Start, and Stage shapes. The Stage shape contains an Enter and an Exit shape, joined by a single connector.
     
   
-With the SharePoint Workflow template open, drag actions, conditions, and other shapes onto the drawing canvas to design a workflow. For more information about individual shapes and what they mean, see the article  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio).
+With the SharePoint Workflow template open, drag actions, conditions, and other shapes onto the drawing canvas to design a workflow. For more information about individual shapes and what they mean, see the article  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio.md).
   
     
     
@@ -176,7 +177,7 @@ With the SharePoint Workflow template open, drag actions, conditions, and other
   
     
     
-Validating the workflow in Visio 2013 is like validating any other connected diagram: Visio checks the diagram against a set of rules and returns a list of errors that it found in the diagram. See the article  [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio) to learn how to resolve validation issues.
+Validating the workflow in Visio 2013 is like validating any other connected diagram: Visio checks the diagram against a set of rules and returns a list of errors that it found in the diagram. See the article  [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md) to learn how to resolve validation issues.
   
     
     
@@ -190,7 +191,7 @@ Validating the workflow in Visio 2013 is like validating any other connected dia
 2. If any errors are found in the workflow, the **Issues** pane opens below the diagram. Choose each item in the list to select the shape in the diagram that caused the error.
     
   
-3. Resolve each validation error listed in the **Issues** list. Once all of the errors have been addressed, choose **Check Diagram** again. For more information about how to resolve validation issues in Visio 2013, see the article [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio).
+3. Resolve each validation error listed in the **Issues** list. Once all of the errors have been addressed, choose **Check Diagram** again. For more information about how to resolve validation issues in Visio 2013, see the article [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md).
     
   
 4. If no errors are found in the workflow, Visio displays a message stating that the diagram validation is complete and that no issues were found.
@@ -320,7 +321,7 @@ For example, the **Send an email** shape has two properties associated with it:
     
 
 > **Note:**
-> For more information about individual actions, shapes, and their properties, see the articles  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio) and [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform). 
+> For more information about individual actions, shapes, and their properties, see the articles  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio.md) and [Workflow actions quick reference (SharePoint Workflow platform.md)](workflow-actions-quick-reference-sharepoint-workflow-platform.md). 
   
     
     
@@ -362,13 +363,13 @@ For more information, see the following resources:
     
     
 
--  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform)
+-  [Workflow actions quick reference (SharePoint Workflow platform)](workflow-actions-quick-reference-sharepoint-workflow-platform.md)
     
   
--  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio)
+-  [Shapes in the SharePoint Server workflow template in Visio](shapes-in-the-sharepoint-server-workflow-template-in-visio.md)
     
   
--  [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio)
+-  [Troubleshooting SharePoint Server workflow validation errors in Visio](troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md)
     
   
 -  [Create, import, and export SharePoint workflows in Visio 2010](http://office.microsoft.com/en-us/visio-help/create-import-and-export-sharepoint-workflows-in-visio-HA101888007.aspx)
diff --git a/docs/general-development/workflow-initiation-and-configuration-properties.md b/docs/general-development/workflow-initiation-and-configuration-properties.md
index d19dfc1ff1..cee6a2835b 100644
--- a/docs/general-development/workflow-initiation-and-configuration-properties.md
+++ b/docs/general-development/workflow-initiation-and-configuration-properties.md
@@ -1,6 +1,7 @@
 ---
 title: Workflow initiation and configuration properties
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 7386bbf9-3ed6-4732-bcdb-b27baed7397e
 ---
 
@@ -183,10 +184,10 @@ List workflows instances have some additional external variables that are set by
 <a name="bk_addresources"> </a>
 
 
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [How to: Create SharePoint Workflows using Visual Studio](how-to-create-sharepoint-workflows-using-visual-studio)
+-  [How to: Create SharePoint Workflows using Visual Studio](how-to-create-sharepoint-workflows-using-visual-studio.md)
     
   
 
diff --git a/docs/general-development/workflows-in-sharepoint.md b/docs/general-development/workflows-in-sharepoint.md
index f7e14709c5..bd36a2351c 100644
--- a/docs/general-development/workflows-in-sharepoint.md
+++ b/docs/general-development/workflows-in-sharepoint.md
@@ -1,56 +1,57 @@
 ---
 title: Workflows in SharePoint
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e0602371-ae22-44be-8a7e-9e47e9f046d6
 ---
 
 
 # Workflows in SharePoint
 Learn about the Workflow Manager Client 1.0 authoring framework and workflow scenarios for SharePoint.
-SharePoint marks the introduction of Workflow Manager Client 1.0 as the new foundation for SharePoint workflows. Built on Windows Workflow Foundation 4, SharePoint workflows offer a new range of capabilities and enhancements. For an overview of the new flavor of workflows for SharePoint, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint).
+SharePoint marks the introduction of Workflow Manager Client 1.0 as the new foundation for SharePoint workflows. Built on Windows Workflow Foundation 4, SharePoint workflows offer a new range of capabilities and enhancements. For an overview of the new flavor of workflows for SharePoint, see  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md).
   
     
     
 
-For information about setting up Workflow Manager Client 1.0 and pairing it to function correctly with SharePoint, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager).
+For information about setting up Workflow Manager Client 1.0 and pairing it to function correctly with SharePoint, see  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md).
 ## In this section
 
 
--  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint)
+-  [Get started with workflows in SharePoint](get-started-with-workflows-in-sharepoint.md)
     
   
--  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint)
+-  [What's new in workflows for SharePoint](what-s-new-in-workflows-for-sharepoint.md)
     
   
--  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals)
+-  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md)
     
   
--  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices)
+-  [SharePoint workflow development best practices](sharepoint-workflow-development-best-practices.md)
     
   
--  [Using the pairing cmdlet Register-SPWorkflowService](using-the-pairing-cmdlet-register-spworkflowservice)
+-  [Using the pairing cmdlet Register-SPWorkflowService](using-the-pairing-cmdlet-register-spworkflowservice.md)
     
   
--  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio)
+-  [Workflow development in SharePoint Designer and Visio](workflow-development-in-sharepoint-designer-and-visio.md)
     
   
--  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio)
+-  [Develop SharePoint workflows using Visual Studio](develop-sharepoint-workflows-using-visual-studio.md)
     
   
--  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint)
+-  [Workflow actions and activities reference for SharePoint](workflow-actions-and-activities-reference-for-sharepoint.md)
     
   
 
 ## Related sections
 
 
--  [SharePoint development overview](sharepoint-development-overview)
+-  [SharePoint development overview](sharepoint-development-overview.md)
     
   
--  [Add SharePoint capabilities](add-sharepoint-capabilities)
+-  [Add SharePoint capabilities](add-sharepoint-capabilities.md)
     
   
--  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager)
+-  [Set up and configure SharePoint Workflow Manager](set-up-and-configure-sharepoint-workflow-manager.md)
     
     For more information about SharePoint site workflows, see  [Blog article from Sympraxis Consulting: Looping Through Content in a SharePoint Site Workflow](http://sympmarc.com/2016/01/14/looping-through-content-in-a-sharepoint-site-workflow-part-1-introduction)
     
diff --git a/docs/general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md b/docs/general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md
index fb3621545f..8661cfd0f5 100644
--- a/docs/general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md
+++ b/docs/general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md
@@ -1,6 +1,7 @@
 ---
 title: Working with Tasks in SharePoint Workflows using Visual Studio 2012
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: f5869fe2-1bef-4e6f-bfdc-3e109501d260
 ---
 
@@ -86,7 +87,7 @@ This new **Workflow Task** content type differs from the earlier **Task** conten
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig1](../../images/WorkingWithTasksSharePointWorkflowsFig1.png)
+  ![WorkingWithTasksSharePointWorkflowsFig1](../images/WorkingWithTasksSharePointWorkflowsFig1.png)
   
 
   
@@ -110,7 +111,7 @@ Prior to SharePoint, the workflow task list used the same list template as the s
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig2](../../images/WorkingWithTasksSharePointWorkflowsFig2.png)
+![WorkingWithTasksSharePointWorkflowsFig2](../images/WorkingWithTasksSharePointWorkflowsFig2.png)
   
     
     
@@ -139,7 +140,7 @@ Both SharePoint Designer 2013 and Visual Studio 2012 provide workflow authors tw
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig3](../../images/WorkingWithTasksSharePointWorkflowsFig3.png)
+![WorkingWithTasksSharePointWorkflowsFig3](../images/WorkingWithTasksSharePointWorkflowsFig3.png)
   
     
     
@@ -157,7 +158,7 @@ SharePoint lets you specify whether multiple tasks should run serially or in par
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig4](../../images/WorkingWithTasksSharePointWorkflowsFig4.png)
+![WorkingWithTasksSharePointWorkflowsFig4](../images/WorkingWithTasksSharePointWorkflowsFig4.png)
   
     
     
@@ -206,7 +207,7 @@ We are going to create a task in our workflow and assign it to the person who cr
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig4](../../images/WorkingWithTasksSharePointWorkflowsFig5.png)
+  ![WorkingWithTasksSharePointWorkflowsFig4](../images/WorkingWithTasksSharePointWorkflowsFig5.png)
   
 
   
@@ -236,7 +237,7 @@ We are going to create a task in our workflow and assign it to the person who cr
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig5](../../images/WorkingWithTasksSharePointWorkflowsFig6.png)
+  ![WorkingWithTasksSharePointWorkflowsFig5](../images/WorkingWithTasksSharePointWorkflowsFig6.png)
   
 
   
@@ -265,7 +266,7 @@ At this point we can create and assign the task to the author of the announcemen
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig7](../../images/WorkingWithTasksSharePointWorkflowsFig7.png)
+  ![WorkingWithTasksSharePointWorkflowsFig7](../images/WorkingWithTasksSharePointWorkflowsFig7.png)
   
 
   
@@ -289,7 +290,7 @@ Notice in Figure 8 the email options that you can set. Among other options, you
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig8](../../images/WorkingWithTasksSharePointWorkflowsFig8.png)
+![WorkingWithTasksSharePointWorkflowsFig8](../images/WorkingWithTasksSharePointWorkflowsFig8.png)
   
     
     
@@ -307,7 +308,7 @@ You can also set the task outcome options. You can select the workflow task cont
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig9](../../images/WorkingWithTasksSharePointWorkflowsFig9.png)
+![WorkingWithTasksSharePointWorkflowsFig9](../images/WorkingWithTasksSharePointWorkflowsFig9.png)
   
     
     
@@ -336,7 +337,7 @@ Once you have accepted values in the **Task Options** dialog box, select the **S
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig10](../../images/WorkingWithTasksSharePointWorkflowsFig10.png)
+![WorkingWithTasksSharePointWorkflowsFig10](../images/WorkingWithTasksSharePointWorkflowsFig10.png)
   
     
     
@@ -358,7 +359,7 @@ Notice that the **Outcome** property automatically created a variable named **ou
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig11](../../images/WorkingWithTasksSharePointWorkflowsFig11.png)
+![WorkingWithTasksSharePointWorkflowsFig11](../images/WorkingWithTasksSharePointWorkflowsFig11.png)
   
     
     
@@ -390,7 +391,7 @@ To test the workflow, do the following:
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig13](../../images/WorkingWithTasksSharePointWorkflowsFig12.png)
+  ![WorkingWithTasksSharePointWorkflowsFig13](../images/WorkingWithTasksSharePointWorkflowsFig12.png)
   
 
   
@@ -402,7 +403,7 @@ To test the workflow, do the following:
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig13](../../images/WorkingWithTasksSharePointWorkflowsFig13.png)
+  ![WorkingWithTasksSharePointWorkflowsFig13](../images/WorkingWithTasksSharePointWorkflowsFig13.png)
   
 
   
@@ -433,7 +434,7 @@ This approach can pose a challenge, however, in that the content type that the c
   
     
     
-![WorkingWithTasksSharePointWorkflowsFig14](../../images/WorkingWithTasksSharePointWorkflowsFig14.png)
+![WorkingWithTasksSharePointWorkflowsFig14](../images/WorkingWithTasksSharePointWorkflowsFig14.png)
   
     
     
@@ -575,7 +576,7 @@ Now we create a workflow so we can test the custom site column and content type.
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig15](../../images/WorkingWithTasksSharePointWorkflowsFig15.png)
+  ![WorkingWithTasksSharePointWorkflowsFig15](../images/WorkingWithTasksSharePointWorkflowsFig15.png)
   
 
   
@@ -610,7 +611,7 @@ Now we collect the list item properties.
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig16](../../images/WorkingWithTasksSharePointWorkflowsFig16.png)
+  ![WorkingWithTasksSharePointWorkflowsFig16](../images/WorkingWithTasksSharePointWorkflowsFig16.png)
   
 
   
@@ -639,7 +640,7 @@ Now we can create the single task.
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig17](../../images/WorkingWithTasksSharePointWorkflowsFig17.png)
+  ![WorkingWithTasksSharePointWorkflowsFig17](../images/WorkingWithTasksSharePointWorkflowsFig17.png)
   
 
   
@@ -654,7 +655,7 @@ Now we can create the single task.
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig18](../../images/WorkingWithTasksSharePointWorkflowsFig18.png)
+  ![WorkingWithTasksSharePointWorkflowsFig18](../images/WorkingWithTasksSharePointWorkflowsFig18.png)
   
 
   
@@ -721,7 +722,7 @@ Now let's test the workflow.
 
   
 
-  ![WorkingWithTasksSharePointWorkflowsFig19](../../images/WorkingWithTasksSharePointWorkflowsFig.png)
+  ![WorkingWithTasksSharePointWorkflowsFig19](../images/WorkingWithTasksSharePointWorkflowsFig.png)
   
 
   
diff --git a/docs/general-development/working-with-the-excel-services-javascript-object-model.md b/docs/general-development/working-with-the-excel-services-javascript-object-model.md
index c2ea762779..a7fdcffa48 100644
--- a/docs/general-development/working-with-the-excel-services-javascript-object-model.md
+++ b/docs/general-development/working-with-the-excel-services-javascript-object-model.md
@@ -1,6 +1,7 @@
 ---
 title: Working with the Excel Services JavaScript object model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 06219071-a7c1-4f54-b07f-7b7001592330
 ---
 
diff --git a/docs/general-development/working-with-the-sharepoint-workflow-services-client-side-object-model.md b/docs/general-development/working-with-the-sharepoint-workflow-services-client-side-object-model.md
index 9011520abb..b46923fbd7 100644
--- a/docs/general-development/working-with-the-sharepoint-workflow-services-client-side-object-model.md
+++ b/docs/general-development/working-with-the-sharepoint-workflow-services-client-side-object-model.md
@@ -1,6 +1,7 @@
 ---
 title: Working with the SharePoint Workflow Services Client Side Object Model
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: e180c2fb-a903-4ded-884e-b7584fa99189
 ---
 
@@ -150,7 +151,7 @@ When you create custom workflows using Visual Studio 2012, either using a soluti
   
     
     
-![Figure 1. Add a workflow association](../../images/ngSP2013WorkflowCSOM01.png)
+![Figure 1. Add a workflow association](../images/ngSP2013WorkflowCSOM01.png)
   
     
     
@@ -197,7 +198,7 @@ Service Bus is instrumental because it supports the publication and subscription
   
     
     
-SharePoint and Workflow Manager 1.0 use the PubSub model to create associations. Workflow associations are created as subscriptions on topics. For instance, an association for workflow definition may be created on list and set to start automatically when items are added to the list. When an item is added to the list, SharePoint publishes an event to Workflow Manager 1.0, which it sends to the Service Bus topic. The message is evaluated and the registered subscriptions are notified of the event. The subscribed association is found and the workflow is started. For more information about how this process works, see the MSDN article,  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals). 
+SharePoint and Workflow Manager 1.0 use the PubSub model to create associations. Workflow associations are created as subscriptions on topics. For instance, an association for workflow definition may be created on list and set to start automatically when items are added to the list. When an item is added to the list, SharePoint publishes an event to Workflow Manager 1.0, which it sends to the Service Bus topic. The message is evaluated and the registered subscriptions are notified of the event. The subscribed association is found and the workflow is started. For more information about how this process works, see the MSDN article,  [SharePoint workflow fundamentals](sharepoint-workflow-fundamentals.md). 
   
     
     
@@ -677,7 +678,7 @@ To receive the message in the workflow, add a **WaitForCustomEvent** activity an
   
     
     
-![Figure 2. Input EventName and Output Result](../../images/ngSP2013WorkflowCSOM02.png)
+![Figure 2. Input EventName and Output Result](../images/ngSP2013WorkflowCSOM02.png)
   
     
     
diff --git a/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md b/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md
index 6c6ffa3559..e1497da1dc 100644
--- a/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md
+++ b/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md
@@ -1,6 +1,7 @@
 ---
 title: Working with Web Services in SharePoint Workflows using SharePoint Designer 2013
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: bc8769c6-ae71-4519-abf3-c1b6fb071059
 ---
 
@@ -66,7 +67,7 @@ In SharePoint workflows, you call a web service using a new action introduced in
   
     
     
-![Figure 1. Call HTTP Web Service action](../../images/ngWSSP2013WorkflowSPD2013.png)
+![Figure 1. Call HTTP Web Service action](../images/ngWSSP2013WorkflowSPD2013.png)
   
     
     
@@ -174,7 +175,7 @@ The following walkthrough demonstrates how to create a custom workflow that call
 
   
 
-  ![Figure 2. Creating the Customers list in SP](../../images/ngWSSP2013WorkflowSPD201302.png)
+  ![Figure 2. Creating the Customers list in SP](../images/ngWSSP2013WorkflowSPD201302.png)
   
 
   
@@ -199,7 +200,7 @@ The following walkthrough demonstrates how to create a custom workflow that call
 
   
 
-  ![Figure 3. Creating a new List Workflow using SP](../../images/ngWSSP2013WorkflowSPD201303.png)
+  ![Figure 3. Creating a new List Workflow using SP](../images/ngWSSP2013WorkflowSPD201303.png)
   
 
   
@@ -234,7 +235,7 @@ Now that we've created the workflow, we want to enable it to call a web service,
 
   
 
-  ![Figure 4. Dynamically Creating the URL for the Web](../../images/ngWSSP2013WorkflowSPD201304.png)
+  ![Figure 4. Dynamically Creating the URL for the Web](../images/ngWSSP2013WorkflowSPD201304.png)
   
 
   
@@ -256,7 +257,7 @@ Now that we've created the workflow, we want to enable it to call a web service,
 
   
 
-  ![Figure 5. Writing the Web Service Response Code to](../../images/ngWSSP2013WorkflowSPD201305.png)
+  ![Figure 5. Writing the Web Service Response Code to](../images/ngWSSP2013WorkflowSPD201305.png)
   
 
   
@@ -292,7 +293,7 @@ To do this, we're going to add two **Get item from dictionary** actions to the w
 
   
 
-  ![Figure 6. Extracting Values from the Web Service D](../../images/ngWSSP2013WorkflowSPD201306.png)
+  ![Figure 6. Extracting Values from the Web Service D](../images/ngWSSP2013WorkflowSPD201306.png)
   
 
   
@@ -315,7 +316,7 @@ The final step is to update the list item using two of the **Set field in curren
   
     
     
-![Figure 7. Update the List Item](../../images/ngWSSP2013WorkflowSPD201307.png)
+![Figure 7. Update the List Item](../images/ngWSSP2013WorkflowSPD201307.png)
   
     
     
@@ -357,7 +358,7 @@ And finally, we complete the **Transition to stage** section of the workflow sta
 
   
 
-  ![Figure 8. List Items Updated by Custom Workflow](../../images/ngWSSP2013WorkflowSPD201308.png)
+  ![Figure 8. List Items Updated by Custom Workflow](../images/ngWSSP2013WorkflowSPD201308.png)
   
 
   
@@ -379,7 +380,7 @@ SharePointintroduced a new workflow architecture facilitated by a new product, W
 <a name="bk_addresources"> </a>
 
 
--  [Workflows in SharePoint](workflows-in-sharepoint)
+-  [Workflows in SharePoint](workflows-in-sharepoint.md)
     
   
 -  [OData](http://www.odata.org/)
diff --git a/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012.md b/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012.md
index 644237496a..461950a7b7 100644
--- a/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012.md
+++ b/docs/general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012.md
@@ -1,6 +1,7 @@
 ---
 title: Working with Web Services in SharePoint Workflows using Visual Studio 2012
-ms.prod: SHAREPOINT
+ms.date: 09/25/2017
+ms.prod: sharepoint
 ms.assetid: 5ffaa585-a872-4e14-bc0e-4a38c6a16b04
 ---
 
@@ -65,7 +66,7 @@ Working with web services in SharePoint workflows involves two stages. The first
   
     
     
-![Figure 1. Properties Tool Window for the HttpSend](../../images/ngWSSP2013WorkflowVS201201.png)
+![Figure 1. Properties Tool Window for the HttpSend](../images/ngWSSP2013WorkflowVS201201.png)
   
     
     
@@ -219,7 +220,7 @@ When the workflow is completed, users will enter a customer ID, then start the w
 
   
 
-  ![Figure 2. Complete Customer Details Workflow](../../images/ngWSSP2013WorkflowVS201202.png)
+  ![Figure 2. Complete Customer Details Workflow](../images/ngWSSP2013WorkflowVS201202.png)
   
 
   
@@ -248,7 +249,7 @@ The first thing the workflow needs to do is retrieve the customer ID, as entered
 
   
 
-  ![Figure 3. Properties Tool Window](../../images/ngWSSP2013WorkflowVS201203.png)
+  ![Figure 3. Properties Tool Window](../images/ngWSSP2013WorkflowVS201203.png)
   
 
     This activity tells Workflow Manager to use the SharePoint REST API to retrieve the properties of the current list item and to store the **JSON** response in the **DynamicValue** variable that you just created.
@@ -269,7 +270,7 @@ The first thing the workflow needs to do is retrieve the customer ID, as entered
 
   
 
-  ![Figure 4. Properties dialog from the activity](../../images/ngWSSP2013WorkflowVS201204.png)
+  ![Figure 4. Properties dialog from the activity](../images/ngWSSP2013WorkflowVS201204.png)
   
 
   
@@ -303,7 +304,7 @@ The workflow now has a reference to the customer ID, so the next step is to call
 
   
 
-  ![FIgure 5. Assign Activity](../../images/ngWSSP2013WorkflowVS201205.png)
+  ![FIgure 5. Assign Activity](../images/ngWSSP2013WorkflowVS201205.png)
   
 
   
@@ -318,7 +319,7 @@ The workflow now has a reference to the customer ID, so the next step is to call
 
   
 
-  ![Figure 6. HttpSend Properties](../../images/ngWSSP2013WorkflowVS201206.png)
+  ![Figure 6. HttpSend Properties](../images/ngWSSP2013WorkflowVS201206.png)
   
 
   
@@ -370,7 +371,7 @@ Once the web service request has been made and the results are stored in a local
 
   
 
-  ![Figure 7. Properties tool window](../../images/ngWSSP2013WorkflowVS201207.png)
+  ![Figure 7. Properties tool window](../images/ngWSSP2013WorkflowVS201207.png)
   
 
   
@@ -401,7 +402,7 @@ The last step is to update the list item.
 
   
 
-  ![Figure 8. ListItemPropertiesDynamicValue Dialog](../../images/ngWSSP2013WorkflowVS201208.png)
+  ![Figure 8. ListItemPropertiesDynamicValue Dialog](../images/ngWSSP2013WorkflowVS201208.png)
   
 
   
@@ -424,7 +425,7 @@ The workflow is now complete and should function properly. To confirm its stabil
 
   
 
-  ![Figure 9. New List Item](../../images/ngWSSP2013WorkflowVS201209.png)
+  ![Figure 9. New List Item](../images/ngWSSP2013WorkflowVS201209.png)
   
 
   
@@ -436,7 +437,7 @@ The workflow is now complete and should function properly. To confirm its stabil
 
   
 
-  ![Figure 10 Updated List Item](../../images/ngWSSP2013WorkflowVS201210.png)
+  ![Figure 10 Updated List Item](../images/ngWSSP2013WorkflowVS201210.png)
   
 
     Notice that the list item was updated by the SharePoint hosted app on behalf of the person who started the workflow. In this walkthrough, however, it was started by the administrator.
diff --git a/images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG b/docs/images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG
similarity index 100%
rename from images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG
rename to docs/images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG
diff --git a/images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif b/docs/images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif
similarity index 100%
rename from images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif
rename to docs/images/0d28b4f9-7f81-47c0-976e-247c2b9544d4.gif
diff --git a/images/101_page_model_overview.gif b/docs/images/101_page_model_overview.gif
similarity index 100%
rename from images/101_page_model_overview.gif
rename to docs/images/101_page_model_overview.gif
diff --git a/images/102_master_page.gif b/docs/images/102_master_page.gif
similarity index 100%
rename from images/102_master_page.gif
rename to docs/images/102_master_page.gif
diff --git a/images/103_master_page_with_page_layout_outlined.gif b/docs/images/103_master_page_with_page_layout_outlined.gif
similarity index 100%
rename from images/103_master_page_with_page_layout_outlined.gif
rename to docs/images/103_master_page_with_page_layout_outlined.gif
diff --git a/images/104_master_page_preview_message.gif b/docs/images/104_master_page_preview_message.gif
similarity index 100%
rename from images/104_master_page_preview_message.gif
rename to docs/images/104_master_page_preview_message.gif
diff --git a/images/105_page_layout.gif b/docs/images/105_page_layout.gif
similarity index 100%
rename from images/105_page_layout.gif
rename to docs/images/105_page_layout.gif
diff --git a/images/106_content_region_and_content_placeholder.gif b/docs/images/106_content_region_and_content_placeholder.gif
similarity index 100%
rename from images/106_content_region_and_content_placeholder.gif
rename to docs/images/106_content_region_and_content_placeholder.gif
diff --git a/images/107_page_layout_with_page_fields.gif b/docs/images/107_page_layout_with_page_fields.gif
similarity index 100%
rename from images/107_page_layout_with_page_fields.gif
rename to docs/images/107_page_layout_with_page_fields.gif
diff --git a/images/108_master_page_with_page_layout.gif b/docs/images/108_master_page_with_page_layout.gif
similarity index 100%
rename from images/108_master_page_with_page_layout.gif
rename to docs/images/108_master_page_with_page_layout.gif
diff --git a/images/109_one_master_many_layouts.gif b/docs/images/109_one_master_many_layouts.gif
similarity index 100%
rename from images/109_one_master_many_layouts.gif
rename to docs/images/109_one_master_many_layouts.gif
diff --git a/images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG b/docs/images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG
similarity index 100%
rename from images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG
rename to docs/images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG
diff --git a/images/110_page_with_authored_content.gif b/docs/images/110_page_with_authored_content.gif
similarity index 100%
rename from images/110_page_with_authored_content.gif
rename to docs/images/110_page_with_authored_content.gif
diff --git a/images/111_rendered_page.gif b/docs/images/111_rendered_page.gif
similarity index 100%
rename from images/111_rendered_page.gif
rename to docs/images/111_rendered_page.gif
diff --git a/images/112_master_plus_layout_plus_page.gif b/docs/images/112_master_plus_layout_plus_page.gif
similarity index 100%
rename from images/112_master_plus_layout_plus_page.gif
rename to docs/images/112_master_plus_layout_plus_page.gif
diff --git a/images/113_114_master_and_layout_and_page_and_web_part_closeup.gif b/docs/images/113_114_master_and_layout_and_page_and_web_part_closeup.gif
similarity index 100%
rename from images/113_114_master_and_layout_and_page_and_web_part_closeup.gif
rename to docs/images/113_114_master_and_layout_and_page_and_web_part_closeup.gif
diff --git a/images/115_content_search_web_part_tool_pane.gif b/docs/images/115_content_search_web_part_tool_pane.gif
similarity index 100%
rename from images/115_content_search_web_part_tool_pane.gif
rename to docs/images/115_content_search_web_part_tool_pane.gif
diff --git a/images/116_117_control_templates_1_and_2.gif b/docs/images/116_117_control_templates_1_and_2.gif
similarity index 100%
rename from images/116_117_control_templates_1_and_2.gif
rename to docs/images/116_117_control_templates_1_and_2.gif
diff --git a/images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif b/docs/images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif
similarity index 100%
rename from images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif
rename to docs/images/11734dcf-1b57-40cc-b1e8-8b10b7e5d5cb.gif
diff --git a/images/118_119_control_template_outlined_on_web_part_and_page.gif b/docs/images/118_119_control_template_outlined_on_web_part_and_page.gif
similarity index 100%
rename from images/118_119_control_template_outlined_on_web_part_and_page.gif
rename to docs/images/118_119_control_template_outlined_on_web_part_and_page.gif
diff --git a/images/120_121_item_templates_outlined_on_web_part_and_page.gif b/docs/images/120_121_item_templates_outlined_on_web_part_and_page.gif
similarity index 100%
rename from images/120_121_item_templates_outlined_on_web_part_and_page.gif
rename to docs/images/120_121_item_templates_outlined_on_web_part_and_page.gif
diff --git a/images/122_123_two_channels_two_master_pages.gif b/docs/images/122_123_two_channels_two_master_pages.gif
similarity index 100%
rename from images/122_123_two_channels_two_master_pages.gif
rename to docs/images/122_123_two_channels_two_master_pages.gif
diff --git a/images/124_one_layout_many_masters.gif b/docs/images/124_one_layout_many_masters.gif
similarity index 100%
rename from images/124_one_layout_many_masters.gif
rename to docs/images/124_one_layout_many_masters.gif
diff --git a/images/125_126_page_layout_with_channel_panels.gif b/docs/images/125_126_page_layout_with_channel_panels.gif
similarity index 100%
rename from images/125_126_page_layout_with_channel_panels.gif
rename to docs/images/125_126_page_layout_with_channel_panels.gif
diff --git a/images/127_128_item_display_templates_with_channel_panel.gif b/docs/images/127_128_item_display_templates_with_channel_panel.gif
similarity index 100%
rename from images/127_128_item_display_templates_with_channel_panel.gif
rename to docs/images/127_128_item_display_templates_with_channel_panel.gif
diff --git a/images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG b/docs/images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG
similarity index 100%
rename from images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG
rename to docs/images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG
diff --git a/images/14d5a820-ab44-4d12-98de-6672884bf344.PNG b/docs/images/14d5a820-ab44-4d12-98de-6672884bf344.PNG
similarity index 100%
rename from images/14d5a820-ab44-4d12-98de-6672884bf344.PNG
rename to docs/images/14d5a820-ab44-4d12-98de-6672884bf344.PNG
diff --git a/images/159f676e-421e-4190-94a6-cf311f7db2ca.gif b/docs/images/159f676e-421e-4190-94a6-cf311f7db2ca.gif
similarity index 100%
rename from images/159f676e-421e-4190-94a6-cf311f7db2ca.gif
rename to docs/images/159f676e-421e-4190-94a6-cf311f7db2ca.gif
diff --git a/images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF b/docs/images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF
similarity index 100%
rename from images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF
rename to docs/images/17740d96-b5cf-4a0f-938d-a0d0d1e91f1e.GIF
diff --git a/images/19126dce-b896-4623-8686-92f2fa807283.gif b/docs/images/19126dce-b896-4623-8686-92f2fa807283.gif
similarity index 100%
rename from images/19126dce-b896-4623-8686-92f2fa807283.gif
rename to docs/images/19126dce-b896-4623-8686-92f2fa807283.gif
diff --git a/images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif b/docs/images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif
similarity index 100%
rename from images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif
rename to docs/images/19b38f1b-8f98-4e91-8384-ba0e2d3da744.gif
diff --git a/images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg b/docs/images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg
similarity index 100%
rename from images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg
rename to docs/images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg
diff --git a/images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif b/docs/images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif
similarity index 100%
rename from images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif
rename to docs/images/1a9680d3-7a96-4d82-b0b9-9a9384bf96c2.gif
diff --git a/images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG b/docs/images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG
similarity index 100%
rename from images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG
rename to docs/images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG
diff --git a/images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg b/docs/images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg
similarity index 100%
rename from images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg
rename to docs/images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg
diff --git a/images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png b/docs/images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png
similarity index 100%
rename from images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png
rename to docs/images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png
diff --git a/images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif b/docs/images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif
similarity index 100%
rename from images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif
rename to docs/images/21aebcdb-d7e6-4a61-ac6e-6ae266b1b55d.gif
diff --git a/images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG b/docs/images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG
similarity index 100%
rename from images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG
rename to docs/images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG
diff --git a/images/25ba5677-f530-432a-9980-64b5eb33119c.png b/docs/images/25ba5677-f530-432a-9980-64b5eb33119c.png
similarity index 100%
rename from images/25ba5677-f530-432a-9980-64b5eb33119c.png
rename to docs/images/25ba5677-f530-432a-9980-64b5eb33119c.png
diff --git a/images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG b/docs/images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG
similarity index 100%
rename from images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG
rename to docs/images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG
diff --git a/images/2d011e17-953f-42b1-97d3-2525372296c1.gif b/docs/images/2d011e17-953f-42b1-97d3-2525372296c1.gif
similarity index 100%
rename from images/2d011e17-953f-42b1-97d3-2525372296c1.gif
rename to docs/images/2d011e17-953f-42b1-97d3-2525372296c1.gif
diff --git a/images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG b/docs/images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG
similarity index 100%
rename from images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG
rename to docs/images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG
diff --git a/images/2df9591d-a837-4130-98e4-5863d0c717e8.gif b/docs/images/2df9591d-a837-4130-98e4-5863d0c717e8.gif
similarity index 100%
rename from images/2df9591d-a837-4130-98e4-5863d0c717e8.gif
rename to docs/images/2df9591d-a837-4130-98e4-5863d0c717e8.gif
diff --git a/images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif b/docs/images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif
similarity index 100%
rename from images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif
rename to docs/images/2e5dc58a-55d2-48c6-a162-974199ff5e5c.gif
diff --git a/images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG b/docs/images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG
similarity index 100%
rename from images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG
rename to docs/images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG
diff --git a/images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG b/docs/images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG
similarity index 100%
rename from images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG
rename to docs/images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG
diff --git a/images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg b/docs/images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg
similarity index 100%
rename from images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg
rename to docs/images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg
diff --git a/images/3b33c622-c52a-45fd-8ea1-d7f307539753.png b/docs/images/3b33c622-c52a-45fd-8ea1-d7f307539753.png
similarity index 100%
rename from images/3b33c622-c52a-45fd-8ea1-d7f307539753.png
rename to docs/images/3b33c622-c52a-45fd-8ea1-d7f307539753.png
diff --git a/images/3b9184db-99a4-416e-ba1e-7f8653484cee.png b/docs/images/3b9184db-99a4-416e-ba1e-7f8653484cee.png
similarity index 100%
rename from images/3b9184db-99a4-416e-ba1e-7f8653484cee.png
rename to docs/images/3b9184db-99a4-416e-ba1e-7f8653484cee.png
diff --git a/images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif b/docs/images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif
similarity index 100%
rename from images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif
rename to docs/images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif
diff --git a/images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png b/docs/images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png
similarity index 100%
rename from images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png
rename to docs/images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png
diff --git a/images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG b/docs/images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG
similarity index 100%
rename from images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG
rename to docs/images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG
diff --git a/images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg b/docs/images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg
similarity index 100%
rename from images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg
rename to docs/images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg
diff --git a/images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG b/docs/images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG
similarity index 100%
rename from images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG
rename to docs/images/43a35ca2-2c93-4323-a169-769c3a54fa38.PNG
diff --git a/images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg b/docs/images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg
similarity index 100%
rename from images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg
rename to docs/images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg
diff --git a/images/44928b39-5683-4bce-8ddf-31d886243b87.gif b/docs/images/44928b39-5683-4bce-8ddf-31d886243b87.gif
similarity index 100%
rename from images/44928b39-5683-4bce-8ddf-31d886243b87.gif
rename to docs/images/44928b39-5683-4bce-8ddf-31d886243b87.gif
diff --git a/images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png b/docs/images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png
similarity index 100%
rename from images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png
rename to docs/images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png
diff --git a/images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG b/docs/images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG
similarity index 100%
rename from images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG
rename to docs/images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG
diff --git a/images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif b/docs/images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif
similarity index 100%
rename from images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif
rename to docs/images/49a93d59-6755-4afc-a703-ca8469b6fa74.gif
diff --git a/images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG b/docs/images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG
similarity index 100%
rename from images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG
rename to docs/images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG
diff --git a/images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif b/docs/images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif
similarity index 100%
rename from images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif
rename to docs/images/4a1e594e-cc3b-4bd6-bfe7-27568e30bb2b.gif
diff --git a/images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG b/docs/images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG
similarity index 100%
rename from images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG
rename to docs/images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG
diff --git a/images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG b/docs/images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG
similarity index 100%
rename from images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG
rename to docs/images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG
diff --git a/images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG b/docs/images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG
similarity index 100%
rename from images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG
rename to docs/images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG
diff --git a/images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif b/docs/images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif
similarity index 100%
rename from images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif
rename to docs/images/558e6305-5a42-4b5c-9a70-1116ddcf6637.gif
diff --git a/images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png b/docs/images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png
similarity index 100%
rename from images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png
rename to docs/images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png
diff --git a/images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg b/docs/images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg
similarity index 100%
rename from images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg
rename to docs/images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg
diff --git a/images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG b/docs/images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG
similarity index 100%
rename from images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG
rename to docs/images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG
diff --git a/images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG b/docs/images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG
similarity index 100%
rename from images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG
rename to docs/images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG
diff --git a/images/65926095-d833-4eb2-b899-9efe40e2d540.GIF b/docs/images/65926095-d833-4eb2-b899-9efe40e2d540.GIF
similarity index 100%
rename from images/65926095-d833-4eb2-b899-9efe40e2d540.GIF
rename to docs/images/65926095-d833-4eb2-b899-9efe40e2d540.GIF
diff --git a/images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG b/docs/images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG
similarity index 100%
rename from images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG
rename to docs/images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG
diff --git a/images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG b/docs/images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG
similarity index 100%
rename from images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG
rename to docs/images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG
diff --git a/images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png b/docs/images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png
similarity index 100%
rename from images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png
rename to docs/images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png
diff --git a/images/6d3bbe0a-399e-4747-9e1a-01d42954ce32.png b/docs/images/6d3bbe0a-399e-4747-9e1a-01d42954ce32.png
similarity index 100%
rename from images/6d3bbe0a-399e-4747-9e1a-01d42954ce32.png
rename to docs/images/6d3bbe0a-399e-4747-9e1a-01d42954ce32.png
diff --git a/images/70d5a602-b349-4791-bf05-d61635d0fc91.gif b/docs/images/70d5a602-b349-4791-bf05-d61635d0fc91.gif
similarity index 100%
rename from images/70d5a602-b349-4791-bf05-d61635d0fc91.gif
rename to docs/images/70d5a602-b349-4791-bf05-d61635d0fc91.gif
diff --git a/images/7298a25b-ed54-4953-a781-26c3f633866a.jpg b/docs/images/7298a25b-ed54-4953-a781-26c3f633866a.jpg
similarity index 100%
rename from images/7298a25b-ed54-4953-a781-26c3f633866a.jpg
rename to docs/images/7298a25b-ed54-4953-a781-26c3f633866a.jpg
diff --git a/images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG b/docs/images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG
similarity index 100%
rename from images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG
rename to docs/images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG
diff --git a/images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg b/docs/images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg
similarity index 100%
rename from images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg
rename to docs/images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg
diff --git a/images/7639578e-3d3f-40cf-8f53-355bb19c539b.png b/docs/images/7639578e-3d3f-40cf-8f53-355bb19c539b.png
similarity index 100%
rename from images/7639578e-3d3f-40cf-8f53-355bb19c539b.png
rename to docs/images/7639578e-3d3f-40cf-8f53-355bb19c539b.png
diff --git a/images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif b/docs/images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif
similarity index 100%
rename from images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif
rename to docs/images/7745688c-c612-4a38-b8aa-b5fdb5e4eeb8.gif
diff --git a/images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif b/docs/images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif
similarity index 100%
rename from images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif
rename to docs/images/77a290e8-e4aa-4c54-b1ec-3d74bf3962b6.gif
diff --git a/images/7849d413-381f-4558-9e50-b3cc9990d3e3.png b/docs/images/7849d413-381f-4558-9e50-b3cc9990d3e3.png
similarity index 100%
rename from images/7849d413-381f-4558-9e50-b3cc9990d3e3.png
rename to docs/images/7849d413-381f-4558-9e50-b3cc9990d3e3.png
diff --git a/images/787df903-833d-4a12-a692-716ceaf54c10.gif b/docs/images/787df903-833d-4a12-a692-716ceaf54c10.gif
similarity index 100%
rename from images/787df903-833d-4a12-a692-716ceaf54c10.gif
rename to docs/images/787df903-833d-4a12-a692-716ceaf54c10.gif
diff --git a/images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG b/docs/images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG
similarity index 100%
rename from images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG
rename to docs/images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG
diff --git a/images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG b/docs/images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG
similarity index 100%
rename from images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG
rename to docs/images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG
diff --git a/images/7fd942de-a324-4f70-a750-f5304c993832.PNG b/docs/images/7fd942de-a324-4f70-a750-f5304c993832.PNG
similarity index 100%
rename from images/7fd942de-a324-4f70-a750-f5304c993832.PNG
rename to docs/images/7fd942de-a324-4f70-a750-f5304c993832.PNG
diff --git a/images/833fcdcc-1755-438b-9ada-dce9646564c0.gif b/docs/images/833fcdcc-1755-438b-9ada-dce9646564c0.gif
similarity index 100%
rename from images/833fcdcc-1755-438b-9ada-dce9646564c0.gif
rename to docs/images/833fcdcc-1755-438b-9ada-dce9646564c0.gif
diff --git a/images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG b/docs/images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG
similarity index 100%
rename from images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG
rename to docs/images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG
diff --git a/images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG b/docs/images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG
similarity index 100%
rename from images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG
rename to docs/images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG
diff --git a/images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif b/docs/images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif
similarity index 100%
rename from images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif
rename to docs/images/884d6dcb-c690-4b43-9bb2-d1bcaf4b7a31.gif
diff --git a/images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg b/docs/images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg
similarity index 100%
rename from images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg
rename to docs/images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg
diff --git a/images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG b/docs/images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG
similarity index 100%
rename from images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG
rename to docs/images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG
diff --git a/images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif b/docs/images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif
similarity index 100%
rename from images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif
rename to docs/images/8d56d824-d96a-4f1e-9040-ce1da9a734d8.gif
diff --git a/images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG b/docs/images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG
similarity index 100%
rename from images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG
rename to docs/images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG
diff --git a/images/903d3109-d567-4156-a44f-29793c42ae45.gif b/docs/images/903d3109-d567-4156-a44f-29793c42ae45.gif
similarity index 100%
rename from images/903d3109-d567-4156-a44f-29793c42ae45.gif
rename to docs/images/903d3109-d567-4156-a44f-29793c42ae45.gif
diff --git a/images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg b/docs/images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg
similarity index 100%
rename from images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg
rename to docs/images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg
diff --git a/images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif b/docs/images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif
similarity index 100%
rename from images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif
rename to docs/images/9159345c-ce12-41a6-8994-fc2e9aa26fd6.gif
diff --git a/images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png b/docs/images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png
similarity index 100%
rename from images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png
rename to docs/images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png
diff --git a/images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif b/docs/images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif
similarity index 100%
rename from images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif
rename to docs/images/921bd9ab-d9a4-4cb6-b168-9ae53401d6d6.gif
diff --git a/images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif b/docs/images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif
similarity index 100%
rename from images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif
rename to docs/images/96681da7-ceab-40f3-8d08-441aea9b4a6f.gif
diff --git a/images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif b/docs/images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif
similarity index 100%
rename from images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif
rename to docs/images/97765b6d-51e9-4d07-8b5d-3e93c0508b16.gif
diff --git a/images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg b/docs/images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg
similarity index 100%
rename from images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg
rename to docs/images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg
diff --git a/images/99209248-8927-4fc2-abfc-53d530376516.PNG b/docs/images/99209248-8927-4fc2-abfc-53d530376516.PNG
similarity index 100%
rename from images/99209248-8927-4fc2-abfc-53d530376516.PNG
rename to docs/images/99209248-8927-4fc2-abfc-53d530376516.PNG
diff --git a/images/99376713-6a54-4d88-9b05-068578169506.gif b/docs/images/99376713-6a54-4d88-9b05-068578169506.gif
similarity index 100%
rename from images/99376713-6a54-4d88-9b05-068578169506.gif
rename to docs/images/99376713-6a54-4d88-9b05-068578169506.gif
diff --git a/images/997021de-c60c-46b0-961f-7e1e63c0f619.gif b/docs/images/997021de-c60c-46b0-961f-7e1e63c0f619.gif
similarity index 100%
rename from images/997021de-c60c-46b0-961f-7e1e63c0f619.gif
rename to docs/images/997021de-c60c-46b0-961f-7e1e63c0f619.gif
diff --git a/images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif b/docs/images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif
similarity index 100%
rename from images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif
rename to docs/images/99ff6118-ed5d-4a21-9c11-3aabec8df1e5.gif
diff --git a/images/9a38d876-2189-418c-9314-ae493a4cab61.PNG b/docs/images/9a38d876-2189-418c-9314-ae493a4cab61.PNG
similarity index 100%
rename from images/9a38d876-2189-418c-9314-ae493a4cab61.PNG
rename to docs/images/9a38d876-2189-418c-9314-ae493a4cab61.PNG
diff --git a/images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG b/docs/images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG
similarity index 100%
rename from images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG
rename to docs/images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG
diff --git a/images/9dc5cefe-083a-4807-bee6-473001f23db9.png b/docs/images/9dc5cefe-083a-4807-bee6-473001f23db9.png
similarity index 100%
rename from images/9dc5cefe-083a-4807-bee6-473001f23db9.png
rename to docs/images/9dc5cefe-083a-4807-bee6-473001f23db9.png
diff --git a/images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif b/docs/images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif
similarity index 100%
rename from images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif
rename to docs/images/9faa4fbc-5fd6-4960-ba25-8a8cc0195562.gif
diff --git a/images/ALMBuildDeployProcess.png b/docs/images/ALMBuildDeployProcess.png
similarity index 100%
rename from images/ALMBuildDeployProcess.png
rename to docs/images/ALMBuildDeployProcess.png
diff --git a/images/ALMChangeManagement.png b/docs/images/ALMChangeManagement.png
similarity index 100%
rename from images/ALMChangeManagement.png
rename to docs/images/ALMChangeManagement.png
diff --git a/images/ALMCodePromotion.png b/docs/images/ALMCodePromotion.png
similarity index 100%
rename from images/ALMCodePromotion.png
rename to docs/images/ALMCodePromotion.png
diff --git a/images/ALMDeveloperTesting.png b/docs/images/ALMDeveloperTesting.png
similarity index 100%
rename from images/ALMDeveloperTesting.png
rename to docs/images/ALMDeveloperTesting.png
diff --git a/images/ALMIntegrationTesting.png b/docs/images/ALMIntegrationTesting.png
similarity index 100%
rename from images/ALMIntegrationTesting.png
rename to docs/images/ALMIntegrationTesting.png
diff --git a/images/ALMIntegrationandUAT.png b/docs/images/ALMIntegrationandUAT.png
similarity index 100%
rename from images/ALMIntegrationandUAT.png
rename to docs/images/ALMIntegrationandUAT.png
diff --git a/images/ALMTestingTypes.png b/docs/images/ALMTestingTypes.png
similarity index 100%
rename from images/ALMTestingTypes.png
rename to docs/images/ALMTestingTypes.png
diff --git a/images/ALMUATTesting.png b/docs/images/ALMUATTesting.png
similarity index 100%
rename from images/ALMUATTesting.png
rename to docs/images/ALMUATTesting.png
diff --git a/images/ALMWithTFS.png b/docs/images/ALMWithTFS.png
similarity index 100%
rename from images/ALMWithTFS.png
rename to docs/images/ALMWithTFS.png
diff --git a/images/AppDevelopmentClientBuildComponents.png b/docs/images/AppDevelopmentClientBuildComponents.png
similarity index 100%
rename from images/AppDevelopmentClientBuildComponents.png
rename to docs/images/AppDevelopmentClientBuildComponents.png
diff --git a/images/AppDevelopmentEnvironment.png b/docs/images/AppDevelopmentEnvironment.png
similarity index 100%
rename from images/AppDevelopmentEnvironment.png
rename to docs/images/AppDevelopmentEnvironment.png
diff --git a/images/AppDevelopmentVirtualEnvironment.png b/docs/images/AppDevelopmentVirtualEnvironment.png
similarity index 100%
rename from images/AppDevelopmentVirtualEnvironment.png
rename to docs/images/AppDevelopmentVirtualEnvironment.png
diff --git a/images/AppForSharePointVSTemplate.PNG b/docs/images/AppForSharePointVSTemplate.PNG
similarity index 100%
rename from images/AppForSharePointVSTemplate.PNG
rename to docs/images/AppForSharePointVSTemplate.PNG
diff --git a/images/AppParts_ConceptualArchitecture.png b/docs/images/AppParts_ConceptualArchitecture.png
similarity index 100%
rename from images/AppParts_ConceptualArchitecture.png
rename to docs/images/AppParts_ConceptualArchitecture.png
diff --git a/images/AppParts_IFrameError.png b/docs/images/AppParts_IFrameError.png
similarity index 100%
rename from images/AppParts_IFrameError.png
rename to docs/images/AppParts_IFrameError.png
diff --git a/images/AppUXGuidelines_AppTemplate.png b/docs/images/AppUXGuidelines_AppTemplate.png
similarity index 100%
rename from images/AppUXGuidelines_AppTemplate.png
rename to docs/images/AppUXGuidelines_AppTemplate.png
diff --git a/images/AppUXGuidelines_ChromeControl.png b/docs/images/AppUXGuidelines_ChromeControl.png
similarity index 100%
rename from images/AppUXGuidelines_ChromeControl.png
rename to docs/images/AppUXGuidelines_ChromeControl.png
diff --git a/images/AppUXGuidelines_ECBcustomaction.png b/docs/images/AppUXGuidelines_ECBcustomaction.png
similarity index 100%
rename from images/AppUXGuidelines_ECBcustomaction.png
rename to docs/images/AppUXGuidelines_ECBcustomaction.png
diff --git a/images/AppUXGuidelines_QuickLaunchHeading.png b/docs/images/AppUXGuidelines_QuickLaunchHeading.png
similarity index 100%
rename from images/AppUXGuidelines_QuickLaunchHeading.png
rename to docs/images/AppUXGuidelines_QuickLaunchHeading.png
diff --git a/images/AppUXGuidelines_QuickLaunchLink.png b/docs/images/AppUXGuidelines_QuickLaunchLink.png
similarity index 100%
rename from images/AppUXGuidelines_QuickLaunchLink.png
rename to docs/images/AppUXGuidelines_QuickLaunchLink.png
diff --git a/images/AppUXGuidelines_QuickLaunchSelected.png b/docs/images/AppUXGuidelines_QuickLaunchSelected.png
similarity index 100%
rename from images/AppUXGuidelines_QuickLaunchSelected.png
rename to docs/images/AppUXGuidelines_QuickLaunchSelected.png
diff --git a/images/AppUXGuidelines_TopNav.png b/docs/images/AppUXGuidelines_TopNav.png
similarity index 100%
rename from images/AppUXGuidelines_TopNav.png
rename to docs/images/AppUXGuidelines_TopNav.png
diff --git a/images/AppUXGuidelines_TopNavSelected.png b/docs/images/AppUXGuidelines_TopNavSelected.png
similarity index 100%
rename from images/AppUXGuidelines_TopNavSelected.png
rename to docs/images/AppUXGuidelines_TopNavSelected.png
diff --git a/images/AppUXGuidelines_bgdisabled.png b/docs/images/AppUXGuidelines_bgdisabled.png
similarity index 100%
rename from images/AppUXGuidelines_bgdisabled.png
rename to docs/images/AppUXGuidelines_bgdisabled.png
diff --git a/images/AppUXGuidelines_body.png b/docs/images/AppUXGuidelines_body.png
similarity index 100%
rename from images/AppUXGuidelines_body.png
rename to docs/images/AppUXGuidelines_body.png
diff --git a/images/AppUXGuidelines_dragfiles.png b/docs/images/AppUXGuidelines_dragfiles.png
similarity index 100%
rename from images/AppUXGuidelines_dragfiles.png
rename to docs/images/AppUXGuidelines_dragfiles.png
diff --git a/images/AppUXGuidelines_h1.png b/docs/images/AppUXGuidelines_h1.png
similarity index 100%
rename from images/AppUXGuidelines_h1.png
rename to docs/images/AppUXGuidelines_h1.png
diff --git a/images/AppUXGuidelines_h2.png b/docs/images/AppUXGuidelines_h2.png
similarity index 100%
rename from images/AppUXGuidelines_h2.png
rename to docs/images/AppUXGuidelines_h2.png
diff --git a/images/AppUXGuidelines_h3.png b/docs/images/AppUXGuidelines_h3.png
similarity index 100%
rename from images/AppUXGuidelines_h3.png
rename to docs/images/AppUXGuidelines_h3.png
diff --git a/images/AppUXGuidelines_h4.png b/docs/images/AppUXGuidelines_h4.png
similarity index 100%
rename from images/AppUXGuidelines_h4.png
rename to docs/images/AppUXGuidelines_h4.png
diff --git a/images/AppUXGuidelines_hr.png b/docs/images/AppUXGuidelines_hr.png
similarity index 100%
rename from images/AppUXGuidelines_hr.png
rename to docs/images/AppUXGuidelines_hr.png
diff --git a/images/AppUXGuidelines_hyperlink.png b/docs/images/AppUXGuidelines_hyperlink.png
similarity index 100%
rename from images/AppUXGuidelines_hyperlink.png
rename to docs/images/AppUXGuidelines_hyperlink.png
diff --git a/images/AppUXGuidelines_md-bghoverable-normal.png b/docs/images/AppUXGuidelines_md-bghoverable-normal.png
similarity index 100%
rename from images/AppUXGuidelines_md-bghoverable-normal.png
rename to docs/images/AppUXGuidelines_md-bghoverable-normal.png
diff --git a/images/AppUXGuidelines_ms-accentlines.png b/docs/images/AppUXGuidelines_ms-accentlines.png
similarity index 100%
rename from images/AppUXGuidelines_ms-accentlines.png
rename to docs/images/AppUXGuidelines_ms-accentlines.png
diff --git a/images/AppUXGuidelines_ms-accenttext.png b/docs/images/AppUXGuidelines_ms-accenttext.png
similarity index 100%
rename from images/AppUXGuidelines_ms-accenttext.png
rename to docs/images/AppUXGuidelines_ms-accenttext.png
diff --git a/images/AppUXGuidelines_ms-attractmode.png b/docs/images/AppUXGuidelines_ms-attractmode.png
similarity index 100%
rename from images/AppUXGuidelines_ms-attractmode.png
rename to docs/images/AppUXGuidelines_ms-attractmode.png
diff --git a/images/AppUXGuidelines_ms-bgfooter.png b/docs/images/AppUXGuidelines_ms-bgfooter.png
similarity index 100%
rename from images/AppUXGuidelines_ms-bgfooter.png
rename to docs/images/AppUXGuidelines_ms-bgfooter.png
diff --git a/images/AppUXGuidelines_ms-bgheader.png b/docs/images/AppUXGuidelines_ms-bgheader.png
similarity index 100%
rename from images/AppUXGuidelines_ms-bgheader.png
rename to docs/images/AppUXGuidelines_ms-bgheader.png
diff --git a/images/AppUXGuidelines_ms-bghoverable-onhover.png b/docs/images/AppUXGuidelines_ms-bghoverable-onhover.png
similarity index 100%
rename from images/AppUXGuidelines_ms-bghoverable-onhover.png
rename to docs/images/AppUXGuidelines_ms-bghoverable-onhover.png
diff --git a/images/AppUXGuidelines_ms-bgoverlay.png b/docs/images/AppUXGuidelines_ms-bgoverlay.png
similarity index 100%
rename from images/AppUXGuidelines_ms-bgoverlay.png
rename to docs/images/AppUXGuidelines_ms-bgoverlay.png
diff --git a/images/AppUXGuidelines_ms-bgselected.png b/docs/images/AppUXGuidelines_ms-bgselected.png
similarity index 100%
rename from images/AppUXGuidelines_ms-bgselected.png
rename to docs/images/AppUXGuidelines_ms-bgselected.png
diff --git a/images/AppUXGuidelines_ms-calloutlink.png b/docs/images/AppUXGuidelines_ms-calloutlink.png
similarity index 100%
rename from images/AppUXGuidelines_ms-calloutlink.png
rename to docs/images/AppUXGuidelines_ms-calloutlink.png
diff --git a/images/AppUXGuidelines_ms-commandlink.png b/docs/images/AppUXGuidelines_ms-commandlink.png
similarity index 100%
rename from images/AppUXGuidelines_ms-commandlink.png
rename to docs/images/AppUXGuidelines_ms-commandlink.png
diff --git a/images/AppUXGuidelines_ms-core-pagetitle.png b/docs/images/AppUXGuidelines_ms-core-pagetitle.png
similarity index 100%
rename from images/AppUXGuidelines_ms-core-pagetitle.png
rename to docs/images/AppUXGuidelines_ms-core-pagetitle.png
diff --git a/images/AppUXGuidelines_ms-disabled.png b/docs/images/AppUXGuidelines_ms-disabled.png
similarity index 100%
rename from images/AppUXGuidelines_ms-disabled.png
rename to docs/images/AppUXGuidelines_ms-disabled.png
diff --git a/images/AppUXGuidelines_ms-disabledlines.png b/docs/images/AppUXGuidelines_ms-disabledlines.png
similarity index 100%
rename from images/AppUXGuidelines_ms-disabledlines.png
rename to docs/images/AppUXGuidelines_ms-disabledlines.png
diff --git a/images/AppUXGuidelines_ms-dlg-heading.png b/docs/images/AppUXGuidelines_ms-dlg-heading.png
similarity index 100%
rename from images/AppUXGuidelines_ms-dlg-heading.png
rename to docs/images/AppUXGuidelines_ms-dlg-heading.png
diff --git a/images/AppUXGuidelines_ms-emphasis.png b/docs/images/AppUXGuidelines_ms-emphasis.png
similarity index 100%
rename from images/AppUXGuidelines_ms-emphasis.png
rename to docs/images/AppUXGuidelines_ms-emphasis.png
diff --git a/images/AppUXGuidelines_ms-emphasisborder.png b/docs/images/AppUXGuidelines_ms-emphasisborder.png
similarity index 100%
rename from images/AppUXGuidelines_ms-emphasisborder.png
rename to docs/images/AppUXGuidelines_ms-emphasisborder.png
diff --git a/images/AppUXGuidelines_ms-emptymode.png b/docs/images/AppUXGuidelines_ms-emptymode.png
similarity index 100%
rename from images/AppUXGuidelines_ms-emptymode.png
rename to docs/images/AppUXGuidelines_ms-emptymode.png
diff --git a/images/AppUXGuidelines_ms-error.png b/docs/images/AppUXGuidelines_ms-error.png
similarity index 100%
rename from images/AppUXGuidelines_ms-error.png
rename to docs/images/AppUXGuidelines_ms-error.png
diff --git a/images/AppUXGuidelines_ms-helper.png b/docs/images/AppUXGuidelines_ms-helper.png
similarity index 100%
rename from images/AppUXGuidelines_ms-helper.png
rename to docs/images/AppUXGuidelines_ms-helper.png
diff --git a/images/AppUXGuidelines_ms-herocommandlink.png b/docs/images/AppUXGuidelines_ms-herocommandlink.png
similarity index 100%
rename from images/AppUXGuidelines_ms-herocommandlink.png
rename to docs/images/AppUXGuidelines_ms-herocommandlink.png
diff --git a/images/AppUXGuidelines_ms-lines.png b/docs/images/AppUXGuidelines_ms-lines.png
similarity index 100%
rename from images/AppUXGuidelines_ms-lines.png
rename to docs/images/AppUXGuidelines_ms-lines.png
diff --git a/images/AppUXGuidelines_ms-listlink.png b/docs/images/AppUXGuidelines_ms-listlink.png
similarity index 100%
rename from images/AppUXGuidelines_ms-listlink.png
rename to docs/images/AppUXGuidelines_ms-listlink.png
diff --git a/images/AppUXGuidelines_ms-metadata.png b/docs/images/AppUXGuidelines_ms-metadata.png
similarity index 100%
rename from images/AppUXGuidelines_ms-metadata.png
rename to docs/images/AppUXGuidelines_ms-metadata.png
diff --git a/images/AppUXGuidelines_ms-popupborder.png b/docs/images/AppUXGuidelines_ms-popupborder.png
similarity index 100%
rename from images/AppUXGuidelines_ms-popupborder.png
rename to docs/images/AppUXGuidelines_ms-popupborder.png
diff --git a/images/AppUXGuidelines_ms-secondarycommandlink.png b/docs/images/AppUXGuidelines_ms-secondarycommandlink.png
similarity index 100%
rename from images/AppUXGuidelines_ms-secondarycommandlink.png
rename to docs/images/AppUXGuidelines_ms-secondarycommandlink.png
diff --git a/images/AppUXGuidelines_ms-sidenav-selected.png b/docs/images/AppUXGuidelines_ms-sidenav-selected.png
similarity index 100%
rename from images/AppUXGuidelines_ms-sidenav-selected.png
rename to docs/images/AppUXGuidelines_ms-sidenav-selected.png
diff --git a/images/AppUXGuidelines_ms-sidenav.png b/docs/images/AppUXGuidelines_ms-sidenav.png
similarity index 100%
rename from images/AppUXGuidelines_ms-sidenav.png
rename to docs/images/AppUXGuidelines_ms-sidenav.png
diff --git a/images/AppUXGuidelines_ms-soften.png b/docs/images/AppUXGuidelines_ms-soften.png
similarity index 100%
rename from images/AppUXGuidelines_ms-soften.png
rename to docs/images/AppUXGuidelines_ms-soften.png
diff --git a/images/AppUXGuidelines_ms-stronglines.png b/docs/images/AppUXGuidelines_ms-stronglines.png
similarity index 100%
rename from images/AppUXGuidelines_ms-stronglines.png
rename to docs/images/AppUXGuidelines_ms-stronglines.png
diff --git a/images/AppUXGuidelines_ms-subtleemphasis.png b/docs/images/AppUXGuidelines_ms-subtleemphasis.png
similarity index 100%
rename from images/AppUXGuidelines_ms-subtleemphasis.png
rename to docs/images/AppUXGuidelines_ms-subtleemphasis.png
diff --git a/images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png b/docs/images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png
similarity index 100%
rename from images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png
rename to docs/images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png
diff --git a/images/AppUXGuidelines_ms-subtleemphasiscommand.png b/docs/images/AppUXGuidelines_ms-subtleemphasiscommand.png
similarity index 100%
rename from images/AppUXGuidelines_ms-subtleemphasiscommand.png
rename to docs/images/AppUXGuidelines_ms-subtleemphasiscommand.png
diff --git a/images/AppUXGuidelines_ms-subtlelines.png b/docs/images/AppUXGuidelines_ms-subtlelines.png
similarity index 100%
rename from images/AppUXGuidelines_ms-subtlelines.png
rename to docs/images/AppUXGuidelines_ms-subtlelines.png
diff --git a/images/AppUXGuidelines_ms-textlarge.png b/docs/images/AppUXGuidelines_ms-textlarge.png
similarity index 100%
rename from images/AppUXGuidelines_ms-textlarge.png
rename to docs/images/AppUXGuidelines_ms-textlarge.png
diff --git a/images/AppUXGuidelines_ms-textsmall.png b/docs/images/AppUXGuidelines_ms-textsmall.png
similarity index 100%
rename from images/AppUXGuidelines_ms-textsmall.png
rename to docs/images/AppUXGuidelines_ms-textsmall.png
diff --git a/images/AppUXGuidelines_ms-textxlarge.png b/docs/images/AppUXGuidelines_ms-textxlarge.png
similarity index 100%
rename from images/AppUXGuidelines_ms-textxlarge.png
rename to docs/images/AppUXGuidelines_ms-textxlarge.png
diff --git a/images/AppUXGuidelines_ms-topbar.png b/docs/images/AppUXGuidelines_ms-topbar.png
similarity index 100%
rename from images/AppUXGuidelines_ms-topbar.png
rename to docs/images/AppUXGuidelines_ms-topbar.png
diff --git a/images/AppUXGuidelines_ms-uppercase.png b/docs/images/AppUXGuidelines_ms-uppercase.png
similarity index 100%
rename from images/AppUXGuidelines_ms-uppercase.png
rename to docs/images/AppUXGuidelines_ms-uppercase.png
diff --git a/images/AppUXGuidelines_ms-webpart-titletext.png b/docs/images/AppUXGuidelines_ms-webpart-titletext.png
similarity index 100%
rename from images/AppUXGuidelines_ms-webpart-titletext.png
rename to docs/images/AppUXGuidelines_ms-webpart-titletext.png
diff --git a/images/AppUXGuidelines_mspivotlink.png b/docs/images/AppUXGuidelines_mspivotlink.png
similarity index 100%
rename from images/AppUXGuidelines_mspivotlink.png
rename to docs/images/AppUXGuidelines_mspivotlink.png
diff --git a/images/AppUXGuidelines_part.png b/docs/images/AppUXGuidelines_part.png
similarity index 100%
rename from images/AppUXGuidelines_part.png
rename to docs/images/AppUXGuidelines_part.png
diff --git a/images/AppUX_devhosted.png b/docs/images/AppUX_devhosted.png
similarity index 100%
rename from images/AppUX_devhosted.png
rename to docs/images/AppUX_devhosted.png
diff --git a/images/AppUX_hostweb.png b/docs/images/AppUX_hostweb.png
similarity index 100%
rename from images/AppUX_hostweb.png
rename to docs/images/AppUX_hostweb.png
diff --git a/images/AppUX_landscape.png b/docs/images/AppUX_landscape.png
similarity index 100%
rename from images/AppUX_landscape.png
rename to docs/images/AppUX_landscape.png
diff --git a/images/AppVSTemplateSolutionExplorer.jpg b/docs/images/AppVSTemplateSolutionExplorer.jpg
similarity index 100%
rename from images/AppVSTemplateSolutionExplorer.jpg
rename to docs/images/AppVSTemplateSolutionExplorer.jpg
diff --git a/images/Apps_NAPA_Run_Button.png b/docs/images/Apps_NAPA_Run_Button.png
similarity index 100%
rename from images/Apps_NAPA_Run_Button.png
rename to docs/images/Apps_NAPA_Run_Button.png
diff --git a/images/Apps_Napa_OpenInVS.png b/docs/images/Apps_Napa_OpenInVS.png
similarity index 100%
rename from images/Apps_Napa_OpenInVS.png
rename to docs/images/Apps_Napa_OpenInVS.png
diff --git a/images/BCSin2013FeatureSet.jpg b/docs/images/BCSin2013FeatureSet.jpg
similarity index 100%
rename from images/BCSin2013FeatureSet.jpg
rename to docs/images/BCSin2013FeatureSet.jpg
diff --git a/images/BasicAppPart_gallery.jpg b/docs/images/BasicAppPart_gallery.jpg
similarity index 100%
rename from images/BasicAppPart_gallery.jpg
rename to docs/images/BasicAppPart_gallery.jpg
diff --git a/images/BasicAppPart_result.png b/docs/images/BasicAppPart_result.png
similarity index 100%
rename from images/BasicAppPart_result.png
rename to docs/images/BasicAppPart_result.png
diff --git a/images/BrowserWarnings4SelfSignedCerts.png b/docs/images/BrowserWarnings4SelfSignedCerts.png
similarity index 100%
rename from images/BrowserWarnings4SelfSignedCerts.png
rename to docs/images/BrowserWarnings4SelfSignedCerts.png
diff --git a/images/Buildsearch-drivenmobileappspages.gif b/docs/images/Buildsearch-drivenmobileappspages.gif
similarity index 100%
rename from images/Buildsearch-drivenmobileappspages.gif
rename to docs/images/Buildsearch-drivenmobileappspages.gif
diff --git a/images/Buildsearch-drivenmobileappspages_item_details.gif b/docs/images/Buildsearch-drivenmobileappspages_item_details.gif
similarity index 100%
rename from images/Buildsearch-drivenmobileappspages_item_details.gif
rename to docs/images/Buildsearch-drivenmobileappspages_item_details.gif
diff --git a/images/CBAAddButton.PNG b/docs/images/CBAAddButton.PNG
similarity index 100%
rename from images/CBAAddButton.PNG
rename to docs/images/CBAAddButton.PNG
diff --git a/images/CBAAddDialog.PNG b/docs/images/CBAAddDialog.PNG
similarity index 100%
rename from images/CBAAddDialog.PNG
rename to docs/images/CBAAddDialog.PNG
diff --git a/images/CBAAddDoc.PNG b/docs/images/CBAAddDoc.PNG
similarity index 100%
rename from images/CBAAddDoc.PNG
rename to docs/images/CBAAddDoc.PNG
diff --git a/images/CBAAddTab.PNG b/docs/images/CBAAddTab.PNG
similarity index 100%
rename from images/CBAAddTab.PNG
rename to docs/images/CBAAddTab.PNG
diff --git a/images/CBADocLibrary.PNG b/docs/images/CBADocLibrary.PNG
similarity index 100%
rename from images/CBADocLibrary.PNG
rename to docs/images/CBADocLibrary.PNG
diff --git a/images/CBADocLibrary2.PNG b/docs/images/CBADocLibrary2.PNG
similarity index 100%
rename from images/CBADocLibrary2.PNG
rename to docs/images/CBADocLibrary2.PNG
diff --git a/images/CBARelationship.PNG b/docs/images/CBARelationship.PNG
similarity index 100%
rename from images/CBARelationship.PNG
rename to docs/images/CBARelationship.PNG
diff --git a/images/CBARelationship2.PNG b/docs/images/CBARelationship2.PNG
similarity index 100%
rename from images/CBARelationship2.PNG
rename to docs/images/CBARelationship2.PNG
diff --git a/images/CBAScreenSet.PNG b/docs/images/CBAScreenSet.PNG
similarity index 100%
rename from images/CBAScreenSet.PNG
rename to docs/images/CBAScreenSet.PNG
diff --git a/images/CBA_IM1.PNG b/docs/images/CBA_IM1.PNG
similarity index 100%
rename from images/CBA_IM1.PNG
rename to docs/images/CBA_IM1.PNG
diff --git a/images/CBA_IM4a.PNG b/docs/images/CBA_IM4a.PNG
similarity index 100%
rename from images/CBA_IM4a.PNG
rename to docs/images/CBA_IM4a.PNG
diff --git a/images/CBA_IM_10.PNG b/docs/images/CBA_IM_10.PNG
similarity index 100%
rename from images/CBA_IM_10.PNG
rename to docs/images/CBA_IM_10.PNG
diff --git a/images/CBA_IM_10a.PNG b/docs/images/CBA_IM_10a.PNG
similarity index 100%
rename from images/CBA_IM_10a.PNG
rename to docs/images/CBA_IM_10a.PNG
diff --git a/images/CBA_IM_11.PNG b/docs/images/CBA_IM_11.PNG
similarity index 100%
rename from images/CBA_IM_11.PNG
rename to docs/images/CBA_IM_11.PNG
diff --git a/images/CBA_IM_11a.PNG b/docs/images/CBA_IM_11a.PNG
similarity index 100%
rename from images/CBA_IM_11a.PNG
rename to docs/images/CBA_IM_11a.PNG
diff --git a/images/CBA_IM_11b.PNG b/docs/images/CBA_IM_11b.PNG
similarity index 100%
rename from images/CBA_IM_11b.PNG
rename to docs/images/CBA_IM_11b.PNG
diff --git a/images/CBA_IM_11c.PNG b/docs/images/CBA_IM_11c.PNG
similarity index 100%
rename from images/CBA_IM_11c.PNG
rename to docs/images/CBA_IM_11c.PNG
diff --git a/images/CBA_IM_12.PNG b/docs/images/CBA_IM_12.PNG
similarity index 100%
rename from images/CBA_IM_12.PNG
rename to docs/images/CBA_IM_12.PNG
diff --git a/images/CBA_IM_13.PNG b/docs/images/CBA_IM_13.PNG
similarity index 100%
rename from images/CBA_IM_13.PNG
rename to docs/images/CBA_IM_13.PNG
diff --git a/images/CBA_IM_14.PNG b/docs/images/CBA_IM_14.PNG
similarity index 100%
rename from images/CBA_IM_14.PNG
rename to docs/images/CBA_IM_14.PNG
diff --git a/images/CBA_IM_15.PNG b/docs/images/CBA_IM_15.PNG
similarity index 100%
rename from images/CBA_IM_15.PNG
rename to docs/images/CBA_IM_15.PNG
diff --git a/images/CBA_IM_16.PNG b/docs/images/CBA_IM_16.PNG
similarity index 100%
rename from images/CBA_IM_16.PNG
rename to docs/images/CBA_IM_16.PNG
diff --git a/images/CBA_IM_17.PNG b/docs/images/CBA_IM_17.PNG
similarity index 100%
rename from images/CBA_IM_17.PNG
rename to docs/images/CBA_IM_17.PNG
diff --git a/images/CBA_IM_18.PNG b/docs/images/CBA_IM_18.PNG
similarity index 100%
rename from images/CBA_IM_18.PNG
rename to docs/images/CBA_IM_18.PNG
diff --git a/images/CBA_IM_19.PNG b/docs/images/CBA_IM_19.PNG
similarity index 100%
rename from images/CBA_IM_19.PNG
rename to docs/images/CBA_IM_19.PNG
diff --git a/images/CBA_IM_2.PNG b/docs/images/CBA_IM_2.PNG
similarity index 100%
rename from images/CBA_IM_2.PNG
rename to docs/images/CBA_IM_2.PNG
diff --git a/images/CBA_IM_20.PNG b/docs/images/CBA_IM_20.PNG
similarity index 100%
rename from images/CBA_IM_20.PNG
rename to docs/images/CBA_IM_20.PNG
diff --git a/images/CBA_IM_20a.PNG b/docs/images/CBA_IM_20a.PNG
similarity index 100%
rename from images/CBA_IM_20a.PNG
rename to docs/images/CBA_IM_20a.PNG
diff --git a/images/CBA_IM_21.PNG b/docs/images/CBA_IM_21.PNG
similarity index 100%
rename from images/CBA_IM_21.PNG
rename to docs/images/CBA_IM_21.PNG
diff --git a/images/CBA_IM_22.PNG b/docs/images/CBA_IM_22.PNG
similarity index 100%
rename from images/CBA_IM_22.PNG
rename to docs/images/CBA_IM_22.PNG
diff --git a/images/CBA_IM_23.PNG b/docs/images/CBA_IM_23.PNG
similarity index 100%
rename from images/CBA_IM_23.PNG
rename to docs/images/CBA_IM_23.PNG
diff --git a/images/CBA_IM_24.PNG b/docs/images/CBA_IM_24.PNG
similarity index 100%
rename from images/CBA_IM_24.PNG
rename to docs/images/CBA_IM_24.PNG
diff --git a/images/CBA_IM_25.PNG b/docs/images/CBA_IM_25.PNG
similarity index 100%
rename from images/CBA_IM_25.PNG
rename to docs/images/CBA_IM_25.PNG
diff --git a/images/CBA_IM_26.PNG b/docs/images/CBA_IM_26.PNG
similarity index 100%
rename from images/CBA_IM_26.PNG
rename to docs/images/CBA_IM_26.PNG
diff --git a/images/CBA_IM_27.PNG b/docs/images/CBA_IM_27.PNG
similarity index 100%
rename from images/CBA_IM_27.PNG
rename to docs/images/CBA_IM_27.PNG
diff --git a/images/CBA_IM_28.PNG b/docs/images/CBA_IM_28.PNG
similarity index 100%
rename from images/CBA_IM_28.PNG
rename to docs/images/CBA_IM_28.PNG
diff --git a/images/CBA_IM_28a.PNG b/docs/images/CBA_IM_28a.PNG
similarity index 100%
rename from images/CBA_IM_28a.PNG
rename to docs/images/CBA_IM_28a.PNG
diff --git a/images/CBA_IM_29.PNG b/docs/images/CBA_IM_29.PNG
similarity index 100%
rename from images/CBA_IM_29.PNG
rename to docs/images/CBA_IM_29.PNG
diff --git a/images/CBA_IM_29a.PNG b/docs/images/CBA_IM_29a.PNG
similarity index 100%
rename from images/CBA_IM_29a.PNG
rename to docs/images/CBA_IM_29a.PNG
diff --git a/images/CBA_IM_2a.PNG b/docs/images/CBA_IM_2a.PNG
similarity index 100%
rename from images/CBA_IM_2a.PNG
rename to docs/images/CBA_IM_2a.PNG
diff --git a/images/CBA_IM_3.PNG b/docs/images/CBA_IM_3.PNG
similarity index 100%
rename from images/CBA_IM_3.PNG
rename to docs/images/CBA_IM_3.PNG
diff --git a/images/CBA_IM_30.PNG b/docs/images/CBA_IM_30.PNG
similarity index 100%
rename from images/CBA_IM_30.PNG
rename to docs/images/CBA_IM_30.PNG
diff --git a/images/CBA_IM_4.PNG b/docs/images/CBA_IM_4.PNG
similarity index 100%
rename from images/CBA_IM_4.PNG
rename to docs/images/CBA_IM_4.PNG
diff --git a/images/CBA_IM_5.PNG b/docs/images/CBA_IM_5.PNG
similarity index 100%
rename from images/CBA_IM_5.PNG
rename to docs/images/CBA_IM_5.PNG
diff --git a/images/CBA_IM_5a.PNG b/docs/images/CBA_IM_5a.PNG
similarity index 100%
rename from images/CBA_IM_5a.PNG
rename to docs/images/CBA_IM_5a.PNG
diff --git a/images/CBA_IM_6.PNG b/docs/images/CBA_IM_6.PNG
similarity index 100%
rename from images/CBA_IM_6.PNG
rename to docs/images/CBA_IM_6.PNG
diff --git a/images/CBA_IM_7.PNG b/docs/images/CBA_IM_7.PNG
similarity index 100%
rename from images/CBA_IM_7.PNG
rename to docs/images/CBA_IM_7.PNG
diff --git a/images/CBA_IM_8.PNG b/docs/images/CBA_IM_8.PNG
similarity index 100%
rename from images/CBA_IM_8.PNG
rename to docs/images/CBA_IM_8.PNG
diff --git a/images/CBA_IM_8a.PNG b/docs/images/CBA_IM_8a.PNG
similarity index 100%
rename from images/CBA_IM_8a.PNG
rename to docs/images/CBA_IM_8a.PNG
diff --git a/images/CBA_IM_8b.PNG b/docs/images/CBA_IM_8b.PNG
similarity index 100%
rename from images/CBA_IM_8b.PNG
rename to docs/images/CBA_IM_8b.PNG
diff --git a/images/CBA_IM_8c.PNG b/docs/images/CBA_IM_8c.PNG
similarity index 100%
rename from images/CBA_IM_8c.PNG
rename to docs/images/CBA_IM_8c.PNG
diff --git a/images/CBA_IM_8d.PNG b/docs/images/CBA_IM_8d.PNG
similarity index 100%
rename from images/CBA_IM_8d.PNG
rename to docs/images/CBA_IM_8d.PNG
diff --git a/images/CBA_IM_9.PNG b/docs/images/CBA_IM_9.PNG
similarity index 100%
rename from images/CBA_IM_9.PNG
rename to docs/images/CBA_IM_9.PNG
diff --git a/images/CBA_IM_9a.PNG b/docs/images/CBA_IM_9a.PNG
similarity index 100%
rename from images/CBA_IM_9a.PNG
rename to docs/images/CBA_IM_9a.PNG
diff --git a/images/CBAaction.PNG b/docs/images/CBAaction.PNG
similarity index 100%
rename from images/CBAaction.PNG
rename to docs/images/CBAaction.PNG
diff --git a/images/CBAadd.PNG b/docs/images/CBAadd.PNG
similarity index 100%
rename from images/CBAadd.PNG
rename to docs/images/CBAadd.PNG
diff --git a/images/CBAentity.PNG b/docs/images/CBAentity.PNG
similarity index 100%
rename from images/CBAentity.PNG
rename to docs/images/CBAentity.PNG
diff --git a/images/CBAnewsfeed.PNG b/docs/images/CBAnewsfeed.PNG
similarity index 100%
rename from images/CBAnewsfeed.PNG
rename to docs/images/CBAnewsfeed.PNG
diff --git a/images/CBAproperty.PNG b/docs/images/CBAproperty.PNG
similarity index 100%
rename from images/CBAproperty.PNG
rename to docs/images/CBAproperty.PNG
diff --git a/images/CBAscreen.PNG b/docs/images/CBAscreen.PNG
similarity index 100%
rename from images/CBAscreen.PNG
rename to docs/images/CBAscreen.PNG
diff --git a/images/CBAsocial.PNG b/docs/images/CBAsocial.PNG
similarity index 100%
rename from images/CBAsocial.PNG
rename to docs/images/CBAsocial.PNG
diff --git a/images/CBAtemplate.PNG b/docs/images/CBAtemplate.PNG
similarity index 100%
rename from images/CBAtemplate.PNG
rename to docs/images/CBAtemplate.PNG
diff --git a/images/CFW.gif b/docs/images/CFW.gif
similarity index 100%
rename from images/CFW.gif
rename to docs/images/CFW.gif
diff --git a/images/CSRFieldType_addcolumn.png b/docs/images/CSRFieldType_addcolumn.png
similarity index 100%
rename from images/CSRFieldType_addcolumn.png
rename to docs/images/CSRFieldType_addcolumn.png
diff --git a/images/CSRFieldType_result.png b/docs/images/CSRFieldType_result.png
similarity index 100%
rename from images/CSRFieldType_result.png
rename to docs/images/CSRFieldType_result.png
diff --git a/images/CSRListView_result.png b/docs/images/CSRListView_result.png
similarity index 100%
rename from images/CSRListView_result.png
rename to docs/images/CSRListView_result.png
diff --git a/images/Caution.gif b/docs/images/Caution.gif
similarity index 100%
rename from images/Caution.gif
rename to docs/images/Caution.gif
diff --git a/images/ChromControl_stylesheet.png b/docs/images/ChromControl_stylesheet.png
similarity index 100%
rename from images/ChromControl_stylesheet.png
rename to docs/images/ChromControl_stylesheet.png
diff --git a/images/ChromeControl_manifest.PNG b/docs/images/ChromeControl_manifest.PNG
similarity index 100%
rename from images/ChromeControl_manifest.PNG
rename to docs/images/ChromeControl_manifest.PNG
diff --git a/images/ChromeControl_result.png b/docs/images/ChromeControl_result.png
similarity index 100%
rename from images/ChromeControl_result.png
rename to docs/images/ChromeControl_result.png
diff --git a/images/CloudBusinessApptemplate.PNG b/docs/images/CloudBusinessApptemplate.PNG
similarity index 100%
rename from images/CloudBusinessApptemplate.PNG
rename to docs/images/CloudBusinessApptemplate.PNG
diff --git a/images/ConvertAuto2ProviderFig10.jpg b/docs/images/ConvertAuto2ProviderFig10.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig10.jpg
rename to docs/images/ConvertAuto2ProviderFig10.jpg
diff --git a/images/ConvertAuto2ProviderFig12.jpg b/docs/images/ConvertAuto2ProviderFig12.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig12.jpg
rename to docs/images/ConvertAuto2ProviderFig12.jpg
diff --git a/images/ConvertAuto2ProviderFig18.png b/docs/images/ConvertAuto2ProviderFig18.png
similarity index 100%
rename from images/ConvertAuto2ProviderFig18.png
rename to docs/images/ConvertAuto2ProviderFig18.png
diff --git a/images/ConvertAuto2ProviderFig20.jpg b/docs/images/ConvertAuto2ProviderFig20.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig20.jpg
rename to docs/images/ConvertAuto2ProviderFig20.jpg
diff --git a/images/ConvertAuto2ProviderFig21.jpg b/docs/images/ConvertAuto2ProviderFig21.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig21.jpg
rename to docs/images/ConvertAuto2ProviderFig21.jpg
diff --git a/images/ConvertAuto2ProviderFig22.jpg b/docs/images/ConvertAuto2ProviderFig22.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig22.jpg
rename to docs/images/ConvertAuto2ProviderFig22.jpg
diff --git a/images/ConvertAuto2ProviderFig3.jpg b/docs/images/ConvertAuto2ProviderFig3.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig3.jpg
rename to docs/images/ConvertAuto2ProviderFig3.jpg
diff --git a/images/ConvertAuto2ProviderFig4.jpg b/docs/images/ConvertAuto2ProviderFig4.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig4.jpg
rename to docs/images/ConvertAuto2ProviderFig4.jpg
diff --git a/images/ConvertAuto2ProviderFig5.jpg b/docs/images/ConvertAuto2ProviderFig5.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig5.jpg
rename to docs/images/ConvertAuto2ProviderFig5.jpg
diff --git a/images/ConvertAuto2ProviderFig6.jpg b/docs/images/ConvertAuto2ProviderFig6.jpg
similarity index 100%
rename from images/ConvertAuto2ProviderFig6.jpg
rename to docs/images/ConvertAuto2ProviderFig6.jpg
diff --git a/images/ConvertAuto2Providerfig11.jpg b/docs/images/ConvertAuto2Providerfig11.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig11.jpg
rename to docs/images/ConvertAuto2Providerfig11.jpg
diff --git a/images/ConvertAuto2Providerfig13.jpg b/docs/images/ConvertAuto2Providerfig13.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig13.jpg
rename to docs/images/ConvertAuto2Providerfig13.jpg
diff --git a/images/ConvertAuto2Providerfig14.jpg b/docs/images/ConvertAuto2Providerfig14.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig14.jpg
rename to docs/images/ConvertAuto2Providerfig14.jpg
diff --git a/images/ConvertAuto2Providerfig17.jpg b/docs/images/ConvertAuto2Providerfig17.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig17.jpg
rename to docs/images/ConvertAuto2Providerfig17.jpg
diff --git a/images/ConvertAuto2Providerfig7.jpg b/docs/images/ConvertAuto2Providerfig7.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig7.jpg
rename to docs/images/ConvertAuto2Providerfig7.jpg
diff --git a/images/ConvertAuto2Providerfig8.jpg b/docs/images/ConvertAuto2Providerfig8.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig8.jpg
rename to docs/images/ConvertAuto2Providerfig8.jpg
diff --git a/images/ConvertAuto2Providerfig9.jpg b/docs/images/ConvertAuto2Providerfig9.jpg
similarity index 100%
rename from images/ConvertAuto2Providerfig9.jpg
rename to docs/images/ConvertAuto2Providerfig9.jpg
diff --git a/images/CreatSharePoint2013WorkflowsFig4.png b/docs/images/CreatSharePoint2013WorkflowsFig4.png
similarity index 100%
rename from images/CreatSharePoint2013WorkflowsFig4.png
rename to docs/images/CreatSharePoint2013WorkflowsFig4.png
diff --git a/images/CreateSharePoint2013Workflows.png b/docs/images/CreateSharePoint2013Workflows.png
similarity index 100%
rename from images/CreateSharePoint2013Workflows.png
rename to docs/images/CreateSharePoint2013Workflows.png
diff --git a/images/CreateSharePoint2013WorkflowsFig2.png b/docs/images/CreateSharePoint2013WorkflowsFig2.png
similarity index 100%
rename from images/CreateSharePoint2013WorkflowsFig2.png
rename to docs/images/CreateSharePoint2013WorkflowsFig2.png
diff --git a/images/CreateSharePoint2013WorkflowsFig5.png b/docs/images/CreateSharePoint2013WorkflowsFig5.png
similarity index 100%
rename from images/CreateSharePoint2013WorkflowsFig5.png
rename to docs/images/CreateSharePoint2013WorkflowsFig5.png
diff --git a/images/CreateSharePoint2013WorkflowsFig7.png b/docs/images/CreateSharePoint2013WorkflowsFig7.png
similarity index 100%
rename from images/CreateSharePoint2013WorkflowsFig7.png
rename to docs/images/CreateSharePoint2013WorkflowsFig7.png
diff --git a/images/CreateSharePoint2013WorkflowsFig8.png b/docs/images/CreateSharePoint2013WorkflowsFig8.png
similarity index 100%
rename from images/CreateSharePoint2013WorkflowsFig8.png
rename to docs/images/CreateSharePoint2013WorkflowsFig8.png
diff --git a/images/CrossDomainReadItemsResult.png b/docs/images/CrossDomainReadItemsResult.png
similarity index 100%
rename from images/CrossDomainReadItemsResult.png
rename to docs/images/CrossDomainReadItemsResult.png
diff --git a/images/Crosszone_loaderror.png b/docs/images/Crosszone_loaderror.png
similarity index 100%
rename from images/Crosszone_loaderror.png
rename to docs/images/Crosszone_loaderror.png
diff --git a/images/Crosszone_loadsuccess.png b/docs/images/Crosszone_loadsuccess.png
similarity index 100%
rename from images/Crosszone_loadsuccess.png
rename to docs/images/Crosszone_loadsuccess.png
diff --git a/images/CustomActions_target.png b/docs/images/CustomActions_target.png
similarity index 100%
rename from images/CustomActions_target.png
rename to docs/images/CustomActions_target.png
diff --git a/images/CustomProxy_result.jpg b/docs/images/CustomProxy_result.jpg
similarity index 100%
rename from images/CustomProxy_result.jpg
rename to docs/images/CustomProxy_result.jpg
diff --git a/images/DataAccess_SharePointData.png b/docs/images/DataAccess_SharePointData.png
similarity index 100%
rename from images/DataAccess_SharePointData.png
rename to docs/images/DataAccess_SharePointData.png
diff --git a/images/DesktopListView_basic.png b/docs/images/DesktopListView_basic.png
similarity index 100%
rename from images/DesktopListView_basic.png
rename to docs/images/DesktopListView_basic.png
diff --git a/images/ExtEvtsAndAlerts_Figure2.jpg b/docs/images/ExtEvtsAndAlerts_Figure2.jpg
similarity index 100%
rename from images/ExtEvtsAndAlerts_Figure2.jpg
rename to docs/images/ExtEvtsAndAlerts_Figure2.jpg
diff --git a/images/ExtEvtsAndAlerts_Figure3.jpg b/docs/images/ExtEvtsAndAlerts_Figure3.jpg
similarity index 100%
rename from images/ExtEvtsAndAlerts_Figure3.jpg
rename to docs/images/ExtEvtsAndAlerts_Figure3.jpg
diff --git a/images/ExtEvtsAndAlrts_Figure1.jpg b/docs/images/ExtEvtsAndAlrts_Figure1.jpg
similarity index 100%
rename from images/ExtEvtsAndAlrts_Figure1.jpg
rename to docs/images/ExtEvtsAndAlrts_Figure1.jpg
diff --git a/images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg b/docs/images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg
similarity index 100%
rename from images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg
rename to docs/images/ExternalEventsAndAlerts_UnsubscribeFlow.jpg
diff --git a/images/GitHub-Mark-64px.png b/docs/images/GitHub-Mark-64px.png
similarity index 100%
rename from images/GitHub-Mark-64px.png
rename to docs/images/GitHub-Mark-64px.png
diff --git a/images/HostWebAndAppWeb.png b/docs/images/HostWebAndAppWeb.png
similarity index 100%
rename from images/HostWebAndAppWeb.png
rename to docs/images/HostWebAndAppWeb.png
diff --git a/images/ImgRendition_crop.PNG b/docs/images/ImgRendition_crop.PNG
similarity index 100%
rename from images/ImgRendition_crop.PNG
rename to docs/images/ImgRendition_crop.PNG
diff --git a/images/ImgRendition_orig.PNG b/docs/images/ImgRendition_orig.PNG
similarity index 100%
rename from images/ImgRendition_orig.PNG
rename to docs/images/ImgRendition_orig.PNG
diff --git a/images/LastChild.gif b/docs/images/LastChild.gif
similarity index 100%
rename from images/LastChild.gif
rename to docs/images/LastChild.gif
diff --git a/images/LocSPApp_AppwebList.png b/docs/images/LocSPApp_AppwebList.png
similarity index 100%
rename from images/LocSPApp_AppwebList.png
rename to docs/images/LocSPApp_AppwebList.png
diff --git a/images/LocSPApp_AppwebPage.png b/docs/images/LocSPApp_AppwebPage.png
similarity index 100%
rename from images/LocSPApp_AppwebPage.png
rename to docs/images/LocSPApp_AppwebPage.png
diff --git a/images/LocSPApp_TestCreatesite.png b/docs/images/LocSPApp_TestCreatesite.png
similarity index 100%
rename from images/LocSPApp_TestCreatesite.png
rename to docs/images/LocSPApp_TestCreatesite.png
diff --git a/images/MDS_GeneralFlow.png b/docs/images/MDS_GeneralFlow.png
similarity index 100%
rename from images/MDS_GeneralFlow.png
rename to docs/images/MDS_GeneralFlow.png
diff --git a/images/MDS_SeattleMaster.png b/docs/images/MDS_SeattleMaster.png
similarity index 100%
rename from images/MDS_SeattleMaster.png
rename to docs/images/MDS_SeattleMaster.png
diff --git a/images/MDS_UpdateSections.png b/docs/images/MDS_UpdateSections.png
similarity index 100%
rename from images/MDS_UpdateSections.png
rename to docs/images/MDS_UpdateSections.png
diff --git a/images/NuGet.PNG b/docs/images/NuGet.PNG
similarity index 100%
rename from images/NuGet.PNG
rename to docs/images/NuGet.PNG
diff --git a/images/Octocat.png b/docs/images/Octocat.png
similarity index 100%
rename from images/Octocat.png
rename to docs/images/Octocat.png
diff --git a/images/Office365AppDevelpment.png b/docs/images/Office365AppDevelpment.png
similarity index 100%
rename from images/Office365AppDevelpment.png
rename to docs/images/Office365AppDevelpment.png
diff --git a/images/OfficeWebWidgetsOverview_demo.png b/docs/images/OfficeWebWidgetsOverview_demo.png
similarity index 100%
rename from images/OfficeWebWidgetsOverview_demo.png
rename to docs/images/OfficeWebWidgetsOverview_demo.png
diff --git a/images/OnPremDevSites.png b/docs/images/OnPremDevSites.png
similarity index 100%
rename from images/OnPremDevSites.png
rename to docs/images/OnPremDevSites.png
diff --git a/images/OptimizePage_Fig01_MDSArchitecture.png b/docs/images/OptimizePage_Fig01_MDSArchitecture.png
similarity index 100%
rename from images/OptimizePage_Fig01_MDSArchitecture.png
rename to docs/images/OptimizePage_Fig01_MDSArchitecture.png
diff --git a/images/OptimizePage_Fig02_PageStructure.png b/docs/images/OptimizePage_Fig02_PageStructure.png
similarity index 100%
rename from images/OptimizePage_Fig02_PageStructure.png
rename to docs/images/OptimizePage_Fig02_PageStructure.png
diff --git a/images/OptimizePage_Fig03_SingleImage.png b/docs/images/OptimizePage_Fig03_SingleImage.png
similarity index 100%
rename from images/OptimizePage_Fig03_SingleImage.png
rename to docs/images/OptimizePage_Fig03_SingleImage.png
diff --git a/images/OptimizePage_Fig04_ImageTable.png b/docs/images/OptimizePage_Fig04_ImageTable.png
similarity index 100%
rename from images/OptimizePage_Fig04_ImageTable.png
rename to docs/images/OptimizePage_Fig04_ImageTable.png
diff --git a/images/OptimizePage_Fig05_DevDashboard.png b/docs/images/OptimizePage_Fig05_DevDashboard.png
similarity index 100%
rename from images/OptimizePage_Fig05_DevDashboard.png
rename to docs/images/OptimizePage_Fig05_DevDashboard.png
diff --git a/images/PeoplePicker_HTMLHierarchy.png b/docs/images/PeoplePicker_HTMLHierarchy.png
similarity index 100%
rename from images/PeoplePicker_HTMLHierarchy.png
rename to docs/images/PeoplePicker_HTMLHierarchy.png
diff --git a/images/PeoplePicker_basic.png b/docs/images/PeoplePicker_basic.png
similarity index 100%
rename from images/PeoplePicker_basic.png
rename to docs/images/PeoplePicker_basic.png
diff --git a/images/ProviderHostedAppBuildComponents.png b/docs/images/ProviderHostedAppBuildComponents.png
similarity index 100%
rename from images/ProviderHostedAppBuildComponents.png
rename to docs/images/ProviderHostedAppBuildComponents.png
diff --git a/images/REST_OverallSyntax.png b/docs/images/REST_OverallSyntax.png
similarity index 100%
rename from images/REST_OverallSyntax.png
rename to docs/images/REST_OverallSyntax.png
diff --git a/images/REST_RESTStructure.png b/docs/images/REST_RESTStructure.png
similarity index 100%
rename from images/REST_RESTStructure.png
rename to docs/images/REST_RESTStructure.png
diff --git a/images/REST_parameterAliasSyntax.png b/docs/images/REST_parameterAliasSyntax.png
similarity index 100%
rename from images/REST_parameterAliasSyntax.png
rename to docs/images/REST_parameterAliasSyntax.png
diff --git a/images/REST_parameterDictionarySyntax.png b/docs/images/REST_parameterDictionarySyntax.png
similarity index 100%
rename from images/REST_parameterDictionarySyntax.png
rename to docs/images/REST_parameterDictionarySyntax.png
diff --git a/images/REST_parameterQuerySyntax.png b/docs/images/REST_parameterQuerySyntax.png
similarity index 100%
rename from images/REST_parameterQuerySyntax.png
rename to docs/images/REST_parameterQuerySyntax.png
diff --git a/images/REST_parameterSyntax.png b/docs/images/REST_parameterSyntax.png
similarity index 100%
rename from images/REST_parameterSyntax.png
rename to docs/images/REST_parameterSyntax.png
diff --git a/images/REST_queryOptionSyntax.png b/docs/images/REST_queryOptionSyntax.png
similarity index 100%
rename from images/REST_queryOptionSyntax.png
rename to docs/images/REST_queryOptionSyntax.png
diff --git a/docs/images/RegrantPermissionsToAnApp.png b/docs/images/RegrantPermissionsToAnApp.png
new file mode 100644
index 0000000000000000000000000000000000000000..e053bf470524df28e2d29dec7456cc0869914e71
GIT binary patch
literal 47344
zcmbTd1zVd<*ENhg6xTwbxVyW%yHniVwRkD+#WlDTw_*i~ySqzp_riDfx}WzCd^zAC
z31^bY%<R3_UTaO1ijp)c5+M=<1O%$AjD#8l1T+@}1SBp36z~i`Nh%`n2hvSVS`4CQ
z;v*P%0AnSpC<*~l7mxh<1r~UW=q#h_1_6QA_wN^S(5cKE0-`lsRzg(6+vqe0Rs=_$
zC_<TfeZ8=7iFhgC?EL?3j-qvvq8KXe{Ai^&?`eh@IKVBi`|x}qV|f|)S!Tabn(^Qx
zK7(e8e*K(e!GRlEe;BPGSlP7uI}Ppj?ZNtw!3Zl}-SNcUHSY6ieM8>#EpLh$QwGv{
z?laLjb&TLgIjo;F(wH(421ToSEq`;j+?dsD45;>%3TM)q7X1W4zn)I5%0E-aK8<6`
z&CBz(DLC27>n56p93s7QvzijVWPQ-CAz2&?bkHxY#py;i8}VI1%Apo6A@Emytxrj+
z_K53LAZn%lL1nHUN1^gsuhA}e=Svb8wD)D^a6q}*qj@WGvSP3GQqukVudmDq7Lw>N
zq6v9BS*fTYud+w(JNW@GCR0b|1%Jl`5A$ciC_C@3eZlO`nUHV@+YRb_lws-0Yr~;3
zI!eW1EzC84PluwyFJnj%LP)!Nm>UZ{I#Qk3|J-GyGTbfWln51ogH}`^&FPw?32T03
zv3LXx;Z<966yi7-|FvA*-0)6%wV=;TP7ds^l3V(I4?i{St_RYpNtxwH8T}+uHtCuB
zz`;iK!atx~LohcNXmv4jJE3hYWsEHx^?X_8x?cs8%TBVd{wgujuXq>NDM!%4{CKki
z|1G6`w|dp_uH%yC>Sm{OIwR{QIen2m%axf?Q^_m@`-RVSy!AbMq1h{SXf6d=&Hu}E
zm_R{XIW$<Y4frOnw1Gy2itXq&LodH_lW91~ZS@g($8fxMZ+Y?-+*A-pIO$h;gyJ#s
z5M>U7R`Ou$MQRopZNSdgntCE3VK?On>UJJnaM=Y-42+h-@}g1qS*k-gb#--@+La4$
zb>C%sEKhxtvKh2k2{ym0l`m+zO}$L^Ss#O}12zs}6-s72nVf8?OdJA#Q0(~|$xtAj
z6~irDB<-h%vUwZ3mwv}tX>uU`&?ys;Ok)v5_nSj6lQoaGEqMHU$5jT~c#C|VSas!Y
zmGPvcalzB0CE37-N7=#?9s9Jz#KiD6*yO)HU&PU2p4MMmC6X(x8eMhPMiT4abQul>
z<R`?U?un*tJir8CFfDk(aYAp3DhM6zTSfN9pNstY5S3m3D@c(-b-N}$!W(+%l{q?8
zWQr~Ak$AO&?Vj)_TZtT{@;TR5=P!_IWn^kH8Hqb6p}h!bNS>~qGqa0D*}zVF!xm<m
zhG@&AdI=3M@nJOylFoyqnGS?Zux71eB?Q4y5blSOzOz6wL)#PED=I3|@`sQP<?Z;n
zQX6|Sm}0LO^LABECKyXd7ug|AsQ{OvJW7!wTx*LAg!)4+NFyZS`I7_RjwoLO_>!XN
zFto1!|L*M>f0_C!da_Vc#K4hRTkDh@p*X`n^KUdVs!)`KA*Am}p>U|a&hNb?u~|JI
z(b0d}{4HrdTg}AJO0dF!5&e!$GYyPGyG*t6Pa}91${1cLN5JFcpc<8s3!l>$+XGD$
zz4%)&CaP#c&^J2G$`oc}BL-Z0?C)fK5h^u6G)aC)v6f*Kshn4%f_dV6HF|u4f4q6}
zM~iImJ9Heu0bYFsyqXq918IJ}!%I0&FkpKpoIw?LUr$DcawZ~{NG+`v>(i(A%Wd(I
z>xO=*!CYRygU8|B3$YDVrJ;8W<xj$f_1>~J@iUbRRfJroOVwE|TuvJbIl#Qpn)-j9
z-m@iE1c7Kd2VPWcH1&u*<cBV#%hlp?SnijTt?E?kx<2@unVObig~NpQvaqogG8kJ;
zo(o2&GbqW*7Mu!CRP(psG8z@n9v!(qzx;eip}!95k2~YHU91tbJjG|xE>ro^e}rMB
zoTsQfNRWdNf-QN(w=T^&d)CuYh60-<TY5TxRVT(@kn2%PcaTE-gdvjO|EIrV-qwoS
zY6R@}k<VGCCg}qq&$s#@QZh0!HnyaRe803iY@~3N8L^G<6lX?^OFogB1nmlysL|an
zpBpN6`i3xlM0t7nRth@0k&zKPURqv0E<I!AZu^XS6e@A1WUrIuv$YI2^PfPpZYh>g
zGn}ZV4Ok||C8{Q}TaH^#|ANgLIA3TY0^^gAoF5(G6B85TeX_DQKi%GjT#+xD{)Os`
zEQ^GKGBz~!v!%()-4$js;n%rg`vw2c_`$=(baDjrOSYbgiHZJ?Rso+8u1lXJ3dx3)
zWf~i-CWQj7-NE&s6v4=RZc%=(GY0)Gdw&CeIlYk)3;GNO%e=sV<GHfFeK*n0^0|ud
z`}7fAANG--gt~-?79BZSSn`B}gdzvGS$)#D(wK9*e>OMga`+^v6`am=BGXRi3I=-a
z9VODuSNuZtAKiC89Lo}y@_OC_7dIAbG3r<A)S2E;Rh-yf7Z2Yn-P4tiEcD)YP5x!G
z7>&Va{j8s|-evYOT_i0XAw`%;xY6!nw>Ol?X*Vz6v7@1<wKCN!K5T~(2J<g4f{;H(
zN4(OVt+pJxw&e%@?(3taCPcMu(zMe;JrXuqsM3XM-csBmqDrRSLLM6*heyF@aXV0u
zZQk4Ni^QT<4nrpL;cWN3AvB=GM%p#o9aJXVERv3&uhf>7l7NGSuhY>`&(L5n?DqM)
za%bmvf7<3fytCK1S9VF`965<{(Xqjp+2ri*jBOEJNM0!WE++WJ)L^Hd7OTVK1g;?X
zKwd#%?<X&MbV2U+5~A75-5EUXa=itzH=6G!b9-xnfR)>G!H#$$_H%7M1t5^o_ZCH?
zBCw%u4kk}lKqnPAm1#`+6<X!JlAAKZ<bt~sXZ)qgIcQM`iS+whWg2uu+>Y69u;WYp
zt+KOJ#mfs5TufYOC|d<Kvn9pku}YOH<-e1umGKoSQsCg>XKilJI+|-Ye+I6`Impt=
zD(4BoJ`9z~;70DBDsa5q9j}~>Ewl4(L`~^6+sbD8_!|w+Py!2$7NQK&ns?I4b7wwN
z)vHJuvA8ZfDua0c>azQXSkS-GbpCt8;TV<Rzp^}J3`t3-#xqxG>~xbhjsyx>Gdb*f
z_zRvbrS7N3CnQL7W-J)Z=qV@y|FE}=^U9Pe`ci-WBO^?=bQVl>oE!(SoiXKyO-DJ+
zy;AQpiaV~)QMKv3oMgfHPL92_JZohP^Xq87R6E{Cu=#A`;ARS*0<YDsNe@~)G+Q1K
zpCLl22znnLJcJzDJ5|v{1xI!F>sVJ0Lwx7?{yZxwEh#Am)#krZLIb0;o+7w?`}-U{
zV9MgO(uH`m++nr*C$?c=xfq`GVrh_hP&CBa@6)Rb9q3*D-FCjxhI6ja8cqrh(h2(X
z>~!7D*~10r7;zu7ExvX#F+f_2Nw>`vJQC1x&&$iV-W5Rf+OSlW&_cG?)YGx$rCFh&
zS~-V8Ma~~8r>5YJ5;=@<ge)-XOGQPQ6bBLA8*)U09P$qixTqA8b&re_aXT4w6lmJb
zCe3<YtSE9xfKR}}-j@(451kjnLD$)*RT||QZS@L83wum5$e$IesWL~s4K}99rJ;@B
zzCPU!&zeRpb*AuVhamTY8l`QRqB|Ukr{&U9bDMmiSsAy0-OR+q)Qr}=;JMIz-yHEL
zB8T4#PMU{u3)%BxnV1k0=^%&S^V-MXPTww8t8d>KkI4vu%sO?2ax|^cUY29v?r0gh
z5X~10=0LZ>QnNw_@mDYbPy$8YkZ7h8j6p!|+Z^l?e7^s|V`d6n3)d%&0zbGvnzq>$
z(Bbwl;d14|ZaD$b1QVBQA?P;v*3sJj<A+Ma-WcOpPIh(=X{sC^v#$T(i_*))8CEi8
zi^D41o9Mh|l}h4mTfm?vRp@e&SG?|xWooSkiNS{SuTN7!5I$+e{%zL>2M6fbKYj0x
z&8Xu=t?jw8<~;L}Q*HM{e2_~fGd6;(-<fhcZcmr7)-o6la@YNuPuFIOwBx_;(<$Zf
zaZ<DVtK(1nTZKeJ)UW-8MBzg_1JQO170W++A09Ai5N1mhPgXkZ2Ch?nkz-gzcetOp
z?qB1K#F1{o;H`_G?>PlmTgzaG6{sWxWQIe9NhvXpM=Mn(j})iC{+pfebinL<mgtK>
zU0++H8D*X=ltk9o*B`ltWQu>$9i;iU1+Ybb7GXVwb+1lGkxHVT9!UW2dKD#sr4aC0
zK4Iqj6G;w7hOeH}1E~5V4gEDa067wV{lgvqUFD{`hnL7uRQKKIqEw@^IC=E;Pu_zw
z87vT%A$zd@FJ;~*OGrq`Q1Tpq{5PnC&ELWl(@;=QTGhIex~@xI0e(k*riQZy01!~j
z<@0$fd;$uRPOJ4ccQb@ux69v`g!q#!av+d^!G3;Ekcj>k!{c#0XZOBXJb%%)8EeO#
zl$6BQz&5;LR4#FRe9-O>cEwGeZ!<fT#iGv8|4~|892Oo4DlJXcmXwePi@>N*qQQ1;
z>p#9xRaL#@CMPFnU|`_nOuY>Ims1d~?Ow$(6)R_(ZI%yaQss+rP=F7E1aW$d%(Xae
zgpAHm%KtTfV#h}*5V5wl9y+|~bvcO1(5^8e;P<SOE5E+KGHSEkze*lVb)`%mHm}pk
z;<8`qwDM9johclMR?6YMdwsge{`oKe!iWY&1<4fJa1a8kQmsV<)LcSbTSv!<FK&CT
zKARf>7i*o+B$$|(whL8=a5+lp9RYjCoR!k?9}OoO)<)Broi@6bi|pbvW-VR4KTcVt
z*BWS*;UFI{BSa&ZvFfN(D?4ob;`PD#H+7^#wU-}cIna&rhxJ-)0>H1JO1zqdO6~Yz
zb2{wrdLFhQ5Xi9GwNr20)*dbEI!D}B@A-Ovlv*j{k!~wht-ydIXc|PH9)Ut4Hap#F
zaK395PoG)~vtc`5wZFg5>Ap0De8`l5_xZnddPREIqR-TzV?5M7m+XlSD~9>-;X}Cs
zQk-*z#<1E6R}FciHkxg0roCiG;NSM-qS<4dO4K{lR65F52L0wL(}C|m;u+n)jxwVn
z5%PRIvnxz)oDZtjVloE%ZF09foqZx>WxZONw@V3^;`iM9p+Hr{@C0eq;<TBYm?*l8
z{8g%YxycUCVtD&%cF^r`5>``j*{1Q^&u@~^csV>CA@zqWPQAZ?<f4N6AClGrmVA8X
z_sq&4LKJa06r05wV*Jyyv)GuJo~^xOjd}^$-|A>_XmL=%5Gd<@?%kdzdWViV^eL4P
zx!P4a({=KLUfUPP3$=D;4rXRn4fezJv8&u9yxzrDwYf!qVhLHyAwsV{SkOWc;NNn6
z(`fG!>UxHI-ox*zg|v!9Beu1-S6D{w`JPJu3jIop9E*!fc)xQM{p5Do?SG?|%?O8=
zFlsfKm&56XYp59Xd`b&;SU>i_8dS2M$saBtkCegt?^{T1%{0MOYF9Iz=r#jsGUe~5
z1M0LIL6@Dd(nu=+f3-NSuhdJ*OH&Uz@HbDpHv*8gqUreP+tJkJRKy*TQM+eU4d~%?
z`3AH(S}|W~X=Rls6p%S=+HAA_XQ}^jU=|NU6@xCeLVZxl>2>pm?hjsGUR8`KYvgo>
zY(X<Fn=X%+w6-Xpr|<h08(o!Z<(XVggqYZvuS~5DtIcG+WVJ?}$1Bx#{syn%@^}%b
z#3l2#+O<Z4KG){gdN5C_&R{(tq2s=5B`bH0WpGmKXU0CCmX@oPkEnN-vX#dan0*ym
z?XYqhxW-v+v~jx~nvNNZ0Wir|h7SLI*VGYBI8>5;6P68_Ux}mpFZZX=f{Rr)4bYKj
z=F#<&dBPW(i=)HS;Ehhd;izHV3|);Qj!db_;ne_?MM8Xnufc=+iPc^NHUz$6f-EeM
zgjgtSQ8CP<gg2yoaIuhbXk-62wpz?1IglHQWal{&ualt-dO8t)noNiIxE-kC?hU%Q
zxDDf4b>I5wjuc_*Bqt@S&8YbY1dOIJ(_==_X@0iU;IN&c;o!J^_AtH0&+3D-8JOK&
zURj1Z_;Y~NR_H!Fv%s~GhMT6A*l3ZJwojiz9WwC&Eh{-wp-PxKQ4Zx6vHH(JT?6H^
ziAqI^7&IBaw|_2$J``N4-hgS{(y6j#@V_{hnLd1w=ctYw|H5>p_Sw}U)=R!JoS_;n
zh+Jz<XKp!m;0rEBYQ*d33D1diCZlVb6G%%ev*aWuN`9~7wV$HmQ&O%O*_T^;C`{WI
zed2v$9(u&d!!WdInMs-1Nerp7qK&lJNI6QST9vx?3wQL3#@!`a_*7(By@j6(l|Blq
z&UEh0;`M)R*h(;oXCs0C@UhYDXLNj2`mj0V8>GcZDzEP;O}6GpD!3f{!Jj0BQ9lg<
z>c3)zGv;$6#6?>DAUl*&W`n|K!Hk`<5{JXM(Bj3i)1VM;e+|))9^GXe!$F~>V20bQ
zpkYJggTLrOwxXTzNlF?kN<y!CVQCLu>Xx5}ZwR{{=p$wbZsj!Th=CLW<l{nx#L7zg
z=;8XhrZ%^iiMHs&?3^6Cg(_Oy=-#dEZI{>ntA~qCU=oI>dQ|8V`S^H4B%n11E$d=q
zVuh4whh){jY9Jg}$!3}kwS74b)U%_gBE?Luy5>411%)b=f{>_;;a+k0(Nsq55`~P%
zM{j=p4m!??)AjE3VUuRZ*-RvO(ZKBDehO%4=&nosWRrjSAHLhF{i~ETM|>g~eUpQo
zPBxJW9j!j^tA<2`hQnubhm$?innA}p@}rd-Y(i>kKE9kk#dvXiuUB9w875&?LkQ8g
z_+Bs+0Oc41bz_53)a{~zEiiFBXgHuCE88o-FnSf~ok!rv6Q(v%;r{$4qn+JJ6vRxk
zJ9gIkg8{ZRr2#{OPWBNpZ{85~QGm+eh4mu>mKalUoJy?J&H3Mso*t39A37z$6jXdv
zoUmT=62O?zi-)f4s;$F>W_7ZzN;!UVZ)2fa`5GLgjIwsLr&=G0#jH$>h9ao0(<)m(
z+h@w$xjT$k-1lSu`ehJAO%Ook?&78&r8a6ZrAFD9>Sc;KOD3qW@`1BvfAKpNW|ZT4
z`vBf$(eFYyRDyofhMp^r9y=^7EV!J++(e@idxDumVYKE#G8v<vH~_)WJy6?JXw!sC
z^*U%a8hcl7eP}aNmu*veT_QkrCLaJd=faghVpF`dO)0o?1U%+&!$Z=!oxm9*&GxiV
zq?&8+=9rir!!I@_t6Fq2F_|h5j|AF)p_KZy{R?@&l;*l7L^QPfhlljhDAluJ+F^(x
ztyDS6M428GxCF2A^77&|MFqJS<!_7DQB5TO<_1_&tnP*HB{K`|?EXB>RZrPg<*KH~
zVr^1htzRa<pCUGH&`>Ez@)uUx@%tyL4J^h_@Gw3TzDO6F2Uc6_Ro`Fj4(8X$rP66O
zqi_yf0LWUZM5>Op&IQq>TCWi^df>|C3Wcg~V}ZncO)$^TVl*uP>+w%RmDSP9)WLYB
z8%#FPGXKcTYIa&Q>Y?^^dVlZH;(!@O2Br+*y5+G+iz7jZH*}!h+%^*<-ExR5?o*O_
zUhfx`V0;&Lkgf9+&Ws5MT<G@sxlw^wxS!WWRJ}woc~&1+3rnqPlhpioO#pQS9q*NY
zJNo8TaPeyNT%LM7qDk*{x|BG&6T)*c+oEi)VD9SA7C8=H?mT?26#9>>D*kp^i5VLv
z%RJ}7=Ss8I#8cnUFg`Z6X0RUS|HV>^Y99$xy=eZpaj#zgAnib%N-;yo<N4=y-;x1W
zp0q;4A{KhUe>6tA-~0n1hxgQ+jk>tFcvSTNp{NhtE7Q8`<6Boc%5N!yuHk7qoX{$^
zdfFW7WkKE$1d+1cw{)m)WDJBk!Cy0)8h!UUAp<d%yEmqv0NMz^2LyzKX>__3KsQyq
z8)Zg)nsY|4T_q5>_UL)GLO?(SG%In;d)#&_3Q3e0^!@KmuTIN_7Ua_LV`-KzkB>U5
zI>NrUGL+hixdIsg7ZUuM7fhT3@OA%(rimyB^Iw;zZ;OSXk@O46VE=Im|A&sF#m*GR
zU{e+*iT{-s0Hj?cS^wWXW)&EUOeN{$Lwlus+A46?|DGPm>Sml4$&;NYC*se+H%jX*
zp4G_w44Rp<HQoLok{o(piaQ-%d5!k?KaTK;DM+(0*jd%q&i9AIvB_pz$Z!V%PBnuM
zhho9mXh!<&?QJ5t)E|k#goUFYM{j>$P8y#EvG0ZKM;91rhiR#mav@IM0$#i>mIJPS
zOLpT07DrCD2E5!SmnzG!m$j$Y8Y$&)ak7x2S1FSS>DIdsulcwEfLiv0u&Aw^t*Pl}
ze6H$MY+@WmzW;#Xb<mh`sx=|8e0)=PDZh;y=dOd3ev(v`iq<1xY_ACbDV~I`DXT9+
zH;D)crU{;y52@y`T-yxXkZ(xV{eU{|LAajKE56d?qz$sg85t}+0)y+8?PnB9XP^AL
zDvRjJt-iDjDu0S6;I*6^QhoTeMlJXXgYgAJ)G4%w6di$-X$IrJ9^~EZ$IZcbQ4Gh5
zZ(f)}ROUU-cG3sEoE$_i71YrIZnJs9^$!LJ)*c+;2iuR|_w8GYL*>NjyU#&drO+AB
zpJPWY0qvq?S5-}{<a*bY1XdK}u=mAaao}tH0cqMdPFF=|>z~?&%s+Fxoi`@_)Tn{v
zTF%$_{BJM!>C<^X#sP?Tc$Zo^M-b;t$RM8@0@ds6y6N)r(uz5cl7d1)TKeP!Ox;iU
zk<WE#a8SAj3nBcsVivd0=0hAp>?O_amoHx+$*}aM#u!*wrvChalgKroi&u<6y+kh4
zYoconjU1~QTW+xI_Io%#h|QvFvc2f)v>~vukW1(Nc>y8u_vnfoQoF~r0e4LQlI!to
zo?g3}v5MKa<CX7{GrBiv*dqRuP?!H*y;ON{&tjFK+rx&T8MK)^y*vW%rNb7$WicCf
z+1uJ8xl|i8&8)7j4z5bmrRlBe0Z)H4-|2(@K(AGWz>WNNBQ0&uTRU$Xs~AIz2lEsu
zE2qH5!m@=N6<!4d?i)o=IS#7(4>9(V3^R|?cz#-sCA>o1a)g`*qI)_BpaWXx^Z4{A
zaCvuCty%<^BdRPf4=^Nw_hZZSY1Q7(N8qd;Zr!A+wuVD4y9EW125W`_Va`IA_=}tc
z{oTdlCk^BrrEce^5EW%>OGnR}`|*>-n#CGTzvnq{4W$8RrgB=y=$V*iMaqnQd3ber
znpCV=sEEjGEFtGe??&*rDRXu=3l|&LrDDDW8RX3vnEjKGKLXpt?-A3}A9Z)f^H}l&
z4*D$)FUG48v4kb1rQ8n7?&sNU)2h=zl187))^!`vq>+v=_)`?4kI2o>-*Kp%`||Rl
zeOtxj_Gb*pnxV(nUAyb;nkTyKmce43zGrmcPycPt&!d|O{|YQunRRnlC;7fukzyOR
zA6OEpF7o+e+Ulzus6w~%V6~?O04%k-4JB&jF!KYus#!1yuwp!Nttk-fd6QOkI>jAg
z<tpV-6WS23Cy2KzjrQ#M?_X)vOTOOLu~6$xjE#?NV}lRb{Xabc@T6U~h>F{3EoF3X
z3ra{aCdz_^j1Novw+Sf+dUSvOYERWHI3_m6P5j`JCqe1!TA|z!UM67{9X3)z9Y`*n
zki&VZLbFoD9TRWHebv*xQnNt|AYu%d@QMpkV{uxE2=RX#gT!Q;zk|WxtF|SQum94W
zWX>k}v`APv2S?rak_F6zUtblA%#eQ^zN8i!SU0je)oU5WeZE(DcX&n#OH`mTb6fI-
z^TnyufWa%5umzfLyzBTpp01$xKtFgtYU$GSK<3F@VZYr2)F_F<X=`lPaIGRr5Dr-k
zzPq;7V&!5j5RPx-C)||s=>kFE*VIaF$IULqcaDA6w(M+FTRVpitI1rfQYD@x-UL4>
zQ8`jumZ3eiDI=4iiHUoflf>*F{-^zQ>ZQuMtNO@yVF?gCuro+ACKu)xySrE)KcajI
z(VDg9%<mD~3>Wgf9_sIhG5`1oGi~W;8hAL710PTFZD1$qoRaJdKyP{9UScE<RH+q>
z3@1}F8+ZD@_x?SeuLuqL4@7)t>;3{wgP>AUuDN0^PF<?SFP@|Z>c3Yk4hb$pxGU*k
zskgWLQ0M{wZ9>JH;UQf{Gp}ENiAW@P1B%kz+#E&@;2Bvn#%>$kvDC591pxvqfdw8O
zK0&w8URBRFGdGtceG~@)CO;Vk1%-{BJvKI0@^hjJjX4Xxi;GKs^6lLnP@OR`u|y;Z
zj))M#pjyMe$4HHi4ecR6Zb4zvlL<i<HncRr6Tp7$85tQ0DU;OwjF#TFdo`5u6<t9_
z&V*I>{{B8e?;G0ZR5?%r7lHs46`X0L^AHD+!$rL*ODWh16r`mqSTXwzOw~Sz(PATz
zEu%vf-++@#pP~Np-JN{3N^txW@n@67Jc39BKzq*6H2<2zaK>p;meh7_!;?_M^(}ve
zh{BzAZW}NgA-|Oy^*8x)!>L{iPjaH)az(N!jYyS$#djq*xS};!uv?`MYsn^X;o)HA
z`jaB#Nt7}<q6Qg{N-h8`i-P$-K}-Mj+bu0R>2G|XPM^lMaYv?t%JF#xb2%~%)F(8V
zweui5<HEwFLZQgv4#>k1azw2fmf_&wLg7)FTK^x)Q8~hll`=aaJVz)P<It0|I}Zip
z9DT%9Ea2ig?8Mg&<`XSqY$NtN|H2UaKopt(w*koPayayw<!S>nNjmYn(qt_=Gq#Q1
zTUX4VE^()>ZZH6h+kZh2T{4GaXWh|MBp*i|a#P!|;^6CMlPz62Gbd68pSa_j1=U2y
z$!Ha|IN2LF(G9aaU9LfQ<`6~Zl0qNy8afqafwmdm)zDNo5T^u8qd<27POMUCUB;?o
zKT~UtNZXXPgCJ@suJ**d6&+>udD^1hKs-Zo^y`-+2`5?-@7E4#w7C-?Vy_3EP%%*<
zwg;@n1+khhd<cQel*(2lB>}c>gj)@@S+*rS@v2sf{ukQ_YE@5yz{O_+g%85m$5>1y
z20|=PYS~Vg7lt6*e`yZASm)-2f-r16-)8<!>jj<?1GzEjG$^y}*<WV@TWQYfe~{<t
zW|e{vf-pul693pCAUQ!1MIe4e1w{x)42#7D0gz>Y%Z9igb1+edz~>6GscAaT0s@Bf
zCU)QCG8<I+{`)_|wMSrs1hfdKjv&ci6Ql`=fw&W&B}(?cPcYsFI_9q`He(Fs*?&e@
z|Hn0wZtlg)aA3kU=l$<0>~F&Vw#k3_IpjZm5+4OlIeyTbO_pAH2%6r-f2lWTz*LpV
zHw8I<5_-^pJ+g23PUPe3r`2cT!Z+{gEphC&VRU~Me;!vskzd6bqx&HlqSTII?vOeP
zbj!|Zu5>H{Ut^SHU=YYuv;;|VlqNZ$ozwcL96!~w9;!k8tY5a@>3S64i(SIbyUt4n
zwJpQK{ho}}f5VqoDwdE)K;%`0kRZ)7%6&mVQra+pwcDVUFG-8Z4D)A7s5G%`5Ly#c
zLPN(3l;K(<{c+>_7=<DYkk7)q+LVN$I(ng0+P2no4%;NAk`p9<mN@nHAit1l4-Li>
z<)tM`X$*^Pv^Sk(a@fuMbm<#iWX9rbPe}ifptD-Z)p~oe`H9YC3aP{M3<(MC^RbPP
z(?jn1<lo#69|eBe+>{XWd0bW;HrcFFQAK0=Z^C|#jfx^*aTY0}iv4x$ced7sRrpn-
z+NiVLW%kcjJ)rXd#Mh#oPOV)_%^lIgC*eSWa_EEcoQGSmx(XvHf>Mr<$9r!;sut&$
z9T*<iURT~V1{bZn%z3-T>VHb{Crni5Q0mFtuq86SAykCRgR?BgcRNJdu<T$2JZ2+>
zlKbD`$j<jy4TI!TaS8PM#d4t^vseS9da}NT^@mmKx74?te*5;#^K4aAPAOX$^6l^6
zzgbPzS{+IbdD22QHa2#PHI$&F$$(Fn>b0Vs`=jZhnnlxN#ys!+vOAbEGYyB6ae0Dh
z2h#B*oDK_(S~+^XWWB=0Go)Yav}%L(ztS{ctf7f^A_pwii1W9qx8}^v&Ha<gjG747
zdf5fiV{T&#`Xc0T)SRQfM};(sMvP?$M$+#^goRZZ)M2I&)Qw^$cUdnN{`~e+m0VhM
zYwK+6iM?zFSj)jD%_u5WOfg$utX0>E=XnEEq?4~xmK=4#2^MmOaR?IMnN$WN!@~``
zJ^li^ro9kRuC|1E|8HI7TEkzSdzXoiN8ZN9n+wGHFVBw~Z62jIMJ2@iUURlh`IBsH
zYzUISi#q|aSwE%I@9<pFj=Qa+{l)tQ<r9ZN5z`UXIl7Fk9$oZAd%#Weq+s5^-XKqi
z7+codd+!e?QLhE?{tZ?W_g%ZhSVV3Y6P@#;+ID-HM`cH&+)SSY0#!bzPA%U~O-+S`
z!4NAR-t@r#hVjA3Lf7vwI-`!yecX7^teoe|iHoTr?b%oUo2!H`2wCX2{k{VLvoG6U
zfOU(&-uUIKPJt;H`1ZIq?3U1MVV4%HG%_~y%NxAY>G!~6k0#RxRCr<mUlw|Ld8%Ys
zIM@=Z(up5}W*7IJ4~`q`3*3PZ_v<6`^Z-)uy;)HNDbOa$7<Kv%?9`FIYuD%_mfv-q
zFpgj<=CToJD7o9;{-V73-S<1gz|vLDRl;4uTIQ(aEX&cL%jIqE>2c2+T}Go287c>E
z()Vg@0Da)BqvgVH6F&Ip=*auzPxb1eBf$H^cYnz3@Mcm}6u|a|kyiTHb`pR$cYpGA
zQSkY;)%*Fg`M1u{fOIB9xpdmjizA^n4YYk~LB_v^Q~c`c>Iv?H_n$)btzV4w!^K1;
zzXK^+`PvRMR`!ETLe-_L&dkVgkn0omt^hKy5pbKG4FZ|Z9g?sYRq1zFcw(@qmF!o4
zp8d%oBBU&+%y+~E5CK<}Lshu%Z~Da=`^{fDC55!05l6!gKo5-k^<n$E)jS#lXdGk;
z^3}?}2^!4vMtp({`7EwJtU;e%s~{^Yt01>`<(+`C!;oB{fvInh5ZE)e#~S~Um(Avt
zA^`!wep?7)knT7Xp{LI<7&exsmR}sNc7~CEdY;ZDq7>v$ML~#O2G{ik5mPK<{=9zj
z-_e**6hA<Clvp7RcT{quYpU=mI#A9N4ks#gJF3*KJzp(lJ`#h=>9xeDP-IGffqks=
zIi(uU><Ivsl)}NmBi+IPos(we+?FVr>RNli$xs)$Z3bZ+c($bb(hsr#l1R%zr_LXC
zj}B(Qw4T&x${}$&@j&Z9@q`=pgG2}tN><+i@;9QomIgeeumrQYfPD_%kT&Csz}04l
zT?C$T+VYHyj1sC6Uojvu4h_4#*O!*?XL!9YP1?jr@Q4<>wcm>d<3l`e{lM_;<8x~%
z47})QPsKnTd9w&S^FpuCtadyGJHO3Q|1MXC3HK7Qex+3|$%zfStZQhXfv%^bq}`Y7
zL9UH3iY4Oea=wD%`982?6zV%~qf=V!Co66yo}*`FZeF}lCi*b7?9T7UkN&Zk<TG@^
z?2!Z!&a3p>jd}v!@i!=Ob=#DDr+U!xSw~~7TJ=cH-wqMX#0`kDw^{X>yl26)l_tAc
zDn(}FHieuaXbPCU-)AQ+R%02{9m*HCbM8|*b8R8L<}6s4m?4{R7fanmuJa@LuW7Y9
zMwLp{1)-54=E3?Aue9nlV}(A^ItI8$-AN#MDk|!bR{z&amkc%wZ+{XOW?oZO8tn6p
zCcp6rPC>s11qGSLmX^&1zsaA8eNr)mi8&dH2gNcJ^>y{r$BoV+S|<d@!3i_goCzQH
zM^f4ASe65vTLA2;<M7em(_wYK!FUn?&-5wZKjDaDMioEwY@}9bRcLpRyoN6+=kRKF
zI69zj>gwtug`1je1|Qbsj>=88`<~bW3W8`+sa1*9cXrfqlx>D(eBCC~`LePy(NH*I
z0ax^@$av!O^&)QkkWJV{C!_AbzUQv4u7r09e*iDM({<BKyJ`@IGNs!UyT(>sq9G{O
zOrf7yp$pM9en!cf?DD=Ulq=V3a@Cyb$S<Of4=D=n>g~;e|JTa;?R&kPJD}wy12Pqt
zI#{E9uh=|5Fn};RL9|%tYi3qie2`j}Y62{5;n)77tGh@4E+OOhwJ5jAJfTl>UI}V<
zb*M4prrmz;OjLB1;2BUniSUY_Gc!+;_zI*N&u?QjK*I|RxNaTJ@pT^&)D!`Px~I`Y
zZl`qtApQV49@wnvr3wL$Tif?Js{@#<2qV&6@o9_(%>k31mnbfEKdJ!94X_sM0aQ>d
z5jPx;d<3+Rs7Ho=rg4{Zn^pV<xm0Xn!;z<_XV*i3-Fy{i;Ep%Ck#k!?!54p1fi+ke
z@m5jQh;NX3DZ^jw$ixpOvo8Wx`FSZb&@=h;07Diad?`&R?Uu$IA_#q741w^yT6!~+
zejpa~IiOIK7wAwT<`XrIBNm3UnX={}eev}=2>_3PZVo3~9F%Xh2?_8s2s2A4L08^$
zDc=SsKXveQ;1dv~y3%`G+zTcYfJRc(hOj|v@;=57U0#Pqz@`pr^!Wf7UEX7ildU1j
zXMS`aiUepiLW(BjBnE7+gg-SLE>;_QJ?3wV<+9KT$Q8{OgG$RSZ0mIFP0eRoMR(uC
zpT%{d1Aba<l4OW!&2*ZVV}kBUmgLQ5KKGI5b@?A_F3MMiWa`Olj0xAwZ;7dev9^s(
z?@DRcs;$rUYfz<wia}+?bmbCq74#|}F7YTP0JqP}9eA-=H5oDhKIMktVd;T2M-<)%
zQV*U2_7PIt+<Xs^CPdT;vk0uB>U9Kgd488e6%_SSl1Ij@wYr#z*G8Cx_lSa~=Qwnm
zQNA}BkSWW`*sM1<=@kSX-Jqv{BtFv`Hs8KXJzS7)ELN$i)205VB>l-@t0-l;uuQK_
zrU8$~T_b{@lkIyF%p3-`-YwIr?2Q+zfdK7m4k8y*BoBu9>Hf49ou|_jt?WG$NefBJ
z<?%7Ced{Dm2x|?qORo)XclB_m<Sz+AKtL}x8fK%6RfyR_48g>SlAz0wqe}`&3u`rJ
z(=CFFU2xP{{TV3k9keYak`(ueyUQbTVS0M{BMJO9j9hqZDC(Y6R<lDyEXhKrpI0WF
zqYQkmx|-S^ChrsW|5BuGA=x_%DeTVfF44S$MyY3xt!AZWrEaxkG_F&~rnk4Z{Zey*
zN9n@ZYE!LFn`utFhof=ZdX*-7S#jUzKD2Xw1RUqdTtUH6-)7r&+oNv<)N#2GyimU<
zdV2CrpT3*qf2P6DpJW(gd=v}J@^r}LaANb=nd^dnu1Kj+BLU$u=uXwxb?jHBu@m&G
zlv~DTVLU6#Cl66{c0AOmmCLmu?MI*z-S6y2*ISINtS&eFV3=gfby#hJt;WK`!^6hD
zHI94-lnnRXYt$wKMJa9cEk`<UEfy}W1sV?LhWwk6boz^vlhqoxj<hqq<CBxcO7#yg
zm0IP7O|J7`<WfL^9`Q~IM#f_{SZfm3_GTXSOKWLt#6}8Bt<=~@d{nwgH=p9Y->)R$
z^Zj!<oy<=z)p)w#a{=BZT674jwAHAE942D1?)gP<1E{e`HcaXzW7)iJq{r=?C)bYx
zAPwCv|0fV~T02i0{xQ+URo85xM>KLebCp3erqVt|n@O3CCY?4bCns#*X?ern*Vm6{
z#0_i>d=IB<?Pe!Sk4v_i6&d(hI?K9uC+oFAn{UpNH&o+Igbw3+obexd*u3|)v>fz;
zWB9#~^2G{O=u%VZG;HS!HD@CfQ;{g6d+VDTh}msW_GS{3rMGkwTmY8%HES;h^7-rN
z=k9Oj1hJZ99$EkAENM=`dBSifG_+S>n9Ir67I{{wF^(KIujjRIi#bl+z4BHmJW}AJ
ze4FQ}??c-|h?bsjb-jY0gdzc>?!iL9edgfeZ;7wnLdUx<FObjwJ|tAXb}5=ROeyh0
zfQ)%DKZSOfC=5S?foeLdY+j75Rm`>;eoE6FcRsE%sa(Wkp9c?n2&pwp0kLP_8T_$A
z5q}ObeNuDiTd=PA2pQ9F!P35TrBd-Xtn|t#Ee;;~c-a(w9=o&Cp-~%MT`{=i)e_EX
zZ7+{mI6lU@8^(;vk7$v-!);cms3b@*uo$%ab2*p<g$1;lBWn|iQ&zA(BR;`l7|Qb1
zRO)DxOb^3iOrp=j4f)78t~+pKl{jj@FY8dOZT31t6MIcWOi9IM=-c$*dn1!>yn^?_
ze|@NHs^etkF8H4<8887UKdMGWyn5;|IM`;6fne5Wl3a&H;p=tE=Vbe#-tpY|`P&mo
z&O+}ck&sgW0peBidmEv6LJ(w=Ug^j}0H1&E#Njl`Em%uSZBp)g7qq6n*X*4)2NRw-
z>^?Nm5z|g=)$)d5JIvWebTWGFa<vBsGm(?msuV$^!1YaN?VeO-3u@c%7yDq9saM*x
zt%n13RHp8qK?vK&-1WY!AjAvul(p#S;GjK4!}O^^KpgwXUnq7EdYGzG&2XbR)OOdi
zP?B*l{Q957jm-_X)?{2n7$QR(%t_vlB_}ov8|O4KH7Z6Mwjrkr|CqAc+cyR~rK(%W
z*m2K!Z<ZpqagZT38AGRBO0xon{_8`Ls0e?gxdWX7Jl%fR_6&j!eQ7~STsxDXh{{SX
z+9<v|NWOG=Zq|ja52-DW$~!v+UC!ZuMlo!MCLwE~-xL6UD|Zh;&JeYA)5>0oxok=Q
z^77N_r~>+^>Qoe^(RR`=(2@KQhB^u#^sfN3AZo5Q9hWQV()n_?d&lSMsV92}|9Ym&
z>P8#r%z{)j_a!`jDzJvFp)FFSq?^_x$*ChT{@#s7`F7p@kAw?|0WKPfp^52<p{Z}K
zVnCax4*0KxB&DlLaY#s%hRU6eQP7>$GUkSshWh9FbtZKxM}xxArmWa97?^087zM{w
ztcT1GPMiP2=1)RlS-3Vew>o8h*cn^-YG&3m{Ti4mWmaeXF>YdM$a!9GV|;b2MU=zL
z>=}=@Dj93kZK`2Fc9EGaNnOLkZnl_>kZJQ>aLWyfA`@WMo$My}_KY0?E<f;7o(xB)
zjWQ)7rs*NbG**GVQ#*?CKg(FCb(3DI7-gc|w>yn)BiwwbWLgW_a$0-b)sdMInaQJ3
zL&*Gy<k9^)#5z~d+FF11<gU7WZ(wjaNtWP#0iT%0X*c@bF$uBZgBN`w<$E2-F^GiE
zu(DQqa%{)2t>g!XWU0yw>Mc00xvbX?t(H%aKAI_YI0D7Q<9y6^52QE>RS?T)YYZ*N
zL&FYT02w;|l^OM)$$U@wpUsV)!-V!+SW+)1ZqU;C2T$OhGHI#|`wTl<Jv)N}qX=l<
zL7sed5>pNH_R*Khl1faF%wvaMCPgCN#-$diNl#Dd>V>}rvbMqWoeVsay0YZWcht<>
zE`-=`+Abo}(#+<2s@T}~k3f=4Ql=mbd4+M!5a8tGWapn<>tE~d3A2|sW5HJ|=OE)1
zjW4zOV%EE_+CfJa1UGyNI})uu2U$xX6~Q5t_XhTD=0i`SOXZ@B6aK>1qDb%A**=H(
zk3$>!`p+vb5(_H*hi9wDs!_t=B=qCNFw(K9_YlX&#$kM+Mm}A`Pg9j1nX@fdcwDc)
zfDO>d=DP4pN^mULQErd47XD10t1JBr%4vvyj#?V??~S*Ojbj|h>d0ux$qAVzJ=`oU
zY=id=g(9Aty%ilBD=`X%s%Pr%gs6(u3nl$7eh-JJr=w4+jJALz5p;KqgY0L50WcCK
zEcoJ)Xdnh&V9z3<W@x14N;QJ6cm$ZD?d&ZXumi1L39biKx_v4I+>`{osAlKV{#ed-
zPl@nFNtCL&tu)T8wnlt0RcL#2SzBK}9Lp%us=O*i1Wp#f2L$}>4TT>Z90ZOIj35G|
z9xAg@%g~UYJ-)iNenQohe&f@vUa|ZAyNT7s_?X2sCQ|`TFV?WM#QDZoi`MJ7|5LF$
zct%uI^q*I9FRws0nF=83M^_tzXGs#p!X>ee5CL_x=PR}%3UeMOkC#}hdoUlD26f``
z+$TKv0(N}&g0GH_C1~Ess_ik}*C?r*^v53ovhkW<wQ@cM3=L%6-w|)yBH!t%)F_|K
zq<);ZXKRgv4dS@S*`4h8h_|kOcq&~J`$;(Pf%wzms!NjP%4dhPm)ZiXoK;vXfa4?&
z=Nlc)=TH{IWP*Y@Y=5DKuZFX@95aR7o&j$%ZK)F`24S7csMJh$Zc>*w*mNd_v>Qr}
z1LjE@5~n)Ixn<hTxc63erP$oC`Nz@G7<8XVo{psollJLa)@SUI2jUqj3bn&GY(O1-
zgM2gbzQ5Jgvcv_;B;{tl9c>rUYu5s3bNA`yu-vA6E~-1sfNC)?GZ>cQGuzH~QDn+K
zH_!{Z?k>cRYBRqGT`DRTxH7PkT>(BDlgps}yzCSOK3qHvI>0$t%)t92GczJ0LM<&1
z3Tmz0&aUlxpDHFprNL5h<SwhH2(Shf>q>_*XKr50LL>TJZi#AWU|YNgQ429`tgaG~
zuv)xhY()uN2B6~-N-alI12pVjUc?tmx*xpr6t}1?#>|Gk5lRdTvO)_??o^=@rqg$K
zI?XjZ+h+BdjUyx+*?bSu-hZE);^RNy*BE!?CMAjSL3M3((Jxk^_!E_Bm8mDG)flv0
z?<^x9uNjBDHDsmd2>N*f9A?UXOM&`{R;^*c&RkT?97<;9z0l)d09x;r4_(Trw41bE
zxC!&|Wx6vkp~rUR9sH`UKC8DF1^lQqFYz}!`^bV_x#{WYZJ;(l1KWRgIO=!*^+8Hz
z+NoS$^7C{Q7PZmi-~Gb3K?EeEl?JDH1KQG4;SjL`9?zYnWNBp@zpMX_9dMKsg>JN`
zTGqRJ&PuIqtaH}Y@jaDhd5Z~JTUID4YUlFiDU^<Soi2ohtCt4i-q8mQgpZEMYo~f4
zVx%$K<7V}3e+?epK5)DwBqj;Cy`6R;A4DbOC{yg<0-Eq_b}OZZgYlt;f#|VY1(l2%
zrW&D#u1v)4IHgKxNjp0We!qj$n)P-7KUZw#2ezGwE8r%NQsNE<S2693<_G}xy|d#c
z+x<gv&ub{JI)EI7gocBGgHuxy{-##p?o9JtA0aa%i&3w&O#B5c<?nlrR4k#xdZVUs
zneuWFj8I;;<9<6yr=QCG&M-AQAN;2e(c^0M-=Cxw*iuW}ByZkFehkeE&w{`D6T!tg
zj#<6;2$=9GmM>TiX@bVO8bnr(*fB2D%}-6c+|o75!N%i-+Bj|_MgpoEUDW#RYCbQx
zePd9zzb3h;AsTJK3Rcu5(zKz;k+h|sB=#TV<_fEs*rVZudE6s<!Q|PvVSk?Or4Hxi
zwTpI(BGCxiU6)6c4EcCFctUp*L#25Hlu9RZWP~Nd6p6Sv?dPV7V&E;9@$r}pRLV8)
zx$ZZ*Hj=58N(_**-~sPJmz&@DT3gCr^;|(8&)tdGj9IJmrRE~NJ6jw&t$ZbH!Sk23
zpz{a+*Ve0)9H|bE8!atMt-%RmTK?FBy*+FK0>p?oV*VP#j(h6<1?W6@L`1}#4$qQP
zSklvgrDb_5>exJ(gWHtbCZa_qgP#ck;iRy|0D}Q=g(Lh$H&{`Yf)75XNmWZuMKx0>
z4%<9kU5d>+%4cSOnR`uHs_t6*Eo)$*kBwCruP`NvUoK8rRZNFRr^-%ux?|fd<@ihY
ztBGmtT%@uxC~X%dZ}<{QW@ox}b^zz!EH;vZREhJnfaArv0=(a`M6XJ=K>B)zaNior
z7+>9wRZ!8!y`ssRLZKm#9~m2y>sT3U^a1nnLQxhVggXoTy!cv>_+{18L00&wP^(;B
zP2HT0AV-v&l@0QJ4v~<Nku#Qg3mGP)^^phAvG$Ow9jd^*9etM34eIJ@+uEv|BAaWc
zMH6rs`9<KEn3#T37d_uhIna)a5AFf(N2clD($^pf^~!mbS^5+tt}F*j+xvaCV7*k&
ziC5mfNVJxw7UB;vL>F6+QMoe8%2su{aL;hS0a)N{p!qMYG_5U}r~K(8%;Xrw7~YR)
z6b$U_SdL+nhx+=u>ZNW;b@t%;^Y!+QG-pt@(0<*;E<JZG!;cn|*=I#g+xarJCM1s?
z^&Qh)g>eNR0TPQzGBP32O%-G1GHE?cIZZX!Bm=U;pS)CmsC=JO_=Dr%O8YTcLnl}`
zI5=2Y3)bAwtq#qr^ac*E$H&KSEE%E<n3QD{yulAZ)%MEa^9&jMVrPc@0fQowMt-h9
zJu)T+r8R)utcWhPGAvw`JRy_Ip*`Tm)5^+fC~R-fJj39RIZJG8%uQP4FZAId8NaJj
zNnbtR8?EtzR~=m)(J!PEU~9nFmJnF2h5UdFre5`u?V_J1-HRDRp+RAwLdLW)x0YxZ
z7mZbpX=!L0J)?%jOvWte*=x4`Jx)bQA$lM#DyN_jcAG38k{nOOhBYD!xVc(IFv9I8
z+m6Upa<}QO4OynxzdH9+q(krTssoKYBLf5JeM$;8&81!rZcRw!^*#m5Wdh|$NQ!t8
z#0XB8hJ{*`4ph2`M1on#pAr>`?ap09Z?RzXkCd2*YayU;$~BBf_{q!W3Qk*cX!3^a
zO&H8J1+)hXi@Um7URqkjns5|WE(+7Jv)u@8Y?6;aATeZkB*Z2V`Fz6qB?_4K`pZQ5
zPy?ZRtTv2Xy&qtGp_~C{NvL;0{%^C86kv&gHdQ6znt8i>%!?xPzdls=s+N4dD2p$q
z#)?tPf8)E<FX&70s@cD5WkwKkKjaE#tgkVG&>ug*j+(F(q==|p3x#|}qrjoaOeN9Q
z-=Yw|O0VFE!jx3(xRBwP#CdZv?dR}hWe#M!t6GRd*2f(%O3D*=x%z&6tNZlUi6YNW
znEWIgO^A&kLQ#ku_DeJXHu^B=is(%f+ltxp;W)2@D~pP21hB<xfs^uN8;8CP*~>Ot
z=}zKJ8mG{x{_dHA_}F>jW8C3_N&%ad{J!JoJRg-zy_Jf634@dhMVAB#4d2>^d5yNz
zVO1MiEgnGweT(&)5_((rvk_mw+S%Fp5;#JIii)x=8S&|;-N=Jz&Pl|`_3hM$E6;GI
zdhbeou)uN3wz1G2BTU%2r)Q0DpFJuKKhJxoA2CO3aN9)$A%w?zvpIlZl5I~ni5t>s
z!kACk?T-SB(?;X+@N&6krPdy85)g^}Jp4cKe;Bm7_Ad3{yTbuQFEeoTG~|26Z3B>a
zfy@UK5*T>cQ1f8p(z!+rZS6(C29_X)R*@`;j5q#+7y6jwI%yIj5s#S2ut{#7yLMAY
zPZu-QB~T%khoHU=IEgfp+xKhvh7dU4RO(600#Lr^!mY;DD&m6hIP4mcMbdF_knp9A
zwr6P$`YCFZ%0shd9JDsHq`Aj)lr>Nx8*n*7euODBN2M`UC`5KyKxIoPbq$X6cwKS<
z$z{-vG`7@5>NT4U#>FYcwK%P(nah97{#di|%eK(!_s-9>T7x&HJz@`n*oA6+ZtqsI
zFJ$%h1mCp7#UNGPPi7c5@0Dnv^PfnQQ}sZp<v8Ys$yACxr3Q4u&X*#lwuKoOSFIq^
za<$Ua%~IiSe%HU9<T(I&PQS&G08CWpW1pj!o|LLq;+`>)^G%DdTmmT`4nkAH7jBv>
zVBt0};5n66JQX)XquHc4<O*xBPrG-AGMc~T;?yWpr{Qv}ja`82gX2^9CbBxYx=I~s
zh<>xZZilDCwU`K1;u(MIha{L|)WA64NZ9dQ`OWM64dJ}4_xwYlK)?uK@_TtWey4g=
z9O^(P(=J;m-$r$Hbv_pUDZEd97)-+B48akrVvJA$tKoWQJD=5TEth-e2R?kC*<2oY
z8t$W3vHAV73JA#o9S^D3G^yBm*d)Yg#)PEw1uP05g;~jHzdTH=KZ^x;=M)@imFW~H
zo^YA-1lK}~)+^));f!6<0r>3RVMt$HT%87vw0rA}ynEUI)AL4$*Q83GH#sRhkca`6
z2|2-TRGT4EyKi_n3W5GG)Cz!f39bQxg$iP#A)CoU0nZ}6<btP5T}8I@6;X&$PSBgz
z;r<{oMA#<zNG8ClM=e+kDkc{2NAIfIVz72(ROEN<9}?5Bd2f{1b@nNjy^;%u;%G`N
zf0``g;5)mFz=>V)Z1V7YQUgUvW;{nwk-pQsECyeYP$g$%<Cm&dqQ)w;`3G*4s-y(F
z7fQUK8K+yTbpNI%-7Cn+F$BcJ=js#gnpK2UNdM6!MIK{lp{{N6)Ou``L>Y4vk-z8I
zxHg`S9Nu=tY|nVYvV5^p={e&pTnFx88UvO{rpH#k`^86vLYw5|SZHImbpxbU_p_Ru
zj>5u1xDUjqCV9$Qo1JcpQ%gV92IPwGhKs1vYYa0v&2V{lj{C2$E;c)B4>fC*1jRmo
z-B@Y&sEmzO+*<AF3V2>Q<beO3{(KD@jg0^3=%6^)3;4uPyopW9td=^Zy~>h%V0k>Q
z=Kz0|rBa@34P35vA&3&>uv`anIBDLeOBubA50$%}D_5T_Ri3Q=@O9nKOFv7$<+Yab
zN8j)NkEC-B%k%x;cr7lwRm)gzd6~<0Pg-_uVOdLS*|xoGZF$+YZR2-+zQ6vi<EWnd
zzOFaU^L76Demr02bgpuNGXU29xjDI4u<lvx4!6w$wXaGRPJ2fLH3MC4eDz0BwA9QM
z%oxP`&`BL%+hfyJS6{rko{r9IKConjy%XHns*26V%vNekPD-k^pCmCs-EZ<8N*8F*
zJk_UOl2y8SPnLMVU4lN%p5$^e_tv!K^FO?;;($3=N@L2RA>q}s#YVL17BgF`D;*i5
z!IU~{;3nBR*pX44G-F9y&Ns#%b;$TCQ#vUjF44%lySjF}_5#yCP?g)a6Or5Qa=Q|$
z$ufj8%=>*`iVK;Ck53W^GR&o$osYSUx)Ceg<0#&Gkv1F8Mz9+9&do1GGiRQ6K8lEL
z^hGFytH8v!wX}GEIk-dW?Ni2MI<KSE)7<$^LO{-QkoaZOsUzr1{hr|$_*9sN!2$>P
zf}y?Ut6;{3S{$|qdFu|g%p!bzUx9AfYN}|wS>AdA&YO8e{}Z3#6D&<=ll$?(_t!c~
zBJs-AMv`~$EG*6DD~$QFeQ6UgvoV2u5l-G1NI5kE<)C>CO2munkA)J#nRFU_Q%;w2
zU8V`u>44m=&I}h(@DAQ$HCy0*GA=p#t!7h8lgoi<7&BCKo9QLqt;z{dO;QNK2$z;?
zcNADBR&0Y|8N5C)j8%44;<YN-FcW!Sk)=(3Q0zc*oksj6oBOba@Cnp`x-_GMBL~yD
ziFL&1Ii`8$j0Sa{-BFk(>nLxLn!Jx6lFp4gpEmYGt+^}ZllcRmKFZ2S|3Lo;n*XhC
zlm27Y+}^0l5{dGVkkD@qR3`Ia7{Ab9Z*Q+?!dEopOf<u3J65az*Zm81lk3YyX{RPw
zaZ>)}|GuSVBg&||*sN~NoOxG{h>W_}YI=EPIXTSqv#`~9QltOAV3?MgkQCeA3ZC=M
zrS}XcjfEP*T8V~?5;}~A?A>NR{DWv0?No~kT&upJN|}Y`oyH%NQQ)!T1P!FLk{RoT
zBM}PM=y^Q@56|!3{6RuOM@rVE2{gcfkNxbvv-Px5!?TpNJ8Fh@ko1mt#Hgw(RTz=<
zZ2-a@GRYbw$4@g8;RJ&?eWcOtVXTL;g_&eI9fKH}SsW|+)moUHNvGQ8^rdal#TMu|
z5_F`w$IRCR-6l+$Z*(3QS(!2EgMiLJ<>m+Lw<YmGHP@uxpaasm;r(%SY@&Qs`b%%k
zPHu$1{ZfT0bl*>9F_Cck6b5H(vPPasvcB8TWvwqbTceZmq6i(v9U>5N*hH0%`U2CT
z7>z$8WqH=X73#IL7yQShummQ^N~>edx4*qWFSn*yEgpj92R-HL2=9*xIu~9#pqESM
zbz$TB*zO~gNxV0z`$@G$;#k)UUadlHet3TPF@xI_ft4jTFgR$p-b5JguTeDx<xdf{
zCgD~k>CRy93PBk6>*F4?-=sn`2?J1Ibxog7UnvOF8}|Nk@HJjeh7l$@BLj_dzWw<z
zEIb_HhV+xwT@g|S?u@<e>&`UMgrgxQF44B~gYhJeT65ND=h@k~m>0~m?%Ov>I?4VY
z1)Lvnl8iTv)<fdxWb59s?uAwEvqK4%`za2Rq-UfgEdZbHl3h!yxgYS-`F$$Y?9dk$
zhT7lI_){*^Ll3NmH01_wgf5^=p{boNo7+PKi(*@sE8|Pl=r^@@4z5e%o*8@_o7}e#
zes}$KxF+}lRGGi-f$DqfX&yi^_&r|2_~8QDk<0aJzJHbaEh-{Ef9|#iGwvryS>7ak
z{_|JJ!F<by;!!AbT9XsIEi8K9$c9K?mVWSQKtIEO{ggK9K*vIey7%5WID%Np3*L7s
z<D=c5zkTSN8ylSudjphsq0?n<HA`qN?2a|{uXS)dpCRj;&}xudyJe9~zj!1`N#mON
zrU#V0g}TyPu~T~WlBfrik6f%3%H_SGiT85asNVRx)oKGvL5{MHvb57*eC^+{8?&oq
zLPyEw2|l9S374p3%jkQ-*V-*EOpRUjh7;w*k7O0*=K;Sgou+fwhX61QX;CUs=Hew^
z$errLvNN_<{rSLX@PZoxAGo=(t_LKsKwdPn=Vq-&uXpyZa1!A=(QK~#cZ~vCrtSU$
z+?E6ug2iVcWr>3vRv2^iQ)7!iv7yw5=8F8amfLYJ=>`H9@FMV)usDK&a?PgewbE^T
zcPp((2gu!v>7^eYBT}FDPMklLDwlE(r8+zwRaGtP81ObD{Au!dxhp<i+zCJG@E(B;
zREvpuM?{3l>pJ+S>N24*u@v#8SR7Am?)`=@K86#`yCfbKn+nR9&{briyY*B~<C#Bh
z$feU|@T*IU_4fXwhrSKa%kJO(tv>P4HCf+QJR{shhLU^3IyN~R4<@Y}pRD9kEr5L?
zuhYp#??0}z6CV`QY!<7I|9tN5<9%|fx0`kE%z{>0WP()Fe&TObTopWHXmvf`02}&D
z9<QL*C;W8|yQ~h=bZNDB%S*Z+u=cyL4#d&AFW$SmGx9YYbx~4J?wZWlWqoq^!Fx+&
zF;>)-7ZNL;oMXz60LrAQpnv#9f8%7Vt{Fu!JoiK?4FBR2#p>m1pblpEm;2kg!`C6w
z^S1zt!ajlbiYK6D^!z>>#n;C&56#{v(<mi0eH9*vp^l9as(@X;T^d~&<ki$dg#B@#
zUb5Qc5?mWoG<^W>p{h@6pOa(*FK}1d3QJJqWu_aYjVIEO)tqPQXZ-9DL+A$a+JG>k
zRr0=oDFrgG1tbNt)=HJKv&>nPxYdfg$1j9<33!nt0y&IsuG_aIme?ih<oH0d+?1vz
z*EKS(kgp-&brI*pg2;P!3Ug+myQJ5CbP*95naOGl|85QUtHbw;%gcYq(y)W^EQu*s
z*MV0TMfi0x^0m*doH<8sQ1a;Z6><tp!3iv9-PZx`1{F(Po0sp?-w&v_q@|@%<P@0+
z(dHXQ8**CBLPf(aq&S6zgnz3YHg{#<caI{D+lB!K;Hv1Vy!*gcWF?P09{e%&goFgb
zW6eG*fBtf<3JTMED8){8PEP7s8qezs_3H)k7E68LBCZji8Vo#B0-MuI?@_3;IAAT3
z({_OJGA^>;J9!z9aO{=ny~mSvHDP(u@9)mst@lqC^HlK!*ap*AB(j<kjemvH81Gl%
z+o*@5GN-LPUlt%bT9QGkqzXG`J53k2qi3U19K3C&iR~VmOwG<OG>SzC_E~C-i%v&#
zMV1U`_FB-HIHO*twWrIKqi4yoz3548-Yz|Z`X5}5VeYS&z=42wylXG$aQo-HHcwp1
zLN{Y=D&pEXwPDfoAuMyWEw6FzcLTXxO1;fCBqSR1ELW_M{g2p+FyrH>0gBJz>%%;Q
zXlxHW(^B(nu4p+?A)2|lS+9h6d8&Y!OlAeN;z`XViW#H6@HU&zM3E&WSUc9vdXFMF
zTOT`ari75#c5Sh$N}^0z)D}%R6l>?w_yhO<7jg?a;FAo|x)8i-)6}b6n6@J2`;O8+
zU7(QZ{<L@QTsl*(-9U4Ttj~zm@zxb)A+#XB=R>!D*dmy}CdZo3RA{HBWVi#B-DTnE
zXa*;d=SUjQ<wjE|vKdQ~fD0F5mlbXa@tn`v(SA*VS%JA?Mj*NoTc@bs{uld;ou=_z
zkF<zmhlJfb&uNOFX!5^*bT0+@J;u(|3NkJ-B2OlJJ|iRR5G}6f2HhUbT=tJsuDA$s
zDec!bH~85rz89);-kg~Ra!;*h3Lehn&)&kF+RYK8_jwF>wMU8JNN3XNz$z(GPW~a*
zJ4lH(&djG>%2Gu%MwiB*&HcJ;zUG32+ivxDU41_PxWx*3E6`T}XLzQ74}2dOw~M&J
zwxbRWk@b4T3b)!(7n3`=jbra^&#1e53Sj4sO8$g-cz7r-4nXoF0yCRZt?O8s2KTyy
ztk*0Y<(nU8(`NX;#>FJX1V=M?9)SQR?}<WsSZ*2IXh%FsYC=1`83G=1;UOcRz6|xV
zYF6s$)mX`&e0==@!xEaj-Uqz{Ris~~rQ76S%7$8JH4COqH+6@z^|p%%M32$NlEMX1
zFCFq`W;CrXB&L@HjS^R>)*;H;aRNe51`mt#+pFpHYlz}lnD5fk(?nD{&?z8pBHBoE
zZ-B>Bl26h>-wG^0LVFw>M+@I!+}hm?v|*3Eb(u(tPC2iO4qO$LEMt;PzU<6nHI*T-
zm<cNj19+j4jOPIuK=Elwri*_!=3}tJnKw9<=DyMN@m<(bJuepTI9-b3@cRD#{BQlg
zZpb_79bW}mM+p}IP3YPEX0h7&U&V2YQ7)bB1Hn1#IY0C0+{esyiZ>ZhcEKFjl}(rU
zl{~B_Y4i_DN}C&-J0r=D8~353cycfDPYhV{<thm!N|sword8{w8j7TbU*y2rd#09L
z?A8uaq$VxWsSR0NY+3yJ3FWprzEL!#syG``?u)Rwb+Qf_MD_lIiZYys^%jTNRp-xY
zhk(o1$02etv6XgTBmAvX%{p&K1W6b%<kH69Uua?n)-Mhl9$3`H9dC=0Vv@QykxOUn
zpcUt<0)n;T;xUMob6R(o!ikzuNS@ags5Pocyx`d6kUu9C-LB34%218z3gjSb>b#|R
z%22OV_v-os2R!+@B#CM$GVv<p>Qp@+y3DTtH>gjZFflrV{Q0-5jgbR|r_ZHptIRaL
zz>SxUq2+j^^5zT7qyLMqftaSttb!h22;1i_zpfCv5aZrR=s<8H!sGuzV0bE5FVyh$
z>1;gTba=yHqGif|<zma)>K3TpltaU%o0^gRIL0C-y6f<+fX0bIR(UfaN8{M^utDjA
z6bIpg`RX~3V~h6>2i!sD<B97*d82c6sJOn7Wj=rqu(GvY&ifn-xGET%W%5iHTtuF9
z{TJ)1EDKLT$yh>&OQWfcWM64Q-*#+f#b1(47An|J{j>^`4pW4E?lyINetz;_f$chf
zn6@rfvm*O=Cs(kgf$m1WF+5qD@OnHJlApb1Q1p_Fa`%f$kFFo`6pROF>TpRABl00A
zRb@>3N;y~JnrQ6wq3#e^VIvVKAwgue@A1t0JINi*hVL1<;n4`C^exQoxj`93$Z2&n
z-)6qN;OwxEo`-aIG!7Oc^|q7WA7_rwRG)5+7s>sD<LLCv9so$KK;d7wSML<T*6$L7
z0E^Mb_|<0g*&lB_i0=qdyhop9;%Fou;~DiXdXRHESlH;R^Q-}t!h5TvO7ZSYuA7b3
z^daoji+@*VVg7wi6#)ucvdz-mHv_>jL$Tm!!S!}w59J+x&tyo>9^NOIR1RA<hbgIV
z1+LR6>TW^<{0y!N>1@+0^WJ|8P+PvA=IA2Jt;|Z64-~30G(`QC<#xZ?%V=}gZ*y>-
zzc6K0UbSp~bpEf78zrMA?;0HOKD&$V-AT|ydvCz?t^Wvh@i8)^Yh*t@I44&Fd!?3;
z^C`wZ9^=AEbP+Srx^CkLg(MS!go7}=E?l*Pm3_y4zWwmPR_8--VtYen1`kKQX65g-
zMDEed9pn%wT!-=uXeM6%?y)(k(((R0Bj(J67z|(%Khl-`J<or)PTef8-Bb4#6(iL0
za@JP2-766yc3Gz4Hd-92Kb%?^YUwyzVNm789XmiPC2$uR6)oaf#A&;Pa{zz0=C8;*
zLHr9_Z8u>ifqGe{!l1_c^rX$>=42q9!s%$Q3WyAEPi7yVdM-h&3Y!QJc1O!~F3%6w
zMpdqZadd?dnFoBoSv-dm&uME6kKr3V7iVnOP)(4Y>Z+?3s!e5A^}Py5$O^=t(LRL}
zz0+^`QZczlx-`tF_iIk-U~(C<r!-hzKK)Xe?}%S8Heb@G=$vEo)m#fQCNH<<Owr~i
zsEUB0J~ax4{;4{ZtF6werQ-@|994Gd&31Nnz+<IU7nO2d=$G0r_c+%WkBn$d#6Sf2
zKESJacl|Ro+}|Lq6~Ul$lz7Mq_{%P~2VG7kniM+(n<QuL^oTetzK%ZX+x<oHACQtI
z=eRWwkO*ARRxQWLy68BvhKVP|CRQy`qx+b6LtCy=ELiG99;i!`*!N-r7jAD%%kfn0
zf+9MivnnRh)Z9FhCQu{RhnCu44;XMkKj&<|gRyePpAQ5SWNZP=jD?x_?X-9-+DBhb
zf7>D`2l=Fc>8{;UBP+R}A<*`cJwDtVw^*E0e0^oS8P!0)C+zL*1&4{ffvT6G8{m1I
z?O&U6JL%J_l?X?yK43M;WGqJPsV^T+A8LL<L`5!FiqJ|N85p1wh~L}uygpD5U&wUo
z!hi3f^JqhN-s}b6O6FE~y*swvAV6xHn2=%i#RACK%NWb_AKFYDJFbO&q?^2n5fFki
zyxf^}YEjy|^xLQ$!n*tCinJ%qfSpyTA1641Bu7{1i?O}f$X5Q5TU0+)eZoBlfj6ov
z_44wvNP4~HqS@aB)QzLcpKGEU2GJIbc#r$bhle`~5H4%|@9tLd@WV_t$Frm9ZZBsf
z-x3fH-X<r}_L23Qs2I71s}w8sn`UKA#A3UY>sA|Yzt@bskSN$u`Btw>Q+}lWdRGx{
zZ9dA|?)7--(eR1?8P_9{Y2MjlyM6Q9I5}q5>0003STA*{*-!yH4+$<1bZ)X|rdpd1
zx4CRPEo-E|*Oe)tE?`XM-`+{4yoS_j&|N;F(9_UvbwjJ5v<q|!&-gb*NHLFNjyvuQ
zCwEu~J`uAzz^dtOMUo-@R5q3{H8E2w)v%pAGd$bz|3k(yFxc<@a&QkSt^YKZ)kDMc
zs6%9@!uIogbAQb{<Mvg_YTfG&d0KdghzKKzgwV=vy-xnt&2JomW?I1K#<RDKz?>zc
zTx0(d8ZQv7K}?78l*oONYixM9E<~DaiY#!7=WclSo29#GP`H>zdXRQGp9~(8@oagI
z?IY>2m^t)vr_xk0pXJM2VcM;cW<(GCoB0L297bhPnK$DxS2e<QTepLX6b~jx>5zOh
zSAw%`D10w5FGt5q&tU#oscx*-*%#D9?z|(nB1nyuu2Gtn%=3wVqubL~mBf9>#~3Lp
zU_#d{mOvH#ar#2kP<%ep1lxgLU};JA++|~BMz7f)8!I&L$<9TiQIQZEnuLQ<<UdfQ
z+O)^f9Q8YDiDawQHQ_oyCgnZ3TCqxgX<|EjnIL{;vwqcimG*w-QC|wOr-$zj46TRv
zdr;QeCD{D-i%bUH+R<Wzeb*1Tt$9+o_N+m`TDbKVymYQuZ9O^IkWs(}P0|jYN)yf%
zh3PAl+A)APHZ3Q9kN8fQ-h125qS*--g3eq}Q1Bq}fKJN4^^wOQ)$Kt~SocBTGMAB5
zN>MuUSBR0fR|=v3NaJhN9l?O?*diH5?iNCbhxDyEOFR3+Wy7D1>i;?@zE?_?I;*K)
zh_5DsEYfthDsH<bTNePi8R>9;W#p5Hw9Qb2Q*zhnI{4yor%9EfQCj?JP*~yLS9iko
zrMoPiU%+2Kx3KP%z3ev0GIzIfhlo&KtDcijY<oxBZEfp52SvTy>{#da9c}DSCL7{r
zwB#|<u{krnhfbCe-vLMPq72TKtlBRP)wcyrS<ci4m~WF$?u33GJd$&(m*O<tRuEHl
z43}6mo~q?qMz|*63-8H3tZhy~g*YDxIoy@unk8^K!MB|T6sJE#9teHQNHwRf&PKa`
zE%400*z64>5;VC3Q(l?oL`I;N9>itn@|xI^R&v`rJVby02?HfpGQ2|DKjn^Q3ZG<2
zu{JH5QM)=%JJf8s`Fkp8<KyU5*J9ope+VOFwHneglHf(GCYUr2d(T?!U}_|M5|Pf=
z8$qNqQ*$&oZrm3}I9WB>S2yd!&<gDp4wFH+(kPCP_|t3t@`&Q|R4EUWRZ7;E`N2AZ
z?NSC7gWT=1PU%0iXY}Nn%=!aT!(&^uoqiZNq1_)8Gs;$dQ|L6Z9pExs1iKI7c)ELf
zj#nF2C#KjcO`Z&$INE)Ej;5+wDMz{N7j*}7)lN!e-S(%dCc*e2L&!~G-qB<O07eFy
z$j;xMXO&(koc{~#+u@n#^E&GGa}9g~<D*?->Neon`-RH@(NghWMZH30i(x0@oj}T?
zDa;W3*6fI2HH>I<p*Lx!(_k}<O2tb44N&ujQ#dJiyK$o=!ikpK9JyWM+SDinJokR*
zwo%drsl=%0^HaimN10RprCgVt?oBBg2Qm><!t+1*$Xj&6#cCORJ`uWvl%Hrn(Xi3n
z?%yHYEkYIvQ?@#4%glL3udbXN-YMDXu4ehXzNB*7-&|ZQG+BSxhOJ_VGgnA|8_Bqb
zW;UG4fp7X#A(N+ENoAYBdqRZ24c%=uho|mO|LjLLE~}N+`+DL<VQf_e9$7V;mFoG@
z`o#F{K1<mAB^kYzZ{@8Bb+GtK0D8hF=wfs1ofW>z4r#D^=H0uV>?18S`pNbg0gYq~
z|G+2L2UE?`%xvfSaMqC&iGTPR;r4cK!run|rerr?jcz?uIX{oEaGUKO_$M+1?!%jh
zXZtj%D1uI)v!(zVLpGj@Fyz_b0ho5SXgIg@ezqKbxI~xYbvlBozVI7`0Siko$<Lyl
zDSaH^7_9`J^P}4(mWHXo;K08v(g*vieGL$c*G%8tK9d^xp`S}r`?d7>KZe(nQvM!_
z@N0ivN4^&6WlfSJk%fZC3x**jxUgX@;((zf@fRt}h5zh}fE%d*Hc{6he!*A35Gg)D
zMoOgHzl$92(4-YdH)XzG%O#Fp0{^QrK%y`iqD8wUBd?&z9ooai*$@;e&2Zszccy{=
z)84xgKcMwrvDiKq;!jhY&M3Zd6v0NI-kK`g!V0B2dLK|58Jl;(+>E-F{=0V+8U^lX
zm`+?cq>9KjIiMrH0#exgUCga7)zCJca;yj?&#{REO)@o3&iK#n!>A{<O#DP0(ac37
zKNtaEAQ^=;nw6(8L6qW6k0Ev06591P1SUTr*=7z&|0(U`6LdQ0w~&gyNU^^~qzT!I
z#bfh*M{{TBM4Z%i;7UM5SP5wx?4E*MaVattLEY6GfwH2j_8|Zq)%R>)`-^J|?N(dl
z%UUaQ^Ud=$X*Ii+e!Xk)0t*<c_)GiQfKzU%*B7xzod)We?jIc7))Od#Gk{uVYhna@
zPV?czY`H3aH}5_vRPjQKrah@aCa@~*5$yTB0}$Rf_)(E@=!E5F!zszy$w0$jTVFjh
z?!1<*y=mrrp!6>S2ZNitA)#ESLc0S#04|SRCuX_%v$awu24z~H`M1%>l^zCsc@%jv
zq!6u%Tn}_9_HTn@UnaVx0o}*_`U!W7g#X$}xj8&OyqI8o7>GS@j}~FvN0e5TDq_Uq
zd2ITF$>j~8STMWWzdu6&5wXfx(j4FXEb}qR0lH5&-1}-z86(%xY*f42^{tc&jsIJ)
z8{V<86=9k@qwdZfy>#yS!VadoE_eOw@&7bqkUM3>v3P^gNY#RR<Km`@IGb4iU`NXc
z$=vhS9a?ZM=y`l6I3U0Z4JdY2dM9ksVD&t})?@lFzRm5>tcRY|+<B@@!*TJ(HhsZ|
z%?!=RuThG9iAL}C{uJwzs4~^C*^XImPz3MSyUuhEmw-3q{G6`ZFV@$q00G^>x<LHr
zbgbV0l+xfX3}BEka&?(cC#qzN+0;U?&fqpB!WUb7PJ!cWNNzaE$xO!VS6jGOzRZ*i
zH+>!bsV62@ze<kIlj>UAqs^V>%1|&qJ-24|)?Zm$JDDT?Xu3g0y%LTlRQRQ-1NGAE
zur5@Y9+hmruS%~X-Ehrmtq&jL{tOM-fJfr-_Vm_mO{`45h!Rhfjg^~#$I8UcpCZnr
z?%<M;z%F3Q2cu{BnVUtoNjUDSku1(P0MKi%m;Y=iGCG~n`TBhFMhNNLKMBKnbFFNc
zm{s*7mJ!8q+LF|L&zFyEDzWqLE0k8r?CtO+$)301mF~m8jF1*3=F7;7D(f`kO`w-R
z<SmZg|7*y`9v+VR{iCS%wPhL38*amchLL}=hJLyGQ>Dx!R=R|&DxJKl5m^70)5^le
zqc){SWVEmB%0BKKaZ<%gua^ZT!zGT&%gDSz6&aiXrz>-7q&sO3bCd13x#L)M&pcs#
zZ+{X7fhLQA`s7r(PMyMk@)&YYKcy&_U|KS2YB(HWeR&j4d0_Wd<9W}8ps>wM^PUJF
zdDgq!AEiV~Dy*$sAg)Cfup=Q!Tt%y70IrD<?PPQvHA-`CtJ_i~|HuXO5+NZWO6kI0
z#wHediYMAvbV>u!xieuXo&OXyn8eY3_MDlBFm(}&^!_Q2UL_)npO~1;IteCiW4Z11
zJKzEmvAG{~yN?07I`Obqx)Nsau29)#W=0Yxc2}HhhSXFvou$YQv47W1%+19(<!B4}
zg^@%Gww7fORpL`JkbDMMGVNCdb<vC{P9r3!vi?!Cy`4fn!&zhWWK;g&a6&BpJ0ETw
z2@2~29d(F}$k69BrV%Vt5kp@#OACu6op%m?Em8_H^)J8mprz$(P^2bWF}uV9{tf(r
zf&L->Sk?fEV^SH6cRST1SH%EEA<<7!ZTy1hwIjaJFc;oa+opiV`0RdLQ(s3@A0G3M
ztZ&V7M^7;x*6D-tyF4SMwll8e6i?5rtnjtPkhrxblRR_Z<_E^Kq@;IuQ$rs9ZtSEh
zWEd)2)m6OZz-J*wMMF3tOt~Y^zvWp^OO!|AS>HwZ#dB_tKwp~nof`}S9DF5J_WnMH
zV5Fia?(V(3jG}Dt5IM3VbCeCO%@zVz-UlX1ROVnd8zZ&;79r@sh88H@eDcx;Aw+-u
ztY<M~#T;l9noG%Rf=-j_3$Dm6bi6Icl``gnPNt9hD3m0J!6)LyGX(?cpQUm{4yFmY
zGV9874}A~dQleMDnwxzz=BMUn3q30J0z%xZJ=Q_OKSSP6QoZsj0&Wto4-afY^y4od
z1H>nbbzUXQZ(jPKLf}asP>HtKt(fqmEXo&Z9lkkdA0b}IQ_aT!QHEkBD=`Ps_7xr3
zxVy`#?e1MH%vw}tK@=6CZcc7|-OOfH@>e$z2%a})c?6Bgq?pR~fcCG`(pu4Yi+=M?
z?ALLdK!k#siIT;gSI4M-q%jss?(u{IFzd(BC(}n)c&jp=ILYVtgZ!kvKl;qr3pi>k
z4M!_mxjI?+A0G$ALg4QcQfQJte*U(@j~bw<Ff(y|-JU%PC7NS7RUoZQJAUy4=<%I0
z1ijslAL<Bd%(nPOVT40&8ff`L3bH@T-8xloOvXWS(D%ezjMibk6+4OJyx*B}RA#X2
zo^)MJO$fv)-^-rb`xPMmZ`^!D<6*rf#PXPg!2qFc^iCn{YlvLo;$hvH#8FxeCdbQd
zkbRDL?s&|;Q$ZCFO=htpJwQu7VT4c@{DqG{Zz8@sBj1LY0JjT{BoHO9`4@sU&l^{Q
zeWzqyygS~ryW&kCff{k4GsB9r@Cp4BYhk6gwpC4{@pNT#UAy>goPZvB96>ytg^|p*
zSmip*{X3J)p`Q$q510FLI&7RpPc#Mjc-GP&C+EKuH*|*LY}Qt;HaEO95!^z14!FPS
z1W3#6@W_>YLp=B)SjR2>-%sMhQoBFWz-KBez=?f`PKqE=-kF&eHZT}0?*Do+#1pSD
z-9*VLc@g<-uajI=b`o#6ozwQ~{l@k&U!4m}@+c$M7O5l^7BP<#6(zg>la>m@G(U8u
zF@jMF+&;O1*>DDD<Lej6M9=y(QE!Goy73joOB8uk^?KZbpWCKf?fD^7;@gm)^r%<y
zDwAy$%h7@n3@0=S#pbLpx<k#2wBx_1eGGCeLvCtr)Q3h<X!BLZQFer)%}X3)Y@mNJ
zO4YVq<LgEyKO$o>QPFMz?1Bv*@J9=7IlP_EIr2w9yCEJ+?D_JoG0h$&pXGbrn6{iw
zA!&kzQPuvKi0R2H-487J_?jW2-N@5v3Ay=y+7I#7yTQ6N!54q;ikqtXJA8GSKOld^
zp(2UAUCty-mg^m!k4mYg^!dd?y)Y^SLz7;h1XNqF^Y708_9n8{u3<fd4d;DB+Uzeb
z?5q1KI5BJ5RX10hnDg`gK5#`Y7)N!DQY1e+M4cnLT39k6hGsI%b_em{sJF#tWGncB
z_N{zHwkbX%?AeVqEzU2XE0fRQXfiELn61#GB)&$yk_;mx$3b+lTTDKs5$eIW3uaDf
zd}r%0i2h!BU||Rak{Drda;J^s+k8BF$PPvETrUU%Y~C{k{oGL65(>0Cm-le@II#9w
zIlmBvR)66ME?;`3RLnnUGBfv{_9dc8$7?QKXh6pk6xABUsVM15Px~M89qq0E-Zk9l
zgfZk0D6mt%ep{G3v(j5-(G&B>=Cl7s;aHptJ7nfhaUPtGDwHiuU|NsKr&Nr|so0)_
zEgR}cRMXn59<}V5get6|7CiRXC&l`l{KEW9AQ=M9!+`VvK-#_Iw8Ht%Mjwn$@(1A%
z=xUjU7|n)~zHM}eMBS339&i__wv1#y2b;(c#11p+G#>$hbqc4YMw`SnWpD&+FuaGG
z8>ih|5=v8l&W(?}u@6h-#hXz~5>@TU93DXA#Mp9CO)9s5BJZ0IJDX!%#PyqbD7&-7
zg$sJ0<F=^@fkk{SOdlJ1do{mdJr08&JoyPF2M$$4N^OCjM52<$)qU;^__R({+kFBG
z2K{65c31N<z0zN(WN>1OT{9_Oheo+0)~KwGyE7#bSdf*29A~9qISA!#<ZM87^)H?o
z;o%5qwPf<EjUOW-JxQrQd_aIhxISJ?%s2ilAu*CH(07__;41E_tGfg^<-ghmVYIdd
zv`O-P)@W4;uLzu3|8uc~mRn@+Hy5PB{4`^VpPAM;`))JuVmU~!vq~>Mm}w*HAN6@K
zdN_^S`P<wEHur@IP8A*)LTrsqGn5!IK+f|&>Wp{OpGwCwhHI(M!2eS17JqxcY(nq!
zA?0aMt9B@C$XGHGm53FEV+Pcg@aP065fssTL&fZE4_6B{#-mY~Vi6>Q^dB)k@$ia-
zu;?{k0a~#{1fkpE0u!=zsKfR@zs!@iW&{K{A@7Gq6|iqE)%YOx@(QE#Up5Ih-Ihje
z<ZlAQDwWMZ?~2}|xc&IKhq6pdSs1T^i3qEc+TzgX>eO+{$j>-V<&dpR(b5`L!@&H3
z?g66|!PJ7=NAz_Uco;8y(0}*|uiZ|Z_WZ+lZaavHfEZD-;rfp#S>U`>KFKD~C8x#N
zfG@!8HmWjF$=O$khPhKKiJRZBQAM5v5M}rWgc$Pw2t}`bI5Fb6la}v;ICM6fSd~hZ
z+X(k9Ery<1<KZ9V$}+|}t&Ghdx4DfA4SrHDtSe=b-)E2S;Go`hK#3WIzCoeM1yxgs
zbV$NZ!q!ZOuP;lHUISN}l~RX@jjl~TQv82L;?q-7EUX-rVnS|eclLh?42OGLfLB-A
zjvqVVd4FN*>FEikz5^J*SsnFij3k`{t)yMOZ}^QZSRI;Lo(DSj9}?<3oVq21SU#J0
zV$8u=GI4n2?c|7r@gu>7?XM87$Dh&J%Kvtl0CyvU56buNx@#P{ghBi@<6;SJRklN&
z)imUFw%Pmn;cJN~oY6NuNpndD2HrDEE31Wi`9-eRx`CD^s{bCYSDAHb4l>F75H_`n
zQkbi`T5jV(+#)9V!d$w#O(JdEQ+=cHx+LYo9E<nx2kif2F1?r{spmig9G9|m^+oE+
z!hQ`2`t=%tr(?v2J@ycH3%yHDV!iM8G(+teVzrsie$Z>+pZ=fkF6mE#1ym6S9wnEu
zS=Cj3J_)5EB(SogJDOeSi;-iht@xw%)!JXoIq#tVz8&$+6MP8#R&Bni32mtz>ISQ`
zV$k+%0{DpX2=zvd)DaTpSH9J-^kF`rERIIKN;>f_$1`ZYG4M$Xal3v{e@%Re+eU6Z
zb^ky^Me@msjD}u<PSb9={rYVEZ(k&Fp@NT0JuRP0-<!4T)LGd?7PwajZDrkp|EPa-
zWP!EJkaquuu2hwO++PZZ%d%!z853IL%zd<2<Ymhg`I<AfgGTKB*@-I(k;)r;dA$^9
z1Rv($x*$2~aYVDZN?#YDXxB_vhTyV#!zDlP!B98xq`I16Ef%pfW3oRUDOQBS+s^|>
z$%gUfE=wBv%+Syfb!Z}o?NaTxnkW41<py&D5EVe2_EXqSx5LoVPP<*j?P4m?SA4O-
zXLWBpx2sI0<joTdy=J-R_5rRyHn29~?-#!FJN%C=i)v;NuJ6R3*87@)MY~bttikmo
z;9i~98m+@tuhw(GQa0AKRDc`Siqoni+7v~;e;%g$MFE=#V!L<LjB_=gKWD$s4tp=(
zKSku;Sbn%(U+?kKH{yK~Vdm*2m})k(_(1zP^YPLFgDRz|xGCCCSxf7k)@r+(wV7q_
zHYSmZUdK1D(G>vz9U3{8;`6?^yGP!|MS{!h^SRs0R-^E`xElCtj-Dyxp-|rpR_y-~
zF~LOIpNEO_cx+t^TzH!fAz4sd!Ke=?C}?PCP30DXD}ry&-+pn$KBHk^K>h*zS?HgB
z`~z3P4e^}IG4D9y?(5)d?=X=!%kv6c$6}qwZ2F?h&(L*j=~94Phb`&^G{P=IT!K1}
z(-UjW%IKN3hOQ{@GhyZ}@St7jtXJ=GFvnVy(d`8LUV1^_@KF;&(TB^Uhknr5pf&vC
zEif4SE|EqV-PYpsmHkR+>Nn<~Gyeya`^$dL+(Ss@bv215%d4>xsw{(-0<Oo)<Xc>c
zG(<gDhM>8%S99p;?dh?@`AzdLXm8)1Gwu##u?sWhe<-{?S?1$ocm$>u0I7ncKr|{L
z0?e#vYKfq+_ETEhInZc>IQt1hy<rd(Tv;9M0K@vzl{T2mE=q($AYuR0Chp+CMt}@V
zDYpR1saA|-8TeDb%@ZyN;I?29;1OEiS^(L#mW7t9g)3Nk5^-4|?lj&t7P4dvcC%T_
z9?EL6fQ4?I!ZPpFHi`uJ90<8=_Pkb!s5ZO)B7mF(D<hjX?##eOIMt+TyI2dNdp1B~
zO<hXIyj^-)3=kvH{j-;#!cs1<f3pu@L)na(Z??&qn8K?)k@)3{)nv52QKM!7ljkh4
z`W5kOycS~tV+VY{OSpuXwgpFs_?t|mxNU|`P1LQwt4zvL%7Jr^Kb6pW9{crt_H~}j
zLg0l}`r|*%z@8=Zc3_$o*4MAj3_Gva?Tr`ae)EP>iBq<8cBrc;5qNd-iLABZ9EW<U
z5yn;jQwK(6JT5zFZRu^rAz<1Ml<4iB5Ai^4XxJ9?V*iAT_4zsIy1cA>Fpe>IrfA+K
zXE|bY7Z5Rjhy$YKe~D!C`+~P#u<kzq99&0MM-oAD?CaKoB^BVj_C=DOE>>11HxcZs
z<Z6Tm1OzlDePYLEr<PA<8f<qwjTlp+RhO#NZ+ZYE<Gd{@V);JvOCoMt8(ZV!{e8EW
zA-6Hxt!+^E%vR`nfLB4H{4EM1<F@|b%6K~@+=?rKi`-tUM6JRIXn+SkV!Z1&30#W0
zVcyb{`if|JAJ?7NJquk)hip;_alGp{{8s<2+uBKuWBXxoZ>;LCOLM=Ylq?X%U;Sk6
zD1XVN$Q?=NlhnRA1OCzT&0d7I=jn=-;C6J8Vt))O!cRU2P2xeHBS=19W#D6s8Qz{^
zhqp8Z1Y^GX8P0E*vSf6S5&MDBn%nAS0i%IPzFJowRGttS8I%m!_Aj#6cO3>f&{-3o
z!uG_Q9-C(qL?5bWB1-N1hRJ6Od+wp7#)HcA_~O|4S1LISRbGe81rW*V2rH)CU0s(N
z-EzOx^kRhsh?r|>Lj)Rcq4@bd&QbCdCB93Dn*^w2dtyJqkHpxDp5a3U7HSj+dS-|C
zNjESrH@h4H=6G`B+^2X5+<z~H;0KZ%+a2&%E;l=Gp1b8CcN$g6BrrAs@<sFY;g2Y`
zDefbHH%e5{BdZ12q(5XBSnI%tR_y;u6Q1h(rUf8g-Q2`20*aIA#8YBoj7+R>uw*O>
zqOzj4YE3?97UFx0Pp483#?Vrey?3mj<;VaYg{^h$!3#P}OiU94rnj*@?}fg%Mpt1<
z#ddOcc=<CL8*l#be4_)=jv!`F$XL}Z0-GE^7zC9B{-riA7hv6pFU4q^?)U?QJ^<Vy
zyc+qAhvIZB;Rj4lZ-4*KY8>CAvZL5S1(k&N;6>iPoj^x%cXxN2R01$RF55+=gv!o!
z2bze?e*820l|}*rOz9?yexY8{XbaLk?UDYUeNwWCE;qGn$qpf2p5E>1Z$w^b_2}O%
zlc@Ujet8Oz$(`H-z#lS7VfyQ%6>MFAoCPpoA`TleWvPU6EdZ`P;4GTWm5mI=X93Qf
z4)^H;8?+VxwmP#kH!rNLM2}A^PcN?ttqJ!Z{-w^KQK>&{=m@E|Y;qsAGB7YGx^&pc
zW+jj-(r&O>tai8_1l?>*gl}?uvR|}cNR{+G(suZ8IC%gn5%)VnLP8xv`}yjgt`QLf
zMN$<+PIohj9Z*${=<&~1sY+ff9MqLcewJi1XnN{+eR2HiWHDWan`F@84g7;Uds}lk
z(#XF-(wrFx&x5mWdWD{|;R^msK1}8a?4NUmKAG*$4>TWW>{r{L2ZtFjINdaICpau;
zsMr}U2d^0xUF?Ot9ys>VK<1dy-dQ#<a?V)Q0ydR#Z<wEOfm}w8x+Old)?ADIDT#nb
zKlKGuY6A)hSEJkI4!DKJqsP5`U%WB|yztgYKbq`C0UZLr_eBy?w8X#uey!hMMZn!R
zTds{T<5)O)eXv}rnW+z6c-4|PU`;w+uDk_~?c6`PK_~=oNWjv4yvn%GPYfPpoiTiX
zS^(*I3Cs{eQvB6yRfI+ssi%APT_82vx$HMT`O!q?2G(I?HJXZ2i#zhEU9YutlQd!J
zzd_~~P*TaKef$QPI${Xu%YaPO;rFb;XaG%uM#_(}zYorb+~7z6YrLjd>$#KO{JRnu
zPRxlH@VLz9f`CrE<fHWJ2Lo=bz5eX+TnRB=2K7={(?}^Lv{Y_85)LP&zci?;!L0~x
zIQaP7_9w0FFpod@(%PI4@l3oyUYtZEIb;@Z#9+@cQ)!@dwnEV1tbcq{(g2}7$Yx+@
z2v)N37NECC_&v`+=$)w7`np)~Bii0#zAXNyI^d_+l#J}_>qRGFdnf9#ChM6W#i(7I
zCs|1%o4^!pBE3*=O+<ou^4#fhf3O`%D&YOFMaR$BxC(xA)ppFS*Ys7MTz3337L{;Y
z!<vfN!-K`D#f-fB$eW-2YU+y*8uSkz`!0#r!bUa}mD9$Pv&W9h6_Yzew>c|O@5A{1
z{!{u+ILs~juv*b67jjUF+Ic^`_jIV+_I-L}W@K_Qw)&L~<g4&|-?)xtiNv*?^#eEW
zUDYOUU4>4i-Its8U1D6^=|X!_3~uSS($j}(x7R>O)WNcky`|Y#K|Gql>v7R74Q^ZB
z>molVsD3(dL;wR-e5o!o$0xNcmc5zsR7ifi+h)NkLq{^Z`2h#7kIyT+`3R#{t#BM2
zq{=8Tw<Z?^xwJ$auU-7d;<Q)m$j}sE<A?z<L3+F{1KmR=H(~RXy<r#^0a?DA*c&c3
zi~oV*z)H-1?l*L6U_0`1l?Q@Uk-mVtAN`xesVOyf_8gc8kh-VoUD^Eol-F%=>-q84
zA2~^+u?*5)0-WgeT=g}(Bl<OFsEz(4kb0;2R=3L(PU{)KAaEv{B|t=hM|nSHFWj*%
z7Nl9J+~#t+Lbe$vlMgP&r6b^L(*!8;uPcA(CJTx<O7f8t6_N!_?<ckas~Jui?V^9W
zhf^oz`QrW`fb^yFc`ysIdUu~;Vqjw66CoJ90YN9Xq$@(-j=D*n-F10=-Y%KTC9^v3
zOo3pfAC35ka3Dvr#GvpcS2D6>rVNq`2`^u)=jHpvZ8c>v@`FbfpM~20jh${=wxI=t
z!@A0IzyZNL_++_dG)16Pr_j!?%MV@@CPXDBIt7|O{33nw%Mu7}!Y)+w)uz_GK3RPP
zJL1I#yW5gO^=6xW!1T0TXnm_7V$`chfKJN8gHQhYKGd#vM37hn+tc2`3sbV(xo#_X
zBu@e*_Gz9VoeE;)wJ<*X)~o)?{U~ozIlBsLvd5db_o&+v_kMN714M+-6PBNx#G1Hw
zcwDu+gygO+^U7wJnlT`^)a~6m99$L0b;q%hkOuBl0#BYq6q}}<?mh9t5mC2z-+Lji
z)>Gg1mYd@Z<a?D6wQMD&-3zD)mHED^8<{4D)fF!weQ)`83ZFR|84+oxRY~3mg6Lcf
zPhYIhNt5>Fnzd-qT#3fOv6h`1M40*xorM1`;xruqP9-EIMw56pfsRhV;~Ew^8k@>5
zJ)L-u{iB5?L@5{`DS(cil+!FuqWqh)b2+5$z{mC#*%cRDxFGHcu}((4h}1|WbNh`!
ze^Yvh2}_Mie%yd5sF+5WNAma(S)_up+YLjos5_B1CWd=ZQN+c{qFLVour&dSME_%y
z-Es>mDW@(infEGr+R>4X6j8cDFv|M58;Jk;%CfHyaHm)sOxp@JyXajqc~~E#K;`9h
zuwXejM7O4$JKfmQ7<*zvLL{nc6%VW>NVj({%O1>;$Sw#PcgWC#Ce^K|4p2*oJSY(g
zxrt1wcqma{q~6V~oAEjC;Ur?r78+#!9Q*nHRDAZJyBJ%i&JsLp1dWtZJfG;}kk|qv
zGlfpLe;Y)u2;dOHC5p)#N<_Wd1AZ~(%<PyP#mwwi9Zv!G-t9D=Z@NMJV46U#RIc9f
zUc2`vB*ee@jmR&wNuqh?)6Mph%*T=!>X2N6fnyk%u0r(lb!E@JsVZ!>02H(J)}!3M
zunczVk+=a>+Q(B^`j@3^abdh#izTDijORWy(!;STe=UjxDM2e_-?V20dUE^GPB5zx
zw(6uN$>$eljbm1R*hx=aBY6>Q6`e-{V1zf0a%w1v1J2G)0*$Y0Kx6ztAq6plXvPMr
z$8l$ffGfDoWFSUx`SEC}E*6nBxH~|+I0@qixCEWxy+A_-;zrViJOss|BLJ+m-RWfl
zbXU_doY_T7%OEbUe+v*cgBk^QXKEo#Ps8fo5aM;{_v<k+`7%2ZMY8g8a82;HpC4e+
z^RV79@W^Am{CG%XcNqZ=Ju}5jR34ZJq$W`^3}4qDHCYYf6v_}@R==x?+vO7Vl9D(K
zcuYisH`2OJO9f1+3dBO3c3Yo}%BcJ?vGK(+euaco)&Ac4_z83zU#@R2D|PFt1LJ!h
zvu?kjqM}ZV9MnPB6dn9H#+(C&22;&)`XHtL!Ea{V9CyKechfDMGar@*<kyKTx`M7p
zUsNbq1L1VZileYTsxfQ2&CcjaqLFB~x!3vmLGzc5B0>FldOZitpqeq#vF}3yL&!6X
zk$HL~^@A9}naJlM5=7Z3o=T*zTxO4v7aSjZ>pAjhC+c$c<AUn34;Qyc#H=8^$!8Y#
z!{cH|#FUh|&yqK{N0T+`sT!Qtvs0{2#4S!XlkM_gWMz3f0S+d1vr#gyA2X~RY_MX0
z*QZfw;I)S_UW!<IICla<QNhb?JVvlqXdPJrNIAs3E}xu^l-h!>%ZAE%osT(ecWO&G
zOWda~e{?RoSe-h~?jAMOeEH<QWihHR@Sn}{WmKPkF<TFTO|Elj$)+m@ZrQ{66x=`I
zb@KNY+g+oesnpZe)$ed$t`}P*X>&&*;0XAz=I8q6zx&8$zQ7bXb~(?)5@Aw@caZO#
zc=ZenGM!l2s8S|{HT@_6j~2rLJa=SWQKBT7h{1prv84YIWP(J8Yhk>R$}9*^5d}gh
z9vd?mj;W@&ua>jLdMchV?S6uheMEwucOZb2JQ`5uGqwc=Xgi5usn=9v`9V1Izc{AJ
zCY@bSR)7=hFH2o^J2|38<1i>w{6|?gd*xDDQLCqbhpjEoqpkV+WTk@-7`8D2qeLmO
zDVbCGy#L&Rr7BzJf_|OL@rv`^nxQJYDqiSb0)-l7=-X-{ET8)cQ$(x26JlasWddY$
zL=uiAdti75P21J=&$MELj+cO9?33j-Zs*=9L70cmd0-{5o=RzPIo)_6=zkUHuw^8?
zQ?`<vZCDtaH|?6<Yf3Z@`ErT2I&l8Qe87XVBuq`7rQuxOEQtU0o8>3G@;g<zzMO5@
zXL-MsE&>BR%5tfQ&kPc4Cm=V<6Xt#B%|G9#m?DI!dMK~@P47RtMz6jsH>*RIvZ3-C
zYD@1e=uG%YG*aw4!PEA?Sscb1w-m>iIsNfo0auGhoYq%Pv%PV|96hSlefzA5xvM1c
zrk;sJJW+{@E1B*UnE%++V8C_1OJ@`Ezd@Sztb^ExL}wS{UHuU18}z${3s_+V9f(Fk
z$zTE*y!@?A5<&?_9vOyl<uv5(-Q55Tcfx-^-+|zLY<eK%PAjO;b?=Pi%$R})pooVM
zyTgO#E%%|JOV-tK^QJA1)^7nI{{(lMH)y&#aiWa>Fn?XEc0+MJ;xn?YE|YA*!S}T`
z%vbXu%8&0jqUEq(m}OnEptr9m*R*O^ks>~WY)hi2PA!i3dTq;C32GEvLZ-`qn3sX!
z5`~*Jd*jI^s4m7K;VT{TUA;ND8R9UK#b$EYhu7)4_<ErkUOWkNo;73-VX(}aR_V6)
zqrr*N(Uw+r$b(X^A3dO`A?Jl(sUcH?DQLY@IhR6xk2p<_KOdW8<pD6r7wfnIEDuGZ
z?9X7Z<O}o{$K7;|ty4r(nN<nSwcrw|gkbmZqeX4|4JYre#<VO$?kg=GR#OLWB&i7l
zvZv5WtgC8T7JEI;jUyy6ur4IoDL-h5iD^t+{Tjfsoezi32}`TzAeN~$QZ$s|2p>`E
z|Dh?LTDbRufx=5X5lhT6e%z-~OMw6oQX=hL=+d>Ow#0>8zjMa-OIxvN48q}}dl_w#
z;W?w_vWd0-*{LE}*QpRCQI-Ct%KA;Ua9i^CM^x@;FGuYgulhBat0dKEq1;g@kXM#t
zZd#<PfpDh1&|v(JAo=X8F5v}_oO^<JdP4aSMydCSuXT;-K_*=e7{5xLLksRuPR56x
z7ARO5wbUku^Xt$>mr%3GuM=Bo7dW`er^@Rc?W~5i;ARY);+YL!{KG=MiWL_qis*Sz
zU|#gxxYT|<3hqx9z)&pfKA%Y&b>**h8aaZtK@k&#TY;w8Oho%%uD~mlCzs>>@*R&R
zRw1Wj+HIzQd<6}>k_fKw6lKSEU*DMG$Em8-iRtsT&2Be*qdgAdTqQ8ih!Lm!-lc5W
z$5A&w|JU|qx@f(RqNBN8qRVg5c+wbq+e}tJ1(|?ulEDFGo=4Wf*!chB351|5XkeJV
z*6)8~e#qUechH|)PEQ(tt=TjYd_ztv^7`rY^tf@u%qbJbFv|zY>-Qpybgffyv!uYk
z>vX-DrI2(N>WZvO?haY-mel{$3K1)u79>3}G|Wn*99PQ!Up~PF%tztmukUnDdlYy`
zdD{K1FTOK#L{k(-@0&w=(Ws!6TX(d_K35>TRb_dCysppQyM+`??a?nfqPw^xe<yd?
zSVv6xr4+}}RPYroFad0;#eZJ!@N?r=lc3W<&lqU7{coK9<ml^dG^wc{N#M=qBtv<K
z+a`l$YbjJX@$-g#`8SQiV)J}u6E^#u1uW*LnzL(yvrBf~RryM#KR=$?G@6d3DX7ZF
z%%!9H<5Ji(p2j(ccszIRYQ_)kKK$1#Ng0mpF*1IQ9HDqS@?Q=u(bHJii28B*gBn+5
zD;+J3o=li1ynMj~TB&_oUCrTwM+i1r@K}IN&Su5h1Kd@lxIlgJaI->%wOyYaKdG25
z+5^gxbFGfp((yG9HU87}XKs#K-?yeRI%g*I#F6r^0vBPT#WR*pyaIyONB4WEF4*lI
z6z^qfbHFQ*=lj2qTcW3!|5799IAc@h%WV#8*W90$kk@$_e&fmIW6oMVPIG|xBd<RH
zfb2dBhn>uAUF}+`l!zTGnzib8K4qtv7v%bRQuw9qtIMHat?vhv0c8Kn8iDViANPG9
z&(-<Q%B2Cz`h-S~9~VLv4?ifGO)%MM<z=2|%Dquw5O$yEb9pOOn^}V9ctXYa`GQN3
zZ%>if-lzsSZxkcX_sK?i<M(e2KuyKb5tjOz<Z(hh()yk!+wb}Z7c)o5uPH49xDlDD
zXRGAO(<Aq@Zx>gW;~n--+WOx0JwNt5O)-vbeJ+H(f^aA#bRT>@uDpdjmpo%%rfL2=
z=kxYp9DelaI<T6pRo&L4&X?`)D@=NOQKNm;wCv-mT3P((H6NZNh!Aqk`Qj@G^P*OW
z1=57W8aZM~g_JUJ1vspR!3B%GiB0!tZ#I3PzWT8CBCIR7bi`9rci<_Z3kwSi0u5rS
zw?xV{(22N?K*JRGJd0r(3fg)^AG*iLsF=8F^HGw)3+psKM`jBCAJtFazMrmu!a{fO
z!f$SF4kVx|;StI+Vku^DY11dD+*E#jIl5OZR8YptYmCjExVfWJ;3Z{kZ@(V=UU6U9
z4gKF1M}O8x&wQ5ncC*mnN$=2l3;DnE?iZ~j8YxfhD~9PkPDi45%lD%kMh?Q*9^KZj
zRq^4|An5vZh5o(QC2DJ18}fv*owa?-*Dg``rz{_lCWmbr#bi0{i{D=VZZZVixh&4u
zTl#iPL5G~f7!A<hpd?yn*?ypu>W<kR%}`Bv6BV7pYB@+X81pwC8AyDa5raBs{j_r!
zC(hAhF;dTX&;CmYmM)dahkUXpe@CSf^2*>dfjP!Lrqg7TFRUm$-ysSXy?o9GutDB1
z57Eq0=kRfO!A%eDOJ~@Iv4oKFJ@tdj_)iWCqd}Zi3lnwSU_K!h`580uDf)&Tge<vT
z(o%-kuY4d^Re8E)R<kZ`A=Gf0(6mB2OAmd*TvMJS@HD^M(pb$iiM~)wcv<}cIaHr0
zGJGpG`0I%b=x<5D{@fDHlj#3?`>LoYyT)ITMjGjoP>>kuE<x!=x}+PVyQI5QX_4;k
z?gr^@q@|m)dEf8*U!1khxjToeS!-t2%<Si3$1lZZ#`y-_Vw430T8nvVeo^HDQM6I_
z0FL#Gm7tt;AP{eRm#XZvxr-@^02*g&n?29eWo1X_=8~KC&i_n`Mv_TO$(++m`q}MV
zrUDk8nu-d<VdG&DS9or?wyJnmn@vl|NN6{?GkuhARJJ^+G2Bn6#2ZmhQd3n|Kbo!I
z0PV~mdH>4@QjFtT2OMsw!$B95xuiJ@OJ&(unY0Fbv-?d2P~Y>C9)oauH}r$}!7YGy
zb672Zb#e-nOn_*)_TEKQ`c_6qW2#biP%gu_u(7kZIP5FS$&CTPj4q+@n*ZQo`N54c
zn__>eG%-HD+Hpxe{f>V`W(33;UL7sIL`7|WTJ>}laRu$p2_zb@njeJpIuZ^wh!2US
zrKFern=~424(Xm$lxUUe9qy(9i@eh00i(<BeA3q44fnHu+EU}aR`XBg0xd1Ab`5un
zdr%<SOy&$!r5rnHh~U)2ZZ&reatnZSK(G87G_QfkEZfn!Xt5fpx1fPwVaq&`%Ob+p
z*Y}Fgn%mdPz~p@QZ+2K!SmV`^>&jKa;N}~NxK-PFkZq&kWaZDAgr5@hkpef?VRtsO
zD2%?3B4`)HvWP~I`2>EyOL~p|p`VMJ>sQXt54VyD^ezv#4t+f!W&>O_z+HjX=FpI^
z0zk=tZi?u&=)ef#0;NLSxP-IB5h6rX3roxXudDEQ^lD#0!aax-ay9_@iqD}uf}<IJ
zZb+OjRhBMVh_J8}CW;Ld6cofv`sU7zL4|ae0i$dxuTqW0+|}`N=}HyIlKkS2jFTjl
z)vTE>cQjwQe;Pl?&dy#wUJkOmPNY0YuiK<Sf)uK|)p7$DKZF!ZJQwe5r9|(WY~8Mv
zoRQDlg#2o0Nuu~#%p>O%+87T*dLCXj_y-qN$8R62&jmy&$?tAM<9@WYvoJkcXi^r2
zYb`1-g`~QZ2jr!-s0m->TbT73TAj+=KTcq)rv{U{g(b2X4(mQWKJdAouYTo>BYD;s
zysH>n+c^`iM(EfAss-#G8BiH>QonPiv;Rb^l=r(u+U=BHj8%^7wIQua-eTPc{k$e|
zr`L2W=4<!<p0fALO)eX5D_5segV_O*73F0}s7P8>2ID8~opdhBArV1oybh-^{*o5O
zmgr=h?x&mL!kKI5`ICHuE><fQON&G9>({}+0rokFl`u~b#>1C%$<1P=fscoW=UmGq
zUE5<Ij-e8i+|FLB%4x+?OIgikkoU!ba3SBPwa$Q<JZ*h|VuM;y14Ph)4iL@+al?I%
zA`T|@e2q#-kc?b-&XQ#9O=)<Vob}_k8%q!qGueQO|J&>Wbf%Hs@&lL3@v{-RPEY}l
zUK>h5zoQPxZhOQB3JBXHN!X^l+YKkDrKP{KGOVe;i0Lw50o(x+h5p=xp&{R31R*=J
z!JDAW6EI#cx6$?lXjmxEmO;H^j5n}h52y2x*;C~yc<?=NkXsA-T>M!w27L|c;kb_t
ziS}g7U-}}ncqSAk)A(Hoi9{Difd5yJrTw9Sv(bKkTAJqdcD9<D##D(K(NArXQf{o|
zP2e%m7YXBX*)srZ&mm9khsmKI?AYffMy^IOLsfl!Vtp8lKXY?e>fNZ>X)ot5%%5$X
z$E{Bw!cR~KqFzR$5$Cb7huYVWGngQg#(OinrZ3cjL5jV}OMv*wmuaKd-egI4KF)Md
z1riw?VLJUYx$(Q(##>Oq0{lg=Hq(tx);?*gw}<<NlJN{cOf<12Nnqd8eTK(oHVkrA
z$R#sV3@Y<w2efz`)zs9b@detO{dg9cP3nL_?%QC7k1q(^19>dGM!%DO$NhdTS$~XP
zM;K4&nYH22U9Uf}xhTT5cg)Ub?HXhCuW3!}o|h@%Iii;0$4g~_eUdHw`W)!}3MP%$
zJxh)*!x2xi3n*8Li;GdAI?=V9?FkbH{k_^j+gn)gM)Zgva5kco^3$jce45JwlL#6a
z^Wwlj!G{g_+M{K{F(>cvRO!whRQ+{*6jYSRbY4ijxQDw3txC!L<_$Ke2mM-~+N{;K
z?+rRQ&u++6!r#efee4uL%^YE8XAAi9z1m_MFihT61iJ)zp9{|LM$TN^-^L>8z5E>z
z94zh|0A>*j^O-j(yHK3nx_02WPY}rrWH;=V%jXVb=3i$fCo3x}-SEyw=K2X>^}x#e
z8ahK>km;OA%)aE0Nka?Y?KkL==>qw|-(A1^`Ve6iK});!asxp+ar&!t*alqtnC4VI
zO}IHBd*(e82eWAqcn7s~dHq)(-gg|RAF%CWr-wBJJVg*GV|;uOjsU1m&P2}jj-UvH
zqB`tN`^3%8&x2Bv9_lVo28%K=S)#>*;TT13z=Pe@v0XMSHN2YOFGRl4IRXEg4>~CH
zS7ta7&&cngDzo^4*W085?n7T#AX@dXTqo-{FDF=>eFfXv3>e9ILBLAg-eSESu<iR;
z!z9yh2P;xnyqPP#*YO#>v|RAz=z|vU62NeL0X_AB;1%)a-mZFy5Lev;nk7#Yn!BZ;
zE?ng6TD2Dg@X0J0uKS-$73<BmdQgds4Gl0OeFuG1E$A&@E5s|r-&uY!w|*JT@Ail?
zwCXcVVTBiiY<K`<0$Bc=X`{_U2SZR#P!j?Q^w9A=h9&iw9498b2fu0xx$DPYrHrG}
zU!B|PxKbMJ2KPnor$4BH6m~=fd)@N9smKg<*kG8L93Ua|xV?%FdV}K1FQ7vh4o_=6
zAe7AqGG{^ERK|p$pf^sz+G2I&>$XLV41RWI)&k9Z+Y7=e5OB4>zRv70{~6fwMA6AC
zry8cpGCN5Z-M;QmGfc2RU9g&Z8wfh^8($IwgDW~Z`d8@iI)i>JN|<c_P+TlU<XzUh
zk>rEYOIL5@*QoSwZE|1F1NSvZlBId|lSh?&ju%a~c;Ih-c0Z2owMzE1H!c;iJ$I1(
zW?nRC6*3%1AXh;fGj;ely|qY}`e6pEate{<BLW9nVw4X}{J^4Hzt|u?o9ky_G+5FM
zz7#siem_PnD^7*gr_>NJz#W7K8&aOklx&0nIl-GqwmYSa5)w+s6rb)lU}h9Ncpb1x
zD_3hc7?;XuBQ!kEW_Ld!xDYLb9D{%!J-7i;Yk<|$1eO*PdULvcuxs*WC1x^%r3#1}
z1h`bLZ2HmF!0~T!GeiNuA_Z)h7g08*RfOxy0#M3z@B0Xx*A0$7phcON#x8FUrEl!*
zHP}u`1o_u_i<mEz9FCC-H(R?2xSYbCTP^z&0MxPU*#o>cYua~09!IAjMLs_fGzT;J
zUPR`+f>)sFAiy!gjqL3R=hdHEV=vr)W)As`Y4^XU-5|8>y;lA2Je%yK-K3zCpxHXr
zyb-t;?PqwPo5oGz*3UJuNO5?0s8q8R3&heloLx6{#dU!hE5qr7LUNUGBiep#Q7h>E
z0?iW*j(ZJmPe%wX=(rG7)sE_qAomt*350}Rd_DtJUgYHDD1@C|v(FR}_<sPxi3|vJ
zC+sqOGauRy&JybkYjblzl1oU+zC=bGz%?{BGFZN99>qIBg@u33_EC*O(p(ZPv=UI1
z0KwC4aZW~oK2OkuAYclc;R(`XcIuQ37~0}-;FW!=^Lwh3Dygn!Qx!*roe24j`<3S_
zmu{5A+U4Zr#2e&(%5>4VQ#m@>AH3xK34-1kcnn4Kmn8E}pjZY50p0%3;u{_wjr`YE
z2)wcCs8H?DAuMm+Y)Q8f3Du4L$?%j(=k~a~SBpvlM&>QLxRo-~&ib<*cMo@s8Y{Jm
zkNrzLjw>y8cLVWsUwOcO^6&Ux&{Q&rlXx3&3!=Y6LqfjU$4JE0sc{#p4H`LFE&CAr
zD!w3}f`V@tyNW&rUcK7mWwZeltjm*rVL9ihFd&NT?(L?2`=%osVG3@IZu8?Spx$|j
zhPG{Y4M=^1*GF%b43X!6I>7ztPP5gaSt(RGiYsb#Qw{1oPmGG&<(A4%aG6t#6GTbA
z33tbkBYkZbR4pt(Q||2z<-B-;K`#4xQZU+AUqWFZRl{k|c?ueaiV^}DSzL7A4ogNr
zC!;DA3VFk2X*viIId(~z{na#ncr^!u7C5fzC7lk<sRea|y=o8r(|a=&0_7Uoxgm)2
za>^Lkzn2ylGh*P8Ha2$+^!4>E^orzYK_*WdweQGR&_`P4^wrT3UKI2sy?pudYi(79
zpE}nYwj7Uz%hmSf_T`>|w-Ejkp>Aa0DFO8&u3*bKH9S@M!x&Wbf^67{u7L^Uy|unP
zF~nl=$+w_=1}PW`6c|aTu=XF`)9SSF(qPGb0k+PKvzw?gzn^|FZzS2RCX%}Kd<rJV
z?NhlOn3>tXZ333U1>oFqzEK4_t^9N3g{7s(o9nRiFR@U(+PkNwaP(kVs8BkJl#2<w
zUP@Gfnec0HbvPSU8VKM1{7ur&RY(jAe>Dzl)l-YLz{-`SpGBus0*lwtENlWKK!8!v
z)YKBxQ7%?sqojnf*S;!QB3}W8yQx}11W@n+@KFr)(qXFvzb&WClnOuRzfe;dsU+SM
z*z9k6g!w?ERHTY&&&V55veZDhON0^G_FI)AzRF~|qq9?3RtMb*WX{7(2-kRUb8`#f
zA~}CUj;9qg`v4JE_J-EmL~;fj>kQ_>gm*9bp)sm45WAMkJUa)JXzjQ(`$PzRr*jm6
z5Y`ve;jF%5g6W)x?+B#-b}uU-6A~Wo|J`!D0*(N2EW^_`Xcw_umA7m~kPn8hPrOdC
zf)Of;(M{B?FXS|BYt3kwVQ7w+{bz5_2s|@(QD$al#$F1$DYE#R_rc-8;3()Pwm(&f
zpoSpt3kjr#V1<Hs1;qmUcVaM9L(9v{&9LD7d}7f5GJ54Bxh!5^sEp{Ka=3{eUt#{?
zVXay?Z`cLw;`h<mApZpZrn{A2W4SNyf5XdtB3^_l*p+|9;e9K;3NP0RZw2KK+Cpjk
zP%}>9s-hHl76<htRchmb?)FCn;qNvx>ZIehGF;dqns=7|2#I*{s2Tr&*B>4QpnTrQ
zM_PYDy0z#oo_&X>Z$jJyN&ng2+xeEGOnad}{H+q^e$K<+w0c>pl#ls2{cNoD4M}8#
z_3DM=6Rheaq@Q*&kmqK|L(<ouGOyqLp6!eP9jQ{@d*US|s-t?+)H9X<lSms@)A8-j
zC?{w<il(zsg;1!h_nFe(#kx<7b6u%RDby5PU)k-Y#Iu*|7<sc9jzd$W#E$nqUbw5-
z(m`m2M<Cn6<c74CZnBe41Ne%Ln+WaCjjt^q$erxJ!77*p&eSeWbUXaH*d<6@4?-JW
z1on;PxD-!qWw*w7Rk!yx9r;(R$|H4E?+f!+CdY4rKY||lo5p{!uvfo6!aPvQUzM2K
zWYpfZ1O`8#2V#dCr%S8B#Qz$TGB<6ls-9f`Zc`c2n)}D*RNk~zG;2-uU&`Q-N$_)i
z6(y0HFTaK@->;|4uX+{piIT{Sw#w^u#FJ0Ejmgp$(^rsB7Q839^EJ;~3n0cleGg4Y
zr@{8Kru$b(iAK|gv3AIt^SPOTId7iG`eV<D*-A|PJ+<P)RT1oWLDSVM=+9UVxL%J0
zg6Z$7VTjbNkB@5h91r?7qSM0!2JueXbgk+LIL<%r*4^S3x+Z3sR(T2LWIq2$pxR%7
zI#2%0*D+|Of?f-R*l*J#`&+%vByB&>qaAmB=<RsRUZ%YQuJhd?oz3%zJimwRwef-1
zaYMrQ#s-T<GJ!))6sD8bXZZg!;rH?d9-EH(6Q&FLM0?u5jVkNFhx4p4?t9|N$oV{v
zc~OjhPFsHMI&`uTeKWLj56PIQ8>*h!xFthPUG8$V#N$ZeHoj~-mN)%R@$5}2JXM_P
zQtq#tZ3x889otwdh<tkWTHZq>27p~RR5HyNTqS82F#!23#{%U#|9n_vCd|Xni3kg`
z%GSiY^?fE7bT31X@NWPfQ`QVWblQA4?@=bYjiR%Wqkf6`yyAm*-Fsza|G}zIg4t8G
z*gL5BqrF&UU0N#t6%55ALU8uz$FR!^^@Z{9w=w2OOsYx$9gHXJWC@N+pQ)oXD?01$
zFn%@f3pQjl*lt~`1_FUi&T_2YQ&K~FLZh_;*8hGGS=RL40ZQ_jhH9h$3DcGdm2_ri
z|8Lgvf-$uGlwZ?_O@wDFBdhPU-(G0KN=O6VVlf;0Llgz<(RlE4>8}qTcg~)}l0;as
zbxM4W8!@FG^RARDd3Cx6@-9uXy2h}~7pp#`ka$=6(_TJqP*ejhTFZ;rM~M779>gt{
zhH0%byq+Eg?aYZdKr<mH>Wp9Mf=ct0S6kbJB!4y};I&xvi+>yi@B(8Yzb4C*QP4vF
z_8Oq2%Fsv9Ddx2bkU&2_{mf2@W=<**7Jn>BpnV*Jw!slg$HD*aj}#Ef#s2mOoy`9q
zZUwwN>R*=S|LLO;1gxBZgkq2a7<!W_kywzgam#JLM7HpP6x_CMaS$zT8k(RAaIxJb
zG!rOzrQ3~gx0RE;NQ)DCj9F;sk>0tXfs%+i`#&*q*W;Mache`t=O1+c-TmEo8Mq41
zKl^7Nz_kBQkD|N~LHqZ(35_Hs{D1Do?f?)o25L<}e{3rEu<VG_VwLXXl)1{g!CcK&
zS3VZXSfEG*Yv<v7<>11?_X<4P|J?fTNSn}{pL+|z>X%ILed(%Rw*K+;3m@;nEg*Fa
z`m_$9HDI<)sql*2pDDfLyDHQ!Zb&UA+4`LKpS$y?Ge#nYX!ay8sDe8lTQ2lbkus3F
zB3<IK-(xf!c*VH@Bz%CguQpvVYHxzGGaj{EuDAim^!8@SS_o)$I9e{e+m+95ANaz!
zi=t;(4I<K=fFNYG&1WvlqU>nC*?fC58I-9Y`+wu)vAYGT3XlXf3zT+MRaM?9(3bPn
z$-EA>fg>ak?IxO7P*C9^U+Fjua`sg?R8Dku|L0qd<$cJW$dRbsA47x1R-Mzl1mN@N
z4{mHs9B5@9!7+fjy)=H$>-uQYagFq>DR4M?RmVawRC72_%4c8oxnJSEPLn~onkL%S
z(P1ObfC{I>{pZPF(qxNXP|M5kt(MaT$(iN4AZ1PUhPOonsdlN+F_Mhq5y<3tNh3#h
zN;O+f$6AEJimMlVeX%gp-`@|E@W8wd`{a-IpXoIO0f;n##E?2Nb+N_#F5H}>sHj*3
zg>2mVOY7!u1J1%JGs(IHDBqT}7N1P$*zVtERbSYcm~0&05H`>kGXSg=NO(fKk&)22
zY}ds=j<akkU$^d4X)_OWXu;kS6hDgvOlOt_@{1P|R^Id>jiyxf)Z4fzDfxBsB4#<s
zMwbb{S|DoMG5MxHx8Wgm<w>t!yY*ANzKdXFM5!Eoa;xX4ti5u1(oKqe<c~xj<uX26
z-1-r^!{c<s7y!09LX^6uYWcCTlYhw~^mQ3z_h&}Y;Si_;2TmpOKkpqLhSR1&;>B=~
zKXJ@hl{TFYAei%uiHQliHD(8iAd>q<c?A^lr~yFggXP|4zEj0<Q|)#$&T-N8Wm~N>
zN%08{MT$hX`&Ev5u~8?%9gf5W>P59fHO)`sUyT=E72hcVV^*YSy7&e)3AZz%&!|9~
z06X{e#5^-Eg(hv{HqMr=?nkD}K^ZJ;tivA%AlddMGO}E8L4nY9Wkr>lncgxf&P?dA
z)R3Hs)2ngtbudmx+jh=&7?L>jx5GRTt{8M$?zhU{w>EAAXNq!#*GFNRSEuT&&68cT
zeyGNMO4oDkS)Bk$&XxK;F`V-~FgGwExBIj+0G$p3Nn`eq7#qq62??nRt3qFX`eJjk
zKC{!ruY2yND3FE~{Bf>+PSIFOT2?y!>XtWN{f%jyUlUHnS}ZF0ppairN4{e2h`XiH
z$;4_kS&3oI{PHdjHxfCwUrTl@#>CM#Jh-R*4KKAhMwR);CQ$8-5P^QMKbcqzr~}Og
zSJR8e!a1|X?BiW3KMbM1${g{D-?OuQN{_7hp9fmv`xR*8f%dELo?(}kko;rdm=Y^^
zQE*8XrVto~dl<Qol;CZM<6QraijY0pC)Vd@Fj9pv!@(2eA9w!$zr?**c@PJQd{Z23
zZB>+&aaG7S-%$v7iEFI1O`6}uWBPY|IT7TmJ<^Ql%@K(pCcwlb#|p0F2H!kLCNoGR
zjbFV!>+e>6!NNQB{5a}WyJD|2iE#I~Uv1cl@xBl@d7D$ol7yIm-zb6^&TGiZ#&*Ti
zc*3K4;wRLyifIj*DEQ2qBcZ5bUZI<6a_FW>=hE;z2D_{wCY$dlUCv16*0Nu)uoP>S
z<Ts91*TCt>My_PSj0%z=$ttB7OIBVg?nPpT^Fsu|IP&6#q+1PKdUSHIed3?opPCe5
zaPjj>FueH&add})DHh2#HeKN~C9HKkt@`&Lg_m8OG<|f2J%|DFV_kh-?2G;q(?vpB
zA)RdgIufjUb%2{U?;*`U*Dn%@3_6^FJg3}WG+T*w?!^-(|JRdO<7U+o{tB5etSP-|
z@qe_zprGB9US)|BzRB&Bjl}2g7$1)|H;Ye8urf9_Ug%FK+z-p@pvae+FEoB%Lu>V_
zx2FrJ;+17}A}z<^{6G2EbJasbLt9jTnvePMgV%mmuI5%0l(FG#;iP%+)i<Ci(oGq6
zjE14%GcZ3K)}#fd@_Wp$tgI|9{wREc<M3+uv$K=<BgKN2*}=(aN1bU`&qhW!I$cx#
z&fU9hUP4jHQY%i$()3ADX30R7&MLFU1fN|ZHFj{)3<VyYRlx0=xut+bZu6^?nEd>A
zGrt{yp6u53cA0-!^MMK2C<;poaDzX}vNwZp-G=!Fq}aD#FD_4d-NusyB@oHEvp{pX
zrg&kq<Hh_`Um;DAMl0mr!r8aZ$1*ZFL|k0vgYLupMbhiJ9sz5B&}!y4Z><aqIGnyh
zrtXkAm~RfX^aC&i&?SYdcTPD71HNfGmA+V{5fH4O3uz0qzh4mEjdiLUFo2jF!L{w-
z??eLgee5-fFER0~au>I04-vFdV`3=Gqirq(#H7W$Grq>RZeMVfCML$=;o!w5B-lz9
zkJSzeshF@ZoBNUM6F1D@Cz;a?>Pr|vh+^yC%;$OThE}u7R8OO=2P@Y75)kyFaI}km
zlASpGxtnKFa%!HNiQx(1rKStCv?%NlqI#kzId%SWKuAPXKY;D<ZXHX-jG9s;EJ}<@
zGY6-6TpV#+K0ZDkTt34b!@srbsXtOtE>Op30T!{5OQcewmEWpkZKb<RV-*$}+30o!
zxr-}0px<mbJ++Mk(2A{{oi+7}2p1C*=ArXcs4c*rJSB1_%x6lwmxGkvDdoL*6mIgk
zV<#*u1WwKGZg{foKm98d@(mm*`T0S~%v9fCGyws@kezeWM9jo<Sz5gv!WLLgv-GkU
zMG5fnPh9TL!_MPA8;x|nv;w$Ai?@z*DI+BdCHLEg{CuQA{c28Jdfz{qIqQxvu@4V-
zLpzTZb`_Y+a((?HA0!Q345g${aOvLD^+qg(H3oCxMB=`BwYj<ZrFQ>_MKrL_|EMD^
zqg-tw4438|Lw<4bC-N(+k}9<jAxFoW%;?PccqJnvqoMF5zb;tu*sjH)rmU=W_1|oc
z1i0)W+8xj-NlB_28v2cG{C?SW?pwBc3KSZKx=-WeNssa+rKP>d<+cZmr57>1@0~pB
zosLNZO0$|?Ou4~bF?P{(_4Md9;!7Kmlgg5-tmZ+>zIwWSd=1aU%}z)SHK2+V0N<&l
z`8kXkw^K37cO2dMl@<dlE+JC*7z}XdMTCS1=_@JWkV?xKVa4=)rh0`u9u$iZZfIyo
zvr(0wU(&w&Gbbk#8FUhH3SPQ9C#e_rv~_p&WYA*;gE~H--(?tL0Lx)f#~Ssr3~Ru&
zH1CjLq_we8l>9Prg1W{^2MSrwiK>LODl!ZAmBwfBH^V!}i|_I1a*){)>f@F&ChphN
z<@b4VXU{-i#X7y=0u+hAmYx$nwK$lb8)yUs$Z`otKV{}ebM1fio)t#n5V>^y?eGJu
zc+_Y)h7B{h56AWg`Yx-Zw<@PNqk+qfi^auGx>t|H>FMd1R$kUZIW<09+&B)<v#*OV
zxf1dCW?FlQ@aRYG22WP(oNs&tYf)DA$qL_V$+gywi3tUNAs>-?O-StEi8{8TLuk<(
zUJBxR<BeV-OueJ+rKMUYvh4urbjuFEX2Zb*KApq0vl{@3<;te^yfEii^<^va^kVb0
zT4*S4fyT_z&fc=3;c~hqu0WhFn$CN9`m*MD5fa<q(a|B3#u=<~Xty)WKto@L@51D)
z%Xn!#IL*-Q-;H{K`kmdnW3guIjKLqy|A2(n<fEj$J?q=<;&kgzWqBp}%Pk%}>`Zpk
zQlBwlua4$I_YxahhDL<229sOAwEX-q(SXMbo6+|&nuZ=#EhXhgh=JqoSSHxUHxr!x
z63WjjF41asWOH2=IY4zx4NZV>+wGxbjRJm4ZmHEv;2Yd675F=baOCP`uNimBtCBVl
z7j{Ur%sruIt*u$3Q(6jIYJv6TT_H`U9<Z{d-|u5z1}FKBNgliq5fRye{1E0K<#T1d
z*W|2NZK&S=`V;h&$Vja!5Gri^E!)^_0};iB4>1lqJ3OI@^dp1Aojw*zH8?Mu%2!c&
z@#yC6=eCVZ&ysBP;Zcdtg=f+GT6Q-P6s;|#8Pf2vaeNnV{su&jV>!~JltcMA-?4A!
z`Qjl^Qjr_GU(Ol#Mvw{zAbL>0aw8=mZ~;8+!R3IHie9<H{)}!akOwm`Fx<5)2OfM=
z4OaX%XUA|1h!FXiY)0-`*pb4*#L^KRR<hhKFx?JH3`8+9VuVYFI|t3>23p)3=qu<c
z$m@>3Pi}qvgFNi;##L5C9Ug71`D#UYfXnN$DKnEi{r&30qqMLG^s$W6;0#jr3YGGE
z&VGZG3`!Rc<Q#<9eg4pb`+AAB+QXetE<}ZS0@34~cuA+lyk*>nbZE@XliuAtNj!*d
zFaP7UzTf8>l3Y6Wa1v$OxZMO81hiEr1nL6SA%n%zOV4i2t%tv#C2Wz^Pc(T$taQoX
zK85N5<ks~C-;YjCj4-r?2%V}*<B=>(;Q+MARsyesJALPAP{%>hK^X;S<49g;xm-oi
zYR{>1yb34k2qYF5xXW%|tlc$v8%a+QpLYTFc(%R^c2-~u-4j7#KJHU5p=)aTXL81P
z^Nf;&m;~0ny-2N+k>E@6-u#|j?g(5MGCqgnkNjj)BlTZ>s#W%L3OZyf$1QhOj~zFU
zkB><U6N-}v=!8X4?~sphu5WK;esE$czH2N#4Y4&RGN(71nLD~h?@grFWcFOVu3hou
z;owopQE<7qNV(Y?l7Gx5CLs|;2qR^-N6ebK3Ee5Ld2D$Q4a3L8Az`!FWsF=V)z;Q_
zCneiYCgyaR`#y+e_2$bw3lmfOTi#peAus*M4*!>!A82W5F@kaFRZsQ`OVJ3JH$Ny4
zGk*~S@ATAu+(e4CUTla?NWeWe!?1-{=HKg<pItx5nA_-$(5bdns{Bd7V(2t;6pH&E
zSq+QA>I+2cwPp*`RX72Q5p39+6*Ek$rzf!V(!GNa913ugza!_P^Z-f1>c!J-V{L;A
zgLC~Zi%B*l3_SC*v-Fx(U#AL`-h6tqh{MTmz3vwb8G&>LqFTqWqLQ%MgTo|ZexG)5
ze{fBzW%>3yAH|4t-sJ|8G(p)i_Z!>u_}WAcJ?!b@xnAsc`>ld_u6i!jw&i6{kg7hJ
zD|0+oXlx|%E3`1wzaEY~(DA@Gp3Ny1S0S!AmBA5SQm>1ykd_kiQ7V}i&IJv#03=iv
zD$dLpHBYyCd4Uc$zsfi5l7!viXWOH0=6^H<madT+hnMC2{dU%OvGDO{DJ=5~3p@M0
zqlFs#{OXr>)Q75pGpLFCLFozaLBFJTmuR>3?=6u}><eHxaArAri-mqk=5|5mB&eJK
zLi!T{xiXT**BB{Ewn@%Pk)s>B66hh|F<>7yB1-1v2laEhKtSW~NN25MJ}Yk^T0kRA
zV_M1rPmbIVrNX|_SkF~!r!NI(i8k>{Sk+D{<9I$=$4e?Ji37rc3&WR(&Tsc0JFhg?
zG=*e75#O71iq6(X<&aa$*j(i}>@D_BF4;-7B|*@%!u&++bkce3cjcP;FsmM$HGlYU
zPGMFTGZZuZ+T8=B4B83NSgVfL<sWxwGEtwdxm=ZWpg4Cr9`RUt<!LUojPhq^65Uu#
zTn$O+WO2?;C++&QXvPR^HD;a40rbHwgN`ce%L1#>PKe=UlNLtAVYOYAT#KDNIJ-Ii
z&#u4W>3TCxC||B{$|5<{lQEmJL_Fn9a4mMEKS`xinUlR^7k!R(Ug?wxW?6}5^S8vu
zBhsS-dvhAr#b)y>0A%pruXZA+SmD0cvam9Hl-cD`idRC8|JIyHJjssRhQ^33yU#-p
zCS;m2Yn?2<jU5yVd3sEAGJef@dPAppkGOXyRkIva@VMKO@d`OnbaHYuuZ(^fSu|??
zU2sS#Dbea4)}tywdM`@@fyj(XIbGQ&4sN9$aIeYRWX}$q)_xzhF-fW{m#6n;(7S?#
ze?cj1gw7TO(<*Zah#!Ues*H>;L)T1O@mmDR1V<iAWKGorj&GGuzldI3B>5WZ4r{vq
zKAq(Z-MToxU^SBloA24bWkWp4*l%q)q$zn1=j-=})V2#qx2=mN+uMCS#Au^ww<I#<
z`a~?L@Z(b!d~l9S1Oq7-_?+!fv!~}8STv08$aLvWB{sYJLOp%&>FMbik@0Qldmxmt
zgR{^b^*$}1d^~mwmvl%39C*(U<s|6_YlT+0i99dQhSRf2<gqfPO}d&fgPS`ZGrZS&
zWKqZ>Zgad77hM~QwVPA=-O<}kr>8RMR7^?qYP@}VgrC(%1-zcpTHzw?sd?zT)tBX(
zIc#GagK>Lz3<d8!3$D-A=X#*rJfKJC{RkS>^9#ykYWQk+Tf~@GMz?1o{c6@(dV|P~
zMhd6-j8{;N*ADdDl&D@Ip(bZ{T0`@g?WS*U8#VDp^}P`r0=ojvA%s>@bm2e&e8N7d
z(fjq#_ai@eeA~N|*u@Boii^f0&QOKrK7XzP4pY0e9gOU`G=#SgMEDtPKR%CM?#Mn-
zJfBNR{88GMX##FyEOnVU9B^>6+UUnpSTLLz=T;rOI1;TSaT(MaobxTIHHO-gEXvA4
zD<$98YLiO}Zx5yEn_32MB_kTXcD9~!qxIkO+z;3BE|yARHC>e4(9_o!<rg>|8y7Zd
z0_|aVy^y5kS&ug5GKN=WMpa+zNQQYTG!CYliGGcCOiYs~7M4L(@+vCmX6Y5E8)46~
zVxd#`8;VMP{BhrOAG3}HOGw2)KYDt4-thJBx8m^PN?*J2W{N5rB?(xbS3QxWt!~Fw
zuhuu#w<PMp)>=~X<#c4c-WJ$mJ5)P}g|khu)mkkHVdyH)42;ek|Nf(RnR>XSxma;*
zK)KG?yx<Barup6~x;kTkl(6isKLHc2fVN=vZh01N3@Hc>s0me{viw889*m;9wK%Ae
zzI_}RkYJskpV#ZfK!a$ucwZ8Ya}X1gpoF2AnVWA|_fVp5ZEj^;%^K_O+i8E__;b|1
zJb{pOaQ5=-czZcsjOym<^ziV2@6H*Ggx7v9#t=lycbX+<TRmLEIU)t3A3$YBFNs4g
zPF?l|G<EFK>kSJ+JrcXyL%+Wn4i69CmC}#4L8wIA6@kSIa|Wi~GMP*FPFWOU<k+_|
zge*o<R_u1Q)4r^e5A{djQ0?M$CLt+#c6OG$W<jDu?EfV8w4}q7Z3p_Kf2tBmes@x7
z?F|sXbyO=ba8)Rt3NfU$=FvAuil-!TYF+1UY%TUKjqghqg-OE>mO>E@aF`?5WiAzn
z4J2)|vOk<xq8!r<Zu+(toh_<Od_!@Eu`2)LGtKLs@>ar<krK=u3dXM5SgUN6@<PdP
ziRZg>zRmhr8&kKu@NUSN8ND-f40MJ><Sdlf&>YSm7+=t!Vef1vpRkyP->!Fu?k?A*
zuP?gRF{qb`>10F}>qGN)y;7HD*uFZOapUW!9Mfp^<Wr&Yi=ws!tL$I`gZ`i`0rrOm
zPJ2@fj`RJQNJ~GflBEbg5~klQT}8*6o4>~^D2>#Njd#d}1F5Lqx;q^-*45Sdz`*Mj
zIJ%8U8&H6_i`ldXH;9OKSY#v_mmbyhYttC_o2f)<PhKYX>#xAl?pRG7kv{u0>=`e@
zW_`qKtg<r@GSG~0nesgul;P+Pw9mU<9fc>4s+ue=74!VE1Fe*gFt;k7RStN{j_>`?
z9-8jz9i75ugGBeh8Mm^crsH!6fh5hVEbsgRl~HYJX=&0l(plVXA#1YZ<)h}-<tH{m
zCSMs(!&Bc-3^8l0{GT8v3uJNb`hXgc0Rv__$zOCu7Da%Gc5*MzF8E~zay<|;5Q#~T
zNN)p%*s#dR$cV3N16w~8F^#dD>>ppP77Oz>1B4j><G3XBLkvU7`tmeVVbW3b;Ikv$
zoqmFI0Y!As5?|5e;9zJo<P9rULPDH&Xv<|sA0Ea`lrPgCWY`xgo-L^s+?KcQlR15o
zHOe)YS_kEfp16rPWc;>uZna1F%&_#)a`x-z!RP6dwU%=MaA0=QH#H@2q_6;C62Js%
z;=`wNeDfH1Tz-*}{J}y}QD0F(FGeVb(`K(Lmq>t(or#p$0`d07;#%#apscJcagiID
zlR@=caYeE#{ueD!l<NQq1}dEolKP6-vO4LbwH}_Qzx&&ed_b+)?dGIxiFP9)KK}0B
z9<3Edqg!3;>Qe_uF|pB;`p%3>^6h+juEZ`^CY6!9uNP<s7Mz%_C?Q%k_WRq#yQn{`
z4~|etd7S|Z0=WM^1F_LrV(!WD_Hw86WwCIc*4beH@-V3!``QY#<tK)fu8#|g78UOK
z6TgKDl_PhpGRIH57z*V1xWo1gx%S0IYQ?8)*}S}C5tCiZD)W6vy;M~uIXwFoyb9+>
zhT4XE@QLC{c(aNN^&txm<z&@{XP~D=CY_IO!0UGqUQ(@<8mI8dL{|2vUYVLyph94*
zSoUa+&Wllqfk!3W+~06xUqA4%MpIQ+l}Tlv>KWKpo+xhm##`E=JrrBrBqB~Jg8E>$
zdIF6?%p*wZ!8a0^j^2vTf0<Km;$nI(2?VCm(b1_qPBqmv9xkVYeP%P+rP(kxEo*+g
zbIZ5lNaT)COBBpFnQcX_sjIMUTw&5*FQ^fiNL*42s{(}s(cs|V%2oKdIMV@yE6RH>
z%8`c2FwC$)9kD}uxD(%BS~ioMmN6Ke_|$x{qM0+*)fTMz$BXtItuB8;CX0}YpKT6%
z%u3zOYNS=3*OLm@{NCvOczEk%0Zt*<vI7)L-b}(wON&IsG&JlyEJN)>UmOs|=85!*
z?5qrnu60(Ez0Ktv&=IP~w~3~!#=gxa^25l&-ekU+N1u^FPie8ZspwoG-By1htX6LZ
znj_OvneS|F)4-CSer+i@Jw2_J>eXoZ63Bj@hIn*@GRtJs`87WwSUmi=;oQ^d;@Gj`
zb7#Gu4o%5;xUkOW#atnK@EkaQ$6_>skHa`%?M*gQa8^-K;dnIfa^5%2B9O-QxbgSA
z%HAd$zcixecs2r$1rRigw%h?NTHY90!jJp4FELKhbLw2Rc+HB^e6wqEy1y>scfRux
z!S1n*toAqPx9z?#vDDA5X=&*UH@|(bXH~dI1(Mny4cuz#%pCELE-MEQzeJD0$rkN{
z+C2RyO(KxT@LOqHarW{3ZRKFqRL)tVNF>p)(tIabtCsh_5PYQnTIhR3yrCHhDtCST
zPuFn$O{?62M-EyI)fedpCitfWI<m5q=FSOcbCj`kn+MJDUnrR63x5L$6m)OfZXNT7
z{51a$8XS6ZF;f*|v@JR2FTyJ<oF>vaX|`}1X-(UKJ(c6%kx{?sDz0&TeiqD0)}Fv&
zInN3rG2m@FQ?6zVj17Ccd&>{GgD41}xsf`26v8i<ZlCBZ*NE^<zEd?NB-A`kO5`+6
z`x!5(T7y!`TI~s37<jaky?r)HlOE7qPy}GnF#Jq88rT;fOiXqkAMPmMv#ji7`tJUN
zKxev*_bC>cK4P`Nol!?Gh`eP<VVe4aZ%2mXQsp*I8rZs~4d8XK^$`M4&#3^fB4+sV
zKa9rzg_?N6cYnlwoDXY7{g<=2XE9+@_ZP}kE{vCbb@?%Sx~%d1dW`xXE`=XJpEqQ*
z19V5*%O2}^6Hx%hrC;J(tao+G5NP;-IBxn(fQ-KV=SBsz#}m~5Mu<dF4~>mQ(LID5
zeF9WK6qx4upYG4jpRmX`llAoUD)f8NlBJ9c47%9lpSglKkYo)&Qy*{03ARug1JI}*
s9kt#C(fkj)@?HrEjI@wFO5~N7unoN1mPcqC6!;VWB=fOE=*zeN1<(PlX#fBK

literal 0
HcmV?d00001

diff --git a/images/S15_CalloutControlExample.png b/docs/images/S15_CalloutControlExample.png
similarity index 100%
rename from images/S15_CalloutControlExample.png
rename to docs/images/S15_CalloutControlExample.png
diff --git a/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png b/docs/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png
similarity index 100%
rename from images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png
rename to docs/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig2.png
diff --git a/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png b/docs/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png
similarity index 100%
rename from images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png
rename to docs/images/SP15Con_BuildSharePointAppsForMobileDevices_Fig3.png
diff --git a/images/SP15Con_CF_BCS_Overview.jpg b/docs/images/SP15Con_CF_BCS_Overview.jpg
similarity index 100%
rename from images/SP15Con_CF_BCS_Overview.jpg
rename to docs/images/SP15Con_CF_BCS_Overview.jpg
diff --git a/images/SP15Con_CF_ConnFrwkArch.jpg b/docs/images/SP15Con_CF_ConnFrwkArch.jpg
similarity index 100%
rename from images/SP15Con_CF_ConnFrwkArch.jpg
rename to docs/images/SP15Con_CF_ConnFrwkArch.jpg
diff --git a/images/SP15Con_CF_IndexingConnectors.jpg b/docs/images/SP15Con_CF_IndexingConnectors.jpg
similarity index 100%
rename from images/SP15Con_CF_IndexingConnectors.jpg
rename to docs/images/SP15Con_CF_IndexingConnectors.jpg
diff --git a/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png b/docs/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png
similarity index 100%
rename from images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png
rename to docs/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig3.png
diff --git a/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png b/docs/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png
similarity index 100%
rename from images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png
rename to docs/images/SP15Con_CreateSharePointListAppsForWindowsPhoneFig4.png
diff --git a/images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png b/docs/images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png
similarity index 100%
rename from images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png
rename to docs/images/SP15Con_HowToAddGeolocationColumnUpdated_Fig1.png
diff --git a/images/SP15Con_HowToAddGeolocationColumn_fig.png b/docs/images/SP15Con_HowToAddGeolocationColumn_fig.png
similarity index 100%
rename from images/SP15Con_HowToAddGeolocationColumn_fig.png
rename to docs/images/SP15Con_HowToAddGeolocationColumn_fig.png
diff --git a/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png b/docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png
similarity index 100%
rename from images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png
rename to docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig1.png
diff --git a/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png b/docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png
similarity index 100%
rename from images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png
rename to docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig2.png
diff --git a/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png b/docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png
similarity index 100%
rename from images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png
rename to docs/images/SP15Con_HowToCreateMapBasedPhoneApp_Fig3.png
diff --git a/images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png b/docs/images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png
similarity index 100%
rename from images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png
rename to docs/images/SP15Con_HowToExtendGeolocationFieldTypeUsingClientSideRenderingFig2.png
diff --git a/images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png b/docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png
similarity index 100%
rename from images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png
rename to docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png
diff --git a/images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png b/docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png
similarity index 100%
rename from images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png
rename to docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png
diff --git a/images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG b/docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG
similarity index 100%
rename from images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG
rename to docs/images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG
diff --git a/images/SP15Con_SharePointClientAuthenticationFig1.png b/docs/images/SP15Con_SharePointClientAuthenticationFig1.png
similarity index 100%
rename from images/SP15Con_SharePointClientAuthenticationFig1.png
rename to docs/images/SP15Con_SharePointClientAuthenticationFig1.png
diff --git a/images/SP15Con_VisualStudioMobileSPListTemplate.png b/docs/images/SP15Con_VisualStudioMobileSPListTemplate.png
similarity index 100%
rename from images/SP15Con_VisualStudioMobileSPListTemplate.png
rename to docs/images/SP15Con_VisualStudioMobileSPListTemplate.png
diff --git a/images/SP15HelloWorldSPApp_Fig01.png b/docs/images/SP15HelloWorldSPApp_Fig01.png
similarity index 100%
rename from images/SP15HelloWorldSPApp_Fig01.png
rename to docs/images/SP15HelloWorldSPApp_Fig01.png
diff --git a/images/SP15HighTrustLaunchNew.gif b/docs/images/SP15HighTrustLaunchNew.gif
similarity index 100%
rename from images/SP15HighTrustLaunchNew.gif
rename to docs/images/SP15HighTrustLaunchNew.gif
diff --git a/images/SP15_Buildsearch-drivenmobileappspages_home.gif b/docs/images/SP15_Buildsearch-drivenmobileappspages_home.gif
similarity index 100%
rename from images/SP15_Buildsearch-drivenmobileappspages_home.gif
rename to docs/images/SP15_Buildsearch-drivenmobileappspages_home.gif
diff --git a/images/SP15_CMISCapabilities.jpg b/docs/images/SP15_CMISCapabilities.jpg
similarity index 100%
rename from images/SP15_CMISCapabilities.jpg
rename to docs/images/SP15_CMISCapabilities.jpg
diff --git a/images/SP15_CMISObjectTypeExamples.png b/docs/images/SP15_CMISObjectTypeExamples.png
similarity index 100%
rename from images/SP15_CMISObjectTypeExamples.png
rename to docs/images/SP15_CMISObjectTypeExamples.png
diff --git a/images/SP15_CalloutLeftRight.png b/docs/images/SP15_CalloutLeftRight.png
similarity index 100%
rename from images/SP15_CalloutLeftRight.png
rename to docs/images/SP15_CalloutLeftRight.png
diff --git a/images/SP15_CalloutMenu.png b/docs/images/SP15_CalloutMenu.png
similarity index 100%
rename from images/SP15_CalloutMenu.png
rename to docs/images/SP15_CalloutMenu.png
diff --git a/images/SP15_CalloutTopBottom.png b/docs/images/SP15_CalloutTopBottom.png
similarity index 100%
rename from images/SP15_CalloutTopBottom.png
rename to docs/images/SP15_CalloutTopBottom.png
diff --git a/images/SP15_Content_Enrichment.gif b/docs/images/SP15_Content_Enrichment.gif
similarity index 100%
rename from images/SP15_Content_Enrichment.gif
rename to docs/images/SP15_Content_Enrichment.gif
diff --git a/images/SP15_DeveloperSiteHome_border.png b/docs/images/SP15_DeveloperSiteHome_border.png
similarity index 100%
rename from images/SP15_DeveloperSiteHome_border.png
rename to docs/images/SP15_DeveloperSiteHome_border.png
diff --git a/images/SP15_FeatureReceiverVS.png b/docs/images/SP15_FeatureReceiverVS.png
similarity index 100%
rename from images/SP15_FeatureReceiverVS.png
rename to docs/images/SP15_FeatureReceiverVS.png
diff --git a/images/SP15_Office365AdminInset_border.png b/docs/images/SP15_Office365AdminInset_border.png
similarity index 100%
rename from images/SP15_Office365AdminInset_border.png
rename to docs/images/SP15_Office365AdminInset_border.png
diff --git a/images/SP15_OnPremACSArchitecture.png b/docs/images/SP15_OnPremACSArchitecture.png
similarity index 100%
rename from images/SP15_OnPremACSArchitecture.png
rename to docs/images/SP15_OnPremACSArchitecture.png
diff --git a/images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG b/docs/images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG
similarity index 100%
rename from images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG
rename to docs/images/SP15_OverviewOfWinPhoneSPTemplatesInVisualStudio_fig1.PNG
diff --git a/images/SP15_RegisterApp.png b/docs/images/SP15_RegisterApp.png
similarity index 100%
rename from images/SP15_RegisterApp.png
rename to docs/images/SP15_RegisterApp.png
diff --git a/images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg b/docs/images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg
similarity index 100%
rename from images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg
rename to docs/images/SP15_User_Segmentation_with_ContentBySearchWebPart.jpg
diff --git a/images/SP15_appChooseSiteTemplate.gif b/docs/images/SP15_appChooseSiteTemplate.gif
similarity index 100%
rename from images/SP15_appChooseSiteTemplate.gif
rename to docs/images/SP15_appChooseSiteTemplate.gif
diff --git a/images/SP15_app_ChooseSiteTemplates.gif b/docs/images/SP15_app_ChooseSiteTemplates.gif
similarity index 100%
rename from images/SP15_app_ChooseSiteTemplates.gif
rename to docs/images/SP15_app_ChooseSiteTemplates.gif
diff --git a/images/SP15_app_ServerType.gif b/docs/images/SP15_app_ServerType.gif
similarity index 100%
rename from images/SP15_app_ServerType.gif
rename to docs/images/SP15_app_ServerType.gif
diff --git a/images/SP15_basicself-hostedapp.gif b/docs/images/SP15_basicself-hostedapp.gif
similarity index 100%
rename from images/SP15_basicself-hostedapp.gif
rename to docs/images/SP15_basicself-hostedapp.gif
diff --git a/images/SP15_hosting_Provider.gif b/docs/images/SP15_hosting_Provider.gif
similarity index 100%
rename from images/SP15_hosting_Provider.gif
rename to docs/images/SP15_hosting_Provider.gif
diff --git a/images/SP15_hosting_SPhosted.gif b/docs/images/SP15_hosting_SPhosted.gif
similarity index 100%
rename from images/SP15_hosting_SPhosted.gif
rename to docs/images/SP15_hosting_SPhosted.gif
diff --git a/images/SP15_search_app_permission_Napa.gif b/docs/images/SP15_search_app_permission_Napa.gif
similarity index 100%
rename from images/SP15_search_app_permission_Napa.gif
rename to docs/images/SP15_search_app_permission_Napa.gif
diff --git a/images/SP15_search_apps_permission_Visual_Studio.PNG b/docs/images/SP15_search_apps_permission_Visual_Studio.PNG
similarity index 100%
rename from images/SP15_search_apps_permission_Visual_Studio.PNG
rename to docs/images/SP15_search_apps_permission_Visual_Studio.PNG
diff --git a/images/SPAdminCenter_newSiteCollection.png b/docs/images/SPAdminCenter_newSiteCollection.png
similarity index 100%
rename from images/SPAdminCenter_newSiteCollection.png
rename to docs/images/SPAdminCenter_newSiteCollection.png
diff --git a/images/SPAdminCenter_newSiteCollection_provisioning.png b/docs/images/SPAdminCenter_newSiteCollection_provisioning.png
similarity index 100%
rename from images/SPAdminCenter_newSiteCollection_provisioning.png
rename to docs/images/SPAdminCenter_newSiteCollection_provisioning.png
diff --git a/images/SPCon15_BDCMobileAppDemo.png b/docs/images/SPCon15_BDCMobileAppDemo.png
similarity index 100%
rename from images/SPCon15_BDCMobileAppDemo.png
rename to docs/images/SPCon15_BDCMobileAppDemo.png
diff --git a/images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png b/docs/images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png
similarity index 100%
rename from images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png
rename to docs/images/SPCon15_BDC_SetPermissions_ODataWebNorthWind.png
diff --git a/images/SPCon15_CreateMapView_ChooseViewType__fig2.png b/docs/images/SPCon15_CreateMapView_ChooseViewType__fig2.png
similarity index 100%
rename from images/SPCon15_CreateMapView_ChooseViewType__fig2.png
rename to docs/images/SPCon15_CreateMapView_ChooseViewType__fig2.png
diff --git a/images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png b/docs/images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png
similarity index 100%
rename from images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png
rename to docs/images/SPCon15_CreateMapView_DifferentPushPinsOnMapView__fig5.png
diff --git a/images/SPCon15_CreateMapView_ECB_Menu__fig1.png b/docs/images/SPCon15_CreateMapView_ECB_Menu__fig1.png
similarity index 100%
rename from images/SPCon15_CreateMapView_ECB_Menu__fig1.png
rename to docs/images/SPCon15_CreateMapView_ECB_Menu__fig1.png
diff --git a/images/SPCon15_CreateMapView_MyMapView__fig4.png b/docs/images/SPCon15_CreateMapView_MyMapView__fig4.png
similarity index 100%
rename from images/SPCon15_CreateMapView_MyMapView__fig4.png
rename to docs/images/SPCon15_CreateMapView_MyMapView__fig4.png
diff --git a/images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png b/docs/images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png
similarity index 100%
rename from images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png
rename to docs/images/SPCon15_CreateMapView_PushPinsOnMapView__fig6.png
diff --git a/images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png b/docs/images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png
similarity index 100%
rename from images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png
rename to docs/images/SPCon15_CreateMapView_SelectFieldsForView__fig3.png
diff --git a/images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png b/docs/images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png
similarity index 100%
rename from images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png
rename to docs/images/SPCon15_Setting_BDCObjectPermission_DialogueBox.png
diff --git a/images/SPD-Dictionary-1a.png b/docs/images/SPD-Dictionary-1a.png
similarity index 100%
rename from images/SPD-Dictionary-1a.png
rename to docs/images/SPD-Dictionary-1a.png
diff --git a/images/SPD15-BuildADictionaryDialog.png b/docs/images/SPD15-BuildADictionaryDialog.png
similarity index 100%
rename from images/SPD15-BuildADictionaryDialog.png
rename to docs/images/SPD15-BuildADictionaryDialog.png
diff --git a/images/SPD15-CoordinationActions.png b/docs/images/SPD15-CoordinationActions.png
similarity index 100%
rename from images/SPD15-CoordinationActions.png
rename to docs/images/SPD15-CoordinationActions.png
diff --git a/images/SPD15-CoordinationActions2.png b/docs/images/SPD15-CoordinationActions2.png
similarity index 100%
rename from images/SPD15-CoordinationActions2.png
rename to docs/images/SPD15-CoordinationActions2.png
diff --git a/images/SPD15-CoordinationActions3.png b/docs/images/SPD15-CoordinationActions3.png
similarity index 100%
rename from images/SPD15-CoordinationActions3.png
rename to docs/images/SPD15-CoordinationActions3.png
diff --git a/images/SPD15-CorrelationActions4.png b/docs/images/SPD15-CorrelationActions4.png
similarity index 100%
rename from images/SPD15-CorrelationActions4.png
rename to docs/images/SPD15-CorrelationActions4.png
diff --git a/images/SPD15-CountItemsInDictionary.png b/docs/images/SPD15-CountItemsInDictionary.png
similarity index 100%
rename from images/SPD15-CountItemsInDictionary.png
rename to docs/images/SPD15-CountItemsInDictionary.png
diff --git a/images/SPD15-Dictionary-1b.png b/docs/images/SPD15-Dictionary-1b.png
similarity index 100%
rename from images/SPD15-Dictionary-1b.png
rename to docs/images/SPD15-Dictionary-1b.png
diff --git a/images/SPD15-Dictionary-2.png b/docs/images/SPD15-Dictionary-2.png
similarity index 100%
rename from images/SPD15-Dictionary-2.png
rename to docs/images/SPD15-Dictionary-2.png
diff --git a/images/SPD15-EventingActions1.png b/docs/images/SPD15-EventingActions1.png
similarity index 100%
rename from images/SPD15-EventingActions1.png
rename to docs/images/SPD15-EventingActions1.png
diff --git a/images/SPD15-EventingActions2.png b/docs/images/SPD15-EventingActions2.png
similarity index 100%
rename from images/SPD15-EventingActions2.png
rename to docs/images/SPD15-EventingActions2.png
diff --git a/images/SPD15-EventingActions3.jpg b/docs/images/SPD15-EventingActions3.jpg
similarity index 100%
rename from images/SPD15-EventingActions3.jpg
rename to docs/images/SPD15-EventingActions3.jpg
diff --git a/images/SPD15-EventingActions4.png b/docs/images/SPD15-EventingActions4.png
similarity index 100%
rename from images/SPD15-EventingActions4.png
rename to docs/images/SPD15-EventingActions4.png
diff --git a/images/SPD15-EventingActions5.png b/docs/images/SPD15-EventingActions5.png
similarity index 100%
rename from images/SPD15-EventingActions5.png
rename to docs/images/SPD15-EventingActions5.png
diff --git a/images/SPD15-GetAnItemFromDictionary.png b/docs/images/SPD15-GetAnItemFromDictionary.png
similarity index 100%
rename from images/SPD15-GetAnItemFromDictionary.png
rename to docs/images/SPD15-GetAnItemFromDictionary.png
diff --git a/images/SPD15-PackagingWorkflow1.png b/docs/images/SPD15-PackagingWorkflow1.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow1.png
rename to docs/images/SPD15-PackagingWorkflow1.png
diff --git a/images/SPD15-PackagingWorkflow2.png b/docs/images/SPD15-PackagingWorkflow2.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow2.png
rename to docs/images/SPD15-PackagingWorkflow2.png
diff --git a/images/SPD15-PackagingWorkflow3.png b/docs/images/SPD15-PackagingWorkflow3.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow3.png
rename to docs/images/SPD15-PackagingWorkflow3.png
diff --git a/images/SPD15-PackagingWorkflow4.png b/docs/images/SPD15-PackagingWorkflow4.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow4.png
rename to docs/images/SPD15-PackagingWorkflow4.png
diff --git a/images/SPD15-PackagingWorkflow5.png b/docs/images/SPD15-PackagingWorkflow5.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow5.png
rename to docs/images/SPD15-PackagingWorkflow5.png
diff --git a/images/SPD15-PackagingWorkflow6.png b/docs/images/SPD15-PackagingWorkflow6.png
similarity index 100%
rename from images/SPD15-PackagingWorkflow6.png
rename to docs/images/SPD15-PackagingWorkflow6.png
diff --git a/images/SPD15-TaskActions2.png b/docs/images/SPD15-TaskActions2.png
similarity index 100%
rename from images/SPD15-TaskActions2.png
rename to docs/images/SPD15-TaskActions2.png
diff --git a/images/SPD15-TaskActions3.png b/docs/images/SPD15-TaskActions3.png
similarity index 100%
rename from images/SPD15-TaskActions3.png
rename to docs/images/SPD15-TaskActions3.png
diff --git a/images/SPD15-TaskActions4.png b/docs/images/SPD15-TaskActions4.png
similarity index 100%
rename from images/SPD15-TaskActions4.png
rename to docs/images/SPD15-TaskActions4.png
diff --git a/images/SPD15-TaskActions5.png b/docs/images/SPD15-TaskActions5.png
similarity index 100%
rename from images/SPD15-TaskActions5.png
rename to docs/images/SPD15-TaskActions5.png
diff --git a/images/SPD15-VisualDesigner1.png b/docs/images/SPD15-VisualDesigner1.png
similarity index 100%
rename from images/SPD15-VisualDesigner1.png
rename to docs/images/SPD15-VisualDesigner1.png
diff --git a/images/SPD15-VisualDesigner2.png b/docs/images/SPD15-VisualDesigner2.png
similarity index 100%
rename from images/SPD15-VisualDesigner2.png
rename to docs/images/SPD15-VisualDesigner2.png
diff --git a/images/SPD15-VisualDesigner3.png b/docs/images/SPD15-VisualDesigner3.png
similarity index 100%
rename from images/SPD15-VisualDesigner3.png
rename to docs/images/SPD15-VisualDesigner3.png
diff --git a/images/SPD15-WFAppPermissions1.png b/docs/images/SPD15-WFAppPermissions1.png
similarity index 100%
rename from images/SPD15-WFAppPermissions1.png
rename to docs/images/SPD15-WFAppPermissions1.png
diff --git a/images/SPD15-WFAppPermissions10.png b/docs/images/SPD15-WFAppPermissions10.png
similarity index 100%
rename from images/SPD15-WFAppPermissions10.png
rename to docs/images/SPD15-WFAppPermissions10.png
diff --git a/images/SPD15-WFAppPermissions11.png b/docs/images/SPD15-WFAppPermissions11.png
similarity index 100%
rename from images/SPD15-WFAppPermissions11.png
rename to docs/images/SPD15-WFAppPermissions11.png
diff --git a/images/SPD15-WFAppPermissions12.png b/docs/images/SPD15-WFAppPermissions12.png
similarity index 100%
rename from images/SPD15-WFAppPermissions12.png
rename to docs/images/SPD15-WFAppPermissions12.png
diff --git a/images/SPD15-WFAppPermissions13.png b/docs/images/SPD15-WFAppPermissions13.png
similarity index 100%
rename from images/SPD15-WFAppPermissions13.png
rename to docs/images/SPD15-WFAppPermissions13.png
diff --git a/images/SPD15-WFAppPermissions14.png b/docs/images/SPD15-WFAppPermissions14.png
similarity index 100%
rename from images/SPD15-WFAppPermissions14.png
rename to docs/images/SPD15-WFAppPermissions14.png
diff --git a/images/SPD15-WFAppPermissions15.png b/docs/images/SPD15-WFAppPermissions15.png
similarity index 100%
rename from images/SPD15-WFAppPermissions15.png
rename to docs/images/SPD15-WFAppPermissions15.png
diff --git a/images/SPD15-WFAppPermissions2.png b/docs/images/SPD15-WFAppPermissions2.png
similarity index 100%
rename from images/SPD15-WFAppPermissions2.png
rename to docs/images/SPD15-WFAppPermissions2.png
diff --git a/images/SPD15-WFAppPermissions3.png b/docs/images/SPD15-WFAppPermissions3.png
similarity index 100%
rename from images/SPD15-WFAppPermissions3.png
rename to docs/images/SPD15-WFAppPermissions3.png
diff --git a/images/SPD15-WFAppPermissions4.png b/docs/images/SPD15-WFAppPermissions4.png
similarity index 100%
rename from images/SPD15-WFAppPermissions4.png
rename to docs/images/SPD15-WFAppPermissions4.png
diff --git a/images/SPD15-WFAppPermissions5.png b/docs/images/SPD15-WFAppPermissions5.png
similarity index 100%
rename from images/SPD15-WFAppPermissions5.png
rename to docs/images/SPD15-WFAppPermissions5.png
diff --git a/images/SPD15-WFAppPermissions6.png b/docs/images/SPD15-WFAppPermissions6.png
similarity index 100%
rename from images/SPD15-WFAppPermissions6.png
rename to docs/images/SPD15-WFAppPermissions6.png
diff --git a/images/SPD15-WFAppPermissions7.png b/docs/images/SPD15-WFAppPermissions7.png
similarity index 100%
rename from images/SPD15-WFAppPermissions7.png
rename to docs/images/SPD15-WFAppPermissions7.png
diff --git a/images/SPD15-WFAppPermissions8.png b/docs/images/SPD15-WFAppPermissions8.png
similarity index 100%
rename from images/SPD15-WFAppPermissions8.png
rename to docs/images/SPD15-WFAppPermissions8.png
diff --git a/images/SPD15-WFAppPermissions9.png b/docs/images/SPD15-WFAppPermissions9.png
similarity index 100%
rename from images/SPD15-WFAppPermissions9.png
rename to docs/images/SPD15-WFAppPermissions9.png
diff --git a/images/SPD15-install-connect-1.png b/docs/images/SPD15-install-connect-1.png
similarity index 100%
rename from images/SPD15-install-connect-1.png
rename to docs/images/SPD15-install-connect-1.png
diff --git a/images/SPD15-install-connect-2.png b/docs/images/SPD15-install-connect-2.png
similarity index 100%
rename from images/SPD15-install-connect-2.png
rename to docs/images/SPD15-install-connect-2.png
diff --git a/images/SPD15-install-connect-3.png b/docs/images/SPD15-install-connect-3.png
similarity index 100%
rename from images/SPD15-install-connect-3.png
rename to docs/images/SPD15-install-connect-3.png
diff --git a/images/SPD15-install-connect-4.png b/docs/images/SPD15-install-connect-4.png
similarity index 100%
rename from images/SPD15-install-connect-4.png
rename to docs/images/SPD15-install-connect-4.png
diff --git a/images/SPD15-wf-step1.png b/docs/images/SPD15-wf-step1.png
similarity index 100%
rename from images/SPD15-wf-step1.png
rename to docs/images/SPD15-wf-step1.png
diff --git a/images/SPF15Con_REST_OverallSyntax.png b/docs/images/SPF15Con_REST_OverallSyntax.png
similarity index 100%
rename from images/SPF15Con_REST_OverallSyntax.png
rename to docs/images/SPF15Con_REST_OverallSyntax.png
diff --git a/images/SPF15Con_REST_RESTStructure.png b/docs/images/SPF15Con_REST_RESTStructure.png
similarity index 100%
rename from images/SPF15Con_REST_RESTStructure.png
rename to docs/images/SPF15Con_REST_RESTStructure.png
diff --git a/images/SPF15Con_REST_parameterAliasSyntax.png b/docs/images/SPF15Con_REST_parameterAliasSyntax.png
similarity index 100%
rename from images/SPF15Con_REST_parameterAliasSyntax.png
rename to docs/images/SPF15Con_REST_parameterAliasSyntax.png
diff --git a/images/SPF15Con_REST_parameterDictionarySyntax.png b/docs/images/SPF15Con_REST_parameterDictionarySyntax.png
similarity index 100%
rename from images/SPF15Con_REST_parameterDictionarySyntax.png
rename to docs/images/SPF15Con_REST_parameterDictionarySyntax.png
diff --git a/images/SPF15Con_REST_parameterQuerySyntax.png b/docs/images/SPF15Con_REST_parameterQuerySyntax.png
similarity index 100%
rename from images/SPF15Con_REST_parameterQuerySyntax.png
rename to docs/images/SPF15Con_REST_parameterQuerySyntax.png
diff --git a/images/SPF15Con_REST_parameterSyntax.png b/docs/images/SPF15Con_REST_parameterSyntax.png
similarity index 100%
rename from images/SPF15Con_REST_parameterSyntax.png
rename to docs/images/SPF15Con_REST_parameterSyntax.png
diff --git a/images/SPF15Con_REST_queryOptionSyntax.png b/docs/images/SPF15Con_REST_queryOptionSyntax.png
similarity index 100%
rename from images/SPF15Con_REST_queryOptionSyntax.png
rename to docs/images/SPF15Con_REST_queryOptionSyntax.png
diff --git a/images/SPS14_PerfPoint_ArchOverview.gif b/docs/images/SPS14_PerfPoint_ArchOverview.gif
similarity index 100%
rename from images/SPS14_PerfPoint_ArchOverview.gif
rename to docs/images/SPS14_PerfPoint_ArchOverview.gif
diff --git a/images/SPS15CON_WAS_Architecture.png b/docs/images/SPS15CON_WAS_Architecture.png
similarity index 100%
rename from images/SPS15CON_WAS_Architecture.png
rename to docs/images/SPS15CON_WAS_Architecture.png
diff --git a/images/SPS15CON_xls_JsUdfinWebApp.jpg b/docs/images/SPS15CON_xls_JsUdfinWebApp.jpg
similarity index 100%
rename from images/SPS15CON_xls_JsUdfinWebApp.jpg
rename to docs/images/SPS15CON_xls_JsUdfinWebApp.jpg
diff --git a/images/SP_VS_Properties_Window_AppEvents.PNG b/docs/images/SP_VS_Properties_Window_AppEvents.PNG
similarity index 100%
rename from images/SP_VS_Properties_Window_AppEvents.PNG
rename to docs/images/SP_VS_Properties_Window_AppEvents.PNG
diff --git a/images/SP_VS_Properties_Window_RemoteEvents.PNG b/docs/images/SP_VS_Properties_Window_RemoteEvents.PNG
similarity index 100%
rename from images/SP_VS_Properties_Window_RemoteEvents.PNG
rename to docs/images/SP_VS_Properties_Window_RemoteEvents.PNG
diff --git a/images/SearchComponentInteraction.jpg b/docs/images/SearchComponentInteraction.jpg
similarity index 100%
rename from images/SearchComponentInteraction.jpg
rename to docs/images/SearchComponentInteraction.jpg
diff --git a/images/SharePointAPIsetsandselectedSharePointextensions.png b/docs/images/SharePointAPIsetsandselectedSharePointextensions.png
similarity index 100%
rename from images/SharePointAPIsetsandselectedSharePointextensions.png
rename to docs/images/SharePointAPIsetsandselectedSharePointextensions.png
diff --git a/images/SharePointServer14Con_XLSvcs_RESTModel.gif b/docs/images/SharePointServer14Con_XLSvcs_RESTModel.gif
similarity index 100%
rename from images/SharePointServer14Con_XLSvcs_RESTModel.gif
rename to docs/images/SharePointServer14Con_XLSvcs_RESTModel.gif
diff --git a/images/SharePointSolutionVSTemplate.png b/docs/images/SharePointSolutionVSTemplate.png
similarity index 100%
rename from images/SharePointSolutionVSTemplate.png
rename to docs/images/SharePointSolutionVSTemplate.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png
diff --git a/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png b/docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png
similarity index 100%
rename from images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png
rename to docs/images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png
diff --git a/images/SharePointtab.PNG b/docs/images/SharePointtab.PNG
similarity index 100%
rename from images/SharePointtab.PNG
rename to docs/images/SharePointtab.PNG
diff --git a/images/SiteURL.PNG b/docs/images/SiteURL.PNG
similarity index 100%
rename from images/SiteURL.PNG
rename to docs/images/SiteURL.PNG
diff --git a/images/Sp15_app_.png b/docs/images/Sp15_app_.png
similarity index 100%
rename from images/Sp15_app_.png
rename to docs/images/Sp15_app_.png
diff --git a/images/StylesheetControl_result.png b/docs/images/StylesheetControl_result.png
similarity index 100%
rename from images/StylesheetControl_result.png
rename to docs/images/StylesheetControl_result.png
diff --git a/images/StylesheetControl_result2.png b/docs/images/StylesheetControl_result2.png
similarity index 100%
rename from images/StylesheetControl_result2.png
rename to docs/images/StylesheetControl_result2.png
diff --git a/images/TFSBuildTargets.png b/docs/images/TFSBuildTargets.png
similarity index 100%
rename from images/TFSBuildTargets.png
rename to docs/images/TFSBuildTargets.png
diff --git a/images/Top-levelprojectnode.PNG b/docs/images/Top-levelprojectnode.PNG
similarity index 100%
rename from images/Top-levelprojectnode.PNG
rename to docs/images/Top-levelprojectnode.PNG
diff --git a/images/UpdateAppOpenFeatureXML.png b/docs/images/UpdateAppOpenFeatureXML.png
similarity index 100%
rename from images/UpdateAppOpenFeatureXML.png
rename to docs/images/UpdateAppOpenFeatureXML.png
diff --git a/images/UpdatingApp_AppTileUpdateNotice.png b/docs/images/UpdatingApp_AppTileUpdateNotice.png
similarity index 100%
rename from images/UpdatingApp_AppTileUpdateNotice.png
rename to docs/images/UpdatingApp_AppTileUpdateNotice.png
diff --git a/images/UpdatingApp_ImmediateUpgradeProcess.png b/docs/images/UpdatingApp_ImmediateUpgradeProcess.png
similarity index 100%
rename from images/UpdatingApp_ImmediateUpgradeProcess.png
rename to docs/images/UpdatingApp_ImmediateUpgradeProcess.png
diff --git a/images/WebProxy_result.png b/docs/images/WebProxy_result.png
similarity index 100%
rename from images/WebProxy_result.png
rename to docs/images/WebProxy_result.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig1.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig1.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig1.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig1.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig10.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig10.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig10.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig10.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig11.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig11.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig11.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig11.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig12.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig12.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig12.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig12.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig13.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig13.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig13.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig13.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig14.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig14.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig14.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig14.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig15.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig15.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig15.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig15.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig16.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig16.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig16.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig16.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig17.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig17.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig17.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig17.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig18.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig18.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig18.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig18.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig2.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig2.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig2.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig2.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig3.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig3.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig3.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig3.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig4.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig4.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig4.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig4.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig5.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig5.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig5.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig5.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig6.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig6.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig6.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig6.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig7.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig7.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig7.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig7.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig8.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig8.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig8.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig8.png
diff --git a/images/WorkingWithTasksSharePointWorkflowsFig9.png b/docs/images/WorkingWithTasksSharePointWorkflowsFig9.png
similarity index 100%
rename from images/WorkingWithTasksSharePointWorkflowsFig9.png
rename to docs/images/WorkingWithTasksSharePointWorkflowsFig9.png
diff --git a/images/XRANKFormula.gif b/docs/images/XRANKFormula.gif
similarity index 100%
rename from images/XRANKFormula.gif
rename to docs/images/XRANKFormula.gif
diff --git a/images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG b/docs/images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG
similarity index 100%
rename from images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG
rename to docs/images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG
diff --git a/images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG b/docs/images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG
similarity index 100%
rename from images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG
rename to docs/images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG
diff --git a/images/a35fd1af-7194-4c99-b298-bac97025b981.PNG b/docs/images/a35fd1af-7194-4c99-b298-bac97025b981.PNG
similarity index 100%
rename from images/a35fd1af-7194-4c99-b298-bac97025b981.PNG
rename to docs/images/a35fd1af-7194-4c99-b298-bac97025b981.PNG
diff --git a/images/a61afe25-9597-403f-b3fa-d3f630155021.png b/docs/images/a61afe25-9597-403f-b3fa-d3f630155021.png
similarity index 100%
rename from images/a61afe25-9597-403f-b3fa-d3f630155021.png
rename to docs/images/a61afe25-9597-403f-b3fa-d3f630155021.png
diff --git a/images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png b/docs/images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png
similarity index 100%
rename from images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png
rename to docs/images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png
diff --git a/images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg b/docs/images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg
similarity index 100%
rename from images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg
rename to docs/images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg
diff --git a/images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG b/docs/images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG
similarity index 100%
rename from images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG
rename to docs/images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG
diff --git a/images/adm.gif b/docs/images/adm.gif
similarity index 100%
rename from images/adm.gif
rename to docs/images/adm.gif
diff --git a/images/adm_arch.gif b/docs/images/adm_arch.gif
similarity index 100%
rename from images/adm_arch.gif
rename to docs/images/adm_arch.gif
diff --git a/images/adm_dev.gif b/docs/images/adm_dev.gif
similarity index 100%
rename from images/adm_dev.gif
rename to docs/images/adm_dev.gif
diff --git a/images/adm_dev_arch.gif b/docs/images/adm_dev_arch.gif
similarity index 100%
rename from images/adm_dev_arch.gif
rename to docs/images/adm_dev_arch.gif
diff --git a/images/aebc97ae-c886-4d50-94ff-238049a259c7.gif b/docs/images/aebc97ae-c886-4d50-94ff-238049a259c7.gif
similarity index 100%
rename from images/aebc97ae-c886-4d50-94ff-238049a259c7.gif
rename to docs/images/aebc97ae-c886-4d50-94ff-238049a259c7.gif
diff --git a/images/alert_caution.gif b/docs/images/alert_caution.gif
similarity index 100%
rename from images/alert_caution.gif
rename to docs/images/alert_caution.gif
diff --git a/images/alert_note.gif b/docs/images/alert_note.gif
similarity index 100%
rename from images/alert_note.gif
rename to docs/images/alert_note.gif
diff --git a/images/alert_security.gif b/docs/images/alert_security.gif
similarity index 100%
rename from images/alert_security.gif
rename to docs/images/alert_security.gif
diff --git a/images/api-aad-add-function-parameters.png b/docs/images/api-aad-add-function-parameters.png
similarity index 100%
rename from images/api-aad-add-function-parameters.png
rename to docs/images/api-aad-add-function-parameters.png
diff --git a/images/api-aad-add-function.png b/docs/images/api-aad-add-function.png
similarity index 100%
rename from images/api-aad-add-function.png
rename to docs/images/api-aad-add-function.png
diff --git a/images/api-aad-azure-app-service-authentication.png b/docs/images/api-aad-azure-app-service-authentication.png
similarity index 100%
rename from images/api-aad-azure-app-service-authentication.png
rename to docs/images/api-aad-azure-app-service-authentication.png
diff --git a/images/api-aad-create-new-aad-app.png b/docs/images/api-aad-create-new-aad-app.png
similarity index 100%
rename from images/api-aad-create-new-aad-app.png
rename to docs/images/api-aad-create-new-aad-app.png
diff --git a/images/api-aad-create-new-function-app.png b/docs/images/api-aad-create-new-function-app.png
similarity index 100%
rename from images/api-aad-create-new-function-app.png
rename to docs/images/api-aad-create-new-function-app.png
diff --git a/images/api-aad-custom-function.png b/docs/images/api-aad-custom-function.png
similarity index 100%
rename from images/api-aad-custom-function.png
rename to docs/images/api-aad-custom-function.png
diff --git a/images/api-aad-function-authentication-aad-app.png b/docs/images/api-aad-function-authentication-aad-app.png
similarity index 100%
rename from images/api-aad-function-authentication-aad-app.png
rename to docs/images/api-aad-function-authentication-aad-app.png
diff --git a/images/api-aad-function-authentication-aad.png b/docs/images/api-aad-function-authentication-aad.png
similarity index 100%
rename from images/api-aad-function-authentication-aad.png
rename to docs/images/api-aad-function-authentication-aad.png
diff --git a/images/api-aad-function-authentication-login-aad.png b/docs/images/api-aad-function-authentication-login-aad.png
similarity index 100%
rename from images/api-aad-function-authentication-login-aad.png
rename to docs/images/api-aad-function-authentication-login-aad.png
diff --git a/images/api-aad-function-authentication-on.png b/docs/images/api-aad-function-authentication-on.png
similarity index 100%
rename from images/api-aad-function-authentication-on.png
rename to docs/images/api-aad-function-authentication-on.png
diff --git a/images/api-aad-function-authentication-save.png b/docs/images/api-aad-function-authentication-save.png
similarity index 100%
rename from images/api-aad-function-authentication-save.png
rename to docs/images/api-aad-function-authentication-save.png
diff --git a/images/api-aad-function-authentication.png b/docs/images/api-aad-function-authentication.png
similarity index 100%
rename from images/api-aad-function-authentication.png
rename to docs/images/api-aad-function-authentication.png
diff --git a/images/api-aad-function-code.png b/docs/images/api-aad-function-code.png
similarity index 100%
rename from images/api-aad-function-code.png
rename to docs/images/api-aad-function-code.png
diff --git a/images/api-aad-function-cors-delete.png b/docs/images/api-aad-function-cors-delete.png
similarity index 100%
rename from images/api-aad-function-cors-delete.png
rename to docs/images/api-aad-function-cors-delete.png
diff --git a/images/api-aad-function-cors-save.png b/docs/images/api-aad-function-cors-save.png
similarity index 100%
rename from images/api-aad-function-cors-save.png
rename to docs/images/api-aad-function-cors-save.png
diff --git a/images/api-aad-function-cors.png b/docs/images/api-aad-function-cors.png
similarity index 100%
rename from images/api-aad-function-cors.png
rename to docs/images/api-aad-function-cors.png
diff --git a/images/api-aad-platform-features.png b/docs/images/api-aad-platform-features.png
similarity index 100%
rename from images/api-aad-platform-features.png
rename to docs/images/api-aad-platform-features.png
diff --git a/images/api-aad-sign-in.png b/docs/images/api-aad-sign-in.png
similarity index 100%
rename from images/api-aad-sign-in.png
rename to docs/images/api-aad-sign-in.png
diff --git a/images/api-aad-visual-studio-authentication-wizard.png b/docs/images/api-aad-visual-studio-authentication-wizard.png
similarity index 100%
rename from images/api-aad-visual-studio-authentication-wizard.png
rename to docs/images/api-aad-visual-studio-authentication-wizard.png
diff --git a/images/api-aad-webapi-anonymous-unauthorized.png b/docs/images/api-aad-webapi-anonymous-unauthorized.png
similarity index 100%
rename from images/api-aad-webapi-anonymous-unauthorized.png
rename to docs/images/api-aad-webapi-anonymous-unauthorized.png
diff --git a/images/api-aad-webapi-authentication-aad-login.png b/docs/images/api-aad-webapi-authentication-aad-login.png
similarity index 100%
rename from images/api-aad-webapi-authentication-aad-login.png
rename to docs/images/api-aad-webapi-authentication-aad-login.png
diff --git a/images/api-aad-webapi-authentication-aad-ok.png b/docs/images/api-aad-webapi-authentication-aad-ok.png
similarity index 100%
rename from images/api-aad-webapi-authentication-aad-ok.png
rename to docs/images/api-aad-webapi-authentication-aad-ok.png
diff --git a/images/api-aad-webapi-authentication-aad.png b/docs/images/api-aad-webapi-authentication-aad.png
similarity index 100%
rename from images/api-aad-webapi-authentication-aad.png
rename to docs/images/api-aad-webapi-authentication-aad.png
diff --git a/images/api-aad-webapi-authentication-on.png b/docs/images/api-aad-webapi-authentication-on.png
similarity index 100%
rename from images/api-aad-webapi-authentication-on.png
rename to docs/images/api-aad-webapi-authentication-on.png
diff --git a/images/api-aad-webapi-authentication-save.png b/docs/images/api-aad-webapi-authentication-save.png
similarity index 100%
rename from images/api-aad-webapi-authentication-save.png
rename to docs/images/api-aad-webapi-authentication-save.png
diff --git a/images/api-aad-webapi-authentication.png b/docs/images/api-aad-webapi-authentication.png
similarity index 100%
rename from images/api-aad-webapi-authentication.png
rename to docs/images/api-aad-webapi-authentication.png
diff --git a/images/api-aad-webapi-azure-aad.png b/docs/images/api-aad-webapi-azure-aad.png
similarity index 100%
rename from images/api-aad-webapi-azure-aad.png
rename to docs/images/api-aad-webapi-azure-aad.png
diff --git a/images/api-aad-webapi-azure-app-details.png b/docs/images/api-aad-webapi-azure-app-details.png
similarity index 100%
rename from images/api-aad-webapi-azure-app-details.png
rename to docs/images/api-aad-webapi-azure-app-details.png
diff --git a/images/api-aad-webapi-azure-app-registrations.png b/docs/images/api-aad-webapi-azure-app-registrations.png
similarity index 100%
rename from images/api-aad-webapi-azure-app-registrations.png
rename to docs/images/api-aad-webapi-azure-app-registrations.png
diff --git a/images/api-aad-webapi-azure-new-app-registration-create.png b/docs/images/api-aad-webapi-azure-new-app-registration-create.png
similarity index 100%
rename from images/api-aad-webapi-azure-new-app-registration-create.png
rename to docs/images/api-aad-webapi-azure-new-app-registration-create.png
diff --git a/images/api-aad-webapi-azure-new-app-registration.png b/docs/images/api-aad-webapi-azure-new-app-registration.png
similarity index 100%
rename from images/api-aad-webapi-azure-new-app-registration.png
rename to docs/images/api-aad-webapi-azure-new-app-registration.png
diff --git a/images/api-aad-webapi-azure-sign-in.png b/docs/images/api-aad-webapi-azure-sign-in.png
similarity index 100%
rename from images/api-aad-webapi-azure-sign-in.png
rename to docs/images/api-aad-webapi-azure-sign-in.png
diff --git a/images/api-aad-webapi-response-anonymous.png b/docs/images/api-aad-webapi-response-anonymous.png
similarity index 100%
rename from images/api-aad-webapi-response-anonymous.png
rename to docs/images/api-aad-webapi-response-anonymous.png
diff --git a/images/api-aad-webapi-vs-cors-nuget.png b/docs/images/api-aad-webapi-vs-cors-nuget.png
similarity index 100%
rename from images/api-aad-webapi-vs-cors-nuget.png
rename to docs/images/api-aad-webapi-vs-cors-nuget.png
diff --git a/images/api-aad-webapi-vs-create-app-service.png b/docs/images/api-aad-webapi-vs-create-app-service.png
similarity index 100%
rename from images/api-aad-webapi-vs-create-app-service.png
rename to docs/images/api-aad-webapi-vs-create-app-service.png
diff --git a/images/api-aad-webapi-vs-host-app-service.png b/docs/images/api-aad-webapi-vs-host-app-service.png
similarity index 100%
rename from images/api-aad-webapi-vs-host-app-service.png
rename to docs/images/api-aad-webapi-vs-host-app-service.png
diff --git a/images/api-aad-webapi-vs-manage-nuget.png b/docs/images/api-aad-webapi-vs-manage-nuget.png
similarity index 100%
rename from images/api-aad-webapi-vs-manage-nuget.png
rename to docs/images/api-aad-webapi-vs-manage-nuget.png
diff --git a/images/api-aad-webapi-vs-no-authentication.png b/docs/images/api-aad-webapi-vs-no-authentication.png
similarity index 100%
rename from images/api-aad-webapi-vs-no-authentication.png
rename to docs/images/api-aad-webapi-vs-no-authentication.png
diff --git a/images/api-aad-webapi-vs-publish-settings.png b/docs/images/api-aad-webapi-vs-publish-settings.png
similarity index 100%
rename from images/api-aad-webapi-vs-publish-settings.png
rename to docs/images/api-aad-webapi-vs-publish-settings.png
diff --git a/images/api-aad-webapi-vs-publish.png b/docs/images/api-aad-webapi-vs-publish.png
similarity index 100%
rename from images/api-aad-webapi-vs-publish.png
rename to docs/images/api-aad-webapi-vs-publish.png
diff --git a/images/api-aad-webapi-vs-web-application.png b/docs/images/api-aad-webapi-vs-web-application.png
similarity index 100%
rename from images/api-aad-webapi-vs-web-application.png
rename to docs/images/api-aad-webapi-vs-web-application.png
diff --git a/images/api-aad-webapi-vs-webapi.png b/docs/images/api-aad-webapi-vs-webapi.png
similarity index 100%
rename from images/api-aad-webapi-vs-webapi.png
rename to docs/images/api-aad-webapi-vs-webapi.png
diff --git a/images/app-installed-your-site.png b/docs/images/app-installed-your-site.png
similarity index 100%
rename from images/app-installed-your-site.png
rename to docs/images/app-installed-your-site.png
diff --git a/images/arch.gif b/docs/images/arch.gif
similarity index 100%
rename from images/arch.gif
rename to docs/images/arch.gif
diff --git a/images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg b/docs/images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg
similarity index 100%
rename from images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg
rename to docs/images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg
diff --git a/images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png b/docs/images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png
similarity index 100%
rename from images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png
rename to docs/images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png
diff --git a/images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG b/docs/images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG
similarity index 100%
rename from images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG
rename to docs/images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG
diff --git a/images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif b/docs/images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif
similarity index 100%
rename from images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif
rename to docs/images/b86ecdb8-88a7-4407-af86-07d2442235dc.gif
diff --git a/images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG b/docs/images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG
similarity index 100%
rename from images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG
rename to docs/images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG
diff --git a/images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG b/docs/images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG
similarity index 100%
rename from images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG
rename to docs/images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG
diff --git a/images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif b/docs/images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif
similarity index 100%
rename from images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif
rename to docs/images/bee8bbc5-a93d-4695-927b-c10e0e63ddf9.gif
diff --git a/images/big_adm.gif b/docs/images/big_adm.gif
similarity index 100%
rename from images/big_adm.gif
rename to docs/images/big_adm.gif
diff --git a/images/big_arch.gif b/docs/images/big_arch.gif
similarity index 100%
rename from images/big_arch.gif
rename to docs/images/big_arch.gif
diff --git a/images/big_dev.gif b/docs/images/big_dev.gif
similarity index 100%
rename from images/big_dev.gif
rename to docs/images/big_dev.gif
diff --git a/images/big_kw.gif b/docs/images/big_kw.gif
similarity index 100%
rename from images/big_kw.gif
rename to docs/images/big_kw.gif
diff --git a/images/box.gif b/docs/images/box.gif
similarity index 100%
rename from images/box.gif
rename to docs/images/box.gif
diff --git a/images/bullet.gif b/docs/images/bullet.gif
similarity index 100%
rename from images/bullet.gif
rename to docs/images/bullet.gif
diff --git a/images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif b/docs/images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif
similarity index 100%
rename from images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif
rename to docs/images/c046bc5c-1e31-4ac6-9cba-05482cc36915.gif
diff --git a/images/c1230e3b-d149-413c-aa66-d258250a4512.PNG b/docs/images/c1230e3b-d149-413c-aa66-d258250a4512.PNG
similarity index 100%
rename from images/c1230e3b-d149-413c-aa66-d258250a4512.PNG
rename to docs/images/c1230e3b-d149-413c-aa66-d258250a4512.PNG
diff --git a/images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG b/docs/images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG
similarity index 100%
rename from images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG
rename to docs/images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG
diff --git a/images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG b/docs/images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG
similarity index 100%
rename from images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG
rename to docs/images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG
diff --git a/images/cdn-add-webpart-to-site.png b/docs/images/cdn-add-webpart-to-site.png
similarity index 100%
rename from images/cdn-add-webpart-to-site.png
rename to docs/images/cdn-add-webpart-to-site.png
diff --git a/images/cdn-create-webpart-yo.png b/docs/images/cdn-create-webpart-yo.png
similarity index 100%
rename from images/cdn-create-webpart-yo.png
rename to docs/images/cdn-create-webpart-yo.png
diff --git a/images/cdn-helloworld-folder.png b/docs/images/cdn-helloworld-folder.png
similarity index 100%
rename from images/cdn-helloworld-folder.png
rename to docs/images/cdn-helloworld-folder.png
diff --git a/images/cdn-public-origins.png b/docs/images/cdn-public-origins.png
similarity index 100%
rename from images/cdn-public-origins.png
rename to docs/images/cdn-public-origins.png
diff --git a/images/cdn-upload-solution-to-app-catalog.png b/docs/images/cdn-upload-solution-to-app-catalog.png
similarity index 100%
rename from images/cdn-upload-solution-to-app-catalog.png
rename to docs/images/cdn-upload-solution-to-app-catalog.png
diff --git a/images/cdn-web-part-f12-source.png b/docs/images/cdn-web-part-f12-source.png
similarity index 100%
rename from images/cdn-web-part-f12-source.png
rename to docs/images/cdn-web-part-f12-source.png
diff --git a/images/cdn-web-part-files-in-folder.png b/docs/images/cdn-web-part-files-in-folder.png
similarity index 100%
rename from images/cdn-web-part-files-in-folder.png
rename to docs/images/cdn-web-part-files-in-folder.png
diff --git a/images/cdn-web-part-picker.png b/docs/images/cdn-web-part-picker.png
similarity index 100%
rename from images/cdn-web-part-picker.png
rename to docs/images/cdn-web-part-picker.png
diff --git a/images/cdn-web-part-rendering.png b/docs/images/cdn-web-part-rendering.png
similarity index 100%
rename from images/cdn-web-part-rendering.png
rename to docs/images/cdn-web-part-rendering.png
diff --git a/images/cdn-write-manifest-json.png b/docs/images/cdn-write-manifest-json.png
similarity index 100%
rename from images/cdn-write-manifest-json.png
rename to docs/images/cdn-write-manifest-json.png
diff --git a/images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif b/docs/images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif
similarity index 100%
rename from images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif
rename to docs/images/ce88b78d-5d41-406f-bf51-bee45ad2fe8f.gif
diff --git a/images/chrome-load-unsafe-scripts.png b/docs/images/chrome-load-unsafe-scripts.png
similarity index 100%
rename from images/chrome-load-unsafe-scripts.png
rename to docs/images/chrome-load-unsafe-scripts.png
diff --git a/images/collall.gif b/docs/images/collall.gif
similarity index 100%
rename from images/collall.gif
rename to docs/images/collall.gif
diff --git a/images/collapse.gif b/docs/images/collapse.gif
similarity index 100%
rename from images/collapse.gif
rename to docs/images/collapse.gif
diff --git a/images/collapse_all.gif b/docs/images/collapse_all.gif
similarity index 100%
rename from images/collapse_all.gif
rename to docs/images/collapse_all.gif
diff --git a/images/contribute-docs-clone-options.png b/docs/images/contribute-docs-clone-options.png
similarity index 100%
rename from images/contribute-docs-clone-options.png
rename to docs/images/contribute-docs-clone-options.png
diff --git a/images/contribute-docs-submit-pr.png b/docs/images/contribute-docs-submit-pr.png
similarity index 100%
rename from images/contribute-docs-submit-pr.png
rename to docs/images/contribute-docs-submit-pr.png
diff --git a/images/contribute-fork-docs-repo.png b/docs/images/contribute-fork-docs-repo.png
similarity index 100%
rename from images/contribute-fork-docs-repo.png
rename to docs/images/contribute-fork-docs-repo.png
diff --git a/images/copycode.gif b/docs/images/copycode.gif
similarity index 100%
rename from images/copycode.gif
rename to docs/images/copycode.gif
diff --git a/images/copycodeHighlight.gif b/docs/images/copycodeHighlight.gif
similarity index 100%
rename from images/copycodeHighlight.gif
rename to docs/images/copycodeHighlight.gif
diff --git a/images/custom-property-pane-control-cascading-items-loaded-enabled.png b/docs/images/custom-property-pane-control-cascading-items-loaded-enabled.png
similarity index 100%
rename from images/custom-property-pane-control-cascading-items-loaded-enabled.png
rename to docs/images/custom-property-pane-control-cascading-items-loaded-enabled.png
diff --git a/images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png b/docs/images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png
similarity index 100%
rename from images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png
rename to docs/images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png
diff --git a/images/custom-property-pane-control-cascading-loading-items.png b/docs/images/custom-property-pane-control-cascading-loading-items.png
similarity index 100%
rename from images/custom-property-pane-control-cascading-loading-items.png
rename to docs/images/custom-property-pane-control-cascading-loading-items.png
diff --git a/images/custom-property-pane-control-cascading-loading-lists.png b/docs/images/custom-property-pane-control-cascading-loading-lists.png
similarity index 100%
rename from images/custom-property-pane-control-cascading-loading-lists.png
rename to docs/images/custom-property-pane-control-cascading-loading-lists.png
diff --git a/images/custom-property-pane-control-cascading-selected-list-item.png b/docs/images/custom-property-pane-control-cascading-selected-list-item.png
similarity index 100%
rename from images/custom-property-pane-control-cascading-selected-list-item.png
rename to docs/images/custom-property-pane-control-cascading-selected-list-item.png
diff --git a/images/custom-property-pane-control-components-folder.png b/docs/images/custom-property-pane-control-components-folder.png
similarity index 100%
rename from images/custom-property-pane-control-components-folder.png
rename to docs/images/custom-property-pane-control-components-folder.png
diff --git a/images/custom-property-pane-control-item-property-web-part-manifest.png b/docs/images/custom-property-pane-control-item-property-web-part-manifest.png
similarity index 100%
rename from images/custom-property-pane-control-item-property-web-part-manifest.png
rename to docs/images/custom-property-pane-control-item-property-web-part-manifest.png
diff --git a/images/custom-property-pane-control-list-property-web-part-manifest.png b/docs/images/custom-property-pane-control-list-property-web-part-manifest.png
similarity index 100%
rename from images/custom-property-pane-control-list-property-web-part-manifest.png
rename to docs/images/custom-property-pane-control-list-property-web-part-manifest.png
diff --git a/images/custom-property-pane-control-loading-options.png b/docs/images/custom-property-pane-control-loading-options.png
similarity index 100%
rename from images/custom-property-pane-control-loading-options.png
rename to docs/images/custom-property-pane-control-loading-options.png
diff --git a/images/custom-property-pane-control-selecting-option.png b/docs/images/custom-property-pane-control-selecting-option.png
similarity index 100%
rename from images/custom-property-pane-control-selecting-option.png
rename to docs/images/custom-property-pane-control-selecting-option.png
diff --git a/images/custom-property-pane-control-visual-studio-code.png b/docs/images/custom-property-pane-control-visual-studio-code.png
similarity index 100%
rename from images/custom-property-pane-control-visual-studio-code.png
rename to docs/images/custom-property-pane-control-visual-studio-code.png
diff --git a/images/custom-property-pane-control-web-part-first-run.png b/docs/images/custom-property-pane-control-web-part-first-run.png
similarity index 100%
rename from images/custom-property-pane-control-web-part-first-run.png
rename to docs/images/custom-property-pane-control-web-part-first-run.png
diff --git a/images/custom-property-pane-control-web-part-imports.png b/docs/images/custom-property-pane-control-web-part-imports.png
similarity index 100%
rename from images/custom-property-pane-control-web-part-imports.png
rename to docs/images/custom-property-pane-control-web-part-imports.png
diff --git a/images/custom-property-pane-control-yeoman.png b/docs/images/custom-property-pane-control-yeoman.png
similarity index 100%
rename from images/custom-property-pane-control-yeoman.png
rename to docs/images/custom-property-pane-control-yeoman.png
diff --git a/images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG b/docs/images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG
similarity index 100%
rename from images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG
rename to docs/images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG
diff --git a/images/d4e17424-c06b-4635-aab8-4912cee5fe35.png b/docs/images/d4e17424-c06b-4635-aab8-4912cee5fe35.png
similarity index 100%
rename from images/d4e17424-c06b-4635-aab8-4912cee5fe35.png
rename to docs/images/d4e17424-c06b-4635-aab8-4912cee5fe35.png
diff --git a/images/d69871f6-c503-463b-bf96-4b6d7306c313.png b/docs/images/d69871f6-c503-463b-bf96-4b6d7306c313.png
similarity index 100%
rename from images/d69871f6-c503-463b-bf96-4b6d7306c313.png
rename to docs/images/d69871f6-c503-463b-bf96-4b6d7306c313.png
diff --git a/images/datatables-sewp-filter.png b/docs/images/datatables-sewp-filter.png
similarity index 100%
rename from images/datatables-sewp-filter.png
rename to docs/images/datatables-sewp-filter.png
diff --git a/images/datatables-sewp.png b/docs/images/datatables-sewp.png
similarity index 100%
rename from images/datatables-sewp.png
rename to docs/images/datatables-sewp.png
diff --git a/images/datatables-spfx-list-configured.png b/docs/images/datatables-spfx-list-configured.png
similarity index 100%
rename from images/datatables-spfx-list-configured.png
rename to docs/images/datatables-spfx-list-configured.png
diff --git a/images/datatables-spfx-listname-property.png b/docs/images/datatables-spfx-listname-property.png
similarity index 100%
rename from images/datatables-spfx-listname-property.png
rename to docs/images/datatables-spfx-listname-property.png
diff --git a/images/datatables-spfx.png b/docs/images/datatables-spfx.png
similarity index 100%
rename from images/datatables-spfx.png
rename to docs/images/datatables-spfx.png
diff --git a/images/datatables-vscode.png b/docs/images/datatables-vscode.png
similarity index 100%
rename from images/datatables-vscode.png
rename to docs/images/datatables-vscode.png
diff --git a/images/datatables-yeoman.png b/docs/images/datatables-yeoman.png
similarity index 100%
rename from images/datatables-yeoman.png
rename to docs/images/datatables-yeoman.png
diff --git a/images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG b/docs/images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG
similarity index 100%
rename from images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG
rename to docs/images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG
diff --git a/images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG b/docs/images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG
similarity index 100%
rename from images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG
rename to docs/images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG
diff --git a/images/deploy-container-create-helloworld-webpart.png b/docs/images/deploy-container-create-helloworld-webpart.png
similarity index 100%
rename from images/deploy-container-create-helloworld-webpart.png
rename to docs/images/deploy-container-create-helloworld-webpart.png
diff --git a/images/deploy-create-cdn-endpoint.png b/docs/images/deploy-create-cdn-endpoint.png
similarity index 100%
rename from images/deploy-create-cdn-endpoint.png
rename to docs/images/deploy-create-cdn-endpoint.png
diff --git a/images/deploy-create-cdn-profile.png b/docs/images/deploy-create-cdn-profile.png
similarity index 100%
rename from images/deploy-create-cdn-profile.png
rename to docs/images/deploy-create-cdn-profile.png
diff --git a/images/deploy-create-storage-account.png b/docs/images/deploy-create-storage-account.png
similarity index 100%
rename from images/deploy-create-storage-account.png
rename to docs/images/deploy-create-storage-account.png
diff --git a/images/deploy-option-blob-container.png b/docs/images/deploy-option-blob-container.png
similarity index 100%
rename from images/deploy-option-blob-container.png
rename to docs/images/deploy-option-blob-container.png
diff --git a/images/deploy-storage-account-accesskey.png b/docs/images/deploy-storage-account-accesskey.png
similarity index 100%
rename from images/deploy-storage-account-accesskey.png
rename to docs/images/deploy-storage-account-accesskey.png
diff --git a/images/design-manager-preview-UI.jpg b/docs/images/design-manager-preview-UI.jpg
similarity index 100%
rename from images/design-manager-preview-UI.jpg
rename to docs/images/design-manager-preview-UI.jpg
diff --git a/images/design-wp-contexual-edits.png b/docs/images/design-wp-contexual-edits.png
similarity index 100%
rename from images/design-wp-contexual-edits.png
rename to docs/images/design-wp-contexual-edits.png
diff --git a/images/design-wp-item-level-edits.png b/docs/images/design-wp-item-level-edits.png
similarity index 100%
rename from images/design-wp-item-level-edits.png
rename to docs/images/design-wp-item-level-edits.png
diff --git a/images/design-wp-pp-accordion-groups.png b/docs/images/design-wp-pp-accordion-groups.png
similarity index 100%
rename from images/design-wp-pp-accordion-groups.png
rename to docs/images/design-wp-pp-accordion-groups.png
diff --git a/images/design-wp-pp-accordion.png b/docs/images/design-wp-pp-accordion.png
similarity index 100%
rename from images/design-wp-pp-accordion.png
rename to docs/images/design-wp-pp-accordion.png
diff --git a/images/design-wp-pp-non-reactive.png b/docs/images/design-wp-pp-non-reactive.png
similarity index 100%
rename from images/design-wp-pp-non-reactive.png
rename to docs/images/design-wp-pp-non-reactive.png
diff --git a/images/design-wp-pp-pages-step1.png b/docs/images/design-wp-pp-pages-step1.png
similarity index 100%
rename from images/design-wp-pp-pages-step1.png
rename to docs/images/design-wp-pp-pages-step1.png
diff --git a/images/design-wp-pp-pages-step2.png b/docs/images/design-wp-pp-pages-step2.png
similarity index 100%
rename from images/design-wp-pp-pages-step2.png
rename to docs/images/design-wp-pp-pages-step2.png
diff --git a/images/design-wp-pp-pages-step3.png b/docs/images/design-wp-pp-pages-step3.png
similarity index 100%
rename from images/design-wp-pp-pages-step3.png
rename to docs/images/design-wp-pp-pages-step3.png
diff --git a/images/design-wp-pp-reactive.png b/docs/images/design-wp-pp-reactive.png
similarity index 100%
rename from images/design-wp-pp-reactive.png
rename to docs/images/design-wp-pp-reactive.png
diff --git a/images/design-wp-pp-single.png b/docs/images/design-wp-pp-single.png
similarity index 100%
rename from images/design-wp-pp-single.png
rename to docs/images/design-wp-pp-single.png
diff --git a/images/design-wp-pp.png b/docs/images/design-wp-pp.png
similarity index 100%
rename from images/design-wp-pp.png
rename to docs/images/design-wp-pp.png
diff --git a/images/design-wp-responsive-max-width.png b/docs/images/design-wp-responsive-max-width.png
similarity index 100%
rename from images/design-wp-responsive-max-width.png
rename to docs/images/design-wp-responsive-max-width.png
diff --git a/images/design-wp-responsive-min-width.png b/docs/images/design-wp-responsive-min-width.png
similarity index 100%
rename from images/design-wp-responsive-min-width.png
rename to docs/images/design-wp-responsive-min-width.png
diff --git a/images/design-wp-todo-example.png b/docs/images/design-wp-todo-example.png
similarity index 100%
rename from images/design-wp-todo-example.png
rename to docs/images/design-wp-todo-example.png
diff --git a/images/design-wp-todo-fabric-animations.png b/docs/images/design-wp-todo-fabric-animations.png
similarity index 100%
rename from images/design-wp-todo-fabric-animations.png
rename to docs/images/design-wp-todo-fabric-animations.png
diff --git a/images/design-wp-todo-loading-indicator.png b/docs/images/design-wp-todo-loading-indicator.png
similarity index 100%
rename from images/design-wp-todo-loading-indicator.png
rename to docs/images/design-wp-todo-loading-indicator.png
diff --git a/images/design-wp-todo-pp-checkbox.png b/docs/images/design-wp-todo-pp-checkbox.png
similarity index 100%
rename from images/design-wp-todo-pp-checkbox.png
rename to docs/images/design-wp-todo-pp-checkbox.png
diff --git a/images/design-wp-todo-pp-description.png b/docs/images/design-wp-todo-pp-description.png
similarity index 100%
rename from images/design-wp-todo-pp-description.png
rename to docs/images/design-wp-todo-pp-description.png
diff --git a/images/design-wp-todo-pp-dropdown.png b/docs/images/design-wp-todo-pp-dropdown.png
similarity index 100%
rename from images/design-wp-todo-pp-dropdown.png
rename to docs/images/design-wp-todo-pp-dropdown.png
diff --git a/images/design-wp-todo-pp-slider.png b/docs/images/design-wp-todo-pp-slider.png
similarity index 100%
rename from images/design-wp-todo-pp-slider.png
rename to docs/images/design-wp-todo-pp-slider.png
diff --git a/images/design-wp-toolbar.png b/docs/images/design-wp-toolbar.png
similarity index 100%
rename from images/design-wp-toolbar.png
rename to docs/images/design-wp-toolbar.png
diff --git a/images/design-wp-toolbox.png b/docs/images/design-wp-toolbox.png
similarity index 100%
rename from images/design-wp-toolbox.png
rename to docs/images/design-wp-toolbox.png
diff --git a/images/dev.gif b/docs/images/dev.gif
similarity index 100%
rename from images/dev.gif
rename to docs/images/dev.gif
diff --git a/images/dev_arch.gif b/docs/images/dev_arch.gif
similarity index 100%
rename from images/dev_arch.gif
rename to docs/images/dev_arch.gif
diff --git a/images/dropdown.gif b/docs/images/dropdown.gif
similarity index 100%
rename from images/dropdown.gif
rename to docs/images/dropdown.gif
diff --git a/images/dropdownHover.gif b/docs/images/dropdownHover.gif
similarity index 100%
rename from images/dropdownHover.gif
rename to docs/images/dropdownHover.gif
diff --git a/images/drpdown.gif b/docs/images/drpdown.gif
similarity index 100%
rename from images/drpdown.gif
rename to docs/images/drpdown.gif
diff --git a/images/drpdown_orange.gif b/docs/images/drpdown_orange.gif
similarity index 100%
rename from images/drpdown_orange.gif
rename to docs/images/drpdown_orange.gif
diff --git a/images/drpdown_orange_up.gif b/docs/images/drpdown_orange_up.gif
similarity index 100%
rename from images/drpdown_orange_up.gif
rename to docs/images/drpdown_orange_up.gif
diff --git a/images/drpup.gif b/docs/images/drpup.gif
similarity index 100%
rename from images/drpup.gif
rename to docs/images/drpup.gif
diff --git a/images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif b/docs/images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif
similarity index 100%
rename from images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif
rename to docs/images/e2cf6848-bd29-416b-b397-a1d670bd2910.gif
diff --git a/images/e3718687-682a-41a8-92b5-4eff9070348d.gif b/docs/images/e3718687-682a-41a8-92b5-4eff9070348d.gif
similarity index 100%
rename from images/e3718687-682a-41a8-92b5-4eff9070348d.gif
rename to docs/images/e3718687-682a-41a8-92b5-4eff9070348d.gif
diff --git a/images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif b/docs/images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif
similarity index 100%
rename from images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif
rename to docs/images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif
diff --git a/images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG b/docs/images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG
similarity index 100%
rename from images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG
rename to docs/images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG
diff --git a/images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG b/docs/images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG
similarity index 100%
rename from images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG
rename to docs/images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG
diff --git a/images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG b/docs/images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG
similarity index 100%
rename from images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG
rename to docs/images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG
diff --git a/images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG b/docs/images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG
similarity index 100%
rename from images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG
rename to docs/images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG
diff --git a/images/e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png b/docs/images/e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png
similarity index 100%
rename from images/e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png
rename to docs/images/e5f8a9a2-e5fb-42d1-b19a-300178c626fb.png
diff --git a/images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png b/docs/images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png
similarity index 100%
rename from images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png
rename to docs/images/e70a43c1-43ba-4f5c-b25f-e3995f18dd16.png
diff --git a/images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif b/docs/images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif
similarity index 100%
rename from images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif
rename to docs/images/e9cf225a-7040-4545-8db2-9e6f04e7a6eb.gif
diff --git a/images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif b/docs/images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif
similarity index 100%
rename from images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif
rename to docs/images/eb20da0e-793f-43af-aa5e-67f85cdfa2df.gif
diff --git a/images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png b/docs/images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png
similarity index 100%
rename from images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png
rename to docs/images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png
diff --git a/images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg b/docs/images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg
similarity index 100%
rename from images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg
rename to docs/images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg
diff --git a/images/ec60797c-d329-4922-a811-70c64598f4d5.PNG b/docs/images/ec60797c-d329-4922-a811-70c64598f4d5.PNG
similarity index 100%
rename from images/ec60797c-d329-4922-a811-70c64598f4d5.PNG
rename to docs/images/ec60797c-d329-4922-a811-70c64598f4d5.PNG
diff --git a/images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif b/docs/images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif
similarity index 100%
rename from images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif
rename to docs/images/ed480e23-e0e8-4896-93b1-98a94f50b9a0.gif
diff --git a/images/edit-webpart-classic-page.png b/docs/images/edit-webpart-classic-page.png
similarity index 100%
rename from images/edit-webpart-classic-page.png
rename to docs/images/edit-webpart-classic-page.png
diff --git a/images/edit-webpart-modern-page.png b/docs/images/edit-webpart-modern-page.png
similarity index 100%
rename from images/edit-webpart-modern-page.png
rename to docs/images/edit-webpart-modern-page.png
diff --git a/images/enterprise-guidance-trust-spfx-dialog.png b/docs/images/enterprise-guidance-trust-spfx-dialog.png
similarity index 100%
rename from images/enterprise-guidance-trust-spfx-dialog.png
rename to docs/images/enterprise-guidance-trust-spfx-dialog.png
diff --git a/images/exp.gif b/docs/images/exp.gif
similarity index 100%
rename from images/exp.gif
rename to docs/images/exp.gif
diff --git a/images/expall.gif b/docs/images/expall.gif
similarity index 100%
rename from images/expall.gif
rename to docs/images/expall.gif
diff --git a/images/expand_all.gif b/docs/images/expand_all.gif
similarity index 100%
rename from images/expand_all.gif
rename to docs/images/expand_all.gif
diff --git a/images/ext-app-alert-sp-page.png b/docs/images/ext-app-alert-sp-page.png
similarity index 100%
rename from images/ext-app-alert-sp-page.png
rename to docs/images/ext-app-alert-sp-page.png
diff --git a/images/ext-app-approve-cdn-address.png b/docs/images/ext-app-approve-cdn-address.png
similarity index 100%
rename from images/ext-app-approve-cdn-address.png
rename to docs/images/ext-app-approve-cdn-address.png
diff --git a/images/ext-app-assets-folder.png b/docs/images/ext-app-assets-folder.png
similarity index 100%
rename from images/ext-app-assets-folder.png
rename to docs/images/ext-app-assets-folder.png
diff --git a/images/ext-app-cdn-folder-created.png b/docs/images/ext-app-cdn-folder-created.png
similarity index 100%
rename from images/ext-app-cdn-folder-created.png
rename to docs/images/ext-app-cdn-folder-created.png
diff --git a/images/ext-app-cdn-origins-pending.png b/docs/images/ext-app-cdn-origins-pending.png
similarity index 100%
rename from images/ext-app-cdn-origins-pending.png
rename to docs/images/ext-app-cdn-origins-pending.png
diff --git a/images/ext-app-cdn-write-manifest.png b/docs/images/ext-app-cdn-write-manifest.png
similarity index 100%
rename from images/ext-app-cdn-write-manifest.png
rename to docs/images/ext-app-cdn-write-manifest.png
diff --git a/images/ext-app-debug-manifest-message.png b/docs/images/ext-app-debug-manifest-message.png
similarity index 100%
rename from images/ext-app-debug-manifest-message.png
rename to docs/images/ext-app-debug-manifest-message.png
diff --git a/images/ext-app-gulp-serve.png b/docs/images/ext-app-gulp-serve.png
similarity index 100%
rename from images/ext-app-gulp-serve.png
rename to docs/images/ext-app-gulp-serve.png
diff --git a/images/ext-app-header-footer-visible.png b/docs/images/ext-app-header-footer-visible.png
similarity index 100%
rename from images/ext-app-header-footer-visible.png
rename to docs/images/ext-app-header-footer-visible.png
diff --git a/images/ext-app-install-solution-to-site.png b/docs/images/ext-app-install-solution-to-site.png
similarity index 100%
rename from images/ext-app-install-solution-to-site.png
rename to docs/images/ext-app-install-solution-to-site.png
diff --git a/images/ext-app-sppkg-deploy-trust.png b/docs/images/ext-app-sppkg-deploy-trust.png
similarity index 100%
rename from images/ext-app-sppkg-deploy-trust.png
rename to docs/images/ext-app-sppkg-deploy-trust.png
diff --git a/images/ext-app-vscode-app-base.png b/docs/images/ext-app-vscode-app-base.png
similarity index 100%
rename from images/ext-app-vscode-app-base.png
rename to docs/images/ext-app-vscode-app-base.png
diff --git a/images/ext-app-vscode-manifest.png b/docs/images/ext-app-vscode-manifest.png
similarity index 100%
rename from images/ext-app-vscode-manifest.png
rename to docs/images/ext-app-vscode-manifest.png
diff --git a/images/ext-app-vscode-methods.png b/docs/images/ext-app-vscode-methods.png
similarity index 100%
rename from images/ext-app-vscode-methods.png
rename to docs/images/ext-app-vscode-methods.png
diff --git a/images/ext-app-vscode-solution-structure.png b/docs/images/ext-app-vscode-solution-structure.png
similarity index 100%
rename from images/ext-app-vscode-solution-structure.png
rename to docs/images/ext-app-vscode-solution-structure.png
diff --git a/images/ext-com-accept-debug-scripts.png b/docs/images/ext-com-accept-debug-scripts.png
similarity index 100%
rename from images/ext-com-accept-debug-scripts.png
rename to docs/images/ext-com-accept-debug-scripts.png
diff --git a/images/ext-com-assets-folder.png b/docs/images/ext-com-assets-folder.png
similarity index 100%
rename from images/ext-com-assets-folder.png
rename to docs/images/ext-com-assets-folder.png
diff --git a/images/ext-com-create-new-list.png b/docs/images/ext-com-create-new-list.png
similarity index 100%
rename from images/ext-com-create-new-list.png
rename to docs/images/ext-com-create-new-list.png
diff --git a/images/ext-com-default-customizer-output.png b/docs/images/ext-com-default-customizer-output.png
similarity index 100%
rename from images/ext-com-default-customizer-output.png
rename to docs/images/ext-com-default-customizer-output.png
diff --git a/images/ext-com-dialog-button-in-toolbar.png b/docs/images/ext-com-dialog-button-in-toolbar.png
similarity index 100%
rename from images/ext-com-dialog-button-in-toolbar.png
rename to docs/images/ext-com-dialog-button-in-toolbar.png
diff --git a/images/ext-com-dialog-debug-scripts.png b/docs/images/ext-com-dialog-debug-scripts.png
similarity index 100%
rename from images/ext-com-dialog-debug-scripts.png
rename to docs/images/ext-com-dialog-debug-scripts.png
diff --git a/images/ext-com-dialog-gulp-serve.png b/docs/images/ext-com-dialog-gulp-serve.png
similarity index 100%
rename from images/ext-com-dialog-gulp-serve.png
rename to docs/images/ext-com-dialog-gulp-serve.png
diff --git a/images/ext-com-dialog-oob-alert-dialog.png b/docs/images/ext-com-dialog-oob-alert-dialog.png
similarity index 100%
rename from images/ext-com-dialog-oob-alert-dialog.png
rename to docs/images/ext-com-dialog-oob-alert-dialog.png
diff --git a/images/ext-com-dialog-output.png b/docs/images/ext-com-dialog-output.png
similarity index 100%
rename from images/ext-com-dialog-output.png
rename to docs/images/ext-com-dialog-output.png
diff --git a/images/ext-com-dialog-visible-deployment.png b/docs/images/ext-com-dialog-visible-deployment.png
similarity index 100%
rename from images/ext-com-dialog-visible-deployment.png
rename to docs/images/ext-com-dialog-visible-deployment.png
diff --git a/images/ext-com-dialog-visible-dialog.png b/docs/images/ext-com-dialog-visible-dialog.png
similarity index 100%
rename from images/ext-com-dialog-visible-dialog.png
rename to docs/images/ext-com-dialog-visible-dialog.png
diff --git a/images/ext-com-dialog-vs-code-initial.png b/docs/images/ext-com-dialog-vs-code-initial.png
similarity index 100%
rename from images/ext-com-dialog-vs-code-initial.png
rename to docs/images/ext-com-dialog-vs-code-initial.png
diff --git a/images/ext-com-dialog-yeoman-complete.png b/docs/images/ext-com-dialog-yeoman-complete.png
similarity index 100%
rename from images/ext-com-dialog-yeoman-complete.png
rename to docs/images/ext-com-dialog-yeoman-complete.png
diff --git a/images/ext-com-dialog-yeoman-prompts.png b/docs/images/ext-com-dialog-yeoman-prompts.png
similarity index 100%
rename from images/ext-com-dialog-yeoman-prompts.png
rename to docs/images/ext-com-dialog-yeoman-prompts.png
diff --git a/images/ext-com-install-solution-to-site.png b/docs/images/ext-com-install-solution-to-site.png
similarity index 100%
rename from images/ext-com-install-solution-to-site.png
rename to docs/images/ext-com-install-solution-to-site.png
diff --git a/images/ext-com-sppkg-deploy-trust.png b/docs/images/ext-com-sppkg-deploy-trust.png
similarity index 100%
rename from images/ext-com-sppkg-deploy-trust.png
rename to docs/images/ext-com-sppkg-deploy-trust.png
diff --git a/images/ext-com-vscode-base.png b/docs/images/ext-com-vscode-base.png
similarity index 100%
rename from images/ext-com-vscode-base.png
rename to docs/images/ext-com-vscode-base.png
diff --git a/images/ext-com-vscode-manifest.png b/docs/images/ext-com-vscode-manifest.png
similarity index 100%
rename from images/ext-com-vscode-manifest.png
rename to docs/images/ext-com-vscode-manifest.png
diff --git a/images/ext-com-vscode-solution-structure.png b/docs/images/ext-com-vscode-solution-structure.png
similarity index 100%
rename from images/ext-com-vscode-solution-structure.png
rename to docs/images/ext-com-vscode-solution-structure.png
diff --git a/images/ext-com-yeoman-complete.png b/docs/images/ext-com-yeoman-complete.png
similarity index 100%
rename from images/ext-com-yeoman-complete.png
rename to docs/images/ext-com-yeoman-complete.png
diff --git a/images/ext-com-yeoman-prompts.png b/docs/images/ext-com-yeoman-prompts.png
similarity index 100%
rename from images/ext-com-yeoman-prompts.png
rename to docs/images/ext-com-yeoman-prompts.png
diff --git a/images/ext-erro-loading-debug-manifests.png b/docs/images/ext-erro-loading-debug-manifests.png
similarity index 100%
rename from images/ext-erro-loading-debug-manifests.png
rename to docs/images/ext-erro-loading-debug-manifests.png
diff --git a/images/ext-field-accept-debug-scripts.png b/docs/images/ext-field-accept-debug-scripts.png
similarity index 100%
rename from images/ext-field-accept-debug-scripts.png
rename to docs/images/ext-field-accept-debug-scripts.png
diff --git a/images/ext-field-add-field-to-list.png b/docs/images/ext-field-add-field-to-list.png
similarity index 100%
rename from images/ext-field-add-field-to-list.png
rename to docs/images/ext-field-add-field-to-list.png
diff --git a/images/ext-field-assets-folder.png b/docs/images/ext-field-assets-folder.png
similarity index 100%
rename from images/ext-field-assets-folder.png
rename to docs/images/ext-field-assets-folder.png
diff --git a/images/ext-field-create-items-to-list.png b/docs/images/ext-field-create-items-to-list.png
similarity index 100%
rename from images/ext-field-create-items-to-list.png
rename to docs/images/ext-field-create-items-to-list.png
diff --git a/images/ext-field-create-new-list-order.png b/docs/images/ext-field-create-new-list-order.png
similarity index 100%
rename from images/ext-field-create-new-list-order.png
rename to docs/images/ext-field-create-new-list-order.png
diff --git a/images/ext-field-create-new-list.png b/docs/images/ext-field-create-new-list.png
similarity index 100%
rename from images/ext-field-create-new-list.png
rename to docs/images/ext-field-create-new-list.png
diff --git a/images/ext-field-default-customizer-output.png b/docs/images/ext-field-default-customizer-output.png
similarity index 100%
rename from images/ext-field-default-customizer-output.png
rename to docs/images/ext-field-default-customizer-output.png
diff --git a/images/ext-field-gulp-serve.png b/docs/images/ext-field-gulp-serve.png
similarity index 100%
rename from images/ext-field-gulp-serve.png
rename to docs/images/ext-field-gulp-serve.png
diff --git a/images/ext-field-install-solution-to-site.png b/docs/images/ext-field-install-solution-to-site.png
similarity index 100%
rename from images/ext-field-install-solution-to-site.png
rename to docs/images/ext-field-install-solution-to-site.png
diff --git a/images/ext-field-list-settings.png b/docs/images/ext-field-list-settings.png
similarity index 100%
rename from images/ext-field-list-settings.png
rename to docs/images/ext-field-list-settings.png
diff --git a/images/ext-field-new-number-field-percent.png b/docs/images/ext-field-new-number-field-percent.png
similarity index 100%
rename from images/ext-field-new-number-field-percent.png
rename to docs/images/ext-field-new-number-field-percent.png
diff --git a/images/ext-field-new-number-field.png b/docs/images/ext-field-new-number-field.png
similarity index 100%
rename from images/ext-field-new-number-field.png
rename to docs/images/ext-field-new-number-field.png
diff --git a/images/ext-field-onrender-default-solution.png b/docs/images/ext-field-onrender-default-solution.png
similarity index 100%
rename from images/ext-field-onrender-default-solution.png
rename to docs/images/ext-field-onrender-default-solution.png
diff --git a/images/ext-field-percent-field-graphic.png b/docs/images/ext-field-percent-field-graphic.png
similarity index 100%
rename from images/ext-field-percent-field-graphic.png
rename to docs/images/ext-field-percent-field-graphic.png
diff --git a/images/ext-field-render-field-without-debug.png b/docs/images/ext-field-render-field-without-debug.png
similarity index 100%
rename from images/ext-field-render-field-without-debug.png
rename to docs/images/ext-field-render-field-without-debug.png
diff --git a/images/ext-field-sppkg-deploy-trust.png b/docs/images/ext-field-sppkg-deploy-trust.png
similarity index 100%
rename from images/ext-field-sppkg-deploy-trust.png
rename to docs/images/ext-field-sppkg-deploy-trust.png
diff --git a/images/ext-field-vscode-customizer-base.png b/docs/images/ext-field-vscode-customizer-base.png
similarity index 100%
rename from images/ext-field-vscode-customizer-base.png
rename to docs/images/ext-field-vscode-customizer-base.png
diff --git a/images/ext-field-vscode-manifest.png b/docs/images/ext-field-vscode-manifest.png
similarity index 100%
rename from images/ext-field-vscode-manifest.png
rename to docs/images/ext-field-vscode-manifest.png
diff --git a/images/ext-field-vscode-solution-structure.png b/docs/images/ext-field-vscode-solution-structure.png
similarity index 100%
rename from images/ext-field-vscode-solution-structure.png
rename to docs/images/ext-field-vscode-solution-structure.png
diff --git a/images/ext-field-yeoman-complete.png b/docs/images/ext-field-yeoman-complete.png
similarity index 100%
rename from images/ext-field-yeoman-complete.png
rename to docs/images/ext-field-yeoman-complete.png
diff --git a/images/ext-field-yeoman-prompts.png b/docs/images/ext-field-yeoman-prompts.png
similarity index 100%
rename from images/ext-field-yeoman-prompts.png
rename to docs/images/ext-field-yeoman-prompts.png
diff --git a/images/ext-yeoman-app-complete.png b/docs/images/ext-yeoman-app-complete.png
similarity index 100%
rename from images/ext-yeoman-app-complete.png
rename to docs/images/ext-yeoman-app-complete.png
diff --git a/images/ext-yeoman-app-prompts.png b/docs/images/ext-yeoman-app-prompts.png
similarity index 100%
rename from images/ext-yeoman-app-prompts.png
rename to docs/images/ext-yeoman-app-prompts.png
diff --git a/images/external-scripts-browser-loading-angular-from-cache.png b/docs/images/external-scripts-browser-loading-angular-from-cache.png
similarity index 100%
rename from images/external-scripts-browser-loading-angular-from-cache.png
rename to docs/images/external-scripts-browser-loading-angular-from-cache.png
diff --git a/images/external-scripts-browser-loading-angular-two-web-parts.png b/docs/images/external-scripts-browser-loading-angular-two-web-parts.png
similarity index 100%
rename from images/external-scripts-browser-loading-angular-two-web-parts.png
rename to docs/images/external-scripts-browser-loading-angular-two-web-parts.png
diff --git a/images/external-scripts-browser-loading-angular.png b/docs/images/external-scripts-browser-loading-angular.png
similarity index 100%
rename from images/external-scripts-browser-loading-angular.png
rename to docs/images/external-scripts-browser-loading-angular.png
diff --git a/images/external-scripts-bundle-size.png b/docs/images/external-scripts-bundle-size.png
similarity index 100%
rename from images/external-scripts-bundle-size.png
rename to docs/images/external-scripts-bundle-size.png
diff --git a/images/external-scripts-external-angular-bundle-size.png b/docs/images/external-scripts-external-angular-bundle-size.png
similarity index 100%
rename from images/external-scripts-external-angular-bundle-size.png
rename to docs/images/external-scripts-external-angular-bundle-size.png
diff --git a/images/external-scripts-external-angular-two-bundles-size.png b/docs/images/external-scripts-external-angular-two-bundles-size.png
similarity index 100%
rename from images/external-scripts-external-angular-two-bundles-size.png
rename to docs/images/external-scripts-external-angular-two-bundles-size.png
diff --git a/images/external-scripts-gulp-bundle.png b/docs/images/external-scripts-gulp-bundle.png
similarity index 100%
rename from images/external-scripts-gulp-bundle.png
rename to docs/images/external-scripts-gulp-bundle.png
diff --git a/images/external-scripts-non-amd-deps-error.png b/docs/images/external-scripts-non-amd-deps-error.png
similarity index 100%
rename from images/external-scripts-non-amd-deps-error.png
rename to docs/images/external-scripts-non-amd-deps-error.png
diff --git a/images/external-scripts-non-amd-no-deps-error.png b/docs/images/external-scripts-non-amd-no-deps-error.png
similarity index 100%
rename from images/external-scripts-non-amd-no-deps-error.png
rename to docs/images/external-scripts-non-amd-no-deps-error.png
diff --git a/images/external-scripts-two-bundles-size.png b/docs/images/external-scripts-two-bundles-size.png
similarity index 100%
rename from images/external-scripts-two-bundles-size.png
rename to docs/images/external-scripts-two-bundles-size.png
diff --git a/images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif b/docs/images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif
similarity index 100%
rename from images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif
rename to docs/images/f0a9be9a-434a-4650-ad57-1fb90b016dd1.gif
diff --git a/images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG b/docs/images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG
similarity index 100%
rename from images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG
rename to docs/images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG
diff --git a/images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG b/docs/images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG
similarity index 100%
rename from images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG
rename to docs/images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG
diff --git a/images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG b/docs/images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG
similarity index 100%
rename from images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG
rename to docs/images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG
diff --git a/images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG b/docs/images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG
similarity index 100%
rename from images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG
rename to docs/images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG
diff --git a/images/fabric-components-doc-card-view-ex.png b/docs/images/fabric-components-doc-card-view-ex.png
similarity index 100%
rename from images/fabric-components-doc-card-view-ex.png
rename to docs/images/fabric-components-doc-card-view-ex.png
diff --git a/images/fada902b-fa38-4ac8-8566-3693b736ac35.gif b/docs/images/fada902b-fa38-4ac8-8566-3693b736ac35.gif
similarity index 100%
rename from images/fada902b-fa38-4ac8-8566-3693b736ac35.gif
rename to docs/images/fada902b-fa38-4ac8-8566-3693b736ac35.gif
diff --git a/images/feature-provision-project-items.png b/docs/images/feature-provision-project-items.png
similarity index 100%
rename from images/feature-provision-project-items.png
rename to docs/images/feature-provision-project-items.png
diff --git a/images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png b/docs/images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png
similarity index 100%
rename from images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png
rename to docs/images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png
diff --git a/images/filter1a.gif b/docs/images/filter1a.gif
similarity index 100%
rename from images/filter1a.gif
rename to docs/images/filter1a.gif
diff --git a/images/filter1c.gif b/docs/images/filter1c.gif
similarity index 100%
rename from images/filter1c.gif
rename to docs/images/filter1c.gif
diff --git a/images/footer.gif b/docs/images/footer.gif
similarity index 100%
rename from images/footer.gif
rename to docs/images/footer.gif
diff --git a/images/fullcalendar-sewp-draganddrop.png b/docs/images/fullcalendar-sewp-draganddrop.png
similarity index 100%
rename from images/fullcalendar-sewp-draganddrop.png
rename to docs/images/fullcalendar-sewp-draganddrop.png
diff --git a/images/fullcalendar-sewp.png b/docs/images/fullcalendar-sewp.png
similarity index 100%
rename from images/fullcalendar-sewp.png
rename to docs/images/fullcalendar-sewp.png
diff --git a/images/fullcalendar-spfx-list-configured.png b/docs/images/fullcalendar-spfx-list-configured.png
similarity index 100%
rename from images/fullcalendar-spfx-list-configured.png
rename to docs/images/fullcalendar-spfx-list-configured.png
diff --git a/images/fullcalendar-spfx-listname-property.png b/docs/images/fullcalendar-spfx-listname-property.png
similarity index 100%
rename from images/fullcalendar-spfx-listname-property.png
rename to docs/images/fullcalendar-spfx-listname-property.png
diff --git a/images/fullcalendar-spfx.png b/docs/images/fullcalendar-spfx.png
similarity index 100%
rename from images/fullcalendar-spfx.png
rename to docs/images/fullcalendar-spfx.png
diff --git a/images/fullcalendar-vscode.png b/docs/images/fullcalendar-vscode.png
similarity index 100%
rename from images/fullcalendar-vscode.png
rename to docs/images/fullcalendar-vscode.png
diff --git a/images/fullcalendar-yeoman.png b/docs/images/fullcalendar-yeoman.png
similarity index 100%
rename from images/fullcalendar-yeoman.png
rename to docs/images/fullcalendar-yeoman.png
diff --git a/images/gradient.gif b/docs/images/gradient.gif
similarity index 100%
rename from images/gradient.gif
rename to docs/images/gradient.gif
diff --git a/images/greencheck.gif b/docs/images/greencheck.gif
similarity index 100%
rename from images/greencheck.gif
rename to docs/images/greencheck.gif
diff --git a/images/greychck.gif b/docs/images/greychck.gif
similarity index 100%
rename from images/greychck.gif
rename to docs/images/greychck.gif
diff --git a/images/guidance-governance-spfx-structure-schema.png b/docs/images/guidance-governance-spfx-structure-schema.png
similarity index 100%
rename from images/guidance-governance-spfx-structure-schema.png
rename to docs/images/guidance-governance-spfx-structure-schema.png
diff --git a/images/guidance-productionbuilds-debug-vs-ship-bundle.png b/docs/images/guidance-productionbuilds-debug-vs-ship-bundle.png
similarity index 100%
rename from images/guidance-productionbuilds-debug-vs-ship-bundle.png
rename to docs/images/guidance-productionbuilds-debug-vs-ship-bundle.png
diff --git a/images/guidance-productionbuilds-import-lodash-at.png b/docs/images/guidance-productionbuilds-import-lodash-at.png
similarity index 100%
rename from images/guidance-productionbuilds-import-lodash-at.png
rename to docs/images/guidance-productionbuilds-import-lodash-at.png
diff --git a/images/guidance-productionbuilds-import-lodash.png b/docs/images/guidance-productionbuilds-import-lodash.png
similarity index 100%
rename from images/guidance-productionbuilds-import-lodash.png
rename to docs/images/guidance-productionbuilds-import-lodash.png
diff --git a/images/guidance-productionbuilds-two-bundles-with-libraries.png b/docs/images/guidance-productionbuilds-two-bundles-with-libraries.png
similarity index 100%
rename from images/guidance-productionbuilds-two-bundles-with-libraries.png
rename to docs/images/guidance-productionbuilds-two-bundles-with-libraries.png
diff --git a/images/guidance-productionbuilds-webpack-visualizer-angular.png b/docs/images/guidance-productionbuilds-webpack-visualizer-angular.png
similarity index 100%
rename from images/guidance-productionbuilds-webpack-visualizer-angular.png
rename to docs/images/guidance-productionbuilds-webpack-visualizer-angular.png
diff --git a/images/guidance-sharingdata-cookie-chrome.png b/docs/images/guidance-sharingdata-cookie-chrome.png
similarity index 100%
rename from images/guidance-sharingdata-cookie-chrome.png
rename to docs/images/guidance-sharingdata-cookie-chrome.png
diff --git a/images/guidance-sharingdata-cookie-edge-first-request.png b/docs/images/guidance-sharingdata-cookie-edge-first-request.png
similarity index 100%
rename from images/guidance-sharingdata-cookie-edge-first-request.png
rename to docs/images/guidance-sharingdata-cookie-edge-first-request.png
diff --git a/images/guidance-sharingdata-cookie-edge-subsequent-request.png b/docs/images/guidance-sharingdata-cookie-edge-subsequent-request.png
similarity index 100%
rename from images/guidance-sharingdata-cookie-edge-subsequent-request.png
rename to docs/images/guidance-sharingdata-cookie-edge-subsequent-request.png
diff --git a/images/guidance-sharingdata-loading-data-separately.png b/docs/images/guidance-sharingdata-loading-data-separately.png
similarity index 100%
rename from images/guidance-sharingdata-loading-data-separately.png
rename to docs/images/guidance-sharingdata-loading-data-separately.png
diff --git a/images/guidance-sharingdata-reusing-data-global-variable-loading-message.png b/docs/images/guidance-sharingdata-reusing-data-global-variable-loading-message.png
similarity index 100%
rename from images/guidance-sharingdata-reusing-data-global-variable-loading-message.png
rename to docs/images/guidance-sharingdata-reusing-data-global-variable-loading-message.png
diff --git a/images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png b/docs/images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png
similarity index 100%
rename from images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png
rename to docs/images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png
diff --git a/images/gulp-extend-image-resize-available-tasks.png b/docs/images/gulp-extend-image-resize-available-tasks.png
similarity index 100%
rename from images/gulp-extend-image-resize-available-tasks.png
rename to docs/images/gulp-extend-image-resize-available-tasks.png
diff --git a/images/gulp-extend-image-resize-task.png b/docs/images/gulp-extend-image-resize-task.png
similarity index 100%
rename from images/gulp-extend-image-resize-task.png
rename to docs/images/gulp-extend-image-resize-task.png
diff --git a/images/gulp-image-resize-task-available.png b/docs/images/gulp-image-resize-task-available.png
similarity index 100%
rename from images/gulp-image-resize-task-available.png
rename to docs/images/gulp-image-resize-task-available.png
diff --git a/images/gulp-tasks-available.png b/docs/images/gulp-tasks-available.png
similarity index 100%
rename from images/gulp-tasks-available.png
rename to docs/images/gulp-tasks-available.png
diff --git a/images/gulp-upload-cdn.png b/docs/images/gulp-upload-cdn.png
similarity index 100%
rename from images/gulp-upload-cdn.png
rename to docs/images/gulp-upload-cdn.png
diff --git a/images/header_prev_next.jpg b/docs/images/header_prev_next.jpg
similarity index 100%
rename from images/header_prev_next.jpg
rename to docs/images/header_prev_next.jpg
diff --git a/images/header_sql_tutorial_blank.jpg b/docs/images/header_sql_tutorial_blank.jpg
similarity index 100%
rename from images/header_sql_tutorial_blank.jpg
rename to docs/images/header_sql_tutorial_blank.jpg
diff --git a/images/header_sql_tutorial_logo.GIF b/docs/images/header_sql_tutorial_logo.GIF
similarity index 100%
rename from images/header_sql_tutorial_logo.GIF
rename to docs/images/header_sql_tutorial_logo.GIF
diff --git a/images/hello-vs-webpart-finish-wizard.PNG b/docs/images/hello-vs-webpart-finish-wizard.PNG
similarity index 100%
rename from images/hello-vs-webpart-finish-wizard.PNG
rename to docs/images/hello-vs-webpart-finish-wizard.PNG
diff --git a/images/hello-vs-webpart-new-project-ts-nodejs.PNG b/docs/images/hello-vs-webpart-new-project-ts-nodejs.PNG
similarity index 100%
rename from images/hello-vs-webpart-new-project-ts-nodejs.PNG
rename to docs/images/hello-vs-webpart-new-project-ts-nodejs.PNG
diff --git a/images/hello-vs-webpart-npm-explorer.PNG b/docs/images/hello-vs-webpart-npm-explorer.PNG
similarity index 100%
rename from images/hello-vs-webpart-npm-explorer.PNG
rename to docs/images/hello-vs-webpart-npm-explorer.PNG
diff --git a/images/hello-vs-webpart-soln-explorer.PNG b/docs/images/hello-vs-webpart-soln-explorer.PNG
similarity index 100%
rename from images/hello-vs-webpart-soln-explorer.PNG
rename to docs/images/hello-vs-webpart-soln-explorer.PNG
diff --git a/images/hello-vs-webpart-task-runner.PNG b/docs/images/hello-vs-webpart-task-runner.PNG
similarity index 100%
rename from images/hello-vs-webpart-task-runner.PNG
rename to docs/images/hello-vs-webpart-task-runner.PNG
diff --git a/images/hello-vs-webpart-update-properties.PNG b/docs/images/hello-vs-webpart-update-properties.PNG
similarity index 100%
rename from images/hello-vs-webpart-update-properties.PNG
rename to docs/images/hello-vs-webpart-update-properties.PNG
diff --git a/images/hellow-vs-webpart-step1-wizard.PNG b/docs/images/hellow-vs-webpart-step1-wizard.PNG
similarity index 100%
rename from images/hellow-vs-webpart-step1-wizard.PNG
rename to docs/images/hellow-vs-webpart-step1-wizard.PNG
diff --git a/images/helloworld-wp-gulp-serve.png b/docs/images/helloworld-wp-gulp-serve.png
similarity index 100%
rename from images/helloworld-wp-gulp-serve.png
rename to docs/images/helloworld-wp-gulp-serve.png
diff --git a/images/helloworld-wp-vscode-project-structure.png b/docs/images/helloworld-wp-vscode-project-structure.png
similarity index 100%
rename from images/helloworld-wp-vscode-project-structure.png
rename to docs/images/helloworld-wp-vscode-project-structure.png
diff --git a/images/helloworld-wp-vscode-project.png b/docs/images/helloworld-wp-vscode-project.png
similarity index 100%
rename from images/helloworld-wp-vscode-project.png
rename to docs/images/helloworld-wp-vscode-project.png
diff --git a/images/install-app-your-site.png b/docs/images/install-app-your-site.png
similarity index 100%
rename from images/install-app-your-site.png
rename to docs/images/install-app-your-site.png
diff --git a/images/integrate-webpart-properties-schema.png b/docs/images/integrate-webpart-properties-schema.png
old mode 100755
new mode 100644
similarity index 100%
rename from images/integrate-webpart-properties-schema.png
rename to docs/images/integrate-webpart-properties-schema.png
diff --git a/images/jquery-accordion-wb.png b/docs/images/jquery-accordion-wb.png
similarity index 100%
rename from images/jquery-accordion-wb.png
rename to docs/images/jquery-accordion-wb.png
diff --git a/images/kw.gif b/docs/images/kw.gif
similarity index 100%
rename from images/kw.gif
rename to docs/images/kw.gif
diff --git a/images/kw_adm.gif b/docs/images/kw_adm.gif
similarity index 100%
rename from images/kw_adm.gif
rename to docs/images/kw_adm.gif
diff --git a/images/kw_adm_arch.gif b/docs/images/kw_adm_arch.gif
similarity index 100%
rename from images/kw_adm_arch.gif
rename to docs/images/kw_adm_arch.gif
diff --git a/images/kw_adm_dev.gif b/docs/images/kw_adm_dev.gif
similarity index 100%
rename from images/kw_adm_dev.gif
rename to docs/images/kw_adm_dev.gif
diff --git a/images/kw_adm_dev_arch.gif b/docs/images/kw_adm_dev_arch.gif
similarity index 100%
rename from images/kw_adm_dev_arch.gif
rename to docs/images/kw_adm_dev_arch.gif
diff --git a/images/kw_arch.gif b/docs/images/kw_arch.gif
similarity index 100%
rename from images/kw_arch.gif
rename to docs/images/kw_arch.gif
diff --git a/images/kw_dev.gif b/docs/images/kw_dev.gif
similarity index 100%
rename from images/kw_dev.gif
rename to docs/images/kw_dev.gif
diff --git a/images/kw_dev_arch.gif b/docs/images/kw_dev_arch.gif
similarity index 100%
rename from images/kw_dev_arch.gif
rename to docs/images/kw_dev_arch.gif
diff --git a/images/load.gif b/docs/images/load.gif
similarity index 100%
rename from images/load.gif
rename to docs/images/load.gif
diff --git a/images/load_hover.gif b/docs/images/load_hover.gif
similarity index 100%
rename from images/load_hover.gif
rename to docs/images/load_hover.gif
diff --git a/images/localization-english-greeting-dutch-workbench.png b/docs/images/localization-english-greeting-dutch-workbench.png
similarity index 100%
rename from images/localization-english-greeting-dutch-workbench.png
rename to docs/images/localization-english-greeting-dutch-workbench.png
diff --git a/images/localization-initial-changes.png b/docs/images/localization-initial-changes.png
similarity index 100%
rename from images/localization-initial-changes.png
rename to docs/images/localization-initial-changes.png
diff --git a/images/localization-intellisense.png b/docs/images/localization-intellisense.png
similarity index 100%
rename from images/localization-intellisense.png
rename to docs/images/localization-intellisense.png
diff --git a/images/localization-keys-comparison.png b/docs/images/localization-keys-comparison.png
similarity index 100%
rename from images/localization-keys-comparison.png
rename to docs/images/localization-keys-comparison.png
diff --git a/images/localization-learn-more-nl-nl.png b/docs/images/localization-learn-more-nl-nl.png
similarity index 100%
rename from images/localization-learn-more-nl-nl.png
rename to docs/images/localization-learn-more-nl-nl.png
diff --git a/images/localization-loc-folder.png b/docs/images/localization-loc-folder.png
similarity index 100%
rename from images/localization-loc-folder.png
rename to docs/images/localization-loc-folder.png
diff --git a/images/localization-multilingual-properties.png b/docs/images/localization-multilingual-properties.png
similarity index 100%
rename from images/localization-multilingual-properties.png
rename to docs/images/localization-multilingual-properties.png
diff --git a/images/localization-property-pane-nl-nl.png b/docs/images/localization-property-pane-nl-nl.png
similarity index 100%
rename from images/localization-property-pane-nl-nl.png
rename to docs/images/localization-property-pane-nl-nl.png
diff --git a/images/localization-standard-locale-file.png b/docs/images/localization-standard-locale-file.png
similarity index 100%
rename from images/localization-standard-locale-file.png
rename to docs/images/localization-standard-locale-file.png
diff --git a/images/localization-visual-studio-code.png b/docs/images/localization-visual-studio-code.png
similarity index 100%
rename from images/localization-visual-studio-code.png
rename to docs/images/localization-visual-studio-code.png
diff --git a/images/localization-web-part-body-qps-ploc.png b/docs/images/localization-web-part-body-qps-ploc.png
similarity index 100%
rename from images/localization-web-part-body-qps-ploc.png
rename to docs/images/localization-web-part-body-qps-ploc.png
diff --git a/images/localization-web-part-property-pane-qps-ploc.png b/docs/images/localization-web-part-property-pane-qps-ploc.png
similarity index 100%
rename from images/localization-web-part-property-pane-qps-ploc.png
rename to docs/images/localization-web-part-property-pane-qps-ploc.png
diff --git a/images/localization-yo-sharepoint.png b/docs/images/localization-yo-sharepoint.png
similarity index 100%
rename from images/localization-yo-sharepoint.png
rename to docs/images/localization-yo-sharepoint.png
diff --git a/images/loggingSample.png b/docs/images/loggingSample.png
similarity index 100%
rename from images/loggingSample.png
rename to docs/images/loggingSample.png
diff --git a/images/mod_icon_badge_conoverview.png b/docs/images/mod_icon_badge_conoverview.png
similarity index 100%
rename from images/mod_icon_badge_conoverview.png
rename to docs/images/mod_icon_badge_conoverview.png
diff --git a/images/mod_icon_badge_reference.png b/docs/images/mod_icon_badge_reference.png
similarity index 100%
rename from images/mod_icon_badge_reference.png
rename to docs/images/mod_icon_badge_reference.png
diff --git a/images/mod_icon_dobox.gif b/docs/images/mod_icon_dobox.gif
similarity index 100%
rename from images/mod_icon_dobox.gif
rename to docs/images/mod_icon_dobox.gif
diff --git a/images/mod_icon_getstartbox.gif b/docs/images/mod_icon_getstartbox.gif
similarity index 100%
rename from images/mod_icon_getstartbox.gif
rename to docs/images/mod_icon_getstartbox.gif
diff --git a/images/mod_icon_howto.png b/docs/images/mod_icon_howto.png
similarity index 100%
rename from images/mod_icon_howto.png
rename to docs/images/mod_icon_howto.png
diff --git a/images/mod_icon_incloud.gif b/docs/images/mod_icon_incloud.gif
similarity index 100%
rename from images/mod_icon_incloud.gif
rename to docs/images/mod_icon_incloud.gif
diff --git a/images/mod_icon_links_samples.png b/docs/images/mod_icon_links_samples.png
similarity index 100%
rename from images/mod_icon_links_samples.png
rename to docs/images/mod_icon_links_samples.png
diff --git a/images/mod_icon_onpremises.gif b/docs/images/mod_icon_onpremises.gif
similarity index 100%
rename from images/mod_icon_onpremises.gif
rename to docs/images/mod_icon_onpremises.gif
diff --git a/images/mod_icon_startbox.gif b/docs/images/mod_icon_startbox.gif
similarity index 100%
rename from images/mod_icon_startbox.gif
rename to docs/images/mod_icon_startbox.gif
diff --git a/images/mod_icon_video.png b/docs/images/mod_icon_video.png
similarity index 100%
rename from images/mod_icon_video.png
rename to docs/images/mod_icon_video.png
diff --git a/images/mod_logo_sharepoint.png b/docs/images/mod_logo_sharepoint.png
similarity index 100%
rename from images/mod_logo_sharepoint.png
rename to docs/images/mod_logo_sharepoint.png
diff --git a/images/ng-intro-angular-config.png b/docs/images/ng-intro-angular-config.png
similarity index 100%
rename from images/ng-intro-angular-config.png
rename to docs/images/ng-intro-angular-config.png
diff --git a/images/ng-intro-app-folder.png b/docs/images/ng-intro-app-folder.png
similarity index 100%
rename from images/ng-intro-app-folder.png
rename to docs/images/ng-intro-app-folder.png
diff --git a/images/ng-intro-app-module.png b/docs/images/ng-intro-app-module.png
similarity index 100%
rename from images/ng-intro-app-module.png
rename to docs/images/ng-intro-app-module.png
diff --git a/images/ng-intro-dataservice.png b/docs/images/ng-intro-dataservice.png
similarity index 100%
rename from images/ng-intro-dataservice.png
rename to docs/images/ng-intro-dataservice.png
diff --git a/images/ng-intro-hide-finished-tasks.png b/docs/images/ng-intro-hide-finished-tasks.png
similarity index 100%
rename from images/ng-intro-hide-finished-tasks.png
rename to docs/images/ng-intro-hide-finished-tasks.png
diff --git a/images/ng-intro-homecontroller-event.png b/docs/images/ng-intro-homecontroller-event.png
similarity index 100%
rename from images/ng-intro-homecontroller-event.png
rename to docs/images/ng-intro-homecontroller-event.png
diff --git a/images/ng-intro-homecontroller.png b/docs/images/ng-intro-homecontroller.png
similarity index 100%
rename from images/ng-intro-homecontroller.png
rename to docs/images/ng-intro-homecontroller.png
diff --git a/images/ng-intro-injector-class-variable.png b/docs/images/ng-intro-injector-class-variable.png
similarity index 100%
rename from images/ng-intro-injector-class-variable.png
rename to docs/images/ng-intro-injector-class-variable.png
diff --git a/images/ng-intro-manifest-property.png b/docs/images/ng-intro-manifest-property.png
similarity index 100%
rename from images/ng-intro-manifest-property.png
rename to docs/images/ng-intro-manifest-property.png
diff --git a/images/ng-intro-project-visual-studio-code.png b/docs/images/ng-intro-project-visual-studio-code.png
similarity index 100%
rename from images/ng-intro-project-visual-studio-code.png
rename to docs/images/ng-intro-project-visual-studio-code.png
diff --git a/images/ng-intro-property-interface.png b/docs/images/ng-intro-property-interface.png
similarity index 100%
rename from images/ng-intro-property-interface.png
rename to docs/images/ng-intro-property-interface.png
diff --git a/images/ng-intro-property-pane-toggle-browser.png b/docs/images/ng-intro-property-pane-toggle-browser.png
similarity index 100%
rename from images/ng-intro-property-pane-toggle-browser.png
rename to docs/images/ng-intro-property-pane-toggle-browser.png
diff --git a/images/ng-intro-property-pane-toggle.png b/docs/images/ng-intro-property-pane-toggle.png
similarity index 100%
rename from images/ng-intro-property-pane-toggle.png
rename to docs/images/ng-intro-property-pane-toggle.png
diff --git a/images/ng-intro-strings-interface.png b/docs/images/ng-intro-strings-interface.png
similarity index 100%
rename from images/ng-intro-strings-interface.png
rename to docs/images/ng-intro-strings-interface.png
diff --git a/images/ng-intro-strings.png b/docs/images/ng-intro-strings.png
similarity index 100%
rename from images/ng-intro-strings.png
rename to docs/images/ng-intro-strings.png
diff --git a/images/ng-intro-web-part-css.png b/docs/images/ng-intro-web-part-css.png
similarity index 100%
rename from images/ng-intro-web-part-css.png
rename to docs/images/ng-intro-web-part-css.png
diff --git a/images/ng-intro-web-part-import-angular.png b/docs/images/ng-intro-web-part-import-angular.png
similarity index 100%
rename from images/ng-intro-web-part-import-angular.png
rename to docs/images/ng-intro-web-part-import-angular.png
diff --git a/images/ng-intro-web-part-render-angular.png b/docs/images/ng-intro-web-part-render-angular.png
similarity index 100%
rename from images/ng-intro-web-part-render-angular.png
rename to docs/images/ng-intro-web-part-render-angular.png
diff --git a/images/ng-intro-workbench-office-ui-fabric.png b/docs/images/ng-intro-workbench-office-ui-fabric.png
similarity index 100%
rename from images/ng-intro-workbench-office-ui-fabric.png
rename to docs/images/ng-intro-workbench-office-ui-fabric.png
diff --git a/images/ng-intro-yeoman-generator.png b/docs/images/ng-intro-yeoman-generator.png
similarity index 100%
rename from images/ng-intro-yeoman-generator.png
rename to docs/images/ng-intro-yeoman-generator.png
diff --git a/images/ng-migration-angular-ngofficeuifabric-config.png b/docs/images/ng-migration-angular-ngofficeuifabric-config.png
similarity index 100%
rename from images/ng-migration-angular-ngofficeuifabric-config.png
rename to docs/images/ng-migration-angular-ngofficeuifabric-config.png
diff --git a/images/ng-migration-angular-ngofficeuifabric-import.png b/docs/images/ng-migration-angular-ngofficeuifabric-import.png
similarity index 100%
rename from images/ng-migration-angular-ngofficeuifabric-import.png
rename to docs/images/ng-migration-angular-ngofficeuifabric-import.png
diff --git a/images/ng-migration-angular-web-part-properties.png b/docs/images/ng-migration-angular-web-part-properties.png
similarity index 100%
rename from images/ng-migration-angular-web-part-properties.png
rename to docs/images/ng-migration-angular-web-part-properties.png
diff --git a/images/ng-migration-app-config-web-url.png b/docs/images/ng-migration-app-config-web-url.png
similarity index 100%
rename from images/ng-migration-app-config-web-url.png
rename to docs/images/ng-migration-app-config-web-url.png
diff --git a/images/ng-migration-app-files-visual-studio-code.png b/docs/images/ng-migration-app-files-visual-studio-code.png
similarity index 100%
rename from images/ng-migration-app-files-visual-studio-code.png
rename to docs/images/ng-migration-app-files-visual-studio-code.png
diff --git a/images/ng-migration-app-folder-visual-studio-code.png b/docs/images/ng-migration-app-folder-visual-studio-code.png
similarity index 100%
rename from images/ng-migration-app-folder-visual-studio-code.png
rename to docs/images/ng-migration-app-folder-visual-studio-code.png
diff --git a/images/ng-migration-correct-styling.png b/docs/images/ng-migration-correct-styling.png
similarity index 100%
rename from images/ng-migration-correct-styling.png
rename to docs/images/ng-migration-correct-styling.png
diff --git a/images/ng-migration-finished-tasks-hidden.png b/docs/images/ng-migration-finished-tasks-hidden.png
similarity index 100%
rename from images/ng-migration-finished-tasks-hidden.png
rename to docs/images/ng-migration-finished-tasks-hidden.png
diff --git a/images/ng-migration-first-run.png b/docs/images/ng-migration-first-run.png
similarity index 100%
rename from images/ng-migration-first-run.png
rename to docs/images/ng-migration-first-run.png
diff --git a/images/ng-migration-import-propertypanetoggle.png b/docs/images/ng-migration-import-propertypanetoggle.png
similarity index 100%
rename from images/ng-migration-import-propertypanetoggle.png
rename to docs/images/ng-migration-import-propertypanetoggle.png
diff --git a/images/ng-migration-injector-property.png b/docs/images/ng-migration-injector-property.png
similarity index 100%
rename from images/ng-migration-injector-property.png
rename to docs/images/ng-migration-injector-property.png
diff --git a/images/ng-migration-old-office-ui-fabric.png b/docs/images/ng-migration-old-office-ui-fabric.png
similarity index 100%
rename from images/ng-migration-old-office-ui-fabric.png
rename to docs/images/ng-migration-old-office-ui-fabric.png
diff --git a/images/ng-migration-original-angular-application.png b/docs/images/ng-migration-original-angular-application.png
similarity index 100%
rename from images/ng-migration-original-angular-application.png
rename to docs/images/ng-migration-original-angular-application.png
diff --git a/images/ng-migration-project-visual-studio-code.png b/docs/images/ng-migration-project-visual-studio-code.png
similarity index 100%
rename from images/ng-migration-project-visual-studio-code.png
rename to docs/images/ng-migration-project-visual-studio-code.png
diff --git a/images/ng-migration-todo-list.png b/docs/images/ng-migration-todo-list.png
similarity index 100%
rename from images/ng-migration-todo-list.png
rename to docs/images/ng-migration-todo-list.png
diff --git a/images/ng-migration-workbench-aspx-doclib.png b/docs/images/ng-migration-workbench-aspx-doclib.png
similarity index 100%
rename from images/ng-migration-workbench-aspx-doclib.png
rename to docs/images/ng-migration-workbench-aspx-doclib.png
diff --git a/images/ng-migration-workbench-weburl.png b/docs/images/ng-migration-workbench-weburl.png
similarity index 100%
rename from images/ng-migration-workbench-weburl.png
rename to docs/images/ng-migration-workbench-weburl.png
diff --git a/images/ng-migration-yeoman-generator.png b/docs/images/ng-migration-yeoman-generator.png
similarity index 100%
rename from images/ng-migration-yeoman-generator.png
rename to docs/images/ng-migration-yeoman-generator.png
diff --git a/images/ngDebuggingSP2013Workflows.png b/docs/images/ngDebuggingSP2013Workflows.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows.png
rename to docs/images/ngDebuggingSP2013Workflows.png
diff --git a/images/ngDebuggingSP2013Workflows01.png b/docs/images/ngDebuggingSP2013Workflows01.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows01.png
rename to docs/images/ngDebuggingSP2013Workflows01.png
diff --git a/images/ngDebuggingSP2013Workflows02.png b/docs/images/ngDebuggingSP2013Workflows02.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows02.png
rename to docs/images/ngDebuggingSP2013Workflows02.png
diff --git a/images/ngDebuggingSP2013Workflows04.png b/docs/images/ngDebuggingSP2013Workflows04.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows04.png
rename to docs/images/ngDebuggingSP2013Workflows04.png
diff --git a/images/ngDebuggingSP2013Workflows05.png b/docs/images/ngDebuggingSP2013Workflows05.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows05.png
rename to docs/images/ngDebuggingSP2013Workflows05.png
diff --git a/images/ngDebuggingSP2013Workflows06.png b/docs/images/ngDebuggingSP2013Workflows06.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows06.png
rename to docs/images/ngDebuggingSP2013Workflows06.png
diff --git a/images/ngDebuggingSP2013Workflows07.png b/docs/images/ngDebuggingSP2013Workflows07.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows07.png
rename to docs/images/ngDebuggingSP2013Workflows07.png
diff --git a/images/ngDebuggingSP2013Workflows08.png b/docs/images/ngDebuggingSP2013Workflows08.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows08.png
rename to docs/images/ngDebuggingSP2013Workflows08.png
diff --git a/images/ngDebuggingSP2013Workflows10.png b/docs/images/ngDebuggingSP2013Workflows10.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows10.png
rename to docs/images/ngDebuggingSP2013Workflows10.png
diff --git a/images/ngDebuggingSP2013Workflows11.png b/docs/images/ngDebuggingSP2013Workflows11.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows11.png
rename to docs/images/ngDebuggingSP2013Workflows11.png
diff --git a/images/ngDebuggingSP2013Workflows12.png b/docs/images/ngDebuggingSP2013Workflows12.png
similarity index 100%
rename from images/ngDebuggingSP2013Workflows12.png
rename to docs/images/ngDebuggingSP2013Workflows12.png
diff --git a/images/ngFormsFig10.png b/docs/images/ngFormsFig10.png
similarity index 100%
rename from images/ngFormsFig10.png
rename to docs/images/ngFormsFig10.png
diff --git a/images/ngFormsFig5.png b/docs/images/ngFormsFig5.png
similarity index 100%
rename from images/ngFormsFig5.png
rename to docs/images/ngFormsFig5.png
diff --git a/images/ngFormsFig6.png b/docs/images/ngFormsFig6.png
similarity index 100%
rename from images/ngFormsFig6.png
rename to docs/images/ngFormsFig6.png
diff --git a/images/ngFormsFig7.png b/docs/images/ngFormsFig7.png
similarity index 100%
rename from images/ngFormsFig7.png
rename to docs/images/ngFormsFig7.png
diff --git a/images/ngFormsFig8.png b/docs/images/ngFormsFig8.png
similarity index 100%
rename from images/ngFormsFig8.png
rename to docs/images/ngFormsFig8.png
diff --git a/images/ngFormsFig9.png b/docs/images/ngFormsFig9.png
similarity index 100%
rename from images/ngFormsFig9.png
rename to docs/images/ngFormsFig9.png
diff --git a/images/ngGK_Fig02.png b/docs/images/ngGK_Fig02.png
similarity index 100%
rename from images/ngGK_Fig02.png
rename to docs/images/ngGK_Fig02.png
diff --git a/images/ngGK_Fig03.png b/docs/images/ngGK_Fig03.png
similarity index 100%
rename from images/ngGK_Fig03.png
rename to docs/images/ngGK_Fig03.png
diff --git a/images/ngGK_Fig04.png b/docs/images/ngGK_Fig04.png
similarity index 100%
rename from images/ngGK_Fig04.png
rename to docs/images/ngGK_Fig04.png
diff --git a/images/ngGK_Fig05.png b/docs/images/ngGK_Fig05.png
similarity index 100%
rename from images/ngGK_Fig05.png
rename to docs/images/ngGK_Fig05.png
diff --git a/images/ngGK_Fig06.png b/docs/images/ngGK_Fig06.png
similarity index 100%
rename from images/ngGK_Fig06.png
rename to docs/images/ngGK_Fig06.png
diff --git a/images/ngGK_Fig07.png b/docs/images/ngGK_Fig07.png
similarity index 100%
rename from images/ngGK_Fig07.png
rename to docs/images/ngGK_Fig07.png
diff --git a/images/ngGK_Fig08.png b/docs/images/ngGK_Fig08.png
similarity index 100%
rename from images/ngGK_Fig08.png
rename to docs/images/ngGK_Fig08.png
diff --git a/images/ngGK_Fig09.png b/docs/images/ngGK_Fig09.png
similarity index 100%
rename from images/ngGK_Fig09.png
rename to docs/images/ngGK_Fig09.png
diff --git a/images/ngGK_Fig10.png b/docs/images/ngGK_Fig10.png
similarity index 100%
rename from images/ngGK_Fig10.png
rename to docs/images/ngGK_Fig10.png
diff --git a/images/ngGK_Fig11.png b/docs/images/ngGK_Fig11.png
similarity index 100%
rename from images/ngGK_Fig11.png
rename to docs/images/ngGK_Fig11.png
diff --git a/images/ngGK_Fig12.png b/docs/images/ngGK_Fig12.png
similarity index 100%
rename from images/ngGK_Fig12.png
rename to docs/images/ngGK_Fig12.png
diff --git a/images/ngGK_Fig13.png b/docs/images/ngGK_Fig13.png
similarity index 100%
rename from images/ngGK_Fig13.png
rename to docs/images/ngGK_Fig13.png
diff --git a/images/ngGK_Fig14.png b/docs/images/ngGK_Fig14.png
similarity index 100%
rename from images/ngGK_Fig14.png
rename to docs/images/ngGK_Fig14.png
diff --git a/images/ngGK_Fig15.png b/docs/images/ngGK_Fig15.png
similarity index 100%
rename from images/ngGK_Fig15.png
rename to docs/images/ngGK_Fig15.png
diff --git a/images/ngGK_Fig16.png b/docs/images/ngGK_Fig16.png
similarity index 100%
rename from images/ngGK_Fig16.png
rename to docs/images/ngGK_Fig16.png
diff --git a/images/ngGK_Fig17.png b/docs/images/ngGK_Fig17.png
similarity index 100%
rename from images/ngGK_Fig17.png
rename to docs/images/ngGK_Fig17.png
diff --git a/images/ngGK_Fig18.png b/docs/images/ngGK_Fig18.png
similarity index 100%
rename from images/ngGK_Fig18.png
rename to docs/images/ngGK_Fig18.png
diff --git a/images/ngGK_Fig19.png b/docs/images/ngGK_Fig19.png
similarity index 100%
rename from images/ngGK_Fig19.png
rename to docs/images/ngGK_Fig19.png
diff --git a/images/ngGK_Fig20.png b/docs/images/ngGK_Fig20.png
similarity index 100%
rename from images/ngGK_Fig20.png
rename to docs/images/ngGK_Fig20.png
diff --git a/images/ngGK_Fig21.png b/docs/images/ngGK_Fig21.png
similarity index 100%
rename from images/ngGK_Fig21.png
rename to docs/images/ngGK_Fig21.png
diff --git a/images/ngGK_Fig22.png b/docs/images/ngGK_Fig22.png
similarity index 100%
rename from images/ngGK_Fig22.png
rename to docs/images/ngGK_Fig22.png
diff --git a/images/ngGK_Flowchart.png b/docs/images/ngGK_Flowchart.png
similarity index 100%
rename from images/ngGK_Flowchart.png
rename to docs/images/ngGK_Flowchart.png
diff --git a/images/ngSP2013WorkflowCSOM01.png b/docs/images/ngSP2013WorkflowCSOM01.png
similarity index 100%
rename from images/ngSP2013WorkflowCSOM01.png
rename to docs/images/ngSP2013WorkflowCSOM01.png
diff --git a/images/ngSP2013WorkflowCSOM02.png b/docs/images/ngSP2013WorkflowCSOM02.png
similarity index 100%
rename from images/ngSP2013WorkflowCSOM02.png
rename to docs/images/ngSP2013WorkflowCSOM02.png
diff --git a/images/ngWSSP2013WorkflowSPD2013.png b/docs/images/ngWSSP2013WorkflowSPD2013.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD2013.png
rename to docs/images/ngWSSP2013WorkflowSPD2013.png
diff --git a/images/ngWSSP2013WorkflowSPD201302.png b/docs/images/ngWSSP2013WorkflowSPD201302.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201302.png
rename to docs/images/ngWSSP2013WorkflowSPD201302.png
diff --git a/images/ngWSSP2013WorkflowSPD201303.png b/docs/images/ngWSSP2013WorkflowSPD201303.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201303.png
rename to docs/images/ngWSSP2013WorkflowSPD201303.png
diff --git a/images/ngWSSP2013WorkflowSPD201304.png b/docs/images/ngWSSP2013WorkflowSPD201304.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201304.png
rename to docs/images/ngWSSP2013WorkflowSPD201304.png
diff --git a/images/ngWSSP2013WorkflowSPD201305.png b/docs/images/ngWSSP2013WorkflowSPD201305.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201305.png
rename to docs/images/ngWSSP2013WorkflowSPD201305.png
diff --git a/images/ngWSSP2013WorkflowSPD201306.png b/docs/images/ngWSSP2013WorkflowSPD201306.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201306.png
rename to docs/images/ngWSSP2013WorkflowSPD201306.png
diff --git a/images/ngWSSP2013WorkflowSPD201307.png b/docs/images/ngWSSP2013WorkflowSPD201307.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201307.png
rename to docs/images/ngWSSP2013WorkflowSPD201307.png
diff --git a/images/ngWSSP2013WorkflowSPD201308.png b/docs/images/ngWSSP2013WorkflowSPD201308.png
similarity index 100%
rename from images/ngWSSP2013WorkflowSPD201308.png
rename to docs/images/ngWSSP2013WorkflowSPD201308.png
diff --git a/images/ngWSSP2013WorkflowVS201201.png b/docs/images/ngWSSP2013WorkflowVS201201.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201201.png
rename to docs/images/ngWSSP2013WorkflowVS201201.png
diff --git a/images/ngWSSP2013WorkflowVS201202.png b/docs/images/ngWSSP2013WorkflowVS201202.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201202.png
rename to docs/images/ngWSSP2013WorkflowVS201202.png
diff --git a/images/ngWSSP2013WorkflowVS201203.png b/docs/images/ngWSSP2013WorkflowVS201203.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201203.png
rename to docs/images/ngWSSP2013WorkflowVS201203.png
diff --git a/images/ngWSSP2013WorkflowVS201204.png b/docs/images/ngWSSP2013WorkflowVS201204.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201204.png
rename to docs/images/ngWSSP2013WorkflowVS201204.png
diff --git a/images/ngWSSP2013WorkflowVS201205.png b/docs/images/ngWSSP2013WorkflowVS201205.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201205.png
rename to docs/images/ngWSSP2013WorkflowVS201205.png
diff --git a/images/ngWSSP2013WorkflowVS201206.png b/docs/images/ngWSSP2013WorkflowVS201206.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201206.png
rename to docs/images/ngWSSP2013WorkflowVS201206.png
diff --git a/images/ngWSSP2013WorkflowVS201207.png b/docs/images/ngWSSP2013WorkflowVS201207.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201207.png
rename to docs/images/ngWSSP2013WorkflowVS201207.png
diff --git a/images/ngWSSP2013WorkflowVS201208.png b/docs/images/ngWSSP2013WorkflowVS201208.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201208.png
rename to docs/images/ngWSSP2013WorkflowVS201208.png
diff --git a/images/ngWSSP2013WorkflowVS201209.png b/docs/images/ngWSSP2013WorkflowVS201209.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201209.png
rename to docs/images/ngWSSP2013WorkflowVS201209.png
diff --git a/images/ngWSSP2013WorkflowVS201210.png b/docs/images/ngWSSP2013WorkflowVS201210.png
similarity index 100%
rename from images/ngWSSP2013WorkflowVS201210.png
rename to docs/images/ngWSSP2013WorkflowVS201210.png
diff --git a/images/ngWfFig01.png b/docs/images/ngWfFig01.png
similarity index 100%
rename from images/ngWfFig01.png
rename to docs/images/ngWfFig01.png
diff --git a/images/ngWfFig02.png b/docs/images/ngWfFig02.png
similarity index 100%
rename from images/ngWfFig02.png
rename to docs/images/ngWfFig02.png
diff --git a/images/ngWfFig03.png b/docs/images/ngWfFig03.png
similarity index 100%
rename from images/ngWfFig03.png
rename to docs/images/ngWfFig03.png
diff --git a/images/ngWfFig04.png b/docs/images/ngWfFig04.png
similarity index 100%
rename from images/ngWfFig04.png
rename to docs/images/ngWfFig04.png
diff --git a/images/ngWfFig05.png b/docs/images/ngWfFig05.png
similarity index 100%
rename from images/ngWfFig05.png
rename to docs/images/ngWfFig05.png
diff --git a/images/ngWfFig06.png b/docs/images/ngWfFig06.png
similarity index 100%
rename from images/ngWfFig06.png
rename to docs/images/ngWfFig06.png
diff --git a/images/ngWfFig07.png b/docs/images/ngWfFig07.png
similarity index 100%
rename from images/ngWfFig07.png
rename to docs/images/ngWfFig07.png
diff --git a/images/ngWfFig08.png b/docs/images/ngWfFig08.png
similarity index 100%
rename from images/ngWfFig08.png
rename to docs/images/ngWfFig08.png
diff --git a/images/ngWfFig09.png b/docs/images/ngWfFig09.png
similarity index 100%
rename from images/ngWfFig09.png
rename to docs/images/ngWfFig09.png
diff --git a/images/ngWfFig10.png b/docs/images/ngWfFig10.png
similarity index 100%
rename from images/ngWfFig10.png
rename to docs/images/ngWfFig10.png
diff --git a/images/ngWfFig11.png b/docs/images/ngWfFig11.png
similarity index 100%
rename from images/ngWfFig11.png
rename to docs/images/ngWfFig11.png
diff --git a/images/ng_MsmqFeature.png b/docs/images/ng_MsmqFeature.png
similarity index 100%
rename from images/ng_MsmqFeature.png
rename to docs/images/ng_MsmqFeature.png
diff --git a/images/ng_MsmqQueues.png b/docs/images/ng_MsmqQueues.png
similarity index 100%
rename from images/ng_MsmqQueues.png
rename to docs/images/ng_MsmqQueues.png
diff --git a/images/note.gif b/docs/images/note.gif
similarity index 100%
rename from images/note.gif
rename to docs/images/note.gif
diff --git a/images/npm-outdated-global-packages-list.png b/docs/images/npm-outdated-global-packages-list.png
similarity index 100%
rename from images/npm-outdated-global-packages-list.png
rename to docs/images/npm-outdated-global-packages-list.png
diff --git a/images/npm-outdated-packages-list.png b/docs/images/npm-outdated-packages-list.png
similarity index 100%
rename from images/npm-outdated-packages-list.png
rename to docs/images/npm-outdated-packages-list.png
diff --git a/images/npm-update-packagejson-versions.png b/docs/images/npm-update-packagejson-versions.png
similarity index 100%
rename from images/npm-update-packagejson-versions.png
rename to docs/images/npm-update-packagejson-versions.png
diff --git a/images/odc_Office15_Access15OverviewDK2_Figure07.jpg b/docs/images/odc_Office15_Access15OverviewDK2_Figure07.jpg
similarity index 100%
rename from images/odc_Office15_Access15OverviewDK2_Figure07.jpg
rename to docs/images/odc_Office15_Access15OverviewDK2_Figure07.jpg
diff --git a/images/pencil.GIF b/docs/images/pencil.GIF
similarity index 100%
rename from images/pencil.GIF
rename to docs/images/pencil.GIF
diff --git a/images/postman-add-webhook-body.png b/docs/images/postman-add-webhook-body.png
similarity index 100%
rename from images/postman-add-webhook-body.png
rename to docs/images/postman-add-webhook-body.png
diff --git a/images/postman-get-new-access-token.png b/docs/images/postman-get-new-access-token.png
similarity index 100%
rename from images/postman-get-new-access-token.png
rename to docs/images/postman-get-new-access-token.png
diff --git a/images/preconfiguredentries-multiple-web-parts-toolbox.png b/docs/images/preconfiguredentries-multiple-web-parts-toolbox.png
similarity index 100%
rename from images/preconfiguredentries-multiple-web-parts-toolbox.png
rename to docs/images/preconfiguredentries-multiple-web-parts-toolbox.png
diff --git a/images/preconfiguredentries-needs-configuration.png b/docs/images/preconfiguredentries-needs-configuration.png
similarity index 100%
rename from images/preconfiguredentries-needs-configuration.png
rename to docs/images/preconfiguredentries-needs-configuration.png
diff --git a/images/preconfiguredentries-recent-documents-canvas.png b/docs/images/preconfiguredentries-recent-documents-canvas.png
similarity index 100%
rename from images/preconfiguredentries-recent-documents-canvas.png
rename to docs/images/preconfiguredentries-recent-documents-canvas.png
diff --git a/images/preconfiguredentries-recent-images-canvas.png b/docs/images/preconfiguredentries-recent-images-canvas.png
similarity index 100%
rename from images/preconfiguredentries-recent-images-canvas.png
rename to docs/images/preconfiguredentries-recent-images-canvas.png
diff --git a/images/preconfiguredentries-recent-images-toolbox.png b/docs/images/preconfiguredentries-recent-images-toolbox.png
similarity index 100%
rename from images/preconfiguredentries-recent-images-toolbox.png
rename to docs/images/preconfiguredentries-recent-images-toolbox.png
diff --git a/images/preconfiguredentries-three-configurations-toolbox.png b/docs/images/preconfiguredentries-three-configurations-toolbox.png
similarity index 100%
rename from images/preconfiguredentries-three-configurations-toolbox.png
rename to docs/images/preconfiguredentries-three-configurations-toolbox.png
diff --git a/images/preconfiguredentries-visual-studio-code.png b/docs/images/preconfiguredentries-visual-studio-code.png
similarity index 100%
rename from images/preconfiguredentries-visual-studio-code.png
rename to docs/images/preconfiguredentries-visual-studio-code.png
diff --git a/images/preconfiguredentries-yeoman.png b/docs/images/preconfiguredentries-yeoman.png
similarity index 100%
rename from images/preconfiguredentries-yeoman.png
rename to docs/images/preconfiguredentries-yeoman.png
diff --git a/images/privclass.gif b/docs/images/privclass.gif
similarity index 100%
rename from images/privclass.gif
rename to docs/images/privclass.gif
diff --git a/images/privdelegate.gif b/docs/images/privdelegate.gif
similarity index 100%
rename from images/privdelegate.gif
rename to docs/images/privdelegate.gif
diff --git a/images/privdelicate.gif b/docs/images/privdelicate.gif
similarity index 100%
rename from images/privdelicate.gif
rename to docs/images/privdelicate.gif
diff --git a/images/privenum.gif b/docs/images/privenum.gif
similarity index 100%
rename from images/privenum.gif
rename to docs/images/privenum.gif
diff --git a/images/privenumeration.gif b/docs/images/privenumeration.gif
similarity index 100%
rename from images/privenumeration.gif
rename to docs/images/privenumeration.gif
diff --git a/images/privevent.gif b/docs/images/privevent.gif
similarity index 100%
rename from images/privevent.gif
rename to docs/images/privevent.gif
diff --git a/images/privextension.gif b/docs/images/privextension.gif
similarity index 100%
rename from images/privextension.gif
rename to docs/images/privextension.gif
diff --git a/images/privfield.gif b/docs/images/privfield.gif
similarity index 100%
rename from images/privfield.gif
rename to docs/images/privfield.gif
diff --git a/images/privinterface.gif b/docs/images/privinterface.gif
similarity index 100%
rename from images/privinterface.gif
rename to docs/images/privinterface.gif
diff --git a/images/privmethod.gif b/docs/images/privmethod.gif
similarity index 100%
rename from images/privmethod.gif
rename to docs/images/privmethod.gif
diff --git a/images/privproperty.gif b/docs/images/privproperty.gif
similarity index 100%
rename from images/privproperty.gif
rename to docs/images/privproperty.gif
diff --git a/images/privstructure.gif b/docs/images/privstructure.gif
similarity index 100%
rename from images/privstructure.gif
rename to docs/images/privstructure.gif
diff --git a/images/property-pane-example.png b/docs/images/property-pane-example.png
similarity index 100%
rename from images/property-pane-example.png
rename to docs/images/property-pane-example.png
diff --git a/images/property-validation-description-error-apply-disabled.png b/docs/images/property-validation-description-error-apply-disabled.png
similarity index 100%
rename from images/property-validation-description-error-apply-disabled.png
rename to docs/images/property-validation-description-error-apply-disabled.png
diff --git a/images/property-validation-description-too-long-error.png b/docs/images/property-validation-description-too-long-error.png
similarity index 100%
rename from images/property-validation-description-too-long-error.png
rename to docs/images/property-validation-description-too-long-error.png
diff --git a/images/property-validation-empty-description-error.png b/docs/images/property-validation-empty-description-error.png
similarity index 100%
rename from images/property-validation-empty-description-error.png
rename to docs/images/property-validation-empty-description-error.png
diff --git a/images/property-validation-empty-list-name-error.png b/docs/images/property-validation-empty-list-name-error.png
similarity index 100%
rename from images/property-validation-empty-list-name-error.png
rename to docs/images/property-validation-empty-list-name-error.png
diff --git a/images/property-validation-invalid-list-name-error.png b/docs/images/property-validation-invalid-list-name-error.png
similarity index 100%
rename from images/property-validation-invalid-list-name-error.png
rename to docs/images/property-validation-invalid-list-name-error.png
diff --git a/images/property-validation-list-name-property.png b/docs/images/property-validation-list-name-property.png
similarity index 100%
rename from images/property-validation-list-name-property.png
rename to docs/images/property-validation-list-name-property.png
diff --git a/images/property-validation-partial-list-name-validation.png b/docs/images/property-validation-partial-list-name-validation.png
similarity index 100%
rename from images/property-validation-partial-list-name-validation.png
rename to docs/images/property-validation-partial-list-name-validation.png
diff --git a/images/property-validation-valid-list-name.png b/docs/images/property-validation-valid-list-name.png
similarity index 100%
rename from images/property-validation-valid-list-name.png
rename to docs/images/property-validation-valid-list-name.png
diff --git a/images/property-validation-visual-studio-code.png b/docs/images/property-validation-visual-studio-code.png
similarity index 100%
rename from images/property-validation-visual-studio-code.png
rename to docs/images/property-validation-visual-studio-code.png
diff --git a/images/property-validation-yeoman-generator.png b/docs/images/property-validation-yeoman-generator.png
similarity index 100%
rename from images/property-validation-yeoman-generator.png
rename to docs/images/property-validation-yeoman-generator.png
diff --git a/images/protclass.gif b/docs/images/protclass.gif
similarity index 100%
rename from images/protclass.gif
rename to docs/images/protclass.gif
diff --git a/images/protdelegate.gif b/docs/images/protdelegate.gif
similarity index 100%
rename from images/protdelegate.gif
rename to docs/images/protdelegate.gif
diff --git a/images/protdeligate.gif b/docs/images/protdeligate.gif
similarity index 100%
rename from images/protdeligate.gif
rename to docs/images/protdeligate.gif
diff --git a/images/protenum.gif b/docs/images/protenum.gif
similarity index 100%
rename from images/protenum.gif
rename to docs/images/protenum.gif
diff --git a/images/protenumeration.gif b/docs/images/protenumeration.gif
similarity index 100%
rename from images/protenumeration.gif
rename to docs/images/protenumeration.gif
diff --git a/images/protevent.gif b/docs/images/protevent.gif
similarity index 100%
rename from images/protevent.gif
rename to docs/images/protevent.gif
diff --git a/images/protextension.gif b/docs/images/protextension.gif
similarity index 100%
rename from images/protextension.gif
rename to docs/images/protextension.gif
diff --git a/images/protfield.gif b/docs/images/protfield.gif
similarity index 100%
rename from images/protfield.gif
rename to docs/images/protfield.gif
diff --git a/images/protinterface.gif b/docs/images/protinterface.gif
similarity index 100%
rename from images/protinterface.gif
rename to docs/images/protinterface.gif
diff --git a/images/protmethod.gif b/docs/images/protmethod.gif
similarity index 100%
rename from images/protmethod.gif
rename to docs/images/protmethod.gif
diff --git a/images/protoperator.gif b/docs/images/protoperator.gif
similarity index 100%
rename from images/protoperator.gif
rename to docs/images/protoperator.gif
diff --git a/images/protproperty.gif b/docs/images/protproperty.gif
similarity index 100%
rename from images/protproperty.gif
rename to docs/images/protproperty.gif
diff --git a/images/protstructure.gif b/docs/images/protstructure.gif
similarity index 100%
rename from images/protstructure.gif
rename to docs/images/protstructure.gif
diff --git a/images/pubclass.gif b/docs/images/pubclass.gif
similarity index 100%
rename from images/pubclass.gif
rename to docs/images/pubclass.gif
diff --git a/images/pubdelegate.gif b/docs/images/pubdelegate.gif
similarity index 100%
rename from images/pubdelegate.gif
rename to docs/images/pubdelegate.gif
diff --git a/images/pubenum.gif b/docs/images/pubenum.gif
similarity index 100%
rename from images/pubenum.gif
rename to docs/images/pubenum.gif
diff --git a/images/pubenumeration.gif b/docs/images/pubenumeration.gif
similarity index 100%
rename from images/pubenumeration.gif
rename to docs/images/pubenumeration.gif
diff --git a/images/pubevent.gif b/docs/images/pubevent.gif
similarity index 100%
rename from images/pubevent.gif
rename to docs/images/pubevent.gif
diff --git a/images/pubextension.gif b/docs/images/pubextension.gif
similarity index 100%
rename from images/pubextension.gif
rename to docs/images/pubextension.gif
diff --git a/images/pubfield.gif b/docs/images/pubfield.gif
similarity index 100%
rename from images/pubfield.gif
rename to docs/images/pubfield.gif
diff --git a/images/pubinterface.gif b/docs/images/pubinterface.gif
similarity index 100%
rename from images/pubinterface.gif
rename to docs/images/pubinterface.gif
diff --git a/images/pubmethod.gif b/docs/images/pubmethod.gif
similarity index 100%
rename from images/pubmethod.gif
rename to docs/images/pubmethod.gif
diff --git a/images/puboperator.gif b/docs/images/puboperator.gif
similarity index 100%
rename from images/puboperator.gif
rename to docs/images/puboperator.gif
diff --git a/images/pubproperty.gif b/docs/images/pubproperty.gif
similarity index 100%
rename from images/pubproperty.gif
rename to docs/images/pubproperty.gif
diff --git a/images/pubstructure.gif b/docs/images/pubstructure.gif
similarity index 100%
rename from images/pubstructure.gif
rename to docs/images/pubstructure.gif
diff --git a/images/react-cascading-dropdowns-item-dropdown-list-items.png b/docs/images/react-cascading-dropdowns-item-dropdown-list-items.png
similarity index 100%
rename from images/react-cascading-dropdowns-item-dropdown-list-items.png
rename to docs/images/react-cascading-dropdowns-item-dropdown-list-items.png
diff --git a/images/react-cascading-dropdowns-itemname-property-pane-dropdown.png b/docs/images/react-cascading-dropdowns-itemname-property-pane-dropdown.png
similarity index 100%
rename from images/react-cascading-dropdowns-itemname-property-pane-dropdown.png
rename to docs/images/react-cascading-dropdowns-itemname-property-pane-dropdown.png
diff --git a/images/react-cascading-dropdowns-itemname-property-web-part-manifest.png b/docs/images/react-cascading-dropdowns-itemname-property-web-part-manifest.png
similarity index 100%
rename from images/react-cascading-dropdowns-itemname-property-web-part-manifest.png
rename to docs/images/react-cascading-dropdowns-itemname-property-web-part-manifest.png
diff --git a/images/react-cascading-dropdowns-list-dropdown-available-lists.png b/docs/images/react-cascading-dropdowns-list-dropdown-available-lists.png
similarity index 100%
rename from images/react-cascading-dropdowns-list-dropdown-available-lists.png
rename to docs/images/react-cascading-dropdowns-list-dropdown-available-lists.png
diff --git a/images/react-cascading-dropdowns-list-selected-item-disabled.png b/docs/images/react-cascading-dropdowns-list-selected-item-disabled.png
similarity index 100%
rename from images/react-cascading-dropdowns-list-selected-item-disabled.png
rename to docs/images/react-cascading-dropdowns-list-selected-item-disabled.png
diff --git a/images/react-cascading-dropdowns-listname-property-pane-dropdown.png b/docs/images/react-cascading-dropdowns-listname-property-pane-dropdown.png
similarity index 100%
rename from images/react-cascading-dropdowns-listname-property-pane-dropdown.png
rename to docs/images/react-cascading-dropdowns-listname-property-pane-dropdown.png
diff --git a/images/react-cascading-dropdowns-listname-property-web-part-manifest.png b/docs/images/react-cascading-dropdowns-listname-property-web-part-manifest.png
similarity index 100%
rename from images/react-cascading-dropdowns-listname-property-web-part-manifest.png
rename to docs/images/react-cascading-dropdowns-listname-property-web-part-manifest.png
diff --git a/images/react-cascading-dropdowns-loading-indicator-when-loading-items.png b/docs/images/react-cascading-dropdowns-loading-indicator-when-loading-items.png
similarity index 100%
rename from images/react-cascading-dropdowns-loading-indicator-when-loading-items.png
rename to docs/images/react-cascading-dropdowns-loading-indicator-when-loading-items.png
diff --git a/images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png b/docs/images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png
similarity index 100%
rename from images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png
rename to docs/images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png
diff --git a/images/react-cascading-dropdowns-visual-studio-code.png b/docs/images/react-cascading-dropdowns-visual-studio-code.png
similarity index 100%
rename from images/react-cascading-dropdowns-visual-studio-code.png
rename to docs/images/react-cascading-dropdowns-visual-studio-code.png
diff --git a/images/react-cascading-dropdowns-web-part-first-run.png b/docs/images/react-cascading-dropdowns-web-part-first-run.png
similarity index 100%
rename from images/react-cascading-dropdowns-web-part-first-run.png
rename to docs/images/react-cascading-dropdowns-web-part-first-run.png
diff --git a/images/react-cascading-dropdowns-yo-sharepoint.png b/docs/images/react-cascading-dropdowns-yo-sharepoint.png
similarity index 100%
rename from images/react-cascading-dropdowns-yo-sharepoint.png
rename to docs/images/react-cascading-dropdowns-yo-sharepoint.png
diff --git a/images/requirements1a.gif b/docs/images/requirements1a.gif
similarity index 100%
rename from images/requirements1a.gif
rename to docs/images/requirements1a.gif
diff --git a/images/requirements1c.gif b/docs/images/requirements1c.gif
similarity index 100%
rename from images/requirements1c.gif
rename to docs/images/requirements1c.gif
diff --git a/images/save.gif b/docs/images/save.gif
similarity index 100%
rename from images/save.gif
rename to docs/images/save.gif
diff --git a/images/save_hover.gif b/docs/images/save_hover.gif
similarity index 100%
rename from images/save_hover.gif
rename to docs/images/save_hover.gif
diff --git a/images/security.gif b/docs/images/security.gif
similarity index 100%
rename from images/security.gif
rename to docs/images/security.gif
diff --git a/images/seealso1a.gif b/docs/images/seealso1a.gif
similarity index 100%
rename from images/seealso1a.gif
rename to docs/images/seealso1a.gif
diff --git a/images/seealso1c.gif b/docs/images/seealso1c.gif
similarity index 100%
rename from images/seealso1c.gif
rename to docs/images/seealso1c.gif
diff --git a/images/sp-app-deploy-trust.png b/docs/images/sp-app-deploy-trust.png
similarity index 100%
rename from images/sp-app-deploy-trust.png
rename to docs/images/sp-app-deploy-trust.png
diff --git a/images/sp-app-replace-pkg.png b/docs/images/sp-app-replace-pkg.png
similarity index 100%
rename from images/sp-app-replace-pkg.png
rename to docs/images/sp-app-replace-pkg.png
diff --git a/images/sp-helloworld-wp-modern-page.png b/docs/images/sp-helloworld-wp-modern-page.png
similarity index 100%
rename from images/sp-helloworld-wp-modern-page.png
rename to docs/images/sp-helloworld-wp-modern-page.png
diff --git a/images/sp-lists-render-localhost.png b/docs/images/sp-lists-render-localhost.png
similarity index 100%
rename from images/sp-lists-render-localhost.png
rename to docs/images/sp-lists-render-localhost.png
diff --git a/images/sp-lists-render-spsite.png b/docs/images/sp-lists-render-spsite.png
similarity index 100%
rename from images/sp-lists-render-spsite.png
rename to docs/images/sp-lists-render-spsite.png
diff --git a/images/sp-lists-spsiteurl-wp.png b/docs/images/sp-lists-spsiteurl-wp.png
similarity index 100%
rename from images/sp-lists-spsiteurl-wp.png
rename to docs/images/sp-lists-spsiteurl-wp.png
diff --git a/images/sp-mock-localhost-wp.png b/docs/images/sp-mock-localhost-wp.png
similarity index 100%
rename from images/sp-mock-localhost-wp.png
rename to docs/images/sp-mock-localhost-wp.png
diff --git a/images/sp-modern-page-toolbox.png b/docs/images/sp-modern-page-toolbox.png
similarity index 100%
rename from images/sp-modern-page-toolbox.png
rename to docs/images/sp-modern-page-toolbox.png
diff --git a/images/sp-modern-site-page.png b/docs/images/sp-modern-site-page.png
similarity index 100%
rename from images/sp-modern-site-page.png
rename to docs/images/sp-modern-site-page.png
diff --git a/images/sp-pnp-js-guide-completed-setup.png b/docs/images/sp-pnp-js-guide-completed-setup.png
similarity index 100%
rename from images/sp-pnp-js-guide-completed-setup.png
rename to docs/images/sp-pnp-js-guide-completed-setup.png
diff --git a/images/sp-pnp-js-guide-first-open.png b/docs/images/sp-pnp-js-guide-first-open.png
similarity index 100%
rename from images/sp-pnp-js-guide-first-open.png
rename to docs/images/sp-pnp-js-guide-first-open.png
diff --git a/images/sp-pnp-js-guide-first-run.png b/docs/images/sp-pnp-js-guide-first-run.png
similarity index 100%
rename from images/sp-pnp-js-guide-first-run.png
rename to docs/images/sp-pnp-js-guide-first-run.png
diff --git a/images/sp-pnp-js-guide-with-mock-data.png b/docs/images/sp-pnp-js-guide-with-mock-data.png
similarity index 100%
rename from images/sp-pnp-js-guide-with-mock-data.png
rename to docs/images/sp-pnp-js-guide-with-mock-data.png
diff --git a/images/sp-sample-todo-wp.png b/docs/images/sp-sample-todo-wp.png
similarity index 100%
rename from images/sp-sample-todo-wp.png
rename to docs/images/sp-sample-todo-wp.png
diff --git a/images/sp-workbench-helloworld-pp.png b/docs/images/sp-workbench-helloworld-pp.png
similarity index 100%
rename from images/sp-workbench-helloworld-pp.png
rename to docs/images/sp-workbench-helloworld-pp.png
diff --git a/images/sp-workbench-helloworld-wp.png b/docs/images/sp-workbench-helloworld-wp.png
similarity index 100%
rename from images/sp-workbench-helloworld-wp.png
rename to docs/images/sp-workbench-helloworld-wp.png
diff --git a/images/sp-workbench-o365-helloworld-wp.png b/docs/images/sp-workbench-o365-helloworld-wp.png
similarity index 100%
rename from images/sp-workbench-o365-helloworld-wp.png
rename to docs/images/sp-workbench-o365-helloworld-wp.png
diff --git a/images/sp-workbench-o365-toolbox.png b/docs/images/sp-workbench-o365-toolbox.png
similarity index 100%
rename from images/sp-workbench-o365-toolbox.png
rename to docs/images/sp-workbench-o365-toolbox.png
diff --git a/images/sp-workbench-o365-unsface-scripts.png b/docs/images/sp-workbench-o365-unsface-scripts.png
similarity index 100%
rename from images/sp-workbench-o365-unsface-scripts.png
rename to docs/images/sp-workbench-o365-unsface-scripts.png
diff --git a/images/sp-workbench-o365.png b/docs/images/sp-workbench-o365.png
similarity index 100%
rename from images/sp-workbench-o365.png
rename to docs/images/sp-workbench-o365.png
diff --git a/images/sp-workbench-toolbox.png b/docs/images/sp-workbench-toolbox.png
similarity index 100%
rename from images/sp-workbench-toolbox.png
rename to docs/images/sp-workbench-toolbox.png
diff --git a/images/sp-workbench.png b/docs/images/sp-workbench.png
similarity index 100%
rename from images/sp-workbench.png
rename to docs/images/sp-workbench.png
diff --git a/images/sp-wp-classic-page-pp.png b/docs/images/sp-wp-classic-page-pp.png
similarity index 100%
rename from images/sp-wp-classic-page-pp.png
rename to docs/images/sp-wp-classic-page-pp.png
diff --git a/images/sp-wp-classic-page.png b/docs/images/sp-wp-classic-page.png
similarity index 100%
rename from images/sp-wp-classic-page.png
rename to docs/images/sp-wp-classic-page.png
diff --git a/images/sp-wp-modern-page-pp.png b/docs/images/sp-wp-modern-page-pp.png
similarity index 100%
rename from images/sp-wp-modern-page-pp.png
rename to docs/images/sp-wp-modern-page-pp.png
diff --git a/images/sp-wp-modern-page.png b/docs/images/sp-wp-modern-page.png
similarity index 100%
rename from images/sp-wp-modern-page.png
rename to docs/images/sp-wp-modern-page.png
diff --git a/images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png b/docs/images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png
similarity index 100%
rename from images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png
rename to docs/images/sp15Con_CreateDisplayTemplateSP2013_Figure02.png
diff --git a/images/sp15Con_DesignPackageExp_Figure1.png b/docs/images/sp15Con_DesignPackageExp_Figure1.png
similarity index 100%
rename from images/sp15Con_DesignPackageExp_Figure1.png
rename to docs/images/sp15Con_DesignPackageExp_Figure1.png
diff --git a/images/sp15Con_DeviceChannels_Fig1.png b/docs/images/sp15Con_DeviceChannels_Fig1.png
similarity index 100%
rename from images/sp15Con_DeviceChannels_Fig1.png
rename to docs/images/sp15Con_DeviceChannels_Fig1.png
diff --git a/images/sp15Con_SiteMasterPage_Figure2.png b/docs/images/sp15Con_SiteMasterPage_Figure2.png
similarity index 100%
rename from images/sp15Con_SiteMasterPage_Figure2.png
rename to docs/images/sp15Con_SiteMasterPage_Figure2.png
diff --git a/images/sp15_BM25_formula.gif b/docs/images/sp15_BM25_formula.gif
similarity index 100%
rename from images/sp15_BM25_formula.gif
rename to docs/images/sp15_BM25_formula.gif
diff --git a/images/sp15_freshness_formula.gif b/docs/images/sp15_freshness_formula.gif
similarity index 100%
rename from images/sp15_freshness_formula.gif
rename to docs/images/sp15_freshness_formula.gif
diff --git a/images/sp15_linear_model_formula.gif b/docs/images/sp15_linear_model_formula.gif
similarity index 100%
rename from images/sp15_linear_model_formula.gif
rename to docs/images/sp15_linear_model_formula.gif
diff --git a/images/sp15_neural_network_formula.gif b/docs/images/sp15_neural_network_formula.gif
similarity index 100%
rename from images/sp15_neural_network_formula.gif
rename to docs/images/sp15_neural_network_formula.gif
diff --git a/images/sp15_transform_table_ranking_model.gif b/docs/images/sp15_transform_table_ranking_model.gif
similarity index 100%
rename from images/sp15_transform_table_ranking_model.gif
rename to docs/images/sp15_transform_table_ranking_model.gif
diff --git a/images/sp15neuralnetworkinrankingmodels.gif b/docs/images/sp15neuralnetworkinrankingmodels.gif
similarity index 100%
rename from images/sp15neuralnetworkinrankingmodels.gif
rename to docs/images/sp15neuralnetworkinrankingmodels.gif
diff --git a/images/spd15-.JPG b/docs/images/spd15-.JPG
similarity index 100%
rename from images/spd15-.JPG
rename to docs/images/spd15-.JPG
diff --git a/images/spd15-AddListItemPerms-txt.JPG b/docs/images/spd15-AddListItemPerms-txt.JPG
similarity index 100%
rename from images/spd15-AddListItemPerms-txt.JPG
rename to docs/images/spd15-AddListItemPerms-txt.JPG
diff --git a/images/spd15-AddListItemPerms-visio.JPG b/docs/images/spd15-AddListItemPerms-visio.JPG
similarity index 100%
rename from images/spd15-AddListItemPerms-visio.JPG
rename to docs/images/spd15-AddListItemPerms-visio.JPG
diff --git a/images/spd15-AssignForm2Grp-txt.JPG b/docs/images/spd15-AssignForm2Grp-txt.JPG
similarity index 100%
rename from images/spd15-AssignForm2Grp-txt.JPG
rename to docs/images/spd15-AssignForm2Grp-txt.JPG
diff --git a/images/spd15-AssignForm2Grp-visio.JPG b/docs/images/spd15-AssignForm2Grp-visio.JPG
similarity index 100%
rename from images/spd15-AssignForm2Grp-visio.JPG
rename to docs/images/spd15-AssignForm2Grp-visio.JPG
diff --git a/images/spd15-AssignToDoItem-txt.JPG b/docs/images/spd15-AssignToDoItem-txt.JPG
similarity index 100%
rename from images/spd15-AssignToDoItem-txt.JPG
rename to docs/images/spd15-AssignToDoItem-txt.JPG
diff --git a/images/spd15-AssignToDoItem-visio.JPG b/docs/images/spd15-AssignToDoItem-visio.JPG
similarity index 100%
rename from images/spd15-AssignToDoItem-visio.JPG
rename to docs/images/spd15-AssignToDoItem-visio.JPG
diff --git a/images/spd15-CheckInItem-txt.JPG b/docs/images/spd15-CheckInItem-txt.JPG
similarity index 100%
rename from images/spd15-CheckInItem-txt.JPG
rename to docs/images/spd15-CheckInItem-txt.JPG
diff --git a/images/spd15-CheckInItem-visio.JPG b/docs/images/spd15-CheckInItem-visio.JPG
similarity index 100%
rename from images/spd15-CheckInItem-visio.JPG
rename to docs/images/spd15-CheckInItem-visio.JPG
diff --git a/images/spd15-CheckOutItem-txt.JPG b/docs/images/spd15-CheckOutItem-txt.JPG
similarity index 100%
rename from images/spd15-CheckOutItem-txt.JPG
rename to docs/images/spd15-CheckOutItem-txt.JPG
diff --git a/images/spd15-CheckOutItem-visio.JPG b/docs/images/spd15-CheckOutItem-visio.JPG
similarity index 100%
rename from images/spd15-CheckOutItem-visio.JPG
rename to docs/images/spd15-CheckOutItem-visio.JPG
diff --git a/images/spd15-ChkExactUserPerms-txt.JPG b/docs/images/spd15-ChkExactUserPerms-txt.JPG
similarity index 100%
rename from images/spd15-ChkExactUserPerms-txt.JPG
rename to docs/images/spd15-ChkExactUserPerms-txt.JPG
diff --git a/images/spd15-ChkExactUserPerms-visio.JPG b/docs/images/spd15-ChkExactUserPerms-visio.JPG
similarity index 100%
rename from images/spd15-ChkExactUserPerms-visio.JPG
rename to docs/images/spd15-ChkExactUserPerms-visio.JPG
diff --git a/images/spd15-ChkUserPerms-txt.JPG b/docs/images/spd15-ChkUserPerms-txt.JPG
similarity index 100%
rename from images/spd15-ChkUserPerms-txt.JPG
rename to docs/images/spd15-ChkUserPerms-txt.JPG
diff --git a/images/spd15-ChkUserPerms-visio.JPG b/docs/images/spd15-ChkUserPerms-visio.JPG
similarity index 100%
rename from images/spd15-ChkUserPerms-visio.JPG
rename to docs/images/spd15-ChkUserPerms-visio.JPG
diff --git a/images/spd15-CollectDataFrUser-txt.JPG b/docs/images/spd15-CollectDataFrUser-txt.JPG
similarity index 100%
rename from images/spd15-CollectDataFrUser-txt.JPG
rename to docs/images/spd15-CollectDataFrUser-txt.JPG
diff --git a/images/spd15-CollectDataFrUser-visio.JPG b/docs/images/spd15-CollectDataFrUser-visio.JPG
similarity index 100%
rename from images/spd15-CollectDataFrUser-visio.JPG
rename to docs/images/spd15-CollectDataFrUser-visio.JPG
diff --git a/images/spd15-CompareDataSrc-txt.JPG b/docs/images/spd15-CompareDataSrc-txt.JPG
similarity index 100%
rename from images/spd15-CompareDataSrc-txt.JPG
rename to docs/images/spd15-CompareDataSrc-txt.JPG
diff --git a/images/spd15-CompareDataSrc-visio.JPG b/docs/images/spd15-CompareDataSrc-visio.JPG
similarity index 100%
rename from images/spd15-CompareDataSrc-visio.JPG
rename to docs/images/spd15-CompareDataSrc-visio.JPG
diff --git a/images/spd15-CompareDocField-txt.JPG b/docs/images/spd15-CompareDocField-txt.JPG
similarity index 100%
rename from images/spd15-CompareDocField-txt.JPG
rename to docs/images/spd15-CompareDocField-txt.JPG
diff --git a/images/spd15-CompareDocField-visio.JPG b/docs/images/spd15-CompareDocField-visio.JPG
similarity index 100%
rename from images/spd15-CompareDocField-visio.JPG
rename to docs/images/spd15-CompareDocField-visio.JPG
diff --git a/images/spd15-CopyListItem-txt.JPG b/docs/images/spd15-CopyListItem-txt.JPG
similarity index 100%
rename from images/spd15-CopyListItem-txt.JPG
rename to docs/images/spd15-CopyListItem-txt.JPG
diff --git a/images/spd15-CopyListItem-visio.JPG b/docs/images/spd15-CopyListItem-visio.JPG
similarity index 100%
rename from images/spd15-CopyListItem-visio.JPG
rename to docs/images/spd15-CopyListItem-visio.JPG
diff --git a/images/spd15-CreateListItem-txt.JPG b/docs/images/spd15-CreateListItem-txt.JPG
similarity index 100%
rename from images/spd15-CreateListItem-txt.JPG
rename to docs/images/spd15-CreateListItem-txt.JPG
diff --git a/images/spd15-CreateListItem-visio.JPG b/docs/images/spd15-CreateListItem-visio.JPG
similarity index 100%
rename from images/spd15-CreateListItem-visio.JPG
rename to docs/images/spd15-CreateListItem-visio.JPG
diff --git a/images/spd15-CreatedBySpecPerson-txt.JPG b/docs/images/spd15-CreatedBySpecPerson-txt.JPG
similarity index 100%
rename from images/spd15-CreatedBySpecPerson-txt.JPG
rename to docs/images/spd15-CreatedBySpecPerson-txt.JPG
diff --git a/images/spd15-CreatedBySpecPerson-visio.JPG b/docs/images/spd15-CreatedBySpecPerson-visio.JPG
similarity index 100%
rename from images/spd15-CreatedBySpecPerson-visio.JPG
rename to docs/images/spd15-CreatedBySpecPerson-visio.JPG
diff --git a/images/spd15-CreatedInSpecDateSpan-txt.JPG b/docs/images/spd15-CreatedInSpecDateSpan-txt.JPG
similarity index 100%
rename from images/spd15-CreatedInSpecDateSpan-txt.JPG
rename to docs/images/spd15-CreatedInSpecDateSpan-txt.JPG
diff --git a/images/spd15-CreatedInSpecDateSpan-visio.JPG b/docs/images/spd15-CreatedInSpecDateSpan-visio.JPG
similarity index 100%
rename from images/spd15-CreatedInSpecDateSpan-visio.JPG
rename to docs/images/spd15-CreatedInSpecDateSpan-visio.JPG
diff --git a/images/spd15-DeleteItem-txt.JPG b/docs/images/spd15-DeleteItem-txt.JPG
similarity index 100%
rename from images/spd15-DeleteItem-txt.JPG
rename to docs/images/spd15-DeleteItem-txt.JPG
diff --git a/images/spd15-DeleteItem-visio.JPG b/docs/images/spd15-DeleteItem-visio.JPG
similarity index 100%
rename from images/spd15-DeleteItem-visio.JPG
rename to docs/images/spd15-DeleteItem-visio.JPG
diff --git a/images/spd15-DiscardItem-txt.JPG b/docs/images/spd15-DiscardItem-txt.JPG
similarity index 100%
rename from images/spd15-DiscardItem-txt.JPG
rename to docs/images/spd15-DiscardItem-txt.JPG
diff --git a/images/spd15-DiscardItem-visio.JPG b/docs/images/spd15-DiscardItem-visio.JPG
similarity index 100%
rename from images/spd15-DiscardItem-visio.JPG
rename to docs/images/spd15-DiscardItem-visio.JPG
diff --git a/images/spd15-FileIsSpecType-txt.JPG b/docs/images/spd15-FileIsSpecType-txt.JPG
similarity index 100%
rename from images/spd15-FileIsSpecType-txt.JPG
rename to docs/images/spd15-FileIsSpecType-txt.JPG
diff --git a/images/spd15-FileIsSpecType-visio.JPG b/docs/images/spd15-FileIsSpecType-visio.JPG
similarity index 100%
rename from images/spd15-FileIsSpecType-visio.JPG
rename to docs/images/spd15-FileIsSpecType-visio.JPG
diff --git a/images/spd15-FileSzInSpecRange-txt.JPG b/docs/images/spd15-FileSzInSpecRange-txt.JPG
similarity index 100%
rename from images/spd15-FileSzInSpecRange-txt.JPG
rename to docs/images/spd15-FileSzInSpecRange-txt.JPG
diff --git a/images/spd15-FileSzInSpecRange-visio.JPG b/docs/images/spd15-FileSzInSpecRange-visio.JPG
similarity index 100%
rename from images/spd15-FileSzInSpecRange-visio.JPG
rename to docs/images/spd15-FileSzInSpecRange-visio.JPG
diff --git a/images/spd15-ImportFromVisio.JPG b/docs/images/spd15-ImportFromVisio.JPG
similarity index 100%
rename from images/spd15-ImportFromVisio.JPG
rename to docs/images/spd15-ImportFromVisio.JPG
diff --git a/images/spd15-InheritListItemPerms-txt.JPG b/docs/images/spd15-InheritListItemPerms-txt.JPG
similarity index 100%
rename from images/spd15-InheritListItemPerms-txt.JPG
rename to docs/images/spd15-InheritListItemPerms-txt.JPG
diff --git a/images/spd15-InheritListItemPerms-visio.JPG b/docs/images/spd15-InheritListItemPerms-visio.JPG
similarity index 100%
rename from images/spd15-InheritListItemPerms-visio.JPG
rename to docs/images/spd15-InheritListItemPerms-visio.JPG
diff --git a/images/spd15-LogHist-txt.JPG b/docs/images/spd15-LogHist-txt.JPG
similarity index 100%
rename from images/spd15-LogHist-txt.JPG
rename to docs/images/spd15-LogHist-txt.JPG
diff --git a/images/spd15-LogHist-visio.JPG b/docs/images/spd15-LogHist-visio.JPG
similarity index 100%
rename from images/spd15-LogHist-visio.JPG
rename to docs/images/spd15-LogHist-visio.JPG
diff --git a/images/spd15-LookupMgr4User-txt.JPG b/docs/images/spd15-LookupMgr4User-txt.JPG
similarity index 100%
rename from images/spd15-LookupMgr4User-txt.JPG
rename to docs/images/spd15-LookupMgr4User-txt.JPG
diff --git a/images/spd15-LookupMgr4User-visio.JPG b/docs/images/spd15-LookupMgr4User-visio.JPG
similarity index 100%
rename from images/spd15-LookupMgr4User-visio.JPG
rename to docs/images/spd15-LookupMgr4User-visio.JPG
diff --git a/images/spd15-ModifiedBySpecPerson-txt.JPG b/docs/images/spd15-ModifiedBySpecPerson-txt.JPG
similarity index 100%
rename from images/spd15-ModifiedBySpecPerson-txt.JPG
rename to docs/images/spd15-ModifiedBySpecPerson-txt.JPG
diff --git a/images/spd15-ModifiedBySpecPerson-visio.JPG b/docs/images/spd15-ModifiedBySpecPerson-visio.JPG
similarity index 100%
rename from images/spd15-ModifiedBySpecPerson-visio.JPG
rename to docs/images/spd15-ModifiedBySpecPerson-visio.JPG
diff --git a/images/spd15-ModifiedInSpecDateSpan-txt.JPG b/docs/images/spd15-ModifiedInSpecDateSpan-txt.JPG
similarity index 100%
rename from images/spd15-ModifiedInSpecDateSpan-txt.JPG
rename to docs/images/spd15-ModifiedInSpecDateSpan-txt.JPG
diff --git a/images/spd15-ModifiedInSpecDateSpan-visio.JPG b/docs/images/spd15-ModifiedInSpecDateSpan-visio.JPG
similarity index 100%
rename from images/spd15-ModifiedInSpecDateSpan-visio.JPG
rename to docs/images/spd15-ModifiedInSpecDateSpan-visio.JPG
diff --git a/images/spd15-PauseDate-txt.JPG b/docs/images/spd15-PauseDate-txt.JPG
similarity index 100%
rename from images/spd15-PauseDate-txt.JPG
rename to docs/images/spd15-PauseDate-txt.JPG
diff --git a/images/spd15-PauseDate-visio.JPG b/docs/images/spd15-PauseDate-visio.JPG
similarity index 100%
rename from images/spd15-PauseDate-visio.JPG
rename to docs/images/spd15-PauseDate-visio.JPG
diff --git a/images/spd15-PauseDuration-txt.JPG b/docs/images/spd15-PauseDuration-txt.JPG
similarity index 100%
rename from images/spd15-PauseDuration-txt.JPG
rename to docs/images/spd15-PauseDuration-txt.JPG
diff --git a/images/spd15-PauseDuration-visio.JPG b/docs/images/spd15-PauseDuration-visio.JPG
similarity index 100%
rename from images/spd15-PauseDuration-visio.JPG
rename to docs/images/spd15-PauseDuration-visio.JPG
diff --git a/images/spd15-ReplaceListItemPerms-txt.JPG b/docs/images/spd15-ReplaceListItemPerms-txt.JPG
similarity index 100%
rename from images/spd15-ReplaceListItemPerms-txt.JPG
rename to docs/images/spd15-ReplaceListItemPerms-txt.JPG
diff --git a/images/spd15-ReplaceListItemPerms-visio.JPG b/docs/images/spd15-ReplaceListItemPerms-visio.JPG
similarity index 100%
rename from images/spd15-ReplaceListItemPerms-visio.JPG
rename to docs/images/spd15-ReplaceListItemPerms-visio.JPG
diff --git a/images/spd15-RmListItemPerms-txt.JPG b/docs/images/spd15-RmListItemPerms-txt.JPG
similarity index 100%
rename from images/spd15-RmListItemPerms-txt.JPG
rename to docs/images/spd15-RmListItemPerms-txt.JPG
diff --git a/images/spd15-RmListItemPerms-visio.JPG b/docs/images/spd15-RmListItemPerms-visio.JPG
similarity index 100%
rename from images/spd15-RmListItemPerms-visio.JPG
rename to docs/images/spd15-RmListItemPerms-visio.JPG
diff --git a/images/spd15-SendApproval4DocSet-txt.JPG b/docs/images/spd15-SendApproval4DocSet-txt.JPG
similarity index 100%
rename from images/spd15-SendApproval4DocSet-txt.JPG
rename to docs/images/spd15-SendApproval4DocSet-txt.JPG
diff --git a/images/spd15-SendApproval4DocSet-visio.JPG b/docs/images/spd15-SendApproval4DocSet-visio.JPG
similarity index 100%
rename from images/spd15-SendApproval4DocSet-visio.JPG
rename to docs/images/spd15-SendApproval4DocSet-visio.JPG
diff --git a/images/spd15-SendDoc2Repos-txt.JPG b/docs/images/spd15-SendDoc2Repos-txt.JPG
similarity index 100%
rename from images/spd15-SendDoc2Repos-txt.JPG
rename to docs/images/spd15-SendDoc2Repos-txt.JPG
diff --git a/images/spd15-SendDoc2Repos-visio.JPG b/docs/images/spd15-SendDoc2Repos-visio.JPG
similarity index 100%
rename from images/spd15-SendDoc2Repos-visio.JPG
rename to docs/images/spd15-SendDoc2Repos-visio.JPG
diff --git a/images/spd15-SendDocSet2Repos-txt.JPG b/docs/images/spd15-SendDocSet2Repos-txt.JPG
similarity index 100%
rename from images/spd15-SendDocSet2Repos-txt.JPG
rename to docs/images/spd15-SendDocSet2Repos-txt.JPG
diff --git a/images/spd15-SendDocSet2Repos-visio.JPG b/docs/images/spd15-SendDocSet2Repos-visio.JPG
similarity index 100%
rename from images/spd15-SendDocSet2Repos-visio.JPG
rename to docs/images/spd15-SendDocSet2Repos-visio.JPG
diff --git a/images/spd15-SetContentApprStatus-visio.JPG b/docs/images/spd15-SetContentApprStatus-visio.JPG
similarity index 100%
rename from images/spd15-SetContentApprStatus-visio.JPG
rename to docs/images/spd15-SetContentApprStatus-visio.JPG
diff --git a/images/spd15-SetContentApprStatus4DocSet-txt.JPG b/docs/images/spd15-SetContentApprStatus4DocSet-txt.JPG
similarity index 100%
rename from images/spd15-SetContentApprStatus4DocSet-txt.JPG
rename to docs/images/spd15-SetContentApprStatus4DocSet-txt.JPG
diff --git a/images/spd15-SetContentApprovalStatus-txt.JPG b/docs/images/spd15-SetContentApprovalStatus-txt.JPG
similarity index 100%
rename from images/spd15-SetContentApprovalStatus-txt.JPG
rename to docs/images/spd15-SetContentApprovalStatus-txt.JPG
diff --git a/images/spd15-SetContentApprovalStatus-visio.JPG b/docs/images/spd15-SetContentApprovalStatus-visio.JPG
similarity index 100%
rename from images/spd15-SetContentApprovalStatus-visio.JPG
rename to docs/images/spd15-SetContentApprovalStatus-visio.JPG
diff --git a/images/spd15-SetFieldCurrItem-txt.JPG b/docs/images/spd15-SetFieldCurrItem-txt.JPG
similarity index 100%
rename from images/spd15-SetFieldCurrItem-txt.JPG
rename to docs/images/spd15-SetFieldCurrItem-txt.JPG
diff --git a/images/spd15-SetFieldCurrItem-visio.JPG b/docs/images/spd15-SetFieldCurrItem-visio.JPG
similarity index 100%
rename from images/spd15-SetFieldCurrItem-visio.JPG
rename to docs/images/spd15-SetFieldCurrItem-visio.JPG
diff --git a/images/spd15-SetTimePortion-txt.JPG b/docs/images/spd15-SetTimePortion-txt.JPG
similarity index 100%
rename from images/spd15-SetTimePortion-txt.JPG
rename to docs/images/spd15-SetTimePortion-txt.JPG
diff --git a/images/spd15-SetTimePortion-visio.JPG b/docs/images/spd15-SetTimePortion-visio.JPG
similarity index 100%
rename from images/spd15-SetTimePortion-visio.JPG
rename to docs/images/spd15-SetTimePortion-visio.JPG
diff --git a/images/spd15-SetWFStatus-txt.JPG b/docs/images/spd15-SetWFStatus-txt.JPG
similarity index 100%
rename from images/spd15-SetWFStatus-txt.JPG
rename to docs/images/spd15-SetWFStatus-txt.JPG
diff --git a/images/spd15-SetWFStatus-visio.JPG b/docs/images/spd15-SetWFStatus-visio.JPG
similarity index 100%
rename from images/spd15-SetWFStatus-visio.JPG
rename to docs/images/spd15-SetWFStatus-visio.JPG
diff --git a/images/spd15-SetWFVar-txt.JPG b/docs/images/spd15-SetWFVar-txt.JPG
similarity index 100%
rename from images/spd15-SetWFVar-txt.JPG
rename to docs/images/spd15-SetWFVar-txt.JPG
diff --git a/images/spd15-SetWFVar-visio.JPG b/docs/images/spd15-SetWFVar-visio.JPG
similarity index 100%
rename from images/spd15-SetWFVar-visio.JPG
rename to docs/images/spd15-SetWFVar-visio.JPG
diff --git a/images/spd15-StartApprovalProc-txt.JPG b/docs/images/spd15-StartApprovalProc-txt.JPG
similarity index 100%
rename from images/spd15-StartApprovalProc-txt.JPG
rename to docs/images/spd15-StartApprovalProc-txt.JPG
diff --git a/images/spd15-StartApprovalProc-visio.JPG b/docs/images/spd15-StartApprovalProc-visio.JPG
similarity index 100%
rename from images/spd15-StartApprovalProc-visio.JPG
rename to docs/images/spd15-StartApprovalProc-visio.JPG
diff --git a/images/spd15-StartCustomTask-txt.JPG b/docs/images/spd15-StartCustomTask-txt.JPG
similarity index 100%
rename from images/spd15-StartCustomTask-txt.JPG
rename to docs/images/spd15-StartCustomTask-txt.JPG
diff --git a/images/spd15-StartCustomTask-visio.JPG b/docs/images/spd15-StartCustomTask-visio.JPG
similarity index 100%
rename from images/spd15-StartCustomTask-visio.JPG
rename to docs/images/spd15-StartCustomTask-visio.JPG
diff --git a/images/spd15-StartFeedback-txt.JPG b/docs/images/spd15-StartFeedback-txt.JPG
similarity index 100%
rename from images/spd15-StartFeedback-txt.JPG
rename to docs/images/spd15-StartFeedback-txt.JPG
diff --git a/images/spd15-StartFeedback-visio.JPG b/docs/images/spd15-StartFeedback-visio.JPG
similarity index 100%
rename from images/spd15-StartFeedback-visio.JPG
rename to docs/images/spd15-StartFeedback-visio.JPG
diff --git a/images/spd15-StopWF-txt.JPG b/docs/images/spd15-StopWF-txt.JPG
similarity index 100%
rename from images/spd15-StopWF-txt.JPG
rename to docs/images/spd15-StopWF-txt.JPG
diff --git a/images/spd15-StopWF-visio.JPG b/docs/images/spd15-StopWF-visio.JPG
similarity index 100%
rename from images/spd15-StopWF-visio.JPG
rename to docs/images/spd15-StopWF-visio.JPG
diff --git a/images/spd15-TaskActions1.png b/docs/images/spd15-TaskActions1.png
similarity index 100%
rename from images/spd15-TaskActions1.png
rename to docs/images/spd15-TaskActions1.png
diff --git a/images/spd15-TitleFieldKeywords-txt.JPG b/docs/images/spd15-TitleFieldKeywords-txt.JPG
similarity index 100%
rename from images/spd15-TitleFieldKeywords-txt.JPG
rename to docs/images/spd15-TitleFieldKeywords-txt.JPG
diff --git a/images/spd15-TitleFieldKeywords-visio.JPG b/docs/images/spd15-TitleFieldKeywords-visio.JPG
similarity index 100%
rename from images/spd15-TitleFieldKeywords-visio.JPG
rename to docs/images/spd15-TitleFieldKeywords-visio.JPG
diff --git a/images/spd15-UpdateListItem-txt.JPG b/docs/images/spd15-UpdateListItem-txt.JPG
similarity index 100%
rename from images/spd15-UpdateListItem-txt.JPG
rename to docs/images/spd15-UpdateListItem-txt.JPG
diff --git a/images/spd15-UpdateListItem-visio.JPG b/docs/images/spd15-UpdateListItem-visio.JPG
similarity index 100%
rename from images/spd15-UpdateListItem-visio.JPG
rename to docs/images/spd15-UpdateListItem-visio.JPG
diff --git a/images/spd15-WFStart-icon.JPG b/docs/images/spd15-WFStart-icon.JPG
similarity index 100%
rename from images/spd15-WFStart-icon.JPG
rename to docs/images/spd15-WFStart-icon.JPG
diff --git a/images/spd15-WFStop-icon.JPG b/docs/images/spd15-WFStop-icon.JPG
similarity index 100%
rename from images/spd15-WFStop-icon.JPG
rename to docs/images/spd15-WFStop-icon.JPG
diff --git a/images/spd15-Wait4FieldChange-txt.JPG b/docs/images/spd15-Wait4FieldChange-txt.JPG
similarity index 100%
rename from images/spd15-Wait4FieldChange-txt.JPG
rename to docs/images/spd15-Wait4FieldChange-txt.JPG
diff --git a/images/spd15-Wait4FieldChange-visio.JPG b/docs/images/spd15-Wait4FieldChange-visio.JPG
similarity index 100%
rename from images/spd15-Wait4FieldChange-visio.JPG
rename to docs/images/spd15-Wait4FieldChange-visio.JPG
diff --git a/images/spd15-addcomment-txt.JPG b/docs/images/spd15-addcomment-txt.JPG
similarity index 100%
rename from images/spd15-addcomment-txt.JPG
rename to docs/images/spd15-addcomment-txt.JPG
diff --git a/images/spd15-addcomment-visio.JPG b/docs/images/spd15-addcomment-visio.JPG
similarity index 100%
rename from images/spd15-addcomment-visio.JPG
rename to docs/images/spd15-addcomment-visio.JPG
diff --git a/images/spd15-addtimetodate-txt.JPG b/docs/images/spd15-addtimetodate-txt.JPG
similarity index 100%
rename from images/spd15-addtimetodate-txt.JPG
rename to docs/images/spd15-addtimetodate-txt.JPG
diff --git a/images/spd15-addtimetodate-visio.JPG b/docs/images/spd15-addtimetodate-visio.JPG
similarity index 100%
rename from images/spd15-addtimetodate-visio.JPG
rename to docs/images/spd15-addtimetodate-visio.JPG
diff --git a/images/spd15-docalc-txt.JPG b/docs/images/spd15-docalc-txt.JPG
similarity index 100%
rename from images/spd15-docalc-txt.JPG
rename to docs/images/spd15-docalc-txt.JPG
diff --git a/images/spd15-docalc-visio.JPG b/docs/images/spd15-docalc-visio.JPG
similarity index 100%
rename from images/spd15-docalc-visio.JPG
rename to docs/images/spd15-docalc-visio.JPG
diff --git a/images/spd15-wf-PO.JPG b/docs/images/spd15-wf-PO.JPG
similarity index 100%
rename from images/spd15-wf-PO.JPG
rename to docs/images/spd15-wf-PO.JPG
diff --git a/images/spd15-wf-error1.JPG b/docs/images/spd15-wf-error1.JPG
similarity index 100%
rename from images/spd15-wf-error1.JPG
rename to docs/images/spd15-wf-error1.JPG
diff --git a/images/spd15-wf-error11.JPG b/docs/images/spd15-wf-error11.JPG
similarity index 100%
rename from images/spd15-wf-error11.JPG
rename to docs/images/spd15-wf-error11.JPG
diff --git a/images/spd15-wf-error12.JPG b/docs/images/spd15-wf-error12.JPG
similarity index 100%
rename from images/spd15-wf-error12.JPG
rename to docs/images/spd15-wf-error12.JPG
diff --git a/images/spd15-wf-error13.JPG b/docs/images/spd15-wf-error13.JPG
similarity index 100%
rename from images/spd15-wf-error13.JPG
rename to docs/images/spd15-wf-error13.JPG
diff --git a/images/spd15-wf-error14.JPG b/docs/images/spd15-wf-error14.JPG
similarity index 100%
rename from images/spd15-wf-error14.JPG
rename to docs/images/spd15-wf-error14.JPG
diff --git a/images/spd15-wf-error15.JPG b/docs/images/spd15-wf-error15.JPG
similarity index 100%
rename from images/spd15-wf-error15.JPG
rename to docs/images/spd15-wf-error15.JPG
diff --git a/images/spd15-wf-error16.JPG b/docs/images/spd15-wf-error16.JPG
similarity index 100%
rename from images/spd15-wf-error16.JPG
rename to docs/images/spd15-wf-error16.JPG
diff --git a/images/spd15-wf-error17.JPG b/docs/images/spd15-wf-error17.JPG
similarity index 100%
rename from images/spd15-wf-error17.JPG
rename to docs/images/spd15-wf-error17.JPG
diff --git a/images/spd15-wf-error18.JPG b/docs/images/spd15-wf-error18.JPG
similarity index 100%
rename from images/spd15-wf-error18.JPG
rename to docs/images/spd15-wf-error18.JPG
diff --git a/images/spd15-wf-error19.JPG b/docs/images/spd15-wf-error19.JPG
similarity index 100%
rename from images/spd15-wf-error19.JPG
rename to docs/images/spd15-wf-error19.JPG
diff --git a/images/spd15-wf-error2.JPG b/docs/images/spd15-wf-error2.JPG
similarity index 100%
rename from images/spd15-wf-error2.JPG
rename to docs/images/spd15-wf-error2.JPG
diff --git a/images/spd15-wf-error20.JPG b/docs/images/spd15-wf-error20.JPG
similarity index 100%
rename from images/spd15-wf-error20.JPG
rename to docs/images/spd15-wf-error20.JPG
diff --git a/images/spd15-wf-error21.JPG b/docs/images/spd15-wf-error21.JPG
similarity index 100%
rename from images/spd15-wf-error21.JPG
rename to docs/images/spd15-wf-error21.JPG
diff --git a/images/spd15-wf-error3.JPG b/docs/images/spd15-wf-error3.JPG
similarity index 100%
rename from images/spd15-wf-error3.JPG
rename to docs/images/spd15-wf-error3.JPG
diff --git a/images/spd15-wf-error4.JPG b/docs/images/spd15-wf-error4.JPG
similarity index 100%
rename from images/spd15-wf-error4.JPG
rename to docs/images/spd15-wf-error4.JPG
diff --git a/images/spd15-wf-error5.JPG b/docs/images/spd15-wf-error5.JPG
similarity index 100%
rename from images/spd15-wf-error5.JPG
rename to docs/images/spd15-wf-error5.JPG
diff --git a/images/spd15-wf-error6.JPG b/docs/images/spd15-wf-error6.JPG
similarity index 100%
rename from images/spd15-wf-error6.JPG
rename to docs/images/spd15-wf-error6.JPG
diff --git a/images/spd15-wf-error7.JPG b/docs/images/spd15-wf-error7.JPG
similarity index 100%
rename from images/spd15-wf-error7.JPG
rename to docs/images/spd15-wf-error7.JPG
diff --git a/images/spd15-wf-error8.JPG b/docs/images/spd15-wf-error8.JPG
similarity index 100%
rename from images/spd15-wf-error8.JPG
rename to docs/images/spd15-wf-error8.JPG
diff --git a/images/spd15-wf-error9.JPG b/docs/images/spd15-wf-error9.JPG
similarity index 100%
rename from images/spd15-wf-error9.JPG
rename to docs/images/spd15-wf-error9.JPG
diff --git a/images/spd15-wf-exportToVisio.png b/docs/images/spd15-wf-exportToVisio.png
similarity index 100%
rename from images/spd15-wf-exportToVisio.png
rename to docs/images/spd15-wf-exportToVisio.png
diff --git a/images/spd15-wf-importFromVisio.png b/docs/images/spd15-wf-importFromVisio.png
similarity index 100%
rename from images/spd15-wf-importFromVisio.png
rename to docs/images/spd15-wf-importFromVisio.png
diff --git a/images/spd15-wf-logical-ops.JPG b/docs/images/spd15-wf-logical-ops.JPG
similarity index 100%
rename from images/spd15-wf-logical-ops.JPG
rename to docs/images/spd15-wf-logical-ops.JPG
diff --git a/images/spd15-wf-step1a.JPG b/docs/images/spd15-wf-step1a.JPG
similarity index 100%
rename from images/spd15-wf-step1a.JPG
rename to docs/images/spd15-wf-step1a.JPG
diff --git a/images/spd15-wf.JPG b/docs/images/spd15-wf.JPG
similarity index 100%
rename from images/spd15-wf.JPG
rename to docs/images/spd15-wf.JPG
diff --git a/images/spfx-ext-youtube-tutorial1.png b/docs/images/spfx-ext-youtube-tutorial1.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorial1.png
rename to docs/images/spfx-ext-youtube-tutorial1.png
diff --git a/images/spfx-ext-youtube-tutorial2.png b/docs/images/spfx-ext-youtube-tutorial2.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorial2.png
rename to docs/images/spfx-ext-youtube-tutorial2.png
diff --git a/images/spfx-ext-youtube-tutorial3.png b/docs/images/spfx-ext-youtube-tutorial3.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorial3.png
rename to docs/images/spfx-ext-youtube-tutorial3.png
diff --git a/images/spfx-ext-youtube-tutorial4.png b/docs/images/spfx-ext-youtube-tutorial4.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorial4.png
rename to docs/images/spfx-ext-youtube-tutorial4.png
diff --git a/images/spfx-ext-youtube-tutorialcommand.png b/docs/images/spfx-ext-youtube-tutorialcommand.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorialcommand.png
rename to docs/images/spfx-ext-youtube-tutorialcommand.png
diff --git a/images/spfx-ext-youtube-tutorialfield.png b/docs/images/spfx-ext-youtube-tutorialfield.png
similarity index 100%
rename from images/spfx-ext-youtube-tutorialfield.png
rename to docs/images/spfx-ext-youtube-tutorialfield.png
diff --git a/images/spfx-webcast-youtube-provision-feature-elements.png b/docs/images/spfx-webcast-youtube-provision-feature-elements.png
similarity index 100%
rename from images/spfx-webcast-youtube-provision-feature-elements.png
rename to docs/images/spfx-webcast-youtube-provision-feature-elements.png
diff --git a/images/spfx-youtube-tutorial0.png b/docs/images/spfx-youtube-tutorial0.png
similarity index 100%
rename from images/spfx-youtube-tutorial0.png
rename to docs/images/spfx-youtube-tutorial0.png
diff --git a/images/spfx-youtube-tutorial1.png b/docs/images/spfx-youtube-tutorial1.png
similarity index 100%
rename from images/spfx-youtube-tutorial1.png
rename to docs/images/spfx-youtube-tutorial1.png
diff --git a/images/spfx-youtube-tutorial2.png b/docs/images/spfx-youtube-tutorial2.png
similarity index 100%
rename from images/spfx-youtube-tutorial2.png
rename to docs/images/spfx-youtube-tutorial2.png
diff --git a/images/spfx-youtube-tutorial3.png b/docs/images/spfx-youtube-tutorial3.png
similarity index 100%
rename from images/spfx-youtube-tutorial3.png
rename to docs/images/spfx-youtube-tutorial3.png
diff --git a/images/spfx-youtube-tutorial4.png b/docs/images/spfx-youtube-tutorial4.png
similarity index 100%
rename from images/spfx-youtube-tutorial4.png
rename to docs/images/spfx-youtube-tutorial4.png
diff --git a/images/spfx-youtube-tutorial5.png b/docs/images/spfx-youtube-tutorial5.png
similarity index 100%
rename from images/spfx-youtube-tutorial5.png
rename to docs/images/spfx-youtube-tutorial5.png
diff --git a/images/spfx-youtube-tutorial6.png b/docs/images/spfx-youtube-tutorial6.png
similarity index 100%
rename from images/spfx-youtube-tutorial6.png
rename to docs/images/spfx-youtube-tutorial6.png
diff --git a/images/static.gif b/docs/images/static.gif
similarity index 100%
rename from images/static.gif
rename to docs/images/static.gif
diff --git a/images/tenant-deploy-app-catalog.png b/docs/images/tenant-deploy-app-catalog.png
similarity index 100%
rename from images/tenant-deploy-app-catalog.png
rename to docs/images/tenant-deploy-app-catalog.png
diff --git a/images/tenant-deploy-yeoman.png b/docs/images/tenant-deploy-yeoman.png
similarity index 100%
rename from images/tenant-deploy-yeoman.png
rename to docs/images/tenant-deploy-yeoman.png
diff --git a/images/tenant-deploy-youtube-video.png b/docs/images/tenant-deploy-youtube-video.png
similarity index 100%
rename from images/tenant-deploy-youtube-video.png
rename to docs/images/tenant-deploy-youtube-video.png
diff --git a/images/theme_.PNG b/docs/images/theme_.PNG
similarity index 100%
rename from images/theme_.PNG
rename to docs/images/theme_.PNG
diff --git a/images/themed-styles-blue-web-part-red-site.png b/docs/images/themed-styles-blue-web-part-red-site.png
similarity index 100%
rename from images/themed-styles-blue-web-part-red-site.png
rename to docs/images/themed-styles-blue-web-part-red-site.png
diff --git a/images/themed-styles-button-class.png b/docs/images/themed-styles-button-class.png
similarity index 100%
rename from images/themed-styles-button-class.png
rename to docs/images/themed-styles-button-class.png
diff --git a/images/themed-styles-ms-bgcolor-themedark-class.png b/docs/images/themed-styles-ms-bgcolor-themedark-class.png
similarity index 100%
rename from images/themed-styles-ms-bgcolor-themedark-class.png
rename to docs/images/themed-styles-ms-bgcolor-themedark-class.png
diff --git a/images/themed-styles-row-class.png b/docs/images/themed-styles-row-class.png
similarity index 100%
rename from images/themed-styles-row-class.png
rename to docs/images/themed-styles-row-class.png
diff --git a/images/themed-styles-side-by-side.png b/docs/images/themed-styles-side-by-side.png
similarity index 100%
rename from images/themed-styles-side-by-side.png
rename to docs/images/themed-styles-side-by-side.png
diff --git a/images/thirdpartycss-accordion-not-styled.png b/docs/images/thirdpartycss-accordion-not-styled.png
similarity index 100%
rename from images/thirdpartycss-accordion-not-styled.png
rename to docs/images/thirdpartycss-accordion-not-styled.png
diff --git a/images/thirdpartycss-accordion-styled.png b/docs/images/thirdpartycss-accordion-styled.png
similarity index 100%
rename from images/thirdpartycss-accordion-styled.png
rename to docs/images/thirdpartycss-accordion-styled.png
diff --git a/images/thirdpartycss-jquery-ui-css-size.png b/docs/images/thirdpartycss-jquery-ui-css-size.png
similarity index 100%
rename from images/thirdpartycss-jquery-ui-css-size.png
rename to docs/images/thirdpartycss-jquery-ui-css-size.png
diff --git a/images/thirdpartycss-libraries-cdn.png b/docs/images/thirdpartycss-libraries-cdn.png
similarity index 100%
rename from images/thirdpartycss-libraries-cdn.png
rename to docs/images/thirdpartycss-libraries-cdn.png
diff --git a/images/thirdpartycss-visual-studio-code.png b/docs/images/thirdpartycss-visual-studio-code.png
similarity index 100%
rename from images/thirdpartycss-visual-studio-code.png
rename to docs/images/thirdpartycss-visual-studio-code.png
diff --git a/images/thirdpartycss-yeoman.png b/docs/images/thirdpartycss-yeoman.png
similarity index 100%
rename from images/thirdpartycss-yeoman.png
rename to docs/images/thirdpartycss-yeoman.png
diff --git a/images/toolchain-gulp-serve-task.png b/docs/images/toolchain-gulp-serve-task.png
similarity index 100%
rename from images/toolchain-gulp-serve-task.png
rename to docs/images/toolchain-gulp-serve-task.png
diff --git a/images/tutorial-feature-solution-add-app.png b/docs/images/tutorial-feature-solution-add-app.png
similarity index 100%
rename from images/tutorial-feature-solution-add-app.png
rename to docs/images/tutorial-feature-solution-add-app.png
diff --git a/images/tutorial-feature-solution-app-details.png b/docs/images/tutorial-feature-solution-app-details.png
similarity index 100%
rename from images/tutorial-feature-solution-app-details.png
rename to docs/images/tutorial-feature-solution-app-details.png
diff --git a/images/tutorial-feature-solution-debug-folder.png b/docs/images/tutorial-feature-solution-debug-folder.png
similarity index 100%
rename from images/tutorial-feature-solution-debug-folder.png
rename to docs/images/tutorial-feature-solution-debug-folder.png
diff --git a/images/tutorial-feature-solution-hover-menu.png b/docs/images/tutorial-feature-solution-hover-menu.png
similarity index 100%
rename from images/tutorial-feature-solution-hover-menu.png
rename to docs/images/tutorial-feature-solution-hover-menu.png
diff --git a/images/tutorial-feature-solution-initial-structure.png b/docs/images/tutorial-feature-solution-initial-structure.png
similarity index 100%
rename from images/tutorial-feature-solution-initial-structure.png
rename to docs/images/tutorial-feature-solution-initial-structure.png
diff --git a/images/tutorial-feature-solution-list-view.png b/docs/images/tutorial-feature-solution-list-view.png
similarity index 100%
rename from images/tutorial-feature-solution-list-view.png
rename to docs/images/tutorial-feature-solution-list-view.png
diff --git a/images/tutorial-feature-solution-new-list.png b/docs/images/tutorial-feature-solution-new-list.png
similarity index 100%
rename from images/tutorial-feature-solution-new-list.png
rename to docs/images/tutorial-feature-solution-new-list.png
diff --git a/images/tutorial-feature-solution-override-sppkg.png b/docs/images/tutorial-feature-solution-override-sppkg.png
similarity index 100%
rename from images/tutorial-feature-solution-override-sppkg.png
rename to docs/images/tutorial-feature-solution-override-sppkg.png
diff --git a/images/tutorial-feature-solution-provision-app.png b/docs/images/tutorial-feature-solution-provision-app.png
similarity index 100%
rename from images/tutorial-feature-solution-provision-app.png
rename to docs/images/tutorial-feature-solution-provision-app.png
diff --git a/images/tutorial-feature-solution-trust-app-catalog.png b/docs/images/tutorial-feature-solution-trust-app-catalog.png
similarity index 100%
rename from images/tutorial-feature-solution-trust-app-catalog.png
rename to docs/images/tutorial-feature-solution-trust-app-catalog.png
diff --git a/images/tutorial-feature-solution-updating-app.png b/docs/images/tutorial-feature-solution-updating-app.png
similarity index 100%
rename from images/tutorial-feature-solution-updating-app.png
rename to docs/images/tutorial-feature-solution-updating-app.png
diff --git a/images/tutorial-feature-solution-version-2.png b/docs/images/tutorial-feature-solution-version-2.png
similarity index 100%
rename from images/tutorial-feature-solution-version-2.png
rename to docs/images/tutorial-feature-solution-version-2.png
diff --git a/images/tutorial-sharingdata-console-log.png b/docs/images/tutorial-sharingdata-console-log.png
similarity index 100%
rename from images/tutorial-sharingdata-console-log.png
rename to docs/images/tutorial-sharingdata-console-log.png
diff --git a/images/tutorial-sharingdata-interfaces-documentsservice.png b/docs/images/tutorial-sharingdata-interfaces-documentsservice.png
similarity index 100%
rename from images/tutorial-sharingdata-interfaces-documentsservice.png
rename to docs/images/tutorial-sharingdata-interfaces-documentsservice.png
diff --git a/images/tutorial-sharingdata-interfaces.png b/docs/images/tutorial-sharingdata-interfaces.png
similarity index 100%
rename from images/tutorial-sharingdata-interfaces.png
rename to docs/images/tutorial-sharingdata-interfaces.png
diff --git a/images/tutorial-sharingdata-recent-document-recent-documents.png b/docs/images/tutorial-sharingdata-recent-document-recent-documents.png
similarity index 100%
rename from images/tutorial-sharingdata-recent-document-recent-documents.png
rename to docs/images/tutorial-sharingdata-recent-document-recent-documents.png
diff --git a/images/tutorial-sharingdata-recent-document.png b/docs/images/tutorial-sharingdata-recent-document.png
similarity index 100%
rename from images/tutorial-sharingdata-recent-document.png
rename to docs/images/tutorial-sharingdata-recent-document.png
diff --git a/images/tutorial-sharingdata-recent-documents.png b/docs/images/tutorial-sharingdata-recent-documents.png
similarity index 100%
rename from images/tutorial-sharingdata-recent-documents.png
rename to docs/images/tutorial-sharingdata-recent-documents.png
diff --git a/images/tutorial-sharingdata-vscode.png b/docs/images/tutorial-sharingdata-vscode.png
similarity index 100%
rename from images/tutorial-sharingdata-vscode.png
rename to docs/images/tutorial-sharingdata-vscode.png
diff --git a/images/tutorial-sharingdata-yo-sharepoint-recent-document.png b/docs/images/tutorial-sharingdata-yo-sharepoint-recent-document.png
similarity index 100%
rename from images/tutorial-sharingdata-yo-sharepoint-recent-document.png
rename to docs/images/tutorial-sharingdata-yo-sharepoint-recent-document.png
diff --git a/images/tutorial-sharingdata-yo-sharepoint-recent-documents.png b/docs/images/tutorial-sharingdata-yo-sharepoint-recent-documents.png
similarity index 100%
rename from images/tutorial-sharingdata-yo-sharepoint-recent-documents.png
rename to docs/images/tutorial-sharingdata-yo-sharepoint-recent-documents.png
diff --git a/images/tutorial-spjsom-vscode.png b/docs/images/tutorial-spjsom-vscode.png
similarity index 100%
rename from images/tutorial-spjsom-vscode.png
rename to docs/images/tutorial-spjsom-vscode.png
diff --git a/images/tutorial-spjsom-web-part-list-titles.png b/docs/images/tutorial-spjsom-web-part-list-titles.png
similarity index 100%
rename from images/tutorial-spjsom-web-part-list-titles.png
rename to docs/images/tutorial-spjsom-web-part-list-titles.png
diff --git a/images/tutorial-spjsom-yo-sharepoint.png b/docs/images/tutorial-spjsom-yo-sharepoint.png
similarity index 100%
rename from images/tutorial-spjsom-yo-sharepoint.png
rename to docs/images/tutorial-spjsom-yo-sharepoint.png
diff --git a/images/upload-solution-app-catalog.png b/docs/images/upload-solution-app-catalog.png
similarity index 100%
rename from images/upload-solution-app-catalog.png
rename to docs/images/upload-solution-app-catalog.png
diff --git a/images/vscode-debugging-add-debug-configuration.png b/docs/images/vscode-debugging-add-debug-configuration.png
similarity index 100%
rename from images/vscode-debugging-add-debug-configuration.png
rename to docs/images/vscode-debugging-add-debug-configuration.png
diff --git a/images/vscode-debugging-adding-web-part-to-canvas.png b/docs/images/vscode-debugging-adding-web-part-to-canvas.png
similarity index 100%
rename from images/vscode-debugging-adding-web-part-to-canvas.png
rename to docs/images/vscode-debugging-adding-web-part-to-canvas.png
diff --git a/images/vscode-debugging-breakpoint-active.png b/docs/images/vscode-debugging-breakpoint-active.png
similarity index 100%
rename from images/vscode-debugging-breakpoint-active.png
rename to docs/images/vscode-debugging-breakpoint-active.png
diff --git a/images/vscode-debugging-breakpoint-configured.png b/docs/images/vscode-debugging-breakpoint-configured.png
similarity index 100%
rename from images/vscode-debugging-breakpoint-configured.png
rename to docs/images/vscode-debugging-breakpoint-configured.png
diff --git a/images/vscode-debugging-breakpoint-hit-o365.png b/docs/images/vscode-debugging-breakpoint-hit-o365.png
similarity index 100%
rename from images/vscode-debugging-breakpoint-hit-o365.png
rename to docs/images/vscode-debugging-breakpoint-hit-o365.png
diff --git a/images/vscode-debugging-breakpoint-hit.png b/docs/images/vscode-debugging-breakpoint-hit.png
similarity index 100%
rename from images/vscode-debugging-breakpoint-hit.png
rename to docs/images/vscode-debugging-breakpoint-hit.png
diff --git a/images/vscode-debugging-chrome-debug-environment.png b/docs/images/vscode-debugging-chrome-debug-environment.png
similarity index 100%
rename from images/vscode-debugging-chrome-debug-environment.png
rename to docs/images/vscode-debugging-chrome-debug-environment.png
diff --git a/images/vscode-debugging-chrome-started.png b/docs/images/vscode-debugging-chrome-started.png
similarity index 100%
rename from images/vscode-debugging-chrome-started.png
rename to docs/images/vscode-debugging-chrome-started.png
diff --git a/images/vscode-debugging-debugger-chrome-extension.png b/docs/images/vscode-debugging-debugger-chrome-extension.png
similarity index 100%
rename from images/vscode-debugging-debugger-chrome-extension.png
rename to docs/images/vscode-debugging-debugger-chrome-extension.png
diff --git a/images/vscode-debugging-debugger-extension-installed-reload.png b/docs/images/vscode-debugging-debugger-extension-installed-reload.png
similarity index 100%
rename from images/vscode-debugging-debugger-extension-installed-reload.png
rename to docs/images/vscode-debugging-debugger-extension-installed-reload.png
diff --git a/images/vscode-debugging-debugging-hosted-workbench.png b/docs/images/vscode-debugging-debugging-hosted-workbench.png
similarity index 100%
rename from images/vscode-debugging-debugging-hosted-workbench.png
rename to docs/images/vscode-debugging-debugging-hosted-workbench.png
diff --git a/images/vscode-debugging-gulp-serve.png b/docs/images/vscode-debugging-gulp-serve.png
similarity index 100%
rename from images/vscode-debugging-gulp-serve.png
rename to docs/images/vscode-debugging-gulp-serve.png
diff --git a/images/vscode-debugging-o365-login.png b/docs/images/vscode-debugging-o365-login.png
similarity index 100%
rename from images/vscode-debugging-o365-login.png
rename to docs/images/vscode-debugging-o365-login.png
diff --git a/images/vscode-debugging-vscode-debug.png b/docs/images/vscode-debugging-vscode-debug.png
similarity index 100%
rename from images/vscode-debugging-vscode-debug.png
rename to docs/images/vscode-debugging-vscode-debug.png
diff --git a/images/vscode-debugging-vscode-extensions.png b/docs/images/vscode-debugging-vscode-extensions.png
similarity index 100%
rename from images/vscode-debugging-vscode-extensions.png
rename to docs/images/vscode-debugging-vscode-extensions.png
diff --git a/images/webhook-azure-function0.png b/docs/images/webhook-azure-function0.png
similarity index 100%
rename from images/webhook-azure-function0.png
rename to docs/images/webhook-azure-function0.png
diff --git a/images/webhook-azure-function1.png b/docs/images/webhook-azure-function1.png
similarity index 100%
rename from images/webhook-azure-function1.png
rename to docs/images/webhook-azure-function1.png
diff --git a/images/webhook-azure-function2.png b/docs/images/webhook-azure-function2.png
similarity index 100%
rename from images/webhook-azure-function2.png
rename to docs/images/webhook-azure-function2.png
diff --git a/images/webhook-azure-function3.png b/docs/images/webhook-azure-function3.png
similarity index 100%
rename from images/webhook-azure-function3.png
rename to docs/images/webhook-azure-function3.png
diff --git a/images/webhook-azure-function4.png b/docs/images/webhook-azure-function4.png
similarity index 100%
rename from images/webhook-azure-function4.png
rename to docs/images/webhook-azure-function4.png
diff --git a/images/webhook-azure-function5.png b/docs/images/webhook-azure-function5.png
similarity index 100%
rename from images/webhook-azure-function5.png
rename to docs/images/webhook-azure-function5.png
diff --git a/images/webhook-azure-function6.png b/docs/images/webhook-azure-function6.png
similarity index 100%
rename from images/webhook-azure-function6.png
rename to docs/images/webhook-azure-function6.png
diff --git a/images/webhook-azure-function7.png b/docs/images/webhook-azure-function7.png
similarity index 100%
rename from images/webhook-azure-function7.png
rename to docs/images/webhook-azure-function7.png
diff --git a/images/webhook-azure-function8.png b/docs/images/webhook-azure-function8.png
similarity index 100%
rename from images/webhook-azure-function8.png
rename to docs/images/webhook-azure-function8.png
diff --git a/images/webhook-sample-add-process.png b/docs/images/webhook-sample-add-process.png
similarity index 100%
rename from images/webhook-sample-add-process.png
rename to docs/images/webhook-sample-add-process.png
diff --git a/images/webhook-sample-application.png b/docs/images/webhook-sample-application.png
similarity index 100%
rename from images/webhook-sample-application.png
rename to docs/images/webhook-sample-application.png
diff --git a/images/webhook-sample-async-getchanges.png b/docs/images/webhook-sample-async-getchanges.png
similarity index 100%
rename from images/webhook-sample-async-getchanges.png
rename to docs/images/webhook-sample-async-getchanges.png
diff --git a/images/webhook-sample-call-webhook.png b/docs/images/webhook-sample-call-webhook.png
similarity index 100%
rename from images/webhook-sample-call-webhook.png
rename to docs/images/webhook-sample-call-webhook.png
diff --git a/images/webhook-sample-end-to-end-flow.png b/docs/images/webhook-sample-end-to-end-flow.png
similarity index 100%
rename from images/webhook-sample-end-to-end-flow.png
rename to docs/images/webhook-sample-end-to-end-flow.png
diff --git a/images/webpart-configure-property-pane.png b/docs/images/webpart-configure-property-pane.png
similarity index 100%
rename from images/webpart-configure-property-pane.png
rename to docs/images/webpart-configure-property-pane.png
diff --git a/images/webpart-gallery-helloworld.png b/docs/images/webpart-gallery-helloworld.png
similarity index 100%
rename from images/webpart-gallery-helloworld.png
rename to docs/images/webpart-gallery-helloworld.png
diff --git a/images/wf15-eventingactions3.png b/docs/images/wf15-eventingactions3.png
similarity index 100%
rename from images/wf15-eventingactions3.png
rename to docs/images/wf15-eventingactions3.png
diff --git a/images/wf15-eventingactions4.png b/docs/images/wf15-eventingactions4.png
similarity index 100%
rename from images/wf15-eventingactions4.png
rename to docs/images/wf15-eventingactions4.png
diff --git a/images/wfAddNewItemDialog_b2.png b/docs/images/wfAddNewItemDialog_b2.png
similarity index 100%
rename from images/wfAddNewItemDialog_b2.png
rename to docs/images/wfAddNewItemDialog_b2.png
diff --git a/images/wfArchitecture1.png b/docs/images/wfArchitecture1.png
similarity index 100%
rename from images/wfArchitecture1.png
rename to docs/images/wfArchitecture1.png
diff --git a/images/wfInteropBridge.png b/docs/images/wfInteropBridge.png
similarity index 100%
rename from images/wfInteropBridge.png
rename to docs/images/wfInteropBridge.png
diff --git a/images/wfInteropMessaging.png b/docs/images/wfInteropMessaging.png
similarity index 100%
rename from images/wfInteropMessaging.png
rename to docs/images/wfInteropMessaging.png
diff --git a/images/wfInterop_.png b/docs/images/wfInterop_.png
similarity index 100%
rename from images/wfInterop_.png
rename to docs/images/wfInterop_.png
diff --git a/images/wfInterop_Stage1.png b/docs/images/wfInterop_Stage1.png
similarity index 100%
rename from images/wfInterop_Stage1.png
rename to docs/images/wfInterop_Stage1.png
diff --git a/images/wfNewProject_b2.png b/docs/images/wfNewProject_b2.png
similarity index 100%
rename from images/wfNewProject_b2.png
rename to docs/images/wfNewProject_b2.png
diff --git a/images/wfSimple.gif b/docs/images/wfSimple.gif
similarity index 100%
rename from images/wfSimple.gif
rename to docs/images/wfSimple.gif
diff --git a/images/wfToolbox_b2.png b/docs/images/wfToolbox_b2.png
similarity index 100%
rename from images/wfToolbox_b2.png
rename to docs/images/wfToolbox_b2.png
diff --git a/images/wfVS_ActivityNode.jpg b/docs/images/wfVS_ActivityNode.jpg
similarity index 100%
rename from images/wfVS_ActivityNode.jpg
rename to docs/images/wfVS_ActivityNode.jpg
diff --git a/images/wfVS_NewItem.JPG b/docs/images/wfVS_NewItem.JPG
similarity index 100%
rename from images/wfVS_NewItem.JPG
rename to docs/images/wfVS_NewItem.JPG
diff --git a/images/wfVS_NewProjectDialog.JPG b/docs/images/wfVS_NewProjectDialog.JPG
similarity index 100%
rename from images/wfVS_NewProjectDialog.JPG
rename to docs/images/wfVS_NewProjectDialog.JPG
diff --git a/images/wfVS_WorkflowToolbox.jpg b/docs/images/wfVS_WorkflowToolbox.jpg
similarity index 100%
rename from images/wfVS_WorkflowToolbox.jpg
rename to docs/images/wfVS_WorkflowToolbox.jpg
diff --git a/images/wn_DevTools_1.png b/docs/images/wn_DevTools_1.png
similarity index 100%
rename from images/wn_DevTools_1.png
rename to docs/images/wn_DevTools_1.png
diff --git a/images/wn_DevTools_2.png b/docs/images/wn_DevTools_2.png
similarity index 100%
rename from images/wn_DevTools_2.png
rename to docs/images/wn_DevTools_2.png
diff --git a/images/wn_DevTools_3.png b/docs/images/wn_DevTools_3.png
similarity index 100%
rename from images/wn_DevTools_3.png
rename to docs/images/wn_DevTools_3.png
diff --git a/images/wn_Mobility_.png b/docs/images/wn_Mobility_.png
similarity index 100%
rename from images/wn_Mobility_.png
rename to docs/images/wn_Mobility_.png
diff --git a/images/wn_Mobility_2.png b/docs/images/wn_Mobility_2.png
similarity index 100%
rename from images/wn_Mobility_2.png
rename to docs/images/wn_Mobility_2.png
diff --git a/images/wn_Mobility_3.png b/docs/images/wn_Mobility_3.png
similarity index 100%
rename from images/wn_Mobility_3.png
rename to docs/images/wn_Mobility_3.png
diff --git a/images/wn_Platform_1.png b/docs/images/wn_Platform_1.png
similarity index 100%
rename from images/wn_Platform_1.png
rename to docs/images/wn_Platform_1.png
diff --git a/images/wn_Platform_2.png b/docs/images/wn_Platform_2.png
similarity index 100%
rename from images/wn_Platform_2.png
rename to docs/images/wn_Platform_2.png
diff --git a/images/wn_Platform_3.png b/docs/images/wn_Platform_3.png
similarity index 100%
rename from images/wn_Platform_3.png
rename to docs/images/wn_Platform_3.png
diff --git a/images/wn_Platform_4.png b/docs/images/wn_Platform_4.png
similarity index 100%
rename from images/wn_Platform_4.png
rename to docs/images/wn_Platform_4.png
diff --git a/images/wn_Social_1.png b/docs/images/wn_Social_1.png
similarity index 100%
rename from images/wn_Social_1.png
rename to docs/images/wn_Social_1.png
diff --git a/images/wn_Social_2.png b/docs/images/wn_Social_2.png
similarity index 100%
rename from images/wn_Social_2.png
rename to docs/images/wn_Social_2.png
diff --git a/images/wn_Social_3.png b/docs/images/wn_Social_3.png
similarity index 100%
rename from images/wn_Social_3.png
rename to docs/images/wn_Social_3.png
diff --git a/images/wn_Social_4.png b/docs/images/wn_Social_4.png
similarity index 100%
rename from images/wn_Social_4.png
rename to docs/images/wn_Social_4.png
diff --git a/images/wn_WebStandards_1.png b/docs/images/wn_WebStandards_1.png
similarity index 100%
rename from images/wn_WebStandards_1.png
rename to docs/images/wn_WebStandards_1.png
diff --git a/images/wn_WebStandards_2.png b/docs/images/wn_WebStandards_2.png
similarity index 100%
rename from images/wn_WebStandards_2.png
rename to docs/images/wn_WebStandards_2.png
diff --git a/images/wn_WebStandards_3.png b/docs/images/wn_WebStandards_3.png
similarity index 100%
rename from images/wn_WebStandards_3.png
rename to docs/images/wn_WebStandards_3.png
diff --git a/images/wn_WebStandards_4.png b/docs/images/wn_WebStandards_4.png
similarity index 100%
rename from images/wn_WebStandards_4.png
rename to docs/images/wn_WebStandards_4.png
diff --git a/images/wn_appServices_1.png b/docs/images/wn_appServices_1.png
similarity index 100%
rename from images/wn_appServices_1.png
rename to docs/images/wn_appServices_1.png
diff --git a/images/wn_appServices_2.png b/docs/images/wn_appServices_2.png
similarity index 100%
rename from images/wn_appServices_2.png
rename to docs/images/wn_appServices_2.png
diff --git a/images/wn_appServices_3.png b/docs/images/wn_appServices_3.png
similarity index 100%
rename from images/wn_appServices_3.png
rename to docs/images/wn_appServices_3.png
diff --git a/images/wn_appServices_4.png b/docs/images/wn_appServices_4.png
similarity index 100%
rename from images/wn_appServices_4.png
rename to docs/images/wn_appServices_4.png
diff --git a/images/wn_bcs_1.png b/docs/images/wn_bcs_1.png
similarity index 100%
rename from images/wn_bcs_1.png
rename to docs/images/wn_bcs_1.png
diff --git a/images/wn_bcs_2.png b/docs/images/wn_bcs_2.png
similarity index 100%
rename from images/wn_bcs_2.png
rename to docs/images/wn_bcs_2.png
diff --git a/images/wn_bcs_3.png b/docs/images/wn_bcs_3.png
similarity index 100%
rename from images/wn_bcs_3.png
rename to docs/images/wn_bcs_3.png
diff --git a/images/wn_cloud_1.png b/docs/images/wn_cloud_1.png
similarity index 100%
rename from images/wn_cloud_1.png
rename to docs/images/wn_cloud_1.png
diff --git a/images/wn_cloud_2.png b/docs/images/wn_cloud_2.png
similarity index 100%
rename from images/wn_cloud_2.png
rename to docs/images/wn_cloud_2.png
diff --git a/images/wn_cloud_3.png b/docs/images/wn_cloud_3.png
similarity index 100%
rename from images/wn_cloud_3.png
rename to docs/images/wn_cloud_3.png
diff --git a/images/wn_ecm_1.png b/docs/images/wn_ecm_1.png
similarity index 100%
rename from images/wn_ecm_1.png
rename to docs/images/wn_ecm_1.png
diff --git a/images/wn_ecm_2.png b/docs/images/wn_ecm_2.png
similarity index 100%
rename from images/wn_ecm_2.png
rename to docs/images/wn_ecm_2.png
diff --git a/images/wn_ecm_3.png b/docs/images/wn_ecm_3.png
similarity index 100%
rename from images/wn_ecm_3.png
rename to docs/images/wn_ecm_3.png
diff --git a/images/wn_ecm_4.png b/docs/images/wn_ecm_4.png
similarity index 100%
rename from images/wn_ecm_4.png
rename to docs/images/wn_ecm_4.png
diff --git a/images/wn_search_1.png b/docs/images/wn_search_1.png
similarity index 100%
rename from images/wn_search_1.png
rename to docs/images/wn_search_1.png
diff --git a/images/wn_search_2.png b/docs/images/wn_search_2.png
similarity index 100%
rename from images/wn_search_2.png
rename to docs/images/wn_search_2.png
diff --git a/images/wn_search_3.png b/docs/images/wn_search_3.png
similarity index 100%
rename from images/wn_search_3.png
rename to docs/images/wn_search_3.png
diff --git a/images/wn_workflow_1.png b/docs/images/wn_workflow_1.png
similarity index 100%
rename from images/wn_workflow_1.png
rename to docs/images/wn_workflow_1.png
diff --git a/images/wn_workflow_2.png b/docs/images/wn_workflow_2.png
similarity index 100%
rename from images/wn_workflow_2.png
rename to docs/images/wn_workflow_2.png
diff --git a/images/wn_workflow_3.png b/docs/images/wn_workflow_3.png
similarity index 100%
rename from images/wn_workflow_3.png
rename to docs/images/wn_workflow_3.png
diff --git a/images/wn_workflow_4.png b/docs/images/wn_workflow_4.png
similarity index 100%
rename from images/wn_workflow_4.png
rename to docs/images/wn_workflow_4.png
diff --git a/images/xna.gif b/docs/images/xna.gif
similarity index 100%
rename from images/xna.gif
rename to docs/images/xna.gif
diff --git a/images/yeoman-sp-cmdline-options.png b/docs/images/yeoman-sp-cmdline-options.png
similarity index 100%
rename from images/yeoman-sp-cmdline-options.png
rename to docs/images/yeoman-sp-cmdline-options.png
diff --git a/images/yeoman-sp-complete.png b/docs/images/yeoman-sp-complete.png
similarity index 100%
rename from images/yeoman-sp-complete.png
rename to docs/images/yeoman-sp-complete.png
diff --git a/images/yeoman-sp-generator.png b/docs/images/yeoman-sp-generator.png
similarity index 100%
rename from images/yeoman-sp-generator.png
rename to docs/images/yeoman-sp-generator.png
diff --git a/images/yeoman-sp-prompts.png b/docs/images/yeoman-sp-prompts.png
similarity index 100%
rename from images/yeoman-sp-prompts.png
rename to docs/images/yeoman-sp-prompts.png
diff --git a/images/youtube-getting-started-with-webhooks.png b/docs/images/youtube-getting-started-with-webhooks.png
similarity index 100%
rename from images/youtube-getting-started-with-webhooks.png
rename to docs/images/youtube-getting-started-with-webhooks.png
diff --git a/images/youtube-introducing-sharepoint-webhooks.png b/docs/images/youtube-introducing-sharepoint-webhooks.png
similarity index 100%
rename from images/youtube-introducing-sharepoint-webhooks.png
rename to docs/images/youtube-introducing-sharepoint-webhooks.png
diff --git a/docs/index.md b/docs/index.md
new file mode 100644
index 0000000000..94d6107c08
--- /dev/null
+++ b/docs/index.md
@@ -0,0 +1,39 @@
+---
+title: SharePoint development
+ms.date: 09/25/2017
+---
+
+
+# SharePoint development
+
+Build apps, add-ins, and solutions for SharePoint for your enterprise or customer needs.
+
+## SharePoint Framework
+
+The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one.
+
+[Overview of the SharePoint Framework](spfx/sharepoint-framework-overview.md)
+
+## SharePoint REST service
+
+Interact with SharePoint data by using any technology that supports REST web requests. Perform Create,  Read,  Update, and  Delete (CRUD) operations from your SharePoint Add-ins, solutions, and client applications, using REST web technologies and standard Open Data Protocol (OData) syntax.
+
+[Get to know the SharePoint REST service](apis/rest/get-to-know-the-sharepoint-rest-service.md)
+
+## SharePoint webhooks
+
+Build applications that subscribe to receive notifications on specific events that occur in SharePoint.
+
+[Overview of SharePoint webhooks](apis/webhooks/overview-sharepoint-webhooks.md)
+
+## SharePoint Add-ins
+
+SharePoint Add-ins are self-contained extensions of SharePoint websites that you create, and that run without custom code on the SharePoint server.
+
+[SharePoint Add-ins](sp-add-ins/sharepoint-add-ins.md)
+
+## SharePoint general development
+
+SharePoint is a versatile development platform for building add-ins and solutions with varying scopes that address a wide range of needs. Learn the features, technologies, capabilities, and models for development that distinguish SharePoint as a development platform. Write your first add-in, get started working with the platform, create, use and interact with SharePoint resources in your own code.
+
+[SharePoint development overview](general-development/sharepoint-development-overview.md)
diff --git a/docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md b/docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md
index 2d76671af3..7e8518ccbf 100644
--- a/docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md
+++ b/docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md
@@ -1,8 +1,15 @@
+---
+title: Access SharePoint data from add-ins using the cross-domain library
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Access SharePoint data from add-ins using the cross-domain library
 Learn how to access data in a SharePoint website from your add-in by using the cross domain library in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 When you build SharePoint Add-ins, you usually have to incorporate data from various sources. But for  [security reasons](http://msdn.microsoft.com/library/cc709423.aspx), there are blocking mechanisms that prevent communication with more than one domain at a time. These security mechanisms are implemented in most browsers, making difficult or impossible to accomplish client-side calls across domains.
@@ -23,7 +30,7 @@ When you use the cross-domain library, the webpages in your add-in can access da
  **Note**  In this topic,  **add-in domain** refers to the domain that hosts the add-in pages. This can be the domain of a remote web application in a provider-hosted, but add-in pages can also be on SharePoint in the add-in web and make calls to the host web domain. In the latter scenario, the add-in domain is the domain of the add-in web.
  
 
-The main example in this article shows how to build an add-in that reads data on the add-in web and displays it in a webpage. The  [Next steps](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_Next) section shows more scenarios that build on top of the main example.
+The main example in this article shows how to build an add-in that reads data on the add-in web and displays it in a webpage. The  [Next steps](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_Next) section shows more scenarios that build on top of the main example.
  
 
 ## Prerequisites for using the examples in this article
@@ -75,7 +82,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
  
 
  
-![Cross domain read items sample result screen](../../images/CrossDomainReadItemsResult.png)
+![Cross domain read items sample result screen](../images/CrossDomainReadItemsResult.png)
  
 
 ### Create a SharePoint Add-in and web projects
@@ -94,7 +101,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
  
 4. Select  **Provider-hosted** as the hosting option for your add-in.
     
-     **Note**  You can also use the cross-domain library in a SharePoint-hosted add-in. However, in a SharePoint-hosted add-in the add-in page is already in the add-in web, in which case it wouldn't need the cross-domain library to read the list items. For a SharePoint-hosted add-in sample that reads data in the host web, see  [Use the cross-domain library in a SharePoint-hosted add-in (REST)](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-00c37814) or see [Access data from the host web](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_Hostweb) later in this article.
+     **Note**  You can also use the cross-domain library in a SharePoint-hosted add-in. However, in a SharePoint-hosted add-in the add-in page is already in the add-in web, in which case it wouldn't need the cross-domain library to read the list items. For a SharePoint-hosted add-in sample that reads data in the host web, see  [Use the cross-domain library in a SharePoint-hosted add-in (REST)](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-00c37814) or see [Access data from the host web](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_Hostweb) later in this article.
 
 ### Create list items on the add-in web
 
@@ -147,7 +154,7 @@ Figure 2 shows a webpage that displays the data on the add-in web.
  
   - Instantiates the  **RequestExecutor** object. By default, RequestExecutor uses the add-in web as the context site.
     
-     **Note**  You can change the context site to other sites different than the add-in web by using the  **AppContextSite** endpoint (REST) or object (JSOM). To learn more about AppContextSite, see [Access data from the host web](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_Hostweb) later in this article.
+     **Note**  You can change the context site to other sites different than the add-in web by using the  **AppContextSite** endpoint (REST) or object (JSOM). To learn more about AppContextSite, see [Access data from the host web](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_Hostweb) later in this article.
   - Issues a REST call to the list items endpoint.
     
  
@@ -287,7 +294,7 @@ If you prefer downloadable code samples, you can get this one from code gallery.
 
 |**If you see…**|**Then try…**|
 |:-----|:-----|
-|Error message: Sorry, we had some trouble accessing your site.There is also a button to fix the error, but it doesn't correct the problem.|You may have hit a known problem with security zones in Internet Explorer, see  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-zones-in-sharepoint-add-ins).|
+|Error message: Sorry, we had some trouble accessing your site.There is also a button to fix the error, but it doesn't correct the problem.|You may have hit a known problem with security zones in Internet Explorer, see  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md).|
 |Error message: The required functionalities are not supported by your browser. Please make sure you are using IE 8 or above, or other modern browser. Please make sure the 'X-UA-Compatible' meta tag is set to be 'IE=8' or above.|The cross-domain library requires a document mode of  **IE8** or above. In some scenarios, the document mode is set to **IE7** by default. You can use the Internet Explorer developer tools to determine and change the document mode of your page. For more information, see [Defining Document Compatibility](http://msdn.microsoft.com/library/cc288325.aspx).|
 |Error message: 'Type' is undefined.Additionally, your add-in uses the JavaScript Object Model (JSOM).|The JSOM uses the  **Type.registerNamespace** method in the Microsoft Ajax library to register the **SP** namespace. Use the following code to add a reference to the Microsoft Ajax library from your page:```HTML<script  type="text/javascript"  src="//ajax.aspnetcdn.com/ajax/4.0/1/MicrosoftAjax.js"></script>```|
 
@@ -432,7 +439,7 @@ Your add-in also needs permission to access data from the tenant. The following
 </AppPermissionRequests>
 ```
 
-To switch the context site in your code, use the  **AppContextSite** endpoint (REST) or object (JSOM), just like in the [Access data from the host web](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_Hostweb) section. Here is a reminder of the REST endpoint: /_api/SP.AppContextSite(@target)/web/title?@target='weburl', and an example on how to instantiate the object in JSOM: `appContextSite = new SP.AppContextSite(context, weburl);`.
+To switch the context site in your code, use the  **AppContextSite** endpoint (REST) or object (JSOM), just like in the [Access data from the host web](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_Hostweb) section. Here is a reminder of the REST endpoint: /_api/SP.AppContextSite(@target)/web/title?@target='weburl', and an example on how to instantiate the object in JSOM: `appContextSite = new SP.AppContextSite(context, weburl);`.
  
 
  
@@ -456,7 +463,7 @@ The cross-domain library uses a proxy page that is hosted in an  **IFrame** on t
  
 
  
-However, there is a solution for these scenarios. The solution is the  **apphost pattern**, which consists in wrapping the add-in pages in a page hosted in the add-in web. It's a good idea to use the apphost pattern in add-ins that use the cross-domain library, even if there are no evident security boundaries. For more information, see [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-zones-in-sharepoint-add-ins).
+However, there is a solution for these scenarios. The solution is the  **apphost pattern**, which consists in wrapping the add-in pages in a page hosted in the add-in web. It's a good idea to use the apphost pattern in add-ins that use the cross-domain library, even if there are no evident security boundaries. For more information, see [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md).
  
 
  
@@ -504,18 +511,18 @@ To download a sample of a SharePoint-hosted add-in that uses the cross-domain li
 -  [Code sample: Use custom actions and the cross-domain library to order books](http://code.msdn.microsoft.com/SharePoint-2013-Open-a-36d1598d)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-zones-in-sharepoint-add-ins)
+-  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md)
     
  
--  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013)
+-  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md)
     
  
--  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013)
+-  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md)
     
  
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md b/docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
index 75f09f01bf..8f0d29203f 100644
--- a/docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
+++ b/docs/sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
@@ -1,20 +1,26 @@
+---
+title: Add a custom content type to a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 # Add a custom content type to a SharePoint-hosted SharePoint Add-in
 Learn how to include custom content types in an SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the fourth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the other articles in this series:
+This is the fourth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the other articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
 
@@ -53,7 +59,7 @@ In this article you add a custom content type to the Employee Orientation ShareP
     
     **Content Type Tab**
 
-  ![The Content Type Designer showing 'NewEmployee' as the type name, 'Represents a new employee' as the description, and 'Employee Orientation' as the group.](../../images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG)
+  ![The Content Type Designer showing 'NewEmployee' as the type name, 'Represents a new employee' as the description, and 'Employee Orientation' as the group.](../images/8a9768f4-315d-45c0-88d7-687dbf84495c.PNG)
  
  
 7. Open the  **Columns** tab in the designer.
@@ -62,7 +68,7 @@ In this article you add a custom content type to the Employee Orientation ShareP
     
     **Columns Tab**
 
-    ![The Columns tab of the Content Type Designer with "Employee", "Division", and "Orientation Stage" listed in the grid.](../../images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG)
+    ![The Columns tab of the Content Type Designer with "Employee", "Division", and "Orientation Stage" listed in the grid.](../images/835e78b3-a073-45b2-b4ee-3f9be9d88495.PNG)
  
  
 9. Save the file and close the designer.
@@ -104,7 +110,7 @@ In this article you add a custom content type to the Employee Orientation ShareP
     
     **Content Type Settings dialog box**
 
-    ![The Content Type Settings dialog with just a single content type, named NewEmployee, listed.](../../images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG)
+    ![The Content Type Settings dialog with just a single content type, named NewEmployee, listed.](../images/b90699f4-40de-4f50-ad47-3e8773d0eb92.PNG)
  
 19.  Choose **OK** to close the dialog box, and then save and close the file.
     
@@ -176,7 +182,7 @@ In this article you add a custom content type to the Employee Orientation ShareP
     
     **New Employees in Seattle list**
 
-    ![The "New Employees in Seattle" list with the Division and Orientation Stage columns already present.](../../images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG) 
+    ![The "New Employees in Seattle" list with the Division and Orientation Stage columns already present.](../images/b654af45-663e-425c-b7c7-b8b5524cb316.PNG) 
  
 4. Try adding new items to the list and editing existing items.
     
@@ -189,4 +195,4 @@ In this article you add a custom content type to the Employee Orientation ShareP
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add a list view Web Part to the default page of the SharePoint Add-in:  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in).
+In the next article in this series, you'll add a list view Web Part to the default page of the SharePoint Add-in:  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md).
diff --git a/docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
index 78a43cf93a..3e20b3c07e 100644
--- a/docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
@@ -1,32 +1,36 @@
-
+---
+title: Add a custom page and style to a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # Add a custom page and style to a SharePoint-hosted SharePoint Add-in
 Learn how to include a custom page and CSS file in an SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the seventh in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the seventh in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
 
@@ -124,7 +128,7 @@ In this article you add a help page to the Employee Orientation SharePoint Add-i
 
  
 
-  ![A SharePoint page with title "Help". There is a header line in black, followed by two text lines in green.](../../images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG)
+  ![A SharePoint page with title "Help". There is a header line in black, followed by two text lines in green.](../images/2df51ab0-5b24-4a37-8b6a-6e95dbb1aeaa.PNG)
  
 
     
@@ -140,7 +144,7 @@ In this article you add a help page to the Employee Orientation SharePoint Add-i
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add a custom client-side rendering to a list column in a SharePoint Add-in:  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in).
+In the next article in this series, you'll add a custom client-side rendering to a list column in a SharePoint Add-in:  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
index 5905b12990..165d1e8a08 100644
--- a/docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
@@ -1,23 +1,30 @@
+---
+title: Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in
 Learn how to include Web Parts in a page in an SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the fifth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the earlier articles in this series:
+This is the fifth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the earlier articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
 
@@ -125,7 +132,7 @@ In this article you add a Web Part to the default page of the Employee Orientati
 
  
 
-     ![Default page of the add-in with the "New Employees in Seattle" list displayed in a Web Part.](../../images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG)
+     ![Default page of the add-in with the "New Employees in Seattle" list displayed in a Web Part.](../images/31e8e4b1-e2e6-416b-b360-9979a1f16fc7.PNG)
  
 
     
@@ -144,7 +151,7 @@ In this article you add a Web Part to the default page of the Employee Orientati
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add a workflow to the SharePoint Add-in:  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in).
+In the next article in this series, you'll add a workflow to the SharePoint Add-in:  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md
index 99e42863f5..9018a1efa3 100644
--- a/docs/sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md
@@ -1,26 +1,33 @@
+---
+title: Add a workflow to a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add a workflow to a SharePoint-hosted SharePoint Add-in
 Learn how to include a workflow in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the sixth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the sixth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
 
@@ -96,7 +103,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  **Note**  At various times when designing your workflow, a blue diamond symbol with an exclamation mark in it, 
  
-![A small blue diamond shape with a white exclamation mark in it.](../../images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG)
+![A small blue diamond shape with a white exclamation mark in it.](../images/f7b82a70-80fe-4e7e-a0f5-5a78cd12b367.PNG)
  
 , will appear on one or more items in the workflow designer. These report temporary errors. (Hover the cursor over the symbol to see a brief message, or look in the Visual Studio  **Error List** for details.) These are side effects of the incompleteness of the workflow. They should all be gone when you have finished this procedure.
  
@@ -124,7 +131,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The Properties pane of the Lookup List Item workflow activity with ItemID, ListID, and DisplayName properties set.](../../images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG)
+  ![The Properties pane of the Lookup List Item workflow activity with ItemID, ListID, and DisplayName properties set.](../images/60f3302e-ca9c-45be-b785-0c9f636181da.PNG)
  
 
     Click anywhere outside the pane to save your changes and the designer surface should now look like this.
@@ -134,7 +141,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The workflow designer with a Sequence box and, inside it, an activity named Lookup Current New Employee.](../../images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG)
+  ![The workflow designer with a Sequence box and, inside it, an activity named Lookup Current New Employee.](../images/c8fbf801-e8e4-444a-9d2e-c14e29f537de.PNG)
  
 
     
@@ -161,7 +168,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The Properties dialog for the "Get Dynamic Values" activity, with the Entity Type set to items of the New Employees list, and variables named Title and OrientationStage assigned to the fields of the same names.](../../images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG)
+  ![The Properties dialog for the "Get Dynamic Values" activity, with the Entity Type set to items of the New Employees list, and variables named Title and OrientationStage assigned to the fields of the same names.](../images/36a841e7-ce1b-444c-9bfe-7cdc56399ec1.PNG)
  
 
  
@@ -173,7 +180,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The workflow designer with two activities: a List Item Lookup and a Get Dynamic Values.](../../images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG)
+  ![The workflow designer with two activities: a List Item Lookup and a Get Dynamic Values.](../images/cd8eb456-d883-491a-b171-38c1b9f64018.PNG)
  
 
     
@@ -210,7 +217,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The workflow designer with activities for "List Item Lookup", "Get Dynamic Value", and an "If Then Else" structure. Email is the activity in the Then part and Terminate Worklow is the activity in the Else.](../../images/c1230e3b-d149-413c-aa66-d258250a4512.PNG)
+  ![The workflow designer with activities for "List Item Lookup", "Get Dynamic Value", and an "If Then Else" structure. Email is the activity in the Then part and Terminate Worklow is the activity in the Else.](../images/c1230e3b-d149-413c-aa66-d258250a4512.PNG)
  
 
  
@@ -236,7 +243,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![The workflow Test Service Host window with a line saying that the workflow has started, followed by a line saying that it has completed. The GUID of the workflow instance is at the beginning of each line.](../../images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG)
+  ![The workflow Test Service Host window with a line saying that the workflow has started, followed by a line saying that it has completed. The GUID of the workflow instance is at the beginning of each line.](../images/2422936d-7ef6-4c90-a03f-30053fbb9743.PNG)
  
 
     
@@ -249,13 +256,11 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 
  
 
-  ![An email message in Outlook from the workflow with subject "Cassie Hicks is ready for HR paperwork" and body "Cassie Hicks is waiting in the lobby to fill out benefits and employement forms."](../../images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG)
+  ![An email message in Outlook from the workflow with subject "Cassie Hicks is ready for HR paperwork" and body "Cassie Hicks is waiting in the lobby to fill out benefits and employement forms."](../images/7b1d8f47-9c34-441e-af6a-3af4a8c65533.PNG)
  
 
-    
-    
-    
-     **Tip**  If the workflow begins but never completes, and the email is not sent, try ending the debugging session and trying F5 again a few times before you conclude there is something wrong in your code. Sometimes the problem is in SharePoint Online. If you are still having problems, try adding a content type called  **ListFieldsContentType**, if there isn't one already, to the  **ContentTypes** section of the schema.xml file. The following is an example of the markup. `<ContentType ID="0x0100781dd48170b94fdc9706313c82b3d04c" Name="ListFieldsContentType" Hidden="TRUE">`
+> [!Tip]
+> If the workflow begins but never completes, and the email is not sent, try ending the debugging session and trying F5 again a few times before you conclude there is something wrong in your code. Sometimes the problem is in SharePoint Online. If you are still having problems, try adding a content type called  **ListFieldsContentType**, if there isn't one already, to the  **ContentTypes** section of the schema.xml file. The following is an example of the markup. `<ContentType ID="0x0100781dd48170b94fdc9706313c82b3d04c" Name="ListFieldsContentType" Hidden="TRUE">`
  
  `</ContentType>`Then copy the whole of the  **FieldRefs** section of the **NewEmployee** content type into this new content type.Save the project, retract, and try F5 again.
 4. To end the debugging session, close the browser window or stop debugging in Visual Studio. Each time that you press F5, Visual Studio will retract the previous version of the add-in and install the latest one.
@@ -268,7 +273,7 @@ The workflow sends an email to notify an HR staffer that the new employee has fi
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add a custom page and style to the SharePoint Add-in:  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in).
+In the next article in this series, you'll add a custom page and style to the SharePoint Add-in:  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md
index 12f7da924c..ff5d0f44aa 100644
--- a/docs/sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md
@@ -1,17 +1,24 @@
+---
+title: Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in
 Customize the rendering and validation of controls in SharePoint Add-ins pages.
  
-**Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+**Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
-This is the eighth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the eighth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
--  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in)
--  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
+-  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md)
+-  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md)
 
 **Note**  If you have been working through this series about SharePoint-hosted add-ins, then you have a Visual Studio solution that you can use to continue with this topic. You can also download the repository at  [SharePoint_SP-hosted_Add-Ins_Tutorials](https://github.com/OfficeDev/SharePoint_SP-hosted_Add-Ins_Tutorials) and open the BeforeClientRenderedControl.sln file.
  
@@ -125,7 +132,7 @@ The start tag for the  **Field** element will now look like the following.
     
 **List with custom client-side rendering**
 
-![New employees in Seattle list with Orientation Stage values of "Not started" in red and values of "Completed" in green. Other values in black.](../../images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG)
+![New employees in Seattle list with Orientation Stage values of "Not started" in red and values of "Completed" in green. Other values in black.](../images/dc8e2b7d-1747-4b65-aab4-6fc93c6867d4.PNG)
   
 - To end the debugging session, close the browser window or stop debugging in Visual Studio. Each time that you press F5, Visual Studio will retract the previous version of the add-in and install the latest one.
     
@@ -134,5 +141,5 @@ The start tag for the  **Field** element will now look like the following.
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add a custom menu item and custom button to the ribbon in the SharePoint Add-in:  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in).
+In the next article in this series, you'll add a custom menu item and custom button to the ribbon in the SharePoint Add-in:  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md).
  
diff --git a/docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md b/docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
index 7e10ae8dee..0aa189065f 100644
--- a/docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
+++ b/docs/sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
@@ -1,17 +1,24 @@
+---
+title: Add custom columns to a SharePoint-hostedSharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add custom columns to a SharePoint-hostedSharePoint Add-in
 Learn how to include custom columns in an SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the third in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the pervious articles in this series:
+This is the third in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the pervious articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
 
@@ -116,7 +123,7 @@ In this article we get back to coding by adding some site columns to the Employe
 
  
 
-  ![New Employee in Seattle list with callout button and Create View item highlighted as step one. Then arrow to Create View page with Settings breadcrumb highlighted.](../../images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png)
+  ![New Employee in Seattle list with callout button and Create View item highlighted as step one. Then arrow to Create View page with Settings breadcrumb highlighted.](../images/6c119cae-adf8-42ff-9890-f3aa1e11719d.png)
  
 
     
@@ -128,7 +135,7 @@ In this article we get back to coding by adding some site columns to the Employe
 
  
 
-  ![The list instance settings page with the link for Add Columns from Site Columns highlighted.](../../images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png)
+  ![The list instance settings page with the link for Add Columns from Site Columns highlighted.](../images/a8698b77-b9d2-40f6-89f6-ccc3c6e06073.png)
  
 
     
@@ -140,7 +147,7 @@ In this article we get back to coding by adding some site columns to the Employe
 
  
 
-  ![The SharePoint column selection control, with Employee Orientation selected in the drop down labelled Select site columns.](../../images/3b33c622-c52a-45fd-8ea1-d7f307539753.png)
+  ![The SharePoint column selection control, with Employee Orientation selected in the drop down labelled Select site columns.](../images/3b33c622-c52a-45fd-8ea1-d7f307539753.png)
  
 
     
@@ -158,7 +165,7 @@ In this article we get back to coding by adding some site columns to the Employe
 
  
 
-  ![The list with the new Division and Orientation Stage columns.](../../images/d4e17424-c06b-4635-aab8-4912cee5fe35.png)
+  ![The list with the new Division and Orientation Stage columns.](../images/d4e17424-c06b-4635-aab8-4912cee5fe35.png)
  
 
     
@@ -174,7 +181,7 @@ In this article we get back to coding by adding some site columns to the Employe
 ## 
 <a name="Nextsteps"> </a>
 
-You don't really want your users to have to manually add the custom columns to the list, so in the next article in this series, you'll create a custom content type that includes the custom columns and is automatically associated with the New Employees list template:  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in). 
+You don't really want your users to have to manually add the custom columns to the list, so in the next article in this series, you'll create a custom content type that includes the custom columns and is automatically associated with the New Employees list template:  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md). 
  
 
  
diff --git a/docs/sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in.md b/docs/sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in.md
index a922b48870..2f80e70910 100644
--- a/docs/sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in.md
@@ -1,32 +1,39 @@
+---
+title: Add first-run logic to the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add first-run logic to the provider-hosted add-in
 Learn how to include "first run" code in a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the eighth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the eighth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
--  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+-  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
     
  
--  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in)
+-  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in.md)
     
  
--  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in)
+-  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in.md)
     
  
 
@@ -138,7 +145,7 @@ internal static Version localVersion;
 
 1. The SharePoint host web needs to tell the remote web application what version of the add-in it has installed. We'll use a query parameter to do this. Open the AppManifest.xml file in the  **ChainStore** project. In the designer you'll see the placeholder **{StandardTokens}** as the value of the **Query string** box. Add the string "&amp;SPAddInVersion=1.0.0.0" to the end. The manifest designer should look similar to the following.  *Notice that the version number you pass in the query string has to match the value in the  **Version** box of the designer.*  (If you ever update the add-in, one of your tasks is to raise these two values and keep them the same.)
     
-  ![The General tab of the manifest designer. The Version box has the value one zero zero zero. The Query string box says "{StandardTokens}&amp;SPAddInVersion=1.0.0.0"](../../images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG)
+  ![The General tab of the manifest designer. The Version box has the value one zero zero zero. The Query string box says "{StandardTokens}&amp;SPAddInVersion=1.0.0.0"](../images/db71c411-10c5-43d8-bb5e-3388d2f6f7bc.PNG)
  
 
  
@@ -359,10 +366,10 @@ Since the add-in is now adding a list to the host web, not just items to an exis
  
 4. Navigate to the  **Site Contents** page. The **Local Employees** list is present because your first-run logic added it.
     
-     **Note**  If the list is not there or you have other indications that the first-run code is not executing, it may be that the  **Tenants** table is not being reverted to an empty state when you press F5. The most common cause of this is that the **ChainCorporateDB** project is no longer set as a startup project in Visual Studio. See the note near the top of this article for how to fix this. Also be sure that you've configured the database to be rebuilt as described in [Configure Visual Studio to rebuild the corporate database with each debugging session](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel#Rebuild).
+     **Note**  If the list is not there or you have other indications that the first-run code is not executing, it may be that the  **Tenants** table is not being reverted to an empty state when you press F5. The most common cause of this is that the **ChainCorporateDB** project is no longer set as a startup project in Visual Studio. See the note near the top of this article for how to fix this. Also be sure that you've configured the database to be rebuilt as described in [Configure Visual Studio to rebuild the corporate database with each debugging session](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md#Rebuild).
 5. Open the list and add an item. Note that on the new item form, the  **Added to Corporate DB** field is no longer present, so it cannot be manually set. This is true of the edit item form as well.
     
-  ![The new item form for the Local Employees list. The "Added to Corporate DB" field is no longer on the form. Only the name field and buttons for OK and Cancel.](../../images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG)
+  ![The new item form for the Local Employees list. The "Added to Corporate DB" field is no longer on the form. Only the name field and buttons for OK and Cancel.](../images/3fdc6752-4184-4928-9423-0bc7c0206c62.PNG)
  
 
  
@@ -376,7 +383,7 @@ Since the add-in is now adding a list to the host web, not just items to an exis
  
 8. On the  **Accounts** page, press the **Show Add-in Version** button. The version shows as **1.0.0.0** because the first-run logic changed it.
     
-  ![The Account settings page with the version number of 1.0.0.0.](../../images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG)
+  ![The Account settings page with the version number of 1.0.0.0.](../images/4c6d82a7-7c40-4190-b7e3-1337275e1e60.PNG)
  
 
  
@@ -392,7 +399,7 @@ Since the add-in is now adding a list to the host web, not just items to an exis
 ## 
 <a name="Nextsteps"> </a>
 
- In the next article, you'll see how to get the custom button for the **Local Employee** ribbon back into the add-in now the list is being deployed programmatically: [Programmatically deploy a custom button in the provider-hosted add-in](programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in)
+ In the next article, you'll see how to get the custom button for the **Local Employee** ribbon back into the add-in now the list is being deployed programmatically: [Programmatically deploy a custom button in the provider-hosted add-in](programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/add-in-authorization-policy-types-in-sharepoint.md b/docs/sp-add-ins/add-in-authorization-policy-types-in-sharepoint.md
index 1e2de9366c..c4b46192f7 100644
--- a/docs/sp-add-ins/add-in-authorization-policy-types-in-sharepoint.md
+++ b/docs/sp-add-ins/add-in-authorization-policy-types-in-sharepoint.md
@@ -1,11 +1,18 @@
+---
+title: Add-in authorization policy types in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add-in authorization policy types in SharePoint
 Learn about the different authorization policies for add-ins in SharePoint: add-in-only policy, user+add-in policy, and user-only policy. It also provides guidelines for using add-in-only policy.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-Before reading this article, you should first be familiar with the articles  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013) and [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins).
+Before reading this article, you should first be familiar with the articles  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md) and [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md).
  
 
 ## Get an overview of add-in authorization policies types
@@ -70,7 +77,7 @@ To be able to make add-in-only calls to SharePoint, your add-in must request per
  **Note**  SharePoint Add-ins used to be called "apps for SharePoint". To maintain backward compatibility, the app manifest schema was not changed, so the string "app" appears in may element and attribute names.
  
 
-A user installing the add-in will be prompted to approve this request. If the add-in asks for tenant-scoped permissions, then only a tenant administrator can grant use of the add-in-only policy, so only a tenant administrator can install the add-in. If the add-in does not ask for any permissions scoped higher than site collection, then a site collection administrator can install the add-in. For more information about permission scopes, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+A user installing the add-in will be prompted to approve this request. If the add-in asks for tenant-scoped permissions, then only a tenant administrator can grant use of the add-in-only policy, so only a tenant administrator can install the add-in. If the add-in does not ask for any permissions scoped higher than site collection, then a site collection administrator can install the add-in. For more information about permission scopes, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
  
@@ -139,19 +146,19 @@ Since add-in-only calls effectively elevate user privileges, you should be conse
 <a name="AR"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+-  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/add-in-permissions-in-sharepoint.md b/docs/sp-add-ins/add-in-permissions-in-sharepoint.md
index ecd2e4abfd..6252ddc908 100644
--- a/docs/sp-add-ins/add-in-permissions-in-sharepoint.md
+++ b/docs/sp-add-ins/add-in-permissions-in-sharepoint.md
@@ -1,20 +1,27 @@
+---
+title: Add-in permissions in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add-in permissions in SharePoint
 Learn about add-in permissions in SharePoint, including types of add-in permissions, permission request scopes, and managing permissions. This article also discusses the differences in add-in permission rights, user rights, and Office Store app rights.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-You should first be familiar with the topic  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins) before you read this article. 
+You should first be familiar with the topic  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md) before you read this article. 
 
 ## Get an overview of add-in permissions in SharePoint
 <a name="Perm_intro"> </a>
 
-a SharePoint Add-in requests the permissions that it needs during installation from the user who is installing it. The developer of an add-in must request, through the add-in manifest file, the permissions that the particular add-in needs to be able to run. (Device and web apps that access SharePoint, but are not installed to SharePoint websites must be granted permissions at runtime by the user who is executing the add-in. For more information, see  [Get an overview of add-ins that request access permission from SharePoint on the fly](authorization-code-oauth-flow-for-sharepoint-add-ins#Overview).) Users can grant only the permissions that they have. The user must grant all the permissions that an add-in requests or not grant any permission. Selective grants are not possible. (For add-ins that request permissions on the fly, only a user with Manage permissions to the SharePoint resources that the add-in seeks to access can run the add-in, even if the add-in is asking only for lesser permissions, such as Read.)
+a SharePoint Add-in requests the permissions that it needs during installation from the user who is installing it. The developer of an add-in must request, through the add-in manifest file, the permissions that the particular add-in needs to be able to run. (Device and web apps that access SharePoint, but are not installed to SharePoint websites must be granted permissions at runtime by the user who is executing the add-in. For more information, see  [Get an overview of add-ins that request access permission from SharePoint on the fly](authorization-code-oauth-flow-for-sharepoint-add-ins.md#Overview).) Users can grant only the permissions that they have. The user must grant all the permissions that an add-in requests or not grant any permission. Selective grants are not possible. (For add-ins that request permissions on the fly, only a user with Manage permissions to the SharePoint resources that the add-in seeks to access can run the add-in, even if the add-in is asking only for lesser permissions, such as Read.)
  
 
  
-The permissions that the add-in has been granted are also stored in the content database of the SharePoint farm or SharePoint Online tenancy. They are not stored with a secure token service, such as Microsoft Azure Access Control Service (ACS). When a user first grants an add-in permissions, SharePoint obtains information about the add-in from ACS. SharePoint then stores the basic information about the add-in in the add-in management service and the content database along with the add-in's permissions. For more information about ACS, see  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization).
+The permissions that the add-in has been granted are also stored in the content database of the SharePoint farm or SharePoint Online tenancy. They are not stored with a secure token service, such as Microsoft Azure Access Control Service (ACS). When a user first grants an add-in permissions, SharePoint obtains information about the add-in from ACS. SharePoint then stores the basic information about the add-in in the add-in management service and the content database along with the add-in's permissions. For more information about ACS, see  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md).
  
 
  
@@ -43,7 +50,7 @@ Permission request scopes indicate the location in the SharePoint hierarchy wher
 
  
 
- **Note**  A SharePoint Add-in has its own identity and is a security principal, called an add-in principal. Like users and groups, an add-in principal has certain permissions or rights. The add-in principal has full control rights to the add-in web so it only needs to request permissions to SharePoint resources in the host web or other locations outside the add-in web. For more information about add-in web, see  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape) and [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013).
+ **Note**  A SharePoint Add-in has its own identity and is a security principal, called an add-in principal. Like users and groups, an add-in principal has certain permissions or rights. The add-in principal has full control rights to the add-in web so it only needs to request permissions to SharePoint resources in the host web or other locations outside the add-in web. For more information about add-in web, see  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md) and [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md).
  
 
 SharePoint supports four different permission scopes within the content database and tenancy, as shown in Table 1. Permission scopes are named with URIs, including a "http:" prefix, but they are not URLs and they contain no placeholders. The permission scopes in this table and this article are literal strings.
@@ -380,7 +387,7 @@ SharePoint Add-ins that are installed to SharePoint are granted permissions when
  
 
  
-![Regranting permissions to an app](../../images/RegrantPermissionsToAnApp.png)
+![Regranting permissions to an app](../images/RegrantPermissionsToAnApp.png)
  
 When you are developing an add-in or troubleshooting an add-in, there may be occasions when you want to change, or regrant, the permissions of an add-in that has already been installed. You can do so with these steps:
  
@@ -409,7 +416,7 @@ An add-in's permissions for a specific scope are revoked when it is removed from
 ## Learn why add-ins cannot be hidden from users
 <a name="CannotBeHidden"> </a>
 
-Any user with browse rights to a SharePoint website can launch any SharePoint Add-in installed on the site. Whether the user can do anything with the add-in will depend on the user's other permissions and what  [authorization policy type](add-in-authorization-policy-types-in-sharepoint-2013) is being used by the add-in. If the user tries to do something with the add-in that the user does not have permission to do, and the call to SharePoint is using the user+add-in policy, then the call will fail.
+Any user with browse rights to a SharePoint website can launch any SharePoint Add-in installed on the site. Whether the user can do anything with the add-in will depend on the user's other permissions and what  [authorization policy type](add-in-authorization-policy-types-in-sharepoint.md) is being used by the add-in. If the user tries to do something with the add-in that the user does not have permission to do, and the call to SharePoint is using the user+add-in policy, then the call will fail.
  
 
  
@@ -418,18 +425,18 @@ Any user with browse rights to a SharePoint website can launch any SharePoint Ad
 <a name="Filename_AdditionalResources"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in.md b/docs/sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in.md
index 0dd6ae67a7..2f9c8db06d 100644
--- a/docs/sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in.md
@@ -1,23 +1,30 @@
+---
+title: Add SharePoint write operations to the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add SharePoint write operations to the provider-hosted add-in
 Learn how to write data to SharePoint in a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the fifthin a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the fifthin a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
 
@@ -175,7 +182,7 @@ The next improvement to the Chain Store add-in is to create new items in a list,
  
 10. Click  **new item**. The item creation form should look exactly like the following, including the two asterisks that indicate required fields.:
     
-  ![The item creation form for the Expected Shipments list. With fields for Product, Supplier, Quantity, Arrived, and "Added to Inventory". Asterisks by the titles of Product and Quantity and default value of one for Quantity.](../../images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG)
+  ![The item creation form for the Expected Shipments list. With fields for Product, Supplier, Quantity, Arrived, and "Added to Inventory". Asterisks by the titles of Product and Quantity and default value of one for Quantity.](../images/e552b5c9-8baa-4e53-9295-4d85a79d7734.PNG)
  
 
  
@@ -252,7 +259,7 @@ You might want the method to check the  `expectedShipmentsList` for nullity befo
  
 
  
-Instead, you need to use a special CSOM class called  **ConditionalScope**. The reasons for this are connected to CSOM's batching system, which was mentioned in the previous article in this series. (See  [Client-side runtime and batching](get-a-quick-overview-of-the-sharepoint-object-model#CSOMBatching)).  **ConditionalScope** and the batching system are advanced topics that are outside the scope of this getting started series, but you should see MSDN's documentation of them after you have completed this series of tutorials.
+Instead, you need to use a special CSOM class called  **ConditionalScope**. The reasons for this are connected to CSOM's batching system, which was mentioned in the previous article in this series. (See  [Client-side runtime and batching](get-a-quick-overview-of-the-sharepoint-object-model.md#CSOMBatching)).  **ConditionalScope** and the batching system are advanced topics that are outside the scope of this getting started series, but you should see MSDN's documentation of them after you have completed this series of tutorials.
  
 
  
@@ -327,7 +334,7 @@ Recall that when an add-in requests Read or Write permission with the scope of L
  
 5. From the home page of the Hong Kong store, navigate to  **Site Contents** and open the **Expected Shipments** list. There is now an item on the list corresponding to the order. The following screenshot is an example.
     
-  ![The Expected Shipments list with a single item. There Product and Supplier fields have names. The Quantity field has a number. The two Yes/No fields are both set to "No".](../../images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG)
+  ![The Expected Shipments list with a single item. There Product and Supplier fields have names. The Quantity field has a number. The two Yes/No fields are both set to "No".](../images/e4285084-d31e-4e79-a469-ddebbc7dfb18.PNG)
  
 
  
@@ -343,7 +350,7 @@ Recall that when an add-in requests Read or Write permission with the scope of L
 ## 
 <a name="Nextsteps"> </a>
 
- In the next article, you'll learn how to surface the remote Order Form as a Web Part in a SharePoint page: [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in)
+ In the next article, you'll learn how to surface the remote Order Form as a Web Part in a SharePoint page: [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/associate-a-document-library-with-an-entity.md b/docs/sp-add-ins/associate-a-document-library-with-an-entity.md
index fda7b3687e..401ae1760e 100644
--- a/docs/sp-add-ins/associate-a-document-library-with-an-entity.md
+++ b/docs/sp-add-ins/associate-a-document-library-with-an-entity.md
@@ -1,8 +1,15 @@
+---
+title: Associate a document library with an entity
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Associate a document library with an entity
 By using the document library feature in SharePoint, you can create or upload documents associated with individual items in a list or entity. For example, you might use a document library to store sales literature and product manuals for each product in a list. In a Cloud Business Add-in, you can associate a document library with an entity by creating a relationship.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -41,7 +48,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Select the Documents Library](../../images/CBADocLibrary.PNG)
+  ![Select the Documents Library](../images/CBADocLibrary.PNG)
  
 
     Figure 2 shows the document library on the SharePoint site.
@@ -51,7 +58,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Document library with custom ProductName column](../../images/CBADocLibrary2.PNG)
+  ![Document library with custom ProductName column](../images/CBADocLibrary2.PNG)
  
 
     
@@ -75,7 +82,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Create a relationship](../../images/CBARelationship.PNG)
+  ![Create a relationship](../images/CBARelationship.PNG)
  
 
  
@@ -90,7 +97,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Set the related properties](../../images/CBARelationship2.PNG)
+  ![Set the related properties](../images/CBARelationship2.PNG)
  
 
     
@@ -120,7 +127,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![The Add New Screen dialog box](../../images/CBAScreenSet.PNG)
+  ![The Add New Screen dialog box](../images/CBAScreenSet.PNG)
  
 
     The  **View** screen that is created for the entity contains a **Documents** tab with an **Add Document** button. The button displays a Popup for adding or uploading documents.
@@ -139,7 +146,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Add a new tab](../../images/CBAAddTab.PNG)
+  ![Add a new tab](../images/CBAAddTab.PNG)
  
 
  
@@ -154,7 +161,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Add the Documents entity](../../images/CBAAddDoc.PNG)
+  ![Add the Documents entity](../images/CBAAddDoc.PNG)
  
 
  
@@ -169,7 +176,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![Add a button](../../images/CBAAddButton.PNG)
+  ![Add a button](../images/CBAAddButton.PNG)
  
 
  
@@ -184,7 +191,7 @@ The process of associating a document library with an entity involves three step
 
  
 
-  ![The Add Button dialog box](../../images/CBAAddDialog.PNG)
+  ![The Add Button dialog box](../images/CBAAddDialog.PNG)
  
 
  
@@ -200,10 +207,10 @@ The process of associating a document library with an entity involves three step
 <a name="bk_addresources"> </a>
 
 
--  [Develop cloud business add-ins](develop-cloud-business-add-ins)
+-  [Develop cloud business add-ins](develop-cloud-business-add-ins.md)
     
  
--  [Incident manager: A cloud business add-in tutorial](incident-manager-a-cloud-business-add-in-tutorial)
+-  [Incident manager: A cloud business add-in tutorial](incident-manager-a-cloud-business-add-in-tutorial.md)
     
  
 
diff --git a/docs/sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md b/docs/sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md
index 110b8a1aad..dc9d4dd003 100644
--- a/docs/sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Authorization and authentication of SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Authorization and authentication of SharePoint Add-ins
 Get an overview of authentication and authorization in SharePoint, which is used to authorize requests by a SharePoint Add-in to access SharePoint resources.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 ## Add-in authentication in SharePoint
@@ -12,7 +19,7 @@ When a  *user*  signs in to SharePoint, the user's security token is validated.
  
 
  
-SharePoint Add-ins are also security principals that need to be authenticated and authorized. Add-ins can be authenticated and authorized in several different ways. For more information, see  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins). 
+SharePoint Add-ins are also security principals that need to be authenticated and authorized. Add-ins can be authenticated and authorized in several different ways. For more information, see  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins.md). 
  
 
  
@@ -28,7 +35,7 @@ SharePoint users three types of authorization policies. The user-only policy req
  
 
  
-For more information about authorization policies and how they work, see  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint-2013).
+For more information about authorization policies and how they work, see  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint.md).
  
 
  
@@ -48,7 +55,7 @@ Add-ins can also have permissions revoked or granted by SharePoint Online tenant
  
 
  
-In the add-in manifest file, a SharePoint Add-in specifies the permissions that it needs to function correctly. The permission requests specify both the rights that an add-in needs and the scope at which they need the rights. Scopes indicate where in the SharePoint hierarchy a permission request applies. SharePoint supports four different content scopes: tenancy, site collection, website, and list. There are also special scopes for performing search queries, accessing taxonomy data, social features, Microsoft Business Connectivity Services (BCS) features, and Project Server 2013 features. For more information, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+In the add-in manifest file, a SharePoint Add-in specifies the permissions that it needs to function correctly. The permission requests specify both the rights that an add-in needs and the scope at which they need the rights. Scopes indicate where in the SharePoint hierarchy a permission request applies. SharePoint supports four different content scopes: tenancy, site collection, website, and list. There are also special scopes for performing search queries, accessing taxonomy data, social features, Microsoft Business Connectivity Services (BCS) features, and Project Server 2013 features. For more information, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
  
@@ -56,11 +63,11 @@ In the add-in manifest file, a SharePoint Add-in specifies the permissions that
 ## When is OAuth used?
 <a name="FileName_uniquekeyword4"> </a>
 
-You may have already heard that OAuth 2.0 plays an important role in the authentication and authorization of SharePoint Add-ins. It does, but it is not necessarily a part of the authorization story for every SharePoint Add-in. If you plan to build a SharePoint Add-in that runs in an remote web application and communicates back to SharePoint using server-side code, you will need to use OAuth. If the remote web application is off premise, then you would use  [the low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization) in which Azure ACS is the access token issuer. If it is on premise, then you would typically use [the high-trust system](creating-sharepoint-add-ins-that-use-high-trust-authorization) in which the add-in itself and a digital certificate are the access token issuers.
+You may have already heard that OAuth 2.0 plays an important role in the authentication and authorization of SharePoint Add-ins. It does, but it is not necessarily a part of the authorization story for every SharePoint Add-in. If you plan to build a SharePoint Add-in that runs in an remote web application and communicates back to SharePoint using server-side code, you will need to use OAuth. If the remote web application is off premise, then you would use  [the low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization.md) in which Azure ACS is the access token issuer. If it is on premise, then you would typically use [the high-trust system](creating-sharepoint-add-ins-that-use-high-trust-authorization.md) in which the add-in itself and a digital certificate are the access token issuers.
  
 
  
-You would not use OAuth to make a call from JavaScript on a page in the add-in web itself or from a remote webpage using  [the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library). For more information on the cross-domain library, see  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library).
+You would not use OAuth to make a call from JavaScript on a page in the add-in web itself or from a remote webpage using  [the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library.md). For more information on the cross-domain library, see  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library.md).
  
 
  
@@ -69,12 +76,12 @@ You would not use OAuth to make a call from JavaScript on a page in the add-in w
 <a name="Filename_AdditionalResources"> </a>
 
 
--  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins)
+-  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins.md)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md b/docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md
index 5f95a85131..2c2f99f852 100644
--- a/docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Authorization Code OAuth flow for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Authorization Code OAuth flow for SharePoint Add-ins
 Learn the OAuth flow for add-ins that request permission to access SharePoint resources on the fly, and how to use the OAuthAuthorize.aspx page and the SharePoint redirect URI.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -10,7 +17,7 @@ Learn the OAuth flow for add-ins that request permission to access SharePoint re
 <a name="Overview"> </a>
 
 
- **Note**  This article assumes that you are familiar with  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization) and with the concepts and principles behind OAuth. For more information about OAuth, see [OAuth.net](http://oauth.net/) and [Web Authorization Protocol (oauth)](http://datatracker.ietf.org/doc/active/#oauth).
+ **Note**  This article assumes that you are familiar with  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md) and with the concepts and principles behind OAuth. For more information about OAuth, see [OAuth.net](http://oauth.net/) and [Web Authorization Protocol (oauth)](http://datatracker.ietf.org/doc/active/#oauth).
  
 
 In some scenarios, an add-in can request permission to access SharePoint resources on the fly; that is, an  **add-in can request permission to access SharePoint resources dynamically at runtime**, instead of at add-in installation time. This type of add-in does not have to be launched from, or even installed on, SharePoint. For example, it could be native device add-in, an add-in that is launched from any website, or an Office Add-in launched from an Office application that wants to access resources on SharePoint on the fly.
@@ -21,11 +28,11 @@ In some scenarios, an add-in can request permission to access SharePoint resourc
  **Note**  This type of add-in can only be run by users who have Manage permissions to the resources the add-in wants to access. For example, if an add-in requests only Read permission to a website, a user who has Read, but not Manage, rights to the website cannot run the add-in.
  
 
-To be able to call into SharePoint, this type of  **add-in must first be registered** through the Seller Dashboard or the appregnew.aspx page. For more information about registering add-ins via the Seller Dashboard or appregnew.aspx, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013).
+To be able to call into SharePoint, this type of  **add-in must first be registered** through the Seller Dashboard or the appregnew.aspx page. For more information about registering add-ins via the Seller Dashboard or appregnew.aspx, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md).
  
 
  
-After you've registered your add-in, it is a  *security principal*  and has an identity just as users and groups do. This identity is referred to as anadd-in principal. Like users and groups, an add-in principal has certain permissions. For more information about add-in principals, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013).
+After you've registered your add-in, it is a  *security principal*  and has an identity just as users and groups do. This identity is referred to as anadd-in principal. Like users and groups, an add-in principal has certain permissions. For more information about add-in principals, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md).
  
 
  
@@ -42,7 +49,7 @@ This section summarizes the OAuth authentication and authorization flow for a Sh
 
  
 
- **Note**  The flow  **involves a series of interactions between your add-in, SharePoint, the authorization server (which is ACS), and the end user** at runtime. So, the flow requires either SharePoint Online or a SharePoint farm that is connected to the Internet so it can communicate with ACS. SharePoint farms that are not connected to the Internet must use [the high-trust authorization system](creating-sharepoint-add-ins-that-use-high-trust-authorization).
+ **Note**  The flow  **involves a series of interactions between your add-in, SharePoint, the authorization server (which is ACS), and the end user** at runtime. So, the flow requires either SharePoint Online or a SharePoint farm that is connected to the Internet so it can communicate with ACS. SharePoint farms that are not connected to the Internet must use [the high-trust authorization system](creating-sharepoint-add-ins-that-use-high-trust-authorization.md).
  
 
 There has to be a web application or service that is hosted separately from SharePoint. Even if the add-in is a device add-in, it has to have a web application or service URL that can be registered with ACS (see above), even if the web component is used for nothing else. For simplicity, this article will assume that the add-in is a web application called Contoso.com. The application uses the SharePoint client object model (CSOM) or the SharePoint REST APIs to make calls to SharePoint. When the application first attempts to access SharePoint, SharePoint requests an authorization code from ACS that it can send to the Contoso.com application. The application then uses the authorization code to request an access token from the ACS. Once it has the access token, the Contoso.com application includes it in all its requests to SharePoint.
@@ -59,7 +66,7 @@ Suppose that Contoso provides a photo-printing service online. A user wants to p
  
 
  
-![OAuth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png)
+![OAuth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_0.png)
  
 The photo-printing application is registered, so, it has a client id, client secret, redirect URI. The redirect URI that Contoso provided when it registered the add-in is  `https://contoso.com/RedirectAccept.aspx`. The client id and client secret information are stored included in the photo-printing application's web.config file. The following is an example of how the client id and client secret are entered in the web.config file.
  
@@ -91,18 +98,18 @@ The following are the steps in the Authentication Code Flow.
 
 |**Step**||**Description**|
 |:-----|:-----|:-----|
-|**1**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png)|**Client opens an application and then directs it to a SharePoint site for data.**A user browses to the Contoso photo-printing website, where the UI indicates that the user can print photos that are kept in any SharePoint Online site. Inn this example the URL is  `https://contoso.com/print/home.aspx`.The photo-printing add-in asks the user to enter the URL of the photo collection. The user enters a URL pointing to the SharePoint Online site:  `https://fabrikam.sharepoint.com/`.|
-|**2**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png)|**The add-in redirects to the SharePoint site authorization URL.**When the user clicks the button to get the photos, the Contoso photo-printing add-in redirects the browser to  `https://fabrikam.sharepoint.com/`. This redirect is a HTTP 302 Redirect Response.If you're using Microsoft .NET,  **Response.Redirect** is one of several ways you can do the redirect from your code. Using the TokenHelper.cs (or .vb) file in your project, your code can call the overloaded **GetAuthorizationUrl** method (using the overload with three arguments). This method constructs the OAuthAuthorize.aspx redirect URL for you. Or, your code can manually construct the URL.For example, if you choose to call the  **GetAuthorizationUrl** method to construct the OAuthAuthorize.aspx redirect URL for you, using the TokenHelper.cs (or .vb) in your project, the code is as follows: `Response.Redirect(TokenHelper.GetAuthorizationUrl(`  `sharePointSiteUrl.ToString(),`  `"Web.Read List.Write",`  `"https://contoso.com/RedirectAccept.aspx"));`If you look at the three-parameter overload of the  **GetAuthorizationUrl** method in TokenHelper.cs (or .vb), you see that the second parameter is a permission scope parameter, which is a space-delimited list of permissions the add-in requests in shorthand format. For more information about permission scopes, see [Understand permission scope aliases and the use of the OAuthAuthorize.aspx page](#Scope). The third parameter must be the same redirect URI that is used when the add-in is registered. For more information about registration, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013). You will also see that the returned string is a URL including query string parameters.If you prefer, you can manually construct the OAuthAuthorize.aspx redirect URL. For example, the URL that the Contoso photo-printing add-in redirects the user to in this case is: `https://fabrikam.sharepoint.com/_layouts/15/OAuthAuthorize.aspx?client_id=client_GUID&amp;scope=app_permissions_list&amp;response_type=code&amp;redirect_uri=redirect_uri`As the example show, the Contoso photo-printing add-in sends the OAuth client Id and redirect URI to the Fabrikam site as query string parameters. The following is an example of the GET request with sample query string values. Line breaks have been added for clarity. The actual target URL is a single line. `GET /authcode HTTP/1.1`  `Host: fabrikam.sharepoint.com`   `/oauthauthorize.aspx`  `?client_id= c78d058c-7f82-44ca-a077-fba855e14d38`  `&amp;scope=list.read`  `&amp;response_type=code`  `&amp;redirect_uri= https%3A%2F%2Fcontoso%2Ecom%2Fredirectaccept.aspx` If you want a separate consent pop-up dialog, you can add the query parameter  **IsDlg=1** to the URL construct as shown here: `/oauthauthorize.aspx?IsDlg=1&amp;client_id= c78d058c-7f82-44ca-a077-fba855e14d38&amp;scope=list.read&amp;response_type=code&amp;redirect_uri= https%3A%2F%2Fcontoso%2Ecom%2Fredirectaccept.aspx`|
-|**3**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png)|**SharePoint displays the consent page so the user can grant the add-in permissions.**If the user is not already signed into the Fabrikam SharePoint Online site, the user is prompted to sign in. When the user is signed in, SharePoint renders an HTML consent page.The consent page prompts the user to grant (or deny) the Contoso photo-printing add-in the permissions that the add-in requests. In this case, the user would be granting the add-in read access to the user's picture library on Fabrikam.|
-|**4**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png)|**SharePoint requests a short-lived authorization code from ACS.**The Fabrikam SharePoint Online site asks ACS to create a short-lived (approximately 5 minutes) authorization code unique to this combination of user and add-in.ACS sends the authorization code to the Fabrikam site.|
-|**5**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png)|**The SharePoint Online site redirects to the app's registered redirect URI, passing the authorization code to the add-in.**The Fabrikam SharePoint Online site redirects the browser back to Contoso via HTTP 302 Response. The URL construct for this redirection uses the redirect URI that was specified when the photo-printing add-in was registrated. It also includes the authorization code as a query string. The redirect URL is structured like the following: `https://contoso.com/RedirectAccept.aspx?code=<authcode>`|
-|**6**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png)|**The add-in uses the authorization code to request an access token from ACS, which validates the request, invalidates the authorization code, and then sends access and refresh tokens to the add-in.**Contoso retrieves the authorization code from the query parameter, and then includes it, along with the client ID and client secret, in a request to ACS for an access token.If you are using managed code and the SharePoint CSOM, the TokenHelper.cs (or .vb) file, the method that makes the request to ACS is  **GetClientContextWithAuthorizationCode**. In this case the code looks similar to the following (where  `authCode` is a variable to which the authorization code has been assigned): `TokenHelper.GetClientContextWithAuthorizationCode(`  `"https://fabrikam.sharepoint.com/",`  `"00000003-0000-0ff1-ce00-000000000000",`  `authCode,`  `"1ee82b34-7c1b-471b-b27e-ff272accd564",`  `new Uri(Request.Url.GetLeftPart(UriPartial.Path)));` If you look at the TokenHelper.cs (or .vb) file, the second parameter of the  **GetClientContextWithAuthorizationCode** method is the `targetPrincipalName`. This value is always the constant " `00000003-0000-0ff1-ce00-000000000000`" in an add-in that is accessing SharePoint. You will also see, if you trace the call hierarchy from  **GetClientContextWithAuthorizationCode**, that it obtains the client ID and secret from the web.config file.ACS receives Contoso's request and validates the client ID, client secret, redirect URI, and authorization code. If all are valid, the ACS invalidates the authorization code (it can be used only once) and creates a refresh token and an access token, which it returns to Contoso.The Contoso application can cache this access token for reuse on later requests. By default, access tokens are good for about 12 hours. Each access token is specific to the user account that is specified in the original request for authorization, and grants access only to the services that are specified in that request. Your add-in should store the access token securely.The Contoso application can also cache the refresh token. By default, refresh tokens are good for 6 months. The refresh token can be redeemed for a new access token from ACS whenever the access token expires. For more information about tokens, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins).|
-|**7**|![Oauth](../../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png)|**The add-in can now use the access token to request data from the SharePoint site which it can display to the user.**Contoso includes the access token to make a REST API call or CSOM request to SharePoint, passing the OAuth access token in the HTTP  **Authorization** header.SharePoint returns the information that Contoso requested. For more about how this request is made, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins).|
+|**1**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_1.png)|**Client opens an application and then directs it to a SharePoint site for data.**A user browses to the Contoso photo-printing website, where the UI indicates that the user can print photos that are kept in any SharePoint Online site. Inn this example the URL is  `https://contoso.com/print/home.aspx`.The photo-printing add-in asks the user to enter the URL of the photo collection. The user enters a URL pointing to the SharePoint Online site:  `https://fabrikam.sharepoint.com/`.|
+|**2**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_2.png)|**The add-in redirects to the SharePoint site authorization URL.**When the user clicks the button to get the photos, the Contoso photo-printing add-in redirects the browser to  `https://fabrikam.sharepoint.com/`. This redirect is a HTTP 302 Redirect Response.If you're using Microsoft .NET,  **Response.Redirect** is one of several ways you can do the redirect from your code. Using the TokenHelper.cs (or .vb) file in your project, your code can call the overloaded **GetAuthorizationUrl** method (using the overload with three arguments). This method constructs the OAuthAuthorize.aspx redirect URL for you. Or, your code can manually construct the URL.For example, if you choose to call the  **GetAuthorizationUrl** method to construct the OAuthAuthorize.aspx redirect URL for you, using the TokenHelper.cs (or .vb) in your project, the code is as follows: `Response.Redirect(TokenHelper.GetAuthorizationUrl(`  `sharePointSiteUrl.ToString(),`  `"Web.Read List.Write",`  `"https://contoso.com/RedirectAccept.aspx"));`If you look at the three-parameter overload of the  **GetAuthorizationUrl** method in TokenHelper.cs (or .vb), you see that the second parameter is a permission scope parameter, which is a space-delimited list of permissions the add-in requests in shorthand format. For more information about permission scopes, see [Understand permission scope aliases and the use of the OAuthAuthorize.aspx page](#Scope). The third parameter must be the same redirect URI that is used when the add-in is registered. For more information about registration, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md). You will also see that the returned string is a URL including query string parameters.If you prefer, you can manually construct the OAuthAuthorize.aspx redirect URL. For example, the URL that the Contoso photo-printing add-in redirects the user to in this case is: `https://fabrikam.sharepoint.com/_layouts/15/OAuthAuthorize.aspx?client_id=client_GUID&amp;scope=app_permissions_list&amp;response_type=code&amp;redirect_uri=redirect_uri`As the example show, the Contoso photo-printing add-in sends the OAuth client Id and redirect URI to the Fabrikam site as query string parameters. The following is an example of the GET request with sample query string values. Line breaks have been added for clarity. The actual target URL is a single line. `GET /authcode HTTP/1.1`  `Host: fabrikam.sharepoint.com`   `/oauthauthorize.aspx`  `?client_id= c78d058c-7f82-44ca-a077-fba855e14d38`  `&amp;scope=list.read`  `&amp;response_type=code`  `&amp;redirect_uri= https%3A%2F%2Fcontoso%2Ecom%2Fredirectaccept.aspx` If you want a separate consent pop-up dialog, you can add the query parameter  **IsDlg=1** to the URL construct as shown here: `/oauthauthorize.aspx?IsDlg=1&amp;client_id= c78d058c-7f82-44ca-a077-fba855e14d38&amp;scope=list.read&amp;response_type=code&amp;redirect_uri= https%3A%2F%2Fcontoso%2Ecom%2Fredirectaccept.aspx`|
+|**3**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_3.png)|**SharePoint displays the consent page so the user can grant the add-in permissions.**If the user is not already signed into the Fabrikam SharePoint Online site, the user is prompted to sign in. When the user is signed in, SharePoint renders an HTML consent page.The consent page prompts the user to grant (or deny) the Contoso photo-printing add-in the permissions that the add-in requests. In this case, the user would be granting the add-in read access to the user's picture library on Fabrikam.|
+|**4**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_4.png)|**SharePoint requests a short-lived authorization code from ACS.**The Fabrikam SharePoint Online site asks ACS to create a short-lived (approximately 5 minutes) authorization code unique to this combination of user and add-in.ACS sends the authorization code to the Fabrikam site.|
+|**5**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_5.png)|**The SharePoint Online site redirects to the app's registered redirect URI, passing the authorization code to the add-in.**The Fabrikam SharePoint Online site redirects the browser back to Contoso via HTTP 302 Response. The URL construct for this redirection uses the redirect URI that was specified when the photo-printing add-in was registrated. It also includes the authorization code as a query string. The redirect URL is structured like the following: `https://contoso.com/RedirectAccept.aspx?code=<authcode>`|
+|**6**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_6.png)|**The add-in uses the authorization code to request an access token from ACS, which validates the request, invalidates the authorization code, and then sends access and refresh tokens to the add-in.**Contoso retrieves the authorization code from the query parameter, and then includes it, along with the client ID and client secret, in a request to ACS for an access token.If you are using managed code and the SharePoint CSOM, the TokenHelper.cs (or .vb) file, the method that makes the request to ACS is  **GetClientContextWithAuthorizationCode**. In this case the code looks similar to the following (where  `authCode` is a variable to which the authorization code has been assigned): `TokenHelper.GetClientContextWithAuthorizationCode(`  `"https://fabrikam.sharepoint.com/",`  `"00000003-0000-0ff1-ce00-000000000000",`  `authCode,`  `"1ee82b34-7c1b-471b-b27e-ff272accd564",`  `new Uri(Request.Url.GetLeftPart(UriPartial.Path)));` If you look at the TokenHelper.cs (or .vb) file, the second parameter of the  **GetClientContextWithAuthorizationCode** method is the `targetPrincipalName`. This value is always the constant " `00000003-0000-0ff1-ce00-000000000000`" in an add-in that is accessing SharePoint. You will also see, if you trace the call hierarchy from  **GetClientContextWithAuthorizationCode**, that it obtains the client ID and secret from the web.config file.ACS receives Contoso's request and validates the client ID, client secret, redirect URI, and authorization code. If all are valid, the ACS invalidates the authorization code (it can be used only once) and creates a refresh token and an access token, which it returns to Contoso.The Contoso application can cache this access token for reuse on later requests. By default, access tokens are good for about 12 hours. Each access token is specific to the user account that is specified in the original request for authorization, and grants access only to the services that are specified in that request. Your add-in should store the access token securely.The Contoso application can also cache the refresh token. By default, refresh tokens are good for 6 months. The refresh token can be redeemed for a new access token from ACS whenever the access token expires. For more information about tokens, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md).|
+|**7**|![Oauth](../images/SharePoint_appsForSharePoint_3LeggedOauthFlow_7.png)|**The add-in can now use the access token to request data from the SharePoint site which it can display to the user.**Contoso includes the access token to make a REST API call or CSOM request to SharePoint, passing the OAuth access token in the HTTP  **Authorization** header.SharePoint returns the information that Contoso requested. For more about how this request is made, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md).|
 
 ## Understand permission scope aliases and the use of the OAuthAuthorize.aspx page
 <a name="Scope"> </a>
 
-This section assumes you are familiar with the article  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013). Table 1 shows the same add-in permission request scope URIs that are shown in that article, except it has one additional column ( **Scope Alias** ) and the FullControl right is not available in the **Available Rights** column, because an add-in that request permission to access SharePoint resources on the fly can't request full control right.
+This section assumes you are familiar with the article  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md). Table 1 shows the same add-in permission request scope URIs that are shown in that article, except it has one additional column ( **Scope Alias** ) and the FullControl right is not available in the **Available Rights** column, because an add-in that request permission to access SharePoint resources on the fly can't request full control right.
  
 
  
@@ -137,7 +144,7 @@ If you are not using managed code, the scope aliases are used in the scope field
 
  
 
- **Note**  For a description of the scopes, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+ **Note**  For a description of the scopes, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
 
@@ -328,7 +335,7 @@ namespace DynamicAppPermissionRequest
 }
 ```
 
-The following is a code example for a token cache module that the previous sample code calls. It uses cookies as the cache. There are other caching options. For more information, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins).
+The following is a code example for a token cache module that the previous sample code calls. It uses cookies as the cache. There are other caching options. For more information, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md).
  
 
  
@@ -411,18 +418,18 @@ namespace DynamicAppPermissionRequest
 <a name="AR"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization)
+-  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md b/docs/sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md
index 24d991cccd..437901fd5e 100644
--- a/docs/sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md
+++ b/docs/sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Choose patterns for developing and hosting your SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Choose patterns for developing and hosting your SharePoint Add-in
 Learn about the different ways that you can host the components of SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 The SharePoint add-in model introduces a wide range of hosting and development patterns. Some of these patterns can be used in combination with each other. For example, your add-ins can mix SharePoint-hosted and remotely hosted components. The most useful way to determine which patterns you'll want to use is to start with your own requirements, technologies, and goals and match them with the options and possibilities that are enabled by SharePoint Add-ins.
@@ -19,7 +26,7 @@ SharePoint Add-ins widen the range of possible programming languages and technol
 ### SharePoint-hosted add-ins
 <a name="SPHosted"> </a>
 
-Start with the simplest option: SharePoint-hosted add-ins, or add-ins where all components are hosted on either an on-premises or Office 365 SharePoint farm. SharePoint-hosted add-ins are installed on a SharePoint website, called the host web. They have their resources hosted on an isolated subsite of a host web, called the add-in web. It's important to know  [the difference between host webs and add-in webs](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013). Figure 1 illustrates the basic architecture of a SharePoint-hosted add-in.
+Start with the simplest option: SharePoint-hosted add-ins, or add-ins where all components are hosted on either an on-premises or Office 365 SharePoint farm. SharePoint-hosted add-ins are installed on a SharePoint website, called the host web. They have their resources hosted on an isolated subsite of a host web, called the add-in web. It's important to know  [the difference between host webs and add-in webs](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md). Figure 1 illustrates the basic architecture of a SharePoint-hosted add-in.
  
 
  
@@ -29,7 +36,7 @@ Start with the simplest option: SharePoint-hosted add-ins, or add-ins where all
  
 
  
-![The components of a SharePoint-hosted app are hosted on the appweb of a SharePoint farm.](../../images/SP15_hosting_SPhosted.gif)
+![The components of a SharePoint-hosted app are hosted on the appweb of a SharePoint farm.](../images/SP15_hosting_SPhosted.gif)
  
 You can combine a SharePoint-hosted add-in with add-ins that have remotely hosted components, but any add-in or portion of an add-in that runs on an add-in web has the following set of requirements for three key components: where the add-in is hosted, how the add-in gets authorization, and what language it can use.
  
@@ -42,7 +49,7 @@ You can combine a SharePoint-hosted add-in with add-ins that have remotely hoste
 |Where the add-in components are hosted|In the isolated add-in domain of your SharePoint farm|
 |How the add-in gets authorized|The privileges of the signed-in user|
 |What language the add-in can use|JavaScript (with the SharePoint JSOM library) + HTML|
-This pattern is the easiest to deploy, and you can use the  [Create a basic SharePoint-hosted add-in by using Napa Office 365 Development Tools](create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-tools). You'll want to consider the following before deciding to create a SharePoint-hosted add-in.
+This pattern is the easiest to deploy, and you can use the  [Create a basic SharePoint-hosted add-in by using Napa Office 365 Development Tools](create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-too.md). You'll want to consider the following before deciding to create a SharePoint-hosted add-in.
  
 
  
@@ -52,7 +59,7 @@ This pattern is the easiest to deploy, and you can use the  [Create a basic Shar
 |:-----|:-----|
 |Reuse common SharePoint items, like lists and Web Parts.|You can use only JavaScript in the add-in—you can't use any server-side code.|
 |Relatively easy to create and deploy, so they are good for small team productivity add-ins and business process automation, with lower complexity business rules.|Your add-in has only the authorization privileges of the signed-in user.|
- [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+ [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
  
 
  
@@ -70,7 +77,7 @@ Provider-hosted SharePoint Add-ins include components that are deployed and host
  
 
  
-![The components of a provider-hosted app are hosted on any web server or hosting service.](../../images/SP15_hosting_Provider.gif)
+![The components of a provider-hosted app are hosted on any web server or hosting service.](../images/SP15_hosting_Provider.gif)
  
 The following table shows how the requirements for hosting location, add-in authorization, and languages are much less fixed for provider-hosted add-ins than they are for SharePoint-hosted add-ins.
  
@@ -92,8 +99,8 @@ A provider-hosted add-in interacts with a SharePoint site but also uses resource
 |**Get these benefits**|**But consider this**|
 |:-----|:-----|
 |Host the add-in on Microsoft Azure or any remote web platform, including non-Microsoft platforms. |You are responsible for creating the installation, upgrade, and uninstallation logic of the remote components.|
-|Use one of the SharePoint client object models, the JavaScript cross-domain library, or the SharePoint  [REST/OData-based web service](http://msdn.microsoft.com/magazine/dn198245.aspx) to interact with SharePoint.|Each way of interacting with SharePoint has  [corresponding options for approaches to data access](secure-data-access-and-client-object-models-for-sharepoint-add-ins).|
-|Gain authorization to SharePoint data using one of  [the three authorization systems](three-authorization-systems-for-sharepoint-add-ins).|You need to decide between OAuth and the cross-domain library to authorize your add-in's access to SharePoint.|
+|Use one of the SharePoint client object models, the JavaScript cross-domain library, or the SharePoint  [REST/OData-based web service](http://msdn.microsoft.com/magazine/dn198245.aspx) to interact with SharePoint.|Each way of interacting with SharePoint has  [corresponding options for approaches to data access](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md).|
+|Gain authorization to SharePoint data using one of  [the three authorization systems](three-authorization-systems-for-sharepoint-add-ins.md).|You need to decide between OAuth and the cross-domain library to authorize your add-in's access to SharePoint.|
 
 ## Match your hosting pattern with your development goals
 <a name="MatchPattern"> </a>
@@ -124,22 +131,22 @@ One of the most important questions you need to ask when considering provider-ho
  
 
  
-The  [cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library) lets you interact with more than one domain from the remote components of your add-in through a proxy. If client-side code and the permissions of a user who is signed in to SharePoint are sufficient, the cross-domain library is a good option. The cross-domain library is also convenient whenever you are making remote calls through a firewall.
+The  [cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md) lets you interact with more than one domain from the remote components of your add-in through a proxy. If client-side code and the permissions of a user who is signed in to SharePoint are sufficient, the cross-domain library is a good option. The cross-domain library is also convenient whenever you are making remote calls through a firewall.
  
 
  
-OAuth is an open protocol for authorization that enables secure authorization from client applications (desktop, web, and mobile applications) in an easily manageable way. If you plan to build a SharePoint Add-in that runs in a remote web application and communicates back to SharePoint, you will often need to use OAuth. OAuth is required whenever you are calling into SharePoint from a remotely hosted web application that can't use client-side code (HTML + JavaScript) exclusively.  [Learn more about how OAuth works in SharePoint Add-ins.](creating-sharepoint-add-ins-that-use-low-trust-authorization)
+OAuth is an open protocol for authorization that enables secure authorization from client applications (desktop, web, and mobile applications) in an easily manageable way. If you plan to build a SharePoint Add-in that runs in a remote web application and communicates back to SharePoint, you will often need to use OAuth. OAuth is required whenever you are calling into SharePoint from a remotely hosted web application that can't use client-side code (HTML + JavaScript) exclusively.  [Learn more about how OAuth works in SharePoint Add-ins.](creating-sharepoint-add-ins-that-use-low-trust-authorization.md)
  
 
  
- [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins) and [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins) explain the choice between OAuth and the cross-domain library more thoroughly.
+ [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md) and [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins.md) explain the choice between OAuth and the cross-domain library more thoroughly.
  
 
  
 
 ### OAuth with on-premises SharePoint farms
 
-If you are using an on-premises deployment of SharePoint, you can use OAuth, but you will have to choose between creating high-trust add-ins and using an Office 365 tenancy. Office 365 uses Microsoft Azure Access Control Service (ACS) as the trust broker, and if you do not have access to an Office 365 tenancy, you'll need to use  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins), which uses certificates to establish trust between your add-in and SharePoint. You can add high trust add-ins to the add-in catalog of your SharePoint farm, but you can't sell them in the Office Store. If you do have access to an Office 365 tenancy, you can link it to your on-premises installation of SharePoint and  [use ACS as the trust broker for add-ins that are installed to your on-premises SharePoint](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on-premises-sharepoint-site).
+If you are using an on-premises deployment of SharePoint, you can use OAuth, but you will have to choose between creating high-trust add-ins and using an Office 365 tenancy. Office 365 uses Microsoft Azure Access Control Service (ACS) as the trust broker, and if you do not have access to an Office 365 tenancy, you'll need to use  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md), which uses certificates to establish trust between your add-in and SharePoint. You can add high trust add-ins to the add-in catalog of your SharePoint farm, but you can't sell them in the Office Store. If you do have access to an Office 365 tenancy, you can link it to your on-premises installation of SharePoint and  [use ACS as the trust broker for add-ins that are installed to your on-premises SharePoint](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md).
  
 
  
@@ -159,7 +166,7 @@ The following table lists all of the possible patterns for hosting both the Shar
 ## Combine provider hosting and SharePoint hosting
 <a name="Combined"> </a>
 
-You can also build add-ins that include both SharePoint-hosted and cloud-hosted components. For example, you can create a  [cloud-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-content-type). If you choose to use this architecture, your design and approach must account for security limitations that are built into the model. You can use only JavaScript in the code components that are hosted by SharePoint, and the remotely hosted components must use either OAuth or the cross-domain library to interact with the SharePoint website. When considering this approach, make sure that you understand how  [add-in authorization works in SharePoint](authorization-and-authentication-of-sharepoint-add-ins). Figure 4 shows you how this architecture works if you use Microsoft Azure to host the remote components of your add-in, and you use OAuth.
+You can also build add-ins that include both SharePoint-hosted and cloud-hosted components. For example, you can create a  [cloud-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md). If you choose to use this architecture, your design and approach must account for security limitations that are built into the model. You can use only JavaScript in the code components that are hosted by SharePoint, and the remotely hosted components must use either OAuth or the cross-domain library to interact with the SharePoint website. When considering this approach, make sure that you understand how  [add-in authorization works in SharePoint](authorization-and-authentication-of-sharepoint-add-ins.md). Figure 4 shows you how this architecture works if you use Microsoft Azure to host the remote components of your add-in, and you use OAuth.
  
 
  
@@ -169,9 +176,9 @@ You can also build add-ins that include both SharePoint-hosted and cloud-hosted
  
 
  
-![Server to server communication restrictions](../../images/SP15HelloWorldSPApp_Fig01.png)
+![Server to server communication restrictions](../images/SP15HelloWorldSPApp_Fig01.png)
  
- [Learn how to create an add-in that combines cloud hosting and SharePoint hosting.](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-content-type)
+ [Learn how to create an add-in that combines cloud hosting and SharePoint hosting.](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md)
  
 
  
@@ -237,34 +244,34 @@ For more information, see the following resources:
 
  
 
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)
+-  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+-  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
     
  
--  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on-premises-sharepoint-site)
+-  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md)
     
  
 -  [SharePoint Add-ins compared with SharePoint solutions](http://msdn.microsoft.com/library/0e9efadb-aaf2-4c0d-afd5-d6cf25c4e7a8%28Office.15%29.aspx)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-content-type)
+-  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md)
     
  
 
diff --git a/docs/sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md b/docs/sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md
index 11aad00127..452d83123a 100644
--- a/docs/sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md
+++ b/docs/sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md
@@ -1,12 +1,19 @@
+---
+title: Complete basic operations using JavaScript library code in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Complete basic operations using JavaScript library code in SharePoint
 Learn how to write code to perform basic operations using the JavaScript client object model in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Note**  For a "Hello World" level sample SharePoint Add-in that uses the JavaScript library, see  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data).
+ **Note**  For a "Hello World" level sample SharePoint Add-in that uses the JavaScript library, see  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md).
  
 
 
@@ -42,10 +49,10 @@ This article shows how to perform basic operations using the JavaScript object m
 
  
 
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
 -  [Build Windows Phone apps that access SharePoint](http://msdn.microsoft.com/library/36681335-f772-4499-8445-f94481bc18e7%28Office.15%29.aspx)
@@ -766,7 +773,7 @@ You can manipulate files by using the JavaScript object model. The following sec
 
  
 
- **Note**  You can only work with files up to 1.5 MB by using the JavaScript object model. To upload larger files, use REST (Representational State Transfer). For more information, see  [](complete-basic-operations-using-sharepoint-2013-rest-endpoints#LargeFiles).
+ **Note**  You can only work with files up to 1.5 MB by using the JavaScript object model. To upload larger files, use REST (Representational State Transfer). For more information, see  [](complete-basic-operations-using-sharepoint-rest-endpoints#LargeFiles.md).
  
 
 
@@ -1239,7 +1246,7 @@ function onQueryFailed(sender, args) {
 ## Access objects in the host web
 <a name="BasicOps_AccessHostweb"> </a>
 
-While developing your add-in, you might need to access the host web to interact with items in it. Use the  **AppContextSite** object to reference the host web or other SharePoint sites, as shown in the following example. For a full code sample, see [Get the host web title using the cross-domain library (JSOM)](http://code.msdn.microsoft.com/office/SharePoint-2013-Get-the-563f2a3d).
+While developing your add-in, you might need to access the host web to interact with items in it. Use the  **AppContextSite** object to reference the host web or other SharePoint sites, as shown in the following example. For a full code sample, see [Get the host web title using the cross-domain library (JSOM)](http://code.msdn.microsoft.com/office/SharePoint-Get-the-563f2a3d).
  
 
  
@@ -1283,7 +1290,7 @@ function execCrossDomainRequest(appweburl, hostweburl) {
 }
 ```
 
-The previous example uses the cross-domain library in SharePoint to access the host web. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+The previous example uses the cross-domain library in SharePoint to access the host web. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
  
 
  
@@ -1292,19 +1299,19 @@ The previous example uses the cross-domain library in SharePoint to access the h
 <a name="BasicOps_AddRes"> </a>
 
 
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
 
diff --git a/docs/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md b/docs/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md
index e5931e79fe..7d1bc115ac 100644
--- a/docs/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md
+++ b/docs/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md
@@ -1,8 +1,15 @@
+---
+title: Complete basic operations using SharePoint client library code
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Complete basic operations using SharePoint client library code
 Learn how to write code to perform basic operations with the SharePoint .NET Framework client object model (CSOM).
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -33,7 +40,7 @@ For more details about the sets of APIs available on the SharePoint platform, se
  
 
  
-This article is shows how to perform basic operations using the .NET Framework object model, which is available as a redistributable package on the Microsoft Download Center. Search for "SharePoint Server 2013 Client Components SDK" or "SharePoint Online Client Components SDK". For information about how to use the other client APIs see,  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013),  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints),  [Build Windows Phone apps that access SharePoint](http://msdn.microsoft.com/library/36681335-f772-4499-8445-f94481bc18e7%28Office.15%29.aspx), and  [Using the Silverlight Object Model](http://msdn.microsoft.com/library/cea7829d-f360-4052-8b76-91d90bcefd2a%28Office.15%29.aspx) in the SharePoint 2010 SDK.
+This article is shows how to perform basic operations using the .NET Framework object model, which is available as a redistributable package on the Microsoft Download Center. Search for "SharePoint Server 2013 Client Components SDK" or "SharePoint Online Client Components SDK". For information about how to use the other client APIs see,  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md),  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md),  [Build Windows Phone apps that access SharePoint](http://msdn.microsoft.com/library/36681335-f772-4499-8445-f94481bc18e7%28Office.15%29.aspx), and  [Using the Silverlight Object Model](http://msdn.microsoft.com/library/cea7829d-f360-4052-8b76-91d90bcefd2a%28Office.15%29.aspx) in the SharePoint 2010 SDK.
  
 
  
@@ -1039,10 +1046,10 @@ context.ExecuteQuery();
 <a name="bk_addresources"> </a>
 
 
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
 -  [Build sites for SharePoint](http://msdn.microsoft.com/library/3b372a63-7cdf-462a-abb4-750e611e967d%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md b/docs/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md
index 66d8144684..5df2d37466 100644
--- a/docs/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md
+++ b/docs/sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md
@@ -1,23 +1,30 @@
+---
+title: Complete basic operations using SharePoint REST endpoints
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Complete basic operations using SharePoint REST endpoints
 Learn how to perform basic create, read, update, and delete (CRUD) operations with the SharePoint REST interface.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Developing with the SharePoint client APIs and REST
 <a name="ClientAPIs"> </a>
 
-You can perform basic create, read, update, and delete (CRUD) operations by using the Representational State Transfer (REST) interface provided by SharePoint. The REST interface exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don't have to add references to any SharePoint libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. See  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service) for a thorough introduction to the SharePoint REST interface and its architecture.
+You can perform basic create, read, update, and delete (CRUD) operations by using the Representational State Transfer (REST) interface provided by SharePoint. The REST interface exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don't have to add references to any SharePoint libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. See  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md) for a thorough introduction to the SharePoint REST interface and its architecture.
  
 
  
- [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest) and [Working with folders and files with REST](working-with-folders-and-files-with-rest) explain in greater detail how to work with core SharePoint entities. See [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations) for a sample that shows you how to do many of these operations in the context of an ASP.NET web application written in C#.
+ [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md) and [Working with folders and files with REST](working-with-folders-and-files-with-rest.md) explain in greater detail how to work with core SharePoint entities. See [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations.md) for a sample that shows you how to do many of these operations in the context of an ASP.NET web application written in C#.
  
 
  
-For more details about the sets of APIs available on the SharePoint platform, see  [Choose the right API set in SharePoint](http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d%28Office.15%29.aspx). For information about how to use the other client APIs, see  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013),  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013), and  [Build Windows Phone apps that access SharePoint](http://msdn.microsoft.com/library/36681335-f772-4499-8445-f94481bc18e7%28Office.15%29.aspx).
+For more details about the sets of APIs available on the SharePoint platform, see  [Choose the right API set in SharePoint](http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d%28Office.15%29.aspx). For information about how to use the other client APIs, see  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md),  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md), and  [Build Windows Phone apps that access SharePoint](http://msdn.microsoft.com/library/36681335-f772-4499-8445-f94481bc18e7%28Office.15%29.aspx).
  
 
  
@@ -65,7 +72,7 @@ To read information from a REST endpoint, you must know both the URL of the endp
  
 
  
-The following C# code demonstrates how to make this  **GET** request that returns a JSON representation of all of a site's lists by using JQuery. It also assumes that you have a valid OAuth access token that is stored in the **accessToken** variable. You do not need the access token if you make this call from inside an add-in web, as you would in a SharePoint-hosted add-in. Note that you cannot obtain an access token from code that is running on a browser client. You must obtain the access token from code that is running on a server. [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins) and [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins) explain how you can obtain an access token.
+The following C# code demonstrates how to make this  **GET** request that returns a JSON representation of all of a site's lists by using JQuery. It also assumes that you have a valid OAuth access token that is stored in the **accessToken** variable. You do not need the access token if you make this call from inside an add-in web, as you would in a SharePoint-hosted add-in. Note that you cannot obtain an access token from code that is running on a browser client. You must obtain the access token from code that is running on a server. [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md) and [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md) explain how you can obtain an access token.
  
 
  
@@ -86,7 +93,7 @@ HttpWebResponse endpointResponse =
 
 ```
 
-This request would look a little different if you are writing your add-in in JavaScript but using the SharePoint cross-domain library. In this case, you don't need to provide an access token. The following code demonstrates how this request would look if you are using the cross-domain library and want to receive the OData representation of the lists as XML instead of JSON. (Because Atom is the default response format, you don't have to include an  **Accept** header.) See [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library) for more information about using the cross-domain library.
+This request would look a little different if you are writing your add-in in JavaScript but using the SharePoint cross-domain library. In this case, you don't need to provide an access token. The following code demonstrates how this request would look if you are using the cross-domain library and want to receive the OData representation of the lists as XML instead of JSON. (Because Atom is the default response format, you don't have to include an  **Accept** header.) See [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md) for more information about using the cross-domain library.
  
 
  
@@ -171,7 +178,7 @@ HttpWebResponse endpointResponse =
 
 ```
 
-If you're using the authentication and authorization flow described in  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins), you don't need to include the request digest in your requests.
+If you're using the authentication and authorization flow described in  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md), you don't need to include the request digest in your requests.
  
 
  
@@ -307,7 +314,7 @@ When you send a POST request, the request must include the form digest value in
  "X-RequestDigest": $("#__REQUESTDIGEST").val()
     
  
-- In cloud-hosted add-ins that use OAuth, first retrieve the form digest value by sending a request to the  **contextinfo** endpoint, and then add it to requests, as shown in [Writing data by using the REST interface](complete-basic-operations-using-sharepoint-2013-rest-endpoints#WritingData).
+- In cloud-hosted add-ins that use OAuth, first retrieve the form digest value by sending a request to the  **contextinfo** endpoint, and then add it to requests, as shown in [Writing data by using the REST interface](complete-basic-operations-using-sharepoint-rest-endpoints.md#WritingData).
     
  
 - In cloud-hosted add-ins that use the JavaScript cross-domain library, you don't need to specify the form digest value. By default, SP.RequestExecutor automatically handles this for you. (It also handles the content-length value.)
@@ -317,7 +324,7 @@ When you send a POST request, the request must include the form digest value in
 ### Add-ins that use OAuth must pass access tokens in requests
 <a name="OAuthTokens"> </a>
 
-Cloud-hosted add-ins use either OAuth or the cross-domain library to authorize access to SharePoint data. Add-in components with code that runs on a remote web server must use OAuth to authorize access to SharePoint data. In this case, you need to include an  **Authorization** header to send the access token. See [Reading data with the SharePoint REST interface](complete-basic-operations-using-sharepoint-2013-rest-endpoints#ReadingData) for an example that adds an authorization header to an **HTTPWebRequest** object.
+Cloud-hosted add-ins use either OAuth or the cross-domain library to authorize access to SharePoint data. Add-in components with code that runs on a remote web server must use OAuth to authorize access to SharePoint data. In this case, you need to include an  **Authorization** header to send the access token. See [Reading data with the SharePoint REST interface](complete-basic-operations-using-sharepoint-rest-endpoints.md#ReadingData) for an example that adds an authorization header to an **HTTPWebRequest** object.
  
 
  
@@ -325,7 +332,7 @@ Cloud-hosted add-ins use either OAuth or the cross-domain library to authorize a
  **Note**  Cloud-hosted add-in components that are written in JavaScript must use the  **SP.RequestExecutor** object in the cross-domain library to access to SharePoint data. Cross-domain library requests don't need to include an access token.
  
 
-To learn more about OAuth access tokens and how to get them, see  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins) and [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins).
+To learn more about OAuth access tokens and how to get them, see  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md) and [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md).
  
 
  
@@ -359,10 +366,10 @@ Cross-domain library requests use this format when they access data on the add-i
 |Cloud-hosted|JavaScript add-in component accessing data in a site collection other than the host web by using the cross-domain library (tenant-scoped add-ins only)| _<app web url>_/_api/SP.AppContextSite(@target)/web/title?@target=' _<target site url>_'|
 |SharePoint-hosted|Add-in web component accessing data in another site collection (tenant-scoped add-ins only)| _<app web url>_/_api/SP.AppContextSite(@target)/web/title?@target=' _<target site url>_'|
 
- **Note**  Cross-domain data access scenarios also require appropriate add-in permissions. For more information, see  [Access data from the host web](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_Hostweb) and [Access data across site collections](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library#SP15Accessdatafromremoteapp_TenantScope).
+ **Note**  Cross-domain data access scenarios also require appropriate add-in permissions. For more information, see  [Access data from the host web](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_Hostweb) and [Access data across site collections](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md#SP15Accessdatafromremoteapp_TenantScope).
  
 
-SharePoint Add-ins can get the add-in web URL and host web URL from the query string of the add-in page, as shown in the following code example. The example also shows how to reference the cross-domain library, which is defined in the SP.RequestExecutor.js file on the host web. The example assumes that your add-in launches from SharePoint. See  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins) for guidance on setting your SharePoint context correctly when your add-in does not launch from SharePoint.
+SharePoint Add-ins can get the add-in web URL and host web URL from the query string of the add-in page, as shown in the following code example. The example also shows how to reference the cross-domain library, which is defined in the SP.RequestExecutor.js file on the host web. The example assumes that your add-in launches from SharePoint. See  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md) for guidance on setting your SharePoint context correctly when your add-in does not launch from SharePoint.
  
 
  
@@ -438,7 +445,7 @@ Table 2 shows properties that are commonly used in HTTP requests for the SharePo
 ## Batch job support
 <a name="batch"> </a>
 
-The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis).
+The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md).
  
 
  
@@ -447,31 +454,31 @@ The SharePoint Online (and on-premise SharePoint 2016 and later) REST service su
 <a name="bk_addresources"> </a>
 
 
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
 -  [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations)
     
  
--  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-2013-Perform-ab9c4ae5)
+-  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-Perform-ab9c4ae5)
     
  
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
 -  [Open Data Protocol](http://www.odata.org/)
@@ -480,7 +487,7 @@ The SharePoint Online (and on-premise SharePoint 2016 and later) REST service su
 -  [OData: JavaScript Object Notation (JSON) Format](http://www.odata.org/documentation/odata-version-2-0/JSON-format/)
     
  
--  [Set custom permissions on a list by using the REST interface](set-custom-permissions-on-a-list-by-using-the-rest-interface)
+-  [Set custom permissions on a list by using the REST interface](set-custom-permissions-on-a-list-by-using-the-rest-interface.md)
     
  
 
diff --git a/docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md b/docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md
index f193a6b122..dafeb2cd23 100644
--- a/docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Complete basic operations using SharePoint REST endpoints
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Context Token OAuth flow for SharePoint Add-ins
 Learn about the OAuth authentication and authorization flow for low-trust, provider-hosted add-ins in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -18,14 +25,14 @@ With a provider-hosted add-in, you have a remote web application or service that
 
  
 
- **Note**  The remote component can also host event receivers that respond to events that occur to SharePoint items, such as lists or list items. Examples of remote events that Contoso.com might want to respond to are list events, such as adding or removing a list item; or web events, such as adding or deleting a site. For more information about how to create remote event receivers, see  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins).
+ **Note**  The remote component can also host event receivers that respond to events that occur to SharePoint items, such as lists or list items. Examples of remote events that Contoso.com might want to respond to are list events, such as adding or removing a list item; or web events, such as adding or deleting a site. For more information about how to create remote event receivers, see  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins.md).
  
 
 Contoso.com uses the SharePoint client object model (CSOM) or the SharePoint REST APIs to make calls to SharePoint. The Contoso.com application uses an OAuth token-passing flow to authenticate with SharePoint.  **SharePoint and Contoso.com do not trust each other; but both trust ACS** and will accept tokens issued by ACS. There are three tokens involved: SharePoint has ACS create a context token that SharePoint forwards to Constoso.com. Contoso.com validates that the context token was issued by ACS so it trusts it. Contoso.com then extracts a refresh token from the context token and uses it to get an access token directly from ACS. It includes the access token in all its requests to SharePoint. SharePoint validates that the access token was issued by ACS, so it responds to the requests from Contoso.com.
  
 
  
- **You provide the token-handling code** in the remote component. (But if your remote component is hosted on .NET, the Microsoft Office Developer Tools for Visual Studio provide sample code that does most of the work for you.) For details about token-handling code, see [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins).
+ **You provide the token-handling code** in the remote component. (But if your remote component is hosted on .NET, the Microsoft Office Developer Tools for Visual Studio provide sample code that does most of the work for you.) For details about token-handling code, see [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md).
  
 
  
@@ -46,10 +53,10 @@ There are some preliminary steps that must be done before a SharePoint Add-in ca
   - The  **customer** who is installing the add-in **must have an Office 365 account**. This is necessary to get access to ACS. The customer does not have to use their account for any other purpose.
     
  
-  - The farm must be configured to share the trust relationship that Office 365 has with ACS. This is easily done with Windows PowerShell scripts. For details, see  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on-premises-sharepoint-site).
+  - The farm must be configured to share the trust relationship that Office 365 has with ACS. This is easily done with Windows PowerShell scripts. For details, see  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md).
     
  
-- Regardless of whether the add-in is installed to SharePoint Online or to an on-premise SharePoint farm, the  **SharePoint Add-in must be registered with ACS**. For details about how this can be done, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013). Among other things, the add-in provides ACS with its client ID and client secret as part of the registration.
+- Regardless of whether the add-in is installed to SharePoint Online or to an on-premise SharePoint farm, the  **SharePoint Add-in must be registered with ACS**. For details about how this can be done, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md). Among other things, the add-in provides ACS with its client ID and client secret as part of the registration.
     
  
 
@@ -66,7 +73,7 @@ The OAuth authentication and authorization flow for a SharePoint provider-hosted
  
 
  
-![OAuth authorization process flow](../../images/833fcdcc-1755-438b-9ada-dce9646564c0.gif)
+![OAuth authorization process flow](../images/833fcdcc-1755-438b-9ada-dce9646564c0.gif)
  
 These are the steps that correspond to the numbers in the figure:
  
@@ -77,7 +84,7 @@ These are the steps that correspond to the numbers in the figure:
 
 1. A user launches the SharePoint Add-in from SharePoint. The design of the add-in determines how this is done:
     
-      - If the add-in is designed to surface the remote web application (at Contoso.com) in an add-in part (which is essentially a wrapper around an **IFRAME**), then launching the add-in simply means navigating to a SharePoint page that contains the add-in part. (If the user is not already logged on, SharePoint prompts the user to log on.) SharePoint processes the page and detects that there is a component from the Contoso.com application on the page. (For details about add-in parts, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in).)
+      - If the add-in is designed to surface the remote web application (at Contoso.com) in an add-in part (which is essentially a wrapper around an **IFRAME**), then launching the add-in simply means navigating to a SharePoint page that contains the add-in part. (If the user is not already logged on, SharePoint prompts the user to log on.) SharePoint processes the page and detects that there is a component from the Contoso.com application on the page. (For details about add-in parts, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md).)
     
  
   - If the add-in is designed to use as a full page in the browser, then the user launches it by clicking on its add-in tile on the SharePoint website's  **Site Contents** page. (A variation of this is when the add-in includes a custom menu or ribbon item that launches the remote component.)
@@ -98,7 +105,7 @@ These are the steps that correspond to the numbers in the figure:
 6. The Contoso.com server gets the context token and validates the signature which it can do because it knows the client secret. This assures Contoso.com that the token was issued by ACS and not an imposter pretending to be SharePoint. Contoso.com extracts the refresh token from the context token and sends it, along with other information including the its client ID and client secret, to ACS in a request for an access token that will allow it to access SharePoint,
     
  
-7. ACS validates the refresh token so that it is assured that it issued the token, and then it returns an access token to Contoso.com. Optionally, Contoso.com can cache this access token so it doesn't have ask ACS for an access token every time that it accesses SharePoint. By default, access tokens are good for a few hours at a time. (When this article was written, the default expiration for ACS-issued access tokens to SharePoint was 12 hours, but that could change.) Each access token is specific to the user account that is specified in the original request for authorization, and grants access only to the service (in this case, SharePoint) that is specified in that request. Refresh tokens are longer lived (six months when this article was written) and can also be cached. So, the same refresh token can be redeemed for a new access token from ACS until the refresh token itself expires. (For more information about caching tokens, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins).) When the refresh token expires, the Contoso.com can get a new one by obtaining a new context token. For details about how this is done, see  [Get a new context token](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins#GetNewContextToken).
+7. ACS validates the refresh token so that it is assured that it issued the token, and then it returns an access token to Contoso.com. Optionally, Contoso.com can cache this access token so it doesn't have ask ACS for an access token every time that it accesses SharePoint. By default, access tokens are good for a few hours at a time. (When this article was written, the default expiration for ACS-issued access tokens to SharePoint was 12 hours, but that could change.) Each access token is specific to the user account that is specified in the original request for authorization, and grants access only to the service (in this case, SharePoint) that is specified in that request. Refresh tokens are longer lived (six months when this article was written) and can also be cached. So, the same refresh token can be redeemed for a new access token from ACS until the refresh token itself expires. (For more information about caching tokens, see  [Handle security tokens in provider-hosted low-trust SharePoint Add-ins](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md).) When the refresh token expires, the Contoso.com can get a new one by obtaining a new context token. For details about how this is done, see  [Get a new context token](handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md#GetNewContextToken).
     
  
 8. Contoso.com uses the access token to make a SharePoint REST API call or CSOM request to spnv. It does this by passing the OAuth access token in the HTTP  **Authorization** header. (Sample code for creating the header is provided in the Office Developer Tools for Visual Studio if your remote component is hosted on a .NET platform.
@@ -115,16 +122,16 @@ These are the steps that correspond to the numbers in the figure:
 <a name="Filename_AdditionalResources"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md b/docs/sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md
index 9abc4e8b9e..559fab0f0b 100644
--- a/docs/sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Convert an autohosted SharePoint Add-in to a provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Convert an autohosted SharePoint Add-in to a provider-hosted add-in
 Learn how to convert an autohosted SharePoint Add-in to a provider-hosted add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Microsoft SharePoint introduced a new approach to extending SharePoint sites in addition to the previous approach of using solution-based customizations. This new extensibility model for SharePoint, called the add-in model, enables developers to create custom implementations that can be deployed to SharePoint environments regardless of whether they are running in an on-premises, SharePoint Online, or hybrid deployment.
@@ -19,7 +26,7 @@ This article explains how to convert and migrate an autohosted add-in to a provi
 ## Prerequisites for converting an autohosted add-in to a provider-hosted add-in
 
 
-- All of the  [prerequisites for developing provider-hosted add-ins](get-started-creating-provider-hosted-sharepoint-add-ins#SP15createselfhostapp_bk_prereq).
+- All of the  [prerequisites for developing provider-hosted add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
     
  
 - Azure SDK v2.3. Install it from here  [this Download Center page](http://azure.microsoft.com/downloads).
@@ -39,10 +46,10 @@ Before you convert an autohosted add-in to a provider-hosted add-in, you should
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)|Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface (UI) options, deployment system, security system, and lifecycle.|
-| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in)|Learn about the various ways that you can host SharePoint Add-ins.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the distinction between host webs and add-in webs. Also find out which SharePoint components can be included in a SharePoint Add-in, which are deployed to the host web, which are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)|Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface (UI) options, deployment system, security system, and lifecycle.|
+| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md)|Learn about the various ways that you can host SharePoint Add-ins.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the distinction between host webs and add-in webs. Also find out which SharePoint components can be included in a SharePoint Add-in, which are deployed to the host web, which are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 
 ## Converting the add-in
 <a name="Converting"> </a>
@@ -131,7 +138,7 @@ The next step is to create a new Microsoft Azure SQL Database. Login to the  **A
  
 
  
-![Azure SQL DB listing](../../images/ConvertAuto2ProviderFig3.jpg)
+![Azure SQL DB listing](../images/ConvertAuto2ProviderFig3.jpg)
  
 Click the  **SERVERS** link in the top navigation and then click the **ADD** button in the footer as shown in the following figure:
  
@@ -143,7 +150,7 @@ Click the  **SERVERS** link in the top navigation and then click the **ADD** but
  
 
  
-![Azure SQL DB Add button](../../images/ConvertAuto2ProviderFig4.jpg)
+![Azure SQL DB Add button](../images/ConvertAuto2ProviderFig4.jpg)
  
 In the  **CREATE SERVER** dialog that appears, select the Azure **SUBSCRIPTION**, the  **LOGIN NAME** and **PASSWORD** for the user who will have rights to the server and select the same **REGION** used when creating the Azure Web Site previously. Make a note of the login name and password as those will be needed in a later step.
  
@@ -155,7 +162,7 @@ In the  **CREATE SERVER** dialog that appears, select the Azure **SUBSCRIPTION**
  
 
  
-![Azure SQL New DB dialog](../../images/ConvertAuto2ProviderFig5.jpg)
+![Azure SQL New DB dialog](../images/ConvertAuto2ProviderFig5.jpg)
  
 Once the form is filled out, click the  **check icon** in the lower right to create the database. While the server is now created, the only resource that can access it are other Azure services. Make a note of the name of the Microsoft Azure SQL Database because this will be needed in a later step.
  
@@ -171,7 +178,7 @@ In order to connect to the Microsoft Azure SQL Database and deploy the database,
  
 
  
-![Connect to server error](../../images/ConvertAuto2ProviderFig6.jpg)
+![Connect to server error](../images/ConvertAuto2ProviderFig6.jpg)
  
 To create a firewall rule, within the  **Azure Management Portal**, select the Microsoft Azure SQL Database previously created and then click the  **CONFIGURE** link in the top navigation. Under the **Allowed IP Addresses** section, your IP address is currently shown as shown in the following figure. Click **ADD TO THE ALLOWED IP ADDRESSES** to add a firewall rule. Doing so will allow connections to the Microsoft Azure SQL Database and deployment of the database. Make sure to click the **Save** button in the footer.
  
@@ -183,7 +190,7 @@ To create a firewall rule, within the  **Azure Management Portal**, select the M
  
 
  
-![Azure SQL create firewall rule](../../images/ConvertAuto2Providerfig7.jpg)
+![Azure SQL create firewall rule](../images/ConvertAuto2Providerfig7.jpg)
  
 The next step is to deploy the database. This can be done from Visual Studio using the Azure SDK v2.3. Install it from  [this Download Center page](http://azure.microsoft.com/downloads). Within Visual Studio, open the  **SQL Server Object Explorer** tool window, right-click the **SQL Server** node and select **Add SQL Server**:
  
@@ -195,7 +202,7 @@ The next step is to deploy the database. This can be done from Visual Studio usi
  
 
  
-![Connect to SQL Azure from Visual Studio](../../images/ConvertAuto2Providerfig8.jpg)
+![Connect to SQL Azure from Visual Studio](../images/ConvertAuto2Providerfig8.jpg)
  
 In the  **Connect to Server** dialog, enter the **Server Name**, set the  **Authentication** to **SQL Server Authentication** and enter the same **Login** and **Password** defined when creating the Microsoft Azure SQL Database. The server name should be the fully qualified name of the server which is `[server-name].database.windows.net`, as shown in the following figure:
  
@@ -207,7 +214,7 @@ In the  **Connect to Server** dialog, enter the **Server Name**, set the  **Auth
  
 
  
-![SQL login to server dialog](../../images/ConvertAuto2Providerfig9.jpg)
+![SQL login to server dialog](../images/ConvertAuto2Providerfig9.jpg)
  
 After connecting to the Microsoft Azure SQL Database, expand the node for the newly added server, right-click on the  **Databases** node and select **Publish Data-tier Application** to bring up the publishing wizard.
  
@@ -223,7 +230,7 @@ In the section  **Source Data-tier Application (.dacpac)**, use the  **Browse**
  
 
  
-![Publish DACPAC dialog](../../images/ConvertAuto2ProviderFig10.jpg)
+![Publish DACPAC dialog](../images/ConvertAuto2ProviderFig10.jpg)
  
 Refresh the Visual Studio  **SQL Server Object Explorer** tool window to see the CustomerDb listed under the **Databases** node.
  
@@ -247,7 +254,7 @@ Once the Microsoft Azure SQL Database has been created, make a copy of the conne
  
 
  
-![Azure SQL connection strings dialog](../../images/ConvertAuto2Providerfig11.jpg)
+![Azure SQL connection strings dialog](../images/ConvertAuto2Providerfig11.jpg)
  
 The other way to get the connection string is from within Visual Studio, provided the Azure SDK v2.3 is installed. Within the  **SQL Server Object Explorer** tool window in Visual Studio, select the database **CustomerDb**. Once the database is selected, look at the  **Properties** tool window to see connection string. This is the same value found in the **Azure Management Portal** above.
  
@@ -259,7 +266,7 @@ The other way to get the connection string is from within Visual Studio, provide
  
 
  
-![Obtain SQL connection string in Visual Studio](../../images/ConvertAuto2ProviderFig12.jpg)
+![Obtain SQL connection string in Visual Studio](../images/ConvertAuto2ProviderFig12.jpg)
  
 
  
@@ -282,7 +289,7 @@ To create a new Azure Web Site, first login to the  **Azure Management Portal**
  
 
  
-![Azure Web Sites dashboard](../../images/ConvertAuto2Providerfig13.jpg)
+![Azure Web Sites dashboard](../images/ConvertAuto2Providerfig13.jpg)
  
 Next, in the new web site wizard, select  **COMPUTE**,  **WEB SITE**,  **QUICK CREATE** and then specify a **URL** and **WEB HOSTING PLAN**. Finally specify the  **REGION** where the web site should be created. Make sure to remember the region selected because the same region should be used for the Microsoft Azure SQL Database created later. In addition, if a web hosting plan does not already exist or a new one is desired, select the option **Create new web hosting plan**. The following figure shows an example:
  
@@ -294,7 +301,7 @@ Next, in the new web site wizard, select  **COMPUTE**,  **WEB SITE**,  **QUICK C
  
 
  
-![Create Azure Web Site dialog](../../images/ConvertAuto2Providerfig14.jpg)
+![Create Azure Web Site dialog](../images/ConvertAuto2Providerfig14.jpg)
  
 After creating the Azure Web Site, make a note of the URL that is used for the site. In the figures above, the site created is  `http://spahapptoph.azurewebsites.net`. 
  
@@ -383,7 +390,7 @@ Now the ASP.NET MVC web application files need to be deployed to the Azure Web S
  
 
  
-![Publish web site dialog in Visual Studio](../../images/ConvertAuto2Providerfig17.jpg)
+![Publish web site dialog in Visual Studio](../images/ConvertAuto2Providerfig17.jpg)
  
 In the next step, select the name of the Azure Web Site that was created in a previous step as shown in the following figure, click  **OK**, and ensure the URL of the site is HTTPS.
  
@@ -395,7 +402,7 @@ In the next step, select the name of the Azure Web Site that was created in a pr
  
 
  
-![Select existing web site dialog](../../images/ConvertAuto2ProviderFig18.png)
+![Select existing web site dialog](../images/ConvertAuto2ProviderFig18.png)
  
 In the last step, click the button  **Validate Connection** to ensure the settings and connection is in good working order and finally click **Publish**. This will trigger Visual Studio to deploy the ASP.NET web application to the Azure Web Site. 
  
@@ -449,7 +456,7 @@ Next, remove the reference in the SharePoint add-in project to the ASP.NET MVC w
  
 
  
-![Web project properties in Visual Studio](../../images/ConvertAuto2ProviderFig20.jpg)
+![Web project properties in Visual Studio](../images/ConvertAuto2ProviderFig20.jpg)
  
 The last step requires a manual update to the AppManifest.xml file because some settings are not exposed within the designer. Do this by saving any existing changes to the AppManifest.xml file, and then right-click the same file in  **Solution Explorer** and select **View Code**.
  
@@ -461,7 +468,7 @@ The last step requires a manual update to the AppManifest.xml file because some
  
 
  
-![App manifest context menu in Visual Studio](../../images/ConvertAuto2ProviderFig21.jpg)
+![App manifest context menu in Visual Studio](../images/ConvertAuto2ProviderFig21.jpg)
  
 Within the code view of the AppManifest.xml file, remove the two references to the ASP.NET MVC web application project and the SQL data-tier application project as they are not needed within a SharePoint provider-hosted add-in.
  
@@ -486,7 +493,7 @@ Then find the  **<RemoteWebApplication>** element and update the **ClientId** at
  
 
  
-![Client ID attribute in app manifest](../../images/ConvertAuto2ProviderFig22.jpg)
+![Client ID attribute in app manifest](../images/ConvertAuto2ProviderFig22.jpg)
  
 After saving all changes to the AppManifest.xml file, the add-in is now ready for testing as a SharePoint provider-hosted add-in. Deploy the add-in to a SharePoint farm or SharePoint Online site to verify the conversion steps were performed correctly.
  
diff --git a/docs/sp-add-ins/create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-too.md b/docs/sp-add-ins/create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-too.md
index 42bfad906d..a52b0a694b 100644
--- a/docs/sp-add-ins/create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-too.md
+++ b/docs/sp-add-ins/create-a-basic-sharepoint-hosted-add-in-by-using-napa-office-365-development-too.md
@@ -1,14 +1,21 @@
+---
+title: Create a basic SharePoint-hosted add-in by using Napa Office 365 Development Tools
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a basic SharePoint-hosted add-in by using Napa Office 365 Development Tools
 Learn how to create a basic SharePoint-hosted SharePoint Add-in by using Napa Office 365 Development Tools.
  
 
  
-![Run button](../../images/Apps_NAPA_Run_Button.png)
+![Run button](../images/Apps_NAPA_Run_Button.png)
  
  [Run this sample now!](http://go.microsoft.com/fwlink/?LinkId=313212)
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Napa is a tool that you can use to create SharePoint-hosted SharePoint Add-ins. Napa is itself implemented as a (provider-hosted) SharePoint Add-in that can be installed on SharePoint Online websites that are created with the  **Developer Site** template. SharePoint developer sites have a library called **Add-ins in Testing** on the home page. Instructions for creating a developer site and installing Napa are later in this article.
@@ -22,7 +29,7 @@ By using Napa, you can create your SharePoint Add-ins inside your browser instea
 By following this article, you can learn how to create a simple SharePoint-hosted SharePoint Add-in by using Napa. The add-in that you'll create includes controls and code for managing lists and list items. 
  
 
- **Note**  You can create only SharePoint-hosted SharePoint Add-ins with Napa, not provider-hosted. For information on the differences, see  [SharePoint Add-ins](sharepoint-add-ins).You cannot use SharePoint's add-in updating semantics, which is described in  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013), in Napa. So if you need to update an add-in created in Napa, you first have to export it to Visual Studio. Instructions for doing so are later in this article.You can also create a SharePoint Add-in by using Visual Studio. For more information, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins).
+ **Note**  You can create only SharePoint-hosted SharePoint Add-ins with Napa, not provider-hosted. For information on the differences, see  [SharePoint Add-ins](sharepoint-add-ins.md).You cannot use SharePoint's add-in updating semantics, which is described in  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md), in Napa. So if you need to update an add-in created in Napa, you first have to export it to Visual Studio. Instructions for doing so are later in this article.You can also create a SharePoint Add-in by using Visual Studio. For more information, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md).
  
 
 
@@ -34,7 +41,7 @@ If you don't already have a SharePoint Online subscription that you can use for
 
  
 
- **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more information, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription). 
+ **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more information, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md). 
  
 
 Two ways to get an Office 365 plan. 
@@ -58,7 +65,7 @@ Two ways to get an Office 365 plan.
  
 
  
-![Page 2 of Sign up form for Office 365 account](../../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
+![Page 2 of Sign up form for Office 365 account](../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
  
 
  
@@ -96,7 +103,7 @@ After you finish the signup process, your browser will opens the Office 365 inst
  
 
  
-![Screenshot that shows the Office 365 admin center.](../../images/SP15_Office365AdminInset_border.png)
+![Screenshot that shows the Office 365 admin center.](../images/SP15_Office365AdminInset_border.png)
  
 
  
@@ -116,7 +123,7 @@ After you finish the signup process, your browser will opens the Office 365 inst
  
 
  
-![Screenshot that shows the Developer site homepage.](../../images/SP15_DeveloperSiteHome_border.png)
+![Screenshot that shows the Developer site homepage.](../images/SP15_DeveloperSiteHome_border.png)
  
 
  
@@ -126,7 +133,7 @@ After you finish the signup process, your browser will opens the Office 365 inst
 ## Install Napa
 <a name="Overview"> </a>
 
-If your subscription was not originally created as a Office 365 Developer Site, then you have to create a Developer Site in the Administration UI of the subscription and then install Napa in it. Instructions for creating the site are in  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription).
+If your subscription was not originally created as a Office 365 Developer Site, then you have to create a Developer Site in the Administration UI of the subscription and then install Napa in it. Instructions for creating the site are in  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md).
  
 
  
@@ -376,7 +383,7 @@ The first part of the UI and code is in place, so go ahead and run the add-in to
 
 1. At the bottom of the page, choose the run (
  
-![Run button](../../images/Apps_NAPA_Run_Button.png)
+![Run button](../images/Apps_NAPA_Run_Button.png)
  
 ) button.
     
@@ -626,7 +633,7 @@ Open your project in Visual Studio by choosing the  **Open in Visual Studio** bu
  
 
  
-![Open in Visual Studio button](../../images/Apps_Napa_OpenInVS.png)
+![Open in Visual Studio button](../images/Apps_Napa_OpenInVS.png)
  
 
  
@@ -640,7 +647,7 @@ Open your project in Visual Studio by choosing the  **Open in Visual Studio** bu
 -  [SharePoint development overview](http://msdn.microsoft.com/library/f86e2695-4d7a-4fc5-bc23-689de96c4b06%28Office.15%29.aspx)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway.md b/docs/sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway.md
index b064795354..64c67a3ce6 100644
--- a/docs/sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway.md
+++ b/docs/sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway.md
@@ -1,8 +1,15 @@
+---
+title: Create a cloud business add-in that uses the SAP Gateway
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a cloud business add-in that uses the SAP Gateway
  Learn how to build the LightSwitch SharePoint provider-hosted add-in to access SAP data by means of SAP Gateway for Microsoft.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 This article highlights the key steps that the development team at Microsoft used to create a LightSwitch SharePoint provider-hosted add-in that can access SAP data by means of SAP Gateway for Microsoft. This add-in supports CRUD operations on SAP Data, and can be used to view pictures from and upload pictures to a SharePoint picture library.
@@ -73,7 +80,7 @@ The SellerDashboard solution includes eight projects, and as the following image
  
 
  
-![SellerDashboard](../../images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg)
+![SellerDashboard](../images/4092aef3-2fb9-43f1-ad9a-0a326c4648d4.jpg)
  
 
 ### BoxXDataStudio
@@ -178,7 +185,7 @@ This studio includes all of the components needed to interact with SAP Gateway f
     
     This is the real CRUD implementation for BoxXDataService. The following image shows the main code architecture of CarInventoryBoxXDataOperation. The CRUD namespace is used to implement the CRUD operations, and the Util namespace is the helper code for the CRUD namespace.
     
-  ![CarInventoryBoxDataOperation](../../images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg)
+  ![CarInventoryBoxDataOperation](../images/a9baa59c-4459-4f0d-935d-456f0ca7791e.jpg)
  
 
  
@@ -193,7 +200,7 @@ This studio includes all of the components needed to interact with SAP Gateway f
  
 
  
-![CarInventoryModel](../../images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg)
+![CarInventoryModel](../images/1a814b3b-76a3-4a5c-8eef-550893728499.jpg)
  
 
  
@@ -218,7 +225,7 @@ SellerDashboardStudio includes standard LightSwitch SharePoint add-in components
     
  
 - 
-  ![SellerDashboard.HTMLClient](../../images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg)
+  ![SellerDashboard.HTMLClient](../images/89aa8c23-f8f2-410e-b021-7b0959e11586.jpg)
  
 
     SellerDashboard.HTML.Client includes these four screens:
@@ -247,7 +254,7 @@ SellerDashboardStudio includes standard LightSwitch SharePoint add-in components
     
     This component includes the WCF RIA data source, the SharePoint data source, and the photo-upload Web API. The following image shows its main components.
     
-  ![SellerDashboard.Server](../../images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg)
+  ![SellerDashboard.Server](../images/43e92a09-180d-4adf-9ae2-8f6212d297c9.jpg)
  
 
     The SharePointContext.cs and TokenHelper.cs are the helper classes that provide the client context to authenticate to SharePoint. This enables the photo upload Web API to be used to upload photos of cars to the picture library. The PhotoListHelper.cs and PhotosController.cs files implement the photo-upload Web API. For more information about how the photo-upload Web API is used by LightSwitch, see the article  [Walkthrough: Creating an Add-in for SharePoint by Using LightSwitch](http://msdn.microsoft.com/en-us/library/jj969621.aspx).
@@ -278,7 +285,7 @@ The following image show the components that comprise the SellerDashboard. The s
  
 
  
-![SellerDashboard Solution](../../images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg)
+![SellerDashboard Solution](../images/5be3a1d5-4d6e-4d08-aa9f-ca9b093325ae.jpg)
  
 
  
@@ -410,7 +417,7 @@ xmlns:edmx:"http://schemas.microsoft.com/ado/2007/06/edmx" Version="1.0">
  
 -  *Data source consumed by the LightSwitch server side* 
     
-  ![InventoryItem](../../images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg)
+  ![InventoryItem](../images/b08243f7-3fa3-48b3-bf6c-e3ff49f2e2a2.jpg)
  
 
     In the SellerDashboard server, when you add the WCF RIA Service (BoxXDataService), the data model that's defined in CarInventoryModel is included, and you get the relevant data table. You can change the type of some of the properties. For example, you can change the  **BuyerEmail** type from **String** to **Email Address**, and LightSwitch will support the email format check on the client side.
@@ -442,7 +449,7 @@ ContosoMotorsPicture is a LightSwitch data source model, which maps to the Share
  
 
  
-![ContosoMotorsPicture](../../images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg)
+![ContosoMotorsPicture](../images/1dfc317f-b4f2-46f7-9f3e-4b81f04ef0dd.jpg)
  
  **Data relationship**
  
@@ -454,7 +461,7 @@ Add a one-to-zero relationship or a one-to-one relationship between the Inventor
  
 
  
-![Data relationship](../../images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg)
+![Data relationship](../images/978d8147-cabd-422e-9d02-d8022a114bd6.jpg)
  
 
  
@@ -481,7 +488,7 @@ To access the SharePoint picture library, SellerDashboard needs to authenticate
  
 
  
-![Data center](../../images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg)
+![Data center](../images/eb83c0d8-0937-4df7-984b-3d8b4717b2b3.jpg)
  
  **Implementation**
  
@@ -798,7 +805,7 @@ An empty SharePoint add-in is used to grant the SharePoint add-in the read permi
  
 3. Set the Read permission in the application's manifest.
     
-  ![Manifest](../../images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg)
+  ![Manifest](../images/746bcfe7-7f51-4f5d-a072-12c577e5fa2f.jpg)
  
 
  
diff --git a/docs/sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed.md b/docs/sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed.md
index 8197606bec..b15177835a 100644
--- a/docs/sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed.md
+++ b/docs/sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed.md
@@ -1,10 +1,17 @@
+---
+title: Create a cloud business add-in with a social newsfeed
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a cloud business add-in with a social newsfeed
 By using the  **Cloud Business Add-in** template in Visual Studio, you can create SharePoint Add-ins in which users can view, add, and update SharePoint data. The **Cloud Business Add-in** project type uses Visual Studio LightSwitch technologies, which greatly simplify the process of creating business add-in hosted on SharePoint. In this walkthrough, you'll create an add-in to track job candidates, taking advantage of the SharePoint for Office 365 social integration feature to provide a newsfeed for the add-in.
  
 You can download the complete sample application from the MSDN Code Gallery:  [Creating a Cloud Business Add-in with a Social Newsfeed](http://code.msdn.microsoft.com/Creating-a-Cloud-Business-8540c0c9)
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -41,7 +48,7 @@ To host the add-in, you'll also need a SharePoint site or a SharePoint Developer
 
  
 
-  ![Cloud Business App project template](../../images/CBAtemplate.PNG)
+  ![Cloud Business App project template](../images/CBAtemplate.PNG)
  
 
  
@@ -114,7 +121,7 @@ The candidate tracker add-in needs a database table, which you'll create in the
 
  
 
-  ![Candidates table](../../images/CBAentity.PNG)
+  ![Candidates table](../images/CBAentity.PNG)
  
 
  
@@ -143,7 +150,7 @@ The candidate tracker add-in needs a database table, which you'll create in the
 
  
 
-  ![The BrowseCandidates screen designer](../../images/CBAscreen.PNG)
+  ![The BrowseCandidates screen designer](../images/CBAscreen.PNG)
  
 
     This will display the  **Candidate** information in a tabular format instead of the default list format.
@@ -164,7 +171,7 @@ The candidate tracker add-in needs a database table, which you'll create in the
 
  
 
-  ![Add Button dialog box](../../images/CBAadd.PNG)
+  ![Add Button dialog box](../images/CBAadd.PNG)
  
 
     The  **Add New Screen** dialog box opens.
@@ -190,7 +197,7 @@ A new screen designer window opens.
 
  
 
-  ![Item Tap property](../../images/CBAproperty.PNG)
+  ![Item Tap property](../images/CBAproperty.PNG)
  
 
     The  **Edit Item Tap Action** dialog box opens.
@@ -202,7 +209,7 @@ A new screen designer window opens.
 
  
 
-  ![Edit ItemTap Action dialog box](../../images/CBAaction.PNG)
+  ![Edit ItemTap Action dialog box](../images/CBAaction.PNG)
  
 
  
@@ -276,7 +283,7 @@ One of the features of SharePoint for Office 365 is the ability to add newsfeeds
 
  
 
-  ![Social properties](../../mages/CBAsocial.PNG)
+  ![Social properties](../images/CBAsocial.PNG)
  
 
  
@@ -374,7 +381,7 @@ Of course, this is just a simple example; there's much more that you can do to c
 <a name="bk_addresources"> </a>
 
 
--  [Create cloud business add-ins](create-cloud-business-add-ins)
+-  [Create cloud business add-ins](create-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-a-cloud-business-add-in.md b/docs/sp-add-ins/create-a-cloud-business-add-in.md
index 43c0522cc2..a017e74c61 100644
--- a/docs/sp-add-ins/create-a-cloud-business-add-in.md
+++ b/docs/sp-add-ins/create-a-cloud-business-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Create a cloud business add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a cloud business add-in
 By using the Cloud Business Add-in template in Visual Studio, you can create SharePoint Add-ins 2013 or SharePoint on Office 365 that are optimized for adding and managing data.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -24,7 +31,7 @@ By using the Cloud Business Add-in template in Visual Studio, you can create Sha
 
  
 
-  ![Template for creating a Cloud Business App](../../images/CloudBusinessApptemplate.PNG)
+  ![Template for creating a Cloud Business App](../images/CloudBusinessApptemplate.PNG)
  
 
  
@@ -41,7 +48,7 @@ By using the Cloud Business Add-in template in Visual Studio, you can create Sha
 
  
 
-  ![SharePoint URL](../../images/SiteURL.PNG)
+  ![SharePoint URL](../images/SiteURL.PNG)
  
 
     The URL should take the form https://  _MySite_.sharepoint.com/sites/Developer/.
@@ -59,7 +66,7 @@ By using the Cloud Business Add-in template in Visual Studio, you can create Sha
 
  
 
-  ![The top level project node](../../images/Top-levelprojectnode.PNG)
+  ![The top level project node](../images/Top-levelprojectnode.PNG)
  
 
     The application designer opens.
@@ -71,7 +78,7 @@ By using the Cloud Business Add-in template in Visual Studio, you can create Sha
 
  
 
-  ![The SharePoint properties tab](../../images/SharePointtab.PNG)
+  ![The SharePoint properties tab](../images/SharePointtab.PNG)
  
 
  
@@ -88,10 +95,10 @@ By using the Cloud Business Add-in template in Visual Studio, you can create Sha
 <a name="bk_addresources"> </a>
 
 
--  [Develop cloud business add-ins](develop-cloud-business-add-ins)
+-  [Develop cloud business add-ins](develop-cloud-business-add-ins.md)
     
  
--  [Create cloud business add-ins](create-cloud-business-add-ins)
+-  [Create cloud business add-ins](create-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md b/docs/sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md
index 2c6f61349e..a7f1320906 100644
--- a/docs/sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md
+++ b/docs/sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md
@@ -1,8 +1,15 @@
+---
+title: Create a custom proxy page for the cross-domain library in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a custom proxy page for the cross-domain library in SharePoint
 Learn how to create a custom proxy page to access data in a remote service from a SharePoint webpage by using the cross domain library in SharePoint. 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 When you are building SharePoint Add-ins, you usually have to incorporate data from various sources. However, for security reasons, there are blocking mechanisms that prevent communication with more than one domain at a time.
@@ -15,7 +22,7 @@ You can use the cross-domain library to access data in your remote add-in if you
 ## Prerequisites for using the examples in this article
 <a name="SP15Createcustomproxypage_Prereq"> </a>
 
-You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
  
@@ -32,9 +39,9 @@ The following table lists some useful articles that can help you understand the
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)|Learn about data access options in SharePoint Add-ins. This topic provides guidance on the high-level alternatives you have to choose from when working with data in your add-in.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)|Learn about data access options in SharePoint Add-ins. This topic provides guidance on the high-level alternatives you have to choose from when working with data in your add-in.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 | [Client-side Cross-domain Security](http://msdn.microsoft.com/en-us/library/cc709423%28v=vs.85%29.aspx)|Explore cross-domain threats and use cases, and security principles for cross-origin requests, and weigh the risks for developers to enhance cross-domain access from web applications that run in the browser.|
 
 ## Code example: Access remote data using a custom proxy page for the cross-domain library
@@ -64,7 +71,7 @@ To read data from the remote service, you must do the following:
 1. Open Visual Studio as administrator. (To do this, right-click the Visual Studio icon on the  **Start** menu, and choose **Run as administrator**.)
     
  
-2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins) and name itProxyPageApp. 
+2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md) and name itProxyPageApp. 
     
  
 
@@ -83,7 +90,7 @@ To read data from the remote service, you must do the following:
 ```
 
 
-     **Note**  The  **AllowedRemoteHostUrl** attribute is used to specify the remote domain. The **~remoteAppUrl** resolves to the remote add-in URL. For more information about tokens, see [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in).
+     **Note**  The  **AllowedRemoteHostUrl** attribute is used to specify the remote domain. The **~remoteAppUrl** resolves to the remote add-in URL. For more information about tokens, see [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md).
 
 ### To create a custom proxy page
 
@@ -337,7 +344,7 @@ Response.End();
 
  
 
-  ![SharePoint page with data from a remote service](../../images/CustomProxy_result.jpg)
+  ![SharePoint page with data from a remote service](../images/CustomProxy_result.jpg)
  
 
  
@@ -360,13 +367,13 @@ This article demonstrated how to access remote data by using a custom proxy page
 
  
 
--  [Code sample: Get data by using a proxy page for the cross-domain library](http://code.msdn.microsoft.com/SharePoint-2013-Get-data-10039ff1)
+-  [Code sample: Get data by using a proxy page for the cross-domain library](http://code.msdn.microsoft.com/SharePoint-Get-data-10039ff1)
     
  
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
--  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013)
+-  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md)
     
  
 
@@ -374,28 +381,28 @@ This article demonstrated how to access remote data by using a custom proxy page
 <a name="SP15Createcustomproxypage_Addresources"> </a>
 
 
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#Data)
+-  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#Data)
     
  
 
diff --git a/docs/sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md b/docs/sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md
index 84290cd3c0..d27b597ac5 100644
--- a/docs/sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md
+++ b/docs/sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md
@@ -1,35 +1,42 @@
+---
+title: Create a custom ribbon button in the host web of a SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a custom ribbon button in the host web of a SharePoint Add-in
 Add custom ribbon button commands to the host web of a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the ninth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the ninth in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
 
@@ -64,7 +71,7 @@ You will add the button to the ribbon of a calendar on the host web. Take the fo
 
  
 
-  ![A calendar named Employee Orientation Schedule with an item on June 1st that says "Orient Cassie Hicks"](../../images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG)
+  ![A calendar named Employee Orientation Schedule with an item on June 1st that says "Orient Cassie Hicks"](../images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG)
  
 
  
@@ -116,7 +123,7 @@ Notice that the custom action that you created,  **RunOrientationAdd-in**, is li
  
 
  
-![The feature designer with columns labelled "Items in the solution" and "Items in the feature". The "Run Orientation Add-in" is in the first, not the second.](../../images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG)
+![The feature designer with columns labelled "Items in the solution" and "Items in the feature". The "Run Orientation Add-in" is in the first, not the second.](../images/49ea0bf0-2cfa-4070-aa65-24b4a9c5e874.PNG)
  
 
  
@@ -145,7 +152,7 @@ Notice that the custom action that you created,  **RunOrientationAdd-in**, is li
 
  
 
-  ![The Events ribbon with a custom button named "Employee Orientation"](../../images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png)
+  ![The Events ribbon with a custom button named "Employee Orientation"](../images/916ecbba-11ff-45b6-a8e9-ba717ae6fe0b.png)
  
 
  
@@ -164,7 +171,7 @@ Notice that the custom action that you created,  **RunOrientationAdd-in**, is li
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add JavaScript to the SharePoint Add-in and access SharePoint data with SharePoint's JavaScript object model:  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data).
+In the next article in this series, you'll add JavaScript to the SharePoint Add-in and access SharePoint data with SharePoint's JavaScript object model:  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md).
  
 
  
diff --git a/docs/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md b/docs/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md
index dac5484ba9..a906f3e07c 100644
--- a/docs/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md
+++ b/docs/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md
@@ -1,8 +1,15 @@
+---
+title: Create a developer site on an existing Office 365 subscription
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a developer site on an existing Office 365 subscription
 An Office 365 Developer Site makes it easier to get set up and start creating, testing, and deploying your Office and SharePoint Add-ins more quickly. Many Office 365 Business, Enterprise, Education, and Government subscriptions include a site template you can use to create a Developer Site.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
  **Before you start**
@@ -54,7 +61,7 @@ An Office 365 Developer Site makes it easier to get set up and start creating, t
  
 5. In the  **SharePoint admin center**, on the **Site Collections** tab, click **New > Private Site Collection**.
     
-  ![SharePoint Admin Center new site collection option](../../images/SPAdminCenter_newSiteCollection.png)
+  ![SharePoint Admin Center new site collection option](../images/SPAdminCenter_newSiteCollection.png)
  
 
  
@@ -76,7 +83,7 @@ An Office 365 Developer Site makes it easier to get set up and start creating, t
     
     You'll see the new developer site URL in the  **Site Collections** list. When the site creation is finished, you can navigate to the URL to open your Developer Site.
     
-  ![New site collection provisioning](../../images/SPAdminCenter_newSiteCollection_provisioning.png)
+  ![New site collection provisioning](../images/SPAdminCenter_newSiteCollection_provisioning.png)
  
 
  
@@ -87,7 +94,7 @@ An Office 365 Developer Site makes it easier to get set up and start creating, t
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
 -  [Create or delete a site collection](http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/create-or-delete-a-site-collection-HA102772354.aspx?CTT=1)
diff --git a/docs/sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins.md b/docs/sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins.md
index f69ca80e84..677492032e 100644
--- a/docs/sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins.md
@@ -1,15 +1,22 @@
+---
+title: Create a handler for the update event in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a handler for the update event in SharePoint Add-ins
 Create and use a handler for the update event of a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites for creating a handler for the add-in update event
 <a name="Prerequisites"> </a>
 
-Be thoroughly familiar with both  [Handling add-in events](handle-events-in-sharepoint-add-ins#HandlingAppEvents) and [Update SharePoint Add-ins](update-sharepoint-add-ins) and the prerequisites and core concepts listed in them.
+Be thoroughly familiar with both  [Handling add-in events](handle-events-in-sharepoint-add-ins.md#HandlingAppEvents) and [Update SharePoint Add-ins](update-sharepoint-add-ins.md) and the prerequisites and core concepts listed in them.
  
 
  
@@ -21,7 +28,7 @@ Be thoroughly familiar with both  [Handling add-in events](handle-events-in-shar
  **Note**   **Version numbering system:** For consistency, this topic assumes that the add-in version numbers are 1.0.0.0, 2.0.0.0, 3.0.0.0, and so on. However, the logic and guidance applies no matter what your numbering system is.
  
 
-For custom update logic, you can create a SharePoint remote event receiver that handles the add-in updated event. You should be conservative in using this technique. Use it only for updating steps that can't be done any other way. Also, the guidance found in  [Handling add-in events](handle-events-in-sharepoint-add-ins#HandlingAppEvents) applies for the add-in updated event as much as the add-in installed and add-in uninstalling events. This includes:
+For custom update logic, you can create a SharePoint remote event receiver that handles the add-in updated event. You should be conservative in using this technique. Use it only for updating steps that can't be done any other way. Also, the guidance found in  [Handling add-in events](handle-events-in-sharepoint-add-ins.md#HandlingAppEvents) applies for the add-in updated event as much as the add-in installed and add-in uninstalling events. This includes:
  
 
  
@@ -39,7 +46,7 @@ One scenario in which an  **UpgradedEventEndpoint** handler is useful is when a
  
 
  
-For more details about how to create a handler for the add-in event, see  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins) and [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins). The following procedure assumes that you have added the add-in event receiver item to your SharePoint Add-in project in Visual Studio. 
+For more details about how to create a handler for the add-in event, see  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md) and [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md). The following procedure assumes that you have added the add-in event receiver item to your SharePoint Add-in project in Visual Studio. 
  
 
  
@@ -77,7 +84,7 @@ For more details about how to create a handler for the add-in event, see  [Handl
 
 ```
 
-4. To use the REST interface, your code uses other methods in the  **TokenHelper** class to get an access token, which is then included in the requests it makes to SharePoint. For more information, see [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints). Your code should be structured similarly to the following.
+4. To use the REST interface, your code uses other methods in the  **TokenHelper** class to get an access token, which is then included in the requests it makes to SharePoint. For more information, see [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md). Your code should be structured similarly to the following.
     
 ```C#
   if (properties.EventType == SPRemoteEventType.AppUpgraded)
@@ -228,7 +235,7 @@ catch (Exception e)
 
 ### Use the handler delegation strategy
 
-The handler delegation strategy that is described in  [Handling add-in events](handle-events-in-sharepoint-add-ins#HandlingAppEvents) can be used in an **UpdatedEventHandler** too. Not only is your rollback and "already done" logic bundled and run on the remote component, but your versioning logic is too. The limitations of the strategy apply here too: you usually can't use it to update more than one remote system.
+The handler delegation strategy that is described in  [Handling add-in events](handle-events-in-sharepoint-add-ins.md#HandlingAppEvents) can be used in an **UpdatedEventHandler** too. Not only is your rollback and "already done" logic bundled and run on the remote component, but your versioning logic is too. The limitations of the strategy apply here too: you usually can't use it to update more than one remote system.
  
 
  
@@ -236,18 +243,18 @@ The handler delegation strategy that is described in  [Handling add-in events](h
 ## Next steps
 <a name="Next"> </a>
 
-Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
+Return to  [Major steps in updating an add-in](update-sharepoint-add-ins.md#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
  
 
  
 
--  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013)
+-  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md)
     
  
--  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013)
+-  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md)
     
  
--  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins)
+-  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md)
     
  
 
@@ -255,16 +262,16 @@ Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAp
 <a name="bk_addresources"> </a>
 
 
--  [Update SharePoint Add-ins](update-sharepoint-add-ins)
+-  [Update SharePoint Add-ins](update-sharepoint-add-ins.md)
     
  
 -  [UpgradedEventEndpoint element (PropertiesDefinition complexType) (SharePoint Add-in Manifest)](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx)
     
  
--  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins)
+-  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md)
     
  
--  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins)
+-  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md b/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md
index 00535379f2..769661f60a 100644
--- a/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md
+++ b/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md
@@ -1,8 +1,15 @@
+---
+title: Create a provider-hosted add-in that includes a custom SharePoint list and content type
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a provider-hosted add-in that includes a custom SharePoint list and content type
 Create a SharePoint Add-in that combines a cloud-hosted web application with custom SharePoint-hosted list templates, list instances, and custom content types by using the Office Developer Tools for Visual Studio 2012. Learn how to interact with SharePoint add-in webs by using the REST/OData web service, and how to implement OAuth in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Most classic SharePoint components, such as custom content types, custom list definitions, and workflows, can be included in a cloud-hosted SharePoint Add-in. The simple example in this article contains the following:
@@ -44,7 +51,7 @@ Most classic SharePoint components, such as custom content types, custom list de
   - The test SharePoint website must be created from the  **Developer Site** site definition (which you can create in Central Administration).
     
  
-  - Your remote web application communicates with the add-in web by using either JavaScript and the  [cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library) or [OAuth](authorization-and-authentication-of-sharepoint-add-ins). If OAuth is used, as it is in the continuing example of this article, the SharePoint installation must be configured to use OAuth.
+  - Your remote web application communicates with the add-in web by using either JavaScript and the  [cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md) or [OAuth](authorization-and-authentication-of-sharepoint-add-ins.md). If OAuth is used, as it is in the continuing example of this article, the SharePoint installation must be configured to use OAuth.
     
  
 
@@ -64,9 +71,9 @@ Before you create your first add-in, you should have a basic understanding of wh
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)|Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface (UI) options, deployment system, security system, and life cycle.|
-| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in)|Learn about the various ways that you can host SharePoint Add-ins.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)|Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface (UI) options, deployment system, security system, and life cycle.|
+| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md)|Learn about the various ways that you can host SharePoint Add-ins.|
 
 ## Develop the SharePoint Add-in
 <a name="Develop"> </a>
@@ -105,14 +112,14 @@ Before you create your first add-in, you should have a basic understanding of wh
   -  **System.IdentityModel.dll** This assembly is part of the .NET Framework 4, and it appears on the **Assemblies | Framework** node of the **Add Reference** dialog box.
     
  
-7. If your remote web application accesses information in the host web as well as the add-in web, you must add an  **AppPermissionRequests** element, with one or more child **AppPermissionRequest** elements, to the AppManifest.xml file. (The web application in the continuing example of this article accesses only the add-in web. Add-in principals automatically have all permissions needed to the add-in web, so the AppManifest.xml in the example does not have an **AppPermissionRequests** element.) For more information about add-in permission requests and how to add them, see [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+7. If your remote web application accesses information in the host web as well as the add-in web, you must add an  **AppPermissionRequests** element, with one or more child **AppPermissionRequest** elements, to the AppManifest.xml file. (The web application in the continuing example of this article accesses only the add-in web. Add-in principals automatically have all permissions needed to the add-in web, so the AppManifest.xml in the example does not have an **AppPermissionRequests** element.) For more information about add-in permission requests and how to add them, see [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
     
  
 
 ### To add the SharePoint components
 
 
-1. You add SharePoint components to an add-in exactly as you would add them to a classic farm solution. However, not every kind of SharePoint component can be included in a SharePoint Add-in. The purposes these components serve are accomplished in other ways in SharePoint Add-ins. For detailed information about what kinds of SharePoint components can be included in a SharePoint Add-in and how to include them in a project, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#TypesOfSPComponentsInApps).
+1. You add SharePoint components to an add-in exactly as you would add them to a classic farm solution. However, not every kind of SharePoint component can be included in a SharePoint Add-in. The purposes these components serve are accomplished in other ways in SharePoint Add-ins. For detailed information about what kinds of SharePoint components can be included in a SharePoint Add-in and how to include them in a project, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps).
     
     For purposes of the continuing example, use the following procedures. These will provide examples of using Visual Studio 2012 to add custom columns, content types, list templates, and list instances to a SharePoint Add-in.
     
@@ -458,7 +465,7 @@ Uri sharepointUrl;
 }
 ```
 
-  7. Add the following line that uses one of the SharePoint REST/OData endpoints to obtain list data. In this example, the code reads the  **Characters in Hamlet** list that is deployed to the add-in web. The APIs for this service make it easy, in a single line of code, to select a list and specify three fields from the list to return. Note that in the OData URL you must use the internal names of the fields (columns) rather than the display names, so the code uses `Title`,  `Actor`, and  `CastingStatus` rather than `Character`,  `Actor/Actress`, and  `Casting Status.` For more information about the REST/OData web service, see [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests).
+  7. Add the following line that uses one of the SharePoint REST/OData endpoints to obtain list data. In this example, the code reads the  **Characters in Hamlet** list that is deployed to the add-in web. The APIs for this service make it easy, in a single line of code, to select a list and specify three fields from the list to return. Note that in the OData URL you must use the internal names of the fields (columns) rather than the display names, so the code uses `Title`,  `Actor`, and  `CastingStatus` rather than `Character`,  `Actor/Actress`, and  `Casting Status.` For more information about the REST/OData web service, see [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md).
     
 ```C#
   // REST/OData URL section
@@ -527,7 +534,7 @@ GridView1.DataBind();
 ## Publishing the SharePoint Add-in
 <a name="Publish"> </a>
 
-To publish your SharePoint Add-in, upload the add-in package to a corporate add-in catalog or to the Office add-in store. For more information, see  [Publishing to the Office Store or an organization's add-in catalog](deploying-and-installing-sharepoint-add-ins-methods-and-options#MarketOrCatalog) and [Publish SharePoint Add-ins](publish-sharepoint-add-ins).
+To publish your SharePoint Add-in, upload the add-in package to a corporate add-in catalog or to the Office add-in store. For more information, see  [Publishing to the Office Store or an organization's add-in catalog](deploying-and-installing-sharepoint-add-ins-methods-and-options.md#MarketOrCatalog) and [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md).
  
 
  
@@ -579,10 +586,10 @@ This article demonstrated how to create a simple hybrid SharePoint Add-in with a
 
  
 
-- Adding full CRUD functionality to the add-in with either the REST/OData endpoints or one of the client object models. For more information, see  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests) and [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code).
+- Adding full CRUD functionality to the add-in with either the REST/OData endpoints or one of the client object models. For more information, see  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md) and [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md).
     
  
-- Localizing your SharePoint Add-in for other cultures. For more information, see  [Localize SharePoint Add-ins](localize-sharepoint-add-ins).
+- Localizing your SharePoint Add-in for other cultures. For more information, see  [Localize SharePoint Add-ins](localize-sharepoint-add-ins.md).
     
  
 - Creating a Windows Phone companion add-in that duplicates the functionality of the remote web application. For more information, see  [Build mobile SharePoint Add-ins 2013](http://msdn.microsoft.com/en-us/library/office/jj163228.aspx).
@@ -593,10 +600,10 @@ This article demonstrated how to create a simple hybrid SharePoint Add-in with a
 <a name="SP15createcloud_bk_addlresources"> </a>
 
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins.md b/docs/sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins.md
index 641db8b75a..a95c21c8f4 100644
--- a/docs/sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins.md
@@ -1,15 +1,22 @@
+---
+title: Create a remote event receiver in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a remote event receiver in SharePoint Add-ins
 Create a remote event receiver (RER) that handles list and list item events in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites
 <a name="SP15appevent_prereq"> </a>
 
-It is helpful if you first have an understanding of provider-hosted SharePoint Add-ins, and for you to have developed a few that go a least a little beyond the "Hello World" level. Also, you should be familiar with  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins). 
+It is helpful if you first have an understanding of provider-hosted SharePoint Add-ins, and for you to have developed a few that go a least a little beyond the "Hello World" level. Also, you should be familiar with  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md). 
  
 
  
@@ -94,7 +101,7 @@ To follow along with this article and enter the code yourself, download the samp
 ### To add functionality to the remote event receiver
 
 
-1. If your test SharePoint farm is not on the same computer that is running Visual Studio, (or you are using an SharePoint Online tenancy as your test SharePoint site), configure the project for debugging using the Microsoft Azure Service Bus. For more information, see the  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in). 
+1. If your test SharePoint farm is not on the same computer that is running Visual Studio, (or you are using an SharePoint Online tenancy as your test SharePoint site), configure the project for debugging using the Microsoft Azure Service Bus. For more information, see the  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md). 
     
  
 2. In the code file for the service of the remote event receiver (that is, RemoteEventReceiver1.svc.cs), replace the contents with the following code.
@@ -300,7 +307,7 @@ Test your handler with the following procedure.
 
  
 
-  ![SharePoint remote events in Visual Studio](../../images/SP_VS_Properties_Window_RemoteEvents.PNG)
+  ![SharePoint remote events in Visual Studio](../images/SP_VS_Properties_Window_RemoteEvents.PNG)
  
 
  
@@ -343,13 +350,13 @@ https://github.com/OfficeDev/PnP/tree/master/Samples/Provisioning.ReR)
 <a name="Additional"> </a>
 
 
--  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins)
+-  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md)
     
  
--  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in)
+-  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md)
     
  
--  [Remote Event Receivers FAQ](handle-events-in-sharepoint-add-ins#RERFAQ)
+-  [Remote Event Receivers FAQ](handle-events-in-sharepoint-add-ins.md#RERFAQ)
     
  
 
diff --git a/docs/sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add.md b/docs/sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add.md
index 98f4b6dd3a..4bd1489ff3 100644
--- a/docs/sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add.md
+++ b/docs/sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add.md
@@ -1,8 +1,15 @@
+---
+title: Create a SharePoint Add-in that contains a document template and a task pane add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create a SharePoint Add-in that contains a document template and a task pane add-in
 Use Visual Studio to develop an Office Add-in that appears in a document that is opened from a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can create a SharePoint Add-in that includes a document template (for example, an expense report). The document can include a task pane add-in that interacts with SharePoint data. For example, users can populate fields of an invoice by using data from the Business Connectivity Services (BCS) or create an expense report by selecting an expense category from a SharePoint list.
@@ -143,7 +150,7 @@ In this procedure, you will add a document library and make the workbook the def
  
 12. In the manifest designer, set the value of the  **Start page** value to~appWebUrl/Lists/MyDocumentLibrary. This converts to a value of OfficeEnabledAddin/Lists/MyDocumentLibrary.
     
-     **Note**  This URL refers to the document library. You must use the ~appWebUrl token at the beginning of any URL in your Office Add-in manifest that refers to items within the add-in web. For more information about URL tokens in a SharePoint Add-in project, see  [URL strings and tokens in SharePoint Add-ins](url-strings-and-tokens-in-sharepoint-add-ins).
+     **Note**  This URL refers to the document library. You must use the ~appWebUrl token at the beginning of any URL in your Office Add-in manifest that refers to items within the add-in web. For more information about URL tokens in a SharePoint Add-in project, see  [URL strings and tokens in SharePoint Add-ins](url-strings-and-tokens-in-sharepoint-add-ins.md).
 13. Close the manifest designer to save the change.
     
  
@@ -160,10 +167,10 @@ In this example, the SharePoint list data is only displayed, but you might use t
 
  
 
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
 -  [Persisting add-in state and settings](http://msdn.microsoft.com/library/407df6e8-c237-4d6a-b357-3000fe3de9ff%28Office.15%29.aspx)
@@ -354,7 +361,7 @@ When you are ready to package your add-in for publishing, open the  **Publish Of
 
 - In  **Solution Explorer**, open the shortcut menu for the SharePoint Add-in project, and then choose  **Publish**.
     
-    The  **Publish Office and SharePoint Add-ins** wizard appears. For more information, see [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio).
+    The  **Publish Office and SharePoint Add-ins** wizard appears. For more information, see [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio.md).
     
  
 
diff --git a/docs/sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md b/docs/sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md
index a3c8d38e2b..63c8efe093 100644
--- a/docs/sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md
+++ b/docs/sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md
@@ -1,20 +1,27 @@
+---
+title: Create add-in parts to install with your SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create add-in parts to install with your SharePoint Add-in
 Learn how to create an add-in part in SharePoint that is available in the Web Part gallery of the host web when you install your SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 With add-in parts, you can show your add-in user experience right in the SharePoint website pages. An add-in part displays the webpage (which is typically an interactive form or a dynamic display of data) that you specify by using an  **IFrame** (also referred to as a frame) in a page in the [host web](http://msdn.microsoft.com/library/fp179925.aspx). For more background about add-in parts, see the following articles:
  
 
--  [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#AccessingApp)
+-  [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#AccessingApp)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [Extending SharePoint UI in add-ins](sharepoint-add-ins-ux-design-guidelines#UXGuide_Extending)
+-  [Extending SharePoint UI in add-ins](sharepoint-add-ins-ux-design-guidelines.md#UXGuide_Extending)
     
  
 Figure 1 shows how the add-in part content is displayed in a SharePoint page.
@@ -25,7 +32,7 @@ Figure 1 shows how the add-in part content is displayed in a SharePoint page.
  
 
  
-![App part content displayed in a SharePoint page](../../images/AppParts_ConceptualArchitecture.png)
+![App part content displayed in a SharePoint page](../images/AppParts_ConceptualArchitecture.png)
  
 An add-in part is implemented with the  **ClientWebPart** class, and like all Web Parts it is a available in the Web Part gallery after a user installs the SharePoint Add-in that includes it. Your users can further customize the add-in part using the properties that you provide. (See figure 2 below for an example of configurable properties in an add-in part.)
  
@@ -46,7 +53,7 @@ To follow the steps in this example, you need the following:
 - Microsoft Office Developer Tools for Visual Studio
     
  
-- A SharePoint development environment. If you need help setting up a development environment, see  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+- A SharePoint development environment. If you need help setting up a development environment, see  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
     
  
 
@@ -81,13 +88,13 @@ After completing the tasks, your add-in part should look similar to Figure 2 whe
  
 
  
-![Web part page hosting a basic app part](../../images/BasicAppPart_result.png)
+![Web part page hosting a basic app part](../images/BasicAppPart_result.png)
  
 
 ### Add a form for the add-in part content
 
 
-1. Create a provider-hosted SharePoint Add-in as described in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins), but name the project TestAppPart.
+1. Create a provider-hosted SharePoint Add-in as described in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md), but name the project TestAppPart.
     
  
 2. After the Visual Studio solution has been created, right-click the web application project (not the SharePoint Add-in project) and add a new Web Form by choosing  **Add** > **New Item** > **Web** > **Web Form**. Name the form AppPartContent.aspx.
@@ -208,7 +215,7 @@ After completing the tasks, your add-in part should look similar to Figure 2 whe
     
  **Custom Properties dialog for ClientWebPart**
 
-![The Client Web Part Custom Properties Dialog with 4 properties listed on the left, and each one having 5 attributes set on the right.](../../images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG)
+![The Client Web Part Custom Properties Dialog with 4 properties listed on the left, and each one having 5 attributes set on the right.](../images/6a0f0a56-3184-490a-af19-b51b7545671d.PNG)
  
 
 8. Select the  **enumProp** property, select the **EnumItems** attribute, and then choose the callout ( **...**) button. 
@@ -246,7 +253,7 @@ The dialog should look like the following when you are finished:
 
  
 
-![The Client Web Part Enum Item Collection Editor with 3 items listed and each one having a Value attribute and a Web Display Name attribute.](../../images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG)
+![The Client Web Part Enum Item Collection Editor with 3 items listed and each one having a Value attribute and a Web Display Name attribute.](../images/1b21d968-bd58-4f30-a019-84df6181b81a.PNG)
  
 
  
@@ -350,7 +357,7 @@ The dialog should look like the following when you are finished:
 
  
 
-  ![Basic app part in the web part gallery](../../images/BasicAppPart_gallery.jpg)
+  ![Basic app part in the web part gallery](../images/BasicAppPart_gallery.jpg)
  
 
  
@@ -402,7 +409,7 @@ In most cases, a webpage can't be displayed in a frame if it sends an  **X-Frame
  
 
  
-![App part that can't display its content in a frame](../../images/AppParts_IFrameError.png)
+![App part that can't display its content in a frame](../images/AppParts_IFrameError.png)
  
 Be aware that certain scenarios are susceptible to " [ClickJacking](http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx)" attacks when the webpages are displayed in a frame. Carefully evaluate your add-in part scenarios to make sure there is no risk of  **ClickJacking** attacks.
  
@@ -419,7 +426,7 @@ If your page hosted on the add-in web is not susceptible to ClickJacking attacks
 <WebPartPages:AllowFraming ID="AllowFraming1" runat="server" />
 ```
 
-You can download an  [add-in part code sample](http://code.msdn.microsoft.com/SharePoint-2013-Display-be8dac16) that shows how to use a SharePoint page as the content page.
+You can download an  [add-in part code sample](http://code.msdn.microsoft.com/SharePoint-Display-be8dac16) that shows how to use a SharePoint page as the content page.
  
 
  
@@ -430,7 +437,7 @@ If you're using dynamic content in your add-in part, the content might change it
  
 
  
-You can use POST messages from your content webpage to specify the frame's size. The following JavaScript example shows you how to send a POST message to resize the frame in which your add-in part is hosted. Typically, you would have this in a JavaScript method in a JavaScript file that you call from the page. For example, the page could have a control in which the user specifies the size of the add-in part window. The custom method is then called from  **onchange** handler of the control. For a full sample, see [Code sample: Resize add-in parts dynamically in SharePoint Add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-2013-Resize-app-594acc88). 
+You can use POST messages from your content webpage to specify the frame's size. The following JavaScript example shows you how to send a POST message to resize the frame in which your add-in part is hosted. Typically, you would have this in a JavaScript method in a JavaScript file that you call from the page. For example, the page could have a control in which the user specifies the size of the add-in part window. The custom method is then called from  **onchange** handler of the control. For a full sample, see [Code sample: Resize add-in parts dynamically in SharePoint Add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-Resize-app-594acc88). 
  
 
  
@@ -441,7 +448,7 @@ You can use POST messages from your content webpage to specify the frame's size.
 window.parent.postMessage("<message senderId={SenderId}>resize(120, 300)</message>", {hostweburl});
 ```
 
-In the example above, the  **senderId** value will be set on the query string of the page automatically by the add-in part code when the page is rendered. Your page would just need to read the **SenderId** value off of the query string and use it when requesting a resize. You can retrieve the host web URL from the query string by appending the **StandardTokens** or **HostUrl** tokens to the **Src** attribute in your add-in part definition. You can download the [Resize add-in parts code sample](http://code.msdn.microsoft.com/officeapps/SharePoint-2013-Resize-app-594acc88) to see an add-in part that dynamically resizes.
+In the example above, the  **senderId** value will be set on the query string of the page automatically by the add-in part code when the page is rendered. Your page would just need to read the **SenderId** value off of the query string and use it when requesting a resize. You can retrieve the host web URL from the query string by appending the **StandardTokens** or **HostUrl** tokens to the **Src** attribute in your add-in part definition. You can download the [Resize add-in parts code sample](http://code.msdn.microsoft.com/officeapps/SharePoint-Resize-app-594acc88) to see an add-in part that dynamically resizes.
  
 
  
@@ -452,7 +459,7 @@ Since your add-in part is hosted within a SharePoint page, you might want to mak
  
 
  
-You can see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins) for an explanation on how to reference the **defaultcss.ashx** file in your SharePoint Add-ins. You can also download the [coffeemaker code sample](http://code.msdn.microsoft.com/office/SharePoint-2013-App-part-9d83703c) to see an add-in part that references the style sheet.
+You can see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md) for an explanation on how to reference the **defaultcss.ashx** file in your SharePoint Add-ins. You can also download the [coffeemaker code sample](http://code.msdn.microsoft.com/office/SharePoint-App-part-9d83703c.md) to see an add-in part that references the style sheet.
  
 
  
@@ -483,33 +490,33 @@ The  **_editMode_** token lets your content page determine if the add-in part is
 <a name="SP15Createappparts_AddResources"> </a>
 
 
--  [Code sample: Display remote add-in content in the host web using an add-in part](http://code.msdn.microsoft.com/SharePoint-2013-Display-03c28286)
+-  [Code sample: Display remote add-in content in the host web using an add-in part](http://code.msdn.microsoft.com/SharePoint-Display-03c28286)
     
  
--  [Code sample: Display add-in web content in the host web using an add-in part](http://code.msdn.microsoft.com/SharePoint-2013-Display-be8dac16)
+-  [Code sample: Display add-in web content in the host web using an add-in part](http://code.msdn.microsoft.com/SharePoint-Display-be8dac16)
     
  
--  [Code sample: Resize add-in parts dynamically in SharePoint Add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-2013-Resize-app-594acc88)
+-  [Code sample: Resize add-in parts dynamically in SharePoint Add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-Resize-app-594acc88)
     
  
--  [Code sample: Display remote webpage content using the coffeemaker add-in part](http://code.msdn.microsoft.com/SharePoint-2013-App-part-9d83703c)
+-  [Code sample: Display remote webpage content using the coffeemaker add-in part](http://code.msdn.microsoft.com/SharePoint-App-part-9d83703c)
     
  
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines)
+-  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
diff --git a/docs/sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins.md b/docs/sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins.md
index d7496c9848..c765d2f6b0 100644
--- a/docs/sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins.md
@@ -1,15 +1,22 @@
+---
+title: Create an add-in event receiver in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create an add-in event receiver in SharePoint Add-ins
 Create handlers for the SharePoint Add-in install and uninstall events in SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites
 <a name="SP15appevent_prereq"> </a>
 
-This article presupposes that you have an understanding of provider-hosted SharePoint Add-ins, and that you have developed a few that go a least a little beyond the "Hello World" level. Also, you should be familiar with  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins). 
+This article presupposes that you have an understanding of provider-hosted SharePoint Add-ins, and that you have developed a few that go a least a little beyond the "Hello World" level. Also, you should be familiar with  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md). 
  
 
  
@@ -31,7 +38,7 @@ If you work through the continuing example in this article, you will have a fini
 -  [OfficeDev/PnP/Samples/Core.EventReceivers](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.EventReceivers)
     
  
--  [Create a provider-hosted add-in that customizes add-in installation](https://code.msdn.microsoft.com/SharePoint-2013-Create-a-f27752e0)
+-  [Create a provider-hosted add-in that customizes add-in installation](https://code.msdn.microsoft.com/SharePoint-Create-a-f27752e0)
     
  
 
@@ -51,7 +58,7 @@ If you work through the continuing example in this article, you will have a fini
 
  
 
-  ![App events in the properties window](../../images/SP_VS_Properties_Window_AppEvents.PNG)
+  ![App events in the properties window](../images/SP_VS_Properties_Window_AppEvents.PNG)
  
 
     The Office Developer Tools for Visual Studio will do the following:
@@ -67,7 +74,7 @@ If you work through the continuing example in this article, you will have a fini
   - If the SharePoint Add-in project doesn't already have a web project, the Office Developer Tools for Visual Studio create one. The tools also ensure that add-in manifest is configured for a provider-hosted add-in. They will also add pages, scripts, CSS files, and other artifacts. (If the only remote component that your add-in needs is the event-handling web service, you can delete these from the project. You also should ensure that the  **StartPage** element in the add-in manifest is not pointing to a page that you have deleted.)
     
  
-4. If your test SharePoint farm is not on the same computer that is running Visual Studio, configure the project for debugging using the Microsoft Azure Service Bus. For more information, see  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in). 
+4. If your test SharePoint farm is not on the same computer that is running Visual Studio, configure the project for debugging using the Microsoft Azure Service Bus. For more information, see  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md). 
     
  
 5. If there is a  `ProcessOneWayEvent` method in the AppEventReceiver.svc file, it's implementation should consist of just the line `throw new NotImplementedException();`, because this method cannot be used in an add-in event handler.  *Add-in event handlers have to return an object that tells SharePoint whether to finish or roll back the event and the  `ProcessOneWayEvent` method doesn't return anything.* 
@@ -116,7 +123,7 @@ If you work through the continuing example in this article, you will have a fini
 
 
      **Note**  The  **AppInstalled**,  **AppUpdated**, and  **AppInstalling** events, if you have handlers for them, will each get their own URL registered in the add-in manifest. So you *can*  have different endpoints for them; but this article (and the Office Developer Tools for Visual Studio) assume they have exactly the same endpoint; that's why the code needs to determine which event called it.
-8. As explained in  [Include rollback logic and "already done" logic in your add-in event handlers](handle-events-in-sharepoint-add-ins#Rollback), if anything goes wrong in your installation logic, you almost always want the add-in installation canceled, and you want SharePoint to roll back what it has done for the installation, and you want to roll back what your handler has done. One way to accomplish these goals is to add the following code inside the  **case** for the AppInstalled event.
+8. As explained in  [Include rollback logic and "already done" logic in your add-in event handlers](handle-events-in-sharepoint-add-ins.md#Rollback), if anything goes wrong in your installation logic, you almost always want the add-in installation canceled, and you want SharePoint to roll back what it has done for the installation, and you want to roll back what your handler has done. One way to accomplish these goals is to add the following code inside the  **case** for the AppInstalled event.
     
 ```C#
   case SPRemoteEventType.AppInstalled:
@@ -136,7 +143,7 @@ If you work through the continuing example in this article, you will have a fini
 
 
      **Note**  Move installation code that takes more than 30 seconds into the add-in itself. You can add it to "first run" logic that executes the first time the add-in runs. The add-in can display a message saying something like "We're getting things ready for you." Alternatively, the add-in can prompt the user to run the initialization code.If "first run" logic is not feasible for your add-in, another option is to have your event handler start a remote asynchronous process and then immediately return a  **SPRemoteEventResult** object with the **Status** set to **Continue**. A weakness of this strategy is that if the remote process fails, it has no way to tell SharePoint to roll back the add-in installation.
-9. As explained in  [Add-in event handler architecture strategies](handle-events-in-sharepoint-add-ins#Strategies), the handler delegation strategy is preferred, although not possible in every scenario. In the continuing example, we show you how to implement the handler delegation strategy when adding a list to the host web. (For information on how to create a similar AppInstalled event handler that does not use the handler delegation strategy, see the sample  [OfficeDev/PnP/Samples/Core.AppEvents](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.AppEvents).)
+9. As explained in  [Add-in event handler architecture strategies](handle-events-in-sharepoint-add-ins.md#Strategies), the handler delegation strategy is preferred, although not possible in every scenario. In the continuing example, we show you how to implement the handler delegation strategy when adding a list to the host web. (For information on how to create a similar AppInstalled event handler that does not use the handler delegation strategy, see the sample  [OfficeDev/PnP/Samples/Core.AppEvents](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.AppEvents).)
     
     The following is the new version of the AppInstalled  **case** block. Note that initialization logic that applies to all events goes above the **switch** block. Since the same list that is installed will be removed in the AppUninstalling handler, the list is identified there.
     
@@ -231,7 +238,7 @@ var foundList = matchingLists.FirstOrDefault();
  List createdList = null;
 ```
 
-13. The code to create a host web list will go into the  **StartTry** block, but the code must first check whether the list has already been added (as explained in [Include rollback logic and "already done" logic in your add-in event handlers](handle-events-in-sharepoint-add-ins#Rollback)). If-then-else logic can be delegated to the SharePoint server by using the  **ConditionalScope** class. (See also, [How to: Use Conditional Scope](http://msdn.microsoft.com/library/560112e9-c3ed-4b8f-9cd4-c8bc5d60d63c%28Office.15%29.aspx).) Add the following code inside the  **StartTry** block.
+13. The code to create a host web list will go into the  **StartTry** block, but the code must first check whether the list has already been added (as explained in [Include rollback logic and "already done" logic in your add-in event handlers](handle-events-in-sharepoint-add-ins.md#Rollback)). If-then-else logic can be delegated to the SharePoint server by using the  **ConditionalScope** class. (See also, [How to: Use Conditional Scope](http://msdn.microsoft.com/library/560112e9-c3ed-4b8f-9cd4-c8bc5d60d63c%28Office.15%29.aspx).) Add the following code inside the  **StartTry** block.
     
 ```C#
   ConditionalScope condScope = new ConditionalScope(clientContext, 
@@ -479,7 +486,7 @@ break;
 ## Create an add-in updated event receiver
 <a name="SP15appevent_prereq"> </a>
 
-For details about creating an add-in updated handler, see  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins).
+For details about creating an add-in updated handler, see  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md).
  
 
  
@@ -496,7 +503,7 @@ The add-in event receiver can be hosted in the cloud or in an on-premise server
 <a name="SP15appevent_addlresources"> </a>
 
 
--  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins)
+-  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md b/docs/sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md
index 9d69ae44af..f73a093d7c 100644
--- a/docs/sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md
@@ -1,3 +1,10 @@
+---
+title: Create and use access tokens in provider-hosted high-trust SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create and use access tokens in provider-hosted high-trust SharePoint Add-ins
 Learn about the role of access tokens in high-trust SharePoint Add-ins and how your code works with them.
  
@@ -28,11 +35,11 @@ The main  **things that your code needs to** do are:
 
  
 
-1.  **Create an access token.** The subtasks for creating this token vary depending on whether the remote web application makesadd-in-only calls to SharePoint,user+add-in calls, or both. (For information about the two kinds of calls, see [Add-in authorization policy types in SharePoint 2013](add-in-authorization-policy-types-in-sharepoint-2013.md).) 
+1.  **Create an access token.** The subtasks for creating this token vary depending on whether the remote web application makesadd-in-only calls to SharePoint,user+add-in calls, or both. (For information about the two kinds of calls, see [Add-in authorization policy types in SharePoint 2013](add-in-authorization-policy-types-in-sharepoint.md).) 
     
     If the add-in makes user+add-in calls, then creating the access token includes the following subtasks:
     
-      1. Create an actor token that identifies the SharePoint Add-in and tells SharePoint to delegate user authentication and authorization to your add-in, and encode it in base 64 encoding. Details about the claims and structure of the actor token are in table 2 below. Details about encoding and signing the token are in [Encoding and signing tokens](#EncodingTokens) below.
+      1. Create an actor token that identifies the SharePoint Add-in and tells SharePoint to delegate user authentication and authorization to your add-in, and encode it in base 64 encoding. Details about the claims and structure of the actor token are in table 2 below. Details about encoding and signing the token are in [Encoding and signing tokens](#EncodeTokens) below.
     
  
   2. Sign the actor token with credentials from an x509 certificate that a SharePoint farm administrator has configured SharePoint to trust.
@@ -44,7 +51,7 @@ The main  **things that your code needs to** do are:
   4. Add other required claims to the access token. Details about the claims and structure of the token are in table 1 below.
     
  
-  5. Encode the access token with base 64. Details about encoding and signing the token are in  [Encoding and signing tokens](#EncodingTokens) below.
+  5. Encode the access token with base 64. Details about encoding and signing the token are in  [Encoding and signing tokens](#EncodeTokens) below.
     
  
 
@@ -111,7 +118,7 @@ The following is an  **example of an access token generated by a high-trust Shar
  
 
  
- **This access token is generated if the add-in is making a call to SharePoint using the  [user+add-in policy](add-in-authorization-policy-types-in-sharepoint-2013.md).** If the add-in is using the [add-in-only policy](add-in-authorization-policy-types-in-sharepoint-2013.md) and it makes an add-in-only call to SharePoint, then the actor token (which is a child token within the user+add-in access token and is described below), becomes the access token (and there is no parent token).
+ **This access token is generated if the add-in is making a call to SharePoint using the  [user+add-in policy](add-in-authorization-policy-types-in-sharepoint.md).** If the add-in is using the [add-in-only policy](add-in-authorization-policy-types-in-sharepoint.md) and it makes an add-in-only call to SharePoint, then the actor token (which is a child token within the user+add-in access token and is described below), becomes the access token (and there is no parent token).
  
 
  
@@ -194,7 +201,7 @@ Table 2 describes the claims your code must include in the body of the token and
 ```
 
 
- **Note**  If the high-trust add-in is using the  [add-in-only policy](add-in-authorization-policy-types-in-sharepoint-2013.md) and it makes an add-in-only call to SharePoint, then the token shown here is actually the access token. There is no outer token. Moreover, there is no **trustedfordelegation** claim, since the user's permissions are irrelevant for an add-in-only call.
+ **Note**  If the high-trust add-in is using the  [add-in-only policy](add-in-authorization-policy-types-in-sharepoint.md) and it makes an add-in-only call to SharePoint, then the token shown here is actually the access token. There is no outer token. Moreover, there is no **trustedfordelegation** claim, since the user's permissions are irrelevant for an add-in-only call.
  
 
 
diff --git a/docs/sp-add-ins/create-cloud-business-add-ins.md b/docs/sp-add-ins/create-cloud-business-add-ins.md
index bb831e0f11..2c81c3c190 100644
--- a/docs/sp-add-ins/create-cloud-business-add-ins.md
+++ b/docs/sp-add-ins/create-cloud-business-add-ins.md
@@ -1,28 +1,35 @@
+---
+title: Create cloud business add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create cloud business add-ins
 By using the Cloud Business Add-in template in Visual Studio, you can quickly and easily create line-of-business add-ins that are hosted on SharePoint for Office 365 or SharePoint and based on Visual Studio LightSwitch technologies. Users can download and run cloud business add-ins on desktop computers and most mobile devices.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Start
 
- [Get started developing cloud business add-ins](get-started-developing-cloud-business-add-ins) provides links to learning resources including end-to-end tutorials and samples.
+ [Get started developing cloud business add-ins](get-started-developing-cloud-business-add-ins.md) provides links to learning resources including end-to-end tutorials and samples.
  
 
  
 
 ## Develop
 
- [Develop cloud business add-ins](develop-cloud-business-add-ins) provides help with tasks related to developing a cloud business add-in.
+ [Develop cloud business add-ins](develop-cloud-business-add-ins.md) provides help with tasks related to developing a cloud business add-in.
  
 
  
 
 ## Publish
 
- [Publish cloud business add-ins](publish-cloud-business-add-ins) covers publishing cloud business add-ins to SharePoint for Office 365 and SharePoint.
+ [Publish cloud business add-ins](publish-cloud-business-add-ins.md) covers publishing cloud business add-ins to SharePoint for Office 365 and SharePoint.
  
 
  
@@ -31,7 +38,7 @@ By using the Cloud Business Add-in template in Visual Studio, you can quickly an
 <a name="bk_addresources"> </a>
 
 
--  [New name for apps for SharePoint](new-name-for-apps-for-sharepoint)
+-  [New name for apps for SharePoint](new-name-for-apps-for-sharepoint.md)
     
  
 
diff --git a/docs/sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins.md b/docs/sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins.md
index 3961b30278..c412582ff6 100644
--- a/docs/sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Create custom actions to deploy with SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create custom actions to deploy with SharePoint Add-ins
 Learn how to create a custom action in SharePoint that deploys to the host web when you deploy a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 When you are creating a SharePoint Add-in, custom actions let you interact with the lists and the ribbon in the host web. A custom action deploys to the host web when end users install your add-in. Custom actions can open a remote webpage and pass information through the query string. There are two types of custom actions available for add-ins: Ribbon andMenu Item custom actions.
@@ -11,7 +18,7 @@ When you are creating a SharePoint Add-in, custom actions let you interact with
 ## Prerequisites for using the examples in this article
 <a name="SP15Createcustomactionsapps_Prereq"> </a>
 
-You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
  
@@ -28,9 +35,9 @@ The following table lists useful articles that can help you understand the conce
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)|Learn about the user experience (UX) options that you have when you are building SharePoint Add-ins.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)|Learn about the user experience (UX) options that you have when you are building SharePoint Add-ins.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 
 ## Code example: Create a custom action in the host web document libraries
 <a name="SP15Createcustomactionsapps_Codeexample"> </a>
@@ -56,7 +63,7 @@ Follow these steps to create a custom action in the host web document libraries:
 1. Open Visual Studio as administrator. (To do this, right-click the Visual Studio icon on the  **Start** menu, and choose **Run as administrator**.)
     
  
-2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins) and name itCustomActionsApp. 
+2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md) and name itCustomActionsApp. 
     
  
 
@@ -286,7 +293,7 @@ Follow these steps to create a custom action in the host web document libraries:
 
  
 
-  ![Document library with callout for a document open, the menu that that the callout button on the callout opens, and the Advanced menu open.](../../images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png)
+  ![Document library with callout for a document open, the menu that that the callout button on the callout opens, and the Advanced menu open.](../images/477cecf5-03ff-46ff-9c25-a5f9a86d43f4.png)
  
 
  
@@ -307,7 +314,7 @@ Follow these steps to create a custom action in the host web document libraries:
 
  
 
-  ![Web page with parameters from a custom action](../../images/CustomActions_target.png)
+  ![Web page with parameters from a custom action](../images/CustomActions_target.png)
  
 
  
@@ -319,7 +326,7 @@ Follow these steps to create a custom action in the host web document libraries:
 
  
 
-  ![A document library with a document selected, the File tab open on the ribbon, and the custom button on the ribbon.](../../images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png)
+  ![A document library with a document selected, the File tab open on the ribbon, and the custom button on the ribbon.](../images/b315cb68-ff6a-4770-a1dc-738696ab71d2.png)
  
 
  
@@ -351,22 +358,22 @@ This article demonstrated how to create a custom action in a SharePoint Add-in.
 
  
 
--  [Code sample: Open a remote add-in webpage using an ECB custom action](http://code.msdn.microsoft.com/SharePoint-2013-Open-e0ca1826)
+-  [Code sample: Open a remote add-in webpage using an ECB custom action](http://code.msdn.microsoft.com/SharePoint-Open-e0ca1826)
     
  
 -  [SharePoint-Add-in-Localization](https://github.com/OfficeDev/SharePoint-Add-in-Localization)
     
  
--  [Code sample: Use custom actions and the cross-domain library to order books](http://code.msdn.microsoft.com/SharePoint-2013-Open-a-36d1598d)
+-  [Code sample: Use custom actions and the cross-domain library to order books](http://code.msdn.microsoft.com/SharePoint-Open-a-36d1598d)
     
  
--  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)
+-  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)
     
  
--  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)
+-  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
 
@@ -374,22 +381,22 @@ This article demonstrated how to create a custom action in a SharePoint Add-in.
 <a name="SP15Createcustomactionsapps_AddResources"> </a>
 
 
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines)
+-  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 
diff --git a/docs/sp-add-ins/create-high-trust-sharepoint-add-ins.md b/docs/sp-add-ins/create-high-trust-sharepoint-add-ins.md
index 2d4f9d27e8..1b076acbb4 100644
--- a/docs/sp-add-ins/create-high-trust-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/create-high-trust-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Create high-trust SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create high-trust SharePoint Add-ins
 Learn how to create a high-trust SharePoint Add-in. A high-trust add-in uses digital certificates to establish a trust between the remote web application and SharePoint. High-trust add-ins can only be installed to on premises SharePoint, not to Microsoft SharePoint Online, and they are primarily intended for use with an on premises, rather than cloud-based, web application.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -14,10 +21,10 @@ To follow the procedures in this article, be sure you have the following:
 
  
 
-- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins) for the setup instructions. In particular, be sure you have completed the steps in the section [Configure services in SharePoint for server-to-server add-in use](set-up-an-on-premises-development-environment-for-sharepoint-add-ins#Servertoserver).
+- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md) for the setup instructions. In particular, be sure you have completed the steps in the section [Configure services in SharePoint for server-to-server add-in use](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md#Servertoserver).
     
  
-- Experience creating a provider-hosted SharePoint Add-in. See  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+- Experience creating a provider-hosted SharePoint Add-in. See  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
     
  
 - Visual Studio installed either remotely or on the computer where you have installed SharePoint.
@@ -39,7 +46,7 @@ Read the following articles to get a better understanding of SharePoint Add-ins
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio, how to interact with SharePoint sites by using the SharePoint CSOM.|
+| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio, how to interact with SharePoint sites by using the SharePoint CSOM.|
 | [Digital Certificates](http://msdn.microsoft.com/library/e523b335-0156-4f47-b55c-b80495587c4f.aspx) and [Working with Certificates](http://msdn.microsoft.com/library/6ffb8682-8f07-4a45-afbb-8d2487e9dbc3.aspx)|Learn the basic ideas behind digital certificates.|
 
 ## Introduction to running high-trust add-ins
@@ -53,7 +60,7 @@ A high-trust SharePoint Add-in is primarily intended for use in an on-premises e
  
 
  
-A high-trust add-in uses a certificate instead of a context token to establish trust. (A provider-hosted add-in that's built to use Microsoft Azure Access Control Service (ACS) as its trust broker needs to be modified to work as a high-trust app.) High-trust add-ins require some configuration on the SharePoint farm and on the server hosting the remote web application. This topic describes the configuration steps that are needed to get Visual Studio debugging ( **F5**) working. Configuring a test, staging, or production environment are somewhat different and are described in the topic  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins). 
+A high-trust add-in uses a certificate instead of a context token to establish trust. (A provider-hosted add-in that's built to use Microsoft Azure Access Control Service (ACS) as its trust broker needs to be modified to work as a high-trust app.) High-trust add-ins require some configuration on the SharePoint farm and on the server hosting the remote web application. This topic describes the configuration steps that are needed to get Visual Studio debugging ( **F5**) working. Configuring a test, staging, or production environment are somewhat different and are described in the topic  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md). 
  
 
  
@@ -108,7 +115,7 @@ You'll create a test .pfx certificate file first, and then a corresponding test
 
  
 
-  ![Server Certificates option in IIS](../../images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif)
+  ![Server Certificates option in IIS](../images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif)
  
 
  
@@ -120,7 +127,7 @@ You'll create a test .pfx certificate file first, and then a corresponding test
 
  
 
-  ![Create Self-Signed Cerificate link](../../images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif)
+  ![Create Self-Signed Cerificate link](../images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif)
  
 
  
@@ -135,7 +142,7 @@ You'll create a test .pfx certificate file first, and then a corresponding test
 
  
 
-  ![Exporting a test certificate](../../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
+  ![Exporting a test certificate](../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
  
 
  
@@ -193,12 +200,12 @@ You'll create a test .pfx certificate file first, and then a corresponding test
 ## Configure SharePoint to use certificates and configure trust for your add-in
 <a name="Configure2"> </a>
 
-The Windows PowerShell script that you create in this section is intended to support the use of  **F5** in Visual Studio. It will *not*  properly configure a staging or production SharePoint installation. For instructions on configuring a production SharePoint to use certificates, see [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins).
+The Windows PowerShell script that you create in this section is intended to support the use of  **F5** in Visual Studio. It will *not*  properly configure a staging or production SharePoint installation. For instructions on configuring a production SharePoint to use certificates, see [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md).
  
 
  
 
- **Note**  Double-check that you have completed the steps in  [Configure services in SharePoint for server-to-server add-in use](set-up-an-on-premises-development-environment-for-sharepoint-add-ins#Servertoserver) (which is listed as a prerequisite for this article). If not, you must configure it now, before you proceed.
+ **Note**  Double-check that you have completed the steps in  [Configure services in SharePoint for server-to-server add-in use](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md#Servertoserver) (which is listed as a prerequisite for this article.md). If not, you must configure it now, before you proceed.
  
 
 
@@ -272,7 +279,7 @@ In this section, you learn how to create a high-trust SharePoint Add-in using Vi
 
  
 
- **Note**  As stated in the  [Prerequisites for creating high-trust add-ins](#Prereq) section, this article assumes you know how to create a provider-hosted SharePoint Add-in. For more information, see [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+ **Note**  As stated in the  [Prerequisites for creating high-trust add-ins](#Prereqs) section, this article assumes you know how to create a provider-hosted SharePoint Add-in. For more information, see [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
 
@@ -334,7 +341,7 @@ In this section, you learn how to create a high-trust SharePoint Add-in using Vi
 
  
 
-  ![Sample app retrieving web title](../../images/SP15HighTrustLaunchNew.gif)
+  ![Sample app retrieving web title](../images/SP15HighTrustLaunchNew.gif)
  
 
  
@@ -449,7 +456,7 @@ When you have obtained the new certificate, you need to add a password to it, if
 2. Press  **F5** to debug the add-in.
     
  
-When you are done developing your high-trust add-in, check  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins) for instructions on how to package and publish this kind of SharePoint Add-in.
+When you are done developing your high-trust add-in, check  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md) for instructions on how to package and publish this kind of SharePoint Add-in.
  
 
  
@@ -471,7 +478,7 @@ Office Developer Tools for Visual Studio includes a TokenHelper.cs (or .vb) file
 - Get the SharePoint security token service (STS) certificate.
     
  
-- In add-ins that use the low-trust rather than the high-trust authorization system, these files have additional tasks, such as handling OAuth tokens for the scenario described in  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins). That scenario is outside the scope of this article. 
+- In add-ins that use the low-trust rather than the high-trust authorization system, these files have additional tasks, such as handling OAuth tokens for the scenario described in  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md). That scenario is outside the scope of this article. 
     
  
 For more details about TokenHelper and SharePointContext, see the comments in the files.
@@ -482,7 +489,7 @@ In a high-trust add-in, there is no context token. The context token is specific
  
 
  
-When you are debugging in Visual Studio with  **F5**, Microsoft Office Developer Tools for Visual Studio uses Windows Authentication, and the two generated code files use the Windows identity of the person running the add-in to create the access token. When your add-in is published, you need to configure the remote web application in IIS Manager to use Windows Authentication if you want to use the two generated files without modification. If your add-in will not use Windows Authentication on the production environment, you will need to customize the generated code files, TokenHelper and/or SharePointContext, to use a different authentication system. You would also customize these files if your remote web application accesses SharePoint in an identity other than the user who is running the SharePoint Add-in. Finally, if the remote web application is PHP, node.js, Java, or some other non-ASP.NET platform, then your code needs to obtain the user's ID from whatever authentication system is being used, and then add that ID into the access token it constructs. For more information, see  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins),  [Create and use access tokens in provider-hosted high-trust SharePoint Add-ins](create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins) and [Using SharePoint Add-ins with SAML and FBA Sites in SharePoint](http://blogs.technet.com/b/speschka/archive/2012/12/07/using-sharepoint-apps-with-saml-and-fba-sites-in-sharepoint-2013.aspx).
+When you are debugging in Visual Studio with  **F5**, Microsoft Office Developer Tools for Visual Studio uses Windows Authentication, and the two generated code files use the Windows identity of the person running the add-in to create the access token. When your add-in is published, you need to configure the remote web application in IIS Manager to use Windows Authentication if you want to use the two generated files without modification. If your add-in will not use Windows Authentication on the production environment, you will need to customize the generated code files, TokenHelper and/or SharePointContext, to use a different authentication system. You would also customize these files if your remote web application accesses SharePoint in an identity other than the user who is running the SharePoint Add-in. Finally, if the remote web application is PHP, node.js, Java, or some other non-ASP.NET platform, then your code needs to obtain the user's ID from whatever authentication system is being used, and then add that ID into the access token it constructs. For more information, see  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md),  [Create and use access tokens in provider-hosted high-trust SharePoint Add-ins](create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md) and [Using SharePoint Add-ins with SAML and FBA Sites in SharePoint](http://blogs.technet.com/b/speschka/archive/2012/12/07/using-sharepoint-apps-with-saml-and-fba-sites-in-sharepoint-2013.aspx).
  
 
  
@@ -491,25 +498,25 @@ When you are debugging in Visual Studio with  **F5**, Microsoft Office Developer
 <a name="bk_addresources"> </a>
 
 
--  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins)
+-  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md)
     
  
 -  [Troubleshooting Tips for High Trust Add-ins on SharePoint](http://blogs.technet.com/b/speschka/archive/2012/11/01/more-troubleshooting-tips-for-high-trust-apps-on-sharepoint-2013.aspx)
     
  
--  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013)
+-  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
 -  [Announcing the new SharePointContext helper in SharePoint Add-ins 2013](http://blogs.msdn.com/b/officeapps/archive/2013/11/07/announcing-the-new-sharepointcontext-helper-in-apps-for-sharepoint-2013.aspx)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga.md b/docs/sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga.md
index 102510eb01..88fb9f6d5a 100644
--- a/docs/sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga.md
+++ b/docs/sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga.md
@@ -1,8 +1,15 @@
+---
+title: Create provider-hosted SharePoint Add-ins to access SAP data by using the SAP Gateway for Microsoft
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create provider-hosted SharePoint Add-ins to access SAP data by using the SAP Gateway for Microsoft
 Learn how you can build a SharePoint Add-in that can access SAP data.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can create a SharePoint Add-in that reads and writes SAP data, and optionally reads and writes SharePoint data, by using SAP Gateway for Microsoft and the Azure AD Authentication Library for .NET. This article provides the procedures for how you can design the SharePoint Add-in to get authorized access to SAP. 
@@ -15,7 +22,7 @@ The following are prerequisites to the procedures in this article:
 
  
 
--  **An Office 365 Developer Site** in an Office 365 domain that is associated with a Microsoft Azure Active Directory subscription. See [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365) or [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription).
+-  **An Office 365 Developer Site** in an Office 365 domain that is associated with a Microsoft Azure Active Directory subscription. See [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md) or [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md).
     
  
 -  **Visual Studio 2013 Update 2** or later, which you can obtain from [Welcome to Visual Studio 2013](http://msdn.microsoft.com/library/dd831853.aspx).
@@ -36,13 +43,13 @@ The following are prerequisites to the procedures in this article:
 -  **A basic familiarity with Azure AD.** See [Getting started with Azure AD](http://msdn.microsoft.com/library/azure/dn655157.aspx).
     
  
--  **A basic familiarity with creating SharePoint Add-ins.** See [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+-  **A basic familiarity with creating SharePoint Add-ins.** See [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
     
  
 -  **A basic familiarity OAuth 2.0 in Azure AD**. See  [OAuth 2.0 in Azure AD](http://msdn.microsoft.com/library/azure/dn645545.aspx) and its child topics.
     
  
- **Code sample:** [SharePoint: Using the SAP Gateway to Microsoft in a SharePoint Add-in](http://code.msdn.microsoft.com/SharePoint-2013-Using-the-0931abce)
+ **Code sample:** [SharePoint: Using the SAP Gateway to Microsoft in a SharePoint Add-in](http://code.msdn.microsoft.com/SharePoint-Using-the-0931abce)
  
 
  
@@ -50,7 +57,7 @@ The following are prerequisites to the procedures in this article:
 ## Understand authentication and authorization to SAP Gateway for Microsoft and SharePoint
 <a name="AuthOverview"> </a>
 
-OAuth 2.0 in Azure AD enables applications to access multiple resources hosted by Microsoft Azure and SAP Gateway for Microsoft is one of them. With OAuth 2.0, applications, in addition to users, are security principals. Application principals require authentication and authorization to protected resources in addition to (and sometimes instead of) users. The process involves an OAuth "flow" in which the application, which can be a SharePoint Add-in, obtains an access token (and refresh token) that is accepted by all of the Microsoft Azure-hosted services and applications that are configured to use Azure AD as an OAuth 2.0 authorization server. The process is very similar to the way that the remote components of a provider-hosted SharePoint Add-in gets authorization to SharePoint as described in  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization) and its child articles. However, the ACS authorization system uses Microsoft Azure Access Control Service (ACS) as the trusted token issuer rather than Azure AD.
+OAuth 2.0 in Azure AD enables applications to access multiple resources hosted by Microsoft Azure and SAP Gateway for Microsoft is one of them. With OAuth 2.0, applications, in addition to users, are security principals. Application principals require authentication and authorization to protected resources in addition to (and sometimes instead of) users. The process involves an OAuth "flow" in which the application, which can be a SharePoint Add-in, obtains an access token (and refresh token) that is accepted by all of the Microsoft Azure-hosted services and applications that are configured to use Azure AD as an OAuth 2.0 authorization server. The process is very similar to the way that the remote components of a provider-hosted SharePoint Add-in gets authorization to SharePoint as described in  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md) and its child articles. However, the ACS authorization system uses Microsoft Azure Access Control Service (ACS) as the trusted token issuer rather than Azure AD.
  
 
  
@@ -58,7 +65,7 @@ OAuth 2.0 in Azure AD enables applications to access multiple resources hosted b
  **Tip**  If your SharePoint Add-in accesses SharePoint in addition to accessing SAP Gateway for Microsoft, then it will need to use  *both*  systems: Azure AD to get an access token to SAP Gateway for Microsoft and the ACS authorization system to get an access token to SharePoint. The tokens from the two sources are not interchangeable. For more information, see [Optionally, add SharePoint access to the ASP.NET application](#SharePoint).
  
 
-For a detailed description and diagram of the OAuth flow used by OAuth 2.0 in Azure AD, see  [Authorization Code Grant Flow](http://msdn.microsoft.com/library/azure/dn645542.aspx). (For a similar description, and a diagram, of the flow for accessing SharePoint, see  [See the steps in the Context Token flow](context-token-oauth-flow-for-sharepoint-add-ins#OAuth_ProcessFlowSteps).)
+For a detailed description and diagram of the OAuth flow used by OAuth 2.0 in Azure AD, see  [Authorization Code Grant Flow](http://msdn.microsoft.com/library/azure/dn645542.aspx). (For a similar description, and a diagram, of the flow for accessing SharePoint, see  [See the steps in the Context Token flow](context-token-oauth-flow-for-sharepoint-add-ins.md#OAuth_ProcessFlowSteps).)
  
 
  
@@ -450,7 +457,7 @@ using Newtonsoft.Json.Linq;
 
 
      **Important**  Delete this line when you are ready to deploy the ASP.NET application to staging. See  [Modify the add-in and stage it to Azure and Office 365](#Stage).
-5. Add the following code to the  **Page_Load** method. The string you pass to the `GetSAPData` method is an OData query.
+1. Add the following code to the  **Page_Load** method. The string you pass to the `GetSAPData` method is an OData query.
     
 ```
   if (!IsPostBack)
@@ -509,7 +516,7 @@ using Newtonsoft.Json.Linq;
 </div>
 ```
 
-2. Optionally, give the web page the "look 'n' feel" of a SharePoint page with the SharePoint  [Chrome Control](use-the-client-chrome-control-in-sharepoint-add-ins) and [the host SharePoint website's style sheet](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins).
+2. Optionally, give the web page the "look 'n' feel" of a SharePoint page with the SharePoint  [Chrome Control](use-the-client-chrome-control-in-sharepoint-add-ins.md) and [the host SharePoint website's style sheet](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md).
     
  
 
@@ -532,7 +539,7 @@ using Newtonsoft.Json.Linq;
 ## Optionally, add SharePoint access to the ASP.NET application
 <a name="SharePoint"> </a>
 
-Of course, your SharePoint Add-in doesn't have to expose only SAP data in a web page launched from SharePoint. It can also create, read, update, and delete (CRUD) SharePoint data. Your code behind can do this using either the SharePoint client object model (CSOM) or the REST APIs of SharePoint. The CSOM is deployed as a pair of assemblies that the Office Developer Tools for Visual Studio automatically included in the ASP.NET project and set to  **Copy Local** in Visual Studio so that they are included in the ASP.NET application package. For information about using CSOM, start with [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code). For information about using the REST APIs, start with  [Understanding and Using the SharePoint REST Interface](http://msdn.microsoft.com/en-us/magazine/dn198245.aspx). 
+Of course, your SharePoint Add-in doesn't have to expose only SAP data in a web page launched from SharePoint. It can also create, read, update, and delete (CRUD) SharePoint data. Your code behind can do this using either the SharePoint client object model (CSOM) or the REST APIs of SharePoint. The CSOM is deployed as a pair of assemblies that the Office Developer Tools for Visual Studio automatically included in the ASP.NET project and set to  **Copy Local** in Visual Studio so that they are included in the ASP.NET application package. For information about using CSOM, start with [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md). For information about using the REST APIs, start with  [Understanding and Using the SharePoint REST Interface](http://msdn.microsoft.com/en-us/magazine/dn198245.aspx). 
  
 
  
@@ -541,19 +548,19 @@ Regardless, of whether you use CSOM or the REST APIs to access SharePoint, your
 
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins)
+-  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins.md)
     
  
--  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization)
+-  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md)
     
  
--  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+-  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
     
  
 
@@ -672,7 +679,7 @@ When you have finished debugging the SharePoint Add-in using F5 in Visual Studio
 7. Click  **SAVE** at the bottom of the screen.
     
  
-8. Register the add-in with Azure ACS. This must be done even if the add-in does not access SharePoint and will not use tokens from ACS, because the same process also registers the add-in with the Add-in Management Service of the Office 365 subscription, which is a requirement. (It is called "Add-in Management Service" because SharePoint Add-ins were originally called "apps for SharePoint".) You perform the registration on the AppRegNew.aspx page of any SharePoint website in the Office 365 subscription. For details, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013). As part of this process you will obtain a new client ID and client secret. Insert these values in the web.config for the  **ClientId** (not **ida:ClientID**) and  **ClientSecret** keys.
+8. Register the add-in with Azure ACS. This must be done even if the add-in does not access SharePoint and will not use tokens from ACS, because the same process also registers the add-in with the Add-in Management Service of the Office 365 subscription, which is a requirement. (It is called "Add-in Management Service" because SharePoint Add-ins were originally called "apps for SharePoint".) You perform the registration on the AppRegNew.aspx page of any SharePoint website in the Office 365 subscription. For details, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md). As part of this process you will obtain a new client ID and client secret. Insert these values in the web.config for the  **ClientId** (not **ida:ClientID**) and  **ClientSecret** keys.
     
      **Caution**  If for any reason you press F5 after making this change, the Office Developer Tools for Visual Studio will overwrite one or both of these values. For that reason, you should keep a record of the values obtained with AppRegNew.aspx and always verify that the values in the web.config are correct just before you publish the ASP.NET application. 
 
@@ -700,7 +707,7 @@ When you have finished debugging the SharePoint Add-in using F5 in Visual Studio
 7. After the add-in has installed, click it's icon on the  **Site Contents** page to launch the add-in.
     
  
-For more information about installing SharePoint Add-ins, see  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options).
+For more information about installing SharePoint Add-ins, see  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md).
  
 
 ## Deploying the add-in to production
diff --git a/docs/sp-add-ins/create-sharepoint-add-ins-in-visual-studio.md b/docs/sp-add-ins/create-sharepoint-add-ins-in-visual-studio.md
index f0e576c1a6..7407cb6716 100644
--- a/docs/sp-add-ins/create-sharepoint-add-ins-in-visual-studio.md
+++ b/docs/sp-add-ins/create-sharepoint-add-ins-in-visual-studio.md
@@ -1,8 +1,15 @@
+---
+title: Create SharePoint Add-ins in Visual Studio
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create SharePoint Add-ins in Visual Studio
 Learn to develop SharePoint Add-ins by using templates for projects and project items in Visual Studio.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can develop SharePoint Add-ins by using new templates for projects and project items in  **vsnv**. 
@@ -39,14 +46,14 @@ Creates a SharePoint Add-in based on the information that you specify in a wizar
 - The type of add-in that you want to create: provider-hosted or SharePoint-hosted. 
     
  
-For more information, see  [SharePoint Add-ins](sharepoint-add-ins).
+For more information, see  [SharePoint Add-ins](sharepoint-add-ins.md).
  
 
  
 
 ### Cloud Business Add-in
 
-By using the  **Cloud Business Add-in** template in Visual Studio, you can create a SharePoint-hosted add-in in which mobile users can view, add, and update data from remote locations by using modern, touch-oriented devices such as phones and tablets. For more information, see [Create cloud business add-ins](create-cloud-business-add-ins).
+By using the  **Cloud Business Add-in** template in Visual Studio, you can create a SharePoint-hosted add-in in which mobile users can view, add, and update data from remote locations by using modern, touch-oriented devices such as phones and tablets. For more information, see [Create cloud business add-ins](create-cloud-business-add-ins.md).
  
 
  
@@ -77,7 +84,7 @@ Adds a client web part to your SharePoint Add-in. By adding a client web part, y
 |**Property Name**|**Description**|
 |:-----|:-----|
 |ClientWebPart|Specifies the name, the title, the description, and the dimensions of the client web part.|
-|Content|Defines the location of the page that renders inside the client web part. This element has two properties:  `Type` and `Src`.  `Type` specifies the type of web part that you're creating, such as HTML. `Src` defines the location of the page that will render inside the client web part. The template references properties on the query string by using the pattern _ _PropertyName__, such as  `Src="~addinWebUrl/Pages/ClientWebPart1.aspx?Property1=_property1_"`For more information, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in).|
+|Content|Defines the location of the page that renders inside the client web part. This element has two properties:  `Type` and `Src`.  `Type` specifies the type of web part that you're creating, such as HTML. `Src` defines the location of the page that will render inside the client web part. The template references properties on the query string by using the pattern _ _PropertyName__, such as  `Src="~addinWebUrl/Pages/ClientWebPart1.aspx?Property1=_property1_"`For more information, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md).|
 
 ### Content Type
 
@@ -106,7 +113,7 @@ Adds two project items to your SharePoint Add-in: a list definition and an insta
 
 ### Menu Item Custom Action
 
-Adds a project item that extends the UI of its host site by adding an action to a list menu. The menu custom action contains an Elements.xml file, which you use to define the properties of the action. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins).
+Adds a project item that extends the UI of its host site by adding an action to a list menu. The menu custom action contains an Elements.xml file, which you use to define the properties of the action. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md).
  
 
  
@@ -120,14 +127,14 @@ Adds a module project item to your SharePoint Add-in. Modules are basically cont
 
 ### Remote Event Receiver
 
-Adds a project item for a remote event receiver to your SharePoint Add-in and a web application project to your solution, if such a project isn't already present. The web application contains a web service that's associated with the remote event receiver in your SharePoint Add-in. The web service contains a Visual Basic or Visual C# code file whose code executes when a list, a list item, or a web item event occurs in the SharePoint Add-in. If a web application is present, it's associated with the SharePoint Add-in, and the web service is added to that application. For more information, see  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins).
+Adds a project item for a remote event receiver to your SharePoint Add-in and a web application project to your solution, if such a project isn't already present. The web application contains a web service that's associated with the remote event receiver in your SharePoint Add-in. The web service contains a Visual Basic or Visual C# code file whose code executes when a list, a list item, or a web item event occurs in the SharePoint Add-in. If a web application is present, it's associated with the SharePoint Add-in, and the web service is added to that application. For more information, see  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md).
  
 
  
 
 ### Ribbon Custom Action
 
-Adds a project item that extends the UI of its host site by adding an action to a ribbon. The ribbon custom action contains an Elements.xml file, which defines the properties of the action. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins).
+Adds a project item that extends the UI of its host site by adding an action to a ribbon. The ribbon custom action contains an Elements.xml file, which defines the properties of the action. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md).
  
 
  
@@ -189,6 +196,6 @@ Adds a project item for a workflow custom activity to your SharePoint Add-in. By
 <a name="SP15Projecttemplates_addlresources"> </a>
 
 
--  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins)
+-  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users.md b/docs/sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users.md
index 196831d401..8b92cf2dca 100644
--- a/docs/sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users.md
+++ b/docs/sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users.md
@@ -1,8 +1,15 @@
+---
+title: Create SharePoint Add-ins that can be used by anonymous users
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create SharePoint Add-ins that can be used by anonymous users
 Learn how to create SharePoint Add-ins that can be used by anonymous users on public-facing Microsoft SharePoint sites.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -14,9 +21,9 @@ Learn how to create SharePoint Add-ins that can be used by anonymous users on pu
 
 Anonymous access is possible for SharePoint-hosted and provider-hosted SharePoint Add-ins. Depending on which type you create, review one of the following sets of prerequisites:
  
--  [Get Started Creating SharePoint Hosted SharePoint add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins#SP15SPhostedapps_bk_prereqs)
+-  [Get Started Creating SharePoint Hosted SharePoint add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
--  [Get Started Creating Provider-Hosted SharePoint add-ins](get-started-creating-provider-hosted-sharepoint-add-ins#SP15createselfhostapp_bk_prereq)
+-  [Get Started Creating Provider-Hosted SharePoint add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 You will also need a site collection in your test SharePoint installation that is configured for anonymous access. If you have an Office 365 Developer Site, there is already a public site collection associated with it that uses a special Public Website site definition. (For more information about the use of Public Websites in Microsoft SharePoint Online, see  [Public Website help for Office 365](http://office.microsoft.com/en-gb/office365-sharepoint-online-enterprise-help/public-website-help-for-office-365-HA102891740.aspx?CTT=1).) That site definition is not available for on premises SharePoint installations. So if your test installation is on-premises, you will need:
@@ -88,20 +95,20 @@ For details about the add-in-only policy (with code snippets), add-in permission
 
  
 
--  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint-2013)
+-  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint.md)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in)
+-  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md)
     
  
 
 ## Creating SharePoint-hosted add-ins that are anonymously accessible
 <a name="SP-hosted"> </a>
 
-Creating a SharePoint-hosted add-in that can be run by anonymous users does not require any special techniques. You create it the same way you would create any SharePoint-hosted add-in. For details, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins) and [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013).
+Creating a SharePoint-hosted add-in that can be run by anonymous users does not require any special techniques. You create it the same way you would create any SharePoint-hosted add-in. For details, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md) and [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md).
  
 
  
@@ -250,7 +257,7 @@ If you are developing a SharePoint-hosted add-in and it accesses a SharePoint li
 <a name="bk_addresources"> </a>
 
 
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/create-ux-components-in-sharepoint.md b/docs/sp-add-ins/create-ux-components-in-sharepoint.md
index bba7ac7fa1..cc84182d92 100644
--- a/docs/sp-add-ins/create-ux-components-in-sharepoint.md
+++ b/docs/sp-add-ins/create-ux-components-in-sharepoint.md
@@ -1,8 +1,15 @@
+---
+title: Create UX components in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Create UX components in SharePoint
 Learn how to create UX components for your add-ins in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -19,17 +26,17 @@ The model for SharePoint Add-ins offers many UX components and mechanisms that h
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)|You can reference the style sheet of a SharePoint website in your SharePoint Add-in and use it to style your webpages by using the style sheet in SharePoint. In addition, if someone changes the SharePoint website's style sheet or theme, you can adopt the new set of styles in your add-in without modifying the style sheet reference in your add-in.|
-| [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)|The chrome control in SharePoint enables you to use the header styling of a specific SharePoint site in your add-in without needing to register a server library or use a specific technology or tool. To use this functionality, you must register a SharePoint JavaScript library through a standard <script> tag. You can provide a placeholder by using an HTML **div** element and further customize the control by using the available options. The control inherits its appearance from the specified SharePoint website.|
-| [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)|With add-in parts, you can show your add-in user experience right in the host web. An add-in part displays your add-in content using an  **IFrame**. End users can customize the experience using the custom properties that you can provide for your add-in part. The add-in webpage receives the custom property values through parameters in the query string.|
-| [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)|When you are creating a SharePoint Add-in, custom actions let you interact with the lists and the ribbon in the host web. A custom action deploys to the host web when end users install your add-in. Custom actions can open a remote webpage and pass information through the query string. There are two types of custom actions available for add-ins: Ribbon and Edit Control Block.|
-| [Customize a list view in SharePoint Add-ins using client-side rendering](customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering)|Client-side rendering provides a mechanism that you can use to produce your own output for a set of controls that are hosted in a SharePoint page. This mechanism enables you to use well-known technologies, such as HTML and JavaScript, to define the rendering logic of SharePoint list views. In client-side rendering, you can specify your own JavaScript resources and host them in the data storage options available to your add-ins, such as a document library.|
-| [Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins](use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-ins)|Learn how to use the client-side People Picker control in SharePoint Add-ins. The client-side People Picker control lets users quickly search for and select valid user accounts for people, groups, and claims in their organization. The picker is an HTML and JavaScript control that provides cross-browser support.|
+| [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)|You can reference the style sheet of a SharePoint website in your SharePoint Add-in and use it to style your webpages by using the style sheet in SharePoint. In addition, if someone changes the SharePoint website's style sheet or theme, you can adopt the new set of styles in your add-in without modifying the style sheet reference in your add-in.|
+| [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)|The chrome control in SharePoint enables you to use the header styling of a specific SharePoint site in your add-in without needing to register a server library or use a specific technology or tool. To use this functionality, you must register a SharePoint JavaScript library through a standard <script> tag. You can provide a placeholder by using an HTML **div** element and further customize the control by using the available options. The control inherits its appearance from the specified SharePoint website.|
+| [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)|With add-in parts, you can show your add-in user experience right in the host web. An add-in part displays your add-in content using an  **IFrame**. End users can customize the experience using the custom properties that you can provide for your add-in part. The add-in webpage receives the custom property values through parameters in the query string.|
+| [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)|When you are creating a SharePoint Add-in, custom actions let you interact with the lists and the ribbon in the host web. A custom action deploys to the host web when end users install your add-in. Custom actions can open a remote webpage and pass information through the query string. There are two types of custom actions available for add-ins: Ribbon and Edit Control Block.|
+| [Customize a list view in SharePoint Add-ins using client-side rendering](customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md)|Client-side rendering provides a mechanism that you can use to produce your own output for a set of controls that are hosted in a SharePoint page. This mechanism enables you to use well-known technologies, such as HTML and JavaScript, to define the rendering logic of SharePoint list views. In client-side rendering, you can specify your own JavaScript resources and host them in the data storage options available to your add-ins, such as a document library.|
+| [Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins](use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-ins.md)|Learn how to use the client-side People Picker control in SharePoint Add-ins. The client-side People Picker control lets users quickly search for and select valid user accounts for people, groups, and claims in their organization. The picker is an HTML and JavaScript control that provides cross-browser support.|
 
 ## Next steps: Working with data in SharePoint Add-ins
 <a name="SP15CreateUX_Next"> </a>
 
-Have you finished designing a great UX for your add-in? Incorporate data with the mechanisms available to you in the model for SharePoint Add-ins. For more information, see  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013).
+Have you finished designing a great UX for your add-in? Incorporate data with the mechanisms available to you in the model for SharePoint Add-ins. For more information, see  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md).
  
 
  
@@ -38,13 +45,13 @@ Have you finished designing a great UX for your add-in? Incorporate data with th
 <a name="SP15CreateUX_AddRes"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization.md b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization.md
index 1c0dee83d5..0b4238b32f 100644
--- a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization.md
+++ b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization.md
@@ -1,8 +1,15 @@
+---
+title: Creating SharePoint Add-ins that use high-trust authorization
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Creating SharePoint Add-ins that use high-trust authorization
 Learn about high-trust SharePoint Add-ins, which use digital certificates to establish trust between SharePoint and the remote components that access SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
  **Provided by:**
@@ -20,7 +27,7 @@ A high-trust add-in is a provider-hosted SharePoint Add-in that is installed to
 
  
 
- **Note**   This topic helps you understand the high-trust authorization system for SharePoint Add-ins. For practical information about creating and deploying high-trust add-ins, see the following topics: [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins) [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins)
+ **Note**   This topic helps you understand the high-trust authorization system for SharePoint Add-ins. For practical information about creating and deploying high-trust add-ins, see the following topics: [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md) [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md)
  
 
 In SharePoint, the security token service (STS) provides access tokens for server-to-server authentication. The STS enables temporary access tokens to access other application services such as Exchange 2013, Lync 2013, and SharePoint Add-ins. A farm administrator establishes trust between SharePoint and the other application or add-in by using Windows PowerShell cmdlets and a certificate. Each certificate that is used must be trusted by SharePoint using the  `New-SPTrustedRootAuthority` cmdlet. Also each certificate must be registered with SharePoint as a token issuer using the `New-SPTrustedSecurityTokenIssuer` cmdlet.
@@ -62,7 +69,7 @@ $fullIssuerIdentifier = "<client_ID_of_SP_app> " + "@" + "<realm_GUID> "
 New-SPTrustedSecurityTokenIssuer -RegisteredIssuerName $fullIssuerIdentifier --other parameters omitted--
 ```
 
-Typically, the  `New-SPTrustedSecurityTokenIssuer` cmdlet is used in a script that performs other tasks to configure SharePoint for high-trust add-ins. For more information about such scripts and complete examples of the `New-SPTrustedSecurityTokenIssuer` cmdlet, see [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint-2013).
+Typically, the  `New-SPTrustedSecurityTokenIssuer` cmdlet is used in a script that performs other tasks to configure SharePoint for high-trust add-ins. For more information about such scripts and complete examples of the `New-SPTrustedSecurityTokenIssuer` cmdlet, see [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint.md).
  
 
  
@@ -93,7 +100,7 @@ To get the still trustworthy SharePoint Add-ins working again, the administrator
  
 
  
-The benefit of using one certificate per add-in is that it makes it easier to break trust with a particular add-in, because the certificates that are used by the still trustworthy add-ins are not affected when the administrator breaks trust with the certificate of the one add-in. The disadvantage in this strategy is that an administrator has more certificates to acquire and SharePoint must be configured to use each of them, which can be done with a reusable script as shown in  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint-2013).
+The benefit of using one certificate per add-in is that it makes it easier to break trust with a particular add-in, because the certificates that are used by the still trustworthy add-ins are not affected when the administrator breaks trust with the certificate of the one add-in. The disadvantage in this strategy is that an administrator has more certificates to acquire and SharePoint must be configured to use each of them, which can be done with a reusable script as shown in  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint.md).
  
 
  
@@ -124,7 +131,7 @@ New-SPTrustedRootAuthority -Name "<name_of_certificate>" -Certificate $certifica
 
 ```
 
-The root and intermediate certificates should be added only once on a SharePoint farm. Typically, the web application's certificate is added in a separate script that does other configuration too, such as the call to  `New-SPTrustedSecurityTokenIssuer`. For examples, see  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint-2013).
+The root and intermediate certificates should be added only once on a SharePoint farm. Typically, the web application's certificate is added in a separate script that does other configuration too, such as the call to  `New-SPTrustedSecurityTokenIssuer`. For examples, see  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint.md).
  
 
  
@@ -140,7 +147,7 @@ For more information, see the blog post  [Root of certificate chain not trusted
 ## Web application needs to know that it is a token issuer
 <a name="AppIsTokenIssuer"> </a>
 
-The remote web application component of the SharePoint Add-in is bound to its certificate in IIS. This is sufficient for the traditional purposes of certificates: securely identifying the web application and encoding the HTTP requests and responses. However, in a high-trust SharePoint Add-in, the certificate has the additional task of being the official "issuer" of the access tokens that the web application sends to SharePoint. For this purpose, web application has to know the issuer ID of the certificate that is used when registering the certificate as a token issuer with SharePoint. The web application gets this ID from the  **appSettings** section of the web.config file, where there is a key named **IssuerId**. Instructions for how the add-in developer sets this value, and how the certificate is bound to the web application in IIS, are in  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins). Note that if the customer is using the strategy of having a separate certificate for each high-trust SharePoint Add-in, then the  **ClientId** value is also used as the **IssuerId** value. This is not the case when multiple add-ins share the same certificate, because each SharePoint Add-in must have its own unique client ID, but the issuer ID is the identifier for a **SPTrustedSecurityTokenIssuer** object.
+The remote web application component of the SharePoint Add-in is bound to its certificate in IIS. This is sufficient for the traditional purposes of certificates: securely identifying the web application and encoding the HTTP requests and responses. However, in a high-trust SharePoint Add-in, the certificate has the additional task of being the official "issuer" of the access tokens that the web application sends to SharePoint. For this purpose, web application has to know the issuer ID of the certificate that is used when registering the certificate as a token issuer with SharePoint. The web application gets this ID from the  **appSettings** section of the web.config file, where there is a key named **IssuerId**. Instructions for how the add-in developer sets this value, and how the certificate is bound to the web application in IIS, are in  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md). Note that if the customer is using the strategy of having a separate certificate for each high-trust SharePoint Add-in, then the  **ClientId** value is also used as the **IssuerId** value. This is not the case when multiple add-ins share the same certificate, because each SharePoint Add-in must have its own unique client ID, but the issuer ID is the identifier for a **SPTrustedSecurityTokenIssuer** object.
  
 
  
@@ -191,16 +198,16 @@ Developers will have to understand the requirements for application security as
 <a name="AR"> </a>
 
 
--  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins)
+-  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md)
     
  
--  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins)
+-  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md)
     
  
 -  [Troubleshooting tips for high trust add-ins on SharePoint](http://blogs.technet.com/b/speschka/archive/2012/11/01/more-troubleshooting-tips-for-high-trust-apps-on-sharepoint-2013.aspx)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization.md b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization.md
index 45402f462e..3279ea4c7d 100644
--- a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization.md
+++ b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization.md
@@ -1,14 +1,21 @@
+---
+title: Creating SharePoint Add-ins that use low-trust authorization
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Creating SharePoint Add-ins that use low-trust authorization
 Learn about the low-trust authorization system for SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Remote components in a SharePoint Add-in (or external application) can gain authorization to SharePoint resources by passing an access token to SharePoint with each HTTP request. The remote components obtain the access token from a Microsoft Azure Access Control Service (ACS) account that is associated with the customer's Office 365 tenancy. Azure ACS acts as the authorization server in an  [OAuth 2.0](http://oauth.net/) transaction, called aflow, with SharePoint as the resource server and the remote components as the client. For related protocol specifications, see  [Web Authorization Protocol (oauth)](http://datatracker.ietf.org/doc/active/#oauth). 
  
 
-Provider-hosted SharePoint Add-ins that use low-trust authorization system can be sold in the Office Store and installed on either Microsoft SharePoint Online or an on-premise SharePoint farm that has been configured to use the customer's Office 365 tenancy to establish trust with Azure ACS. The customer must have an Office 365 tenancy to install SharePoint Add-ins that use the low-trust system. However, it is not necessary for the customer to use the tenancy for any other purpose. For instructions about linking an on-premise farm to a Office 365 tenancy, see  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on-premises-sharepoint-site).
+Provider-hosted SharePoint Add-ins that use low-trust authorization system can be sold in the Office Store and installed on either Microsoft SharePoint Online or an on-premise SharePoint farm that has been configured to use the customer's Office 365 tenancy to establish trust with Azure ACS. The customer must have an Office 365 tenancy to install SharePoint Add-ins that use the low-trust system. However, it is not necessary for the customer to use the tenancy for any other purpose. For instructions about linking an on-premise farm to a Office 365 tenancy, see  [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md).
  
 
 
@@ -23,14 +30,14 @@ To use the low-trust system, the SharePoint Add-in must first be registered with
  **Note**  Registration requires that the application have an Internet domain. Any existing domain can be used for this purpose, but you can't be 100% certain that any domain you don't own will always exist, so a web application would need to be part of a native device application even if the web application component played no other role than to enable registration. For an advanced code sample that is designed in this way, see  [Provision sites in batches with the add-in model](http://code.msdn.microsoft.com/Provision-sites-in-batches-fcf31bc6).
  
 
-For more information on registration, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013).
+For more information on registration, see  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md).
  
 
  
 
 ### Add-in secret expiration
 
-The add-in secret must be replaced every 12 months. For details, see  [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in).
+The add-in secret must be replaced every 12 months. For details, see  [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in.md).
  
 
  
@@ -49,7 +56,7 @@ A SharePoint Add-in can be designed to use either of two authorization policies:
 -  **App-only Policy:** Add-ins that use this policy can perform any action that it has permission to do, even if the user does not have permission for the action. The developer must request that this policy be used in the add-in manifest of the add-in. The request must be approved by the user who installs the add-in. This policy is allowed for only provider-hosted SharePoint Add-ins.
     
  
-For more information about authorization policies, see  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint-2013).
+For more information about authorization policies, see  [Add-in authorization policy types in SharePoint](add-in-authorization-policy-types-in-sharepoint.md).
  
 
  
@@ -66,10 +73,10 @@ There are two major OAuth flows used by SharePoint. One is for cloud-hosted Shar
 
  
 
--  **Context Token flow:** The remote component of the SharePoint Add-in uses the SharePoint client object model (CSOM) or REST endpoints to make calls to SharePoint. SharePoint requests a context token from ACS that it can send to the remote server. The remote server uses the context token to request an access token from the ACS. The remote server then uses the access token to talk back to SharePoint. For details about this flow, see [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins).
+-  **Context Token flow:** The remote component of the SharePoint Add-in uses the SharePoint client object model (CSOM) or REST endpoints to make calls to SharePoint. SharePoint requests a context token from ACS that it can send to the remote server. The remote server uses the context token to request an access token from the ACS. The remote server then uses the access token to talk back to SharePoint. For details about this flow, see [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md).
     
  
--  **Authenticaton Code flow:** a SharePoint Add-in is granted the permissions it needs to SharePoint resources when it is installed. But applications that are not installed on SharePoint must ask for permissions "on the fly," that is, each time they run. There is no SharePoint context token in this flow. Instead, when the add-in runs and attempts to access SharePoint, SharePoint prompts the user to grant the permissions to the application that it is requesting. When the user grants the permissions, SharePoint obtains an authorization code from ACS which it passes to the application. The application uses the code to obtain an access token from ACS which it can then use to talk to SharePoint. For details about this flow, see [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins).
+-  **Authenticaton Code flow:** a SharePoint Add-in is granted the permissions it needs to SharePoint resources when it is installed. But applications that are not installed on SharePoint must ask for permissions "on the fly," that is, each time they run. There is no SharePoint context token in this flow. Instead, when the add-in runs and attempts to access SharePoint, SharePoint prompts the user to grant the permissions to the application that it is requesting. When the user grants the permissions, SharePoint obtains an authorization code from ACS which it passes to the application. The application uses the code to obtain an access token from ACS which it can then use to talk to SharePoint. For details about this flow, see [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md).
     
  
 
@@ -186,19 +193,19 @@ clientContext.ExecuteQuery();
 ## In this section
 <a name="Trouble"> </a>
 
- [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on-premises-sharepoint-site)
+ [Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site](use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md)
  
 
  
- [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+ [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
  
 
  
- [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins)
+ [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md)
  
 
  
- [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in)
+ [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in.md)
  
 
  
@@ -207,7 +214,7 @@ clientContext.ExecuteQuery();
 <a name="FileName_AdditionalResources"> </a>
 
 
--  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013)
+-  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library.md b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library.md
index 0e3069938a..22ef1c38e7 100644
--- a/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library.md
+++ b/docs/sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library.md
@@ -1,8 +1,15 @@
+---
+title: Creating SharePoint Add-ins that use the cross-domain library
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Creating SharePoint Add-ins that use the cross-domain library
 Learn about the SharePoint cross-domain JavaScript library.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 There are some scenarios in which neither the low-trust nor the high-trust authorization systems can be used by a SharePoint Add-in, or they are not a good choice as the only means for the add-in to gain authorization to SharePoint resources. Examples:
@@ -43,7 +50,7 @@ Of course, the remote components of the SharePoint Add-in still have to have aut
 
  
 
-- Set the add-in principal type to  **RemoteWebApplication** (the default for provider-hosted apps) in the add-in manifest. When the add-in is registered with ACS, the registration includes the domain of the remote web application. SharePoint trusts domains that are registered with ACS, even though it is not, in this scenario, using any of the token passing flows that are part of the server-side low-trust system. For detailed information about registering add-ins, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013). 
+- Set the add-in principal type to  **RemoteWebApplication** (the default for provider-hosted apps) in the add-in manifest. When the add-in is registered with ACS, the registration includes the domain of the remote web application. SharePoint trusts domains that are registered with ACS, even though it is not, in this scenario, using any of the token passing flows that are part of the server-side low-trust system. For detailed information about registering add-ins, see [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md). 
     
  
 - In a SharePoint-hosted add-in, you can leave the add-in principal type set to its default, which is  **Internal**. Then set the  **AllowedRemoteHostUrl** attribute of the **Internal** element to the URL of the remote web application, as in the following example.
@@ -58,7 +65,7 @@ Of course, the remote components of the SharePoint Add-in still have to have aut
  **Note**  If you use the second option (an  **Internal** add-in principal), then you can use only JavaScript and the cross-domain library to access SharePoint. The SharePoint client object model is blocked for **Internal**SharePoint Add-ins, so you cannot have a dual authorization system that uses both the cross-domain library and either the low-trust or high-trust systems.
  
 
-For details on how to use the library, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+For details on how to use the library, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
  
 
  
@@ -66,7 +73,7 @@ For details on how to use the library, see  [Access SharePoint data from add-ins
 ## Access remote data from a SharePoint page
 <a name="ReverseDirection"> </a>
 
-The SharePoint cross-domain library can also be used in the reverse direction; that is, JavaScript on a SharePoint page can use the library to get data from the remote components of the add-in. To do this, you reverse the cross-domain architecture: you create a proxy page in the remote web application. The library is called from a SharePoint page where it creates an iFrame to host the proxy page. For details on how to use the library in this way, see  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013).
+The SharePoint cross-domain library can also be used in the reverse direction; that is, JavaScript on a SharePoint page can use the library to get data from the remote components of the add-in. To do this, you reverse the cross-domain architecture: you create a proxy page in the remote web application. The library is called from a SharePoint page where it creates an iFrame to host the proxy page. For details on how to use the library in this way, see  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md).
  
 
  
@@ -75,10 +82,10 @@ The SharePoint cross-domain library can also be used in the reverse direction; t
 <a name="ReverseDirection"> </a>
 
 
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
--  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-zones-in-sharepoint-add-ins)
+-  [Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins](work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md)
     
  
 
diff --git a/docs/sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md b/docs/sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md
index 2dd18cf3d8..4f265b6104 100644
--- a/docs/sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md
+++ b/docs/sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md
@@ -1,8 +1,15 @@
+---
+title: Customize a list view in SharePoint Add-ins using client-side rendering
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Customize a list view in SharePoint Add-ins using client-side rendering
 Learn how to customize a list view in a SharePoint-hosted add-in by using the client-side rendering technology in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 In SharePoint, client-side rendering provides a way for you to produce your own output for a set of controls that are hosted in a SharePoint page. It enables you to use well-known technologies, such as HTML and JavaScript, to define the rendering logic of SharePoint list views. With client-side rendering, you can specify your own JavaScript resources and host them in the data storage options that are available to your add-ins, such as in a document library. A SharePoint-hosted add-in includes only SharePoint components. A SharePoint-hosted add-in has its resources in an isolated subsite of the host web, called the add-in web.
@@ -39,9 +46,9 @@ The following table lists useful articles that can help you understand the conce
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in Microsoft SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)|Learn about the UX options that you have when you are building SharePoint Add-ins.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in Microsoft SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)|Learn about the UX options that you have when you are building SharePoint Add-ins.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 
 ## Code example: Customize a list view by using client-side rendering
 <a name="SP15CSRlistview_Codeexample"> </a>
@@ -70,7 +77,7 @@ Figure 1 shows a client-side rendered view of an announcements list.
  
 
  
-![Custom view of an announcements list](../../images/CSRListView_result.png)
+![Custom view of an announcements list](../images/CSRListView_result.png)
  
 
 ### To create the SharePoint Add-in project
@@ -88,7 +95,7 @@ Figure 1 shows a client-side rendered view of an announcements list.
 
  
 
-  ![App for SharePoint Visual Studio template](../../images/AppForSharePointVSTemplate.PNG)
+  ![App for SharePoint Visual Studio template](../images/AppForSharePointVSTemplate.PNG)
  
 
  
@@ -244,19 +251,19 @@ This article demonstrated how to customize a list view in a SharePoint Add-in by
 
  
 
--  [Code sample: Customize a list view in an add-in using client-side rendering](http://code.msdn.microsoft.com/SharePoint-2013-Customize-61761017)
+-  [Code sample: Customize a list view in an add-in using client-side rendering](http://code.msdn.microsoft.com/SharePoint-Customize-61761017)
     
  
--  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)
+-  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)
     
  
--  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)
+-  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)
     
  
--  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)
+-  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
 
@@ -264,19 +271,19 @@ This article demonstrated how to customize a list view in a SharePoint Add-in by
 <a name="SP15CSRlistview_AddResources"> </a>
 
 
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 
diff --git a/docs/sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md b/docs/sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md
index 2f9e2d55b2..02db4d9b16 100644
--- a/docs/sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md
+++ b/docs/sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Debug and troubleshoot a remote event receiver in a SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Debug and troubleshoot a remote event receiver in a SharePoint Add-in
 Set up the your development environment to debug remote events in by using Visual Studio.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -69,7 +76,7 @@ Use the procedures in this section to verify that you can debug an RER.
 
 1. In Visual Studio, create a provider-hosted SharePoint Add-in.
     
-    See  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+    See  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
     
  
 2. In  **Solution Explorer**, choose the add-in project's node.
@@ -146,7 +153,7 @@ If you have a remote event in your project and have not configured remote event
  
 
  
-![Notifications in remote event receivers](../../images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png)
+![Notifications in remote event receivers](../images/SP15Con_Remote_Event_Receivers_FAQ_fig3.png)
  
 
  
@@ -166,7 +173,7 @@ After you press F5 and trust the add-in, go to the Service Bus namespace in your
  
 
  
-![Browsing to the service bus namespace](../../images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG)
+![Browsing to the service bus namespace](../images/SP15Con_Remote_Event_Receivers_FAQ_fig4.PNG)
  
 
  
@@ -217,10 +224,10 @@ When the add-in is in Microsoft SharePoint Online, but the remote event receiver
 <a name="Additional"> </a>
 
 
--  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins)
+-  [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md)
     
  
--  [Debugging SharePoint remote events using Visual Studio 2012](http://blogs.msdn.com/b/officeapps/archive/2013/03/21/update-to-debugging-sharepoint-2013-remote-events-using-visual-studio-2012.aspx)
+-  [Debugging SharePoint remote events using Visual Studio 2012](http://blogs.msdn.com/b/officeapps/archive/2013/03/21/update-to-debugging-sharepoint-remote-events-using-visual-studio-2012.aspx)
     
  
 
diff --git a/docs/sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md
index 4ede628b14..a178b253e0 100644
--- a/docs/sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md
@@ -1,14 +1,21 @@
+---
+title: Deploy and install a SharePoint-hosted SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Deploy and install a SharePoint-hosted SharePoint Add-in
 Learn how SharePoint Add-ins are deployed and installed.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the second in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with the topic  [SharePoint Add-ins](sharepoint-add-ins) and the preceding topics in the series:
+This is the second in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with the topic  [SharePoint Add-ins](sharepoint-add-ins.md) and the preceding topics in the series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 
@@ -31,7 +38,7 @@ You'll find it a lot easier to develop SharePoint-hosted SharePoint Add-ins if y
 
  
 
-  ![Office 365 App Launcher](../../images/ec60797c-d329-4922-a811-70c64598f4d5.PNG)
+  ![Office 365 App Launcher](../images/ec60797c-d329-4922-a811-70c64598f4d5.PNG)
  
 
     
@@ -120,9 +127,10 @@ In order to continue enhancing the same SharePoint Add-in in Visual Studio (see
     
  
 
-## 
+#Next steps
+<a name="Nextsteps"></a>
 
-We strongly recommend that you continue with this series about SharePoint-hosted add-ins before you go on to the more advanced topics. Next we get back to coding in  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in).
+We strongly recommend that you continue with this series about SharePoint-hosted add-ins before you go on to the more advanced topics. Next we get back to coding in  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options.md b/docs/sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options.md
index d8edd5b81c..e05f50a010 100644
--- a/docs/sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options.md
+++ b/docs/sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options.md
@@ -1,8 +1,15 @@
+---
+title: "Deploying and installing SharePoint Add-ins: methods and options"
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Deploying and installing SharePoint Add-ins: methods and options
 Learn about the methods for publishing, installing, and uninstalling a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -98,7 +105,7 @@ The add-in's permissions are also revoked when it is removed (recycled), accordi
 - If there is no other instance of the add-in in the site subscription (tenancy), tenant-scoped permissions are also revoked.
     
  
-The  [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) web service, if one is registered in the add-in manifest of the add-in, executes at the beginning of the uninstallation process (which occurs when the add-in is removed from the second stage Recycle Bin). It is a best practice to have an [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) web service if you have an [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) web service and to design the [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) service to reverse anything done in your [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) service. For more information, see [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins).
+The  [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) web service, if one is registered in the add-in manifest of the add-in, executes at the beginning of the uninstallation process (which occurs when the add-in is removed from the second stage Recycle Bin). It is a best practice to have an [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) web service if you have an [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) web service and to design the [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af-1db4-aad5-9b7b511b4348%28Office.15%29.aspx) service to reverse anything done in your [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) service. For more information, see [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md).
  
 
  
@@ -107,13 +114,13 @@ The  [UninstallingEventEndpoint](http://msdn.microsoft.com/library/4194e44b-f2af
 <a name="SP15deployinstallapps_addlresources"> </a>
 
 
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [SharePoint Add-ins update process](sharepoint-add-ins-update-process)
+-  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md)
     
  
 
diff --git a/docs/sp-add-ins/design-sharepoint-add-ins.md b/docs/sp-add-ins/design-sharepoint-add-ins.md
index 3fce4ed28c..5bc3b185fe 100644
--- a/docs/sp-add-ins/design-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/design-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Design SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Design SharePoint Add-ins
 Get an overview of the design and architecture options that are available in SharePoint Add-ins, and learn how to make the right decisions to ease the development of your add-in in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Let's say you have a killer idea for an add-in. In this section, we'll guide you through the design decisions you need to make and offer best practices to build your add-in. For example, what makes a good user interface? What are the add-in "shapes" available? When should I use one instead of another? What options do I have for data access? 
@@ -15,7 +22,7 @@ Because the Cloud Add-in Model in SharePoint makes so many design options possib
  
 
  
-For an overview of the design and architecture options that are available with SharePoint Add-ins, see  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins). For an overview of what SharePoint Add-ins are, see  [SharePoint Add-ins](sharepoint-add-ins).
+For an overview of the design and architecture options that are available with SharePoint Add-ins, see  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md). For an overview of what SharePoint Add-ins are, see  [SharePoint Add-ins](sharepoint-add-ins.md).
  
 
  
@@ -33,7 +40,7 @@ SharePoint Add-ins support multiple hosting options. You can choose your own web
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in)|Learn about the different ways that you can host the components of SharePoint Add-ins.|
+| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md)|Learn about the different ways that you can host the components of SharePoint Add-ins.|
 
 ## Choose the right data access technologies for your add-in
 <a name="SP15Design_Dataaccess"> </a>
@@ -48,7 +55,7 @@ You must ensure that your add-in accesses data efficiently and securely. Various
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)| Learn about data access options you have when you build SharePoint Add-ins, including data connectivity options for inbound and outbound data scenarios, and the APIs that are available when you want to access SharePoint data from your add-in.|
+| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)| Learn about data access options you have when you build SharePoint Add-ins, including data connectivity options for inbound and outbound data scenarios, and the APIs that are available when you want to access SharePoint data from your add-in.|
 
 ## Design the UX for your add-in
 <a name="SP15Design_UX"> </a>
@@ -63,12 +70,12 @@ As you design your add-in, your real goal should be to create an experience that
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)|Learn about the user experience options that you have when you build SharePoint Add-ins.|
+| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)|Learn about the user experience options that you have when you build SharePoint Add-ins.|
 
 ## Design with update in mind
 <a name="Upgrade"> </a>
 
-Someday you may want to produce an update of your add-in and upload it to the Office Store or an organization's add-in catalog. That task will be a lot easier if you think about how you would update the add-in while you are designing the first version. We recommend that you read the following articles early in the design phase:  [SharePoint Add-ins update process](sharepoint-add-ins-update-process) and [Update SharePoint Add-ins](update-sharepoint-add-ins). 
+Someday you may want to produce an update of your add-in and upload it to the Office Store or an organization's add-in catalog. That task will be a lot easier if you think about how you would update the add-in while you are designing the first version. We recommend that you read the following articles early in the design phase:  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md) and [Update SharePoint Add-ins](update-sharepoint-add-ins.md). 
  
 
  
@@ -86,8 +93,8 @@ Have a solid design for your add-in? Get ready to build your add-in and publish
 
 |**Article**|**Description**|
 |:-----|:-----|
-| [Develop SharePoint Add-ins](develop-sharepoint-add-ins)|Discusses advanced concepts and capabilities of the add-in model.|
-| [Publish SharePoint Add-ins](publish-sharepoint-add-ins)|Describes the process and requirements for publishing SharePoint Add-ins.|
+| [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)|Discusses advanced concepts and capabilities of the add-in model.|
+| [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)|Describes the process and requirements for publishing SharePoint Add-ins.|
 
 ## Additional resources
 <a name="SP15Design_AddRes"> </a>
@@ -99,10 +106,10 @@ Have a solid design for your add-in? Get ready to build your add-in and publish
 -  [Reimagine SharePoint development](http://msdn.microsoft.com/en-US/office/apps/dn133840)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
 -  [Blog for add-ins](http://blogs.msdn.com/b/spoffapps)
diff --git a/docs/sp-add-ins/determine-sharepoint-rest-service-endpoint-uris.md b/docs/sp-add-ins/determine-sharepoint-rest-service-endpoint-uris.md
index 6592c3fffe..a3cfe1c23d 100644
--- a/docs/sp-add-ins/determine-sharepoint-rest-service-endpoint-uris.md
+++ b/docs/sp-add-ins/determine-sharepoint-rest-service-endpoint-uris.md
@@ -1,23 +1,30 @@
+---
+title: Determine SharePoint REST service endpoint URIs
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Determine SharePoint REST service endpoint URIs
 Learn general guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
  **Before you start**
  
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)
+-  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)
     
  
 **Next steps**
  
 
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
 
@@ -57,7 +64,7 @@ The following figure shows the general syntax structure of SharePoint REST URIs.
  
 
  
-![SharePoint REST request syntax](../../images/SPF15Con_REST_OverallSyntax.png)
+![SharePoint REST request syntax](../images/SPF15Con_REST_OverallSyntax.png)
  
 Some endpoints for SharePoint resources deviate from this syntax structure:
  
@@ -196,7 +203,7 @@ The following figure shows the SharePoint REST parameter syntax.
  
 
  
-![SharePoint REST service method parameter syntax](../../images/SPF15Con_REST_parameterSyntax.png)
+![SharePoint REST service method parameter syntax](../images/SPF15Con_REST_parameterSyntax.png)
  
 
 ### Complex types as parameters for the REST service
@@ -278,7 +285,7 @@ However, the SharePoint REST service does not support passing complex types via
  
 
  
-![SharePoint REST service parameter aliasing syntax](../../images/SPF15Con_REST_parameterAliasSyntax.png)
+![SharePoint REST service parameter aliasing syntax](../images/SPF15Con_REST_parameterAliasSyntax.png)
  
 
  
@@ -297,7 +304,7 @@ For REST endpoints that correspond to methods that take  `Dictionary<String, Str
  
 
  
-![REST service syntax for Dictionary parameters](../../images/SPF15Con_REST_parameterDictionarySyntax.png)
+![REST service syntax for Dictionary parameters](../images/SPF15Con_REST_parameterDictionarySyntax.png)
  
 A  `Dictionary<String, object>` is represented as a multi-value object, named KeyedPropertyValue, with the following string properties:
  
@@ -336,7 +343,7 @@ the figure below shows the REST service syntax for parameters in query string.
  
 
  
-![REST service syntax for parameters in query string](../../images/SPF15Con_REST_parameterQuerySyntax.png)
+![REST service syntax for parameters in query string](../images/SPF15Con_REST_parameterQuerySyntax.png)
  
 
  
@@ -379,7 +386,7 @@ The figure below shows the SharePoint REST service static member syntax.
  
 
  
-![REST service syntax for parameters in query string](../../images/SPF15Con_REST_parameterQuerySyntax.png)
+![REST service syntax for parameters in query string](../images/SPF15Con_REST_parameterQuerySyntax.png)
  
 
  
@@ -397,28 +404,28 @@ If you want to select, filter, or order the data you requested from an endpoint,
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
--  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)
+-  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
 -  [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)
     
  
--  [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service)
+-  [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service.md)
     
  
 -  [Use ETag values through the REST service to get document list item versioning](http://msdn.microsoft.com/library/5f7e0579-46b7-44ab-b3b4-cdbc622dcd98%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/develop-cloud-business-add-ins.md b/docs/sp-add-ins/develop-cloud-business-add-ins.md
index a1eda62b78..9187e67d1d 100644
--- a/docs/sp-add-ins/develop-cloud-business-add-ins.md
+++ b/docs/sp-add-ins/develop-cloud-business-add-ins.md
@@ -1,24 +1,31 @@
+---
+title: Develop cloud business add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Develop cloud business add-ins
  Cloud business add-ins are based on Visual Studio LightSwitch technologies. Some of the tasks for developing cloud business add-ins are unique to the Cloud Business Add-in template, but most are the same as for LightSwitch HTML Client add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Cloud Business Add-in developer tasks
 
 
-- Cloud business add-ins are created by using the Cloud Business Add-in template in Visual Studio. See  [Create a cloud business add-in](create-a-cloud-business-add-in).
+- Cloud business add-ins are created by using the Cloud Business Add-in template in Visual Studio. See  [Create a cloud business add-in](create-a-cloud-business-add-in.md).
     
  
-- By using the document library feature in SharePoint, you can create or upload documents associated with individual items in a list or entity. See  [Associate a document library with an entity](associate-a-document-library-with-an-entity).
+- By using the document library feature in SharePoint, you can create or upload documents associated with individual items in a list or entity. See  [Associate a document library with an entity](associate-a-document-library-with-an-entity.md).
     
  
-- In addition to the Office templates that are available when you add a document to a SharePoint document library, you can provide your own templates. See  [Provide a template for a document library in a cloud business add-in](provide-a-template-for-a-document-library-in-a-cloud-business-add-in).
+- In addition to the Office templates that are available when you add a document to a SharePoint document library, you can provide your own templates. See  [Provide a template for a document library in a cloud business add-in](provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md).
     
  
-- Social and collaboration features in SharePoint for Office 365 allow users to track activity on a list and add comments. You can easily create a newsfeed for your Cloud Business Add-in by enabling a couple of properties. See  [Enable a newsfeed for a cloud business add-in](enable-a-newsfeed-for-a-cloud-business-add-in).
+- Social and collaboration features in SharePoint for Office 365 allow users to track activity on a list and add comments. You can easily create a newsfeed for your Cloud Business Add-in by enabling a couple of properties. See  [Enable a newsfeed for a cloud business add-in](enable-a-newsfeed-for-a-cloud-business-add-in.md).
     
  
 
@@ -72,7 +79,7 @@
 <a name="bk_addresources"> </a>
 
 
--  [Create cloud business add-ins](create-cloud-business-add-ins)
+-  [Create cloud business add-ins](create-cloud-business-add-ins.md)
     
  
 -  [HTML Client Screens for LightSwitch Add-ins](http://msdn.microsoft.com/en-us/library/jj674623.aspx)
diff --git a/docs/sp-add-ins/develop-sharepoint-add-ins.md b/docs/sp-add-ins/develop-sharepoint-add-ins.md
index 2a438d77f7..c33f372d8f 100644
--- a/docs/sp-add-ins/develop-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/develop-sharepoint-add-ins.md
@@ -1,9 +1,16 @@
+---
+title: Develop SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Develop SharePoint Add-ins
 Find in-depth articles and resources to help you build advanced capabilities into your SharePoint Add-ins.
  
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
-> **Note**  This article assumes that you are familiar with the article  [SharePoint Add-ins](sharepoint-add-ins) and the getting started material that it links to.
+> **Note**  This article assumes that you are familiar with the article  [SharePoint Add-ins](sharepoint-add-ins.md) and the getting started material that it links to.
 
 Under  **Develop**, we've got the following to help explain all the different things you can do in a SharePoint Add-in:
 
@@ -26,7 +33,7 @@ And, code is key, so take a look at the "Samples" menu in the Dev Center. It's a
 ## Get started with SharePoint Add-ins resources
 <a name="bk_gettingstarted"> </a>
 
-If you're just getting started with developing SharePoint Add-ins, first take a look a  [SharePoint Add-ins](sharepoint-add-ins). That page points you to key articles to get you acquainted quickly with the different kinds of SharePoint Add-ins. Before doing more advanced kinds of development with SharePoint Add-ins, you should start with a good idea of the kinds of add-ins that you want to build, the technologies that you will want to include, and the hosting options that you will want to use.
+If you're just getting started with developing SharePoint Add-ins, first take a look a  [SharePoint Add-ins](sharepoint-add-ins.md). That page points you to key articles to get you acquainted quickly with the different kinds of SharePoint Add-ins. Before doing more advanced kinds of development with SharePoint Add-ins, you should start with a good idea of the kinds of add-ins that you want to build, the technologies that you will want to include, and the hosting options that you will want to use.
  
 ### Essential tasks and resources for developing SharePoint Add-ins using the client object model, JavaScript object model, and REST endpoints in SharePoint
 <a name="bk_essentials"> </a>
@@ -38,9 +45,9 @@ No matter what kind of SharePoint Add-in you decide to build, your add-in will a
 
 |**Topic**|**Description**|
 |:-----|:-----|
-| [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)|Explains how to do common operations by using C# and the client object model.|
-| [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)|Explains how to do common operations by using the JavaScript object model.|
-| [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)|Explains how to do common operations by using the REST interface.|
+| [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)|Explains how to do common operations by using C# and the client object model.|
+| [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)|Explains how to do common operations by using the JavaScript object model.|
+| [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)|Explains how to do common operations by using the REST interface.|
 
 ## Learn the fundamental concepts for development with SharePoint Add-ins
 <a name="bk_fundamentals"> </a>
@@ -51,10 +58,10 @@ In addition to understanding the basic operations, you should understand the fun
 
 |**Topic**|**Description**|
 |:-----|:-----|
-| [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)|Guides you through core concepts related to acquiring the necessary privileges for working with SharePoint resources.|
-| [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in)|Explains how add-in manifests work and how add-in packages are built.|
-| [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)|Explores the ways in which you can build a rich user experience in SharePoint Add-ins.|
-| [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)|Explains the data access options and techniques that are available in different kinds of SharePoint Add-ins.|
+| [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)|Guides you through core concepts related to acquiring the necessary privileges for working with SharePoint resources.|
+| [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md)|Explains how add-in manifests work and how add-in packages are built.|
+| [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)|Explores the ways in which you can build a rich user experience in SharePoint Add-ins.|
+| [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)|Explains the data access options and techniques that are available in different kinds of SharePoint Add-ins.|
 | [License your Office and SharePoint Add-ins](http://msdn.microsoft.com/library/license-your-office-and-sharepoint-add-ins%28Office.15%29.aspx)|Guides you through the add-in license framework for Office and SharePoint Add-ins.|
 
 ## Put the pieces together: Building advanced SharePoint Add-ins by integrating capabilities
@@ -66,13 +73,13 @@ When you are familiar with the capabilities and features of SharePoint Add-ins,
 
 |**Topic**|**Description**|
 |:-----|:-----|
-| [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte)|Explains how to create SharePoint Add-ins that are hosted in the cloud and that include custom SharePoint lists and content types.|
+| [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md)|Explains how to create SharePoint Add-ins that are hosted in the cloud and that include custom SharePoint lists and content types.|
 
 ## Additional resources
 <a name="bk_addresources"> </a>
 
--  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins) 
--  [Design SharePoint Add-ins](design-sharepoint-add-ins)
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md) 
+-  [Design SharePoint Add-ins](design-sharepoint-add-ins.md)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
 -  [SharePoint Add-ins sample pack](http://code.msdn.microsoft.com/office/Apps-for-SharePoint-sample-64c80184)
  
diff --git a/docs/sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in.md b/docs/sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in.md
index 2a96ba9784..9c1afebc3e 100644
--- a/docs/sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in.md
+++ b/docs/sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Enable a newsfeed for a cloud business add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Enable a newsfeed for a cloud business add-in
 Social and collaboration features in SharePoint for Office 365 allow users to track activity on a list and add comments. You can easily create a newsfeed for your Cloud Business Add-in by enabling a couple of properties.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -24,7 +31,7 @@ To host the newsfeed, you'll need a SharePoint Developer site on Office 365, whi
  
 2. In the  **Properties** window, select the **Post when Created** and/or **Post when Updated** check boxes.
     
-  ![Social properties](../../images/CBAsocial.PNG)
+  ![Social properties](../images/CBAsocial.PNG)
  
 
      **Post when Created** adds a thread to the newsfeed for each new list item. **Post when Updated** adds a thread when the value for an item in the list is changed. Post triggers determine which fields in the item will trigger a post.
@@ -52,7 +59,7 @@ To host the newsfeed, you'll need a SharePoint Developer site on Office 365, whi
  
 3. On the SharePoint chrome bar, choose the  **Newsfeed** link.
     
-  ![The SharePoint chrome bar](../../images/CBAnewsfeed.PNG)
+  ![The SharePoint chrome bar](../images/CBAnewsfeed.PNG)
  
 
     The  **Newsfeed** page opens in a new browser window with entries for the added and/or updated items. You can choose the **Like** link for a post, or you can choose the **Reply** link to add a comment.
@@ -63,13 +70,13 @@ To host the newsfeed, you'll need a SharePoint Developer site on Office 365, whi
 <a name="bk_addresources"> </a>
 
 
--  [Develop cloud business add-ins](develop-cloud-business-add-ins)
+-  [Develop cloud business add-ins](develop-cloud-business-add-ins.md)
     
  
 -  [Social and collaboration features in SharePoint](http://msdn.microsoft.com/en-us/library/office/jj163280.aspx)
     
  
--  [Create a cloud business add-in with a social newsfeed](create-a-cloud-business-add-in-with-a-social-newsfeed)
+-  [Create a cloud business add-in with a social newsfeed](create-a-cloud-business-add-in-with-a-social-newsfeed.md)
     
  
 
diff --git a/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md b/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md
index 7b492c0f1d..7345c57594 100644
--- a/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md
+++ b/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md
@@ -1,8 +1,15 @@
+---
+title: Explore the app manifest structure and the package of a SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Explore the app manifest structure and the package of a SharePoint Add-in
 Learn about the add-in package structure and the manifest file for a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -17,16 +24,16 @@ A SharePoint Add-in package is a file that has an ".app" extension and that comp
 -  **Add-in manifest:** This is a required file that is named appmanifest.xml. It tells SharePoint about some important properties of the add-in, such as its title and the permissions it needs to run. For more information about the contents of this file, see [Add-in for SharePoint manifest file](#AppManifest).
     
  
--  **SharePoint Solution Packages:** Optionally, the add-in may include a SharePoint solution package (.wsp file) that contains the components of the add-in web. These components may include pages, list instances, views, documents, **Web**-scoped Features, and other SharePoint components. (For more information about what SharePoint components can be included in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#TypesOfSPComponentsInApps).) The .wsp file may also contain Office Add-ins. The components in the .wsp file are deployed to the add-in web. For an example of an add-in package that includes a SharePoint solution package, see  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-content-type).
+-  **SharePoint Solution Packages:** Optionally, the add-in may include a SharePoint solution package (.wsp file) that contains the components of the add-in web. These components may include pages, list instances, views, documents, **Web**-scoped Features, and other SharePoint components. (For more information about what SharePoint components can be included in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps).) The .wsp file may also contain Office Add-ins. The components in the .wsp file are deployed to the add-in web. For an example of an add-in package that includes a SharePoint solution package, see  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md).
     
  
--  **Host web Features with Custom Actions or add-in parts:** In addition to the SharePoint components that are deployed to the add-in web, a SharePoint Add-in can also deploy one or more custom actions (shortcut menu items or ribbon extensions) to the host web. This is accomplished by including in the add-in package a Feature that is not inside the package's .wsp file and that deploys the components that will go to the host web. This "loose" Feature is called a host web Feature. Add-in parts are deployed to the host web in the same way. The host web Feature consists of a standard SharePoint feature.xml file and one or more associated elements.xml files. An elements.xml file for a custom action, for example, contains the **CustomAction** markup for the custom action. It can also include markup for add-in parts. Only these two kinds of components can be in the host web Feature. These host web Features are not itemized in the add-in manifest. However, they are "parts" in the OPC sense, and there is an explicit OPC relationship between the add-in manifest and each of these files. For an example of an add-in package that includes a host web Feature, see [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins).
+-  **Host web Features with Custom Actions or add-in parts:** In addition to the SharePoint components that are deployed to the add-in web, a SharePoint Add-in can also deploy one or more custom actions (shortcut menu items or ribbon extensions) to the host web. This is accomplished by including in the add-in package a Feature that is not inside the package's .wsp file and that deploys the components that will go to the host web. This "loose" Feature is called a host web Feature. Add-in parts are deployed to the host web in the same way. The host web Feature consists of a standard SharePoint feature.xml file and one or more associated elements.xml files. An elements.xml file for a custom action, for example, contains the **CustomAction** markup for the custom action. It can also include markup for add-in parts. Only these two kinds of components can be in the host web Feature. These host web Features are not itemized in the add-in manifest. However, they are "parts" in the OPC sense, and there is an explicit OPC relationship between the add-in manifest and each of these files. For an example of an add-in package that includes a host web Feature, see [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md).
     
-     **Note**  Tenant administrators have the option to batch-install a SharePoint Add-in to multiple websites. An add-in that has been installed in this way is said to have  **Tenant** scope. If the add-in has not been batch-installed, and is instead installed to each website separately, it has **Web** scope. If the host web Feature includes ribbon extensions or add-in parts, they are not deployed to the host webs if the add-in is batch-installed, so only shortcut menu items are deployed with Tenant-scoped add-ins. Add-in scope should not be confused with Feature scope. Feature scope determines where the elements in a Feature are deployed. The possibilities are **Farm**,  **WebApplication**,  **Site** (that is, site collection), and **Web**. Only the  **Web** option is permitted for Features in SharePoint Add-ins (both host web Features and Features inside a .wsp in an add-in package). Add-in scope refers to the scope at which an add-in is installed. The possibilities are **Web**, in which case the add-in has been installed to one or more websites site-by-site, and  **Tenant**, in which case the add-in has been batch installed to all or some subset of the websites in a customer's tenancy. For more information about  **Tenant** and **Web** scope, see [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins).
--  **Localization resource files (.resx):** These are for localizing aspects of the add-in manifest that include the add-in title and aspects of host web Features in the add-in package. (Individual parts of the add-in package that are inside their own package, such as .wsp files, Azure Web Sites packages, and add-in manifests, each have their own localization processes that are applied exactly as they would be if the items in question were not part of a SharePoint Add-in.) For an example of an add-in package that includes .resx files for a host web Feature, see [Localize SharePoint Add-ins](localize-sharepoint-add-ins).
+     **Note**  Tenant administrators have the option to batch-install a SharePoint Add-in to multiple websites. An add-in that has been installed in this way is said to have  **Tenant** scope. If the add-in has not been batch-installed, and is instead installed to each website separately, it has **Web** scope. If the host web Feature includes ribbon extensions or add-in parts, they are not deployed to the host webs if the add-in is batch-installed, so only shortcut menu items are deployed with Tenant-scoped add-ins. Add-in scope should not be confused with Feature scope. Feature scope determines where the elements in a Feature are deployed. The possibilities are **Farm**,  **WebApplication**,  **Site** (that is, site collection), and **Web**. Only the  **Web** option is permitted for Features in SharePoint Add-ins (both host web Features and Features inside a .wsp in an add-in package). Add-in scope refers to the scope at which an add-in is installed. The possibilities are **Web**, in which case the add-in has been installed to one or more websites site-by-site, and  **Tenant**, in which case the add-in has been batch installed to all or some subset of the websites in a customer's tenancy. For more information about  **Tenant** and **Web** scope, see [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md).
+-  **Localization resource files (.resx):** These are for localizing aspects of the add-in manifest that include the add-in title and aspects of host web Features in the add-in package. (Individual parts of the add-in package that are inside their own package, such as .wsp files, Azure Web Sites packages, and add-in manifests, each have their own localization processes that are applied exactly as they would be if the items in question were not part of a SharePoint Add-in.) For an example of an add-in package that includes .resx files for a host web Feature, see [Localize SharePoint Add-ins](localize-sharepoint-add-ins.md).
     
  
--  **Office Add-ins Manifests:** Optionally, there may be one or more Office Add-ins manifests that each package an Office Add-in. This part can be included in the add-in package only if the add-in is going to be uploaded to a SharePoint corporate add-in catalog, not the public marketplace. See [Publish SharePoint Add-ins](publish-sharepoint-add-ins) for more information.
+-  **Office Add-ins Manifests:** Optionally, there may be one or more Office Add-ins manifests that each package an Office Add-in. This part can be included in the add-in package only if the add-in is going to be uploaded to a SharePoint corporate add-in catalog, not the public marketplace. See [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md) for more information.
     
  
 
@@ -73,7 +80,7 @@ You must use either the  **SupportedLocales** or the **SupportedLanguages** elem
 
  
 
- **Note**  The values of the  **Scope** attribute of the **AppPermissionRequest** element are structured like URIs, but they are actually literal strings. No part of the example **Scope** value in the following example is a placeholder. For more information about permissions, see [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+ **Note**  The values of the  **Scope** attribute of the **AppPermissionRequest** element are structured like URIs, but they are actually literal strings. No part of the example **Scope** value in the following example is a placeholder. For more information about permissions, see [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
 
@@ -109,7 +116,7 @@ You must use either the  **SupportedLocales** or the **SupportedLanguages** elem
 
 ### URL tokens in the add-in manifest
 
-SharePoint provides several tokens that can be used in the  **StartPage** element and other places in add-ins and components of add-ins to represent information that is not known until the add-in is run. The SharePoint infrastructure resolves these tokens. Some are used at the beginning of the URL and others can be used within a URL such as the value of a query parameter. These tokens and several others can also be used in a variety of SharePoint development contexts. For detailed information about all the tokens and where they can be used, see [URL strings and tokens in SharePoint Add-ins](url-strings-and-tokens-in-sharepoint-add-ins). For general information about other tokens and URLs in SharePoint, see  [URLs and tokens in SharePoint](http://msdn.microsoft.com/library/161418d7-8123-4c4e-91a1-97e43c17f0e6%28Office.15%29.aspx).
+SharePoint provides several tokens that can be used in the  **StartPage** element and other places in add-ins and components of add-ins to represent information that is not known until the add-in is run. The SharePoint infrastructure resolves these tokens. Some are used at the beginning of the URL and others can be used within a URL such as the value of a query parameter. These tokens and several others can also be used in a variety of SharePoint development contexts. For detailed information about all the tokens and where they can be used, see [URL strings and tokens in SharePoint Add-ins](url-strings-and-tokens-in-sharepoint-add-ins.md). For general information about other tokens and URLs in SharePoint, see  [URLs and tokens in SharePoint](http://msdn.microsoft.com/library/161418d7-8123-4c4e-91a1-97e43c17f0e6%28Office.15%29.aspx).
  
 
  
@@ -122,10 +129,10 @@ SharePoint provides several tokens that can be used in the  **StartPage** elemen
 <a name="SP15Exploreappmanifest_bk_addlresources"> </a>
 
 
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 -  [Schema reference for manifests of SharePoint Add-ins](http://msdn.microsoft.com/library/1f8c5d44-3b60-0bfe-9069-1df821220691%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model.md b/docs/sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model.md
index c0bdf17ef6..cd268d3479 100644
--- a/docs/sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model.md
+++ b/docs/sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model.md
@@ -1,20 +1,27 @@
+---
+title: Get a quick overview of the SharePoint object model
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get a quick overview of the SharePoint object model
 Get a quick introduction to some of the major classes in the SharePoint object model.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the fourth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the fourth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
 
@@ -118,7 +125,7 @@ private string GetLocalEmployeeName()
 ## 
 <a name="Nextsteps"> </a>
 
- In the next article, we get back to coding and learn how to write data to SharePoint: [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+ In the next article, we get back to coding and learn how to write data to SharePoint: [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md b/docs/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md
index 5eba344ad1..bdebd84226 100644
--- a/docs/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md
@@ -1,11 +1,18 @@
+---
+title: Get started creating provider-hosted SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get started creating provider-hosted SharePoint Add-ins
 Set up a development environment and create your first provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-Provider-hosted add-ins are one of the two major types of SharePoint Add-ins. For an overview of SharePoint Add-ins and the two different types, see  [SharePoint Add-ins](sharepoint-add-ins). Here's a summary of provider-hosted add-ins:
+Provider-hosted add-ins are one of the two major types of SharePoint Add-ins. For an overview of SharePoint Add-ins and the two different types, see  [SharePoint Add-ins](sharepoint-add-ins.md). Here's a summary of provider-hosted add-ins:
  
 
 - They include a web application, or service, or database that is hosted externally from the SharePoint farm or SharePoint Online subscription. They may also include SharePoint components. You can host the external components on any web-hosting stack, including the LAMP (Linux, Apache, MySQL, and PHP) stack.
@@ -14,11 +21,11 @@ Provider-hosted add-ins are one of the two major types of SharePoint Add-ins. Fo
 - The custom business logic in the add-in has to run on either the external components or in JavaScript on custom SharePoint pages.
     
  
-- [Step 1 - Set up your dev environment](get-started-creating-provider-hosted-sharepoint-add-ins#Setup) 
+- [Step 1 - Set up your dev environment](get-started-creating-provider-hosted-sharepoint-add-ins.md#Setup) 
 
-- [Step 2 - Create the app project](get-started-creating-provider-hosted-sharepoint-add-ins#Create) 
+- [Step 2 - Create the app project](get-started-creating-provider-hosted-sharepoint-add-ins.md#Create) 
 
-- [Step 3 - Code your app](get-started-creating-provider-hosted-sharepoint-add-ins#Code)
+- [Step 3 - Code your app](get-started-creating-provider-hosted-sharepoint-add-ins.md#Code)
  
 ## Set up your dev environment
 <a name="Setup"> </a>
@@ -42,7 +49,7 @@ There are many ways to set up a development environment for SharePoint Add-ins.
 <a name="o365_signup"> </a>
 
 
- **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more info, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription). 
+ **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more info, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md). 
  
 
 There are three ways to get an Office 365 plan. 
@@ -69,7 +76,7 @@ There are three ways to get an Office 365 plan.
  
 
  
-![Page 2 of Sign up form for Office 365 account](../../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
+![Page 2 of Sign up form for Office 365 account](../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
  
 
  
@@ -107,7 +114,7 @@ After you finish the signup process, your browser opens the Office 365 installat
  
 
  
-![Screenshot that shows the Office 365 admin center.](../../images/SP15_Office365AdminInset_border.png)
+![Screenshot that shows the Office 365 admin center.](../images/SP15_Office365AdminInset_border.png)
  
 
  
@@ -127,7 +134,7 @@ After you finish the signup process, your browser opens the Office 365 installat
  
 
  
-![Screenshot that shows the Developer site homepage.](../../images/SP15_DeveloperSiteHome_border.png)
+![Screenshot that shows the Developer site homepage.](../images/SP15_DeveloperSiteHome_border.png)
  
 
  
@@ -491,7 +498,7 @@ namespace SampleAddInWeb
 
  
 
-  ![Basic self-hosted app launch page](../../images/SP15_basicself-hostedapp.gif)
+  ![Basic self-hosted app launch page](../images/SP15_basicself-hostedapp.gif)
  
 
  
@@ -501,7 +508,7 @@ namespace SampleAddInWeb
 ## Next steps
 <a name="SP15createprovider_nextsteps"> </a>
 
-See  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel) to learn how to integrate an add-in into SharePoint's UI scheme.
+See  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md) to learn how to integrate an add-in into SharePoint's UI scheme.
  
 
  
@@ -510,7 +517,7 @@ See  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-p
 <a name="bk_addresources"> </a>
 
 
-- For other ways of setting up a development environment, such as an "all on-premise" environment, see the  [Tools](tools-and-environments-for-developing-sharepoint-add-ins) section in the SharePoint Add-ins table of contents.
+- For other ways of setting up a development environment, such as an "all on-premise" environment, see the  [Tools](tools-and-environments-for-developing-sharepoint-add-ins.md) section in the SharePoint Add-ins table of contents.
     
  
 
diff --git a/docs/sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins.md b/docs/sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins.md
index 5d7f53e5ad..234977d6ba 100644
--- a/docs/sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins.md
@@ -1,11 +1,18 @@
+---
+title: Get started creating SharePoint-hosted SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get started creating SharePoint-hosted SharePoint Add-ins
 Set up a development environment and create your first SharePoint-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-SharePoint-hosted add-ins are one of the two major types of SharePoint Add-ins. For an overview of SharePoint Add-ins and the two different types, see  [SharePoint Add-ins](sharepoint-add-ins). Here's a summary of SharePoint-hosted add-ins:
+SharePoint-hosted add-ins are one of the two major types of SharePoint Add-ins. For an overview of SharePoint Add-ins and the two different types, see  [SharePoint Add-ins](sharepoint-add-ins.md). Here's a summary of SharePoint-hosted add-ins:
  
 
 - They contain SharePoint lists, Web Parts, workflows, custom pages, and other components, all of which are installed on a subweb, called the add-in web, of the SharePoint website where the add-in is installed.
@@ -14,17 +21,17 @@ SharePoint-hosted add-ins are one of the two major types of SharePoint Add-ins.
 - The only code they have is JavaScript on custom SharePoint pages.
     
  
-- [Step 1 - Set up your dev environment](get-started-creating-sharepoint-hosted-sharepoint-add-ins#Setup) 
+- [Step 1 - Set up your dev environment](#Setup) 
 
-- [Step 2 - Create the app project](get-started-creating-sharepoint-hosted-sharepoint-add-ins#Create) 
+- [Step 2 - Create the app project](#Create) 
 
-- [Step 3 - Code your app](get-started-creating-sharepoint-hosted-sharepoint-add-ins#Code)
+- [Step 3 - Code your app](#Code)
  
 
 ## Set up your dev environment
 <a name="Setup"> </a>
 
-There are many ways to set up a development environment for SharePoint Add-ins. This section explains the simplest way. For alternatives, see  [Additional Resources](#bk_addresources).
+There are many ways to set up a development environment for SharePoint Add-ins. This section explains the simplest way.
  
 
  
@@ -43,7 +50,7 @@ There are many ways to set up a development environment for SharePoint Add-ins.
 <a name="o365_signup"> </a>
 
 
- **Note**   You might already have access to an Office 365 Developer Site. **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more info, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription). 
+ **Note**   You might already have access to an Office 365 Developer Site. **Are you an MSDN subscriber?** Visual Studio Ultimate and Visual Studio Premium with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more info, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md). 
  
 
 There are three ways to get an Office 365 plan. 
@@ -70,7 +77,7 @@ There are three ways to get an Office 365 plan.
  
 
  
-![Page 2 of Sign up form for Office 365 account](../../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
+![Page 2 of Sign up form for Office 365 account](../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
  
 
  
@@ -108,7 +115,7 @@ After you finish the signup process, your browser opens the Office 365 installat
  
 
  
-![Screenshot that shows the Office 365 admin center.](../../images/SP15_Office365AdminInset_border.png)
+![Screenshot that shows the Office 365 admin center.](../images/SP15_Office365AdminInset_border.png)
  
 
  
@@ -128,7 +135,7 @@ After you finish the signup process, your browser opens the Office 365 installat
  
 
  
-![Screenshot that shows the Developer site homepage.](../../images/SP15_DeveloperSiteHome_border.png)
+![Screenshot that shows the Developer site homepage.](../images/SP15_DeveloperSiteHome_border.png)
  
 
  
@@ -208,7 +215,7 @@ For your first SharePoint-hosted SharePoint Add-in, we'll include the classic Sh
 
  
 
-  ![List folder with child NewEmployeeOrientation template, which itself has three children; a NewEmployeeOrientationInstance, an elements.xml file, and a schema.xml file. The instance itself has a child named elements.xml.](../../images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG)
+  ![List folder with child NewEmployeeOrientation template, which itself has three children; a NewEmployeeOrientationInstance, an elements.xml file, and a schema.xml file. The instance itself has a child named elements.xml.](../images/10e5d116-d24b-4a44-bfff-cfbf2f971b1e.PNG)
  
 
     
@@ -341,7 +348,7 @@ For your first SharePoint-hosted SharePoint Add-in, we'll include the classic Sh
 
  
 
-  ![The add-in's default page is shown with its title New Employees by Location. There is a link labeled New Employees in Seattle. An arrow from this link points to the list view page for the list. It is titled New Employees in Seattle, with the list below.](../../images/9dc5cefe-083a-4807-bee6-473001f23db9.png)
+  ![The add-in's default page is shown with its title New Employees by Location. There is a link labeled New Employees in Seattle. An arrow from this link points to the list view page for the list. It is titled New Employees in Seattle, with the list below.](../images/9dc5cefe-083a-4807-bee6-473001f23db9.png)
  
 
     
@@ -357,10 +364,10 @@ For your first SharePoint-hosted SharePoint Add-in, we'll include the classic Sh
     
  
 
-## 
+#Next Steps
 <a name="Nextsteps"> </a>
 
-So far, there isn't much orientation information in the list. We'll add some in later articles in this series. But first, take a brief break from coding to learn about deploying SharePoint Add-ins in  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in).
+So far, there isn't much orientation information in the list. We'll add some in later articles in this series. But first, take a brief break from coding to learn about deploying SharePoint Add-ins in  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/get-started-developing-cloud-business-add-ins.md b/docs/sp-add-ins/get-started-developing-cloud-business-add-ins.md
index 6fb2945c44..c656186275 100644
--- a/docs/sp-add-ins/get-started-developing-cloud-business-add-ins.md
+++ b/docs/sp-add-ins/get-started-developing-cloud-business-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Get started developing cloud business add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get started developing cloud business add-ins
 The best way to learn to develop a Cloud Business Add-in for SharePoint is to jump in and try it. The following tutorials and associate samples walk you through the process step-by-step. Go ahead - it's much easier than you might imagine.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -10,14 +17,14 @@ The best way to learn to develop a Cloud Business Add-in for SharePoint is to ju
 
 ## Incident Manager Tutorial
 
-In this tutorial, you'll create an add-in for a fictional Contoso Fire Department to handle on-scene incident management. The walkthrough covers the core concepts of building a Cloud Business Add-in as well as more advanced concepts such as integrating SharePoint lists and document libraries. See  [Incident manager: A cloud business add-in tutorial](incident-manager-a-cloud-business-add-in-tutorial) for the tutorial topic and [Incident Manager: A Cloud Business Add-in Tutorial](http://code.msdn.microsoft.com/Incident-Manager-A-Cloud-c32d9b04) for the sample.
+In this tutorial, you'll create an add-in for a fictional Contoso Fire Department to handle on-scene incident management. The walkthrough covers the core concepts of building a Cloud Business Add-in as well as more advanced concepts such as integrating SharePoint lists and document libraries. See  [Incident manager: A cloud business add-in tutorial](incident-manager-a-cloud-business-add-in-tutorial.md) for the tutorial topic and [Incident Manager: A Cloud Business Add-in Tutorial](http://code.msdn.microsoft.com/Incident-Manager-A-Cloud-c32d9b04.md) for the sample.
  
 
  
 
 ## Candidate Tracker Tutorial
 
-In this walkthrough, you'll create an add-in to track job candidates, taking advantage of the SharePoint for Office 365 social integration feature to provide a newsfeed for the add-in. See  [Create a cloud business add-in with a social newsfeed](create-a-cloud-business-add-in-with-a-social-newsfeed) for the walkthrough topic and [Creating a Cloud Business Add-in with a Social Newsfeed](http://code.msdn.microsoft.com/Creating-a-Cloud-Business-8540c0c9) for the sample.
+In this walkthrough, you'll create an add-in to track job candidates, taking advantage of the SharePoint for Office 365 social integration feature to provide a newsfeed for the add-in. See  [Create a cloud business add-in with a social newsfeed](create-a-cloud-business-add-in-with-a-social-newsfeed.md) for the walkthrough topic and [Creating a Cloud Business Add-in with a Social Newsfeed](http://code.msdn.microsoft.com/Creating-a-Cloud-Business-8540c0c9.md) for the sample.
  
 
  
@@ -26,7 +33,7 @@ In this walkthrough, you'll create an add-in to track job candidates, taking adv
 <a name="bk_addresources"> </a>
 
 
--  [Create cloud business add-ins](create-cloud-business-add-ins)
+-  [Create cloud business add-ins](create-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/get-to-know-the-sharepoint-rest-service.md b/docs/sp-add-ins/get-to-know-the-sharepoint-rest-service.md
index 408450847c..ebaa29ef4e 100644
--- a/docs/sp-add-ins/get-to-know-the-sharepoint-rest-service.md
+++ b/docs/sp-add-ins/get-to-know-the-sharepoint-rest-service.md
@@ -1,8 +1,15 @@
+---
+title: Get to know the SharePoint REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get to know the SharePoint REST service
 Get the basics of using the SharePoint REST service to access and update SharePoint data, using the REST and OData web protocol standards.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 SharePoint introduces a Representational State Transfer (REST) service that is comparable to the existing SharePoint  [client object models](http://msdn.microsoft.com/library/88e5e1b9-eab2-4f3b-a3f2-75c96b86f1f4%28Office.15%29.aspx). Now, developers can interact remotely with SharePoint data by using any technology that supports REST web requests. This means that developers can perform  **Create**,  **Read**,  **Update**, and  **Delete** (CRUD) operations from their SharePoint Add-ins, solutions, and client applications, using REST web technologies and standard Open Data Protocol (OData) syntax.
@@ -52,7 +59,7 @@ The client.svc web service in SharePoint handles the HTTP request, and serves th
  
 
  
-![SharePoint REST service architecture](../../images/SPF15Con_REST_RESTStructure.png)
+![SharePoint REST service architecture](../images/SPF15Con_REST_RESTStructure.png)
  
 Because of the functionality and ease of use that client object models provide, they remain the primary development option for communicating with SharePoint sites by using .NET Framework managed code, Silverlight, or JavaScript.
  
@@ -118,7 +125,7 @@ This syntax doesn't apply to the SocialFeedManager or SocialFollowingManager RES
  
 
  
-See  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris) for more guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.
+See  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md) for more guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.
  
 
  
@@ -165,7 +172,7 @@ The following table contains typical REST endpoint URL examples to get you start
 ## Batch job support
 <a name="batch"> </a>
 
-The SharePoint Online (and on-premise SharePoint 2016 or later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis). .
+The SharePoint Online (and on-premise SharePoint 2016 or later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md). .
  
 
  
@@ -180,18 +187,18 @@ Use the resources listed below to learn more about using the SharePoint REST ser
 
 |**Title**|**Description**|
 |:-----|:-----|
-| [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)|Learn how to perform basic create, read, update, and delete (CRUD) operations with the SharePoint REST interface.|
-| [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)|Learn how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the SharePoint REST interface.|
-| [Working with folders and files with REST](working-with-folders-and-files-with-rest)|Learn how to perform basic create, read, update, and delete (CRUD) operations on folders and files with the SharePoint REST interface.|
-| [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)|Learn how to start from a REST endpoint for a given SharePoint item, and navigate to and access related items, such as parent sites or the library structure where that item resides.|
-| [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris)|Learn general guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.|
-| [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)|Learn how to use a wide range of OData query string operators to select, filter, and order the data you request from the SharePoint REST service.|
+| [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)|Learn how to perform basic create, read, update, and delete (CRUD) operations with the SharePoint REST interface.|
+| [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)|Learn how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the SharePoint REST interface.|
+| [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)|Learn how to perform basic create, read, update, and delete (CRUD.) operations on folders and files with the SharePoint REST interface.|
+| [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)|Learn how to start from a REST endpoint for a given SharePoint item, and navigate to and access related items, such as parent sites or the library structure where that item resides.|
+| [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md)|Learn general guidelines for determining SharePoint REST endpoint URIs from the signature of the corresponding client object model APIs.|
+| [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)|Learn how to use a wide range of OData query string operators to select, filter, and order the data you request from the SharePoint REST service.|
 | [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)|This page contains links to all of the REST resources that are available for SharePoint developers on MSDN.|
 | [SharePoint Search REST API overview](http://msdn.microsoft.com/library/8a4f7863-e4c1-4099-9189-a1894db36930%28Office.15%29.aspx)|Add search functionality to client and mobile applications using the Search REST service in SharePoint Server 2013 and any technology that supports REST web requests.|
 | [Social feed REST API reference for SharePoint](http://msdn.microsoft.com/library/f1cb914f-1e91-4e23-bf53-d2ab323eac13%28Office.15%29.aspx)|Learn about SharePoint REST endpoints for feed-related tasks.|
 | [Following people and content REST API reference for SharePoint](http://msdn.microsoft.com/library/c05755df-846d-4a39-941d-950d066cc6d4%28Office.15%29.aspx)|Learn about SharePoint REST endpoints for following people and content.|
-| [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis)|Learn how to combine multiple requests into a single call to the REST service.|
-| [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service)|Learn how to synchronize items between SharePoint and your add-ins or services by using the  **GetListItemChangesSinceToken** resource, part of the SharePoint REST service.|
+| [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md)|Learn how to combine multiple requests into a single call to the REST service.|
+| [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service.md)|Learn how to synchronize items between SharePoint and your add-ins or services by using the  **GetListItemChangesSinceToken** resource, part of the SharePoint REST service.|
 | [Use ETag values through the REST service to get document list item versioning](http://msdn.microsoft.com/library/5f7e0579-46b7-44ab-b3b4-cdbc622dcd98%28Office.15%29.aspx)|Learn how to use HTML ETags with the SharePoint REST service for concurrency control of SharePoint lists and list items.|
 
 ## OData resources
diff --git a/docs/sp-add-ins/get-user-identity-and-properties-in-sharepoint.md b/docs/sp-add-ins/get-user-identity-and-properties-in-sharepoint.md
index a215f235e0..81ca5dc6fa 100644
--- a/docs/sp-add-ins/get-user-identity-and-properties-in-sharepoint.md
+++ b/docs/sp-add-ins/get-user-identity-and-properties-in-sharepoint.md
@@ -1,8 +1,15 @@
+---
+title: Get user identity and properties in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Get user identity and properties in SharePoint
 Retrieve user identity and user information in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 There are different ways to retrieve user identity and information, depending on what information you want to retrieve. This article shows you some of the ways you can accomplish that.
@@ -12,7 +19,7 @@ There are different ways to retrieve user identity and information, depending on
 <a name="Prereq"> </a>
 
 
-- Prepare your add-in development environment as described in  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins).
+- Prepare your add-in development environment as described in  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md).
     
  
 - Install Visual Studio.
@@ -22,7 +29,7 @@ There are different ways to retrieve user identity and information, depending on
     
  
 
- **Note**  For guidance on how to setup a development environment that fits your needs, see  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+ **Note**  For guidance on how to setup a development environment that fits your needs, see  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
 
@@ -36,9 +43,9 @@ The following table lists some useful articles that can help you to understand t
 
 |**Article **|**Description**|
 |:-----|:-----|
-| [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)|Learn about SharePoint add-in permissions for working with SharePoint, including types of add-in permissions, permission request scopes, and managing permissions. This article also discusses the differences in add-in permission rights, and user rights.|
-| [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)|Learn about the OAuth authentication and authorization flow for cloud-hosted add-ins.|
-| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio 2012, how to interact with Microsoft SharePoint sites by using the SharePoint CSOM, and how to implement OAuth in a SharePoint Add-in.|
+| [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)|Learn about SharePoint add-in permissions for working with SharePoint, including types of add-in permissions, permission request scopes, and managing permissions. This article also discusses the differences in add-in permission rights, and user rights.|
+| [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)|Learn about the OAuth authentication and authorization flow for cloud-hosted add-ins.|
+| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio 2012, how to interact with Microsoft SharePoint sites by using the SharePoint CSOM, and how to implement OAuth in a SharePoint Add-in.|
 
 ## Retrieving current website user identity
 <a name="WebsiteUserID"> </a>
@@ -189,19 +196,19 @@ clientContext.ExecuteQuery();
 <a name="AdditionalResources"> </a>
 
 
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+-  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md b/docs/sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md
index ae3f8d1d99..d4eb914a35 100644
--- a/docs/sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md
+++ b/docs/sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md
@@ -1,14 +1,21 @@
+---
+title: Give your provider-hosted add-in the SharePoint look-and-feel
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Give your provider-hosted add-in the SharePoint look-and-feel
 Learn how to give your provider-hosted SharePoint Add-ins the look and feel of SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the second in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the second in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 In the previous article of this series you learned how to set up a development environment and how to use Visual Studio to create a first "Hello World" level add-in that exposes SharePoint data in the add-in's remote web application. In this article, we are going to start with an SharePoint Add-in solution that has already been created. It includes an ASP.NET Web Forms application and an SQL Azure database. We've created these for you because this series of articles is intended to focus only on SharePoint Add-ins. You'll be adding more SharePoint functionality and integration to the add-in with each article in this series.
@@ -31,7 +38,7 @@ We are not going to teach you ASP.NET or T-SQL programming in this series, but y
  
 2. On the  **New SharePoint Site** page, fill out the form for a new team site by using the values in the following screen shot.
     
-  ![The form for creating a new SharePoint subsite with "Fabrikam Hong Kong Store" in the Title textbox and "hongkong" in the URL textbox.](../../images/7639578e-3d3f-40cf-8f53-355bb19c539b.png)
+  ![The form for creating a new SharePoint subsite with "Fabrikam Hong Kong Store" in the Title textbox and "hongkong" in the URL textbox.](../images/7639578e-3d3f-40cf-8f53-355bb19c539b.png)
  
 
  
@@ -72,7 +79,7 @@ We are not going to teach you ASP.NET or T-SQL programming in this series, but y
  
 7. The add-in's start page looks like the one in the screen shot below. At the very top is the name of the SharePoint website where the add-in is installed. This is a side effect of some sample code that the Office Developer Tools for Visual Studio generate. You'll change this in a later step. The page has areas where data from the corporate  **Inventory**,  **Orders**, and  **Employees** SQL database tables can be seen. These tables are empty initially.
     
-  ![The start page of the chain store add-in with labelled areas and buttons for viewing the store's inventory, orders, and employees.](../../images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG)
+  ![The start page of the chain store add-in with labelled areas and buttons for viewing the store's inventory, orders, and employees.](../images/9c836899-8f21-4e0f-9260-69b8171a303c.PNG)
  
 
  
@@ -80,7 +87,7 @@ We are not going to teach you ASP.NET or T-SQL programming in this series, but y
  
 8. Open the  **Order Form** link at the bottom of the page to open an order form. Enter some values in the form and press **Place Order**. The following screenshot shows an example. It won't appear that anything has nappened, but the code behind the button passes the values to a parameterized stored procedure in the SQL database. Using parameterized stored procedures protects the database from SQL injection attacks.
     
-  ![Order form with text boxes for supplier, product, and quantity; with a button labelled Place Order.](../../images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG)
+  ![Order form with text boxes for supplier, product, and quantity; with a button labelled Place Order.](../images/5ce3e68b-1bcf-4a24-9153-b9164af77a6b.PNG)
  
 
  
@@ -88,11 +95,11 @@ We are not going to teach you ASP.NET or T-SQL programming in this series, but y
  
 9. Use the browser's back button to navigate back to the start page, and then press the  **Show Orders** button. The page will refresh and your order will appear on the page similar to the following screenshot.
     
-    The table has a  **Tenant** field with the URL of your test SharePoint website as the value. This does not refer to the SharePoint Online subscription that is sometimes called a tenancy. Instead, each instance of the add-in is a distinct tenant in the corporate database. Since no more than one instance of an add-in can be installed on a specific SharePoint host web, the URL of the host web can be used as a tenant discriminator in the database. (For a refresher on the distinction between host web and add-in web, see [SharePoint Add-ins](sharepoint-add-ins).) All of the stored procedures in the add-in include the discriminator value when they write or read from the database. This ensures that when a user presses the  **Show Orders** (or **Show Employees** or **Show Inventory**) button, only the data that is associated with the user's store is retrieved from the database. This design also ensures that users can only place orders and add employees for their own store.
+    The table has a  **Tenant** field with the URL of your test SharePoint website as the value. This does not refer to the SharePoint Online subscription that is sometimes called a tenancy. Instead, each instance of the add-in is a distinct tenant in the corporate database. Since no more than one instance of an add-in can be installed on a specific SharePoint host web, the URL of the host web can be used as a tenant discriminator in the database. (For a refresher on the distinction between host web and add-in web, see [SharePoint Add-ins](sharepoint-add-ins.md).) All of the stored procedures in the add-in include the discriminator value when they write or read from the database. This ensures that when a user presses the  **Show Orders** (or **Show Employees** or **Show Inventory**.md) button, only the data that is associated with the user's store is retrieved from the database. This design also ensures that users can only place orders and add employees for their own store.
     
     The remote web application obtains the host web URL from a query string parameter that SharePoint adds to the URL of the start page when it launches the add-in. Since SSL is being used, this query string is encrypted as it goes across the Internet to the remote web application. 
     
-  ![The section of the start page for orders with one order showing in an HTML table. It has columns for ID, Tenant, Supplier, Product, and Quantity.](../../images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG)
+  ![The section of the start page for orders with one order showing in an HTML table. It has columns for ID, Tenant, Supplier, Product, and Quantity.](../images/6a82c6eb-4a46-4a97-94f9-c1f4a7605d1f.PNG)
  
 
  
@@ -103,7 +110,7 @@ We are not going to teach you ASP.NET or T-SQL programming in this series, but y
  
 11. By default the add-in remains installed on the SharePoint host web in between debugging sessions in Visual Studio. To see how end users would launch it after it is installed, open the Fabrikam Hong Kong SharePoint website in your browser and navigate to the  **Site Contents** page. You'll see the tile for the add-in as it is in the following screenshot:
     
-  ![The launch tile for the Chain Store add-in on the site contents page with the add-in's icon and name.](../../images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG)
+  ![The launch tile for the Chain Store add-in on the site contents page with the add-in's icon and name.](../images/f16e6360-c511-431f-b2c5-9e5541e64d4b.PNG)
  
 
     
@@ -288,13 +295,13 @@ href="<%= spContext.SPHostUrl.ToString() + "_layouts/15/defaultcss.ashx" %>" />
     
 2. When the add-in's start page opens, it now looks like a SharePoint page. Click the  **Order Form** link. It also now looks like a SharePoint form.
     
-  ![The Order Form again. Now it uses Segoe fonts and the phrase "Place Order" is highlighted in blue.](../../images/a35fd1af-7194-4c99-b298-bac97025b981.PNG)
+  ![The Order Form again. Now it uses Segoe fonts and the phrase "Place Order" is highlighted in blue.](../images/a35fd1af-7194-4c99-b298-bac97025b981.PNG)
  
 3. Create an order and press  **Place Order**.
     
 4.  Use the browser's back button to navigate back to the add-in start page, and then press **Show Orders**. The page should now look similar like the following. Note that the column headings are now all caps. 
     
-  ![The start page with the chrome control across the top. All of the text and controls have SharePoint styling.](../../images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG)
+  ![The start page with the chrome control across the top. All of the text and controls have SharePoint styling.](../images/e56e4b80-1f1c-4a83-9ac0-3005ceea7c3a.PNG)
  
 
 5. Press the  **?** icon on the end of the chrome control. A simple help page opens. Click the browser's back button.
@@ -314,7 +321,7 @@ href="<%= spContext.SPHostUrl.ToString() + "_layouts/15/defaultcss.ashx" %>" />
  
 10. Navigate to the  **Site Contents** page and launch the Chain Store app from its tile. Your custom pages have taken on the chosen look. The following screenshots show how they appear in the **Nature** composed look.
     
-  ![The add-in's start page and order form with the greenish colors of the Nature composed look.](../../images/25ba5677-f530-432a-9980-64b5eb33119c.png)
+  ![The add-in's start page and order form with the greenish colors of the Nature composed look.](../images/25ba5677-f530-432a-9980-64b5eb33119c.png)
  
 
 11. Change the site's look back to the default, which is called  **Office**.
@@ -330,7 +337,7 @@ href="<%= spContext.SPHostUrl.ToString() + "_layouts/15/defaultcss.ashx" %>" />
 ## Next Steps
 <a name="Nextsteps"> </a>
 
- The add-in now looks like SharePoint, but it's still just a web application that doesn't really integrate with SharePoint beyond being launched from a tile in SharePoint. You'll add a custom command, launched from a custom ribbon button in the next article: [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in).
+ The add-in now looks like SharePoint, but it's still just a web application that doesn't really integrate with SharePoint beyond being launched from a tile in SharePoint. You'll add a custom command, launched from a custom ribbon button in the next article: [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md).
  
 
  
diff --git a/docs/sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in.md b/docs/sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in.md
index 9d4e240bb1..b206a5bf28 100644
--- a/docs/sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in.md
@@ -1,29 +1,36 @@
+---
+title: Handle add-in events in the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Handle add-in events in the provider-hosted add-in
 Learn how to customize the installation of a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the seventh in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the seventh in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
--  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+-  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
     
  
--  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in)
+-  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in.md)
     
  
 
@@ -68,7 +75,7 @@ For the Chain Store add-in, we'll combine these strategies. In this article, you
 ## Configure the solution for event receiver debugging
 <a name="RERDebug"> </a>
 
-Debugging of event receivers requires the use of the Azure Service Bus. Follow the instructions at  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in). Since you are using a SharePoint Online website as your test site, be sure carry out the instructions for a remote test site. The remainder of this series will assume you have configured debugging successfully. 
+Debugging of event receivers requires the use of the Azure Service Bus. Follow the instructions at  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md). Since you are using a SharePoint Online website as your test site, be sure carry out the instructions for a remote test site. The remainder of this series will assume you have configured debugging successfully. 
  
 
  
@@ -281,7 +288,7 @@ catch (Exception e)
  
 3. On the  **Accounts** page, press the **Show Add-in Version** button. The version shows as0000.0000.0000.0000.
     
-  ![The Accounts page with the heading "Account settings". A button named "Show Add-in Version" and below this a line of text reading "Registered version: zero zero zero zero dot zero zero zero zero dot zero zero zero zero dot zero zero zero zero".](../../images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG)
+  ![The Accounts page with the heading "Account settings". A button named "Show Add-in Version" and below this a line of text reading "Registered version: zero zero zero zero dot zero zero zero zero dot zero zero zero zero dot zero zero zero zero".](../images/2a905b7d-89c7-456a-8456-21a9b7e9efc5.PNG)
  
 
  
@@ -297,7 +304,7 @@ catch (Exception e)
 ## 
 <a name="Nextsteps"> </a>
 
- In the next article of the series, you will add first-run logic to the add-in that will programmatically deploy the **Local Employees** list and the custom ribbon button: [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in)
+ In the next article of the series, you will add first-run logic to the add-in that will programmatically deploy the **Local Employees** list and the custom ribbon button: [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/handle-events-in-sharepoint-add-ins.md b/docs/sp-add-ins/handle-events-in-sharepoint-add-ins.md
index 416149766b..a0cacd9a12 100644
--- a/docs/sp-add-ins/handle-events-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/handle-events-in-sharepoint-add-ins.md
@@ -1,6 +1,13 @@
+---
+title: Handle events in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Handle events in SharePoint Add-ins
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Your custom code can handle three categories of events in provider-hosted add-ins:
@@ -39,10 +46,10 @@ To handle list and list item events, you create remote event receivers (RERs), w
 
  
 
-- Events in the host web are registered programmatically with the CSOM (client-side object model) or the SharePoint REST API. This task is typically done in "first run" logic in the add-in or in a handler for an add-in event. (See  [Handling add-in events](#HandlingAppEvents) later in the article for an overview of add-in events.) For a code sample that programmatically registers a list event, see [OfficeDev/PnP/Samples/Core.EventReceivers](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.EventReceivers).
+- Events in the host web are registered programmatically with the CSOM (client-side object model) or the SharePoint REST API. This task is typically done in "first run" logic in the add-in or in a handler for an add-in event. (See  [Handling add-in events](#HandlingAppEvents) later in the article for an overview of add-in events.) For a code sample that programmatically registers a list event, see [OfficeDev/PnP/Samples/Core.EventReceivers](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.EventReceivers.md).
     
  
--  Events in the add-in web are usually registered in a Feature of the add-in web with some simple XML markup. Details of how to create the markup and the service are in [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins). It is also possible to register add-in web events programmatically.
+-  Events in the add-in web are usually registered in a Feature of the add-in web with some simple XML markup. Details of how to create the markup and the service are in [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins.md). It is also possible to register add-in web events programmatically.
     
  
 
@@ -133,7 +140,7 @@ To change the events that the remote event receiver handles, open  **Solution Ex
 
  
 
- **Note**  For additional information about RERs, including some troubleshooting information, see  [Remote Event Receivers FAQ](handle-events-in-sharepoint-add-ins#RERFAQ).
+ **Note**  For additional information about RERs, including some troubleshooting information, see  [Remote Event Receivers FAQ](handle-events-in-sharepoint-add-ins.md#RERFAQ).
  
 
 
@@ -152,7 +159,7 @@ The  **AppInstalled** event runs immediately after SharePoint has finished every
 
  
 
- **Note**  When you install an add-in with  [Tenant scope](tenancies-and-deployment-scopes-for-sharepoint-add-ins), it is installed to the add-in catalog site collection and the AppInstalled event runs then and only then. The add-in is visible in multiple web sites in the tenancy, but the event does not run separately for each of these.
+ **Note**  When you install an add-in with  [Tenant scope](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md), it is installed to the add-in catalog site collection and the AppInstalled event runs then and only then. The add-in is visible in multiple web sites in the tenancy, but the event does not run separately for each of these.
  
 
 Besides canceling an add-in installation, this event can be used for many other purposes including:
@@ -168,7 +175,7 @@ Besides canceling an add-in installation, this event can be used for many other
  
 - Set app-instance-relative initialization settings. For example, your add-in can have an add-in web property bag for holding settings that vary from one instance of the add-in to another. Your AppInstalled handler can write varying values to the property bag, based on, say, the site type of the host web (such as Team Site or Blog site).
     
-     **Note**  Checking to see if the host web is an AppCatalog site is a good way to detect whether the add-in has been installed with tenant scope. See  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins).
+     **Note**  Checking to see if the host web is an AppCatalog site is a good way to detect whether the add-in has been installed with tenant scope. See  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md).
 - Perform app-instance-relative configuration in the add-in's remote web application, such as adding a table to a database.
     
  
@@ -208,7 +215,7 @@ Some examples of what a handler for this event can do:
 - Make changes to app-instance-relative components in the add-in's web application or remote database.
     
  
- *Detailed instructions for creating add-in event handlers is in  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins)*  .
+ *Detailed instructions for creating add-in event handlers is in  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md)*  .
  
 
  
@@ -245,7 +252,7 @@ Installation and updating errors can be seen in the SharePoint UI, as shown in t
  
 
  
-![Steps to see add-in installation errors in SharePoint.](../../images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png)
+![Steps to see add-in installation errors in SharePoint.](../images/1edb644e-b3d4-4a9b-b92e-4ae2c07341c2.png)
  
 
 #### Add-in event handler architecture strategies
@@ -308,7 +315,7 @@ For example, if your handler needs to take action on an SQL Server database, you
  
 
  
-The SharePoint add-in model doesn't provide a way to store custom server-side code on SharePoint and invoke it from the CSOM (client-side object model). But the CSOM does provide a way to bundle try-catch and if-then-else logic and send it to the server for execution. For a detailed example of a add-in event handler that uses the handler delegation strategy to add a list to a host web, see  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins). For a code sample, see  [OfficeDev/PnP/Samples/Core.AppEvents.HandlerDelegation](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.AppEvents.HandlerDelegation).
+The SharePoint add-in model doesn't provide a way to store custom server-side code on SharePoint and invoke it from the CSOM (client-side object model). But the CSOM does provide a way to bundle try-catch and if-then-else logic and send it to the server for execution. For a detailed example of a add-in event handler that uses the handler delegation strategy to add a list to a host web, see  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md). For a code sample, see  [OfficeDev/PnP/Samples/Core.AppEvents.HandlerDelegation](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.AppEvents.HandlerDelegation.md).
  
 
  
@@ -388,7 +395,7 @@ properties.EventType == SPRemoteEventType.ItemUpdating)
 ```
 
 |
-See  [Add list item properties with a remote event receiver](http://code.msdn.microsoft.com/SharePoint-2013-Add-list-2c6e71e0) for the complete code sample. See [Migrating a SharePoint event receiver to a remote event receiver](http://channel9.msdn.com/Series/Reimagine-SharePoint-Development/Migrating-a-SharePoint-Event-Receiver-to-a-Remote-Event-Receiver) for a detailed demo of the code sample.
+See  [Add list item properties with a remote event receiver](http://code.msdn.microsoft.com/SharePoint-Add-list-2c6e71e0) for the complete code sample. See [Migrating a SharePoint event receiver to a remote event receiver](http://channel9.msdn.com/Series/Reimagine-SharePoint-Development/Migrating-a-SharePoint-Event-Receiver-to-a-Remote-Event-Receiver) for a detailed demo of the code sample.
  
 
  
@@ -424,7 +431,7 @@ Figure 1 shows how remote event receivers work:
  
 
  
-![How remote event receivers work in SharePoint](../../images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png)
+![How remote event receivers work in SharePoint](../images/SP15Con_Remote_Event_Receivers_FAQ_fig1.png)
  
 
  
@@ -434,7 +441,7 @@ Figure 1 shows how remote event receivers work:
 ### How do I debug remote event receivers?
 <a name="RER_DebugRER"> </a>
 
-See  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in). 
+See  [Debug and troubleshoot a remote event receiver in a SharePoint Add-in](debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md). 
  
 
  
@@ -467,10 +474,10 @@ If a SharePoint 2010 solution package containing an event handler is upgraded to
 <a name="SP15handleevents_addlresources"> </a>
 
 
--  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins)
+-  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins.md)
     
  
--  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins)
+-  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md)
     
  
 -  [Introducing remote event receivers in SharePoint](http://www.microsoft.com/resources/msdn/en-us/office/media/video/videol?cid=sdc&amp;from=mscomsdc&amp;VideoID=3ef8f7ae-85a7-44c3-967d-d1620e2a019f)
diff --git a/docs/sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in.md b/docs/sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in.md
index 2422f5b8f8..10f5e3e111 100644
--- a/docs/sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in.md
@@ -1,38 +1,45 @@
+---
+title: Handle list item events in the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Handle list item events in the provider-hosted add-in
 Learn how to handle list item events in a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the tenth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the tenth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
--  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+-  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
     
  
--  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in)
+-  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in.md)
     
  
--  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in)
+-  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in.md)
     
  
--  [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in)
+-  [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in.md)
     
  
--  [Programmatically deploy a custom button in the provider-hosted add-in](programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in)
+-  [Programmatically deploy a custom button in the provider-hosted add-in](programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
 
@@ -123,10 +130,10 @@ You saw in an earlier article in this series that when an order is placed, it is
 ## Create the list item event receiver
 
 
- **Note**  If you have been working through this series of articles, then you have already configured your development environment for debugging remote event receivers. If you have not done that, see  [Configure the solution for event receiver debugging](handle-add-in-events-in-the-provider-hosted-add-in#RERDebug) before you go any further in this topic.
+ **Note**  If you have been working through this series of articles, then you have already configured your development environment for debugging remote event receivers. If you have not done that, see  [Configure the solution for event receiver debugging](handle-add-in-events-in-the-provider-hosted-add-in.md#RERDebug) before you go any further in this topic.
  
 
-The Office Developer Tools for Visual Studio include a  **Remote Event Receiver** item that can be added to a SharePoint Add-in solution. However, at the time this article was written, this project item assumes that the list (with which the receiver will be registered) is on the add-in web, and consequently the tools create an add-in web and some SharePoint artifacts in it. But the receiver for the Chain Store add-in is going to be registered (in a later step) with the **Expected Shipments** list on the host web, so the add-in does not need an add-in web. (For a reminder of the distinction between add-in webs and host webs, see [SharePoint Add-ins](sharepoint-add-ins).)
+The Office Developer Tools for Visual Studio include a  **Remote Event Receiver** item that can be added to a SharePoint Add-in solution. However, at the time this article was written, this project item assumes that the list (with which the receiver will be registered) is on the add-in web, and consequently the tools create an add-in web and some SharePoint artifacts in it. But the receiver for the Chain Store add-in is going to be registered (in a later step) with the **Expected Shipments** list on the host web, so the add-in does not need an add-in web. (For a reminder of the distinction between add-in webs and host webs, see [SharePoint Add-ins](sharepoint-add-ins.md).)
  
 
  
@@ -564,7 +571,7 @@ expectedShipmentsList.EventReceivers.Add(receiver);
  
 3. Ensure that the  **Define DEBUG constant** box is checked. (It usually is by default.) The following screen shot shows the proper setting.
     
-  ![The Build sub-tab of the Properties tab in Visual Studio. The Configuration drop down is set to Debug. The check box for "Define DEBUG constant" is checked.](../../images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG)
+  ![The Build sub-tab of the Properties tab in Visual Studio. The Configuration drop down is set to Debug. The check box for "Define DEBUG constant" is checked.](../images/4f81174f-d875-4a9e-bff4-adea0f176f00.PNG)
  
 
  
@@ -572,7 +579,7 @@ expectedShipmentsList.EventReceivers.Add(receiver);
  
 4. Change the  **Configuration** drop down to **Release**, and then ensure that the  **Define DEBUG constant** box is ***not*** checked. (It usually is not by default.) The following screen shot shows the proper setting.
     
-  ![The Build sub-tab of the Properties tab. The Configuration drop down says Release. The check box for "Define DEBUG constant" is not checked.](../../images/7fd942de-a324-4f70-a750-f5304c993832.PNG)
+  ![The Build sub-tab of the Properties tab. The Configuration drop down says Release. The check box for "Define DEBUG constant" is not checked.](../images/7fd942de-a324-4f70-a750-f5304c993832.PNG)
  
 
  
@@ -612,7 +619,7 @@ The add-in event and list item event receivers are Windows Communication Service
  
 5. When the breakpoint is hit, hover the cursor over the  `debugEndpoint` variable. When the Visual Studio Data Tip appears, click the down arrow and select **Text Visualizer**.
     
-  ![A Visual Studio text visualizer with an Azure Service Bus URL in it.](../../images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG)
+  ![A Visual Studio text visualizer with an Azure Service Bus URL in it.](../images/494cf01e-3e17-4092-b239-9312ac4ab258.PNG)
  
 
  
@@ -685,21 +692,21 @@ The add-in event and list item event receivers are Windows Communication Service
 ## 
 <a name="Nextsteps"> </a>
 
-See  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options) to learn how to publish your add-in to a SharePoint site. Or go on to advanced work in SharePoint add-in development with these nodes of MSDN:
+See  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md) to learn how to publish your add-in to a SharePoint site. Or go on to advanced work in SharePoint add-in development with these nodes of MSDN:
  
 
  
 
--  [Design SharePoint Add-ins](design-sharepoint-add-ins)
+-  [Design SharePoint Add-ins](design-sharepoint-add-ins.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
--  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins)
+-  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md b/docs/sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md
index f14544da2c..0394cbed2f 100644
--- a/docs/sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md
@@ -1,24 +1,30 @@
+---
+title: Handle security tokens in provider-hosted low-trust SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Handle security tokens in provider-hosted low-trust SharePoint Add-ins
 Learn about the context, access, and refresh tokens that are used for authorization by low-trust, provider-hosted SharePoint Add-ins, and how to work with them in your code.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Important**   **This article is entirely about the use of security tokens in the low-trust authorization system, not the high-trust system.** For information about the use of tokens in the high-trust system, see [Create and use access tokens in provider-hosted high-trust SharePoint Add-ins](create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins).
+ **Important**   **This article is entirely about the use of security tokens in the low-trust authorization system, not the high-trust system.** For information about the use of tokens in the high-trust system, see [Create and use access tokens in provider-hosted high-trust SharePoint Add-ins](create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md).
  
 
 
- **SharePoint Add-ins that use the  [low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization) to gain access to SharePoint data participate in an OAuthflow that involves the passing of security tokens (in [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/) format) among SharePoint, Microsoft Azure Access Control Service (ACS), the remote components of the SharePoint Add-in, and, in some cases, the user's browser.** There are different flows depending on the design of the add-in, but all of them involve at least the following two types of tokens:
+ **SharePoint Add-ins that use the  [low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization.md) to gain access to SharePoint data participate in an OAuthflow that involves the passing of security tokens (in [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/) format) among SharePoint, Microsoft Azure Access Control Service (ACS), the remote components of the SharePoint Add-in, and, in some cases, the user's browser.** There are different flows depending on the design of the add-in, but all of them involve at least the following two types of tokens:
  
 
 
 -  **Access token:** Included in each create, read, update, or delete (CRUD) request from the remote components of the add-in to SharePoint. SharePoint validates the token and serves the request.
     
  
--  **Refresh token:** Used to obtain a first access token in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows), and to replace expiring access tokens in both the Context Token flow and the  [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows) of the low-trust authorization system.
+-  **Refresh token:** Used to obtain a first access token in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows), and to replace expiring access tokens in both the Context Token flow and the  [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows) of the low-trust authorization system.
     
  
 Depending on which OAuth flow the add-in is using, one or the other of the following is also part of the process:
@@ -83,7 +89,7 @@ Depending on your SharePoint Add-in's architecture and the hosting platform, the
     
  
 
- **Note**  In most scenarios, you won't be able to use terms as simple as "AccessToken" as the caching key because your add-in must keep the tokens for different users and SharePoint farms/tenancies distinct. If your add-in uses the  [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows), there is special  **CacheKey** provided by SharePoint that can be used to distinguish cached tokens. This section explains what the issues are and what to do when your application is not using the Context Token flow.
+ **Note**  In most scenarios, you won't be able to use terms as simple as "AccessToken" as the caching key because your add-in must keep the tokens for different users and SharePoint farms/tenancies distinct. If your add-in uses the  [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows), there is special  **CacheKey** provided by SharePoint that can be used to distinguish cached tokens. This section explains what the issues are and what to do when your application is not using the Context Token flow.
  
 
 Caching the access token in session state is fine for most scenarios. If the remote web application is accessing other services that use OAuth (in addition to SharePoint) and it is caching the various access tokens in session state, be sure to use distinct cache keys for the tokens; for example, instead of "AccessToken", use "SharePoint_AccessToken", "Facebook_AccessToken", "SAP_Gateway_AccessToken", etc. . (If you are not using session state or some other caching that automatically separates each user's cache, you would need also to relativize your keys for user.)
@@ -126,7 +132,7 @@ a SharePoint Add-in may have backend servers that are not hosted in the same dom
 ### Handle expired access tokens
 <a name="Expired"> </a>
 
-An access token expires after a few hours (twelve hours as of the time this article was written, but that can change). If the application is still accessing SharePoint after the access token expires, then the first request to SharePoint after the expiration results in a  **401 Unauthorized** error. Your code has to handle this response. Alternatively, the code can test the expiration time of the access token before it is used. **Your code uses the refresh token to obtain another access token from ACS.** In the Context Token flow, the refresh token is included in the context token that your add-in receives from SharePoint at the start of its first session with SharePoint. In the Authorization Code flow, it is passed to the application along with the first access token. Your code must cache it so it is available when needed. The refresh token lasts a few months and can be persisted in a cookie or in server-side storage. For more information, see [Understand the handling and caching of refresh tokens](#RefreshToken).
+An access token expires after a few hours (twelve hours as of the time this article was written, but that can change). If the application is still accessing SharePoint after the access token expires, then the first request to SharePoint after the expiration results in a  **401 Unauthorized** error. Your code has to handle this response. Alternatively, the code can test the expiration time of the access token before it is used. **Your code uses the refresh token to obtain another access token from ACS.** In the Context Token flow, the refresh token is included in the context token that your add-in receives from SharePoint at the start of its first session with SharePoint. In the Authorization Code flow, it is passed to the application along with the first access token. Your code must cache it so it is available when needed. The refresh token lasts a few months and can be persisted in a cookie or in server-side storage. For more information, see [Understand the handling and caching of refresh tokens](#RefreshTokens).
  
 
  
@@ -145,7 +151,7 @@ This section describes, with examples, access tokens and shows how they differ d
  
 
  
-The following is a decoded  **example of a user+add-in access token generated by ACS** to be used for calls to SharePoint using the [user+add-in policy](add-in-authorization-policy-types-in-sharepoint-2013). White space has been added for readability. The token complies with the  [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/?include_text=1) protocol. The JavaScript Object Notation (JSON) object in the token is called theclaim set See table 1 for details about the properties in the claim set. Note that all the values must be lower-case. (User+add-in access tokens are the same in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows) and the [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows).)
+The following is a decoded  **example of a user+add-in access token generated by ACS** to be used for calls to SharePoint using the [user+add-in policy](add-in-authorization-policy-types-in-sharepoint.md). White space has been added for readability. The token complies with the  [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/?include_text=1) protocol. The JavaScript Object Notation (JSON) object in the token is called theclaim set See table 1 for details about the properties in the claim set. Note that all the values must be lower-case. (User+add-in access tokens are the same in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows) and the [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows).)
  
 
  
@@ -181,7 +187,7 @@ The following is a decoded  **example of a user+add-in access token generated by
  
 
  
-The following is a decoded  **example of an add-in-only access token generated by ACS** to be used for calls to SharePoint using the [add-in-only policy](add-in-authorization-policy-types-in-sharepoint-2013). White space has been added for readability. The token complies with the  [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/?include_text=1) protocol. See table 2 for details about the properties in the claim set. (The add-in-only policy is not available for applications that use the [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows), because they do not have an add-in manifest file and, thus, cannot request permission to use add-in-only calls.)
+The following is a decoded  **example of an add-in-only access token generated by ACS** to be used for calls to SharePoint using the [add-in-only policy](add-in-authorization-policy-types-in-sharepoint.md). White space has been added for readability. The token complies with the  [JSON Web Token](http://datatracker.ietf.org/doc/draft-ietf-oauth-json-web-token/?include_text=1) protocol. See table 2 for details about the properties in the claim set. (The add-in-only policy is not available for applications that use the [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows), because they do not have an add-in manifest file and, thus, cannot request permission to use add-in-only calls.)
  
 
  
@@ -221,7 +227,7 @@ The following is a decoded  **example of an add-in-only access token generated b
 ## Understand the structure and handling of context tokens
 <a name="ContextTokens"> </a>
 
-A context token is used only in the  [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows) of the low-trust authorization system. **When the SharePoint Add-in is launched in SharePoint, SharePoint requests that Azure ACS create a context token that SharePoint then passes on to the remote component of the SharePoint Add-in.** The token is passed as a hidden form parameter called **SPAppToken** in a request from SharePoint for the start page of the remote component. The token is signed with a client secret known only to ACS and the SharePoint Add-in. The **context token includes a refresh token that the add-in uses**, along with other information from the context token, **to request an access token** from ACS. (When this article was written, ACS-issued context tokens for SharePoint had a life span of 12 hours, but that could change.) The **main tasks for the code in the SharePoint Add-in** are the following:
+A context token is used only in the  [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows) of the low-trust authorization system. **When the SharePoint Add-in is launched in SharePoint, SharePoint requests that Azure ACS create a context token that SharePoint then passes on to the remote component of the SharePoint Add-in.** The token is passed as a hidden form parameter called **SPAppToken** in a request from SharePoint for the start page of the remote component. The token is signed with a client secret known only to ACS and the SharePoint Add-in. The **context token includes a refresh token that the add-in uses**, along with other information from the context token, **to request an access token** from ACS. (When this article was written, ACS-issued context tokens for SharePoint had a life span of 12 hours, but that could change.) The **main tasks for the code in the SharePoint Add-in** are the following:
  
 
  
@@ -255,7 +261,7 @@ SharePointContextToken contextToken =
     Request.Url.Authority);
 ```
 
-For an example of how to do some of these tasks with PHP, see the sample  [SharePoint: Perform operations on SharePoint Document Library from PHP site](https://code.msdn.microsoft.com/SharePoint-2013-Perform-8a78b8ef).
+For an example of how to do some of these tasks with PHP, see the sample  [SharePoint: Perform operations on SharePoint Document Library from PHP site](https://code.msdn.microsoft.com/SharePoint-Perform-8a78b8ef).
  
 
  
@@ -325,7 +331,7 @@ Your application does not have to use the same cache for everything it is cachin
 - The realm GUID of the SharePoint farm or SharePoint Online tenancy to which the add-in is seeking access.
     
  
-The TokenHelper.cs (or .vb) file has code that creates this request. For an example of PHP code that does this, see  [SharePoint: Perform operations on SharePoint Document Library from PHP site](http://code.msdn.microsoft.com/office/SharePoint-2013-Perform-8a78b8ef/sourcecode?fileId=117521&amp;pathId=1932320454).
+The TokenHelper.cs (or .vb) file has code that creates this request. For an example of PHP code that does this, see  [SharePoint: Perform operations on SharePoint Document Library from PHP site](http://code.msdn.microsoft.com/office/SharePoint-Perform-8a78b8ef/sourcecode?fileId=117521&amp;pathId=1932320454).
  
 
  
@@ -433,7 +439,7 @@ If you want to limit access to your remote component, such as a WCF service, to
 ## Understand the handling and caching of refresh tokens
 <a name="RefreshTokens"> </a>
 
- **A refresh token is included in the context token that SharePoint posts to your web application when it is launched.** The refresh token is an encrypted token that your SharePoint Add-in cannot unencrypt. **Your code uses it**, along with other information, **to get a new access token when the current access token expires**. It is also used to get the *first*  access token in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows). (When this article was written, ACS-issued refresh tokens for SharePoint had a life span of 6 months, but that could change.)
+ **A refresh token is included in the context token that SharePoint posts to your web application when it is launched.** The refresh token is an encrypted token that your SharePoint Add-in cannot unencrypt. **Your code uses it**, along with other information, **to get a new access token when the current access token expires**. It is also used to get the *first*  access token in the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows). (When this article was written, ACS-issued refresh tokens for SharePoint had a life span of 6 months, but that could change.)
  
 
  
@@ -448,7 +454,7 @@ Since an access token lasts hours (currently 12) and an end user gets a new one
 - The add-in's design enables users to schedule the add-in to access SharePoint sometime after the session ends.
     
  
-Both  **scenarios require your add-in to cache the refresh token**, and second scenario requires a server-side cache that is durable across sessions. Your caching options are the same as those for the [access token](#CacheAccessToken) and, in the Context Token flow, you can use [the cache key in the context token](#CacheKey). (In the Context Token flow, you usually just cache the context token. It contains the refresh token and other information you need to get a new access token. In the  [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows), there is no context token, so you cache the refresh token itself.)
+Both  **scenarios require your add-in to cache the refresh token**, and second scenario requires a server-side cache that is durable across sessions. Your caching options are the same as those for the [access token](#CacheAccessToken) and, in the Context Token flow, you can use [the cache key in the context token](#CacheKey). (In the Context Token flow, you usually just cache the context token. It contains the refresh token and other information you need to get a new access token. In the  [Authorization Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows), there is no context token, so you cache the refresh token itself.)
  
 
  
@@ -456,7 +462,7 @@ If you are caching the refresh token in a storage that persists across a specifi
  
 
  
-If the refresh token is expired, a request to ACS for a new access token will result in a  **401 Unauthorized** error. Your add-in should respond to this error by getting a new refresh token and using it to get a new access token. (Since the refresh token is encrypted, your code cannot check its expiration before using it.) In the Context Token flow, your add-in gets a new refresh token by [getting a new context token](#GetNewContextToken). In the Authorization Code flow, your add-in gets a new refresh token by restarting the flow. Specifically, your code should respond to the error by redirecting the user to the SharePoint OAuthAuthorize.aspx page as explained in  [Understand the OAuth flow for add-ins that request permissions on the fly](authorization-code-oauth-flow-for-sharepoint-add-ins#Flow).
+If the refresh token is expired, a request to ACS for a new access token will result in a  **401 Unauthorized** error. Your add-in should respond to this error by getting a new refresh token and using it to get a new access token. (Since the refresh token is encrypted, your code cannot check its expiration before using it.) In the Context Token flow, your add-in gets a new refresh token by [getting a new context token](#GetNewContextToken). In the Authorization Code flow, your add-in gets a new refresh token by restarting the flow. Specifically, your code should respond to the error by redirecting the user to the SharePoint OAuthAuthorize.aspx page as explained in  [Understand the OAuth flow for add-ins that request permissions on the fly](authorization-code-oauth-flow-for-sharepoint-add-ins.md#Flow).
  
 
  
@@ -464,7 +470,7 @@ If the refresh token is expired, a request to ACS for a new access token will re
 ## Understanding the handling authorization codes
 <a name="Authcodes"> </a>
 
- **In the Authorization Code flow, the authorization process begins with an authorization code that ACS issues, at the request of SharePoint, and which SharePoint then passes to the remote application** as a query parameter. The authorization code is unique to each pair of user and remote application. (When this article was written, ACS-issued authorization codes for SharePoint had a life span of 5 minutes, but that could change.) The logic in **your application must get the authorization code from the query parameter and use it in a request to ACS for an access token**. If you are using managed code, sample code for creating the token is in the TokenHelper.cs (and .vb) file. Sample code for reading the query parameter is in [Get sample code behind for a page that accesses SharePoint](authorization-code-oauth-flow-for-sharepoint-add-ins#Default). ACS invalidates the authorization code immediately after issuing the access token, so it can only be used once and there is no point in caching it.
+ **In the Authorization Code flow, the authorization process begins with an authorization code that ACS issues, at the request of SharePoint, and which SharePoint then passes to the remote application** as a query parameter. The authorization code is unique to each pair of user and remote application. (When this article was written, ACS-issued authorization codes for SharePoint had a life span of 5 minutes, but that could change.) The logic in **your application must get the authorization code from the query parameter and use it in a request to ACS for an access token**. If you are using managed code, sample code for creating the token is in the TokenHelper.cs (and .vb) file. Sample code for reading the query parameter is in [Get sample code behind for a page that accesses SharePoint](authorization-code-oauth-flow-for-sharepoint-add-ins.md#Default). ACS invalidates the authorization code immediately after issuing the access token, so it can only be used once and there is no point in caching it.
  
 
  
@@ -495,13 +501,13 @@ The free  [Fiddler tool](http://www.telerik.com/fiddler) can be used to capture
 <a name="bk_addresources"> </a>
 
 
--  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization)
+-  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md)
     
  
-- For code samples that use managed code and TokenHelper, see  [SharePoint: Hello World remote add-in using CSOM](http://code.msdn.microsoft.com/SharePoint-2013-Hello-0fd15fbf) and [SharePoint Add-ins sample pack](http://code.msdn.microsoft.com/office/Apps-for-SharePoint-sample-64c80184)
+- For code samples that use managed code and TokenHelper, see  [SharePoint: Hello World remote add-in using CSOM](http://code.msdn.microsoft.com/SharePoint-Hello-0fd15fbf) and [SharePoint Add-ins sample pack](http://code.msdn.microsoft.com/office/Apps-for-SharePoint-sample-64c80184)
     
  
-- For a code sample that uses REST calls from a PHP add-in:  [SharePoint: Perform operations on SharePoint Document Library from PHP site](https://code.msdn.microsoft.com/SharePoint-2013-Perform-8a78b8ef)
+- For a code sample that uses REST calls from a PHP add-in:  [SharePoint: Perform operations on SharePoint Document Library from PHP site](https://code.msdn.microsoft.com/SharePoint-Perform-8a78b8ef)
     
  
 
diff --git a/docs/sp-add-ins/high-trust-configuration-scripts-for-sharepoint.md b/docs/sp-add-ins/high-trust-configuration-scripts-for-sharepoint.md
index ccbcd59930..bce424f1a7 100644
--- a/docs/sp-add-ins/high-trust-configuration-scripts-for-sharepoint.md
+++ b/docs/sp-add-ins/high-trust-configuration-scripts-for-sharepoint.md
@@ -1,16 +1,22 @@
+---
+title: High-trust configuration scripts for SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # High-trust configuration scripts for SharePoint
 Get customizable Windows PowerShell scripts that configure a Microsoft SharePoint farm to use a high-trust SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## How to use the scripts
 <a name="Usage"> </a>
 
-The scripts below are used to designate one or more X.509 digital certificates as trusted issuers of access tokens in a staging or production Microsoft SharePoint farm. (For a script that is more appropriate for an SharePoint Add-ins development environment, see  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins).) No single set of scripts can work for every SharePoint farm because there are too many different ways that the certificates can be acquired and stored. For that reason, please note the following:
+The scripts below are used to designate one or more X.509 digital certificates as trusted issuers of access tokens in a staging or production Microsoft SharePoint farm. (For a script that is more appropriate for an SharePoint Add-ins development environment, see  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md).) No single set of scripts can work for every SharePoint farm because there are too many different ways that the certificates can be acquired and stored. For that reason, please note the following:
  
 
  
@@ -21,7 +27,7 @@ The scripts below are used to designate one or more X.509 digital certificates a
 - These scripts should be thought of as drafts that may need to be customized.
     
  
-- They are used as part of the overall process of publishing a high-trust SharePoint Add-in. They should only be used by someone familiar with the topics  [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization) and [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins) and the prerequisites listed in them.
+- They are used as part of the overall process of publishing a high-trust SharePoint Add-in. They should only be used by someone familiar with the topics  [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization.md) and [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md) and the prerequisites listed in them.
     
  
 - They should also be reviewed and customized as needed by someone familiar with the add-in customer's certificate policies.
@@ -39,7 +45,7 @@ The scripts below are used to designate one or more X.509 digital certificates a
     To find the user account that an application pool is using, open IIS Manager on a SharePoint server and double-click  **Application Pools** in the **Connections** pane. The **Identity** column in the **Application Pools** list that opens shows the users for the application pools.
     
  
-- The instructions for the two major scripts also assume that the certificate(s) have been installed to IIS on server(s) that host the remote web application(s). For instructions, see  [Configure the remote web server with the certificate](package-and-publish-high-trust-sharepoint-add-ins#ConfigureRemote).
+- The instructions for the two major scripts also assume that the certificate(s) have been installed to IIS on server(s) that host the remote web application(s). For instructions, see  [Configure the remote web server with the certificate](package-and-publish-high-trust-sharepoint-add-ins.md#ConfigureRemote).
     
  
 See specific usage notes for each script in the sections below.
diff --git a/docs/sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint.md b/docs/sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint.md
index 3f3e03952d..93124ab01d 100644
--- a/docs/sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint.md
+++ b/docs/sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint.md
@@ -1,3 +1,9 @@
+---
+title: Highlight content and enhance the functionality of SharePoint-hosted SharePoint Add-ins with the callout control
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Highlight content and enhance the functionality of SharePoint-hosted SharePoint Add-ins with the callout control
 The SharePoint callout control provides a flexible way to engage your user and showcase your SharePoint-hosted app's functionality. You can configure it in a variety of ways to suit your app's UI. This article shows you how to construct this control, add it to your page, and customize its appearance and behavior.
@@ -10,14 +16,14 @@ When you do searches in a SharePoint site, you'll see examples of the callout co
  
 
  
-![Example of the callout control on a SharePoint search results page](../../images/S15_CalloutControlExample.png)
+![Example of the callout control on a SharePoint search results page](../images/S15_CalloutControlExample.png)
  
 
  
 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -94,7 +100,7 @@ You can use these members to control the display of callout.
 |content|Display HTML inside the control whenever there is no value for the  `contentElement` member.|string containing HTML,  **null**, must be null if `contentElement` has a value|
 |contentElement|Display an HTML element inside the control when there is no value for the  `content` member.|any HTML element,  **null**, must be null if `content` has a value|
 |contentWidth|Specify the width, in pixels, of the callout body container. This container also has a 1-pixel border and 15-pixel padding on each side, so the control is 32 pixels wider than the body width that you specify. The control's CSS  `overflow` property is set to `hidden`, so your content will be clipped if it does not fit inside the width that you specify. If you set this member on an open callout, the change will take effect immediately. This is not true of the other members.|Any number between 240 and 610,  **350** (making the control 382 pixels wide by default)|
-|beakOrientation|Specify the orientation of the beak or pointer of the callout control.|**topBottom**, to look like this (Figure 2):**Figure 2. Where the callout control's beak appears with the topBottom orientation** ![Where the callout control's beak appears with the topbottom orientation](../../images/SP15_CalloutTopBottom.png) **leftRight**, to look like this (Figure 3):**Figure 3. Where the callout control's beak appears with the leftright orientation** ![Where the callout control's beak appears with the leftright orientation](../../images/SP15_CalloutLeftRight.png)|
+|beakOrientation|Specify the orientation of the beak or pointer of the callout control.|**topBottom**, to look like this (Figure 2):**Figure 2. Where the callout control's beak appears with the topBottom orientation** ![Where the callout control's beak appears with the topbottom orientation](../images/SP15_CalloutTopBottom.png) **leftRight**, to look like this (Figure 3):**Figure 3. Where the callout control's beak appears with the leftright orientation** ![Where the callout control's beak appears with the leftright orientation](../images/SP15_CalloutLeftRight.png)|
 
 ## How to customize the behavior of the callout control
 <a name="Behavior"> </a>
@@ -212,7 +218,7 @@ When a callout action contains a menu instead of a single action, the user sees
  
 
  
-![A callout action displays a menu when a user clicks on the arrow next to the action label.](../../images/SP15_CalloutMenu.png)
+![A callout action displays a menu when a user clicks on the arrow next to the action label.](../images/SP15_CalloutMenu.png)
  
 You can create as many menu entries as you want and add them to the callout action by passing them in an array, as the value of the  `menuEntries` member of the `CalloutAction` object.
  
@@ -400,13 +406,13 @@ callout.set({positionAlgorithm: tryDownAndRightThenGoDefault});
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint: Use list views, callouts, and dialogs in SharePoint-hosted add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-2013-Use-list-cb3e4e14)
+-  [SharePoint: Use list views, callouts, and dialogs in SharePoint-hosted add-ins](http://code.msdn.microsoft.com/officeapps/SharePoint-Use-list-cb3e4e14)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md b/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md
index 2e99139bd9..975e4d5881 100644
--- a/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md
+++ b/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md
@@ -1,16 +1,22 @@
+---
+title: Host webs, add-in webs, and SharePoint components in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Host webs, add-in webs, and SharePoint components in SharePoint
 Learn about the distinction between host webs and add-in webs. Also find out which SharePoint components can be included in a SharePoint Add-in, which are deployed to the host web, which are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Host webs, add-in webs, and the isolated domain
 <a name="IsolatedDomain"> </a>
 
-When an add-in that includes SharePoint components is installed on a website, it is listed on the  **Site Contents** page from which it can be launched. That listing, which is the launch point of the add-in, is the only required addition to the website, although certain other things can optionally be added, such as a custom action or an add-in part. For information about these options, see [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap#AccessingApp). Other than these UI elements, the SharePoint Add-in components and content, such as lists, content types, workflows, and pages, are deployed to a different website in a special isolated domain. This fact is largely hidden from the user. The special website to which the add-in is  *deployed*  is called anadd-in web. The website to which the add-in is  *installed*  is called thehost web. Although the add-in web has its own isolated domain, it is in the same site collection as the host web. (One exception to this rule is when the add-in is installed with tenant scope. In that scenario, the add-in web is in the site collection of the corporate add-in catalog.) 
+When an add-in that includes SharePoint components is installed on a website, it is listed on the  **Site Contents** page from which it can be launched. That listing, which is the launch point of the add-in, is the only required addition to the website, although certain other things can optionally be added, such as a custom action or an add-in part. For information about these options, see [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#AccessingApp). Other than these UI elements, the SharePoint Add-in components and content, such as lists, content types, workflows, and pages, are deployed to a different website in a special isolated domain. This fact is largely hidden from the user. The special website to which the add-in is  *deployed*  is called anadd-in web. The website to which the add-in is  *installed*  is called thehost web. Although the add-in web has its own isolated domain, it is in the same site collection as the host web. (One exception to this rule is when the add-in is installed with tenant scope. In that scenario, the add-in web is in the site collection of the corporate add-in catalog.) 
  
 
  
@@ -24,7 +30,7 @@ Figure 1 shows a host web with two SharePoint Add-ins installed. Add-in 1 has re
  
 
  
-![Host web, app web, and their components.](../../images/HostWebAndAppWeb.png)
+![Host web, app web, and their components.](../images/HostWebAndAppWeb.png)
  
 For example, suppose that an add-in, with SharePoint components beyond just the UI elements that can be deployed to a host web, is installed on a host website at the following URL:
  
@@ -79,12 +85,12 @@ There are two primary reasons why SharePoint components are deployed to add-in w
 
  
 
--  **Enforcement of add-in permissions:** In the model for SharePoint Add-ins, an add-in has its own identity and it has permissions that are not necessarily the same as the permissions of the user who is executing the add-in. These add-in permissions are requested when the add-in is installed and granted by the person who installs the add-in, as long as person has all the permissions that the add-in requests. (If the user who is installing the add-in does not have all the permissions that are requested by the add-in, the user cannot install the add-in.) By giving each add-in its own domain, SharePoint can reliably identify requests made by the add-in and verify the permissions of the add-in. For more information about add-in permissions, see [Add-in permissions](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap#AppPermissions).
+-  **Enforcement of add-in permissions:** In the model for SharePoint Add-ins, an add-in has its own identity and it has permissions that are not necessarily the same as the permissions of the user who is executing the add-in. These add-in permissions are requested when the add-in is installed and granted by the person who installs the add-in, as long as person has all the permissions that the add-in requests. (If the user who is installing the add-in does not have all the permissions that are requested by the add-in, the user cannot install the add-in.) By giving each add-in its own domain, SharePoint can reliably identify requests made by the add-in and verify the permissions of the add-in. For more information about add-in permissions, see [Add-in permissions](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#AppPermissions).
     
  
 -  **Cross-domain scripting security:** Modern browsers support a "same origin policy" with regard to JavaScript method calls. By deploying each SharePoint Add-in to its own domain, SharePoint takes advantage of the browser's same origin policy to ensure that JavaScript in the SharePoint Add-in cannot execute any JavaScript from any other domain, including the domain in which, from the end-user's perspective, the add-in is installed.
     
-    SharePoint also provides a means of safely overcoming the limits of the policy. Among other things, this enables the remote components of a SharePoint Add-in to query data from any website in the common parent tenancy of the host and add-in webs. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+    SharePoint also provides a means of safely overcoming the limits of the policy. Among other things, this enables the remote components of a SharePoint Add-in to query data from any website in the common parent tenancy of the host and add-in webs. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
     
  
 
@@ -182,7 +188,7 @@ The following are some caveats and details concerning the deployment of certain
 -  **Microsoft Business Connectivity Services (BCS) models, external content types, and external lists:**Business Data Connectivity (BDC) service models typically have a scope that is wider than a site collection. However, when a Business Data Connectivity (BDC) service model is deployed in an add-in, its scope is limited to the add-in web. When a Business Data Connectivity (BDC) service model is included in an add-in, it is not stored in the Business Data Connectivity (BDC) service shared service store. Instead, it is stored as a file in the add-in web.
     
  
--  **Web Templates:** In most cases, you will want the add-in web to instantiate the new built-in site definition configuration **APP#0**, which is optimized for add-in webs. (For more information about it, see  [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#AccessingApp).) SharePoint automatically uses  **APP#0** when the add-in package does not include a [WebTemplate](http://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx) element.
+-  **Web Templates:** In most cases, you will want the add-in web to instantiate the new built-in site definition configuration **APP#0**, which is optimized for add-in webs. (For more information about it, see  [Accessing the add-in from the UI](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#AccessingApp).) SharePoint automatically uses  **APP#0** when the add-in package does not include a [WebTemplate](http://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx) element.
     
     You can also define a custom site type for the add-in web. There are two major steps to doing this:
     
@@ -196,7 +202,7 @@ The following are some caveats and details concerning the deployment of certain
 ```
 
 
-     **Note**  The new  [WebTemplate](http://msdn.microsoft.com/library/62302903-e97a-a9a3-a64e-13176a7c4e1e%28Office.15%29.aspx) element for add-in manifests is not the same markup as the [WebTemplate](http://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx) element that can be included in Features. The **WebTemplate** element that can be included in Features defines a type of site, but the **WebTemplate** element for add-in manifests simply identifies what type of site to use. For more information about the add-in manifest of a SharePoint Add-in, see [Add-in package structure](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#SPAppModelArch_Package).
+     **Note**  The new  [WebTemplate](http://msdn.microsoft.com/library/62302903-e97a-a9a3-a64e-13176a7c4e1e%28Office.15%29.aspx) element for add-in manifests is not the same markup as the [WebTemplate](http://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx) element that can be included in Features. The **WebTemplate** element that can be included in Features defines a type of site, but the **WebTemplate** element for add-in manifests simply identifies what type of site to use. For more information about the add-in manifest of a SharePoint Add-in, see [Add-in package structure](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#SPAppModelArch_Package).
 
      **Caution**  Do not use the  **WebTemplate** element in the add-in manifest to designate any of the built-in SharePoint site definition configurations as the add-in web's site type. We do not support using any of the built-in site definition configurations, other than **APP#0**, for add-in webs. 
 
@@ -208,7 +214,7 @@ The following are some caveats and details concerning the deployment of certain
 <a name="SP15hostedwebs_bk_addlresources"> </a>
 
 
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 -  [SharePoint Add-ins compared with SharePoint solutions](http://msdn.microsoft.com/library/0e9efadb-aaf2-4c0d-afd5-d6cf25c4e7a8%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md b/docs/sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md
index ae9512a800..1adf902b8c 100644
--- a/docs/sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md
+++ b/docs/sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md
@@ -1,9 +1,15 @@
+---
+title: Important aspects of the SharePoint Add-in architecture and development landscape
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Important aspects of the SharePoint Add-in architecture and development landscape
-Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface options, deployment system, security system, and lifecycle. This article supplements the information in the article  [SharePoint Add-ins](sharepoint-add-ins).
+Learn about aspects of the architecture of SharePoint Add-ins and the model for SharePoint Add-ins, including the add-in hosting options, user interface options, deployment system, security system, and lifecycle. This article supplements the information in the article  [SharePoint Add-ins](sharepoint-add-ins.md).
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -21,7 +27,7 @@ The SharePoint add-in model provides the following ways to host the components o
 -  **SharePoint-hosted:** Add-ins that include only SharePoint components and logic that runs on the client.
     
  
-For more detailed information about hosting options and some guidance for how to choose between them, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in).
+For more detailed information about hosting options and some guidance for how to choose between them, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md).
  
 
  
@@ -33,7 +39,7 @@ The website to which a SharePoint Add-in is installed is called the host web. Ho
  
 
  
-As a general rule, any SharePoint component that does not include custom code that runs on the SharePoint servers can be included in a SharePoint Add-in (and be deployed to the add-in web). There are, however, some exceptions and some nuances to how and where the components are deployed. For more information about these nuances and about host webs, the isolated add-in webs, and Features in add-ins, see  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013).
+As a general rule, any SharePoint component that does not include custom code that runs on the SharePoint servers can be included in a SharePoint Add-in (and be deployed to the add-in web). There are, however, some exceptions and some nuances to how and where the components are deployed. For more information about these nuances and about host webs, the isolated add-in webs, and Features in add-ins, see  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md).
  
 
  
@@ -53,7 +59,7 @@ Another way that a SharePoint Add-in can be surfaced is through an add-in part,
  **Note**  You can also deploy add-in parts to the add-in web. To implement this, the markup for the Web Part would be part of a Feature inside a .wsp file in the add-in package, not in the host web Feature.
  
 
-We recommend that you try to give your add-ins a SharePoint appearance to the extent possible, although that is not mandatory and may not always be the best choice. For more information about the user experience guidelines, see  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins). 
+We recommend that you try to give your add-ins a SharePoint appearance to the extent possible, although that is not mandatory and may not always be the best choice. For more information about the user experience guidelines, see  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md). 
  
 
  
@@ -61,7 +67,7 @@ There is, for example, a special master page called app.master. This page is opt
  
 
  
-Another tool you can use to help your add-ins maintain a consistent look and feel with SharePoint is the chrome control that ships with SharePoint. This control enables you to add the SharePoint navigation header area to your add-in pages, including pages hosted externally. For more information about UX design in SharePoint Add-ins, see  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins). For more information about the chrome control, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins).
+Another tool you can use to help your add-ins maintain a consistent look and feel with SharePoint is the chrome control that ships with SharePoint. This control enables you to add the SharePoint navigation header area to your add-in pages, including pages hosted externally. For more information about UX design in SharePoint Add-ins, see  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md). For more information about the chrome control, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md).
  
 
  
@@ -69,7 +75,7 @@ Another tool you can use to help your add-ins maintain a consistent look and fee
 ## Add-in package structure
 <a name="SPAppModelArch_Package"> </a>
 
-A SharePoint Add-in package is a file that has an ".app" extension and that complies with the  [Open Packaging Conventions (OPC)](http://msdn.microsoft.com/en-us/magazine/cc163372.aspx). (You can open the file by adding ".zip" as an extra extension on the filename and then opening it in Windows Explorer.) It contains an add-in manifest that specifies certain properties of the add-in and instructions to the SharePoint installation infrastructure. For more information about the add-in manifest and package, see  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in).
+A SharePoint Add-in package is a file that has an ".app" extension and that complies with the  [Open Packaging Conventions (OPC)](http://msdn.microsoft.com/en-us/magazine/cc163372.aspx). (You can open the file by adding ".zip" as an extra extension on the filename and then opening it in Windows Explorer.) It contains an add-in manifest that specifies certain properties of the add-in and instructions to the SharePoint installation infrastructure. For more information about the add-in manifest and package, see  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md).
  
 
  
@@ -93,7 +99,7 @@ You must request, in the add-in manifest file, the permissions that an add-in ne
  
 
  
-For more information about add-in permissions, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+For more information about add-in permissions, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
  
@@ -101,7 +107,7 @@ For more information about add-in permissions, see  [Add-in permissions in Share
 ### Selective delegation and authorization
 <a name="SelectiveAuthorization"> </a>
 
-Neither users who are launching an add-in, nor resource owners who are granting an add-in permission to access a resource, need to provide the add-in their credentials or password. Instead, SharePoint enables users and resource owners to grant only the specific permissions that the add-in requests. What makes this possible is the use by SharePoint of the transaction protocol  [OAuth 2.0](http://tools.ietf.org/html/draft-ietf-oauth-v2-22). For more information about OAuth in SharePoint, see  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins).
+Neither users who are launching an add-in, nor resource owners who are granting an add-in permission to access a resource, need to provide the add-in their credentials or password. Instead, SharePoint enables users and resource owners to grant only the specific permissions that the add-in requests. What makes this possible is the use by SharePoint of the transaction protocol  [OAuth 2.0](http://tools.ietf.org/html/draft-ietf-oauth-v2-22). For more information about OAuth in SharePoint, see  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md).
  
 
  
@@ -109,7 +115,7 @@ Neither users who are launching an add-in, nor resource owners who are granting
 ### Cross-domain access
 <a name="SelectiveAuthorization"> </a>
 
-A SharePoint Add-in that includes a remote web application that uses JavaScript for its data access logic can use a JavaScript cross domain library to get authorized access to SharePoint data within the tenancy where the add-in is installed. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+A SharePoint Add-in that includes a remote web application that uses JavaScript for its data access logic can use a JavaScript cross domain library to get authorized access to SharePoint data within the tenancy where the add-in is installed. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
  
 
  
@@ -117,7 +123,7 @@ A SharePoint Add-in that includes a remote web application that uses JavaScript
 ## Add-in lifecycle
 <a name="SPAppModelArch_Lifecycle"> </a>
 
-The lifecycle for a SharePoint Add-in includes publishing, installing, upgrading, and uninstalling. For more information about these subjects, see  [Publish SharePoint Add-ins](publish-sharepoint-add-ins),  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options) and [SharePoint Add-ins update process](sharepoint-add-ins-update-process). Note also that there is a mechanism by which tenant administrators can batch install a SharePoint Add-in to multiple websites. For more information, see  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins).
+The lifecycle for a SharePoint Add-in includes publishing, installing, upgrading, and uninstalling. For more information about these subjects, see  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md),  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md) and [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md). Note also that there is a mechanism by which tenant administrators can batch install a SharePoint Add-in to multiple websites. For more information, see  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md).
  
 
  
@@ -181,7 +187,7 @@ Metadata for a SharePoint Add-in, such as user preferences, location information
 ### Secure data access options
 <a name="DataAccess"> </a>
 
-Your options for secure data access, of course, depend on your choice of storage. Data access and search are discussed in detail in several other articles. For more information, see  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins).
+Your options for secure data access, of course, depend on your choice of storage. Data access and search are discussed in detail in several other articles. For more information, see  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md).
  
 
  
@@ -352,10 +358,10 @@ The following is an example of raw  **AppPrerequisites** markup that registers t
 <a name="RegisterDependency"> </a>
 
 
--  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in)
+-  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md)
     
  
--  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)
+-  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)
     
  
 
@@ -363,34 +369,34 @@ The following is an example of raw  **AppPrerequisites** markup that registers t
 <a name="SPAppModelArch_AdditionalResources"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
 -  [SharePoint Add-ins compared with SharePoint solutions](http://msdn.microsoft.com/library/0e9efadb-aaf2-4c0d-afd5-d6cf25c4e7a8%28Office.15%29.aspx)
     
  
--  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013)
+-  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md)
     
  
--  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins)
+-  [Context Token OAuth flow for SharePoint Add-ins](context-token-oauth-flow-for-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
 -  [IFrame](http://www.w3schools.com/tags/tag_iframe.asp)
     
  
--  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in)
+-  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md)
     
  
--  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options)
+-  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md)
     
  
--  [SharePoint Add-ins update process](sharepoint-add-ins-update-process).
+-  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md).
     
  
--  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins)
+-  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md b/docs/sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md
index b14db5d8be..a62b520426 100644
--- a/docs/sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md
+++ b/docs/sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md
@@ -1,3 +1,9 @@
+---
+title: Incident manager A cloud business add-in tutorial
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Incident manager: A cloud business add-in tutorial
 By using the  **Cloud Business Add-in** template in Visual Studio, you can create a SharePoint hosted in which mobile users can view, add, and update data from remote locations by using modern, touch-oriented devices such as phones and tablets. In this tutorial, you'll create an add-in for a fictional Contoso Fire Department to handle on-scene incident management. The walkthrough covers the core concepts of building a Cloud Business Add-in as well as more advanced concepts such as integrating SharePoint lists and document libraries.
@@ -5,7 +11,7 @@ By using the  **Cloud Business Add-in** template in Visual Studio, you can creat
 You can download the Incident Management sample application and associated files from the MSDN Samples Gallery:  [Incident Manager: A Cloud Business Add-in Tutorial](http://code.msdn.microsoft.com/Incident-Manager-A-Cloud-c32d9b04).
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -50,7 +56,7 @@ You will build the mobile add-in that will be used to enter basic information ab
 
  
 
-  ![Cloud Business App template](../../images/CBA_IM1.PNG)
+  ![Cloud Business App template](../images/CBA_IM1.PNG)
  
 
  
@@ -146,7 +152,7 @@ You will build the mobile add-in that will be used to enter basic information ab
 
  
 
-  ![The Incident entity](../../images/CBA_IM_2.PNG)
+  ![The Incident entity](../images/CBA_IM_2.PNG)
  
 
     
@@ -205,7 +211,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The Patient entity](../../images/CBA_IM_2a.PNG)
+  ![The Patient entity](../images/CBA_IM_2a.PNG)
  
 
     
@@ -242,7 +248,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The relationship between Incident and Patient](../../images/CBA_IM_3.PNG)
+  ![The relationship between Incident and Patient](../images/CBA_IM_3.PNG)
  
 
     This creates a zero or one to many relationship between incidents and patients. An incident record doesn't have to have a patient, but every patient has to have a related incident record.
@@ -284,7 +290,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The Incidents screen set](../../images/CBA_IM_4.PNG)
+  ![The Incidents screen set](../images/CBA_IM_4.PNG)
  
 
     Browse, View Details, and Add/Edit screens are added to the HTMLClient project. The Browse screen is automatically set as the home screen for the application, and the necessary commands for launching the View and Add/Edit screens are automatically provided.
@@ -332,7 +338,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![Browse screen layout](../../images/CBA_IM4a.PNG)
+  ![Browse screen layout](../images/CBA_IM4a.PNG)
  
 
     At run time the screen will display a tile for each incident, and each tile will display the incident number, date, and address.
@@ -365,7 +371,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The Add Patients link](../../images/CBA_IM_5.PNG)
+  ![The Add Patients link](../images/CBA_IM_5.PNG)
  
 
  
@@ -380,7 +386,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![Add/Edit screen layout](../../images/CBA_IM_5a.PNG)
+  ![Add/Edit screen layout](../images/CBA_IM_5a.PNG)
  
 
     
@@ -424,7 +430,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![Add/Edit screen layout](../../images/CBA_IM_6.PNG)
+  ![Add/Edit screen layout](../images/CBA_IM_6.PNG)
  
 
     
@@ -450,7 +456,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The Add Incident Popup](../../images/CBA_IM_7.PNG)
+  ![The Add Incident Popup](../images/CBA_IM_7.PNG)
  
 
  
@@ -484,7 +490,7 @@ In the next step, you'll add a Patient entity. Many of the fire department's inc
 
  
 
-  ![The Add Patient Popup](../../images/CBA_IM_8.PNG)
+  ![The Add Patient Popup](../images/CBA_IM_8.PNG)
  
 
  
@@ -587,7 +593,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![Navigate to the SharePoint developer site](../../images/CBA_IM_8a.PNG)
+  ![Navigate to the SharePoint developer site](../images/CBA_IM_8a.PNG)
  
 
  
@@ -602,7 +608,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![Site Settings link](../../images/CBA_IM_8b.PNG)
+  ![Site Settings link](../images/CBA_IM_8b.PNG)
  
 
  
@@ -614,7 +620,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![List templates list](../../images/CBA_IM_8c.PNG)
+  ![List templates list](../images/CBA_IM_8c.PNG)
  
 
  
@@ -638,7 +644,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![The Contoso templates](../../images/CBA_IM_8d.PNG)
+  ![The Contoso templates](../images/CBA_IM_8d.PNG)
  
 
  
@@ -680,7 +686,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![SharePoint data source](../../images/CBA_IM_9.PNG)
+  ![SharePoint data source](../images/CBA_IM_9.PNG)
  
 
  
@@ -695,7 +701,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![SharePoint lists](../../images/CBA_IM_9a.PNG)
+  ![SharePoint lists](../images/CBA_IM_9a.PNG)
  
 
     The entities are added to a new  **Developer Data** node under the **Data Sources** node in **Solution Explorer**, and the  **ContosoApparatus** entity opens in the entity designer.
@@ -735,7 +741,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![The AvailableApparatus query](../../images/CBA_IM_10.PNG)
+  ![The AvailableApparatus query](../images/CBA_IM_10.PNG)
  
 
     
@@ -769,7 +775,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![The Relationship dialog](../../images/CBA_IM_10a.PNG)
+  ![The Relationship dialog](../images/CBA_IM_10a.PNG)
  
 
     
@@ -806,7 +812,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![Add a query](../../images/CBA_IM_11.PNG)
+  ![Add a query](../images/CBA_IM_11.PNG)
  
 
     The  **AvailableApparatus** collection is added to the left pane of the screen designer.
@@ -839,7 +845,7 @@ The first step is to add a couple of pre-populated list templates to your develo
 
  
 
-  ![The Resources tab layout](../../images/CBA_IM_11a.PNG)
+  ![The Resources tab layout](../images/CBA_IM_11a.PNG)
  
 
  
@@ -875,7 +881,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![Navigate to the SharePoint developer site](../../images/CBA_IM_8a.PNG)
+  ![Navigate to the SharePoint developer site](../images/CBA_IM_8a.PNG)
  
 
  
@@ -908,7 +914,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![Document library with IncidentNumber column](../../images/CBA_IM_12.PNG)
+  ![Document library with IncidentNumber column](../images/CBA_IM_12.PNG)
  
 
     In order to associate the document library with your add-in, the document library must contain a custom column that maps to a unique field in your entity. In this case the  **IncidentNumber** column maps to the **IncidentNumber** field in the **Incidents** entity.
@@ -933,7 +939,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![Select the document library](../../images/CBA_IM_13.PNG)
+  ![Select the document library](../images/CBA_IM_13.PNG)
  
 
     An  **IncidentDocuments.lsml** node is added to Solution Explorer.
@@ -961,7 +967,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![The relationship between entities](../../images/CBA_IM_11b.PNG)
+  ![The relationship between entities](../images/CBA_IM_11b.PNG)
  
 
  
@@ -979,7 +985,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![The associated fields](../../images/CBA_IM_11c.PNG)
+  ![The associated fields](../images/CBA_IM_11c.PNG)
  
 
     
@@ -1017,7 +1023,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![Button to create or upload documents](../../images/CBA_IM_14.PNG)
+  ![Button to create or upload documents](../images/CBA_IM_14.PNG)
  
 
  
@@ -1041,7 +1047,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![The SharePoint Create a new file dialog](../../images/CBA_IM_15.PNG)
+  ![The SharePoint Create a new file dialog](../images/CBA_IM_15.PNG)
  
 
  
@@ -1063,7 +1069,7 @@ On the scene of an incident the Incident Commander has to document many things,
 
  
 
-  ![The file name](../../images/CBA_IM_16.PNG)
+  ![The file name](../images/CBA_IM_16.PNG)
  
 
     This will be used as the file name for the document.
@@ -1103,7 +1109,7 @@ The Contoso Fire Department is pleased with the additions to the Incident Manage
 
  
 
-  ![The logo and splash screen files](../../images/CBA_IM_17.PNG)
+  ![The logo and splash screen files](../images/CBA_IM_17.PNG)
  
 
  
@@ -1251,7 +1257,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![The IncidentManager node](../../images/CBA_IM_18.PNG)
+  ![The IncidentManager node](../images/CBA_IM_18.PNG)
  
 
     The  **LightSwitch Publish Application Wizard** appears.
@@ -1263,7 +1269,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![The Publish wizard](../../images/CBA_IM_19.PNG)
+  ![The Publish wizard](../images/CBA_IM_19.PNG)
  
 
     When your add-in is published,  **File Explorer** appears and displays the **Publish** folder for your project.
@@ -1278,7 +1284,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![The Apps in Test list](../../images/CBA_IM_20.PNG)
+  ![The Apps in Test list](../images/CBA_IM_20.PNG)
  
 
  
@@ -1293,7 +1299,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![The Deploy App dialog](../../images/CBA_IM_20a.PNG)
+  ![The Deploy App dialog](../images/CBA_IM_20a.PNG)
  
 
     The  **Upload Add-in** dialog box opens.
@@ -1318,7 +1324,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![App is installing](../../images/CBA_IM_21.PNG)
+  ![App is installing](../images/CBA_IM_21.PNG)
  
 
  
@@ -1333,7 +1339,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![App is installing](../../images/CBA_IM_22.PNG)
+  ![App is installing](../images/CBA_IM_22.PNG)
  
 
  
@@ -1348,7 +1354,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![The app is ready to run](../../images/CBA_IM_23.PNG)
+  ![The app is ready to run](../images/CBA_IM_23.PNG)
  
 
     The add-in opens in the browser and looks exactly the same as when you ran the add-in in Debug mode. Notice that the data you entered during development is gone. When deploying the add-in, the database is deployed but not the data.
@@ -1363,7 +1369,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![Layout in desktop browser](../../images/CBA_IM_24.PNG)
+  ![Layout in desktop browser](../images/CBA_IM_24.PNG)
  
 
     You can also verify your add-in on a mobile device. Sign in to your SharePoint site from the web browser on your device, and then start the add-in.
@@ -1375,7 +1381,7 @@ So far you've only run the add-in in Debug mode, which uses SharePoint to provid
 
  
 
-  ![Layout on mobile device](../../images/CBA_IM_25.PNG)
+  ![Layout on mobile device](../images/CBA_IM_25.PNG)
  
 
  
@@ -1388,13 +1394,13 @@ Congratulations! You have now finished the tutorial, and you know the basics of
 <a name="bk_addresources"> </a>
 
 
--  [Get started developing cloud business add-ins](get-started-developing-cloud-business-add-ins)
+-  [Get started developing cloud business add-ins](get-started-developing-cloud-business-add-ins.md)
     
  
--  [Develop cloud business add-ins](develop-cloud-business-add-ins)
+-  [Develop cloud business add-ins](develop-cloud-business-add-ins.md)
     
  
--  [Publish cloud business add-ins](publish-cloud-business-add-ins)
+-  [Publish cloud business add-ins](publish-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in.md b/docs/sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in.md
index dece9aaf6c..52d219a670 100644
--- a/docs/sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in.md
@@ -1,18 +1,24 @@
+---
+title: Include a custom button in the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Include a custom button in the provider-hosted add-in
 Learn how to include a custom ribbon button in a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the third in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the third in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
 
@@ -69,7 +75,7 @@ The custom button is going to be on the ribbon of a specific list that records t
  
 10. Click  **new item** and on the create item form, enter a name, but do *not*  check **Added to Corporate DB**. Then click  **Save**. The list should look similar to the following:
     
-  ![The Local Employees list with a single item. Name is Brayden Sawtell. The value of the "Added to Corporate DB" column is No.](../../images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG)
+  ![The Local Employees list with a single item. Name is Brayden Sawtell. The value of the "Added to Corporate DB" column is No.](../images/a3371859-e42f-49ea-8f17-48d8a248b075.PNG)
  
 
  
@@ -267,7 +273,7 @@ As you have seen, SharePoint prompts you to grant the add-in permissions to the
  
 4. Leave the  **Properties** field empty and save the file. The **Permission** tab should look similar to the following:
     
-  ![The Permissions tab of the add-in manifest designer show the Scope to List and the Permission to be Read.](../../images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG)
+  ![The Permissions tab of the add-in manifest designer show the Scope to List and the Permission to be Read.](../images/8dd2a25f-103a-42af-aa88-c8ec796315db.PNG)
  
 
  
@@ -283,7 +289,7 @@ As you have seen, SharePoint prompts you to grant the add-in permissions to the
 
 1. Use the F5 key to deploy and run your add-in. Visual Studio hosts the remote web application in IIS Express and hosts the SQL database in a SQL Express. It also makes a temporary installation of the add-in on your test SharePoint site and immediately runs the add-in. You are prompted to grant permissions to the add-in before it's start page opens. This time the prompt has a drop down where you select the list that the app needs to read as seen in the following screenshot. 
     
-  ![The SharePoint add-in permission prompt with the list named Local Employees selected in a drop down that is labelled "Let it read items in the list""](../../images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG)
+  ![The SharePoint add-in permission prompt with the list named Local Employees selected in a drop down that is labelled "Let it read items in the list""](../images/84e8b42c-4800-4947-acbd-21c6f096f4ea.PNG)
  
 
  
@@ -306,7 +312,7 @@ As you have seen, SharePoint prompts you to grant the add-in permissions to the
  
 7. Select an item on the list. The page and ribbon should look similar to the following:
     
-  ![The Local Employees list. One item is highlighted. Above it is the ribbon and a button named "Add To Corporate DB" is in the Actions section.](../../images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG)
+  ![The Local Employees list. One item is highlighted. Above it is the ribbon and a button named "Add To Corporate DB" is in the Actions section.](../images/797a5ceb-7291-4b62-8075-2bb6a1b8e8a1.PNG)
  
 
  
@@ -323,7 +329,7 @@ As you have seen, SharePoint prompts you to grant the add-in permissions to the
  
 11. Click  **Show Employees** and the list of employees will be populated with the employee that you added. It should look similar to the following:
     
-  ![The corporate employees list on the add-in start page showing the same employee that was selected in the earlier step.](../../images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG)
+  ![The corporate employees list on the add-in start page showing the same employee that was selected in the earlier step.](../images/4a300a4e-f479-4f63-b536-6315c5d9ba4d.PNG)
  
 
  
@@ -339,7 +345,7 @@ As you have seen, SharePoint prompts you to grant the add-in permissions to the
 ## 
 <a name="Nextsteps"> </a>
 
- In the next article, we'll take a brief break from coding for an overview of the SharePoint client-side object model: [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model).
+ In the next article, we'll take a brief break from coding for an overview of the SharePoint client-side object model: [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md).
  
 
  
diff --git a/docs/sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md b/docs/sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md
index 655f747d6b..2116f1e859 100644
--- a/docs/sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md
+++ b/docs/sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md
@@ -1,9 +1,15 @@
+---
+title: Include a Web Part in a webpage on the add-in web
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Include a Web Part in a webpage on the add-in web
 Learn how to include a Web Part on a page in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can include an out-of-the-box Web Part in a page in the add-in web of a SharePoint Add-in, but it is important that you do this in a way that won't cause problems if you ever need to update the add-in.
@@ -15,7 +21,7 @@ A code sample that illustrates the guidance of this topic is at:  [OfficeDev/Cor
 
 ## Prerequisites
 
-For the prerequisites, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins).
+For the prerequisites, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md).
  
 
  
@@ -27,7 +33,7 @@ For the prerequisites, see  [Get started creating SharePoint-hosted SharePoint A
 
  
 
-1. Create a SharePoint-hosted SharePoint Add-in project in Visual Studio. For details, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins).
+1. Create a SharePoint-hosted SharePoint Add-in project in Visual Studio. For details, see  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md).
     
  
 2. Open the aspx file to which you want to add a Web Part. This topic uses Default.aspx as an example. 
@@ -75,7 +81,7 @@ For the prerequisites, see  [Get started creating SharePoint-hosted SharePoint A
 </AllUsersWebPart>
 ```
 
-7. Add  **webPart** markup as a child of the **webParts** element. The following is an example that adds an **XsltListViewWebPart**. It assumes that a custom list called "Test List" is part of the same add-in project. For information about how to add a custom list to an add-in web, see  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-content-type). 
+7. Add  **webPart** markup as a child of the **webParts** element. The following is an example that adds an **XsltListViewWebPart**. It assumes that a custom list called "Test List" is part of the same add-in project. For information about how to add a custom list to an add-in web, see  [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md). 
     
      **Note**   Note that the Web Part does not have an ID property. It is a best practice to include an explicit ID for the Web Part only in the two cases where it is really required: The Web Part is being added to a SharePoint wiki page. The Web Part is one of two or more Web Parts that will be connected.
 
diff --git a/docs/sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in.md b/docs/sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in.md
index a479ce2579..49a60b10da 100644
--- a/docs/sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in.md
@@ -1,27 +1,33 @@
+---
+title: Include an add-in part in the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Include an add-in part in the provider-hosted add-in
 Learn how to surface a remote web form in a SharePoint page in a provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the sixth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the sixth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
--  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+-  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
     
  
 
@@ -92,7 +98,7 @@ In this article, you add a special kind of Web Part, called an add-in part to th
  
   4. On the Web Part insertion control that opens, select the  **Place Order** add-in part. The control will look similar to the following.
     
-  ![SharePoint's Web Part insertion control. The part called "Place Order" is highlighted. Its name and description appears in a box at the right.](../../images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG)
+  ![SharePoint's Web Part insertion control. The part called "Place Order" is highlighted. Its name and description appears in a box at the right.](../images/aae61f89-2e9e-4808-8b0c-2439dad7c701.PNG)
  
 
  
@@ -109,7 +115,7 @@ In this article, you add a special kind of Web Part, called an add-in part to th
  
 3. The order form now appears on the page and it has the look-and-feel of the rest of the page. It should look like the following: 
     
-  ![The Place Order add-in part on the page with text boxes for Product, Supplier, and Quantity. There is also a "Place Order" button.](../../images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG)
+  ![The Place Order add-in part on the page with text boxes for Product, Supplier, and Quantity. There is also a "Place Order" button.](../images/beae2e3c-c1f4-4334-8ab8-0c42252cb2a2.PNG)
  
 
  
@@ -131,7 +137,7 @@ In this article, you add a special kind of Web Part, called an add-in part to th
 ## 
 <a name="Nextsteps"> </a>
 
- The add-in depends on two lists that you created manually. You don't want your users to have to do that. In the next article you begin the process of automatically creating these lists. The first major step is to create custom handlers for the event of installing an add-in: [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in)
+ The add-in depends on two lists that you created manually. You don't want your users to have to do that. In the next article you begin the process of automatically creating these lists. The first major step is to create custom handlers for the event of installing an add-in: [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/localize-sharepoint-add-ins.md b/docs/sp-add-ins/localize-sharepoint-add-ins.md
index 8af00c13eb..370a87c686 100644
--- a/docs/sp-add-ins/localize-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/localize-sharepoint-add-ins.md
@@ -1,12 +1,19 @@
+---
+title: Localize SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Localize SharePoint Add-ins
 Localize a SharePoint Add-in by using resource files, JavaScript resource files, and other techniques.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Note**  This topic assumes that you are familiar with basic creation of SharePoint Add-ins; and with SharePoint Features, the distinction between add-in webs and host webs,  [what kind of SharePoint components can be in an add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#TypesOfSPComponentsInApps), and the basics of localization with .resx files.
+ **Note**  This topic assumes that you are familiar with basic creation of SharePoint Add-ins; and with SharePoint Features, the distinction between add-in webs and host webs,  [what kind of SharePoint components can be in an add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps), and the basics of localization with .resx files.
  
 
 
@@ -39,7 +46,7 @@ Also, be aware of the following:
 ## Localize the add-in web components
 <a name="LocalizingAppWeb"> </a>
 
-An add-in web can contain specific kinds of SP components. For more information about the kinds of SharePoint components that can be in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#TypesOfSPComponentsInApps). To localize components that are deployed to an add-in web, you add .resx files in modules in the same Feature that contains the add-in web component. You reference the resources in the markup of the component. How you do this is explained later in this article. However, custom site pages in a SharePoint Add-in use JavaScript string variable files instead of .resx files, as described later in this section.
+An add-in web can contain specific kinds of SP components. For more information about the kinds of SharePoint components that can be in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps). To localize components that are deployed to an add-in web, you add .resx files in modules in the same Feature that contains the add-in web component. You reference the resources in the markup of the component. How you do this is explained later in this article. However, custom site pages in a SharePoint Add-in use JavaScript string variable files instead of .resx files, as described later in this section.
  
 
  
@@ -125,7 +132,7 @@ An add-in web can contain specific kinds of SP components. For more information
 
  
 
-  ![A localized custom list](../../images/LocSPApp_AppwebList.png)
+  ![A localized custom list](../images/LocSPApp_AppwebList.png)
  
 
  
@@ -281,7 +288,7 @@ var step07 = "Review the localized <a href=\"../Lists/Orders\">Orders</a>" +
 
  
 
-  ![A SharePoint page using localized strings](../../images/LocSPApp_AppwebPage.png)
+  ![A SharePoint page using localized strings](../images/LocSPApp_AppwebPage.png)
  
 
  
@@ -382,7 +389,7 @@ protected override void InitializeCulture()
 ## Localize remote JavaScript and the SharePoint chrome control
 <a name="JSandChrome"> </a>
 
-If there are localizable string values in your web application's JavaScript, you can localize them using JavaScript resource files. An especially important example of localizable JavaScript is the  [SharePoint chrome control](use-the-client-chrome-control-in-sharepoint-add-ins), which can be used to give remote pages the appearance of SharePoint pages. We'll use the localization of the chrome control as an example in this section.
+If there are localizable string values in your web application's JavaScript, you can localize them using JavaScript resource files. An especially important example of localizable JavaScript is the  [SharePoint chrome control](use-the-client-chrome-control-in-sharepoint-add-ins.md), which can be used to give remote pages the appearance of SharePoint pages. We'll use the localization of the chrome control as an example in this section.
  
 
  
@@ -525,7 +532,7 @@ Test your add-in by deploying it to a SharePoint website that is provisioned in
  
 
  
-![Create site collection page](../../images/LocSPApp_TestCreatesite.png)
+![Create site collection page](../images/LocSPApp_TestCreatesite.png)
  
 
 ### To test your add-in an on-premises website
@@ -556,7 +563,7 @@ Test your add-in by deploying it to a SharePoint website that is provisioned in
 ## Additional resources
 <a name="SP15Localizeapp_addlresources"> </a>
 
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
 -  [Localization for Office Add-ins](http://msdn.microsoft.com/library/5a1a1cd7-b716-4597-b51f-fa70357d0833%28Office.15%29.aspx)
 -  [ASP.NET Globalization and Localization](http://msdn.microsoft.com/library/8ef3838e-9d05-4236-9dd0-ceecff9df80d.aspx)
 -  [SharePoint-Add-in-Localization](https://github.com/OfficeDev/SharePoint-Add-in-Localization)
diff --git a/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md b/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md
index b4f22f951e..7fa3155157 100644
--- a/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md
+++ b/docs/sp-add-ins/make-batch-requests-with-the-rest-apis.md
@@ -1,9 +1,15 @@
+---
+title: Make batch requests with the REST APIs
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Make batch requests with the REST APIs
 Learn how to use the  `$batch` query option with the REST/OData APIs.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 This article describes how you can batch queries and operations against the REST/OData API of Microsoft SharePoint Online (and on-premise SharePoint 2016 and later) and the  [Files and folders subset](http://msdn.microsoft.com/en-us/office/office365/api/files-rest-operations) of the Office 365 REST APIs. With this technique you can improve the performance of your add-in by combining many operations into a single request to the server and a single response back.
diff --git a/docs/sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md b/docs/sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
index 122d35b9c3..37e77c6cf7 100644
--- a/docs/sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
+++ b/docs/sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
@@ -1,9 +1,15 @@
+---
+title: Navigate the SharePoint data structure represented in the REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Navigate the SharePoint data structure represented in the REST service
 Learn how to start from a REST endpoint for a given SharePoint item, and navigate to and access related items, such as parent sites or the library structure where that item resides. 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -145,28 +151,28 @@ Navigation that is supported by the REST service:
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
--  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris)
+-  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
 -  [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)
     
  
--  [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service)
+-  [Synchronize SharePoint items using the REST service](synchronize-sharepoint-items-using-the-rest-service.md)
     
  
 -  [Use ETag values through the REST service to get document list item versioning](http://msdn.microsoft.com/library/5f7e0579-46b7-44ab-b3b4-cdbc622dcd98%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/new-name-for-apps-for-sharepoint.md b/docs/sp-add-ins/new-name-for-apps-for-sharepoint.md
index b69a4ab30a..45ec326920 100644
--- a/docs/sp-add-ins/new-name-for-apps-for-sharepoint.md
+++ b/docs/sp-add-ins/new-name-for-apps-for-sharepoint.md
@@ -1,7 +1,13 @@
+---
+title: New name for apps for SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # New name for apps for SharePoint
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 We are currently updating our products, documentation, samples, and other resources to reflect the platform name change from "apps for Office and SharePoint" to "Office and SharePoint Add-ins". We made this change to better distinguish the extension platform from Office Add-ins (applications). For your reference, the following table lists the names that are changing and the new names.
diff --git a/docs/sp-add-ins/office-web-widgetsexperimental-license-terms.md b/docs/sp-add-ins/office-web-widgetsexperimental-license-terms.md
index 5d447d0253..4b032f7884 100644
--- a/docs/sp-add-ins/office-web-widgetsexperimental-license-terms.md
+++ b/docs/sp-add-ins/office-web-widgetsexperimental-license-terms.md
@@ -1,8 +1,15 @@
+---
+title: Office Web Widgets - Experimental License Terms
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Office Web Widgets - Experimental License Terms
 Learn about the license terms to use the Office Web Widgets - Experimental.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
  **To download the file you must agree to the following license:**
@@ -142,13 +149,13 @@ It also applies even if Microsoft knew or should have known about the possibilit
 <a name="bk_addresources"> </a>
 
 
--  [Office Web Widgets - Experimental overview](office-web-widgets--experimental-overview)
+-  [Office Web Widgets - Experimental overview](office-web-widgetsexperimental-overview.md)
     
  
--  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins)
+-  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md)
     
  
--  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins)
+-  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/office-web-widgetsexperimental-overview.md b/docs/sp-add-ins/office-web-widgetsexperimental-overview.md
index dfe4f93800..e0b2d54f74 100644
--- a/docs/sp-add-ins/office-web-widgetsexperimental-overview.md
+++ b/docs/sp-add-ins/office-web-widgetsexperimental-overview.md
@@ -1,13 +1,19 @@
+---
+title: Office Web Widgets - Experimental overview
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Office Web Widgets - Experimental overview
 Learn about the Office Web Widgets - Experimental that you can use in Office Add-ins, SharePoint Add-ins, and websites.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Caution**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms).
+ **Caution**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md).
  
 
 
@@ -36,13 +42,13 @@ Client controls, such as the Office Web Widgets - Experimental, can greatly redu
  
 
  
-![Office Web Widgets - Experimental demo](../../images/OfficeWebWidgetsOverview_demo.png)
+![Office Web Widgets - Experimental demo](../images/OfficeWebWidgetsOverview_demo.png)
  
 You can use the widgets by installing the  **Office Web Widgets - Experimental** NuGet package from Visual Studio For more information, see [Managing NuGet Packages Using the Dialog](http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog). You can also browse the  [NuGet gallery page](http://www.nuget.org/packages/Microsoft.Office.WebWidgets.Experimental/).
  
 Your feedback and comments helped us decide what widgets to provide. As you can see in Figure 1, the (1) People Picker and (2) Desktop List View widgets are ready for you to try and experiment. Please keep the feedback coming at the  [Office Developer Platform UserVoice site](http://officespdev.uservoice.com/)
  
-You can also see the widgets in action in the  [Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-2013-Office-Web-6d44aa9e) code sample.
+You can also see the widgets in action in the  [Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-Office-Web-6d44aa9e) code sample.
  
 
 ## People Picker widget
@@ -57,7 +63,7 @@ You can use the experimental People Picker widget in add-ins to help your users
  
 
  
-![People Picker experimental control on a page](../../images/PeoplePicker_basic.png)
+![People Picker experimental control on a page](../images/PeoplePicker_basic.png)
  
 You can declare the widget in the HTML markup or programmatically using JavaScript. In either case, you use a  **div** element as a placeholder for the widget. You can also set properties and event handlers for the People Picker widget. The following table shows the available properties and events in the People Picker widget.
  
@@ -83,7 +89,7 @@ The CSS classes for the People Picker widget are defined in the  **Office.Contro
  
 
  
-For more information, see  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins) and [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85) code sample.
+For more information, see  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md) and [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85.md) code sample.
  
 
  
@@ -100,7 +106,7 @@ Your users can benefit from the List View widget and display the data in a list
  
 
  
-![Desktop List View experimental control on a page](../../images/DesktopListView_basic.png)
+![Desktop List View experimental control on a page](../images/DesktopListView_basic.png)
  
 You can specify an existing view on the list, the widget renders the fields in the order that they appear in the view.
  
@@ -129,11 +135,11 @@ You also can set properties or event handlers for the Desktop List View widget.
 |**onItemAdded**|Function|Event that fires when a new item is added to the list.|
 |**onItemRemoved**|Function|Event that fires when an item is removed from the list.|
 |**selectedItems**|Array|List of Selected items in JSON format.|
-The widget requires the SharePoint website style sheet. You can reference the SharePoint style sheet directly or use the chrome widget. For more information about the style sheet, see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins) and [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins). 
+The widget requires the SharePoint website style sheet. You can reference the SharePoint style sheet directly or use the chrome widget. For more information about the style sheet, see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md) and [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md). 
  
 
  
-To see the List View widget in action, see the  [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-c3edb076) code sample. Also see [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins).
+To see the List View widget in action, see the  [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-c3edb076) code sample. Also see [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md).
  
 
  
@@ -149,24 +155,24 @@ Widgets can help to speed up the development process and reduce the cost and tim
 <a name="bk_addresources"> </a>
 
 
--  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms)
+-  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md)
     
  
 -  [Office Web Widgets - Experimental NuGet gallery page](http://www.nuget.org/packages/Microsoft.Office.WebWidgets.Experimental/)
     
  
--  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins)
+-  [Use the experimental People Picker widget in SharePoint Add-ins](use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md)
     
  
--  [Code sample: Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-2013-Office-Web-6d44aa9e)
+-  [Code sample: Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-Office-Web-6d44aa9e)
     
  
--  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins)
+-  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md)
     
  
--  [Code sample: Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85)
+-  [Code sample: Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85)
     
  
--  [Code sample: Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-c3edb076)
+-  [Code sample: Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-c3edb076)
     
  
diff --git a/docs/sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md b/docs/sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md
index f20c69cb07..8d03465c3f 100644
--- a/docs/sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Package and publish high-trust SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Package and publish high-trust SharePoint Add-ins
 Learn how to package and publish a high-trust SharePoint Add-in for on-premises use.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -15,7 +21,7 @@ You need the following:
 
  
 
-- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins) for the setup instructions.
+- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md) for the setup instructions.
     
  
 - An IIS web server to host the remote web application. IIS Manager should be installed.
@@ -40,8 +46,8 @@ Table 1 lists some useful articles that can help you to understand the concepts
 
 |**Article Title**|**Description**|
 |:-----|:-----|
-| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio.|
-| [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins)|Learn how to create a basic high-trust SharePoint Add-in with the Office Developer Tools for Visual Studio by using a self-signed certificate and an associated issuer ID.|
+| [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)|Learn how to create a basic provider-hosted SharePoint Add-in with the Office Developer Tools for Visual Studio.|
+| [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md)|Learn how to create a basic high-trust SharePoint Add-in with the Office Developer Tools for Visual Studio by using a self-signed certificate and an associated issuer ID.|
 | [Web Deploy](http://www.iis.net/downloads/microsoft/web-deploy)|Web Deploy simplifies deployment of web applications and websites to IIS servers.|
 | [Digital Certificates](http://msdn.microsoft.com/library/e523b335-0156-4f47-b55c-b80495587c4f.aspx) and [Working with Certificates](http://msdn.microsoft.com/library/6ffb8682-8f07-4a45-afbb-8d2487e9dbc3.aspx)|Learn the basic ideas behind digital certificates.|
 
@@ -62,7 +68,7 @@ Before you can publish the add-in, it has to be registered with the SharePoint f
 
 1. Navigate to the http:// _SharePoint_website_/_layouts/15/appregnew.aspx page. Choose the  **Generate** buttons to generate values for the add-in ID and secret. (The secret is not actually used in high-trust SharePoint Add-ins, but the form requires one.) Provide the base URL of the domain where the remote web application of the add-in will run. Do not include the protocol (HTTPS) in the domain, but you have to include the port that the remote components will use for HTTPS requests if it is not 443 (for example,www.contoso.com:5555 orMyAppServer:4444).
     
-    If you need a redirect URI, enter a value for that also. See  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins) for an explanation of how the redirect URI can be used.
+    If you need a redirect URI, enter a value for that also. See  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md) for an explanation of how the redirect URI can be used.
     
     The form on the page should look similar to Figure 1. In this example, the remote web application server is listening for HTTPS requests on the default port 443, so it's not necessary to specify the port in the add-in domain.
     
@@ -71,7 +77,7 @@ Before you can publish the add-in, it has to be registered with the SharePoint f
 
  
 
-  ![Register app on appregnew.aspx](../../images/SP15_RegisterApp.png)
+  ![Register app on appregnew.aspx](../images/SP15_RegisterApp.png)
  
 
  
@@ -84,7 +90,7 @@ Before you can publish the add-in, it has to be registered with the SharePoint f
 ## Choose a strategy for obtaining, maintaining and deploying certificates for high-trust SharePoint Add-ins
 <a name="Certificate"> </a>
 
-When a developer is using  **F5** in Visual Studio to develop and debug a high-trust SharePoint Add-in, the developer can use a self-signed certificate, as described in [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins). However, when the add-in is  *published*  , using a self-signed certificate causes the browser to display a warning page before it will open the remote web application's start page. The user has to choose whether to proceed. Figure 2 shows examples of such warnings.
+When a developer is using  **F5** in Visual Studio to develop and debug a high-trust SharePoint Add-in, the developer can use a self-signed certificate, as described in [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md). However, when the add-in is  *published*  , using a self-signed certificate causes the browser to display a warning page before it will open the remote web application's start page. The user has to choose whether to proceed. Figure 2 shows examples of such warnings.
  
 
  
@@ -94,7 +100,7 @@ When a developer is using  **F5** in Visual Studio to develop and debug a high-t
  
 
  
-![IE and Chrome warnings for self-signed certificate](../../images/BrowserWarnings4SelfSignedCerts.png)
+![IE and Chrome warnings for self-signed certificate](../images/BrowserWarnings4SelfSignedCerts.png)
  
 This annoyance might be acceptable for a developer, but it would be unacceptable for customers. So before final publication to a production environment, the customer has to get a certificate that is signed by a trusted third party. The third party can be a commercial Certificate Authority (CA) or an on-premises CA. In regard to commercial CAs, note that the industry is phasing out "intranet-only" certificates for web servers. They can still be purchased, but all such certificates will expire in November, 2016, or sooner. It is not necessary to have this kind of certificate for a high-trust SharePoint Add-in, because certificates that can be used for internet-facing web servers can also be used for intranet web servers, but the latter generally cost more. 
  
@@ -108,7 +114,7 @@ If the certificate is originally obtained is a cer format, it will contain both
  
 
  
-In addition, the customer has to consider whether to use a single certificate for all high-trust SharePoint Add-ins or separate certificates for each. For more information about this decision, see  [Deciding between using one certificate or many for high-trust SharePoint Add-ins](creating-sharepoint-add-ins-that-use-high-trust-authorization#Deciding).
+In addition, the customer has to consider whether to use a single certificate for all high-trust SharePoint Add-ins or separate certificates for each. For more information about this decision, see  [Deciding between using one certificate or many for high-trust SharePoint Add-ins](creating-sharepoint-add-ins-that-use-high-trust-authorization.md#Deciding).
  
 
  
@@ -183,7 +189,7 @@ Skip the next procedure if you are using ISS Manager 8.
 
  
 
-  ![Exporting a test certificate](../../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
+  ![Exporting a test certificate](../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
  
 
  
@@ -287,7 +293,7 @@ The following procedure configures the certificate as a trusted token issuer in
 ### To configure the certificate
 
 
-1. If you have not done so already, create the high-trust configuration Windows PowerShell script or scripts that you need, as described in  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint-2013).
+1. If you have not done so already, create the high-trust configuration Windows PowerShell script or scripts that you need, as described in  [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint.md).
     
  
 2. Copy the scripts to the SharePoint server.
@@ -330,7 +336,7 @@ Edit the web.config file so that it contains new values for the following keys i
       - If the high-trust SharePoint Add-in has its own certificate that it is not sharing with other SharePoint Add-ins, the  `IssuerId` is the same as the `ClientId`.
     
  
-  - If the SharePoint Add-in is sharing the same certificate that other SharePoint Add-ins are using, the  `IssuerId` is an arbitrary GUID. The script for this scenario that you can find in [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint-2013) generates a text file with this GUID in it. The IT staff can pass the outputted file to the add-in developer for insertion as the `IssuerId` in the web.config file.
+  - If the SharePoint Add-in is sharing the same certificate that other SharePoint Add-ins are using, the  `IssuerId` is an arbitrary GUID. The script for this scenario that you can find in [High-trust configuration scripts for SharePoint](high-trust-configuration-scripts-for-sharepoint.md) generates a text file with this GUID in it. The IT staff can pass the outputted file to the add-in developer for insertion as the `IssuerId` in the web.config file.
     
  
 
@@ -587,16 +593,16 @@ private static X509Certificate2 GetCertificateFromStore()
 <a name="bk_addresources"> </a>
 
 
--  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins)
+-  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md)
     
  
--  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio)
+-  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio.md)
     
  
--  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013)
+-  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md b/docs/sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md
index 6efd5c2770..5229aeba6b 100644
--- a/docs/sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md
+++ b/docs/sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md
@@ -1,36 +1,42 @@
+---
+title: Programmatically deploy a custom button in the provider-hosted add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Programmatically deploy a custom button in the provider-hosted add-in
 Learn how to programmatically register a custom ribbon button with a custom list in the same provider-hosted SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the ninth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the ninth in a series of articles about the basics of developing provider-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel)
+-  [Give your provider-hosted add-in the SharePoint look-and-feel](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md)
     
  
--  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in)
+-  [Include a custom button in the provider-hosted add-in](include-a-custom-button-in-the-provider-hosted-add-in.md)
     
  
--  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model)
+-  [Get a quick overview of the SharePoint object model](get-a-quick-overview-of-the-sharepoint-object-model.md)
     
  
--  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in)
+-  [Add SharePoint write operations to the provider-hosted add-in](add-sharepoint-write-operations-to-the-provider-hosted-add-in.md)
     
  
--  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in)
+-  [Include an add-in part in the provider-hosted add-in](include-an-add-in-part-in-the-provider-hosted-add-in.md)
     
  
--  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in)
+-  [Handle add-in events in the provider-hosted add-in](handle-add-in-events-in-the-provider-hosted-add-in.md)
     
  
--  [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in)
+-  [Add first-run logic to the provider-hosted add-in](add-first-run-logic-to-the-provider-hosted-add-in.md)
     
  
 
@@ -53,7 +59,7 @@ In the previous article you removed the custom  **AddEmployeeToCorpDB** ribbon b
 
 1. In  **Solution Explorer**, press the  **Show All Files** button on the small toolbar at the top of **Solution Explorer**.
     
-  ![The Solution Explorer toolbar with a box drawn around the "Show All Files" button.](../../images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG)
+  ![The Solution Explorer toolbar with a box drawn around the "Show All Files" button.](../images/f6b035f5-1aa7-452a-8f59-9dd44b062d06.PNG)
  
 
  
@@ -281,7 +287,7 @@ Since the add-in is now adding adding and deleting web-scoped custom actions, we
  
 4. Navigate to the  **Site Contents** page. The **Local Employees** list is present because your first-run logic added it.
     
-     **Note**  If the list is not there or you have other indications that the first-run code is not executing, it may be that the  **Tenants** table is not being reverted to an empty state when you press F5. The most common cause of this is that the **ChainCorporateDB** project is no longer set as a startup project in Visual Studio. See the note near the top of this article for how to fix this. Also be sure that you've configured the database to be rebuilt as described in [Configure Visual Studio to rebuild the corporate database with each debugging session](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel#Rebuild).
+     **Note**  If the list is not there or you have other indications that the first-run code is not executing, it may be that the  **Tenants** table is not being reverted to an empty state when you press F5. The most common cause of this is that the **ChainCorporateDB** project is no longer set as a startup project in Visual Studio. See the note near the top of this article for how to fix this. Also be sure that you've configured the database to be rebuilt as described in [Configure Visual Studio to rebuild the corporate database with each debugging session](give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md#Rebuild).
 5. Open the list and add an item.
     
  
@@ -307,7 +313,7 @@ Since the add-in is now adding adding and deleting web-scoped custom actions, we
 ## 
 <a name="Nextsteps"> </a>
 
- Events on lists and list items can also have custom handlers in SharePoint. You learn how to create one and deploy it in your first-run logic in the next article: [Handle list item events in the provider-hosted add-in](handle-list-item-events-in-the-provider-hosted-add-in)
+ Events on lists and list items can also have custom handlers in SharePoint. You learn how to create one and deploy it in your first-run logic in the next article: [Handle list item events in the provider-hosted add-in](handle-list-item-events-in-the-provider-hosted-add-in.md)
  
 
  
diff --git a/docs/sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md b/docs/sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md
index 467e902cfe..e22cee3adf 100644
--- a/docs/sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md
+++ b/docs/sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md
@@ -1,15 +1,21 @@
+---
+title: Provide a template for a document library in a cloud business add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Provide a template for a document library in a cloud business add-in
 In addition to the Office templates that are available when you add a document to a SharePoint document library, you can provide your own templates. For example, you might have your own sales quote template that you want to use when new orders are added.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## 
 
-If you haven't already done so, associate a document library with your cloud business add-in. See  [Associate a document library with an entity](associate-a-document-library-with-an-entity).
+If you haven't already done so, associate a document library with your cloud business add-in. See  [Associate a document library with an entity](associate-a-document-library-with-an-entity.md).
  
 
  
@@ -26,7 +32,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Site Settings link](../../images/CBA_IM_8b.PNG)
+  ![Site Settings link](../images/CBA_IM_8b.PNG)
  
 
  
@@ -38,7 +44,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Site content types link](../../images/CBA_IM_26.PNG)
+  ![Site content types link](../images/CBA_IM_26.PNG)
  
 
  
@@ -50,7 +56,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Create link](../../images/CBA_IM_27.PNG)
+  ![Create link](../images/CBA_IM_27.PNG)
  
 
  
@@ -62,7 +68,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Parent content type selections](../../images/CBA_IM_28.PNG)
+  ![Parent content type selections](../images/CBA_IM_28.PNG)
  
 
  
@@ -74,7 +80,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Group setting](../../images/CBA_IM_28a.PNG)
+  ![Group setting](../images/CBA_IM_28a.PNG)
  
 
  
@@ -89,7 +95,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Specify the document template](../../images/CBA_IM_29.PNG)
+  ![Specify the document template](../images/CBA_IM_29.PNG)
  
 
  
@@ -107,7 +113,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![Adding the template](../../images/CBA_IM_29a.PNG)
+  ![Adding the template](../images/CBA_IM_29a.PNG)
  
 
  
@@ -119,7 +125,7 @@ If you haven't already done so, associate a document library with your cloud bus
 
  
 
-  ![The Create a new file dialog with the new template](../../images/CBA_IM_30.PNG)
+  ![The Create a new file dialog with the new template](../images/CBA_IM_30.PNG)
  
 
  
@@ -130,10 +136,10 @@ If you haven't already done so, associate a document library with your cloud bus
 <a name="bk_addresources"> </a>
 
 
--  [Develop cloud business add-ins](develop-cloud-business-add-ins)
+-  [Develop cloud business add-ins](develop-cloud-business-add-ins.md)
     
  
--  [Associate a document library with an entity](associate-a-document-library-with-an-entity)
+-  [Associate a document library with an entity](associate-a-document-library-with-an-entity.md)
     
  
 
diff --git a/docs/sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint.md b/docs/sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint.md
index 0977e6cfe6..d8d7dff7af 100644
--- a/docs/sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint.md
+++ b/docs/sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint.md
@@ -1,3 +1,9 @@
+---
+title: Publish a cloud business add-in to SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Publish a cloud business add-in to SharePoint
 You can publish your cloud business add-in as a provider-hosted SharePoint add-in. A provider-hosted add-in gives you the flexibility of deploying your web app and database to an on-premise SharePoint site, to Microsoft Azure, or to a third-party hosting site. After you publish your add-in, others can run it from SharePoint on their computers and mobile devices.
@@ -5,7 +11,7 @@ You can publish your cloud business add-in as a provider-hosted SharePoint add-i
 You can publish your add-in directly to a site using WebDeploy, or you can create a package for your add-in that can be deployed to multiple servers.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -19,7 +25,7 @@ You can publish your add-in directly to a site using WebDeploy, or you can creat
 
  
 
-  ![The IncidentManager node](../../images/CBA_IM_18.PNG)
+  ![The IncidentManager node](../images/CBA_IM_18.PNG)
  
 
  
@@ -107,7 +113,7 @@ You can publish your add-in directly to a site using WebDeploy, or you can creat
 
  
 
-  ![The IncidentManager node](../../images/CBA_IM_18.PNG)
+  ![The IncidentManager node](../images/CBA_IM_18.PNG)
  
 
     
@@ -161,10 +167,10 @@ You can publish your add-in directly to a site using WebDeploy, or you can creat
 <a name="bk_addresources"> </a>
 
 
--  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins-2013)
+-  [Register SharePoint Add-ins 2013](register-sharepoint-add-ins.md)
     
  
--  [Publish cloud business add-ins](publish-cloud-business-add-ins)
+-  [Publish cloud business add-ins](publish-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/publish-cloud-business-add-ins.md b/docs/sp-add-ins/publish-cloud-business-add-ins.md
index dec6216ff2..443acc042f 100644
--- a/docs/sp-add-ins/publish-cloud-business-add-ins.md
+++ b/docs/sp-add-ins/publish-cloud-business-add-ins.md
@@ -1,15 +1,21 @@
+---
+title: Publish cloud business add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Publish cloud business add-ins
 Cloud business add-ins can be published to SharePoint for Office 365 or to your own SharePoint site. After you publish your add-in, others can start it from SharePoint on their computers and mobile devices.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Publish a provider hosted add-in
 
-You can publish a cloud business add-in to SharePoint using the provider hosting option. See  [Publish a cloud business add-in to SharePoint](publish-a-cloud-business-add-in-to-sharepoint).
+You can publish a cloud business add-in to SharePoint using the provider hosting option. See  [Publish a cloud business add-in to SharePoint](publish-a-cloud-business-add-in-to-sharepoint.md).
  
 
  
@@ -25,7 +31,7 @@ Once published to a SharePoint site, you can make your add-in available in a loc
 <a name="bk_addresources"> </a>
 
 
--  [Create cloud business add-ins](create-cloud-business-add-ins)
+-  [Create cloud business add-ins](create-cloud-business-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio.md b/docs/sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio.md
index 1181b1764c..b3fe88d71b 100644
--- a/docs/sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio.md
+++ b/docs/sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio.md
@@ -1,9 +1,15 @@
+---
+title: Publish SharePoint Add-ins by using Visual Studio
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Publish SharePoint Add-ins by using Visual Studio
 Learn how to publish your SharePoint Add-in by using Microsoft Visual Studio 2013 or Visual Studio 2012. If the add-in has an associated web application, you deploy it first. Then, as for all SharePoint Add-ins, you package the SharePoint Add-in and then publish it. You can also optionally choose to submit your add-in for inclusion on the Office Store.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -154,7 +160,7 @@ When you're ready to package your SharePoint Add-in, open the  **Publish Office
  
 4. In the boxes under  **What is the identity of your add-in?**, specify the client ID and client secret for your add-in, and then choose the  **Next** button.
     
-    See  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins).
+    See  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md).
     
  
 5. For all types of SharePoint Add-ins, select the  **Open output folder after successful packaging** check box, if it isn't already selected, and then choose the **Finish** button.
@@ -188,7 +194,7 @@ For step-by-step guidance, see  [How to: Install a Deployment Package Using the
 ### Step 3: Publish your SharePoint Add-in
 <a name="Publish"> </a>
 
-To publish your SharePoint Add-in, upload the add-in manifest file (.app) of your add-in to the Office Store, the Office Add-ins catalog, SharePoint, a file share, or the Exchange catalog. The add-in manifest for your add-in is located in the  `app.publish` folder, such as `%UserProfile%\Documents\Visual Studio 2012\Projects\MyApp\bin\Debug\app.publish`. For more information about how to publish your SharePoint Add-in, see  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins).
+To publish your SharePoint Add-in, upload the add-in manifest file (.app) of your add-in to the Office Store, the Office Add-ins catalog, SharePoint, a file share, or the Exchange catalog. The add-in manifest for your add-in is located in the  `app.publish` folder, such as `%UserProfile%\Documents\Visual Studio 2012\Projects\MyApp\bin\Debug\app.publish`. For more information about how to publish your SharePoint Add-in, see  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md).
  
 
  
@@ -197,7 +203,7 @@ To publish your SharePoint Add-in, upload the add-in manifest file (.app) of you
 <a name="Additional"> </a>
 
 
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
 -  [Publish your Office Add-in](http://msdn.microsoft.com/library/7f3ae6a0-06e9-438c-8899-bd9f605e6d9e%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/publish-sharepoint-add-ins.md b/docs/sp-add-ins/publish-sharepoint-add-ins.md
index e6e6b7a6b2..c5e62b6e34 100644
--- a/docs/sp-add-ins/publish-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/publish-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Publish SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Publish SharePoint Add-ins
 Find articles and resources to help you publish your SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -21,7 +27,7 @@ You've finished developing your SharePoint Add-in—the final step is making tha
 -  **An internal organization add-in catalog.** Publish your add-ins to an internal organization add-in catalog, hosted on your SharePoint deployment, to make them available to users with access to that SharePoint deployment.
     
  
-For information about how to package your add-in for publication by using Visual Studio 2012, see  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio).
+For information about how to package your add-in for publication by using Visual Studio 2012, see  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio.md).
  
 
  
@@ -100,13 +106,13 @@ The following table offers a comparison of publishing to the Office Store or to
 -  [License your Office and SharePoint Add-ins](http://msdn.microsoft.com/library/license-your-office-and-sharepoint-add-ins%28Office.15%29.aspx)
     
  
--  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options)
+-  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md)
     
  
--  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins)
+-  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md)
     
  
--  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio)
+-  [Publish SharePoint Add-ins by using Visual Studio](publish-sharepoint-add-ins-by-using-visual-studio.md)
     
  
 -  [Publishing Office Add-ins Store](http://social.msdn.microsoft.com/Forums/en-US/officestore)
diff --git a/docs/sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint.md b/docs/sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint.md
index 7088f1a514..7acd77c807 100644
--- a/docs/sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint.md
+++ b/docs/sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint.md
@@ -1,15 +1,21 @@
+---
+title: Query a remote service using the web proxy in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Query a remote service using the web proxy in SharePoint
 Learn how to access data in a remote domain from a page that is hosted in SharePoint by using the web proxy.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 When you are building SharePoint Add-ins, you usually have to incorporate data from various sources. For security reasons, there are blocking mechanisms that prevent cross-domain communication. When you use the web proxy, the webpages in your add-in can access data in your remote domain and the SharePoint domain.
  
 
-As a developer, you can use the web proxy exposed in client APIs, such as the JavaScript and .NET client object models. When you use the web proxy, you issue the initial request to SharePoint. In turn, SharePoint requests the data to the specified endpoint and forwards the response back to your page. Use the web proxy when you want the communication to occur at the server level. For more information, see  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins).
+As a developer, you can use the web proxy exposed in client APIs, such as the JavaScript and .NET client object models. When you use the web proxy, you issue the initial request to SharePoint. In turn, SharePoint requests the data to the specified endpoint and forwards the response back to your page. Use the web proxy when you want the communication to occur at the server level. For more information, see  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md).
  
 
 
@@ -18,7 +24,7 @@ As a developer, you can use the web proxy exposed in client APIs, such as the Ja
  
 
  
-![Symbols for "your code", "SharePoint Web Proxy" and "Data source" showing that data requests pass through the web proxy.](../../images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png)
+![Symbols for "your code", "SharePoint Web Proxy" and "Data source" showing that data requests pass through the web proxy.](../images/3fbdcfae-6af9-452b-9a07-48575de7e86a.png)
  
 
  
@@ -52,9 +58,9 @@ The following table lists some useful articles that can help you understand the
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)|Learn about data access options in SharePoint Add-ins. This article provides guidance on the high-level alternatives you have to choose from when working with data in your add-in.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)|Learn about data access options in SharePoint Add-ins. This article provides guidance on the high-level alternatives you have to choose from when working with data in your add-in.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 | [Client-side Cross-domain Security](http://msdn.microsoft.com/en-us/library/cc709423%28v=vs.85%29.aspx)|Explore cross-domain threats and use cases, security principles for cross-origin requests, and weigh the risks for developers to enhance cross-domain access from web applications that run in the browser.|
 
 ## Code example: Access data in a remote service using the web proxy
@@ -84,7 +90,7 @@ Figure 1 shows the browser window with data from the remote service in a SharePo
  
 
  
-![SharePoint page with data from the remote service](../../images/WebProxy_result.png)
+![SharePoint page with data from the remote service](../images/WebProxy_result.png)
  
 
 ### To create the SharePoint Add-in project
@@ -102,7 +108,7 @@ Figure 1 shows the browser window with data from the remote service in a SharePo
 
  
 
-  ![App for SharePoint Visual Studio template](../../images/AppForSharePointVSTemplate.PNG)
+  ![App for SharePoint Visual Studio template](../images/AppForSharePointVSTemplate.PNG)
  
 
  
@@ -413,7 +419,7 @@ Figure 1 shows the browser window with data from the remote service in a SharePo
 
  
 
-  ![SharePoint page with data from the remote service](../../images/WebProxy_result.png)
+  ![SharePoint page with data from the remote service](../images/WebProxy_result.png)
  
 
  
@@ -447,13 +453,13 @@ This article demonstrated how to read data in a remote service from a SharePoint
 
  
 
--  [Code sample: Get data from a remote service using the web proxy](http://code.msdn.microsoft.com/SharePoint-2013-Get-data-705bdcd5)
+-  [Code sample: Get data from a remote service using the web proxy](http://code.msdn.microsoft.com/SharePoint-Get-data-705bdcd5)
     
  
--  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013)
+-  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md)
     
  
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
 -  [How to: Access external data with REST in SharePoint](http://msdn.microsoft.com/library/0663cc8c-a736-434d-9858-6ce12ce7f748%28Office.15%29.aspx)
@@ -464,27 +470,27 @@ This article demonstrated how to read data in a remote service from a SharePoint
 <a name="SP15Queryremoteservice_Addresources"> </a>
 
 
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#Data)
+-  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#Data)
     
  
diff --git a/docs/sp-add-ins/register-sharepoint-add-ins.md b/docs/sp-add-ins/register-sharepoint-add-ins.md
index 0e587a22d0..bd61af786f 100644
--- a/docs/sp-add-ins/register-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/register-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Register SharePoint Add-ins 2013
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Register SharePoint Add-ins 2013
 Register your SharePoint Add-ins in Azure ACS by using Visual Studio, the Seller Dashboard, or an AppRegNew.aspx page, and retrieve registration information.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 For the remote components of a provider-hosted SharePoint Add-in to interact with SharePoint using OAuth, the add-in must first register with the  [Azure ACS](https://msdn.microsoft.com/en-us/library/azure/gg429788.aspx) cloud-based service and the SharePoint App Management Service of the tenancy or farm. (It is called "App Management Service" because SharePoint Add-ins were originally called "apps for SharePoint".)
@@ -32,7 +38,7 @@ To register your add-in with Azure ACS, you specify the following information:
  
 After you register your add-in, it has an add-in identity and is a  *security principal*  , referred to as anadd-in principal. When you install your add-in, SharePoint administrators can retrieve information about that particular add-in principal.
  
-When a user first grants an add-in permissions to access SharePoint resources (which can happen either at installation or runtime, depending on the design of the app), SharePoint gets information about the add-in from Azure ACS. SharePoint then stores this information in the App Management Service database of the SharePoint tenancy or farm. The client secret is stored only with Azure ACS. SharePoint never knows the add-in's secret. The content database service and other components, such as the user profile service, can get the display name and other basic information about the add-in directly from the app management shared service. For more information, see  [Retrieve add-in registration and add-in principal information ](register-sharepoint-add-ins-2013#Retrieve) in this article.
+When a user first grants an add-in permissions to access SharePoint resources (which can happen either at installation or runtime, depending on the design of the app), SharePoint gets information about the add-in from Azure ACS. SharePoint then stores this information in the App Management Service database of the SharePoint tenancy or farm. The client secret is stored only with Azure ACS. SharePoint never knows the add-in's secret. The content database service and other components, such as the user profile service, can get the display name and other basic information about the add-in directly from the app management shared service. For more information, see  [Retrieve add-in registration and add-in principal information ](register-sharepoint-add-ins.md#Retrieve) in this article.
  
 
  **Note**  This article assumes that you are familiar with the basic concepts and principles behind the OAuth 2.0 Framework. For more information, see  [OAuth.net](http://oauth.net/) and [Web Authorization Protocol (oauth)](http://datatracker.ietf.org/doc/active/).
@@ -62,7 +68,7 @@ You can register your add-in in one of three ways, depending on where you are in
 
  
 
-  ![The form on the App Reg New page with boxes for client ID, client secret, title, app domain, &amp; redirect URL. Buttons named "generate" are beside the first two. In the corner are Create and Cancel buttons.](../../images/9a38d876-2189-418c-9314-ae493a4cab61.PNG)
+  ![The form on the App Reg New page with boxes for client ID, client secret, title, app domain, &amp; redirect URL. Buttons named "generate" are beside the first two. In the corner are Create and Cancel buttons.](../images/9a38d876-2189-418c-9314-ae493a4cab61.PNG)
  
 
  
@@ -75,7 +81,7 @@ You can register your add-in in one of three ways, depending on where you are in
  
   -  **Add-in Secret** - Also known as the client secret, an opaque string. It is generated on the AppRegNew.aspx page by using the **Generate** button. The following is an example of an add-in secret: **xvVpG0AgVIJfch6ldu4dLUlcZyysmGqBRbpFDu6AfJw=**.
     
-     **Important**  Add-in secrets expire. If you register the add-in on the Seller Dashboard, you can set the expiration for up to three years. In the dashboard, you can also add new secrets when the old ones reach their expiration date. The new secret will be enabled in all instances of the add-in. If you register the add-in with AppRegNew.aspx, the secret expires in one year. For details, see  [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in).
+     **Important**  Add-in secrets expire. If you register the add-in on the Seller Dashboard, you can set the expiration for up to three years. In the dashboard, you can also add new secrets when the old ones reach their expiration date. The new secret will be enabled in all instances of the add-in. If you register the add-in with AppRegNew.aspx, the secret expires in one year. For details, see  [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in.md).
   -  **Title** - A user-friendly title; for example,Contoso photo printing add-in. Users are prompted to grant or deny the add-in the permissions that the add-in is requesting. This title appears as the name of the add-in on the consent prompt. 
     
  
@@ -87,7 +93,7 @@ You can register your add-in in one of three ways, depending on where you are in
   - www.fabrikam.com
     
  
-  -  **Redirect URI:** - The endpoint in your remote application or service to which ACS sends an authentication code. Strictly speaking, SharePoint Add-ins don't use this value. The redirect URI is required for web applications that are launched outside of SharePoint and that use the [Authentication Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows) to get authorized access to SharePoint data. The Redirect URI is ignored for true SharePoint Add-ins (which are launched from SharePoint and use the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization#Flows)). The Redirect URI is usually the same page, controller method, web service method that requested the authentication code from ACS, but it can be a different endpoint. The endpoint must have logic that gets the authorization code from the HTTP Response that is sent by ACS and then uses that code to request an access and refresh token. For more information, see  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins). The form requires that you enter a valid value even for true SharePoint Add-ins, although it is not used.
+  -  **Redirect URI:** - The endpoint in your remote application or service to which ACS sends an authentication code. Strictly speaking, SharePoint Add-ins don't use this value. The redirect URI is required for web applications that are launched outside of SharePoint and that use the [Authentication Code flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows) to get authorized access to SharePoint data. The Redirect URI is ignored for true SharePoint Add-ins (which are launched from SharePoint and use the [Context Token flow](creating-sharepoint-add-ins-that-use-low-trust-authorization.md#Flows)). The Redirect URI is usually the same page, controller method, web service method that requested the authentication code from ACS, but it can be a different endpoint. The endpoint must have logic that gets the authorization code from the HTTP Response that is sent by ACS and then uses that code to request an access and refresh token. For more information, see  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md). The form requires that you enter a valid value even for true SharePoint Add-ins, although it is not used.
     
     The value must be a complete endpoint URL including the protocol,  *which must be HTTPS*  . For example:
     
@@ -153,7 +159,7 @@ Before you package the SharePoint Add-in and before you deploy its remote compon
 
 3. In the AppManifest.xml file in your Visual Studio project, enter the add-in ID value as the  **ClientId** value, *with lower case letters*  .
     
-     **Note**  The add-in manifest does not apply to web applications that request permission to access SharePoint resources on the fly. These are not really "SharePoint Add-ins". They are not installed on SharePoint and do not have an add-in manifest. For more information, see  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins).
+     **Note**  The add-in manifest does not apply to web applications that request permission to access SharePoint resources on the fly. These are not really "SharePoint Add-ins". They are not installed on SharePoint and do not have an add-in manifest. For more information, see  [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md).
 
     The following example shows how the  **ClientId** value is used in the AppManifest.xml file.
     
@@ -235,12 +241,12 @@ To see a list of registered add-in principals, go to:
 <a name="AR"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins)
+-  [Three authorization systems for SharePoint Add-ins](three-authorization-systems-for-sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md b/docs/sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md
index 534a0dca9f..825d3c0e8a 100644
--- a/docs/sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md
+++ b/docs/sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md
@@ -1,9 +1,15 @@
+---
+title: Replace an expiring client secret in a SharePoint Add-in
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Replace an expiring client secret in a SharePoint Add-in
 Learn how to add a new client secret for a SharePoint Add-in that is registered with AppRegNew.aspx.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Client secrets for SharePoint Add-ins that are registered using the AppRegNew.aspx page expire after one year. This article explains how to add a new secret for the add-in, as well as how to create a new client secret that is valid for three years.
diff --git a/docs/sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md b/docs/sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md
index 422c5a20e9..18718f6cce 100644
--- a/docs/sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Secure data access and client object models for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Secure data access and client object models for SharePoint Add-ins
 Learn about the data access options you have when you build SharePoint Add-ins, including connectivity options for accessing data on SharePoint and on external systems, as well as the APIs that are available when you want to access data from your add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 In evaluating your data access options for SharePoint Add-ins, you have to assess your add-in environment and consider several factors, such as communication between the client and server, and the permission level that is required for your add-in to perform the required tasks. You also have to evaluate the APIs that are available in the model for SharePoint Add-ins.
@@ -45,7 +51,7 @@ Keep in mind that you can also access certain data using (5)  *remote event rece
  
 
  
-![Options for using SharePoint data in your add-in](../../images/DataAccess_SharePointData.png)
+![Options for using SharePoint data in your add-in](../images/DataAccess_SharePointData.png)
  
 Figure 2 shows the options that you have for accessing external data on your add-in. When you are working with these scenarios, you have to decide whether you want to use (1) the  *web proxy*  , (2) *external content types*  , or (3) the *cross-domain library with a custom proxy page*  to authenticate and communicate with external services or systems. You can also use (4) theclient object model (JavaScript/.NET client object models), or (5) Representational State Transfer (REST).
  
@@ -57,7 +63,7 @@ Figure 2 shows the options that you have for accessing external data on your add
  
 
  
-![Options for using external data in your add-in](../../images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png)
+![Options for using external data in your add-in](../images/5950bc8a-ed73-4f14-b616-a88c14c4fe56.png)
  
 
  
@@ -79,13 +85,13 @@ The following connectivity options are available when accessing SharePoint data
 
  
 
--  **OAuth:** An open protocol that enables secure authorization in a simple and standard way. OAuth enables users to approve an application to act on their behalf without sharing their user name and password. You can use OAuth with server-side code. It is a good option if you need to run a non-interactive process, or if you need to elevate privileges to other than those of the logged-on user. For information about OAuth, see [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins).
+-  **OAuth:** An open protocol that enables secure authorization in a simple and standard way. OAuth enables users to approve an application to act on their behalf without sharing their user name and password. You can use OAuth with server-side code. It is a good option if you need to run a non-interactive process, or if you need to elevate privileges to other than those of the logged-on user. For information about OAuth, see [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md).
     
  
--  **Cross-domain library:** A client-side alternative in the form of a JavaScript file ( **SP.RequestExecutor.js** ) hosted in the SharePoint website that you can reference in your remote add-in. The cross-domain library allows you to interact with more than one domain in your remote add-in page through a proxy. This is a good option if you prefer your add-in code to run in the client rather than in the server, or if there are connectivity barriers, such as firewalls, between SharePoint and your remote infrastructure. For more information, see [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+-  **Cross-domain library:** A client-side alternative in the form of a JavaScript file ( **SP.RequestExecutor.js** ) hosted in the SharePoint website that you can reference in your remote add-in. The cross-domain library allows you to interact with more than one domain in your remote add-in page through a proxy. This is a good option if you prefer your add-in code to run in the client rather than in the server, or if there are connectivity barriers, such as firewalls, between SharePoint and your remote infrastructure. For more information, see [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
     
  
--  **Remote event receivers:** You can use remote event receivers to handle events that occur to an item in the add-in, such as a list, a list item, or a web. These events resemble those in a traditional SharePoint solution, except that they can work with the remote components of the SharePoint Add-in. Note that some properties of the item are available to the remote event receiver. For more information, see [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins). In a similar way, you can use add-in event receivers to customize how your add-in is installed, updated, and uninstalled. For more information, see  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins).
+-  **Remote event receivers:** You can use remote event receivers to handle events that occur to an item in the add-in, such as a list, a list item, or a web. These events resemble those in a traditional SharePoint solution, except that they can work with the remote components of the SharePoint Add-in. Note that some properties of the item are available to the remote event receiver. For more information, see [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins.md). In a similar way, you can use add-in event receivers to customize how your add-in is installed, updated, and uninstalled. For more information, see  [Create an add-in event receiver in SharePoint Add-ins](create-an-add-in-event-receiver-in-sharepoint-add-ins.md).
     
  
 
@@ -122,13 +128,13 @@ The following connectivity options are available when accessing external data (s
 
  
 
--  **Web proxy:** As a developer, you can use the web proxy exposed in client APIs such as the JSOM. When you use the web proxy, you issue the initial request to SharePoint. In turn, SharePoint requests the data to the specified endpoint and forwards the response back to your page. Use the web proxy when you want the communication to occur at the server level. The web proxy is designed to access unstructured data that doesn't require authentication. For more information, see [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013).
+-  **Web proxy:** As a developer, you can use the web proxy exposed in client APIs such as the JSOM. When you use the web proxy, you issue the initial request to SharePoint. In turn, SharePoint requests the data to the specified endpoint and forwards the response back to your page. Use the web proxy when you want the communication to occur at the server level. The web proxy is designed to access unstructured data that doesn't require authentication. For more information, see [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md).
     
  
 -  **External content types:** You can create add-ins that access external data from SAP, Netflix, and proprietary and other types of data without involving the tenant administrator.Access to external applications is maintained through Business Connectivity Services (BCS), which provides a consistent and uniform interface that can be used by other SharePoint applications. App-scoped ECTs are a good option when you are using a BCS model and access to the data requires authentication. For more information, see [Add-in-scoped external content types in SharePoint](http://msdn.microsoft.com/library/a34cbbba-dc38-4d3d-b796-d54b5848bdfb%28Office.15%29.aspx).
     
  
--  **Custom proxy page for the cross-domain library:** You can use the cross-domain library to access data in your remote add-in if you provide a custom proxy page that is hosted in the remote add-in infrastructure. As the developer, you are responsible for the custom proxy page implementation and must provide custom logic, such as the authentication mechanism to the remote add-in. Use the cross-domain library with a custom proxy page if you want the communication to occur at the client level. For more information, see [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013).
+-  **Custom proxy page for the cross-domain library:** You can use the cross-domain library to access data in your remote add-in if you provide a custom proxy page that is hosted in the remote add-in infrastructure. As the developer, you are responsible for the custom proxy page implementation and must provide custom logic, such as the authentication mechanism to the remote add-in. Use the cross-domain library with a custom proxy page if you want the communication to occur at the client level. For more information, see [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md).
     
  
 
@@ -160,7 +166,7 @@ The following API choices are available when you want to access SharePoint data
 
  
 
--  **Representational State Transfer (REST):** For scenarios in which you need to access SharePoint entities from client technologies that do not use JavaScript and are not built on the .NET Framework platform, SharePoint provides an implementation of a REST web service that uses the [Open Data (OData) protocol](http://www.odata.org/) to perform CRUDQ (Create, Read, Update, Delete, and Query) operations on SharePoint data. In addition, nearly every API in the client object models has a corresponding REST endpoint. This enables your code to interact directly with SharePoint by using any technology that supports standard REST capabilities. To use the REST capabilities that are built into SharePoint, your code constructs a RESTful HTTP request to an endpoint that corresponds to the desired SharePoint object. The REST service handles the HTTP request and serves a response in either Atom or JavaScript Object Notation (JSON) format. To learn more about REST in SharePoint, see [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests).
+-  **Representational State Transfer (REST):** For scenarios in which you need to access SharePoint entities from client technologies that do not use JavaScript and are not built on the .NET Framework platform, SharePoint provides an implementation of a REST web service that uses the [Open Data (OData) protocol](http://www.odata.org/) to perform CRUDQ (Create, Read, Update, Delete, and Query) operations on SharePoint data. In addition, nearly every API in the client object models has a corresponding REST endpoint. This enables your code to interact directly with SharePoint by using any technology that supports standard REST capabilities. To use the REST capabilities that are built into SharePoint, your code constructs a RESTful HTTP request to an endpoint that corresponds to the desired SharePoint object. The REST service handles the HTTP request and serves a response in either Atom or JavaScript Object Notation (JSON) format. To learn more about REST in SharePoint, see [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md).
     
  
 -  **.NET Framework client object model (.NET client OM):** Almost every class in the core site and list server-side object model has a corresponding class in the .NET Framework client object model. In addition, the .NET Framework client object model also exposes a full set of APIs for extending other features, including some SharePoint-level features such as ECM, taxonomy, user profiles, advanced search, analytics, BCS, and others. To learn more about client-side object models, see [Choose the right API set in SharePoint](http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d%28Office.15%29.aspx).
@@ -178,25 +184,25 @@ There might be additional APIs that you can use in your SharePoint Add-in when a
 <a name="SP15_dataaccessoptions_addResources"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
--  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013)
+-  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md)
     
  
--  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013)
+-  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md)
     
  
--  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins)
+-  [Create a remote event receiver in SharePoint Add-ins](create-a-remote-event-receiver-in-sharepoint-add-ins.md)
     
  
 -  [Choose the right API set in SharePoint](http://msdn.microsoft.com/library/f36645da-77c5-47f1-a2ca-13d4b62b320d%28Office.15%29.aspx)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
 
diff --git a/docs/sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface.md b/docs/sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
index 559d1321d2..a91ab5a6c3 100644
--- a/docs/sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
+++ b/docs/sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
@@ -1,15 +1,21 @@
+---
+title: Set custom permissions on a list by using the REST interface
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Set custom permissions on a list by using the REST interface
 Learn how to define custom, fine-grained permissions on a SharePoint list by using the REST interface and JavaScript.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 SharePoint sites, lists, and list items are types of  **SecurableObject**. By default, a securable object inherits the permissions of its parent. To set custom permissions for an object, you need to break its inheritance so that it stops inheriting permissions from its parent, and then define new permissions by adding or removing role assignments.
  
 
- **Note**  See  [Additional resources](set-custom-permissions-on-a-list-by-using-the-rest-interface#bk_addresources) for links to articles about setting fine-grained permissions.
+ **Note**  See  [Additional resources](set-custom-permissions-on-a-list-by-using-the-rest-interface.md#bk_addresources) for links to articles about setting fine-grained permissions.
  
 
 The code example in this article sets custom permissions on a list, and then changes a group's permissions to it. The example uses the REST interface to:
@@ -57,7 +63,7 @@ The following examples represent the contents of the App.js file in a SharePoint
  
 
  
-Before you run the code, replace the placeholder values with actual values. If you're using a different language or environment, you'll need to add or change some request components. See  [How REST requests differ by environment](complete-basic-operations-using-sharepoint-2013-rest-endpoints#bk_HowRequestsDiffer) for more information.
+Before you run the code, replace the placeholder values with actual values. If you're using a different language or environment, you'll need to add or change some request components. See  [How REST requests differ by environment](complete-basic-operations-using-sharepoint-rest-endpoints.md#bk_HowRequestsDiffer) for more information.
  
 
  
@@ -299,13 +305,13 @@ function errorHandler(xhr, ajaxOptions, thrownError) {
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
 - REST resources:
diff --git a/docs/sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md b/docs/sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md
index 976eb89248..610abf1bc1 100644
--- a/docs/sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md
+++ b/docs/sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md
@@ -1,11 +1,18 @@
+---
+title: Set up a development environment for SharePoint Add-ins on Office 365
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Set up a development environment for SharePoint Add-ins on Office 365
 Set up a development environment for SharePoint Add-ins on an Office 365 Developer Site.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-Please read  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins) to get an understanding of your options before you carry out any procedures in this article. See [SharePoint Add-ins](sharepoint-add-ins) if you are not sure what kinds of SharePoint Add-ins you want to create.
+Please read  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md) to get an understanding of your options before you carry out any procedures in this article. See [SharePoint Add-ins](sharepoint-add-ins.md) if you are not sure what kinds of SharePoint Add-ins you want to create.
  
 
 ## Install Visual Studio and tools on your computer
@@ -44,7 +51,7 @@ The registry path will change in future versions of Visual Studio.
 <a name="o365_signup"> </a>
 
 
- **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Enterprise with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more information, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription). 
+ **Note**   You might already have access to an Office 365 Developer Site: **Are you an MSDN subscriber?** Visual Studio Enterprise with MSDN subscribers receive an Office 365 Developer Subscription as a benefit. [Redeem your benefit today.](https://msdn.microsoft.com/subscriptions/manage/default.aspx) **Do you have one of the following Office 365 subscription plans?** **If so, an administrator of the Office 365 subscription can create a Developer Site** by using the [Office 365 admin center](https://portal.microsoftonline.com/admin/default.aspx). For more information, see  [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md). 
  
 
 Three ways to get an Office 365 plan. 
@@ -71,7 +78,7 @@ Three ways to get an Office 365 plan.
  
 
  
-![Page 2 of Sign up form for Office 365 account](../../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
+![Page 2 of Sign up form for Office 365 account](../images/ff384c69-56bf-4ceb-81c3-8b874e2407f0.png)
  
 
  
@@ -109,7 +116,7 @@ After you finish the signup process, your browser will opens the Office 365 inst
  
 
  
-![Screenshot that shows the Office 365 admin center.](../../images/SP15_Office365AdminInset_border.png)
+![Screenshot that shows the Office 365 admin center.](../images/SP15_Office365AdminInset_border.png)
  
 
  
@@ -129,7 +136,7 @@ After you finish the signup process, your browser will opens the Office 365 inst
  
 
  
-![Screenshot that shows the Developer site homepage.](../../images/SP15_DeveloperSiteHome_border.png)
+![Screenshot that shows the Developer site homepage.](../images/SP15_DeveloperSiteHome_border.png)
  
 
  
@@ -140,13 +147,13 @@ After you finish the signup process, your browser will opens the Office 365 inst
 <a name="SP15SetupSPO365_bk_addlresources"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md b/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md
index 60d21047e9..1122944492 100644
--- a/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Set up an on-premises development environment for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Set up an on-premises development environment for SharePoint Add-ins
 Learn how to set up a development environment that is specifically suited to developing SharePoint Add-ins with an on-premises installation of SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -53,7 +59,7 @@ Depending on your specific requirements and budget, you can choose from the foll
 
  
 
-  ![SharePoint Installation Server Type](../../images/SP15_app_ServerType.gif)
+  ![SharePoint Installation Server Type](../images/SP15_app_ServerType.gif)
  
 
  
@@ -75,7 +81,7 @@ dir /od *.log
 
  
 
-  ![Site template page](../../images/SP15_appChooseSiteTemplate.gif)
+  ![Site template page](../images/SP15_appChooseSiteTemplate.gif)
  
 
  
@@ -85,7 +91,7 @@ dir /od *.log
 ## Configure services in SharePoint for server-to-server add-in use
 <a name="Servertoserver"> </a>
 
-In this step, you configure services in SharePoint for server-to-server add-in use. These steps ensure that you will be able to create high trust provider-hosted add-ins with your installation. See  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins) for more information about creating this kind of add-in.
+In this step, you configure services in SharePoint for server-to-server add-in use. These steps ensure that you will be able to create high trust provider-hosted add-ins with your installation. See  [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md) for more information about creating this kind of add-in.
  
 
  
@@ -170,7 +176,7 @@ The registry path will change in future versions of Visual Studio.
 ## Configure an isolated add-in domain in SharePoint
 <a name="SP15appdevonprem_bk_configure"> </a>
 
-Please read  [Host webs, add-in webs, and the isolated domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#IsolatedDomain) before you carry out any procedures in this section.
+Please read  [Host webs, add-in webs, and the isolated domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#IsolatedDomain) before you carry out any procedures in this section.
  
 
  
@@ -242,7 +248,7 @@ $proxyAppSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $a
 
 ```
 
-7. Specify your add-in prefix (see  [Host webs, add-in webs, and the isolated domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#IsolatedDomain)) by typing the following code in the SharePoint Management Shell.
+7. Specify your add-in prefix (see  [Host webs, add-in webs, and the isolated domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#IsolatedDomain)) by typing the following code in the SharePoint Management Shell.
     
 ```
   Set-SPAppSiteSubscriptionName -Name "add-in" -Confirm:$false
@@ -283,7 +289,7 @@ $proxyAppSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $a
 9. Choose the  **OK** button to close the **Internet Options** dialog box.
     
  
-See  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options) for information about your options for deploying your add-ins.
+See  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md) for information about your options for deploying your add-ins.
  
 
  
@@ -296,13 +302,13 @@ See  [Deploying and installing SharePoint Add-ins: methods and options](deployin
 <a name="SP15SetupSPO365_bk_addlresources"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+-  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/sharepoint-add-ins-update-process.md b/docs/sp-add-ins/sharepoint-add-ins-update-process.md
index b322f5771d..d055f8c152 100644
--- a/docs/sp-add-ins/sharepoint-add-ins-update-process.md
+++ b/docs/sp-add-ins/sharepoint-add-ins-update-process.md
@@ -1,15 +1,21 @@
+---
+title: SharePoint Add-ins update process
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # SharePoint Add-ins update process
 Learn about the process for updating SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You have to update a SharePoint Add-in if you add functionality, fix a bug, or make a security update. An update to an add-in is deployed in a SharePoint Add-in package in the same way that the first version of the add-in is deployed. The SharePoint Add-in update process ensures that the add-in's data is preserved if the update fails for any reason.
  
 
- **Important**  You cannot change the  *add-in type*  using the update system. For example, you cannot change an add-in from SharePoint-hosted to provider-hosted with an update. To make a change of type, you need to [migrate from an old add-in to a new one](#Major). In particular, since  [the preview program for autohosted add-ins has been closed](http://blogs.office.com/2014/05/16/update-on-autohosted-apps-preview-program/), you should be aware that you cannot update an autohosted add-in to a provider-hosted add-in. You have to convert the add-in as explained in  [Convert an autohosted SharePoint Add-in to a provider-hosted add-in](convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in).
+ **Important**  You cannot change the  *add-in type*  using the update system. For example, you cannot change an add-in from SharePoint-hosted to provider-hosted with an update. To make a change of type, you need to [migrate from an old add-in to a new one](#Major). In particular, since  [the preview program for autohosted add-ins has been closed](http://blogs.office.com/2014/05/16/update-on-autohosted-apps-preview-program/), you should be aware that you cannot update an autohosted add-in to a provider-hosted add-in. You have to convert the add-in as explained in  [Convert an autohosted SharePoint Add-in to a provider-hosted add-in](convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md).
  
 
 
@@ -30,11 +36,11 @@ Within 24 hours after you upload your update to an organization's add-in catalog
  
 
  
-![The UI steps for updating an app](../../images/UpdatingApp_AppTileUpdateNotice.png)
+![The UI steps for updating an app](../images/UpdatingApp_AppTileUpdateNotice.png)
  
 
     
- **Tip**   When you are developing an update, you don't want to wait 24 hours every time you upload a new version to your test SharePoint add-in catalog. See [Update an add-in without waiting 24 hours ](update-sharepoint-add-ins#ImmediateUpdateNotice) for information about how to immediately update an add-in. By default, SharePoint checks every 24 hours for updates to installed add-ins. A farm administrator can set this to another value by using the following SharePoint Management Shell command, wheren is the number of hours between checks. `Set-SPInternalAppStateUpdateInterval -AppStateSyncHours n` If the value is set to 0, then the check is made every time the built-in timer job **Internal Add-in State Update** executes, which by default is every hour. Farm administrators can use Central Admin to change the frequency of the timer job or run it immediately.
+ **Tip**   When you are developing an update, you don't want to wait 24 hours every time you upload a new version to your test SharePoint add-in catalog. See [Update an add-in without waiting 24 hours ](update-sharepoint-add-ins.md#ImmediateUpdateNotice) for information about how to immediately update an add-in. By default, SharePoint checks every 24 hours for updates to installed add-ins. A farm administrator can set this to another value by using the following SharePoint Management Shell command, wheren is the number of hours between checks. `Set-SPInternalAppStateUpdateInterval -AppStateSyncHours n` If the value is set to 0, then the check is made every time the built-in timer job **Internal Add-in State Update** executes, which by default is every hour. Farm administrators can use Central Admin to change the frequency of the timer job or run it immediately.
  
 
 SharePoint will do the following when a user installs an update to a SharePoint Add-in. These events do not necessarily occur in exactly this order, and some of them may occur in parallel. Also, if update fails, there is a complete rollback.
@@ -109,28 +115,28 @@ If the old and new add-ins each contain an add-in web, consider that a new add-i
 <a name="SP15appupgrade_addlresources"> </a>
 
 
--  [Update SharePoint Add-ins](update-sharepoint-add-ins)
+-  [Update SharePoint Add-ins](update-sharepoint-add-ins.md)
     
  
--  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013)
+-  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md)
     
  
--  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013)
+-  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md)
     
  
--  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins)
+-  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md)
     
  
--  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins)
+-  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md)
     
  
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options)
+-  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md)
     
  
 
diff --git a/docs/sp-add-ins/sharepoint-add-ins-ux-design-guidelines.md b/docs/sp-add-ins/sharepoint-add-ins-ux-design-guidelines.md
index 9f26c70bf3..afac9d0677 100644
--- a/docs/sp-add-ins/sharepoint-add-ins-ux-design-guidelines.md
+++ b/docs/sp-add-ins/sharepoint-add-ins-ux-design-guidelines.md
@@ -1,8 +1,15 @@
+---
+title: SharePoint Add-ins UX design guidelines
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Add-ins UX design guidelines
 Learn about general user experience (UX) design guidelines for add-ins in SharePoint, including choosing the chrome, using CSS, managing user licenses, and other design tasks.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 Add-ins are a new concept for SharePoint, empowering end users to add new functionality to their sites while still ensuring reliability for the SharePoint site itself. Creating a good add-in requires not only making great functionality (although that's obviously important), but also ensuring that the add-in looks right and fits seamlessly into the site where it's installed.
@@ -39,7 +46,7 @@ The add-in template can be used only for SharePoint-hosted ASPX pages. The templ
  
 
  
-![A SharePoint-hosted page using the app template](../../images/AppUXGuidelines_AppTemplate.png)
+![A SharePoint-hosted page using the app template](../images/AppUXGuidelines_AppTemplate.png)
  
 The add-in template is the default in Visual Studio when you create an add-in web and pages within that web.
  
@@ -59,7 +66,7 @@ If you're not building SharePoint-hosted ASPX pages, but you still want your add
  
 
  
-![Chrome control in a webpage](../../images/AppUXGuidelines_ChromeControl.png)
+![Chrome control in a webpage](../images/AppUXGuidelines_ChromeControl.png)
  
 
  
@@ -71,7 +78,7 @@ If you're not building SharePoint-hosted ASPX pages, but you still want your add
  
 
  
-![Videos](../../images/mod_icon_video.png)
+![Videos](../images/mod_icon_video.png)
  
 
  
@@ -126,7 +133,7 @@ If you're not building SharePoint-hosted ASPX pages, but you still want your add
   nav.setBottomHeaderVisible(false);
 ```
 
-The chrome control provides for two optional add-in icons: one on the top navigation bar and one in the title area. The add-in icon on the top navigation bar is 24 x 24 pixels (px), and the icon in the title area is the same size as SharePoint site icons—up to 64 px high by up to 180 px long. We recommend you use a PNG image that you have tested on white, black, gray, bright, and muted backgrounds because users and admins can change the site theme. For more information about using the chrome control, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins).
+The chrome control provides for two optional add-in icons: one on the top navigation bar and one in the title area. The add-in icon on the top navigation bar is 24 x 24 pixels (px), and the icon in the title area is the same size as SharePoint site icons—up to 64 px high by up to 180 px long. We recommend you use a PNG image that you have tested on white, black, gray, bright, and muted backgrounds because users and admins can change the site theme. For more information about using the chrome control, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md).
  
 
  
@@ -185,98 +192,98 @@ The first thing to do when you are styling your add-in is to use semantic HTML a
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![ms-textXLarge](../../images/AppUXGuidelines_ms-textxlarge.png)|Extra large body text|.ms-textXLarge|
-|![ms-textlarge](../../images/AppUXGuidelines_ms-textlarge.png)|Large body text|.ms-textLarge|
-|![body](../../images/AppUXGuidelines_body.png)|Normal body text|Inherited automatically|
-|![ms-textsmall](../../images/AppUXGuidelines_ms-textsmall.png)|Small body text|.ms-textSmall|
-|![ms-metadata](../../images/AppUXGuidelines_ms-metadata.png)|Metadata text|.ms-metadata|
+|![ms-textXLarge](../images/AppUXGuidelines_ms-textxlarge.png)|Extra large body text|.ms-textXLarge|
+|![ms-textlarge](../images/AppUXGuidelines_ms-textlarge.png)|Large body text|.ms-textLarge|
+|![body](../images/AppUXGuidelines_body.png)|Normal body text|Inherited automatically|
+|![ms-textsmall](../images/AppUXGuidelines_ms-textsmall.png)|Small body text|.ms-textSmall|
+|![ms-metadata](../images/AppUXGuidelines_ms-metadata.png)|Metadata text|.ms-metadata|
 
 **Table 2. Title and header styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![ms-core-pagetitle](../../images/AppUXGuidelines_ms-core-pagetitle.png)|Main title on the page|.ms-core-pageTitle|
-|![h1](../../images/AppUXGuidelines_h1.png)|Title for dialog boxes, forms, blogs, and discussion posts. It's an alternative "primary" title for special content types or add-ins that take up the entire pagethat you want to be different from a regular wiki or Web Parts page.|H1|
-|![h2](../../images/AppUXGuidelines_h2.png)|Secondary heading in relation to H1. For example, Communities uses H1 Accent for the title of a post, and H2 Accent for the best "response" to the post.|H2|
-|![h3](../../images/AppUXGuidelines_h3.png)|Generally a subheading under H2.|H3|
-|![h4](../../images/AppUXGuidelines_h4.png)|Subheadings under H3.|H4|
-|![ms-webpart-titletext](../../images/AppUXGuidelines_ms-webpart-titletext.png)|Title of the main/primary Web Part on a page, or for main section headers.|.ms-webpart-titleText|
-|![ms-dlg-heading](../../images/AppUXGuidelines_ms-dlg-heading.png)|Title for headings within dialog boxes or callouts.|.ms-dlg-heading|
+|![ms-core-pagetitle](../images/AppUXGuidelines_ms-core-pagetitle.png)|Main title on the page|.ms-core-pageTitle|
+|![h1](../images/AppUXGuidelines_h1.png)|Title for dialog boxes, forms, blogs, and discussion posts. It's an alternative "primary" title for special content types or add-ins that take up the entire pagethat you want to be different from a regular wiki or Web Parts page.|H1|
+|![h2](../images/AppUXGuidelines_h2.png)|Secondary heading in relation to H1. For example, Communities uses H1 Accent for the title of a post, and H2 Accent for the best "response" to the post.|H2|
+|![h3](../images/AppUXGuidelines_h3.png)|Generally a subheading under H2.|H3|
+|![h4](../images/AppUXGuidelines_h4.png)|Subheadings under H3.|H4|
+|![ms-webpart-titletext](../images/AppUXGuidelines_ms-webpart-titletext.png)|Title of the main/primary Web Part on a page, or for main section headers.|.ms-webpart-titleText|
+|![ms-dlg-heading](../images/AppUXGuidelines_ms-dlg-heading.png)|Title for headings within dialog boxes or callouts.|.ms-dlg-heading|
 
 **Table 3. Navigation styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![QuickLaunchHeading](../../images/AppUXGuidelines_QuickLaunchHeading.png)|Heading of the left navigation bar.|.ms-core-listMenu-verticalBox > .ms-core-listMenu-root > li > .ms-core-listMenu-item|
-|![QuickLaunchLink](../../images/AppUXGuidelines_QuickLaunchLink.png)|Link in the left navigation bar.|.ms-core-listMenu-verticalBox|
-|![QuickLaunchSelected](../../images/AppUXGuidelines_QuickLaunchSelected.png)|Selected item in the left navigation bar.|.ms-core-listMenu-verticalBox + .ms-accentText|
-|![TopNav](../../images/AppUXGuidelines_TopNav.png)|Item in the top navigation bar.||
-|![TopNavSelected](../../images/AppUXGuidelines_TopNavSelected.png)|Selected item in the top navigation bar.||
+|![QuickLaunchHeading](../images/AppUXGuidelines_QuickLaunchHeading.png)|Heading of the left navigation bar.|.ms-core-listMenu-verticalBox > .ms-core-listMenu-root > li > .ms-core-listMenu-item|
+|![QuickLaunchLink](../images/AppUXGuidelines_QuickLaunchLink.png)|Link in the left navigation bar.|.ms-core-listMenu-verticalBox|
+|![QuickLaunchSelected](../images/AppUXGuidelines_QuickLaunchSelected.png)|Selected item in the left navigation bar.|.ms-core-listMenu-verticalBox + .ms-accentText|
+|![TopNav](../images/AppUXGuidelines_TopNav.png)|Item in the top navigation bar.||
+|![TopNavSelected](../images/AppUXGuidelines_TopNavSelected.png)|Selected item in the top navigation bar.||
 
 **Table 4. Command styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![ms-commandlink](../../images/AppUXGuidelines_ms-commandlink.png)|Primary action links you expect the user to take within a given container or page. For example, this would be used to style the commands underneath a callout. This will always be the same color for visited and non-visited commands.|.ms-commandLink|
-|![ms-secondarycommandlink](../../images/AppUXGuidelines_ms-secondarycommandlink.png)|Also used to style action links, but for actions that are secondary to the content. This style is used for these secondary actions, so they don't compete with content for attention.|.ms-secondaryCommandLink|
-|![ms-calloutlink](../../images/AppUXGuidelines_ms-calloutlink.png)|Links in the callout.|.ms-calloutLink|
+|![ms-commandlink](../images/AppUXGuidelines_ms-commandlink.png)|Primary action links you expect the user to take within a given container or page. For example, this would be used to style the commands underneath a callout. This will always be the same color for visited and non-visited commands.|.ms-commandLink|
+|![ms-secondarycommandlink](../images/AppUXGuidelines_ms-secondarycommandlink.png)|Also used to style action links, but for actions that are secondary to the content. This style is used for these secondary actions, so they don't compete with content for attention.|.ms-secondaryCommandLink|
+|![ms-calloutlink](../images/AppUXGuidelines_ms-calloutlink.png)|Links in the callout.|.ms-calloutLink|
 
 **Table 5. Modifier styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![ms-accenttext](../../images/AppUXGuidelines_ms-accenttext.png)|Helper class that will provide the accent color from the current theme for text.|.ms-accentText|
-|![hyperlink](../../images/AppUXGuidelines_hyperlink.png)|Links in the content should inherit from default hyperlink styling and behavior. Hyperlink styling applies a color and a hover effect to indicate that it's a link instead of normal text.|Inherited from using <a>.|
-|![ms-error](../../images/AppUXGuidelines_ms-error.png)|Error messages that occur in forms.|.ms-error|
-|![ms-soften](../../images/AppUXGuidelines_ms-soften.png)|Helper class that provides a softened gray for text that should be less emphasized than normal body text.|.ms-soften|
-|![ms-disabled](../../images/AppUXGuidelines_ms-disabled.png)|Helper class that applies the "disabled" color to text, which is used for denoting disabled states.|.ms-disabled|
-|![ms-uppercase](../../images/AppUXGuidelines_ms-uppercase.png)|Helper class that transforms the text to all caps.|.ms-uppercase|
-|![ms-helper](../../images/AppUXGuidelines_ms-helper.png)|Helper class to style text like forms.|.ms-helper|
-|![hr](../../images/AppUXGuidelines_hr.png)|Dashed line divider that is used to divide sections in the Quick Launch and in menus.|HR|
+|![ms-accenttext](../images/AppUXGuidelines_ms-accenttext.png)|Helper class that will provide the accent color from the current theme for text.|.ms-accentText|
+|![hyperlink](../images/AppUXGuidelines_hyperlink.png)|Links in the content should inherit from default hyperlink styling and behavior. Hyperlink styling applies a color and a hover effect to indicate that it's a link instead of normal text.|Inherited from using <a>.|
+|![ms-error](../images/AppUXGuidelines_ms-error.png)|Error messages that occur in forms.|.ms-error|
+|![ms-soften](../images/AppUXGuidelines_ms-soften.png)|Helper class that provides a softened gray for text that should be less emphasized than normal body text.|.ms-soften|
+|![ms-disabled](../images/AppUXGuidelines_ms-disabled.png)|Helper class that applies the "disabled" color to text, which is used for denoting disabled states.|.ms-disabled|
+|![ms-uppercase](../images/AppUXGuidelines_ms-uppercase.png)|Helper class that transforms the text to all caps.|.ms-uppercase|
+|![ms-helper](../images/AppUXGuidelines_ms-helper.png)|Helper class to style text like forms.|.ms-helper|
+|![hr](../images/AppUXGuidelines_hr.png)|Dashed line divider that is used to divide sections in the Quick Launch and in menus.|HR|
 
 **Table 6. Part user interface styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![drag files](../../images/AppUXGuidelines_dragfiles.png)|Main inline text at the top of a part.|.ms-textXLarge + .ms-soften|
-|![ms-herocommandlink](../../images/AppUXGuidelines_ms-herocommandlink.png)|Commands in the top line of a part; at most there should be only one or two of these per part.|.ms-heroCommandLink|
-|![ms-attractmode](../../images/AppUXGuidelines_ms-attractmode.png)|Text shown to entice the user to interact with the part when it doesn't contain data.|.ms-attractMode|
-|![ms-emptymode](../../images/AppUXGuidelines_ms-emptymode.png)|Text shown to the user when there is no data available.|.ms-emptyMode|
-|![mspivotlink](../../images/AppUXGuidelines_mspivotlink.png)|View controls, such as a pivot.|.ms-pivot-link|
-|![ms-listlink](../../images/AppUXGuidelines_ms-listlink.png)|List items that are also links.|.ms-listLink|
+|![drag files](../images/AppUXGuidelines_dragfiles.png)|Main inline text at the top of a part.|.ms-textXLarge + .ms-soften|
+|![ms-herocommandlink](../images/AppUXGuidelines_ms-herocommandlink.png)|Commands in the top line of a part; at most there should be only one or two of these per part.|.ms-heroCommandLink|
+|![ms-attractmode](../images/AppUXGuidelines_ms-attractmode.png)|Text shown to entice the user to interact with the part when it doesn't contain data.|.ms-attractMode|
+|![ms-emptymode](../images/AppUXGuidelines_ms-emptymode.png)|Text shown to the user when there is no data available.|.ms-emptyMode|
+|![mspivotlink](../images/AppUXGuidelines_mspivotlink.png)|View controls, such as a pivot.|.ms-pivot-link|
+|![ms-listlink](../images/AppUXGuidelines_ms-listlink.png)|List items that are also links.|.ms-listLink|
 
 **Table 7. Background and border styles**
 
 
 |**Example**|**Used for**|**Style**|
 |:-----|:-----|:-----|
-|![ms-emphasis](../../images/AppUXGuidelines_ms-emphasis.png)|To style a rectangle that should be heavily emphasized on the page.|.ms-emphasis|
-|![ms-emphasisborder](../../images/AppUXGuidelines_ms-emphasisborder.png)|Border of an emphasized element.|.ms-emphasisBorder|
-|![ms-subtleemphasis](../../images/AppUXGuidelines_ms-subtleemphasis.png)|A more subtle emphasis of an element.|.ms-subtleEmphasis|
-|![ms-subtleemphasiscommand](../../images/AppUXGuidelines_ms-subtleemphasiscommand.png)|Commands in an element styled with ms-subtleEmphasis.|.ms-subtleEmphasisCommand|
-|![ms-subtleemphasiscommand-disabled](../../images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png)|Disabled command in an element styled with ms-subtleEmphasis.|.ms-subtleEmphasisCommand-disabled|
-|![ms-sidenav](../../images/AppUXGuidelines_ms-sidenav.png)|Side navigation elements.|.ms-sideNav|
-|![ms-sidenav-selected](../../images/AppUXGuidelines_ms-sidenav-selected.png)|To style the selected side navigation element.|.ms-sideNav-selected|
-|![ms-lines](../../images/AppUXGuidelines_ms-lines.png)|To emphasize an element using a border.|.ms-lines|
-|![ms-subtlelines](../../images/AppUXGuidelines_ms-subtlelines.png)|To emphasize an element using a subtle border.|.ms-subtleLines|
-|![ms-stronglines](../../images/AppUXGuidelines_ms-stronglines.png)|To emphasize an element using a strong or colored border.|.ms-strongLines|
-|![ms-disabledlines](../../images/AppUXGuidelines_ms-disabledlines.png)|To emphasize a disabled element using a border.|.ms-disabledLines|
-|![ms-accentlines](../../images/AppUXGuidelines_ms-accentlines.png)|To emphasize an element using an accent border.|.ms-accentLines|
-|![ms-popupborder](../../images/AppUXGuidelines_ms-popupborder.png)|To contain pop-up windows.|.ms-popupBorder|
-|![ms-bgoverlay](../../images/AppUXGuidelines_ms-bgoverlay.png)|To apply an overlay on the background element.|.ms-bgOverlay|
-|![bgdisabled](../../images/AppUXGuidelines_bgdisabled.png)|To make the background of an element appear disabled.|.ms-bgDisabled|
-|![ms-bgheader](../../images/AppUXGuidelines_ms-bgheader.png)|To apply the header background color.|.ms-bgHeader|
-|![ms-bgfooter](../../images/AppUXGuidelines_ms-bgfooter.png)|To apply the footer background color.|.ms-bgFooter|
-|![md-bghoverable normal](../../images/AppUXGuidelines_md-bghoverable-normal.png)|Elements that should have a highlighted color on hover. The example shows the element when the mouse is not hovering over it.|.ms-bgHoverable|
-|![ms-bghoverable-onhover](../../images/AppUXGuidelines_ms-bghoverable-onhover.png)|Elements that should have a highlighted color on hover. The example shows the element when the mouse is hovering over it.|.ms-bgHoverable|
-|![ms-bgselected](../../images/AppUXGuidelines_ms-bgselected.png)|To show selection on an element.|.ms-bgSelected|
-|![ms-topbar](../../images/AppUXGuidelines_ms-topbar.png)|Elements in the top bar of the page.|.ms-topBar|
-For more information, see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins).
+|![ms-emphasis](../images/AppUXGuidelines_ms-emphasis.png)|To style a rectangle that should be heavily emphasized on the page.|.ms-emphasis|
+|![ms-emphasisborder](../images/AppUXGuidelines_ms-emphasisborder.png)|Border of an emphasized element.|.ms-emphasisBorder|
+|![ms-subtleemphasis](../images/AppUXGuidelines_ms-subtleemphasis.png)|A more subtle emphasis of an element.|.ms-subtleEmphasis|
+|![ms-subtleemphasiscommand](../images/AppUXGuidelines_ms-subtleemphasiscommand.png)|Commands in an element styled with ms-subtleEmphasis.|.ms-subtleEmphasisCommand|
+|![ms-subtleemphasiscommand-disabled](../images/AppUXGuidelines_ms-subtleemphasiscommand-disabled.png)|Disabled command in an element styled with ms-subtleEmphasis.|.ms-subtleEmphasisCommand-disabled|
+|![ms-sidenav](../images/AppUXGuidelines_ms-sidenav.png)|Side navigation elements.|.ms-sideNav|
+|![ms-sidenav-selected](../images/AppUXGuidelines_ms-sidenav-selected.png)|To style the selected side navigation element.|.ms-sideNav-selected|
+|![ms-lines](../images/AppUXGuidelines_ms-lines.png)|To emphasize an element using a border.|.ms-lines|
+|![ms-subtlelines](../images/AppUXGuidelines_ms-subtlelines.png)|To emphasize an element using a subtle border.|.ms-subtleLines|
+|![ms-stronglines](../images/AppUXGuidelines_ms-stronglines.png)|To emphasize an element using a strong or colored border.|.ms-strongLines|
+|![ms-disabledlines](../images/AppUXGuidelines_ms-disabledlines.png)|To emphasize a disabled element using a border.|.ms-disabledLines|
+|![ms-accentlines](../images/AppUXGuidelines_ms-accentlines.png)|To emphasize an element using an accent border.|.ms-accentLines|
+|![ms-popupborder](../images/AppUXGuidelines_ms-popupborder.png)|To contain pop-up windows.|.ms-popupBorder|
+|![ms-bgoverlay](../images/AppUXGuidelines_ms-bgoverlay.png)|To apply an overlay on the background element.|.ms-bgOverlay|
+|![bgdisabled](../images/AppUXGuidelines_bgdisabled.png)|To make the background of an element appear disabled.|.ms-bgDisabled|
+|![ms-bgheader](../images/AppUXGuidelines_ms-bgheader.png)|To apply the header background color.|.ms-bgHeader|
+|![ms-bgfooter](../images/AppUXGuidelines_ms-bgfooter.png)|To apply the footer background color.|.ms-bgFooter|
+|![md-bghoverable normal](../images/AppUXGuidelines_md-bghoverable-normal.png)|Elements that should have a highlighted color on hover. The example shows the element when the mouse is not hovering over it.|.ms-bgHoverable|
+|![ms-bghoverable-onhover](../images/AppUXGuidelines_ms-bghoverable-onhover.png)|Elements that should have a highlighted color on hover. The example shows the element when the mouse is hovering over it.|.ms-bgHoverable|
+|![ms-bgselected](../images/AppUXGuidelines_ms-bgselected.png)|To show selection on an element.|.ms-bgSelected|
+|![ms-topbar](../images/AppUXGuidelines_ms-topbar.png)|Elements in the top bar of the page.|.ms-topBar|
+For more information, see  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md).
  
 
  
@@ -446,7 +453,7 @@ Parts are a way for your add-in to surface some information or a small interacti
  
 
  
-![Tag cloud part](../../images/AppUXGuidelines_part.png)
+![Tag cloud part](../images/AppUXGuidelines_part.png)
  
 In Figure 3, the  **Tag Cloud from UX Design add-in** is the title of the part. The tag cloud itself is served from the add-in content, and it is hosted in an **iframe** element and fully isolated from the hosting page. Because the add-in content is using the host web's CSS file, it fits in seamlessly with the host page.
  
@@ -456,7 +463,7 @@ Some kinds of UI lend themselves well to being exposed through part UI. For exam
  
 
  
-The page you display inside the part will be hosted in an  **iframe**, so you should make sure that any JavaScript you write is aware of that and is smart about accessing things like the window object. Even if the rest of your add-in is heavily branded, you should consider adopting the host web's styling for your part, because it will be embedded within the host web's pages and will look jarring and unappealing if it doesn't fit in. In order to use the host web's styling, you'll have to build the link to the default CSS file manually. For more information, see  [How to: Reference the host web's CSS file](sharepoint-add-ins-ux-design-guidelines#UXGuide_CSSHowto) in this article. There also should not be any chrome on the page, because it will be embedded on a page that already has chrome itself.
+The page you display inside the part will be hosted in an  **iframe**, so you should make sure that any JavaScript you write is aware of that and is smart about accessing things like the window object. Even if the rest of your add-in is heavily branded, you should consider adopting the host web's styling for your part, because it will be embedded within the host web's pages and will look jarring and unappealing if it doesn't fit in. In order to use the host web's styling, you'll have to build the link to the default CSS file manually. For more information, see  [How to: Reference the host web's CSS file](#UXGuide_CSS) in this article. There also should not be any chrome on the page, because it will be embedded on a page that already has chrome itself.
  
 
  
@@ -601,7 +608,7 @@ When the part is added to the page, any strings in the query string that match t
  
 
  
-You can also choose to have the Web Part ID sent on the query string by using the _wpid_ string to represent where you want it to be replaced on the query string. This can be helpful in differentiating different part instances if you want to be able to store information about user choices or interactions on a per-instance basis. For more information, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in).
+You can also choose to have the Web Part ID sent on the query string by using the _wpid_ string to represent where you want it to be replaced on the query string. This can be helpful in differentiating different part instances if you want to be able to store information about user choices or interactions on a per-instance basis. For more information, see  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md).
  
 
  
@@ -618,7 +625,7 @@ If you have functionality that would make sense to surface in the context of lis
  
 
  
-![A custom action in the contextual menu](../../images/AppUXGuidelines_ECBcustomaction.png)
+![A custom action in the contextual menu](../images/AppUXGuidelines_ECBcustomaction.png)
  
 The code for custom actions that are surfaced in the host web is the same as in previous versions of SharePoint, with the following restrictions:
  
@@ -675,7 +682,7 @@ You cannot add a custom tab to the ribbon of the host web from your add-in. You
  
 
  
-If you have a few controls that are related to each other, or that the user will likely associate with using your add-in, you should group them in their own custom group so that the user is more likely to find them. If, on the other hand, the functionality you're adding is more likely to be something the user considers part of the core experience of their site, you should try to fit that control into a logical spot in the existing ribbon locations. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins).
+If you have a few controls that are related to each other, or that the user will likely associate with using your add-in, you should group them in their own custom group so that the user is more likely to find them. If, on the other hand, the functionality you're adding is more likely to be something the user considers part of the core experience of their site, you should try to fit that control into a logical spot in the existing ribbon locations. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md).
  
 
  
@@ -687,7 +694,7 @@ In many cases, it makes sense for your add-in to have some configuration informa
  
 
  
-You should add the settings page URL to the app's top-right menu if appropriate so that users can find it easily. If your add-in has a getting started experience or other settings, you can add those also. For more information, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins).
+You should add the settings page URL to the app's top-right menu if appropriate so that users can find it easily. If your add-in has a getting started experience or other settings, you can add those also. For more information, see  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md).
  
 
  
@@ -795,25 +802,25 @@ Due to upgrades or site maintenance, there might be times when SharePoint is in
 <a name="bk_addresources"> </a>
 
 
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)
+-  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)
     
  
--  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)
+-  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
--  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)
+-  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)
     
  
--  [Customize a list view in SharePoint Add-ins using client-side rendering](customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering)
+-  [Customize a list view in SharePoint Add-ins using client-side rendering](customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md)
     
  
 
diff --git a/docs/sp-add-ins/sharepoint-add-ins.md b/docs/sp-add-ins/sharepoint-add-ins.md
index 24edca3c7e..caaf7d65b3 100644
--- a/docs/sp-add-ins/sharepoint-add-ins.md
+++ b/docs/sp-add-ins/sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # SharePoint Add-ins
 SharePoint Add-ins are self-contained extensions of SharePoint websites that you create, and that run without custom code on the SharePoint server.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -37,9 +43,9 @@ There are two basic kinds of SharePoint Add-ins — SharePoint-hosted and provid
     
 |||
 |:-----|:-----|
-|![Immersive Full Page SharePoint app experience](../../images/7298a25b-ed54-4953-a781-26c3f633866a.jpg)|**As an immersive full-page experience** that can have the look and feel of a SharePoint page.|
-|![App Part experience for SharePoint app](../../images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg)|**As part of a webpage, using a special kind of control, called an add-in part**, to surface an iframe element that contains the add-in.|
-|![Custom action experience of SharePoint app](../../images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg)|**As UI commands that extend ribbons and menus** for lists, documents, and more.|
+|![Immersive Full Page SharePoint app experience](../images/7298a25b-ed54-4953-a781-26c3f633866a.jpg)|**As an immersive full-page experience** that can have the look and feel of a SharePoint page.|
+|![App Part experience for SharePoint app](../images/90cd4b6e-462e-442e-92de-86b2d98282d0.jpg)|**As part of a webpage, using a special kind of control, called an add-in part**, to surface an iframe element that contains the add-in.|
+|![Custom action experience of SharePoint app](../images/3a14cfdc-51e1-446f-82d9-acb4f2bcbc0e.jpg)|**As UI commands that extend ribbons and menus** for lists, documents, and more.|
 -  **All SharePoint Add-ins that users install get a tile on the  **Site Contents** page of the SharePoint website.** Clicking the tile runs the add-in.
     
  
@@ -94,7 +100,7 @@ When you need to update an add-in to fix a bug or to add functionality, make the
 
 
  
-![Comparison SharePoint-hosted and provider-hosted apps](../../images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png)
+![Comparison SharePoint-hosted and provider-hosted apps](../images/eb5b0e2b-4b96-46a4-bd74-faafd7717e26.png)
  
 
 ### SharePoint-hosted SharePoint Add-ins
@@ -186,12 +192,12 @@ Ready to get started?
 
 -  **If you are an experienced SharePoint developer, we recommend that you start with SharePoint-hosted add-ins.** They're the most similar to the kinds of SharePoint extensions that you have made in the past.
     
-     [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+     [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
 -  **If you are an experienced ASP.NET web application developer, we recommend that you start with provider-hosted add-ins.** They're built around web applications.
     
-     [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins)
+     [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
     
  
 -  **If you want to develop a provider-hosted add-in on a non-Microsoft stack, here's how to get started:**
@@ -199,18 +205,18 @@ Ready to get started?
       -  Install tools that are appropriate for your stack, if you don't already have them.
     
  
-  - Get a developer account on Office 365 for testing and debugging purposes. For details, go to  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365), or if you already have an Office 365 subscription, you just need to  [create a Developer Site on it.](create-a-developer-site-on-an-existing-office-365-subscription).
+  - Get a developer account on Office 365 for testing and debugging purposes. For details, go to  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md), or if you already have an Office 365 subscription, you just need to  [create a Developer Site on it.](create-a-developer-site-on-an-existing-office-365-subscription.md).
     
  
   - Your add-in will use SharePoint's REST/OData APIs to perform CRUD operations on SharePoint data:
     
-      - Find our explanatory documentation in the article  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service) and other articles to which it links.
+      - Find our explanatory documentation in the article  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md) and other articles to which it links.
     
  
   - Find reference documentation at  [REST API reference for SharePoint](http://msdn.microsoft.com/library/3514e753-19f9-4b41-a1ae-f35c5ffc17d2%28Office.15%29.aspx).
     
  
-  - If you are not using Visual Studio, you have to create the add-in manifest file and the add-in package. For information, see  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in). There are a lot of time-saving advantages to using Visual Studio and Microsoft Office Developer Tools for Visual Studio to make your manifest and package. We recommend that you consider them, even if you use another tool to create the remote web application itself. The  [Community edition of Visual Studio](https://www.visualstudio.com/news/vs2013-community-vs.aspx) is free.
+  - If you are not using Visual Studio, you have to create the add-in manifest file and the add-in package. For information, see  [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md). There are a lot of time-saving advantages to using Visual Studio and Microsoft Office Developer Tools for Visual Studio to make your manifest and package. We recommend that you consider them, even if you use another tool to create the remote web application itself. The  [Community edition of Visual Studio](https://www.visualstudio.com/news/vs2013-community-vs.aspx) is free.
     
  
   - There are sample provider-hosted add-ins for some non-Microsoft languages and platforms in the  [OfficeDev section of GitHub](https://github.com/OfficeDev); for example,  [PHP-App-for-SharePoint](https://github.com/OfficeDev/PHP-App-for-SharePoint).
@@ -229,4 +235,4 @@ Ready to get started?
 
 
  
- [Developing Microsoft SharePoint Server 2013 Core Solutions Jump Start](http://www.microsoftvirtualacademy.com/training-courses/developing-microsoft-sharepoint-server-2013-core-solutions-jump-start)
+ [Developing Microsoft SharePoint Server 2013 Core Solutions Jump Start](http://www.microsoftvirtualacademy.com/training-courses/developing-microsoft-sharepoint-server-core-solutions-jump-start)
diff --git a/docs/sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index.md b/docs/sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index.md
index 764212961d..73d7b15d05 100644
--- a/docs/sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index.md
+++ b/docs/sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index.md
@@ -1,9 +1,15 @@
+---
+title: SharePoint .NET Server, CSOM, JSOM, and REST API index
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # SharePoint .NET Server, CSOM, JSOM, and REST API index
 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -102,13 +108,13 @@ Table 1 lists the most frequently used, core APIs, which are in most cases based
 <a name="bk_addresources"> </a>
 
 
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
 
diff --git a/docs/sp-add-ins/synchronize-sharepoint-items-using-the-rest-service.md b/docs/sp-add-ins/synchronize-sharepoint-items-using-the-rest-service.md
index 8b12fc27e0..d32fdff952 100644
--- a/docs/sp-add-ins/synchronize-sharepoint-items-using-the-rest-service.md
+++ b/docs/sp-add-ins/synchronize-sharepoint-items-using-the-rest-service.md
@@ -1,9 +1,15 @@
+---
+title: Synchronize SharePoint items using the REST service
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Synchronize SharePoint items using the REST service
 Learn how to synchronize items between SharePoint and your add-ins or services by using the  **GetListItemChangesSinceToken** resource, part of the SharePoint REST service.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -75,25 +81,25 @@ The request returns ADO  **rowset** XML which includes rows corresponding to any
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
--  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)
+-  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)
     
  
--  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris)
+-  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md)
     
  
--  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests)
+-  [Use OData query operations in SharePoint REST requests](use-odata-query-operations-in-sharepoint-rest-requests.md)
     
  
 -  [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins.md b/docs/sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins.md
index b214a78f0b..f56e8f304b 100644
--- a/docs/sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Tenancies and deployment scopes for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Tenancies and deployment scopes for SharePoint Add-ins
  Learn about the concept of tenancies and the differences between deploying SharePoint Add-ins at tenant scope and web scope.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -27,7 +33,7 @@ When new site collections are created in the tenancy, add-ins that were previous
 
  
 
- **Note**  Add-in scope should not be confused with Feature scope. Feature scope determines where the elements in a Feature are deployed. The possibilities include  **Farm**,  **WebApplication**,  **Site** (that is, site collection), and **Web**. Only  **Web** is permitted for Features in SharePoint Add-ins (both host web Features and Features inside a .wsp in an add-in package).Add-in scope should also not be confused with add-in permission levels. SharePoint Add-ins can request permissions to all or selected parts of SharePoint content at the levels of list, web, site collection, and tenancy. Installing an add-in with tenant scope does not give it permissions that it would not otherwise have, nor does it cancel key provisions of the SharePoint security model. For more information about add-in permissions, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint-2013).
+ **Note**  Add-in scope should not be confused with Feature scope. Feature scope determines where the elements in a Feature are deployed. The possibilities include  **Farm**,  **WebApplication**,  **Site** (that is, site collection), and **Web**. Only  **Web** is permitted for Features in SharePoint Add-ins (both host web Features and Features inside a .wsp in an add-in package).Add-in scope should also not be confused with add-in permission levels. SharePoint Add-ins can request permissions to all or selected parts of SharePoint content at the levels of list, web, site collection, and tenancy. Installing an add-in with tenant scope does not give it permissions that it would not otherwise have, nor does it cancel key provisions of the SharePoint security model. For more information about add-in permissions, see  [Add-in permissions in SharePoint](add-in-permissions-in-sharepoint.md).
  
 
 
@@ -116,16 +122,16 @@ Regardless of whether an add-in is installed from the Office Store or from an ad
 <a name="SP15tenancies_addlresources"> </a>
 
 
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options)
+-  [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md)
     
  
--  [SharePoint Add-ins update process](sharepoint-add-ins-update-process)
+-  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md)
     
  
 
diff --git a/docs/sp-add-ins/three-authorization-systems-for-sharepoint-add-ins.md b/docs/sp-add-ins/three-authorization-systems-for-sharepoint-add-ins.md
index 313c4cebd2..9797647a00 100644
--- a/docs/sp-add-ins/three-authorization-systems-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/three-authorization-systems-for-sharepoint-add-ins.md
@@ -1,8 +1,15 @@
+---
+title: Three authorization systems for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Three authorization systems for SharePoint Add-ins
 Learn the three systems that SharePoint Add-ins can use to get authorization to SharePoint resources.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 In SharePoint, a SharePoint Add-in is an identity principal just like a user and it must be authenticated and authorized to use SharePoint resources. There are three authorization systems that an add-in can use. They are not mutually exclusive.
@@ -18,17 +25,17 @@ In SharePoint, a SharePoint Add-in is an identity principal just like a user and
 
 -  **Low-Trust**: A provider-hosted SharePoint Add-in can register with Microsoft Azure Access Control Service (ACS) which issues an access token to the add-in that allows the add-in access to the resources in the SharePoint tenancy or farm on which the add-in is installed. Azure ACS is the trusted token issuer in an OAuth 2.0 Framework "flow" that includes SharePoint and the remote components of the add-in. Add-ins that use this system can be sold in the Office Store. The low-trust system is primarily intended for add-ins whose remote components are hosted in the cloud.
     
-    For more information about creating a SharePoint Add-in that uses the low-trust system, see the SDK node  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization).
+    For more information about creating a SharePoint Add-in that uses the low-trust system, see the SDK node  [Creating SharePoint Add-ins that use low-trust authorization](creating-sharepoint-add-ins-that-use-low-trust-authorization.md).
     
      **Note**  The customer who installs the add-in must have an Office 365 account. This is needed to give the add-in access to the Azure ACS. However, the customer need not use the account for any other purpose, and the add-in can be installed to an on-premise SharePoint farm after some simple configuration tasks on the farm.
 -  **High-Trust**: A provider-hosted add-in can establish trust with SharePoint by using digital certificates. The high-trust system is primarily intended for add-ins whose remote components are hosted on-premise. The add-in can be installed to a SharePoint farm that is not connected to the Internet. The add-in cannot be installed on SharePoint Online or sold in the Office Store.
     
-    For more information about creating a SharePoint Add-in that uses the high-trust system, see the SDK node  [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization).
+    For more information about creating a SharePoint Add-in that uses the high-trust system, see the SDK node  [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization.md).
     
  
 -  **Cross-Domain Library**: When the add-in's business logic is in JavaScript, you have the option of using the SharePoint cross-domain library either in place of, or as a supplement to, the low-trust and high-trust systems. The library is also intended for scenarios where the add-in has cloud-hosted components, but the customer's corporate firewall makes it difficult to use the low-trust system. The user's browser blocks scripts from other domains, but the library encapsulates a secure system for working around this restriction. Add-ins that use the library can be sold in the Office Store and can be installed to either SharePoint Online or on-premise SharePoint.
     
-    For more information about creating a SharePoint Add-in that uses the cross-domain library, see the SDK node  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library), the blog post  [Solving cross-domain problems in SharePoint Add-ins](http://blogs.msdn.com/b/officeapps/archive/2012/11/29/solving-cross-domain-problems-in-apps-for-sharepoint.aspx).
+    For more information about creating a SharePoint Add-in that uses the cross-domain library, see the SDK node  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library.md), the blog post  [Solving cross-domain problems in SharePoint Add-ins](http://blogs.msdn.com/b/officeapps/archive/2012/11/29/solving-cross-domain-problems-in-apps-for-sharepoint.aspx).
     
  
 
@@ -72,7 +79,7 @@ So, in the SharePoint implementation, the OAuth roles are played by the followin
 - SharePoint plays the role of the resource server.
     
  
-- Azure ACS plays the role of the authorization server when  [the low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization) is used. When the [the high-trust system](creating-sharepoint-add-ins-that-use-high-trust-authorization) is used, the add-in itself (along with a digitial certificate) becomes the authorization server.
+- Azure ACS plays the role of the authorization server when  [the low-trust authorization system](creating-sharepoint-add-ins-that-use-low-trust-authorization.md) is used. When the [the high-trust system](creating-sharepoint-add-ins-that-use-high-trust-authorization.md) is used, the add-in itself (along with a digitial certificate.md) becomes the authorization server.
     
  
 
diff --git a/docs/sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins.md b/docs/sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins.md
index c6184b59cf..6bcfc7a645 100644
--- a/docs/sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Three ways to think about design options for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Three ways to think about design options for SharePoint Add-ins
-Get an overview of the design and architecture options that are available with SharePoint Add-ins. You should first be familiar with the article  [SharePoint Add-ins](sharepoint-add-ins).
+Get an overview of the design and architecture options that are available with SharePoint Add-ins. You should first be familiar with the article  [SharePoint Add-ins](sharepoint-add-ins.md).
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -32,31 +38,31 @@ There are three major categories of choices that need to be made when a SharePoi
       -  **Provider-hosted** add-ins have their primary data storage and business logic deployed and hosted by you—the developer—outside of SharePoint in servers or a cloud account that you provide. You are responsible for enforcing isolation between the accounts of the various customers who purchase your add-in. Such add-ins can have SharePoint components too. These are hosted in the customer's SharePoint farm. This type of add-in provides you with the most flexibility in the other categories of design choices. It also enables you to use non-Microsoft platforms for the external data, logic, and web user interface (UI). (Within the category of provider-hosted add-ins, you also need to distinguish between add-ins whose remote components are within the same corporate firewall as the SharePoint farm and those whose remote components are outside of that firewall. The authorization systems for these two scenarios are different, which, in turn, makes a difference in which programming language you use to access the SharePoint data..)
     
  
-  -  **SharePoint-hosted** add-ins consist entirely of SharePoint components, such as lists, content types, workflows, and Web Parts. There are no external components. For more information about the kinds of SharePoint components that can be included in SharePoint Add-ins, see [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013).
+  -  **SharePoint-hosted** add-ins consist entirely of SharePoint components, such as lists, content types, workflows, and Web Parts. There are no external components. For more information about the kinds of SharePoint components that can be included in SharePoint Add-ins, see [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md).
     
  
 
-    For more detailed information about the hosting options of SharePoint Add-ins, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in).
+    For more detailed information about the hosting options of SharePoint Add-ins, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md).
     
  
 -  **Connectivity:** SharePoint supports three kinds of secure create/read/update/delete (CRUD) access to data.
     
-      - External web applications in an add-in use the OAuth protocol to access SharePoint data. For more information, see  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins).
+      - External web applications in an add-in use the OAuth protocol to access SharePoint data. For more information, see  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md).
     
  
-  - JavaScript can access data in a SharePoint add-in web and data on other websites within the same tenancy by using a special JavaScript library that enables secure cross-domain scripting. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+  - JavaScript can access data in a SharePoint add-in web and data on other websites within the same tenancy by using a special JavaScript library that enables secure cross-domain scripting. For more information, see  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
     
  
-  - A SharePoint Add-in can also access external data through Business Connectivity Services (BCS) or a web service proxy. For more information, see  [Business Connectivity Services in SharePoint](http://msdn.microsoft.com/library/64b7d032-4b83-4e9e-bc08-f0a161af5457%28Office.15%29.aspx) and [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013).
+  - A SharePoint Add-in can also access external data through Business Connectivity Services (BCS) or a web service proxy. For more information, see  [Business Connectivity Services in SharePoint](http://msdn.microsoft.com/library/64b7d032-4b83-4e9e-bc08-f0a161af5457%28Office.15%29.aspx) and [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md).
     
  
 
-    For more information on data storage and access in SharePoint Add-ins, see  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#Data),  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins), and  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013).
+    For more information on data storage and access in SharePoint Add-ins, see  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#Data.md),  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md), and  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md).
     
  
--  **UI:** There are three ways to surface a SharePoint Add-in in SharePoint: at a minimum, all add-ins are surfaced in a full web page. Optionally, an add-in can also be surfaced through an add-in part, and through a menu item or ribbon button. For more information, see [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins).
+-  **UI:** There are three ways to surface a SharePoint Add-in in SharePoint: at a minimum, all add-ins are surfaced in a full web page. Optionally, an add-in can also be surfaced through an add-in part, and through a menu item or ribbon button. For more information, see [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md).
     
-     **Note**  SharePoint Add-ins can be installed by your customers to multiple site collections in a tenancy, or on a website-by-website basis. The former are called tenant-scoped add-ins. If you want your customers to have the tenant-scoped option, you may not include a custom ribbon button or an add-in part. For more information, see  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins).
+     **Note**  SharePoint Add-ins can be installed by your customers to multiple site collections in a tenancy, or on a website-by-website basis. The former are called tenant-scoped add-ins. If you want your customers to have the tenant-scoped option, you may not include a custom ribbon button or an add-in part. For more information, see  [Tenancies and deployment scopes for SharePoint Add-ins](tenancies-and-deployment-scopes-for-sharepoint-add-ins.md).
 
 ## Architectural tiers
 <a name="Tiers"> </a>
@@ -123,10 +129,10 @@ The SharePoint Add-in model enables so many possibilities for design that a simp
 <a name="AdditionalResources"> </a>
 
 
--  [Design SharePoint Add-ins](design-sharepoint-add-ins)
+-  [Design SharePoint Add-ins](design-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 
diff --git a/docs/sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins.md b/docs/sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins.md
index 364e68ac6a..06b1f5faab 100644
--- a/docs/sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Tools and environments for developing SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Tools and environments for developing SharePoint Add-ins
 Learn your options for creating a development environment for SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 There are two basic patterns for development environments for SharePoint Add-ins:
@@ -18,7 +24,7 @@ There are two basic patterns for development environments for SharePoint Add-ins
 Consider the following:
  
 
-- Almost any add-in you create can be deployed to either SharePoint Online or to on-premise SharePoint farms, regardless of which type of environment you use. As a general rule, add-ins that cannot be deployed to SharePoint Online also cannot be developed with it. Examples: add-ins that require  [Full Control permissions](add-in-permissions-in-sharepoint-2013) and add-ins that use the [high-trust authorization system](creating-sharepoint-add-ins-that-use-high-trust-authorization).
+- Almost any add-in you create can be deployed to either SharePoint Online or to on-premise SharePoint farms, regardless of which type of environment you use. As a general rule, add-ins that cannot be deployed to SharePoint Online also cannot be developed with it. Examples: add-ins that require  [Full Control permissions](add-in-permissions-in-sharepoint.md) and add-ins that use the [high-trust authorization system](creating-sharepoint-add-ins-that-use-high-trust-authorization.md).
     
  
 - You can develop both SharePoint-hosted and provider-hosted SharePoint Add-ins, regardless of which type of environment you use.
@@ -30,19 +36,19 @@ Consider the following:
 - All things considered, the two options are equally easy to set up.
     
  
- **To create the SharePoint Online environment** using an SharePoint Online subscription that you can use for development, see [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription).
+ **To create the SharePoint Online environment** using an SharePoint Online subscription that you can use for development, see [Create a developer site on an existing Office 365 subscription](create-a-developer-site-on-an-existing-office-365-subscription.md).
  
- **To create the on-premise environment**, see [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins).
+ **To create the on-premise environment**, see [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md).
  
 
- **Note**  This topic is only concerned with environments for developing SharePoint Add-ins. If you plan to develop farm solutions, see  [Set up a general development environment for SharePoint](http://msdn.microsoft.com/library/08e4e4e1-d960-43fa-85df-f3c279ed6927%28Office.15%29.aspx). If you plan to do both kinds of development, start with the latter article, and then see  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins) for additional steps you need to develop SharePoint Add-ins.
+ **Note**  This topic is only concerned with environments for developing SharePoint Add-ins. If you plan to develop farm solutions, see  [Set up a general development environment for SharePoint](http://msdn.microsoft.com/library/08e4e4e1-d960-43fa-85df-f3c279ed6927%28Office.15%29.aspx). If you plan to do both kinds of development, start with the latter article, and then see  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md) for additional steps you need to develop SharePoint Add-ins.
  
 
 
 ## Other tooling information
 
  
--  [Create SharePoint Add-ins in Visual Studio](create-sharepoint-add-ins-in-visual-studio)
+-  [Create SharePoint Add-ins in Visual Studio](create-sharepoint-add-ins-in-visual-studio.md)
     
  
 
@@ -50,7 +56,7 @@ Consider the following:
 <a name="bk_addresources"> </a>
 
 
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/troubleshooting-document-libraries.md b/docs/sp-add-ins/troubleshooting-document-libraries.md
index 4e6d62c67c..9ef227def5 100644
--- a/docs/sp-add-ins/troubleshooting-document-libraries.md
+++ b/docs/sp-add-ins/troubleshooting-document-libraries.md
@@ -1,9 +1,15 @@
+---
+title: Troubleshooting document libraries
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Troubleshooting document libraries
 In this topic, you can learn about problems that may occur when you access a SharePoint document library from a cloud business add-in and the techniques that you can use to resolve those problems.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -28,7 +34,7 @@ When attempting to upload a document to an associated document library in a clou
 
  
 
-  ![Selections in the Manage NuGet Packages dialog box](../../images/NuGet.PNG)
+  ![Selections in the Manage NuGet Packages dialog box](../images/NuGet.PNG)
  
 
  
@@ -53,7 +59,7 @@ When attempting to upload a document to an associated document library in a clou
 <a name="bk_addresources"> </a>
 
 
--  [Associate a document library with an entity](associate-a-document-library-with-an-entity)
+-  [Associate a document library with an entity](associate-a-document-library-with-an-entity.md)
     
  
 
diff --git a/docs/sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins.md b/docs/sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins.md
index f78d17c1c6..2163206608 100644
--- a/docs/sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Troubleshooting high-trust SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Troubleshooting high-trust SharePoint Add-ins
 Get some help with problems developing high-trust SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 This article describes the Fiddler tool and also provides some guidance for resolving some specific issues.
@@ -96,7 +102,7 @@ Your first step in troubleshooting the issue is to use the Visual Studio debugge
 - Your web application is accepting anonymous requests. This means there is not a real user identity in the access token. Ensure that anonymous access has been disabled in IIS for the root directory of your remote web application. You can also check this by debugging your remote web application, and checking the value of  **Request.LogonUserIdentity** in the default.aspx.cs (or .vb) file to ensure that it's not an anonymous user.
     
  
-- Your digital certificate was not added to the trusted certificate store. Be sure you have followed the procedures in  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins).
+- Your digital certificate was not added to the trusted certificate store. Be sure you have followed the procedures in  [Package and publish high-trust SharePoint Add-ins](package-and-publish-high-trust-sharepoint-add-ins.md).
     
  
 
diff --git a/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md b/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md
index 2a4aa392a1..7f22c4f2cc 100644
--- a/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md
+++ b/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md
@@ -1,20 +1,25 @@
+---
+title: Update add-in web components in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 # Update add-in web components in SharePoint
 Update pages, lists, content types, and other add-in web components in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites for updating the add-in web components
 <a name="Prerequisites"> </a>
 
-Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins) and the prerequisites and core concepts included in it.
+Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins.md) and the prerequisites and core concepts included in it.
  
 
  
-This topic assumes that you have developed and tested the latest version of the add-in as described in the  [Create and debug the new version as if it were a brand new add-in](update-sharepoint-add-ins#DebugFirst).
+This topic assumes that you have developed and tested the latest version of the add-in as described in the  [Create and debug the new version as if it were a brand new add-in](update-sharepoint-add-ins.md#DebugFirst).
  
 
  
@@ -29,11 +34,11 @@ All of the SharePoint components that are deployed to the add-in web are contain
 
 ### What can and cannot be done declaratively
 
-With a SharePoint-hosted add-in, you can only use XML markup to update an add-in and there are some limits on how you can declaratively change an add-in in an update. In a provider-hosted add-in, you can implement a  [UpdatedEventEndpoint handler](create-a-handler-for-the-update-event-in-sharepoint-add-ins) to do things that can't be done declaratively.
+With a SharePoint-hosted add-in, you can only use XML markup to update an add-in and there are some limits on how you can declaratively change an add-in in an update. In a provider-hosted add-in, you can implement a  [UpdatedEventEndpoint handler](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md) to do things that can't be done declaratively.
  
 
  
-Adding components to an add-in is easy. Any component that is eligible to be included in an add-in can also be added in an update. (For details about what components can be in an add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013#TypesOfSPComponentsInApps). ) But when you want to modify an existing component declaratively, consider the following points. 
+Adding components to an add-in is easy. Any component that is eligible to be included in an add-in can also be added in an update. (For details about what components can be in an add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps). ) But when you want to modify an existing component declaratively, consider the following points. 
  
 
  
@@ -83,7 +88,7 @@ The Microsoft Office Developer Tools for Visual Studio are oriented to creating
 
  
 
-  ![Steps to open the Feature XML editor](../../images/UpdateAppOpenFeatureXML.png)
+  ![Steps to open the Feature XML editor](../images/UpdateAppOpenFeatureXML.png)
  
 
  
@@ -231,14 +236,14 @@ Use the following steps to update the add-in web Feature.
 </Module>
 ```
 
-3. Pages can have Web Parts embedded in them as explained in  [Include a Web Part in a webpage on the add-in web](include-a-web-part-in-a-webpage-on-the-add-in-web). If you change a page that has a Web Part on it (or change the properties of the Web Part), then there is an additional step: you have to add the following markup to the page to prevent the SharePoint from adding a second copy of the Web Part onto the page. The markup should be added to the  **asp:Content** element with the ID `PlaceHolderAdditionalPageHead`. (The Office Developer Tools for Visual Studio may have already added it when the page was first created, but you should verify that it is there.)
+3. Pages can have Web Parts embedded in them as explained in  [Include a Web Part in a webpage on the add-in web](include-a-web-part-in-a-webpage-on-the-add-in-web.md). If you change a page that has a Web Part on it (or change the properties of the Web Part), then there is an additional step: you have to add the following markup to the page to prevent the SharePoint from adding a second copy of the Web Part onto the page. The markup should be added to the  **asp:Content** element with the ID `PlaceHolderAdditionalPageHead`. (The Office Developer Tools for Visual Studio may have already added it when the page was first created, but you should verify that it is there.)
     
 ```XML
   <meta name="WebPartPageExpansion" content="full" />
 ```
 
 
-     **Note**   If the page was configured to allow users to customize it, then this markup has the side effect of removing those customizations. Users will have to repeat them. If the Web Part was added to the page following the guidance in [Include a Web Part in a webpage on the add-in web](include-a-web-part-in-a-webpage-on-the-add-in-web), then the Web Part markup is in the elements manifest, so changing the Web Part's properties is an exception to the general rule that you should not edit an element manifest file as part of an add-in update. 
+     **Note**   If the page was configured to allow users to customize it, then this markup has the side effect of removing those customizations. Users will have to repeat them. If the Web Part was added to the page following the guidance in [Include a Web Part in a webpage on the add-in web](include-a-web-part-in-a-webpage-on-the-add-in-web.md), then the Web Part markup is in the elements manifest, so changing the Web Part's properties is an exception to the general rule that you should not edit an element manifest file as part of an add-in update. 
 4. As an alternative to changing a page, you also have the option of using redirection to a new page using the following steps. 
     
       1. Create the new page and configure its update markup as described in the procedure  **To add components to the add-in** above.
@@ -416,18 +421,18 @@ Follow these steps to verify the deployment of the add-in web Feature and its co
 ## Next steps
 <a name="Next"> </a>
 
-Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
+Return to  [Major steps in updating an add-in](update-sharepoint-add-ins.md#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
  
 
  
 
--  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013)
+-  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md)
     
  
--  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins)
+-  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md)
     
  
--  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins)
+-  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md)
     
  
 
@@ -435,7 +440,7 @@ Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAp
 <a name="bk_addresources"> </a>
 
 
--  [Update SharePoint Add-ins](update-sharepoint-add-ins)
+-  [Update SharePoint Add-ins](update-sharepoint-add-ins.md)
     
  
 -  [How to: Add Elements to an Existing Feature](http://msdn.microsoft.com/library/b007f419-e0d6-4e3a-a3ae-b8e448656d02%28Office.15%29.aspx) in the Microsoft SharePoint 2010 Software Development Kit (SDK).
diff --git a/docs/sp-add-ins/update-host-web-components-in-sharepoint.md b/docs/sp-add-ins/update-host-web-components-in-sharepoint.md
index 3831d89f8d..6ee5ab1219 100644
--- a/docs/sp-add-ins/update-host-web-components-in-sharepoint.md
+++ b/docs/sp-add-ins/update-host-web-components-in-sharepoint.md
@@ -1,16 +1,22 @@
+---
+title: Update host web components in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Update host web components in SharePoint
 Update add-in parts and custom actions in the host web of a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites for updating host web components
 <a name="Prerequisites"> </a>
 
-Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins) and the prerequisites and core concepts listed in it.
+Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins.md) and the prerequisites and core concepts listed in it.
  
 
  
@@ -30,7 +36,7 @@ If you leave the  **Name** property unchanged, the old version remains on pages
  
 
  
-You can deploy other kinds of host web components programmatically using a remote event receiver that you register in the add-in manifest with an  [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) element. You should use an [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) receiver to update components that were originally deployed with an **InstalledEventEndpoint** receiver. [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) receivers are described in [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins).
+You can deploy other kinds of host web components programmatically using a remote event receiver that you register in the add-in manifest with an  [InstalledEventEndpoint](http://msdn.microsoft.com/library/af9f83d8-8325-3ede-d7b0-bb82c0445eb9%28Office.15%29.aspx) element. You should use an [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) receiver to update components that were originally deployed with an **InstalledEventEndpoint** receiver. [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) receivers are described in [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md).
  
 
  
@@ -38,18 +44,18 @@ You can deploy other kinds of host web components programmatically using a remot
 ## Next steps
 <a name="Next"> </a>
 
-Go to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
+Go to  [Major steps in updating an add-in](update-sharepoint-add-ins.md#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
  
 
  
 
--  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013)
+-  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md)
     
  
--  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins)
+-  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md)
     
  
--  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins)
+-  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md)
     
  
 
@@ -57,10 +63,10 @@ Go to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAppUpg
 <a name="bk_addresources"> </a>
 
 
--  [Update SharePoint Add-ins](update-sharepoint-add-ins)
+-  [Update SharePoint Add-ins](update-sharepoint-add-ins.md)
     
  
--  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)
+-  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)
     
  
 
diff --git a/docs/sp-add-ins/update-remote-components-in-sharepoint-add-ins.md b/docs/sp-add-ins/update-remote-components-in-sharepoint-add-ins.md
index 0c57e3626f..d2155db46e 100644
--- a/docs/sp-add-ins/update-remote-components-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/update-remote-components-in-sharepoint-add-ins.md
@@ -1,16 +1,22 @@
+---
+title: Update remote components in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Update remote components in SharePoint Add-ins
 Update the remote web applications and databases in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
 ## Prerequisites for updating the remote components of a SharePoint Add-in
 <a name="Prerequistes"> </a>
 
-Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins) and the prerequisites and core concepts listed in it.
+Be familiar with  [Update SharePoint Add-ins](update-sharepoint-add-ins.md) and the prerequisites and core concepts listed in it.
  
 
  
@@ -45,18 +51,18 @@ For a provider-hosted SharePoint Add-in that uses Microsoft Azure SQL Database o
 ## Next steps
 <a name="Next"> </a>
 
-Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
+Return to  [Major steps in updating an add-in](update-sharepoint-add-ins.md#MajorAppUpgradeSteps), or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.
  
 
  
 
--  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013)
+-  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md)
     
  
--  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013)
+-  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md)
     
  
--  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins)
+-  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md)
     
  
 
@@ -64,10 +70,10 @@ Return to  [Major steps in updating an add-in](update-sharepoint-add-ins#MajorAp
 <a name="bk_addresources"> </a>
 
 
--  [Update SharePoint Add-ins](update-sharepoint-add-ins)
+-  [Update SharePoint Add-ins](update-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins update process](sharepoint-add-ins-update-process)
+-  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md)
     
  
 
diff --git a/docs/sp-add-ins/update-sharepoint-add-ins.md b/docs/sp-add-ins/update-sharepoint-add-ins.md
index 4bafcb9ac3..73199aafbd 100644
--- a/docs/sp-add-ins/update-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/update-sharepoint-add-ins.md
@@ -1,9 +1,14 @@
+---
+title: Update SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 # Update SharePoint Add-ins
 Learn how to create and deploy an update for a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can update your SharePoint Add-in by using the updating support built into SharePoint. Within 24 hours after you upload an updated version of the add-in to the organization's add-in catalog or the add-in is accepted at the Office Store, a notification that an update is available appears next to the add-in on  **Site Contents** page of every website where it is installed. As you can see in Figure 1, a link is provided for users to immediately install the update.
@@ -14,13 +19,13 @@ You can update your SharePoint Add-in by using the updating support built into S
  
 
  
-![The UI steps for updating an app](../../images/UpdatingApp_AppTileUpdateNotice.png)
+![The UI steps for updating an app](../images/UpdatingApp_AppTileUpdateNotice.png)
  
 A user can install the update without first uninstalling the earlier version. The update infrastructure tests the update installation and rolls it back if there are any errors.
  
 
     
- **Important**  You cannot change the  *add-in type*  using the update system. For example, you cannot change an add-in from SharePoint-hosted to provider-hosted with an update. To make a change of type, you need to [migrate from an old add-in to a new one](sharepoint-add-ins-update-process#Major). In particular, since  [the preview program for autohosted add-ins has been closed](http://blogs.office.com/2014/05/16/update-on-autohosted-apps-preview-program/), you should be aware that you cannot update an autohosted add-in to a provider-hosted add-in. You have to convert the add-in as explained in  [Convert an autohosted SharePoint Add-in to a provider-hosted add-in](convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in).
+ **Important**  You cannot change the  *add-in type*  using the update system. For example, you cannot change an add-in from SharePoint-hosted to provider-hosted with an update. To make a change of type, you need to [migrate from an old add-in to a new one](sharepoint-add-ins-update-process.md#Major). In particular, since  [the preview program for autohosted add-ins has been closed](http://blogs.office.com/2014/05/16/update-on-autohosted-apps-preview-program/.md), you should be aware that you cannot update an autohosted add-in to a provider-hosted add-in. You have to convert the add-in as explained in  [Convert an autohosted SharePoint Add-in to a provider-hosted add-in](convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md).
  
 
 
@@ -32,7 +37,7 @@ A user can install the update without first uninstalling the earlier version. Th
 
  
 
-- A test SharePoint installation that is configured for add-in isolation. See  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365) for instructions on how to set up an Office 365 Developer Site.
+- A test SharePoint installation that is configured for add-in isolation. See  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md) for instructions on how to set up an Office 365 Developer Site.
     
  
 - Tools that are used in creating a SharePoint Add-in are usually also used in updating it. For example, most developers use Visual Studio and Microsoft Office Developer Tools for Visual Studio to create SharePoint Add-ins.
@@ -51,11 +56,11 @@ A user can install the update without first uninstalling the earlier version. Th
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in)|Learn about the different types of SharePoint Add-ins. The updating process varies depending on the type.|
-| [SharePoint Add-ins update process](sharepoint-add-ins-update-process)|Learn about the process for updating SharePoint Add-ins.|
+| [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md)|Learn about the different types of SharePoint Add-ins. The updating process varies depending on the type.|
+| [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md)|Learn about the process for updating SharePoint Add-ins.|
 | [Upgrading Features](http://msdn.microsoft.com/library/e917f709-6491-4d50-adbe-2ab8f35da990%28Office.15%29.aspx)|Learn how to update Features (SharePoint 2010 SDK).|
-| [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options)|Learn about the methods for publishing, installing, and uninstalling a SharePoint Add-in.|
-| [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins)|Learn about remote event receivers in SharePoint.|
+| [Deploying and installing SharePoint Add-ins: methods and options](deploying-and-installing-sharepoint-add-ins-methods-and-options.md)|Learn about the methods for publishing, installing, and uninstalling a SharePoint Add-in.|
+| [Handle events in SharePoint Add-ins](handle-events-in-sharepoint-add-ins.md)|Learn about remote event receivers in SharePoint.|
 
 ## Major steps in updating an add-in
 <a name="MajorAppUpgradeSteps"> </a>
@@ -80,13 +85,13 @@ The following are the major steps that may be needed when you create an update f
     For more information, see  [Update the add-in version, permission requests, and prerequisites](#UpdateManifest).
     
  
-- Add or update the markup for add-in web components. For more information, see  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013).
+- Add or update the markup for add-in web components. For more information, see  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md).
     
  
-- Add or update the markup for host web components. For more information, see  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013).
+- Add or update the markup for host web components. For more information, see  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md).
     
  
-- Add custom logic to an  [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) and register it in the appmanifest.xml file. For more information, see [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins).
+- Add custom logic to an  [UpgradedEventEndpoint](http://msdn.microsoft.com/library/09a93d44-d295-47bb-f91c-d243178b0f53%28Office.15%29.aspx) and register it in the appmanifest.xml file. For more information, see [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md).
     
  
 - Update the remote components:
@@ -95,7 +100,7 @@ The following are the major steps that may be needed when you create an update f
     
  
 
-    For more information, see  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins).
+    For more information, see  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md).
     
  
 -  ***** Upload the add-in package to the Office Store or the organization's add-in catalog.
@@ -143,7 +148,7 @@ When the new version of the add-in is functioning correctly as a "new" add-in, r
  
 
  
-When you are ready to test your update, retract the new version from the test site and redeploy the earlier version so you can test update logic. If you have shipped multiple previous versions of the add-in, install each earlier version on a different subweb of your test site. Then upload the latest version of the add-in to your test site's add-in catalog and update every instance of the add-in. Verify that each has the latest add-in version number and the latest version of all components. If there is an add-in web in the add-in, verify that the add-in web components have been deployed using the procedure in  [Verify deployment of add-in web components](update-add-in-web-components-in-sharepoint-2013#VerifyDeployAppWebComp).
+When you are ready to test your update, retract the new version from the test site and redeploy the earlier version so you can test update logic. If you have shipped multiple previous versions of the add-in, install each earlier version on a different subweb of your test site. Then upload the latest version of the add-in to your test site's add-in catalog and update every instance of the add-in. Verify that each has the latest add-in version number and the latest version of all components. If there is an add-in web in the add-in, verify that the add-in web components have been deployed using the procedure in  [Verify deployment of add-in web components](update-add-in-web-components-in-sharepoint.md#VerifyDeployAppWebComp).
  
 
  
@@ -178,11 +183,11 @@ Figure 2 illustrates these steps.
  
 
  
-![Immediate app upgrade process](../../images/UpdatingApp_ImmediateUpgradeProcess.png)
+![Immediate app upgrade process](../images/UpdatingApp_ImmediateUpgradeProcess.png)
  
 
     
- **Note**  If you need to see the "update available" notice on the add-in's tile more frequently than every 24 hours, you can use the method described in  [Update process for a SharePoint Add-in](sharepoint-add-ins-update-process#Minor) to make the notice appear immediately.
+ **Note**  If you need to see the "update available" notice on the add-in's tile more frequently than every 24 hours, you can use the method described in  [Update process for a SharePoint Add-in](sharepoint-add-ins-update-process.md#Minor) to make the notice appear immediately.
  
 
 
@@ -210,16 +215,16 @@ Continue with the next bullet in the section  [Major steps in updating an add-in
 
  
 
--  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint-2013)
+-  [Update add-in web components in SharePoint](update-add-in-web-components-in-sharepoint.md)
     
  
--  [Update host web components in SharePoint](update-host-web-components-in-sharepoint-2013)
+-  [Update host web components in SharePoint](update-host-web-components-in-sharepoint.md)
     
  
--  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins)
+-  [Create a handler for the update event in SharePoint Add-ins](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md)
     
  
--  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins)
+-  [Update remote components in SharePoint Add-ins](update-remote-components-in-sharepoint-add-ins.md)
     
  
 
@@ -227,10 +232,10 @@ Continue with the next bullet in the section  [Major steps in updating an add-in
 <a name="bk_addresources"> </a>
 
 
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins update process](sharepoint-add-ins-update-process)
+-  [SharePoint Add-ins update process](sharepoint-add-ins-update-process.md)
     
  
 
diff --git a/docs/sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery.md b/docs/sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery.md
index 7c46550bad..fdd27db2f3 100644
--- a/docs/sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery.md
+++ b/docs/sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery.md
@@ -1,9 +1,15 @@
+---
+title: Upload a file by using the REST API and jQuery
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Upload a file by using the REST API and jQuery
 Learn how to upload a local file to a SharePoint folder by using the REST API and jQuery AJAX requests.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 The code examples in this article use the REST interface and jQuery AJAX requests to add a local file to the  **Documents** library and then change properties of the list item that represents the uploaded file.
@@ -75,7 +81,7 @@ The following code example uses the SharePoint REST API and jQuery AJAX requests
  
 
  
-You need to meet  [these requirements](upload-a-file-by-using-the-rest-api-and-jquery#RunTheExamples) to use this example.
+You need to meet  [these requirements](upload-a-file-by-using-the-rest-api-and-jquery.md#RunTheExamples) to use this example.
  
 
  
@@ -255,7 +261,7 @@ The following code example uses the SharePoint REST API and jQuery AJAX requests
  
 
  
-You need to meet  [these requirements](upload-a-file-by-using-the-rest-api-and-jquery#RunTheExamples) before you can run this example.
+You need to meet  [these requirements](upload-a-file-by-using-the-rest-api-and-jquery.md#RunTheExamples) before you can run this example.
  
 
  
@@ -404,19 +410,19 @@ function onError(error) {
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
 -  [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)
     
  
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
 
diff --git a/docs/sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins.md b/docs/sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins.md
index 4366bf2923..7dad31a6b7 100644
--- a/docs/sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: URL strings and tokens in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # URL strings and tokens in SharePoint Add-ins
 Learn which URL tokens are available for use in SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
diff --git a/docs/sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md b/docs/sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md
index 9d68327bab..6eccadd616 100644
--- a/docs/sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Use a SharePoint website's style sheet in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use a SharePoint website's style sheet in SharePoint Add-ins
 Learn how to use a SharePoint website's style sheet in a SharePoint Add-in.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 You can reference the style sheet of a SharePoint website in your SharePoint Add-in and use it to style your webpages by using the style sheet in SharePoint. In addition, if someone changes the SharePoint website's style sheet or theme, you can adopt the new set of styles in your add-in without modifying the style sheet reference in your add-in.
@@ -16,7 +22,7 @@ You can reference the style sheet of a SharePoint website in your SharePoint Add
 ## Prerequisites for using the examples in this article
 <a name="SP15Usestylesheetcontrol_Prereq"> </a>
 
-You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+You need a development environment as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
  
@@ -33,9 +39,9 @@ The following table lists useful articles that can help you understand the conce
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)|Learn about the user experience (UX) options and alternatives that you have when building SharePoint Add-ins.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)|Learn about the user experience (UX) options and alternatives that you have when building SharePoint Add-ins.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the difference between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 
 ## Code example: Use a SharePoint website's style sheet in a SharePoint Add-in
 <a name="SP15Usestylesheetcontrol_Example"> </a>
@@ -71,7 +77,7 @@ Figure 1 shows a SharePoint webpage that is using the style sheet.
  
 
  
-![A web page using the stylesheet control](../../images/StylesheetControl_result.png)
+![A web page using the stylesheet control](../images/StylesheetControl_result.png)
  
 
 ### To create the SharePoint Add-in and remote web projects
@@ -80,7 +86,7 @@ Figure 1 shows a SharePoint webpage that is using the style sheet.
 1. Open Visual Studio as administrator. (To do this, right-click the Visual Studio icon on the  **Start** menu, and choose **Run as administrator**.)
     
  
-2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins) and name itStylesheetAdd-in. 
+2. Create the provider-hosted SharePoint Add-in as explained in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md) and name itStylesheetAdd-in. 
     
  
 
@@ -248,7 +254,7 @@ Figure 1 shows a SharePoint webpage that is using the style sheet.
 
  
 
-  ![Stylesheet control used in a web page](../../images/StylesheetControl_result2.png)
+  ![Stylesheet control used in a web page](../images/StylesheetControl_result2.png)
  
 
  
@@ -274,16 +280,16 @@ This article demonstrated how to use the style sheet in a SharePoint Add-in. As
 
  
 
--  [Code sample: Use the SharePoint style sheet in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-7a8684e2)
+-  [Code sample: Use the SharePoint style sheet in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-7a8684e2)
     
  
--  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)
+-  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)
     
  
--  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)
+-  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
 
@@ -291,19 +297,19 @@ This article demonstrated how to use the style sheet in a SharePoint Add-in. As
 <a name="SP15Usestylesheetcontrol_Addresources"> </a>
 
 
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines)
+-  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 
diff --git a/docs/sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md b/docs/sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md
index 885a657667..ed2df924bd 100644
--- a/docs/sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md
+++ b/docs/sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md
@@ -1,9 +1,15 @@
+---
+title: Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site
 Use an Office 365 SharePoint site to create an environment where you can use ACS to establish trust between a provider-hosted add-in and an on-premises SharePoint farm, just as you would if you were developing add-ins for an Office 365 SharePoint site.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -15,10 +21,10 @@ Be sure that you have the following.
 
  
 
-- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins).
+- An on-premises SharePoint development environment. See  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md).
     
  
-- An Office 365 SharePoint site. If don't have one yet and you want to set up a development environment quickly, you can  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365).
+- An Office 365 SharePoint site. If don't have one yet and you want to set up a development environment quickly, you can  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md).
     
  
 -  [Visual Studio 2012](https://www.microsoft.com/en-us/download/details.aspx?id=30682) installed either remotely or on the computer where you installed SharePoint.
@@ -62,7 +68,7 @@ You'll need to replace the default security token service (STS) certificate of y
 
  
 
-  ![Server Certificates option in IIS](../../images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif)
+  ![Server Certificates option in IIS](../images/e38f9b7f-59a3-468c-bcde-a48272f1f217.gif)
  
 
  
@@ -74,7 +80,7 @@ You'll need to replace the default security token service (STS) certificate of y
 
  
 
-  ![Create Self-Signed Cerificate link](../../images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif)
+  ![Create Self-Signed Cerificate link](../images/3f0aae5a-e58b-4ec8-b67f-0024abfa2dab.gif)
  
 
  
@@ -89,7 +95,7 @@ You'll need to replace the default security token service (STS) certificate of y
 
  
 
-  ![Exporting a test certificate](../../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
+  ![Exporting a test certificate](../images/997021de-c60c-46b0-961f-7e1e63c0f619.gif)
  
 
  
@@ -122,7 +128,7 @@ Set-SPSecurityTokenServiceConfig -ImportSigningCertificate $stsCertificate -conf
 ```
 
 
- **Note**  The  [Configure a one-way hybrid environment with SharePoint Server 2013 and Office 365](http://download.microsoft.com/download/6/4/4/644BA525-96CB-4739-B08F-18949A9BDADC/sps-2013-config-one-way-hybrid-environment.docx) document that is available for download on the [SharePoint hybrid resources page](http://www.microsoft.com/en-us/download/details.aspx?id=35593) explains in greater detail how to replace the default STS certificate of your on-premises farm with a certificate from a well-known certification authority or a self-signed certificate.
+ **Note**  The  [Configure a one-way hybrid environment with SharePoint Server 2013 and Office 365](http://download.microsoft.com/download/6/4/4/644BA525-96CB-4739-B08F-18949A9BDADC/sps-config-one-way-hybrid-environment.docx) document that is available for download on the [SharePoint hybrid resources page](http://www.microsoft.com/en-us/download/details.aspx?id=35593) explains in greater detail how to replace the default STS certificate of your on-premises farm with a certificate from a well-known certification authority or a self-signed certificate.
  
 
 
@@ -139,7 +145,7 @@ Figure 4 shows the four steps to enable the connections you need within the over
  
 
  
-![Make ACS work with an on-premises installation of SharePoint by using an Office 365 site](../../images/SP15_OnPremACSArchitecture.png)
+![Make ACS work with an on-premises installation of SharePoint by using an Office 365 site](../images/SP15_OnPremACSArchitecture.png)
  
 
  
@@ -462,7 +468,7 @@ Get-SPWebApplication | ForEach-Object {
 ## Next Steps
 <a name="CreateApp"> </a>
 
-Follow the steps in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins) to create a simple "hello world" provider-hosted add-in that uses ACS as the token issuer.
+Follow the steps in  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md) to create a simple "hello world" provider-hosted add-in that uses ACS as the token issuer.
  
 
  
@@ -471,6 +477,6 @@ Follow the steps in  [Get started creating provider-hosted SharePoint Add-ins](g
 <a name="bk_addresources"> </a>
 
 
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
diff --git a/docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md b/docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md
index 50099c85f2..5d96f5ff95 100644
--- a/docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md
+++ b/docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md
@@ -1,27 +1,33 @@
+---
+title: Use OData query operations in SharePoint REST requests
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use OData query operations in SharePoint REST requests
 Learn how to use a wide range of OData query string operators to select, filter, and order the data you request from the SharePoint REST service. 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
  **Before you start**
  
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)
+-  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)
     
  
--  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris)
+-  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md)
     
  
 The SharePoint REST service supports a wide range of OData query string operators that enable you to select, filter, and order the data you request.
  
 
- **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis).
+ **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md).
  
 
 
@@ -138,7 +144,7 @@ The figure below shows the supported OData query options.
  
 
  
-![SharePoint REST service query option syntax](../../images/SPF15Con_REST_queryOptionSyntax.png)
+![SharePoint REST service query option syntax](../images/SPF15Con_REST_queryOptionSyntax.png)
  
 
  
@@ -149,22 +155,22 @@ The figure below shows the supported OData query options.
 <a name="bk_addresources"> </a>
 
 
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service)
+-  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
     
  
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
--  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service)
+-  [Navigate the SharePoint data structure represented in the REST service](navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md)
     
  
--  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris)
+-  [Determine SharePoint REST service endpoint URIs](determine-sharepoint-rest-service-endpoint-uris.md)
     
  
 -  [REST API reference and samples](http://msdn.microsoft.com/library/rest-api-reference-and-samples%28Office.15%29.aspx)
diff --git a/docs/sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins.md b/docs/sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins.md
index c61a36ab44..1dcae30ad5 100644
--- a/docs/sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: Use the client chrome control in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use the client chrome control in SharePoint Add-ins
 Learn how to use the chrome control in add-ins in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 The chrome control in SharePoint enables you to use the header styling of a specific SharePoint site in your add-in without needing to register a server library or use a specific technology or tool. To use this functionality, you must register a SharePoint JavaScript library through a standard <script> tag. You can provide a placeholder by using an HTML **div** element and further customize the control by using the available options. The control inherits its appearance from the specified SharePoint website.
@@ -40,14 +46,14 @@ The following table lists useful articles that can help you understand the conce
 
 |**Article title**|**Description**|
 |:-----|:-----|
-| [SharePoint Add-ins](sharepoint-add-ins)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
-| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)|Learn about the user experience (UX) options and alternatives that you have when building SharePoint Add-ins.|
-| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)|Learn about the distinction between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
+| [SharePoint Add-ins](sharepoint-add-ins.md)|Learn about the new add-in model in SharePoint that enables you to create add-ins, which are small, easy-to-use solutions for end users.|
+| [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)|Learn about the user experience (UX) options and alternatives that you have when building SharePoint Add-ins.|
+| [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)|Learn about the distinction between host webs and add-in webs. Find out which SharePoint components can be included in a SharePoint Add-in, which components are deployed to the host web, which components are deployed to the add-in web, and how the add-in web is deployed in an isolated domain.|
 
 ## Code example: Use the chrome control in your cloud-hosted add-in
 <a name="SP15Usechromecontrol_Codeexample"> </a>
 
-A cloud-hosted add-in includes at least one remote component. For more information, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in). To use the chrome control in your cloud-hosted add-in, follow these steps:
+A cloud-hosted add-in includes at least one remote component. For more information, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md). To use the chrome control in your cloud-hosted add-in, follow these steps:
  
 
  
@@ -71,7 +77,7 @@ Figure 1 shows a remote webpage with the chrome control.
  
 
  
-![A remote web page with the chrome control](../../images/ChromeControl_result.png)
+![A remote web page with the chrome control](../images/ChromeControl_result.png)
  
 
 ### To create the SharePoint Add-in and remote web projects
@@ -89,7 +95,7 @@ Figure 1 shows a remote webpage with the chrome control.
 
  
 
-  ![App for SharePoint Visual Studio template](../../images/AppForSharePointVSTemplate.PNG)
+  ![App for SharePoint Visual Studio template](../images/AppForSharePointVSTemplate.PNG)
  
 
  
@@ -107,7 +113,7 @@ Figure 1 shows a remote webpage with the chrome control.
 
  
 
-  ![App for SharePoint projects in Solution Explorer](../../images/AppVSTemplateSolutionExplorer.jpg)
+  ![App for SharePoint projects in Solution Explorer](../images/AppVSTemplateSolutionExplorer.jpg)
  
 
  
@@ -126,7 +132,7 @@ Figure 1 shows a remote webpage with the chrome control.
 
  
 
-  ![Manifest editor with query string parameters](../../images/ChromeControl_manifest.PNG)
+  ![Manifest editor with query string parameters](../images/ChromeControl_manifest.PNG)
  
 
     The chrome control automatically takes the following values from the query string:
@@ -433,7 +439,7 @@ function getQueryStringParameter(paramToRetrieve) {
 
  
 
-  ![SharePoint website stylesheet used in a page](../../images/ChromControl_stylesheet.png)
+  ![SharePoint website stylesheet used in a page](../images/ChromControl_stylesheet.png)
  
 
  
@@ -457,22 +463,22 @@ This article demonstrated how to use the chrome control in a SharePoint Add-in.
 
  
 
--  [Code sample: Use the chrome control in a cloud-hosted add-in](http://code.msdn.microsoft.com/SharePoint-2013-Work-with-089ecc6f)
+-  [Code sample: Use the chrome control in a cloud-hosted add-in](http://code.msdn.microsoft.com/SharePoint-Work-with-089ecc6f)
     
  
--  [Code sample: Use the chrome control and the cross-domain library (CSOM)](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-97c30a2e)
+-  [Code sample: Use the chrome control and the cross-domain library (CSOM)](http://code.msdn.microsoft.com/SharePoint-Use-the-97c30a2e)
     
  
--  [Code sample: Use the chrome control and the cross-domain library (REST)](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-a759e9f8)
+-  [Code sample: Use the chrome control and the cross-domain library (REST)](http://code.msdn.microsoft.com/SharePoint-Use-the-a759e9f8)
     
  
--  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)
+-  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)
     
  
--  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)
+-  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
 
@@ -480,22 +486,22 @@ This article demonstrated how to use the chrome control in a SharePoint Add-in.
 <a name="SP15Usechromecontrol_Addresources"> </a>
 
 
--  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins)
+-  [Set up an on-premises development environment for SharePoint Add-ins](set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md)
     
  
--  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins)
+-  [UX design for SharePoint Add-ins](ux-design-for-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines)
+-  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
 
diff --git a/docs/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md b/docs/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md
index bafe40ec3f..2c0716b1f3 100644
--- a/docs/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md
+++ b/docs/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md
@@ -1,13 +1,19 @@
+---
+title: Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins
 Learn how to use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Important**  This topic assumes that you know how to create a SharePoint-hosted SharePoint Add-in. To learn how to create one, start at  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins).
+ **Important**  This topic assumes that you know how to create a SharePoint-hosted SharePoint Add-in. To learn how to create one, start at  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md).
  
 
 
@@ -52,7 +58,7 @@ This article assumes that you create the SharePoint Add-in by using Napa on an O
 
  
 
- **Note**  Go to  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365) to find out how to sign up for a Developer Site and start using Napa.
+ **Note**  Go to  [Set up a development environment for SharePoint Add-ins on Office 365](set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md) to find out how to sign up for a Developer Site and start using Napa.
  
 
 If you're not using Napa on a Developer Site, you'll need the following:
@@ -73,7 +79,7 @@ If you're not using Napa on a Developer Site, you'll need the following:
  **Note**  For guidance about how to set up a development environment that fits your needs, see  [Start building Office and SharePoint Add-ins](http://msdn.microsoft.com/library/187f8c8c-1b15-471c-80b5-69a40e67deea.aspx).
  
 
-The following steps describe the high-level steps for adding the picker to your add-in and then getting its user information from another client-side control. See  [Code example: Using the client-side People Picker](use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-ins#bk_example) for the corresponding code.
+The following steps describe the high-level steps for adding the picker to your add-in and then getting its user information from another client-side control. See  [Code example: Using the client-side People Picker](use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md#bk_example) for the corresponding code.
  
 
  
@@ -246,7 +252,7 @@ function onFail(sender, args) {
 <a name="bk_addresources"> </a>
 
 
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
 -  [People Picker and claims providers overview (SharePoint)](http://technet.microsoft.com/library/gg602078.aspx)
diff --git a/docs/sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md b/docs/sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md
index 8dba279fa3..7af8f03796 100644
--- a/docs/sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md
@@ -1,14 +1,20 @@
+---
+title: Use the experimental Desktop List View widget in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 
 # Use the experimental Desktop List View widget in SharePoint Add-ins
 Learn how to use the Desktop List View widget on any web page, even if the page is not hosted in SharePoint. Use the List View widget in your add-ins to display data in lists that are hosted in a SharePoint site.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Note**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms).
+ **Note**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md).
  
 
 
@@ -21,7 +27,7 @@ You can use the List View widget to display the data in a SharePoint list simila
  
 
  
-![Desktop List View experimental control on a page](../../images/DesktopListView_basic.png)
+![Desktop List View experimental control on a page](../images/DesktopListView_basic.png)
  
 
  
@@ -331,7 +337,7 @@ Office.Controls.Runtime.initialize({});
 3. Choose the add-in icon on the  **Site Contents** page.
     
  
-You can also download this sample from code gallery, see the  [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-c3edb076) code sample.
+You can also download this sample from code gallery, see the  [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-c3edb076) code sample.
  
 
  
@@ -368,7 +374,7 @@ new Office.Controls.ListView(
     });
 ```
 
-For an example that shows how to perform the tasks, see the  **JSSimple.html** page in the [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-c3edb076) code sample.
+For an example that shows how to perform the tasks, see the  **JSSimple.html** page in the [Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-c3edb076) code sample.
  
 
  
@@ -423,19 +429,19 @@ You can use the experimental Desktop List View widget to display data in SharePo
 <a name="bk_addresources"> </a>
 
 
--  [Office Web Widgets - Experimental overview](office-web-widgets--experimental-overview)
+-  [Office Web Widgets - Experimental overview](office-web-widgetsexperimental-overview.md)
     
  
--  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms)
+-  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md)
     
  
 -  [Office Web Widgets - Experimental NuGet gallery page](http://www.nuget.org/packages/Microsoft.Office.WebWidgets.Experimental/)
     
  
--  [Code sample: Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-c3edb076)
+-  [Code sample: Use the Desktop List View experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-c3edb076)
     
  
--  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins)
+-  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md b/docs/sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md
index 40a926c4d4..fb960b6984 100644
--- a/docs/sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md
@@ -1,13 +1,19 @@
+---
+title: Use the experimental People Picker widget in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use the experimental People Picker widget in SharePoint Add-ins
 Learn how to use the People Picker widget on any web page, even if the page is not hosted in SharePoint. Use the People Picker widget in your add-ins to help users find and select people and groups.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Caution**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms).
+ **Caution**  The Office Web Widgets - Experimental are only provided for research and feedback purposes. Do not use in production scenarios. The Office Web Widgets behavior may change significantly in future releases. Read and review the  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md).
  
 
 
@@ -20,7 +26,7 @@ You can use the experimental People Picker widget in add-ins to help your users
  
 
  
-![People Picker experimental control on a page](../../images/PeoplePicker_basic.png)
+![People Picker experimental control on a page](../images/PeoplePicker_basic.png)
  
 
  
@@ -68,7 +74,7 @@ To use the examples in this article, you need the following:
 
 ## Use the People Picker widget in a provider-hosted SharePoint Add-in
 
-In this example, there is a simple page hosted outside of SharePoint that declares a People Picker widget using markup. To keep things simple, this example doesn't declare any options, but you can see an example with options in the  [NextSteps](use-the-experimental-people-picker-widget-in-sharepoint-add-ins#NextSteps) section.
+In this example, there is a simple page hosted outside of SharePoint that declares a People Picker widget using markup. To keep things simple, this example doesn't declare any options, but you can see an example with options in the  [NextSteps](use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md#NextSteps) section.
  
 
  
@@ -264,7 +270,7 @@ Office.Controls.Runtime.initialize({});
 3. Choose the add-in icon on the  **Site Contents** page.
     
  
-You can also download this sample from code gallery, see the  [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85) code sample.
+You can also download this sample from code gallery, see the  [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85) code sample.
  
 
  
@@ -300,7 +306,7 @@ new Office.Controls.PeoplePicker(
     document.getElementById("PeoplePickerDiv"), {});
 ```
 
-For a code sample that shows how to perform the tasks, see the  **JSSimple.html** page in the [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85) code sample.
+For a code sample that shows how to perform the tasks, see the  **JSSimple.html** page in the [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85) code sample.
  
 
  
@@ -346,7 +352,7 @@ You can also specify event handlers for the  **onChange**, **onAdded**, and **on
  
 
  
-For an example of how to specify options, see the  **MarkupOptions.html** and **JSOptions.html** pages in the [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85) code sample.
+For an example of how to specify options, see the  **MarkupOptions.html** and **JSOptions.html** pages in the [Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85) code sample.
  
 
  
@@ -399,7 +405,7 @@ var principal = pplPicker.selectedItems[i];
 $("#msg").text(principal.text + " is selected in the control.");
 ```
 
-For an example of how to retrieve the selected people or groups from the widget, see the  **demo.html** page of the [Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-2013-Office-Web-6d44aa9e) code sample.
+For an example of how to retrieve the selected people or groups from the widget, see the  **demo.html** page of the [Office Web Widgets - Experimental Demo](http://code.msdn.microsoft.com/SharePoint-Office-Web-6d44aa9e) code sample.
  
 
  
@@ -416,7 +422,7 @@ As a developer, you might want to customize the look &amp; feel of the widget. T
  
 
  
-![HTML hierarchy in the People Picker control](../../images/PeoplePicker_HTMLHierarchy.png)
+![HTML hierarchy in the People Picker control](../images/PeoplePicker_HTMLHierarchy.png)
  
 The widget defines many classes prefixed by  **office-peoplepicker**, which you can find and customize in the **Office.Controls.css** style sheet.
  
@@ -435,19 +441,19 @@ You can use the experimental People Picker widget to select people and groups in
 <a name="bk_addresources"> </a>
 
 
--  [Office Web Widgets - Experimental overview](office-web-widgets--experimental-overview)
+-  [Office Web Widgets - Experimental overview](office-web-widgetsexperimental-overview.md)
     
  
--  [Office Web Widgets - Experimental License Terms](office-web-widgets--experimental-license-terms)
+-  [Office Web Widgets - Experimental License Terms](office-web-widgetsexperimental-license-terms.md)
     
  
 -  [Office Web Widgets - Experimental NuGet gallery page](http://www.nuget.org/packages/Microsoft.Office.WebWidgets.Experimental/)
     
  
--  [Code sample: Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-2013-Use-the-57859f85).
+-  [Code sample: Use the People Picker experimental widget in an add-in](http://code.msdn.microsoft.com/SharePoint-Use-the-57859f85).
     
  
--  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins).
+-  [Use the experimental Desktop List View widget in SharePoint Add-ins](use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md).
     
  
 
diff --git a/docs/sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md b/docs/sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md
index 232122028a..161f0c8b94 100644
--- a/docs/sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md
+++ b/docs/sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md
@@ -1,39 +1,45 @@
+---
+title: Use the SharePoint JavaScript APIs to work with SharePoint data
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Use the SharePoint JavaScript APIs to work with SharePoint data
 Use the SharePoint JavaScript object model to work with SharePoint data from JavaScript on pages in the add-in web.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the 10th in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the 10th in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in)
+-  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md)
     
  
 
@@ -249,7 +255,7 @@ function onDeleteCompletedItemsFail(sender, args) {
 
  
 
-  ![The "New Employees in Seattle" list with the "Orientation Stage" column for two items set to Completed. There is a button labelled "Purge Completed Items" below the list.](../../images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG)
+  ![The "New Employees in Seattle" list with the "Orientation Stage" column for two items set to Completed. There is a button labelled "Purge Completed Items" below the list.](../images/e5e4eef8-a218-4797-aabc-c52adbd2d96d.PNG)
  
 
  
@@ -264,7 +270,7 @@ function onDeleteCompletedItemsFail(sender, args) {
 
  
 
-  ![The "New Employees in Seattle" list with two fewer items than before and none of them have "Orientation Stage" set to Completed.](../../images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG)
+  ![The "New Employees in Seattle" list with two fewer items than before and none of them have "Orientation Stage" set to Completed.](../images/a0330fad-1473-4fde-9df2-8be0b37df1a1.PNG)
  
 
  
@@ -280,7 +286,7 @@ function onDeleteCompletedItemsFail(sender, args) {
 ## 
 <a name="Nextsteps"> </a>
 
-In the next article in this series, you'll add JavaScript to a page on the add-in web that works with SharePoint data on the host web:  [Work with host web data from JavaScript in the add-in web](work-with-host-web-data-from-javascript-in-the-add-in-web).
+In the next article in this series, you'll add JavaScript to a page on the add-in web that works with SharePoint data on the host web:  [Work with host web data from JavaScript in the add-in web](work-with-host-web-data-from-javascript-in-the-add-in-web.md).
  
 
  
diff --git a/docs/sp-add-ins/ux-design-for-sharepoint-add-ins.md b/docs/sp-add-ins/ux-design-for-sharepoint-add-ins.md
index b3b692dc37..1a4bb4eb38 100644
--- a/docs/sp-add-ins/ux-design-for-sharepoint-add-ins.md
+++ b/docs/sp-add-ins/ux-design-for-sharepoint-add-ins.md
@@ -1,9 +1,15 @@
+---
+title: UX design for SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # UX design for SharePoint Add-ins
 Learn about the user experience (UX) options that you have when you build add-ins in SharePoint.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 As a developer, you should always give high priority to the user experience (UX) when you are creating add-ins. The model for SharePoint Add-ins offers many UX components and mechanisms that help you build a great user experience. The user experience in the add-in model is also flexible enough to let you use the techniques and platforms that best adapt to the needs of end users.
@@ -20,10 +26,10 @@ As the add-in developer, you have to know the architecture of your add-in. After
 - What can I use if I am creating a cloud-hosted add-in?
     
  
-- What can I use if I am creating a SharePoint-hosted add-in? For more information, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in).
+- What can I use if I am creating a SharePoint-hosted add-in? For more information, see  [Choose patterns for developing and hosting your SharePoint Add-in](choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md).
     
  
-- How can I connect my UX to the host web? For more information, see  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013).
+- How can I connect my UX to the host web? For more information, see  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md).
     
  
 The following diagram shows the main scenarios and options to consider when you are designing your add-in UX.
@@ -36,7 +42,7 @@ The following diagram shows the main scenarios and options to consider when you
  
 
  
-![App UX main scenarios](../../images/AppUX_landscape.png)
+![App UX main scenarios](../images/AppUX_landscape.png)
  
 In choosing your design, you should fundamentally consider which parts of your add-in are hosted in SharePoint and which are not. You should also consider how your add-in interacts with the host web.
  
@@ -55,20 +61,20 @@ The following UX resources are available for cloud-hosted add-ins in SharePoint:
 
  
 
--  **Chrome control:** Thechrome control enables you to use the navigation header of a specific SharePoint site in your add-in without needing to register a server library or use a specific technology or tool. To use this functionality, you must register a SharePoint JavaScript library through standard <script> tags. You can provide a placeholder by using an HTML **div** element and further customize the control by using the available options. The control inherits its appearance from the specified SharePoint website. For more information, see [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins).
+-  **Chrome control:** Thechrome control enables you to use the navigation header of a specific SharePoint site in your add-in without needing to register a server library or use a specific technology or tool. To use this functionality, you must register a SharePoint JavaScript library through standard <script> tags. You can provide a placeholder by using an HTML **div** element and further customize the control by using the available options. The control inherits its appearance from the specified SharePoint website. For more information, see [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md).
     
     **Watch the video: SharePoint chrome control**
 
  
 
  
-![Videos](../../images/mod_icon_video.png)
+![Videos](../images/mod_icon_video.png)
  
 
  
 
  
--  **Stylesheet:** You can reference a SharePoint website's style sheet in your SharePoint Add-in and use it to style your webpages using the available classes. In addition, if the end users change the SharePoint website's theme, your add-in can adopt the new set of styles without modifying the reference in your add-in. For more information, see [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins).
+-  **Stylesheet:** You can reference a SharePoint website's style sheet in your SharePoint Add-in and use it to style your webpages using the available classes. In addition, if the end users change the SharePoint website's theme, your add-in can adopt the new set of styles without modifying the reference in your add-in. For more information, see [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md).
     
  
 Figure 2 shows the resources in the model for SharePoint Add-ins for cloud-hosted add-ins.
@@ -81,7 +87,7 @@ Figure 2 shows the resources in the model for SharePoint Add-ins for cloud-hoste
  
 
  
-![App UX resources for developer-hosted apps](../../images/AppUX_devhosted.png)
+![App UX resources for developer-hosted apps](../images/AppUX_devhosted.png)
  
 
  
@@ -120,10 +126,10 @@ The following UX resources are available to connect your add-in UX to the host w
 
  
 
--  **Custom actions**: You can use custom actions to connect the host web UX with your add-in. There are two types of custom actions:Ribbon orECB. A custom action can send parameters such as the list or item on which it was invoked to a remote page. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins).
+-  **Custom actions**: You can use custom actions to connect the host web UX with your add-in. There are two types of custom actions:Ribbon orECB. A custom action can send parameters such as the list or item on which it was invoked to a remote page. For more information, see  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md).
     
  
--  **Add-in parts:** You can include some of your add-in user experience in the host web by using add-in parts. The add-in part is available in the Web Part gallery in the host web when you deploy the add-in. Users can add the add-in part to a page by using the **Web Part Adder** control. For more information, see [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in).
+-  **Add-in parts:** You can include some of your add-in user experience in the host web by using add-in parts. The add-in part is available in the Web Part gallery in the host web when you deploy the add-in. Users can add the add-in part to a page by using the **Web Part Adder** control. For more information, see [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md).
     
  
 Figure 3 shows the resources in the model for SharePoint Add-ins to connect your add-in UX to the host web.
@@ -136,7 +142,7 @@ Figure 3 shows the resources in the model for SharePoint Add-ins to connect your
  
 
  
-![App UX resources for the host web](../../images/AppUX_hostweb.png)
+![App UX resources for the host web](../images/AppUX_hostweb.png)
  
 
  
@@ -151,37 +157,37 @@ To learn how to use the add-in UX options in SharePoint Add-ins, see the followi
 
  
 
--  [Design SharePoint Add-ins](design-sharepoint-add-ins)
+-  [Design SharePoint Add-ins](design-sharepoint-add-ins.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)
+-  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)
     
  
--  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines)
+-  [SharePoint Add-ins UX design guidelines](sharepoint-add-ins-ux-design-guidelines.md)
     
  
--  [Create UX components in SharePoint](create-ux-components-in-sharepoint-2013)
+-  [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)
     
  
--  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins)
+-  [Use a SharePoint website's style sheet in SharePoint Add-ins](use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md)
     
  
--  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins)
+-  [Use the client chrome control in SharePoint Add-ins](use-the-client-chrome-control-in-sharepoint-add-ins.md)
     
  
--  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in)
+-  [Create add-in parts to install with your SharePoint Add-in](create-add-in-parts-to-install-with-your-sharepoint-add-in.md)
     
  
--  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins)
+-  [Create custom actions to deploy with SharePoint Add-ins](create-custom-actions-to-deploy-with-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md b/docs/sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md
index 8bf86ebf3b..ae2a09f14b 100644
--- a/docs/sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md
+++ b/docs/sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md
@@ -1,9 +1,15 @@
+---
+title: What's new in Office Developer Tools for Visual Studio 2013
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # What's new in Office Developer Tools for Visual Studio 2013
 You can develop SharePoint Add-ins by using the following new features available in the Office Developer Tools for Visual Studio. 
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -23,7 +29,7 @@ You can develop SharePoint Add-ins by using the following new features available
 <a name="SP15NewVSTools_addlresources"> </a>
 
 
--  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins)
+-  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/work-with-external-data-in-sharepoint.md b/docs/sp-add-ins/work-with-external-data-in-sharepoint.md
index bf59250a7d..454cd08426 100644
--- a/docs/sp-add-ins/work-with-external-data-in-sharepoint.md
+++ b/docs/sp-add-ins/work-with-external-data-in-sharepoint.md
@@ -1,9 +1,15 @@
+---
+title: Work with external data in SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Work with external data in SharePoint
 Find resources and guidance for accessing and manipulating external data with JavaScript on pages in SharePoint Add-ins.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
@@ -21,12 +27,12 @@ You can use the cross-domain library to access data in your remote web applicati
  
 
  
-For details about how to use the library in this way, see  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013).
+For details about how to use the library in this way, see  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md).
  
 
  
 
- **Note**  The SharePoint cross-domain library can also be used in the other direction; that is, JavaScript on remote web pages can use it to access data from SharePoint. For more information about this use of the library, see  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library).
+ **Note**  The SharePoint cross-domain library can also be used in the other direction; that is, JavaScript on remote web pages can use it to access data from SharePoint. For more information about this use of the library, see  [Creating SharePoint Add-ins that use the cross-domain library](creating-sharepoint-add-ins-that-use-the-cross-domain-library.md).
  
 
 
@@ -36,7 +42,7 @@ You can use the web proxy that is exposed in the JavaScript client object model
  
 
  
-For details about how to use the proxy, see  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint-2013).
+For details about how to use the proxy, see  [Query a remote service using the web proxy in SharePoint](query-a-remote-service-using-the-web-proxy-in-sharepoint.md).
  
 
  
@@ -45,10 +51,10 @@ For details about how to use the proxy, see  [Query a remote service using the w
 <a name="SP15Workdata_AddRes"> </a>
 
 
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web.md b/docs/sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web.md
index 567a0d7133..bf7441be83 100644
--- a/docs/sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web.md
+++ b/docs/sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web.md
@@ -1,42 +1,48 @@
+---
+title: Work with host web data from JavaScript in the add-in web
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Work with host web data from JavaScript in the add-in web
 Use the SharePoint JavaScript object model (JSOM) to work with SharePoint data in the host web from JavaScript on pages in the add-in web.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
-This is the 11th in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins) and the previous articles in this series:
+This is the 11th in a series of articles about the basics of developing SharePoint-hosted SharePoint Add-ins. You should first be familiar with  [SharePoint Add-ins](sharepoint-add-ins.md) and the previous articles in this series:
  
 
--  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins)
+-  [Get started creating SharePoint-hosted SharePoint Add-ins](get-started-creating-sharepoint-hosted-sharepoint-add-ins.md)
     
  
--  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in)
+-  [Deploy and install a SharePoint-hosted SharePoint Add-in](deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add custom columns to a SharePoint-hostedSharePoint Add-in](add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in)
+-  [Add a custom content type to a SharePoint-hostedSharePoint Add-in](add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md)
     
  
--  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in](add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a workflow to a SharePoint-hosted SharePoint Add-in](add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add a custom page and style to a SharePoint-hosted SharePoint Add-in](add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in)
+-  [Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in](add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md)
     
  
--  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in)
+-  [Create a custom ribbon button in the host web of a SharePoint Add-in](create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md)
     
  
--  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data)
+-  [Use the SharePoint JavaScript APIs to work with SharePoint data](use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md)
     
  
 
@@ -80,7 +86,7 @@ Open the host web -- your developer test website -- and verify that there is a c
 
  
 
-  ![A calendar named Employee Orientation Schedule with an item on June 1st that says "Orient Cassie Hicks"](../../images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG)
+  ![A calendar named Employee Orientation Schedule with an item on June 1st that says "Orient Cassie Hicks"](../images/d2066862-41c1-424d-9bfb-b6c5342bcf2c.PNG)
  
 
  
@@ -352,7 +358,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![The list of permissionson the Permissions tab in the Visual Studio add-in manifest designer with the Edit button visible in the cell of the Properties column.](../../images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG)
+  ![The list of permissionson the Permissions tab in the Visual Studio add-in manifest designer with the Edit button visible in the cell of the Properties column.](../images/03780b79-aca8-44d1-b0bf-d80833d08627.PNG)
  
 
  
@@ -367,7 +373,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![The Properties dialog for list permissions in Visual Studio with property name set to "Base List ID" and the Value set to "106".](../../images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG)
+  ![The Properties dialog for list permissions in Visual Studio with property name set to "Base List ID" and the Value set to "106".](../images/13773fdd-5606-4f35-b8d5-14aad54cffb7.PNG)
  
 
     Choose  **OK**. The  **Permissions** tab should now look similar to the following:
@@ -377,7 +383,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![The Permissions tab of the add-in manifest designer in Visual Studio showing that the add-in wants Manage permission to lists that have base type 106.](../../images/14d5a820-ab44-4d12-98de-6672884bf344.PNG)
+  ![The Permissions tab of the add-in manifest designer in Visual Studio showing that the add-in wants Manage permission to lists that have base type 106.](../images/14d5a820-ab44-4d12-98de-6672884bf344.PNG)
  
 
  
@@ -406,7 +412,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![The SharePoint add-in consent prompt with brief description of the permissions the add-in needs and buttons to "Trust It" or "Cancel".](../../images/99209248-8927-4fc2-abfc-53d530376516.PNG)
+  ![The SharePoint add-in consent prompt with brief description of the permissions the add-in needs and buttons to "Trust It" or "Cancel".](../images/99209248-8927-4fc2-abfc-53d530376516.PNG)
  
 
  
@@ -418,7 +424,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![The Employee Orientation home page with a new button added which has the label "Ensure Items are Scheduled".](../../images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG)
+  ![The Employee Orientation home page with a new button added which has the label "Ensure Items are Scheduled".](../images/72b78f79-78c0-41db-90d5-8f67e1c17b0e.PNG)
  
 
  
@@ -436,7 +442,7 @@ Your add-in automatically has full control permission to its own add-in web, so
 
  
 
-  ![Employee Orientation calendar with new events added for the orientation of two employees on the 10th and 11th of the month](../../images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG)
+  ![Employee Orientation calendar with new events added for the orientation of two employees on the 10th and 11th of the month](../images/f8037509-4bf1-4c69-a673-ee6fe0f0dcb7.PNG)
  
 
  
@@ -460,16 +466,16 @@ Go on to advanced work in SharePoint-hosted SharePoint Add-ins:
 
  
 
--  [Design SharePoint Add-ins](design-sharepoint-add-ins)
+-  [Design SharePoint Add-ins](design-sharepoint-add-ins.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Publish SharePoint Add-ins](publish-sharepoint-add-ins)
+-  [Publish SharePoint Add-ins](publish-sharepoint-add-ins.md)
     
  
--  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins)
+-  [Tools and environments for developing SharePoint Add-ins](tools-and-environments-for-developing-sharepoint-add-ins.md)
     
  
 
diff --git a/docs/sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md b/docs/sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md
index 644ff10cf5..4f37311ef0 100644
--- a/docs/sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md
+++ b/docs/sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md
@@ -1,10 +1,15 @@
+---
+title: Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins
 Learn how to use the cross-domain library in SharePoint when the host web and add-in pages are in different security zones in Windows Internet Explorer.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 If you are using the SharePoint cross-domain library for your add-ins, you should be aware of how security zones work in Internet Explorer. Your add-in may encounter some communication issues if the SharePoint website and the add-in are in different zones. This article explains what happens when you use the cross-domain library in different Internet Explorer security zones.
@@ -17,7 +22,7 @@ For security reasons, Internet Explorer prevents pages that are on different int
  
 
  
-The SharePoint cross-domain library uses a hidden  **IFrame** and a client-side proxy page hosted on SharePoint to enable client-side communication using JavaScript. The cross-domain library is available when you reference the sp.requestexecutor.js file in your pages. For more information, see [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library).
+The SharePoint cross-domain library uses a hidden  **IFrame** and a client-side proxy page hosted on SharePoint to enable client-side communication using JavaScript. The cross-domain library is available when you reference the sp.requestexecutor.js file in your pages. For more information, see [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md).
  
 
  
@@ -35,7 +40,7 @@ The following diagram shows a cross-zone scenario in which the proxy page cannot
  
 
  
-![Cross-zone scenario, proxy page cannot be loaded](../../images/Crosszone_loaderror.png)
+![Cross-zone scenario, proxy page cannot be loaded](../images/Crosszone_loaderror.png)
  
 The following are some examples in which the cross-domain library may not be able to load the proxy page:
  
@@ -75,7 +80,7 @@ The following diagram shows a cross-zone scenario being handled by using the app
  
 
  
-![Cross-zone scenario handling by using the apphost](../../images/Crosszone_loadsuccess.png)
+![Cross-zone scenario handling by using the apphost](../images/Crosszone_loadsuccess.png)
  
 The code required for the apphost page is simple. The main portion of the apphost page is an  **SPAppIFrame** element. You must use CSS to make the **IFrame** invisible so that it doesn't interfere with your add-in.
  
@@ -197,31 +202,31 @@ Other browsers, such as Google Chrome, Mozilla Firefox, and Apple Safari, do not
 <a name="bk_addresources"> </a>
 
 
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-2013-data-from-add-ins-using-the-cross-domain-library)
+-  [Access SharePoint data from add-ins using the cross-domain library](access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md)
     
  
--  [SharePoint Add-ins](sharepoint-add-ins)
+-  [SharePoint Add-ins](sharepoint-add-ins.md)
     
  
--  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins)
+-  [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
     
  
--  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins)
+-  [Three ways to think about design options for SharePoint Add-ins](three-ways-to-think-about-design-options-for-sharepoint-add-ins.md)
     
  
--  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape)
+-  [Important aspects of the SharePoint Add-in architecture and development landscape](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md)
     
  
--  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint-2013)
+-  [Host webs, add-in webs, and SharePoint components in SharePoint](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md)
     
  
--  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscape#Data)
+-  [Data storage in SharePoint Add-ins](important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md#Data)
     
  
--  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint-2013)
+-  [Create a custom proxy page for the cross-domain library in SharePoint](create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md)
     
  
 -  [Client-side Cross-domain Security](http://msdn.microsoft.com/en-us/library/cc709423%28v=vs.85%29.aspx)
diff --git a/docs/sp-add-ins/working-with-folders-and-files-with-rest.md b/docs/sp-add-ins/working-with-folders-and-files-with-rest.md
index a99c4f663e..c9a04b3d00 100644
--- a/docs/sp-add-ins/working-with-folders-and-files-with-rest.md
+++ b/docs/sp-add-ins/working-with-folders-and-files-with-rest.md
@@ -1,13 +1,19 @@
+---
+title: Working with folders and files with REST
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
 # Working with folders and files with REST
 Learn how to perform basic create, read, update, and delete (CRUD) operations on folders and files with the SharePoint REST interface.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis). 
+ **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md). 
  
 
 
@@ -189,7 +195,7 @@ Headers:
     content-length:length of post body
 ```
 
-If you want to update a file's metadata, you'll have to construct an endpoint that reaches the file as a list item. You can do this because each folder is also a list, and each file is also a list item. Construct an endpoint that looks like this:  `https://<site url>/_api/web/lists/getbytitle('Documents')/items(<item id>)`.  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest) explains how to update a list item's metadata.
+If you want to update a file's metadata, you'll have to construct an endpoint that reaches the file as a list item. You can do this because each folder is also a list, and each file is also a list item. Construct an endpoint that looks like this:  `https://<site url>/_api/web/lists/getbytitle('Documents')/items(<item id>)`.  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md) explains how to update a list item's metadata.
  
 
  
@@ -245,7 +251,7 @@ headers:
 ## Working with large files by using REST
 <a name="LargeFiles"> </a>
 
-When you need to upload a binary file that is larger than 1.5 megabytes (MB), the REST interface is your only option. See  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013) for a code example that shows you how to upload a binary file that is smaller than 1.5 MB by using the SharePoint Javascript object model. The maximum size of a binary file that you can create with REST is 2 gigabytes (GB). The following example shows how to **create** a large binary file.
+When you need to upload a binary file that is larger than 1.5 megabytes (MB), the REST interface is your only option. See  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md) for a code example that shows you how to upload a binary file that is smaller than 1.5 MB by using the SharePoint Javascript object model. The maximum size of a binary file that you can create with REST is 2 gigabytes (GB.md). The following example shows how to **create** a large binary file.
  
 
  
@@ -379,22 +385,22 @@ headers:
 <a name="bk_addresources"> </a>
 
 
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
 -  [Files and folders REST API reference](http://msdn.microsoft.com/library/files-and-folders-rest-api-reference%28Office.15%29.aspx)
     
  
--  [Upload a file by using the REST API and jQuery](upload-a-file-by-using-the-rest-api-and-jquery)
+-  [Upload a file by using the REST API and jQuery](upload-a-file-by-using-the-rest-api-and-jquery.md)
     
  
--  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest)
+-  [Working with lists and list items with REST](working-with-lists-and-list-items-with-rest.md)
     
  
 -  [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations)
     
  
--  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-2013-Perform-ab9c4ae5)
+-  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-Perform-ab9c4ae5)
     
  
 -  [Making REST calls with C# and JavaScript for SharePoint](http://www.microsoft.com/resources/msdn/en-us/office/media/video/videol?cid=sdc&amp;from=mscomsdc&amp;VideoID=4e4cc094-ff69-405b-852f-2ac7c41293c5)
@@ -403,19 +409,19 @@ headers:
 -  [Making REST calls with C# and JavaScript for SharePoint demo](http://www.microsoft.com/resources/msdn/en-us/office/media/video/videol?cid=sdc&amp;from=mscomsdc&amp;VideoID=b1e7c9c5-0f62-4a78-bb7b-8e283c86145c)
     
  
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
 -  [Open Data Protocol](http://www.odata.org/)
diff --git a/docs/sp-add-ins/working-with-lists-and-list-items-with-rest.md b/docs/sp-add-ins/working-with-lists-and-list-items-with-rest.md
index afdf0e6dac..644d8d2181 100644
--- a/docs/sp-add-ins/working-with-lists-and-list-items-with-rest.md
+++ b/docs/sp-add-ins/working-with-lists-and-list-items-with-rest.md
@@ -1,21 +1,25 @@
-
+---
+title: Working with lists and list items with REST
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
 
 # Working with lists and list items with REST
 Learn how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the SharePoint REST interface.
  
 
- **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint#bk_newname).
+ **Note**  The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint". For details, see  [New name for apps for Office and SharePoint](new-name-for-apps-for-sharepoint.md#bk_newname).
  
 
 
- **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis).
+ **Tip**  The SharePoint Online (and on-premise SharePoint 2016 and later) REST service supports combining multiple requests into a single call to the service by using the OData  `$batch` query option. For details and links to code samples, see [Make batch requests with the REST APIs](make-batch-requests-with-the-rest-apis.md).
  
 
 
 ## Prerequisites
 
-This topic assumes that you are already familiar with the topics  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-2013-rest-service) and [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints). It does not provide code snippets.
+This topic assumes that you are already familiar with the topics  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md) and [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md). It does not provide code snippets.
  
 
  
@@ -349,16 +353,16 @@ Within SharePoint, ETags apply only to SharePoint lists and list items.
 <a name="bk_addresources"> </a>
 
 
--  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-2013-rest-endpoints)
+-  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)
     
  
--  [Working with folders and files with REST](working-with-folders-and-files-with-rest)
+-  [Working with folders and files with REST](working-with-folders-and-files-with-rest.md)
     
  
 -  [SharePoint-Add-in-REST-OData-BasicDataOperations](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-BasicDataOperations)
     
  
--  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-2013-Perform-ab9c4ae5)
+-  [SharePoint: Perform basic data access operations on files and folders by using REST](http://code.msdn.microsoft.com/SharePoint-Perform-ab9c4ae5)
     
  
 -  [Making REST calls with C# and JavaScript for SharePoint](http://www.microsoft.com/resources/msdn/en-us/office/media/video/videol?cid=sdc&amp;from=mscomsdc&amp;VideoID=4e4cc094-ff69-405b-852f-2ac7c41293c5)
@@ -367,19 +371,19 @@ Within SharePoint, ETags apply only to SharePoint lists and list items.
 -  [Making REST calls with C# and JavaScript for SharePoint demo](http://www.microsoft.com/resources/msdn/en-us/office/media/video/videol?cid=sdc&amp;from=mscomsdc&amp;VideoID=b1e7c9c5-0f62-4a78-bb7b-8e283c86145c)
     
  
--  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-2013-client-library-code)
+-  [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)
     
  
--  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint-2013)
+-  [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)
     
  
--  [Develop SharePoint Add-ins](develop-sharepoint-add-ins)
+-  [Develop SharePoint Add-ins](develop-sharepoint-add-ins.md)
     
  
--  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins)
+-  [Secure data access and client object models for SharePoint Add-ins](secure-data-access-and-client-object-models-for-sharepoint-add-ins.md)
     
  
--  [Work with external data in SharePoint](work-with-external-data-in-sharepoint-2013)
+-  [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)
     
  
 -  [Open Data Protocol](http://www.odata.org/)
diff --git a/docs/spfx/call-microsoft-graph-using-graphhttpclient.md b/docs/spfx/call-microsoft-graph-using-graphhttpclient.md
index 6be1b7eaa4..2eb61e384f 100644
--- a/docs/spfx/call-microsoft-graph-using-graphhttpclient.md
+++ b/docs/spfx/call-microsoft-graph-using-graphhttpclient.md
@@ -1,3 +1,10 @@
+---
+title: Call Microsoft Graph using the SharePoint Framework GraphHttpClient
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Call Microsoft Graph using the SharePoint Framework GraphHttpClient
 
 Using the Microsoft Graph you can build powerful solutions that use data from the different services that are a part of Office 365. In the past, connecting SharePoint Framework solutions to the Microsoft Graph was challenging, as it required you to register an Azure Active Directory application and complete the authorization flow. With the SharePoint Framework GraphHttpClient you can directly call the Microsoft Graph, without any additional setup.
@@ -49,7 +56,7 @@ The GraphHttpClient uses the **Office 365 SharePoint Online** Azure Active Direc
 * **Read and write all groups (preview)** (`Group.ReadWrite.All`) 
 * **Read all usage reports** (`Reports.Read.All`) 
 
-At this moment these are the only two permissions available when using the GraphHttpClient. If you need other permission scopes in your solution, you have to use [ADAL JS with implicit OAuth flow](web-parts/guidance/call-microsoft-graph-from-your-web-part) instead.
+At this moment these are the only two permissions available when using the GraphHttpClient. If you need other permission scopes in your solution, you have to use [ADAL JS with implicit OAuth flow](web-parts/guidance/call-microsoft-graph-from-your-web-part.md) instead.
 
 ### Tokens are retrieved using an internal API
 
@@ -59,4 +66,4 @@ To acquire a valid access token, the GraphHttpClient issues a web request to the
 
 To see how the GraphHttpClient can be used in practice, see a sample solution on GitHub at [https://github.com/SharePoint/sp-dev-fx-extensions/tree/master/samples/js-application-graph-client](https://github.com/SharePoint/sp-dev-fx-extensions/tree/master/samples/js-application-graph-client).
 
-For more information about the Microsoft Graph visit [https://developer.microsoft.com/en-us/graph/](https://developer.microsoft.com/en-us/graph/).
\ No newline at end of file
+For more information about the Microsoft Graph visit [https://developer.microsoft.com/en-us/graph/](https://developer.microsoft.com/en-us/graph/).
diff --git a/docs/spfx/css-recommendations.md b/docs/spfx/css-recommendations.md
index 2dd9c99feb..85f6ad2891 100644
--- a/docs/spfx/css-recommendations.md
+++ b/docs/spfx/css-recommendations.md
@@ -1,6 +1,13 @@
+---
+title: Recommendations for working with CSS in SharePoint Framework solutions
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Recommendations for working with CSS in SharePoint Framework solutions
 
-When building SharePoint Framework solutions, you can use CSS to define how your customizations should look and behave. This article describes how you can make the best use of the capabilities provided by the SharePoint Framework and build your CSS styles in a robust way.
+When building SharePoint Framework solutions, you can use CSS to define how your customization should look like and behave. This article describes how you can make the best use of the capabilities provided with the SharePoint Framework and build your CSS styles in a robust way.
 
 ## SharePoint Framework customizations are part of the page
 
@@ -216,7 +223,7 @@ Because the selector begins with the unique class name, specific to your compone
 
 ## Integrate Office UI Fabric
 
-By making your customizations look and behave like the standard functionality of SharePoint and Office 365 you will make it easier for the end-users to work with them. Office UI Fabric offers you a set of controls and styles for use in your customizations to seamlessly integrate with the existing user experience. For more information on using Office UI Fabric in the SharePoint Framework, read the [Office UI Fabric integration guide](./web-parts/guidance/office-ui-fabric-integration.md).
+By making your customizations look and behave like the standard functionality of SharePoint and Office 365 you will make it easier for the end-users to work with them. Office UI Fabric offers you a set of controls and styles for use in your customizations to seamlessly integrate with the existing user experience. For more information on using Office UI Fabric in the SharePoint Framework, read the [Office UI Fabric integration guide](web-parts/guidance/office-ui-fabric-integration.md).
 
 ## Use theme colors
 
diff --git a/docs/spfx/debug-in-vscode.md b/docs/spfx/debug-in-vscode.md
index a9fb11dbf3..98e847e7e5 100644
--- a/docs/spfx/debug-in-vscode.md
+++ b/docs/spfx/debug-in-vscode.md
@@ -1,3 +1,10 @@
+---
+title: Debug SharePoint Framework solutions in Visual Studio Code
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Debug SharePoint Framework solutions in Visual Studio Code
 
 Visual Studio Code is a popular code editor frequently used for building SharePoint Framework solutions. By setting up debugging of your SharePoint Framework solution in Visual Studio Code, you can more efficiently step through your code and fix errors. This article describes the prerequisites and configuration steps required to configure Visual Studio Code for debugging SharePoint Framework solutions.
@@ -14,15 +21,15 @@ Download and install the latest version of Google Chrome from [https://www.googl
 
 Start Visual Studio Code and open the **Extensions** pane.
 
-![The extensions pane activated in Visual Studio Code](../../images/vscode-debugging-vscode-extensions.png)
+![The extensions pane activated in Visual Studio Code](../images/vscode-debugging-vscode-extensions.png)
 
 In the search box, search for **Debugger for Chrome**.
 
-![The Debugger for Chrome extension selected in the search results](../../images/vscode-debugging-debugger-chrome-extension.png)
+![The Debugger for Chrome extension selected in the search results](../images/vscode-debugging-debugger-chrome-extension.png)
 
 Install the **Debugger for Chrome** extension by clicking the **Install** button, next to the extension. After the extension has been installed, reload the Visual Studio Code window by clicking the **Reload** button.
 
-![Reload button highlighted next to the Debugger for Chrome extension](../../images/vscode-debugging-debugger-extension-installed-reload.png)
+![Reload button highlighted next to the Debugger for Chrome extension](../images/vscode-debugging-debugger-extension-installed-reload.png)
 
 ## Debug SharePoint Framework solution using local workbench
 
@@ -32,15 +39,15 @@ When building SharePoint Framework solutions, you can use the local workbench to
 
 In Visual Studio Code activate the **Debug** pane.
 
-![Debug pane activated in Visual Studio Code](../../images/vscode-debugging-vscode-debug.png)
+![Debug pane activated in Visual Studio Code](../images/vscode-debugging-vscode-debug.png)
 
 In the top section of the pane, open the **Configurations** drop-down and select the **Add Configuration...** option.
 
-![The Add Configuration option highlighted in the debug configurations drop-down](../../images/vscode-debugging-add-debug-configuration.png)
+![The Add Configuration option highlighted in the debug configurations drop-down](../images/vscode-debugging-add-debug-configuration.png)
 
 From the list of debug environments select **Chrome**.
 
-![Chrome highlighted as the debug environment for the new configuration](../../images/vscode-debugging-chrome-debug-environment.png)
+![Chrome highlighted as the debug environment for the new configuration](../images/vscode-debugging-chrome-debug-environment.png)
 
 Replace the contents of the generated **launch.json** file with:
 
@@ -78,7 +85,7 @@ With Visual Studio Code configured for debugging SharePoint Framework solutions
 
 In Visual Studio Code open the main web part source file and add a breakpoint in the first line of the **render** method by either clicking on the margin left to the line number or by highlighting the code line in the editor and pressing the **F9** key.
 
-![Breakpoint configured in a SharePoint Framework client-side web part in Visual Studio Code](../../images/vscode-debugging-breakpoint-configured.png)
+![Breakpoint configured in a SharePoint Framework client-side web part in Visual Studio Code](../images/vscode-debugging-breakpoint-configured.png)
 
 #### Start serving the SharePoint Framework solution
 
@@ -90,13 +97,13 @@ gulp serve --nobrowser
 
 Running this command will build your SharePoint Framework solution and start the local webserver to serve the output files. Because the debugger will start its own instance of the browser, you use the **--nobrowser** argument to prevent the **serve** task from opening a browser window.
 
-![The gulp serve command typed in the integrated terminal in Visual Studio Code](../../images/vscode-debugging-gulp-serve.png)
+![The gulp serve command typed in the integrated terminal in Visual Studio Code](../images/vscode-debugging-gulp-serve.png)
 
 #### Start debugging in Visual Studio Code
 
 Once the gulp task is finished, move the focus to the code area of Visual Studio Code and press **F5** (or from the **Debug** menu select the **Start Debugging** option). The debug mode in Visual Studio Code will start, changing the color of the status bar to orange and a new window of Google Chrome will open showing the local version of the SharePoint workbench.
 
-![Visual Studio Code in debug mode displayed next to Google Chrome showing the local version of the SharePoint workbench](../../images/vscode-debugging-chrome-started.png)
+![Visual Studio Code in debug mode displayed next to Google Chrome showing the local version of the SharePoint workbench](../images/vscode-debugging-chrome-started.png)
 
 > Note, that at this point the breakpoint is disabled, because the web part's code hasn't been loaded yet. SharePoint Framework loads web parts on demand only after they have been added to the page.
 
@@ -104,15 +111,15 @@ Once the gulp task is finished, move the focus to the code area of Visual Studio
 
 To verify that debugging is working, in the workbench add your web part to the canvas.
 
-![Web part toolbox open in SharePoint workbench](../../images/vscode-debugging-adding-web-part-to-canvas.png)
+![Web part toolbox open in SharePoint workbench](../images/vscode-debugging-adding-web-part-to-canvas.png)
 
 Notice, that with the code loaded on the page, the breakpoint indicator changed to active.
 
-![Breakpoint active after adding web part to the canvas](../../images/vscode-debugging-breakpoint-active.png)
+![Breakpoint active after adding web part to the canvas](../images/vscode-debugging-breakpoint-active.png)
 
 If you now reload the page, your breakpoint in Visual Studio Code will be hit, and you will be able to inspect all properties and step through the code.
 
-![Breakpoint hit in Visual Studio Code](../../images/vscode-debugging-breakpoint-hit.png)
+![Breakpoint hit in Visual Studio Code](../images/vscode-debugging-breakpoint-hit.png)
 
 ## Debug SharePoint Framework solution using hosted workbench
 
@@ -166,15 +173,15 @@ In Visual Studio Code open the **./.vscode/launch.json** file. Copy the existing
 
 With the debug configuration for the hosted workbench ready, verify that it's working correctly. In Visual Studio Code, activate the **Debug** pane and in the **Configurations** drop-down, select the newly added **Hosted workbench** configuration.
 
-![The hosted workbench configuration selected in the debug configurations drop-down in Visual Studio Code](../../images/vscode-debugging-debugging-hosted-workbench.png)
+![The hosted workbench configuration selected in the debug configurations drop-down in Visual Studio Code](../images/vscode-debugging-debugging-hosted-workbench.png)
 
 Next, start debugging either by pressing the **F5** key or by selecting from the **Debug** menu the **Start Debugging** option. Visual Studio Code will switch into debug mode, indicated by the orange status bar, and the Debugger for Chrome extension will open a new instance of Google Chrome with the Office 365 login page.
 
-![Office 365 login page displayed in Google Chrome after starting debugging in the hosted workbench](../../images/vscode-debugging-o365-login.png)
+![Office 365 login page displayed in Google Chrome after starting debugging in the hosted workbench](../images/vscode-debugging-o365-login.png)
 
 After you log in, add the web part to the canvas and refresh the workbench, just like with the local workbench, you will see the breakpoint in Visual Studio Code be hit and you will be able to inspect variables and step through the code.
 
-![Breakpoint hit in Visual Studio Code when debugging a SharePoint Framework client-side web part in the hosted workbench](../../images/vscode-debugging-breakpoint-hit-o365.png)
+![Breakpoint hit in Visual Studio Code when debugging a SharePoint Framework client-side web part in the hosted workbench](../images/vscode-debugging-breakpoint-hit-o365.png)
 
 ## Additional information
 
diff --git a/docs/spfx/enterprise-guidance.md b/docs/spfx/enterprise-guidance.md
index 1525b50915..b3e8237082 100644
--- a/docs/spfx/enterprise-guidance.md
+++ b/docs/spfx/enterprise-guidance.md
@@ -1,3 +1,10 @@
+---
+title: SharePoint Framework (SPFx) enterprise guidance
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Framework (SPFx) enterprise guidance
 
 ## Introduction
@@ -95,14 +102,14 @@ SharePoint is and have been one of the most successfull enterprise collaboration
 
 ### Enterprise developers
 
-The SharePoint Framework allows **Enterprise developers**, typically a developer that creates application for use within an organization, to extend SharePoint (Online) with new functionality in a structured and supported way. The SharePoint Framework offers everything from the development framework, build pipeline, to the actual deployment and allows the developers in a short time reach out to all Site Collections with new solutions and features, all controlled by the App Catalog. In an enterprise scenario you also have full control of the CDN locations; external or internal in SharePoint and you can very easily deploy fixes and updates to your whole organization.
+The SharePoint Framework allows **Enterprise developers**, typically a developer that creates application for use within an organization, to extend SharePoint (Online) with new functionality in a structured and supported way. The SharePoint Framework offers everything from the development framework, build pipeline, to the actual deployment and allows the developers in a short time reach out to all Site Collections with new solutions and features, all controlled by the App Catalog. In an enterprise scenarion you also have full control of the CDN locations; external or internal in SharePoint and you can very easy deploy fixes and updates to your whole organization.
 
 Within your enterprise administrators and developers jointly should create a *blue print* for how SharePoint Frameworks solutions should be deployed. The blue print should contain details on preferred client side frameworks, CDN locations etc. For more details, see the section below on *Building a plan around SharePoint Framework customizations*.
 
 ### Citizen developers
 
 Citizen developers have for a long time used SharePoint to build business applications using a lot of different methods and techniques.
-SharePoint Framework will for certain scenarios, specifically JavaScript embeddings and Script Editor Web Parts solutions be one good way forward. This to make these solutions more standardized and maintainable over time. For citizen developers there might be a little bit of learning curve to adjust to this new structured way of building solutions, but will in the long run prove to be more stable, secure and maintainable.
+SharePoint Framework will for certain scenarios, specifically JavaScript embeddings and Script Editor Web Parts solutions be one good way forward. This to make these solutions more standardized and maintainable over time. For citizen developers there might be a little bit of learning curve to adjust to this new structured way of building solutions, but will in the long run proove to be more stable, secure and maintainable.
 
 Given that the, above mentioned, *Custom Script* control methods are in place, the citizen developers will not be allowed to add arbitrary JavaScript code or Script Editor Web Parts. This can potentially make your SharePoint environment more stable and maintainable, but at the same time you might prohibt some *innovation* in your company, and should make sure that your citizen developers aligns with your enterprise developers on using SharePoint Framework going forward.
 
@@ -135,7 +142,7 @@ Finally, developers will need to think about application life cycle management (
 
 All SharePoint Framework solutions deployed into a tenant must be approved by a tenant administrator. This is done by uploading the SharePoint Framework package, the `.sppkg` file into the *Apps for SharePoint* library. When a new solution is added to the library, the administrator will get a dialog that asks for a consent to approve the solution for use in the tenancy. The dialog explains that this is a *full trust client side code* solution without any resource restrictions and that it executes under users context. The dialog also shows from what domain it will primarily get content, that is the CDN location of the SharePoint Framework scripts. Note that any SharePoint Framework application can load data from other locations, after the initial load from the CDN. Once approved the SharePoint Framework solution can be enabled on any Site Collection.
 
-![SharePoint Framework app catalog trust dialog](../../../../images/enterprise-guidance-trust-spfx-dialog.png)
+![SharePoint Framework app catalog trust dialog](../images/enterprise-guidance-trust-spfx-dialog.png)
 
 An administrator of the App Catalog can at any time remove the package from the App Catalog by removing the solution package from the *Apps for SharePoint* library. This will prohibit the solution to be used in all Site Collections. The solution can also be disabled by modifying the *Enabled* property of the uploaded package. This will immediatley disable the solution in all Site Collections; existing pages using client side web parts will not render the web part and the app will not be available on the Site Collections or available to add on existing Site Collections. When removing a SharePoint Framework solution it will not remove any data or information created by the actual client side solution either in SharePoint or in any external data source used by the solution.
 
@@ -161,7 +168,7 @@ What you cannot backup is the actual solution artifacts such as script bundles a
 
 ## SharePoint Framework Roadmap
 
-The SharePoint Framework reached General Availability (GA) in February 2017. General Availability means that IT and developers can supportably use SharePoint Framework in production. Beyond General Availability, we would expect that the set of scenarios where we would see SharePoint Framework-based components are built and used will expand beyond web parts scenarios, and into areas like list and site customizations. For more information about the SharePoint Framework see the dedicated [SharePoint Framework Roadmap article](https://dev.office.com/sharepoint/docs/spfx/roadmap). SharePoint Framework client-side web parts are also available in on-premises with SharePoint 2016 Feature Pack 2.
+The SharePoint Framework reached General Availability (GA) in February 2017. General Availability means that IT and developers can supportably use SharePoint Framework in production. Beyond General Availability, we would expect that the set of scenarios where we would see SharePoint Framework-based components are built and used will expand beyond web parts scenarios, and into areas like list and site customizations. For more information about the SharePoint Framework see the dedicated [SharePoint Framework Roadmap article](https://dev.office.com/sharepoint/docs/spfx/roadmap). Also, the SharePoint team is looking to bring the SharePoint Framework to SharePoint 2016 on-premises during 2017, as part of a future Feature Pack.
 
 Major changes or introduction of new major features will be announced through the Office 365 Message Center, found in your tenant admin - something that an Office 365 administrator already should have on their daily routine to check. Another important resource is the [Office Developer blog](http://dev.office.com/blogs) where you will find even more details and updates.
 
diff --git a/docs/spfx/extensions/changes-between-dev-preview-and-rc.md b/docs/spfx/extensions/changes-between-dev-preview-and-rc.md
index c2af6e0afa..c2e566bfaf 100644
--- a/docs/spfx/extensions/changes-between-dev-preview-and-rc.md
+++ b/docs/spfx/extensions/changes-between-dev-preview-and-rc.md
@@ -1,29 +1,37 @@
-# Changes introduced in the SharePoint Framework Extensions (preview) Release Candidate release
+---
+title: Changes between Dev Preview and Release Candidate for SharePoint Framework Extensions (preview)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
-If you used the developer preview version of the SharePoint Framework Extensions (released in June 2017), you'll have to make some changes to ensure that your extensions work with the Release Candidate (RC) release. This article provides a short list of the changes that were introduced in the SharePoint Framework Extensions RC release.
 
->**Note:** The RC release is enabled on the First Release tenants in Office 365, but is not yet supported for use in production.
+# Changes between Dev Preview and Release Candidate for SharePoint Framework Extensions (preview)
+
+If you have created SharePoint Framework Extensions with the developer preview version (released June 2017), you'll have to perform some changes to make them work with Release Candidate (RC) version. Here's a short list of the changes, which were introduced with the latest version.
+
+Release Candidate is enabled in the First Release tenants in Office 365, but is not supported yet in production use.
 
 ## General solution package changes
 
-- All SharePoint Framework packages are now standardized to version 1.2. All future updates will also have standard versions across all packages.
-- Upgraded to use TypeScript 2.4 and React 15 typings.
-- Updated to Fabric React 4.32.0.
+- All SharePoint Framework packages are now standardized to version 1.2. All future updates will also have version standardization cross all packages to avoid any confusions around used versions.
+- Upgrade to use TypeScript 2.4 and React 15 typings
+- Update to Fabric React 4.32.0.
 
-## Application Customizer changes
+### Application Customizer Changes
 
-- Placeholder logic has changed slightly and placeholders have been renamed. Typical placeholders are now called `'top'` and `'bottom'`.
-- The **`onRender`** method has been deprecated. Instead, call **`render`** from the **`onInit`** method, and add event handling for the possible events when placeholders should be re-rendered. For details, see [Using page placeholders](./get-started/using-page-placeholder-with-extensions.md).
-- The schema definition URL has been updated in the manifest file to point to the online documentation for the JSON schema.
+- Placeholder logic has been changed slightly and they have been renamed.
+- Typical placeholders are now called `'top'` and `'bottom'`
+- `onRender` method is deprecated - you should call render from the onInit, if needed and also add event handling for the possible events when placeholders should be re-rendered. See [updated placeholder tutorial](./get-started/using-page-placeholder-with-extensions.md) for details.
+- Schema definition URL has been updated in the manifest file to point json schema file from the dev.office.com.
 
-## Field Customizer changes
+### Field Customizer Changes
 
-- Changes were made to the APIs that access field values. Use **`event.fieldValue`**. Other options are deprecated.
-- The API to access UI elements to render the Field Customizer output has changed from **`event.cellDiv`** to **`event.domElement`**. 
-- The schema definition URL has been updated in the manifest file to point to the online documentation for the JSON schema.
+- There are changes in the APIs for accessing the actual field values. You should be using `event.fieldValue`. Other options are deprecated.
+- API to access UI element to render the field customizer output has been changed from `event.cellDiv` to `event.domElement`. 
+- Schema definition URL has been updated in the manifest file to point json schema file from the dev.office.com.
 
-## ListView Command Set changes
+### ListView Command Set Changes
 
-- The **`onRefreshCommand`** method has been deprecated and replaced with **`onListViewUpdated`**.
-- Changes were made to the commands structure in the manifest json file. Commands now use the **`items`** collection and command title handling was updated in the json definition.
-- The schema definition URL has been updated in the manifest file to point to the online documentation for the JSON schema.
+- `onRefreshCommand` method deprecated and replaced with `onListViewUpdated`.
+- Manifest json changes around the commands structure. Is using now `items` collections and changes in the title handling of the commands in the json definition.
+- Schema definition URL has been updated in the manifest file to point json schema file from the dev.office.com.
diff --git a/docs/spfx/extensions/get-started/build-a-hello-world-extension.md b/docs/spfx/extensions/get-started/build-a-hello-world-extension.md
index 15e5ba62eb..e8a2e6a020 100644
--- a/docs/spfx/extensions/get-started/build-a-hello-world-extension.md
+++ b/docs/spfx/extensions/get-started/build-a-hello-world-extension.md
@@ -1,153 +1,157 @@
+---
+title: Build your first SharePoint Framework Extension (Hello World part 1)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build your first SharePoint Framework Extension (Hello World part 1)
 
->**Note:** SharePoint Framework Extensions are currently in preview and are subject to change. They are not currently supported for use in production environments.
+>**Note:** The SharePoint Framework Extensions are currently in preview and are subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
 
-SharePoint Framework (SPFx) Extensions are client-side components that run inside the context of a SharePoint page. You can deploy extensions to SharePoint Online, and you can use modern JavaScript tools and libraries to build them.
+Extensions are client-side components that run inside the context of a SharePoint page. Extensions can be deployed to SharePoint Online, and you can also use modern JavaScript tools and libraries to build them.
 
-This article describes how to create your first Hello World SharePoint Framework Extension. You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=0BeS0HukW24&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
+You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=0BeS0HukW24&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
 
 <a href="https://www.youtube.com/watch?v=0BeS0HukW24&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorial1.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorial1.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Create an extension project
+Create a new project directory in your favorite location.
 
-1. Create a new project directory in your favorite location.
-
-    ```
-    md app-extension
-    ```
+```
+md app-extension
+```
 
-2. Go to the project directory.
+Go to the project directory.
 
-    ```
-    cd app-extension
-    ```
+```
+cd app-extension
+```
 
-3. Create a new HelloWorld extension by running the Yeoman SharePoint Generator.
+Create a new HelloWorld extension by running the Yeoman SharePoint Generator.
 
-    ```
-    yo @microsoft/sharepoint
-    ```
+```
+yo @microsoft/sharepoint
+```
 
-4. When prompted:
+When prompted:
 
-    * Accept the default **app-extension** as your solution name, and press **Enter**.
-    * Choose **Use the current folder**, and press **Enter**.
-    * Choose **N** to require the extension to be installed on each site explicitly when it's being used. 
-    * Choose **Extension (Preview)** as the client-side component type to be created. 
-    * Choose **Application Customizer (Preview)** as the extension type to be created.
+* Accept the default **app-extension** as your solution name and press **Enter**.
+* Choose **Use the current folder** and press **Enter**
+* Choose **N** to require extension to be installed on each site explicitly when it's being used 
+* Choose **Extension (Preview)** as the client-side component type to be created. 
+* Choose **Application Customizer (Preview)** as the extension type to be created.
 
-5. The next set of prompts will ask for specific information about your extension. When prompted:
+The next set of prompts will ask for specific information about your extension:
 
-    * Accept the default **HelloWorld** as your extension name, and press **Enter**.
-    * Accept the default **HelloWorld description** as your extension description, and press **Enter**.
+* Accept the default **HelloWorld** as your extension name and press **Enter**.
+* Accept the default **HelloWorld description** as your extension description and press **Enter**.
 
-    ![Yeoman SharePoint generator prompts to create an extension solution](../../../../images/ext-yeoman-app-prompts.png)
+![Yeoman SharePoint generator prompts to create an extension solution](../../../images/ext-yeoman-app-prompts.png)
 
-    > **Note:** If you use a name for the extension that is too long, you might encounter issues. The entries provided are used to generate an alias entry for the application customizer manifest json file. If the alias is longer than 40 characters, you will get an exception when you try to serve the extension using `gulp serve --nobrowser`. You can resolve this by updating the alias entry afterward.
+> Notice that if you use too long naming for the extension, that can cause issues. Provided entries are used to generate alias entry for the application customizer manifest json file. If alias is longer than 40 characters, you will have an exception when you are trying to serve the extension using `gulp serve --nobrowser`. You can solve this by updating the alias entry also afterwards.
 
-    At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** extension. This might take a few minutes. 
+At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** extension. This might take a few minutes. 
 
-    When the scaffold is complete, you should see the following message indicating a successful scaffold:
+When the scaffold is complete, you should see the following message indicating a successful scaffold:
 
-    ![SharePoint client-side solution scaffolded successfully](../../../../images/ext-yeoman-app-complete.png)
+![SharePoint client-side solution scaffolded successfully](../../../images/ext-yeoman-app-complete.png)
 
-    For information about troubleshooting any errors, see [Known issues](../basics/known-issues).
+For information about troubleshooting any errors, see [Known issues](../../known-issues-and-common-questions.md).
 
-6. When the solution scaffolding is complete, type the following into the console to start Visual Studio Code.
+Once solution scaffolding is completed, type the following into the console to start Visual Studio Code.
 
-    ```
-    code .
-    ```
+```
+code .
+```
 
-        >**Note:** Because the SharePoint client-side solution is HTML/TypeScript based, you can use any code editor that supports client-side development to build your extension.
+> Notice that because the SharePoint client-side solution is HTML/TypeScript based, you can use any code editor that supports client-side development to build your extension.
 
-    Notice how the default solution structure looks like the solution structure for client-side web parts. This is the basic SharePoint Framework solution structure, with similar configuration options across all solution types.
+Notice how the default solution structure is like the solution structure of client-side web parts. This is the basic SharePoint Framework solution structure, with similar configuration options across all solution types.
 
-    ![SharePoint Framework solution opened after initial scaffolding](../../../../images/ext-app-vscode-solution-structure.png)
+![SharePoint Framework solution opened after initial scaffolding](../../../images/ext-app-vscode-solution-structure.png)
 
-7. Open **HelloWorldApplicationCustomizer.manifest.json** in the src\extensions\helloWorld folder.
+Open **HelloWorldApplicationCustomizer.manifest.json** at the src\extensions\helloWorld folder.
 
-    This file defines your extension type and a unique identifier for your extension. You’ll need this ID later when you debug and deploy your extension to SharePoint.
+This file defines your extension type and a unique identifier **“id”** for your extension. You’ll need this unique identifier later when debugging and deploying your extension to SharePoint.
 
-    ![Application customizer manifest json content](../../../../images/ext-app-vscode-manifest.png)
+![Application customizer manifest json content](../../../images/ext-app-vscode-manifest.png)
 
-## Code your Application Customizer 
+## Coding your Application Customizer 
 Open the **HelloWorldApplicationCustomizer.ts** file in the **src\extensions\helloWorld** folder.
 
 Notice that base class for the Application Customizer is imported from the **sp-application-base** package, which contains SharePoint framework code required by the Application Customizer.
 
-![Import statement for BaseApplicationCustomizer from @microsoft/sp-application-base](../../../../images/ext-app-vscode-app-base.png)
+![import statement for BaseApplicationCustomizer from @microsoft/sp-application-base](../../../images/ext-app-vscode-app-base.png)
 
 The logic for your Application Customizer is contained in the **onInit** method.
 
 - **onInit()** is called when the client-side extension is first activated on the page. This event occurs after ```this.context``` and ```this.properties``` are assigned. As with web parts, ```onInit()``` returns a promise that you can use to perform asynchronous operations.
 
->**Note:** The class constructor is called at an early stage, when ```this.context``` and ```this.properties``` are undefined. Custom initiation logic is not supported here.
-
-The following are the contents of **onInit()** in the default solution. This default solution writes a log to the Dev Dashboard, and then displays a simple JavaScript alert when the page renders.
+> Notice. The class constructor is called at an early stage, when ```this.context``` and ```this.properties``` are undefined. We do not support including custom initiation logic here.
 
-![Default onInit method in the code](../../../../images/ext-app-vscode-methods.png)
+Below is the contents of **onInit()** in the default solution. This default solution simply writes a log to the Dev Dashboard, and then displays a simple JavaScript alert when the page renders.
 
-If your application customizer uses the **ClientSideComponentProperties** JSON input, it will be deserialized into the **BaseExtension.properties** object. You can define an interface to describe it. The default template is looking for a property called **testMessage**. If that property is provided, it outputs it in an alert message.
+![default onInit method in the code](../../../images/ext-app-vscode-methods.png)
 
-## Debug your Application Customizer using gulp serve and query string parameters
-You cannot current use the local workbench to test SharePoint Framework Extensions. You'll need to test them  against a live SharePoint Online site. You don't have to deploy your customization to the app catalog to do this, which makes the debugging experience simple and efficient. 
+>  If your application customizer uses the ClientSideComponentProperties JSON input, it will be deserialized into the BaseExtension.properties object. You can define an interface to describe it. The default template is looking for a property called testMessage, and if it's provided, outputting it in an alert message.
 
-First, compile your code and host the compiled files from your local computer by running the following command.
+## Debugging your Application Customizer using gulp serve and query string parameters
+SharePoint Framework extensions cannot currently be tested using the local workbench, so you'll need to test and develop them directly against a live SharePoint Online site. You do not, however, need to deploy your customization to the app catalog to do this, which keeps the debugging experience simple and efficient. 
 
+First, compile your code and host the compiled files from your local machine by running this command:
 ```
 gulp serve --nobrowser
 ```
 
->**Note:** If you do not have the SPFx developer certificate installed, Workbench will notify you that it is not configured to load scripts from localhost. If this happens, stop the process that is currently running in the console window, run the `gulp trust-dev-cert` command in your project directory console to install the developer certificate, and then run the `gulp serve --nobrowser` command again.
-
-You use the ```--nobrowser``` option because you don't need to launch the local workbench, since you can't debug extensions locally.
+>**Note:** If you do not have the SPFx developer certificate installed, then Workbench will notify you that it is configured not to load scripts from localhost. Stop currently running process in the console window, execute `gulp trust-dev-cert` command in your project directory console to install the developer certificate before running `gulp serve --nobrowser` command again.
 
-When the code compiles without errors, it will serve the resulting manifest from http://localhost:4321.
+Notice that we used the ```--nobrowser``` option, since there's no value in launching the local workbench since you currently cannot debug extensions locally.
 
-![Gulp serve](../../../../images/ext-app-gulp-serve.png)
+Once it compiles the code without errors, it will serve the resulting manifest from http://localhost:4321.
 
-To test your extension, go to a modern list view page in your SharePoint environment and append the following query string parameters to the URL. Notice that you will need to update the ID to match your own extension identifier. This is available in the **HelloWorldApplicationCustomizer.manifest.json** file.
+![gulp serve](../../../images/ext-app-gulp-serve.png)
 
+To test your extension, navigate to a modern list view page in your SharePoint environment and append the following query string parameters to the URL. Notice that you will need to update the id to match your own extension identifier available from the **HelloWorldApplicationCustomizer.manifest.json** file:
 ```
 ?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js&customActions={"e5625e23-5c5a-4007-a335-e6c2c3afa485":{"location":"ClientSideExtension.ApplicationCustomizer","properties":{"testMessage":"Hello as property!"}}}
 ```
 
 More detail about the URL query parameters:
 
-* **loadSPFX=true** - Ensures that the SharePoint Framework is loaded on the page. For performance reasons, the framework does not load unless at least one extension is registered. Because no components are registered,you must explicitly load the framework.
+* **loadSPFX=true:**  ensures that the SharePoint Framework is loaded on the page. For performance reasons, the framework is not normally loaded unless at least one extension is registered. Since no components are registered yet, we must explicitly load the framework.
 
-* **debugManifestsFile** - Specifies that you want to load SPFx components that are locally served. The loader only looks for components in the App Catalog (for your deployed solution) and the SharePoint manifest server (for the system libraries).
+* **debugManifestsFile:**  specifies that we want to load SPFx components that are being locally served. Normally the loader only looks for components in the App Catalog (for your deployed solution) and the SharePoint manifest server (for the system libraries).
 
-* **customActions** - Simulates a custom action. When you deploy and register this component in a site, you'll create this **CustomAction** object and describe all the different properties you can set on it. 
-    * **Key** - Use the Guid of the extension as the key to associate with the custom action. This has to match the ID value of your extension, which is available in the extension manifest.json file.
-    * **Location** - The type of custom action. Use "ClientSideExtension.ApplicationCustomizer" for the Application Customizer extension.
-    * **Properties** - An optional JSON object that contains properties that will be available via the **this.properties** member. In this HelloWorld example, it defined a ‘testMessage’ property.
+* **customActions:**  this URL query parameter simulates a custom action. When we actually deploy and register this component in a site later in this lab, we’ll create this CustomAction object for real and describe all the different properties you can set on it. 
+    * **Key:** use the Guid of the extension as the key to associate with the custom action. This has to match on the id value of your extension available from the extension manifest.json.
+    * **Location:** the type of custom action, use "ClientSideExtension.ApplicationCustomizer" for the Application Customizer extension
+    * **Properties:** an optional JSON object containing properties that will be available via the this.properties member. In this HelloWorld example, it defined a ‘testMessage’ property.
 
 
-Go to a modern list in SharePoint Online. This can be either a list or a library. Application customizers are also supported in modern pages and on the Site Contents page. 
+Navigate to a out of the box modern list in SharePoint Online. This can be a list or a library for the initial testing. Application customizers are also supported in modern pages and on the Site Contents page. 
 
-Extend the URL with the additional query parameters described. Notice that you'll need to update the GUID to match the ID of your custom Application Customizer. 
+Extend the URL with the additional query parameters defined above. Notice that you'll need to update the GUID to match the ID of your custom Application Customizer available from  **HelloWorldApplicationCustomizer.manifest.json** at the src\extensions\helloWorld folder. 
 
-The full URL should look similar to the following:
+The full URL should look similar to the following depending on your tenant URL:
 
 ```
 contoso.sharepoint.com/Lists/Contoso/AllItems.aspx?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js&customActions={"e5625e23-5c5a-4007-a335-e6c2c3afa485":{"location":"ClientSideExtension.ApplicationCustomizer","properties":{"testMessage":"Hello as property!"}}}
 ```
 
-Choose **Load debug scripts** to continue loading scripts from your local host.
+![Allow Debug Manifest question from the page](../../../images/ext-app-debug-manifest-message.png)
 
-![Allow Debug Manifest question from the page](../../../../images/ext-app-debug-manifest-message.png)
+Click the "**Load debug scripts**" button to continue loading scripts from your local host.
 
 You should now see the alert message on your page.
 
-![Hello as property alert message](../../../../images/ext-app-alert-sp-page.png)
+![Allow Debug Manifest question from the page](../../../images/ext-app-alert-sp-page.png)
 
-This alert is thrown by your SharePoint Framework Extension. Note that because you provided the **testMessage** property as part of the debug query parameters, it's included in the alert message. You can configure your extension instances based on the client component properties, which are passed for the instance also in runtime mode. 
+This alert is thrown by your SharePoint Framework Extension. Notice also that since we provided the testMessage property as part of the debug query parameters, it's included in the alert message. You can configure your extension instances based on the client component properties, which are passed for the instance also in runtime mode. 
 
-> **Note:** If you have issues with debugging, double-check the URL query parameters used for the query. Some browsers encode the parameters and in some scenarios this affects the behavior. 
+> If you are having challenges in getting debugging to work, double check the URL query parameters used for the query. Some browsers tend to encode the parameters and in some scenarios this will impact the behavior. 
 
 ## Next steps
-Congratulations, you've gotten your first SharePoint Framework Extension running! To continue building out your extension, see [Using page placeholders from Application Customizer (Hello World part 2)](./using-page-placeholder-with-extensions.md). You will use the same project and take advantage of specific content placeholders for modifying the UI of SharePoint. Notice that the ```gulp serve``` command is still running in your console window (or in Visual Studio Code if you are using the editor). You can continue to let it run while you go to the next article.
+Congratulations on getting your first SharePoint Framework Extension running! Now that your extension is running, you can continue building out your extension in the next topic, [Using page placeholders from Application Customizer (Hello World part 2)](./using-page-placeholder-with-extensions.md). You will use the same project and take advantage of specific content placeholders for modifying the UI of SharePoint. Notice that the ```gulp serve``` command is still running in your console window (or in Visual Studio Code if you are using the editor.md). You can continue to let it run while you go to the next article.
diff --git a/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md b/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
index eb094f774d..cc4ee22566 100644
--- a/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
+++ b/docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
@@ -1,3 +1,10 @@
+---
+title: Build your first ListView Command Set extension
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build your first ListView Command Set extension
 
 >**Note:** The SharePoint Framework Extensions are currently in preview and are subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
@@ -7,7 +14,7 @@ Extensions are client-side components that run inside the context of a SharePoin
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=iW0LQQqAY0Y&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
 
 <a href="https://www.youtube.com/watch?v=iW0LQQqAY0Y&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorialcommand.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorialcommand.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Create an extension project
@@ -42,15 +49,15 @@ The next set of prompts will ask for specific information about your extension:
 * Accept the default value of **HelloWorld** as your extension name and press **Enter**.
 * Accept the default value of **HelloWorld description** as your extension description and press **Enter**.
 
-![Yeoman SharePoint generator prompts to create an extension solution](../../../../images/ext-com-yeoman-prompts.png)
+![Yeoman SharePoint generator prompts to create an extension solution](../../../images/ext-com-yeoman-prompts.png)
 
 At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** extension. This might take a few minutes. 
 
 When the scaffold is complete, you should see the following message indicating a successful scaffold:
 
-![SharePoint client-side solution scaffolded successfully](../../../../images/ext-com-yeoman-complete.png)
+![SharePoint client-side solution scaffolded successfully](../../../images/ext-com-yeoman-complete.png)
 
-For information about troubleshooting any errors, see [Known issues](../../web-parts/basics/known-issues).
+For information about troubleshooting any errors, see [Known issues](../../known-issues-and-common-questions.md).
 
 Once the solution scaffolding is completed, type the following into the console to start Visual Studio Code.
 
@@ -62,7 +69,7 @@ code .
 
 Notice how the default solution structure is like the solution structure of client-side web parts. This is the basic SharePoint Framework solution structure, with similar configuration options across all solution types.
 
-![SharePoint Framework solution opened after initial scaffolding](../../../../images/ext-com-vscode-solution-structure.png)
+![SharePoint Framework solution opened after initial scaffolding](../../../images/ext-com-vscode-solution-structure.png)
 
 Open **HelloWorldCommandSet.manifest.json** in the **src\extensions\helloWorld** folder.
 
@@ -70,7 +77,7 @@ This file defines your extension type and a unique identifier **“id”** for y
 
 Notice also the actual command definitions in the manifest file. These are the actual buttons which will be exposed based on the registration target. In the default template, you'll find two different buttons: *"Command One"* and *"Command Two"*
 
-![ListView Command Set manifest json content](../../../../images/ext-com-vscode-manifest.png)
+![ListView Command Set manifest json content](../../../images/ext-com-vscode-manifest.png)
 
 > Currently, images are not properly referenced unless you are referring to them from absolute locations in a CDN within your manifest. This will be improved in future releases.
 
@@ -169,11 +176,11 @@ contoso.sharepoint.com/Lists/Orders/AllItems.aspx?loadSpfx=true&debugManifestsFi
 
 Accept the loading of Debug Manifests, by clicking **Load debug scripts** when prompted.
 
-![Accept loading debug scripts](../../../../images/ext-com-accept-debug-scripts.png)
+![Accept loading debug scripts](../../../images/ext-com-accept-debug-scripts.png)
 
 Notice two new buttons available in the toolbar with titles of *Command One* and *Command Two*.
 
-![Accept loading debug scripts](../../../../images/ext-com-default-customizer-output.png)
+![Accept loading debug scripts](../../../images/ext-com-default-customizer-output.png)
 
 ## Enhancing the ListView Command Set rendering
 We'll take advantage of a new Dialog API, which can be used to show modal dialogs easily from your code. 
@@ -223,11 +230,11 @@ Return to the list view and use the same query parameters used previously with t
 
 Accept the loading of Debug Manifests, by clicking **Load debug scripts** when prompted.
 
-![Accept loading debug scripts](../../../../images/ext-com-accept-debug-scripts.png)
+![Accept loading debug scripts](../../../images/ext-com-accept-debug-scripts.png)
 
 We still have the same buttons in the toolbar, but you'll notice they behave differently if you click them one-by-one. Now we are using the new dialog API, which can be easily used with your solutions even for complex scenarios. 
 
-![Dialog shown in the page](../../../../images/ext-com-dialog-output.png)
+![Dialog shown in the page](../../../images/ext-com-dialog-output.png)
 
 ## Adding a ListView Command Set to a solution package for deployment
 
@@ -240,7 +247,7 @@ We'll first need to create an **assets** folder where we will place all feature
 
 Your solution structure should look similar to the following picture:
 
-![assets folder in solution structure](../../../../images/ext-com-assets-folder.png)
+![assets folder in solution structure](../../../images/ext-com-assets-folder.png)
 
 ### Add an elements.xml file for SharePoint definitions
 
@@ -347,7 +354,7 @@ Upload or drag and drop the `command-extension.sppkg` located in the **sharepoin
 
 Notice that we did not update the URLs for hosting the solution for this deployment, so the URL is still pointing to `https://localhost:4321`. Click the **Deploy** button.
 
-![Trust operation in app catalog upload](../../../../images/ext-com-sppkg-deploy-trust.png)
+![Trust operation in app catalog upload](../../../images/ext-com-sppkg-deploy-trust.png)
 
 Move back to your console and ensure that the solution is running. If it's not running, execute the following command in the solution folder:
 
@@ -361,16 +368,16 @@ Chose the gear icon on the top navigation bar on the right and choose **Add an a
 
 In the **Search** box, enter '**extension**' and press *Enter* to filter your apps.
 
-![installing the listview command set to a site](../../../../images/ext-com-install-solution-to-site.png)
+![installing the listview command set to a site](../../../images/ext-com-install-solution-to-site.png)
 
 Choose the **command-extension-client-side-solution** app to install the solution on the site. When the installation is completed, refresh the page by pressing **F5**.
 
 When the application has been successfully installed, Click **New** from the toolbar on the **Site Contents** page and choose **List**
 
-![Creating a new list](../../../../images/ext-com-create-new-list.png)
+![Creating a new list](../../../images/ext-com-create-new-list.png)
 
 Provide the name as **Sample** and click **Create**.
 
 Notice how **Command One** and **Command Two** are being rendered in the toolbar based on your ListView Command Set customizations. 
 
-![Addional buttons visible in the toolbar](../../../../images/ext-com-dialog-visible-deployment.png)
+![Addional buttons visible in the toolbar](../../../images/ext-com-dialog-visible-deployment.png)
diff --git a/docs/spfx/extensions/get-started/building-simple-field-customizer.md b/docs/spfx/extensions/get-started/building-simple-field-customizer.md
index 228fb8271b..83cc79b8d2 100644
--- a/docs/spfx/extensions/get-started/building-simple-field-customizer.md
+++ b/docs/spfx/extensions/get-started/building-simple-field-customizer.md
@@ -1,3 +1,10 @@
+---
+title: Build your first Field Customizer extension
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build your first Field Customizer extension
 
 >**Note:** The SharePoint Framework Extensions are currently in preview and are subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
@@ -7,7 +14,7 @@ Extensions are client-side components that run inside the context of a SharePoin
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=fijOzUmlXrY&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
 
 <a href="https://www.youtube.com/watch?v=fijOzUmlXrY&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorialfield.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorialfield.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Create an extension project
@@ -43,15 +50,15 @@ The next set of prompts will ask for specific information about your extension:
 * Accept the default value of **HelloWorld description** as your extension description and press **Enter**.
 * Accept the default **No JavaScript Framework** as the framework selection and press **Enter** 
 
-![Yeoman SharePoint generator prompts to create an extension solution](../../../../images/ext-field-yeoman-prompts.png)
+![Yeoman SharePoint generator prompts to create an extension solution](../../../images/ext-field-yeoman-prompts.png)
 
 At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** extension. This might take a few minutes. 
 
 When the scaffold is complete, you should see the following message indicating a successful scaffold:
 
-![SharePoint client-side solution scaffolded successfully](../../../../images/ext-field-yeoman-complete.png)
+![SharePoint client-side solution scaffolded successfully](../../../images/ext-field-yeoman-complete.png)
 
-For information about troubleshooting any errors, see [Known issues](../basics/known-issues).
+For information about troubleshooting any errors, see [Known issues](../../known-issues-and-common-questions.md).
 
 Once the solution scaffolding is completed, type the following into the console to start Visual Studio Code.
 
@@ -63,13 +70,13 @@ code .
 
 Notice how the default solution structure is like the solution structure of client-side web parts. This is the basic SharePoint Framework solution structure with similar configuration options across all solution types.
 
-![SharePoint Framework solution opened after initial scaffolding](../../../../images/ext-field-vscode-solution-structure.png)
+![SharePoint Framework solution opened after initial scaffolding](../../../images/ext-field-vscode-solution-structure.png)
 
 Open **HelloWorldFieldCustomizer.manifest.json** at the **src\extensions\helloWorld** folder.
 
 This file defines your extension type and a unique identifier **“id”** for your extension. You’ll need this unique identifier later when debugging and deploying your extension to SharePoint.
 
-![Application customizer manifest json content](../../../../images/ext-field-vscode-manifest.png)
+![Application customizer manifest json content](../../../images/ext-field-vscode-manifest.png)
 
 ## Coding your Field Customizer 
 Open the **HelloWorldFieldCustomizer.ts** file in the **src\extensions\helloWorld** folder.
@@ -125,7 +132,7 @@ Notice that we used the `--nobrowser` option, since there's no value in launchin
 
 Once it compiles the code without errors, it will serve the resulting manifest from https://localhost:4321.
 
-![gulp serve](../../../../images/ext-field-gulp-serve.png)
+![gulp serve](../../../images/ext-field-gulp-serve.png)
 
 To test your extension, navigate to a site in your SharePoint Online tenant.
 
@@ -133,23 +140,23 @@ Move to the **Site Contents** page.
 
 Click **New** from the toolbar and choose **List**:
 
-![Creating a new list](../../../../images/ext-field-create-new-list.png)
+![Creating a new list](../../../images/ext-field-create-new-list.png)
 
 Create a new list named *Orders* and click **Create**:
 
-![Creating a new list with name of Orders](../../../../images/ext-field-create-new-list-order.png)
+![Creating a new list with name of Orders](../../../images/ext-field-create-new-list-order.png)
 
 Click the **plus** sign and choose **Number** to create a new Number field for the list:
 
-![Creating a new Number field](../../../../images/ext-field-new-number-field.png)
+![Creating a new Number field](../../../images/ext-field-new-number-field.png)
 
 Set name of the field to **Percent** and click **Save**:
 
-![Creating a new field called Percent](../../../../images/ext-field-new-number-field-percent.png)
+![Creating a new field called Percent](../../../images/ext-field-new-number-field-percent.png)
 
 Add a few items with different numbers in the percent field. We'll modify the rendering later in this tutorial, so the different numbers will be presented differently based on your custom implementation.
 
-![Creating items in the newly created list with different values in the Percent field](../../../../images/ext-field-create-items-to-list.png)
+![Creating items in the newly created list with different values in the Percent field](../../../images/ext-field-create-items-to-list.png)
 
 Since our Field Customizer is still hosted in localhost and is running, we can use specific debug query parameters to execute the code in the newly created list.
 
@@ -175,11 +182,11 @@ contoso.sharepoint.com/Lists/Orders/AllItems.aspx?loadSPFX=true&debugManifestsFi
 
 Accept the loading of Debug Manifests, by clicking **Load debug scripts** when prompted:
 
-![Accept loading debug scripts](../../../../images/ext-field-accept-debug-scripts.png)
+![Accept loading debug scripts](../../../images/ext-field-accept-debug-scripts.png)
 
 Notice how the Percent values are now presented with additional [ ] characters:
 
-![Accept loading debug scripts](../../../../images/ext-field-default-customizer-output.png)
+![Accept loading debug scripts](../../../images/ext-field-default-customizer-output.png)
 
 ## Enhancing the Field Customizer rendering
 Now that we have successfully tested the out of the box starting point of the Field Customizer, let's modify the logic slightly to have a more polished rendering of the field value. 
@@ -224,11 +231,11 @@ Move back to your previously created list and use the same query parameter as us
 
 Accept the loading of Debug Manifests, by clicking **Load debug scripts** when prompted.
 
-![Accept loading debug scripts](../../../../images/ext-field-accept-debug-scripts.png)
+![Accept loading debug scripts](../../../images/ext-field-accept-debug-scripts.png)
 
 Notice how we have changed the field rendering style completely. The field value is indicated using a graphical representation of the value.
 
-![Graphical Representation of Percent](../../../../images/ext-field-percent-field-graphic.png)
+![Graphical Representation of Percent](../../../images/ext-field-percent-field-graphic.png)
 
 ## Add the field definition to the solution package for deployment
 Now that we have tested our solution properly in debug mode, we can package this to be deployed automatically as part of the solution package deployed to the sites. There are few things to take care of here.
@@ -251,7 +258,7 @@ We'll first need to create an **assets** folder where we will place all feature
 
 Your solution structure should look similar to the following picture:
 
-![assets folder in solution structure](../../../../images/ext-field-assets-folder.png)
+![assets folder in solution structure](../../../images/ext-field-assets-folder.png)
 
 ### Add an elements.xml file for SharePoint definitions
 Create a new file inside the **sharepoint\assets** folder named **elements.xml**
@@ -352,7 +359,7 @@ Upload or drag and drop the `field-extension.sppkg` located in the **sharepoint/
 
 Notice that we did not update the URLs for hosting the solution for this deployment, so the URL is still pointing to https://localhost:4321. Click the **Deploy** button.
 
-![Deploy Dialog](../../../../images/ext-field-sppkg-deploy-trust.png)
+![Deploy Dialog](../../../images/ext-field-sppkg-deploy-trust.png)
 
 Go to the site where you want to test SharePoint asset provisioning. This could be any site collection in the tenant where you deployed this solution package.
 
@@ -360,25 +367,25 @@ Choose the gears icon on the top navigation bar on the right and choose **Add an
 
 In the **Search** box, enter '**field**' and press *Enter* to filter your apps.
 
-![installing field customizer to site](../../../../images/ext-field-install-solution-to-site.png)
+![installing field customizer to site](../../../images/ext-field-install-solution-to-site.png)
 
 Choose the **field-extension-client-side-solution** app to install the solution on the site. Once the installation is completed, refresh the page by pressing **F5**.
 
 When the solution has been installed, Click **New** from the toolbar in **Site Contents** page and choose **List**:
 
-![Creating a new list](../../../../images/ext-field-create-new-list.png)
+![Creating a new list](../../../images/ext-field-create-new-list.png)
 
 Create a list named **Invoices**:
 
 When the new list has been created, move back to the **Site Contents** page and choose **Settings** from the context menu of the just created list:
 
-![List settings for the new list](../../../../images/ext-field-list-settings.png)
+![List settings for the new list](../../../images/ext-field-list-settings.png)
 
 Choose **Add from existing site columns** under the **Columns** section:
 
 Choose the **Percentage** field which was provisioned from the solution package, under the **SPFx Columns** group:
 
-![List settings for the new list](../../../../images/ext-field-add-field-to-list.png)
+![List settings for the new list](../../../images/ext-field-add-field-to-list.png)
 
 Click **OK**.
 
@@ -389,7 +396,7 @@ gulp serve --nobrowser
 ```
 Navigate to the newly created **Invoices** list and add a few new items to the list with different values in the Percentage column to see how the field is being rendered without the Debug query parameters.
 
-![Field Rendering without Debug Query Parameters](../../../../images/ext-field-render-field-without-debug.png)
+![Field Rendering without Debug Query Parameters](../../../images/ext-field-render-field-without-debug.png)
 
 In this case, we continued to host the JavaScript from the localhost, but you could just as well relocate the assets to any CDN and update the URL to enable the loading of the JavaScript assets outside of the localhost as well. 
 
diff --git a/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md b/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
index 3d398513bc..8ec94db910 100644
--- a/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
+++ b/docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
@@ -1,3 +1,10 @@
+---
+title: Hosting extension from Office 365 CDN (Hello world part 4)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Hosting extension from Office 365 CDN (Hello world part 4)
 
 >**Note:** The SharePoint Framework Extensions are currently in preview and are subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
@@ -13,7 +20,7 @@ Be sure you have completed the procedures in the following articles before you s
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=oOIHWamPr34&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
 
 <a href="https://www.youtube.com/watch?v=oOIHWamPr34&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorial4.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorial4.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Using the CDN in your Office 365 tenant
@@ -43,7 +50,7 @@ Open up a browser and move to a site collection where you'd like to host your CD
 
 Create a new document library on your site collection called **CDN** and add a folder named **helloworld** to it.
 
-![helloworld-extension folder in CDN library](../../../../images/ext-app-cdn-folder-created.png) 
+![helloworld-extension folder in CDN library](../../../images/ext-app-cdn-folder-created.png) 
 
 Move back to the PowerShell console and add a new CDN origin. In this case, we are setting the origin as `*/cdn`, which means that any relative folder with the name of **cdn** will act as a CDN origin.
 ```
@@ -55,7 +62,7 @@ Get-SPOTenantCdnOrigins -CdnType Public
 ```
 Notice that your newly added origin is listed as a valid CDN origin. Final configuration of the origin will take a while (approximately 15 minutes), so we can continue creating your test extension, which will be hosted from the origin once deployment is completed. 
 
-![List of public origins in tenant](../../../../images/ext-app-cdn-origins-pending.png)
+![List of public origins in tenant](../../../images/ext-app-cdn-origins-pending.png)
 
 > When origin is listed without the *(configuration pending)* text, it is ready to be used in your tenant. This is the indication of an on-going configuration between SharePoint Online and the CDN system. 
 
@@ -74,7 +81,7 @@ Update the *write-manifests.json* file (under the *config* folder) as follows to
 https://publiccdn.sharepointonline.com/<tenant host name>/sites/site/library/folder
 ```
 
-![Updated write manifest content with path to CDN endpoint](../../../../images/ext-app-cdn-write-manifest.png)
+![Updated write manifest content with path to CDN endpoint](../../../images/ext-app-cdn-write-manifest.png)
 
 Save your changes.
 
@@ -96,12 +103,12 @@ This command will create an **app-extension.sppkg** package in the **sharepoint/
 
 Upload or drag & drop the newly created client-side solution package to the app catalog in your tenant. Click the **Deploy** button.
 
-![App Catalog Trust Dialog with path to CDN endpoint](../../../../images/ext-app-approve-cdn-address.png)
+![App Catalog Trust Dialog with path to CDN endpoint](../../../images/ext-app-approve-cdn-address.png)
 
 Upload or drag & drop the files in the **temp/deploy** folder to the **CDN/helloworld** folder created earlier.
 
 Install the new version of the solution to your site and ensure that it's working properly without your *locahost* hosting the JavaScript file.
 
-![Custom header and footer elements rendered in the page](../../../../images/ext-app-header-footer-visible.png)
+![Custom header and footer elements rendered in the page](../../../images/ext-app-header-footer-visible.png)
 
 Congratulations, you have enabled a public CDN in your Office 365 tenant and taken advantage of it from your solution!
diff --git a/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md b/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md
index c0f4c1d05d..3025f8d697 100644
--- a/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md
+++ b/docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md
@@ -1,3 +1,10 @@
+---
+title: Deploy your extension to SharePoint (Hello world part 3)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 
 # Deploy your extension to SharePoint (Hello world part 3)
 
@@ -13,7 +20,7 @@ Be sure you have completed the procedures in the following articles before you b
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=P_yWI0WVQIg&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV). 
 
 <a href="https://www.youtube.com/watch?v=P_yWI0WVQIg&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorial3.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorial3.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Package the helloWorld Application Customizer
@@ -46,7 +53,7 @@ We'll first need to create an **assets** folder where we will place all feature
 
 Your solution structure should look similar to the following picture:
 
-![assets folder in solution structure](../../../../images/ext-app-assets-folder.png)
+![assets folder in solution structure](../../../images/ext-app-assets-folder.png)
 
 ### Add an elements.xml file for SharePoint definitions
 
@@ -150,7 +157,7 @@ Upload or drag and drop the `app-extension.sppkg` located in the **sharepoint/so
 
 Notice that we did not update the URLs for hosting the solution for this deployment, so the URL is still pointing to `https://localhost:4321`. Click the **Deploy** button.
 
-![Trust operation in app catalog upload](../../../../images/ext-app-sppkg-deploy-trust.png)
+![Trust operation in app catalog upload](../../../images/ext-app-sppkg-deploy-trust.png)
 
 Move back to your console and ensure that the solution is running. If it's not running, execute the following command in the solution folder:
 
@@ -164,13 +171,13 @@ Choose the gear icon on the top navigation bar on the right and choose **Add an
 
 In the **Search** box, enter '**app**' and press *Enter* to filter your apps.
 
-![installing field customizer to site](../../../../images/ext-app-install-solution-to-site.png)
+![installing field customizer to site](../../../images/ext-app-install-solution-to-site.png)
 
 Choose the **app-extension-client-side-solution** app to install the solution on the site. When the installation is completed, refresh the page by pressing **F5**.
 
 When the application has been successfully installed, you can see the header and footer being rendered just like with the debug query parameters.
 
-![Custom header and footer elements rendered in the page](../../../../images/ext-app-header-footer-visible.png)
+![Custom header and footer elements rendered in the page](../../../images/ext-app-header-footer-visible.png)
 
 ## Next steps
 
diff --git a/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md b/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md
index c241431e60..334ec95d6c 100644
--- a/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md
+++ b/docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md
@@ -1,20 +1,31 @@
-# Use page placeholders from Application Customizer (Hello World part 2)
+---
+title: Using page placeholders from Application Customizer (Hello World part 2)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
 
->**Note:** SharePoint Framework Extensions are currently in preview and are subject to change. They are not currently supported for use in production environments.
 
-Application Customizers provide access to well-known locations on SharePoint pages that you can modify based on your business and functional requirements. For example, you can create dynamic header and footer experiences that render across all the pages in SharePoint Online. 
+# Using page placeholders from Application Customizer (Hello World part 2)
 
-This model is similar to using a **UserCustomAction** collection in a **Site** or **Web** object to modify the page experience via custom JavaScript. The key difference or advantage with SharePoint Framework (SPFx) Extensions is that your page elements won't change if changes are made to the HTML/DOM structure in SharePoint Online.
+>**Note:** The SharePoint Framework Extensions are currently in preview and are subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
 
-This article describes how to extend your [Hello World extension](./build-a-hello-world-extension.md) to take advantage of page placeholders. You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=ipRw6o6bOTw&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV).
+Application Customizers also provide access to well known locations in the page, which you can modify based on your business and functional requirements. Typical scenarios would be dynamic header and footer experiences, which would be visible across all the pages in SharePoint Online. 
+
+This model is similar to using a UserCustomAction collection in a Site or Web object to associate custom JavaScript to modify the page experience. The key difference or advantage with SPFx extensions is that you have guaranteed elements on the page regardless of any HTML/DOM structure modifications in future changes to SharePoint Online.
+
+In this article, we'll continue extending the hello world extension built in the previous article [Build your first SharePoint Framework Extension (Hello World part 1)](./build-a-hello-world-extension.md) to take advantage of the page placeholders.
+
+You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=ipRw6o6bOTw&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV).
 
 <a href="https://www.youtube.com/watch?v=ipRw6o6bOTw&list=PLR9nK3mnD-OXtWO5AIIr7nCR3sWutACpV">
-<img src="../../../../images/spfx-ext-youtube-tutorial2.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-ext-youtube-tutorial2.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
-## Get access to page placeholders
+## Getting access to page placeholders
 
-Application Customizer extensions are supported with `Site`, `Web`, and `List` scopes. You can control the scope by deciding where or how the Application Customizer will be registered in your SharePoint tenant. When the Application Customizer exists in the scope and is being rendered, you can use the following method to get access to the placeholder. 
+Application Customizer extensions are supported with `Site`, `Web` and `List` scopes. You can control the scope by deciding where or how the Application Customizer will be registered in your SharePoint tenant. When the Application Customizer exists in the scope and is being rendered, you can use the following method to get access to the placeholder. Once you have received the placeholder object, you have full control over what will be presented to the end user.
+
+Notice that we are requesting a well-known placeholder by using the corresponding well-known identifier. In this case, the code is accessing the footer section of the page using the `Bottom` identifier. 
 
 ```ts
     // Handling the Bottom placeholder
@@ -27,227 +38,217 @@ Application Customizer extensions are supported with `Site`, `Web`, and `List` s
     }
 ```
 
-After you get the placeholder object, you have full control over what will be presented to the end user.
+In the following steps, we'll modify the previously created hello world Application Customizer to access placeholders and modify their content by adding custom html elements to them.
+
+Switch to Visual Studio Code (or your preferred IDE) and open **src\extensions\helloWorld\HelloWorldApplicationCustomizer.ts.**
+
+Add the `PlaceholderContent` and `PlaceholderName` to the import from `@microsoft/sp-application-base` by updating the import statement as follows:
+
+```ts
+import {
+  BaseApplicationCustomizer, 
+  PlaceholderContent,
+  PlaceholderName
+} from '@microsoft/sp-application-base';
+```
+
+Also add the following import statements after the `strings` import at the top of the file:
+
+* We will create style definitions for the output in the following steps
+* `escape` is used to escape Application Customizer properties  
+
+```ts
+import styles from './AppCustomizer.module.scss';
+import { escape } from '@microsoft/sp-lodash-subset'; 
+```
+
+Create a new file named **AppCustomizer.module.scss** under the **src\extensions\helloWorld** folder. 
+
+Update **AppCustomizer.module.scss** as follows:
+
+* These are the styles that will be used within the outputed html for the header and footer placeholders.
+
+```css
+.app {
+  .top {
+    height:60px;
+    text-align:center;
+    line-height:2.5;
+    font-weight:bold;
+    display: flex;
+    align-items: center;
+    justify-content: center;
+  }
+
+  .bottom {
+    height:40px;
+    text-align:center;
+    line-height:2.5;
+    font-weight:bold;
+    display: flex;
+    align-items: center;
+    justify-content: center;
+  }
+}
+```
+
+Move back to **HelloWorldApplicationCustomizer.ts** and update the **IHelloWorldApplicationCustomizerProperties** interface to have specific properties for Header and Footer as follows.
+
+* If your command set uses the ClientSideComponentProperties JSON input, it will be deserialized into the `BaseExtension.properties` object. You can define an interface to describe it.
+
+```ts
+export interface IHelloWorldApplicationCustomizerProperties {
+  Top: string;
+  Bottom: string;
+}
+```
+
+Add the following private variables inside of the **HelloWorldApplicationCustomizer** class. In this scenario, these could just be local variables in an `onRender` method, but if you want to share them with other objects you define them as private variables. 
+
+```ts
+export default class HelloWorldApplicationCustomizer
+  extends BaseApplicationCustomizer<IHelloWorldApplicationCustomizerProperties> {
+  
+  // These have been added
+  private _topPlaceholder: PlaceholderContent | undefined;
+  private _bottomPlaceholder: PlaceholderContent | undefined;
+```
+
+Update `onInit` method code as follows:
+
+```ts
+  @override
+  public onInit(): Promise<void> {
+    Log.info(LOG_SOURCE, `Initialized ${strings.Title}`);
+
+    // Added to handle possible changes on the existence of placeholders
+    this.context.placeholderProvider.changedEvent.add(this, this._renderPlaceHolders);
+
+    // Call render method for generating the needed html elements
+    this._renderPlaceHolders();
+    return Promise.resolve<void>();
+  }
+```
+
+
+Create new `_renderPlaceHolders` private method with the following code:
 
-Notice that you're requesting a well-known placeholder by using the corresponding well-known identifier. In this case, the code is accessing the footer section of the page using the `Bottom` identifier. 
+* We use `this.context.placeholderProvider.tryCreateContent` to get access on the placeholder
+* Extension code should not assume that the expected placeholder is available
+* The code expects custom properties called `Top` and `Bottom`. If the properties exist, they will be rendered inside of the placeholders.
+* Notice that the code path for both the top and the bottom placeholders is almost identical in the below method. The only differences are the variables used and the style definitions.
 
-In the following steps, you'll modify the Hello World Application Customizer to access and modify placeholders by adding custom HTML elements.
+```ts
+   private _renderPlaceHolders(): void {
 
-1. In Visual Studio Code (or your preferred IDE), open **src\extensions\helloWorld\HelloWorldApplicationCustomizer.ts.**
+    console.log('HelloWorldApplicationCustomizer._renderPlaceHolders()');
+    console.log('Available placeholders: ',
+      this.context.placeholderProvider.placeholderNames.map(name => PlaceholderName[name]).join(', '));
 
-2. Add the `PlaceholderContent` and `PlaceholderName` to the import from `@microsoft/sp-application-base` by updating the import statement as follows:
+    // Handling the top placeholder
+    if (!this._topPlaceholder) {
+      this._topPlaceholder =
+        this.context.placeholderProvider.tryCreateContent(
+          PlaceholderName.Top,
+          { onDispose: this._onDispose });
 
-	```ts
-	import {
-	  BaseApplicationCustomizer, 
-	  PlaceholderContent,
-	  PlaceholderName
-	} from '@microsoft/sp-application-base';
-	```
-	
-	  Also add the following import statements after the `strings` import at the top of the file:
+      // The extension should not assume that the expected placeholder is available.
+      if (!this._topPlaceholder) {
+        console.error('The expected placeholder (Top) was not found.');
+        return;
+      }
+
+      if (this.properties) {
+        let topString: string = this.properties.Top;
+        if (!topString) {
+          topString = '(Top property was not defined.)';
+        }
+
+        if (this._topPlaceholder.domElement) {
+          this._topPlaceholder.domElement.innerHTML = `
+                <div class="${styles.app}">
+                  <div class="ms-bgColor-themeDark ms-fontColor-white ${styles.top}">
+                    <i class="ms-Icon ms-Icon--Info" aria-hidden="true"></i> ${escape(topString)}
+                  </div>
+                </div>`;
+        }
+      }
+    }
 
+    // Handling the bottom placeholder
+    if (!this._bottomPlaceholder) {
+      this._bottomPlaceholder =
+        this.context.placeholderProvider.tryCreateContent(
+          PlaceholderName.Bottom,
+          { onDispose: this._onDispose });
 
-	    ```ts
-	    import styles from './AppCustomizer.module.scss';
-	    import { escape } from '@microsoft/sp-lodash-subset'; 
-	    ```
+      // The extension should not assume that the expected placeholder is available.
+      if (!this._bottomPlaceholder) {
+        console.error('The expected placeholder (Bottom) was not found.');
+        return;
+      }
+
+      if (this.properties) {
+        let bottomString: string = this.properties.Bottom;
+        if (!bottomString) {
+          bottomString = '(Bottom property was not defined.)';
+        }
+
+        if (this._bottomPlaceholder.domElement) {
+          this._bottomPlaceholder.domElement.innerHTML = `
+                <div class="${styles.app}">
+                  <div class="ms-bgColor-themeDark ms-fontColor-white ${styles.bottom}">
+                    <i class="ms-Icon ms-Icon--Info" aria-hidden="true"></i> ${escape(bottomString)}
+                  </div>
+                </div>`;
+        }
+      }
+    }
+  }
 
-	  You use `escape` to escape Application Customizer properties. You'll create style definitions for the output in the following steps.  
+```
 
-3. Create a new file named **AppCustomizer.module.scss** under the **src\extensions\helloWorld** folder. 
+Add the following method after the `_renderPlaceHolders` method. In this case, we simply output a console message, when the extension is removed from the page. 
 
-4. Update **AppCustomizer.module.scss** as follows:
+```ts
+  private _onDispose(): void {
+    console.log('[HelloWorldApplicationCustomizer._onDispose] Disposed custom top and bottom placeholders.');
+  }
+```
 
-	>**Note:** These are the styles that will be used in the HTML output for the header and footer placeholders.
+The code is now ready to be tested in SharePoint Online.
 
-	  ```css
-	  .app {
-	    .top {
-	      height:60px;
-	      text-align:center;
-	      line-height:2.5;
-	      font-weight:bold;
-	      display: flex;
-	      align-items: center;
-	      justify-content: center;
-	    }
+Switch to the console window that is running `gulp serve` and check if there are any errors. If there are errors, gulp reports them in the console and you will need to fix them before proceeding.
 
-	    .bottom {
-	      height:40px;
-	      text-align:center;
-	      line-height:2.5;
-	      font-weight:bold;
-	      display: flex;
-	      align-items: center;
-	      justify-content: center;
-	    }
-	  }
-	  ```
-
-5. In the **HelloWorldApplicationCustomizer.ts** file, update the **IHelloWorldApplicationCustomizerProperties** interface to add specific properties for Header and Footer, as follows.
-
-	  **Note:** If your command set uses the ClientSideComponentProperties JSON input, it will be deserialized into the `BaseExtension.properties` object. You can define an interface to describe it.
-
-	```ts
-	export interface IHelloWorldApplicationCustomizerProperties {
-	  Top: string;
-	  Bottom: string;
-	}
-	```
-
-6. Add the following private variables inside the **HelloWorldApplicationCustomizer** class. In this scenario, these can just be local variables in an `onRender` method, but if you want to share them with other objects,  define them as private variables. 
-
-	  ```ts
-	  export default class HelloWorldApplicationCustomizer
-	    extends BaseApplicationCustomizer<IHelloWorldApplicationCustomizerProperties> {
-
-	    // These have been added
-	    private _topPlaceholder: PlaceholderContent | undefined;
-	    private _bottomPlaceholder: PlaceholderContent | undefined;
-  	```
-
-7. Update the `onInit` method code as follows:
-
-	  ```ts
-	    @override
-	    public onInit(): Promise<void> {
-	      Log.info(LOG_SOURCE, `Initialized ${strings.Title}`);
-
-	      // Added to handle possible changes on the existence of placeholders.
-	      this.context.placeholderProvider.changedEvent.add(this, this._renderPlaceHolders);
-
-	      // Call render method for generating the HTML elements.
-	      this._renderPlaceHolders();
-	      return Promise.resolve<void>();
-	    }
-	  ```
-
-
-8. Create a new `_renderPlaceHolders` private method with the following code:
-
-
-
-	  ```ts
-	    private _renderPlaceHolders(): void {
-
-	      console.log('HelloWorldApplicationCustomizer._renderPlaceHolders()');
-	      console.log('Available placeholders: ',
-		this.context.placeholderProvider.placeholderNames.map(name => PlaceholderName[name]).join(', '));
-
-	      // Handling the top placeholder
-	      if (!this._topPlaceholder) {
-		this._topPlaceholder =
-		  this.context.placeholderProvider.tryCreateContent(
-		    PlaceholderName.Top,
-		    { onDispose: this._onDispose });
-
-		// The extension should not assume that the expected placeholder is available.
-		if (!this._topPlaceholder) {
-		  console.error('The expected placeholder (Top) was not found.');
-		  return;
-		}
-
-		if (this.properties) {
-		  let topString: string = this.properties.Top;
-		  if (!topString) {
-		    topString = '(Top property was not defined.)';
-		  }
-
-		  if (this._topPlaceholder.domElement) {
-		    this._topPlaceholder.domElement.innerHTML = `
-			  <div class="${styles.app}">
-			    <div class="ms-bgColor-themeDark ms-fontColor-white ${styles.top}">
-			      <i class="ms-Icon ms-Icon--Info" aria-hidden="true"></i> ${escape(topString)}
-			    </div>
-			  </div>`;
-		  }
-		}
-	      }
-
-	      // Handling the bottom placeholder
-	      if (!this._bottomPlaceholder) {
-		this._bottomPlaceholder =
-		  this.context.placeholderProvider.tryCreateContent(
-		    PlaceholderName.Bottom,
-		    { onDispose: this._onDispose });
-
-		// The extension should not assume that the expected placeholder is available.
-		if (!this._bottomPlaceholder) {
-		  console.error('The expected placeholder (Bottom) was not found.');
-		  return;
-		}
-
-		if (this.properties) {
-		  let bottomString: string = this.properties.Bottom;
-		  if (!bottomString) {
-		    bottomString = '(Bottom property was not defined.)';
-		  }
-
-		  if (this._bottomPlaceholder.domElement) {
-		    this._bottomPlaceholder.domElement.innerHTML = `
-			  <div class="${styles.app}">
-			    <div class="ms-bgColor-themeDark ms-fontColor-white ${styles.bottom}">
-			      <i class="ms-Icon ms-Icon--Info" aria-hidden="true"></i> ${escape(bottomString)}
-			    </div>
-			  </div>`;
-		  }
-		}
-	      }
-	    }
-
-	  ```
-
-	  * Use `this.context.placeholderProvider.tryCreateContent` to get access to the placeholder.
-	  * Extension code should not assume that the expected placeholder is available.
-	  * The code expects custom properties called `Top` and `Bottom`. If the properties exist, they will render inside the placeholders.
-	  * Notice that the code path for both the top and the bottom placeholders is almost identical. The only differences are the variables used and the style definitions.
-
-9. Add the following method after the `_renderPlaceHolders` method. In this case, you simply output a console message when the extension is removed from the page. 
-
-	  ```ts
-	    private _onDispose(): void {
-	      console.log('[HelloWorldApplicationCustomizer._onDispose] Disposed custom top and bottom placeholders.');
-	    }
-	  ```
-
-You're now ready to test your code in SharePoint Online.
-
-## Test your code
-
-Switch to the console window that is running `gulp serve` and check for errors. Gulp reports any errors in the console; you'll need to fix them before you proceed.
-
-If you don't have the solution running, use the following command to check for errors.
+If you don't have the solution running currently, execute the following command and ensure you don't have any errors.
 
 ```
 gulp serve --nobrowser
 ```
 
-Go to a modern list in SharePoint Online. This can be a list or a library. 
+Navigate to an out of the box modern list in SharePoint Online. This can be a list or a library for the initial testing. 
 
 To test your extension, append the following query string parameters to the URL:
 
+* Notice that the GUID used in this query parameter has to match on the ID attribute of your Application Customizer available from **HelloWorldApplicationCustomizer.manifest.json**.
+* We also use Header and Footer JSON properties to provide parameters or configurations to the Application Customizer. In this case, we simply output these values, but you could adjust the behavior based on the properties in actual production usage. 
 
 ```
 ?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js&customActions={"e5625e23-5c5a-4007-a335-e6c2c3afa485":{"location":"ClientSideExtension.ApplicationCustomizer","properties":{"Top":"Top area of the page","Bottom":"Bottom area in the page"}}}
 ```
-
-* Notice that the GUID used in this query parameter has to match on the ID attribute of your Application Customizer. This is available in the **HelloWorldApplicationCustomizer.manifest.json** file.
-* You use Header and Footer JSON properties to provide parameters or configurations to the Application Customizer. In this case, you simply output these values. You can also adjust the behavior based on the properties used in production. 
-
-The full URL should look similar to the following:
+The full URL to request would be something like the following:
 
 ```
 contoso.sharepoint.com/Lists/Contoso/AllItems.aspx?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js&customActions={"e5625e23-5c5a-4007-a335-e6c2c3afa485":{"location":"ClientSideExtension.ApplicationCustomizer","properties":{"Top":"Top area of the page","Bottom":"Bottom area in the page"}}}
 ```
 
-Choose **Load debug scripts** to continue loading scripts from your local host.
+![Allow Debug Manifest question from the page](../../../images/ext-app-debug-manifest-message.png)
 
-![Allow Debug Manifest question from the page](../../../../images/ext-app-debug-manifest-message.png)
+Click the "**Load debug scripts**" button to continue loading scripts from your local host.
 
 You should now see the custom header and footer content in your page. 
 
-![Custom header and footer elements rendered in the page](../../../../images/ext-app-header-footer-visible.png)
+![Custom header and footer elements rendered in the page](../../../images/ext-app-header-footer-visible.png)
 
 ## Next steps
-Congratulations, you've built your own custom header and footer using the Application Customizer! To continue building out your extension, see [Deploy your extension to SharePoint (Hello World part 3)](./serving-your-extension-from-sharepoint.md). You will learn how to deploy and preview the Hello World extension in a SharePoint site collection without using **Debug** query parameters. 
+Congratulations on building your own custom header and footer using the Application Customizer! You can continue building out your Hello World Extension in the next topic [Deploy your extension to site collection (Hello world part 3)](./serving-your-extension-from-sharepoint.md). You will learn how to deploy and preview the Hello World extension in a SharePoint site collection without using **Debug** query parameters. 
diff --git a/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md b/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md
index 39248939bd..bff1e08b62 100644
--- a/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md
+++ b/docs/spfx/extensions/guidance/using-custom-dialogs-with-spfx.md
@@ -1,3 +1,10 @@
+---
+title: Use custom dialog boxes with SharePoint Framework Extensions
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use custom dialog boxes with SharePoint Framework Extensions
 
 You can use custom dialog boxes, available from the **@microsoft/sp-dialog** package, within the context of SharePoint Framework Extensions or client-side web parts. 
@@ -54,15 +61,15 @@ The next set of prompts will ask for specific information about your extension:
 * Use the value of **DialogDemo** as your extension name and press **Enter**.
 * Accept the default value of **DialogDemo description** as your extension description and press **Enter**.
 
-![Yeoman SharePoint generator prompts to create an extension solution](../../../../images/ext-com-dialog-yeoman-prompts.png)
+![Yeoman SharePoint generator prompts to create an extension solution](../../../images/ext-com-dialog-yeoman-prompts.png)
 
 At this point, Yeoman will install the required dependencies and scaffold the solution files along with the *DialogDemo* extension. This might take a few minutes. 
 
 When the scaffold is complete, you should see the following message indicating a successful scaffold:
 
-![SharePoint client-side solution scaffolded successfully](../../../../images/ext-com-dialog-yeoman-complete.png)
+![SharePoint client-side solution scaffolded successfully](../../../images/ext-com-dialog-yeoman-complete.png)
 
->**Note:** For information about troubleshooting any errors, see [Known issues](../basics/known-issues).
+>**Note:** For information about troubleshooting any errors, see [Known issues](../../known-issues-and-common-questions.md).
 
 When the scaffolding is complete, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots, but you can use any editor you prefer. To open the folder in Visual Studio Code, use the following command in the console:
 
@@ -70,7 +77,7 @@ When the scaffolding is complete, open your project folder in your code editor.
 code .
 ```
 
-![Initial Visual Studio Code structure after scaffolding](../../../../images/ext-com-dialog-vs-code-initial.png)
+![Initial Visual Studio Code structure after scaffolding](../../../images/ext-com-dialog-vs-code-initial.png)
 
 ## Modify the extension manifest
 
@@ -270,16 +277,16 @@ Append the following query string parameters to the URL. Notice that you will ne
 
 Accept the loading of Debug Manifests by choosing **Load debug scripts** when prompted.
 
-![Allow debug scripts warning](../../../../images/ext-com-dialog-debug-scripts.png)
+![Allow debug scripts warning](../../../images/ext-com-dialog-debug-scripts.png)
 
 Notice that the new button is visible in the toolbar of the list with the text *Open Custom Dialog box*.
 
-![Open Cusotm Dialog button visible in the toolbar](../../../../images/ext-com-dialog-button-in-toolbar.png)
+![Open Cusotm Dialog button visible in the toolbar](../../../images/ext-com-dialog-button-in-toolbar.png)
 
 Choose the *Open Custom Dialog box* button to see your custom dialog box rendered within the list view. 
 
-![Color Picker rendered in dialog mode](../../../../images/ext-com-dialog-visible-dialog.png)
+![Color Picker rendered in dialog mode](../../../images/ext-com-dialog-visible-dialog.png)
 
 Choose a color in the *Color Picker* and choose **OK** to test how the code is returning the selected value back to the caller. The selection is then shown using the default alert dialog box.
 
-![Dialog with picked color details](../../../../images/ext-com-dialog-oob-alert-dialog.png)
+![Dialog with picked color details](../../../images/ext-com-dialog-oob-alert-dialog.png)
diff --git a/docs/spfx/extensions/overview-extensions.md b/docs/spfx/extensions/overview-extensions.md
index 0653e0ff39..48410f2df1 100644
--- a/docs/spfx/extensions/overview-extensions.md
+++ b/docs/spfx/extensions/overview-extensions.md
@@ -1,3 +1,10 @@
+---
+title: Overview of SharePoint Framework Extensions (preview)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Overview of SharePoint Framework Extensions (preview)
 
 You can use SharePoint Framework Extensions to extend the SharePoint user experience. With SharePoint Frameword Extensions, you can customize more facets of the SharePoint experience, including notification areas, toolbars, and list data views. SharePoint Framework Extensions are available for testing in first release tenants and in Office 365 developer tenants as part of the release candidate release. 
@@ -15,7 +22,7 @@ SharePoint Framework Extensions enable you to extend the SharePoint user experie
 You can build extensions alongside common scripting frameworks, such as AngularJS and React, in addition to plain JavaScript projects. For example, you can use React along with components from Office UI Fabric React to create experiences based on the same components used in Office 365.
 
 ## Get started
-If you haven't installed the SharePoint Framework, follow the steps to [Set up your development environment](../set-up-your-development-environment).
+If you haven't installed the SharePoint Framework, follow the steps to [Set up your development environment](../set-up-your-development-environment.md).
 
 After you install the SharePoint Framework, run the following command to update your Yeoman templates with the latest version:
 
@@ -23,7 +30,7 @@ After you install the SharePoint Framework, run the following command to update
 npm install -g @microsoft/generator-sharepoint
 ```
 
-Next, you can [Build your first SharePoint Framework Extension (Hello World part 1)](./get-started/build-a-hello-world-extension).
+Next, you can [Build your first SharePoint Framework Extension (Hello World part 1)](./get-started/build-a-hello-world-extension.md).
 
 ## Stay up to date
 To keep track of improvements to the SharePoint Framework, including updates to extensions, see the following:
@@ -42,5 +49,5 @@ We invite you to give us your feedback on the SharePoint Framework Extensions pr
 
 ## Additional resources
 
-- [Overview of the SharePoint Framework](../sharepoint-framework-overview)
-- [SharePoint Framework development tools and libraries](../tools-and-libraries)
+- [Overview of the SharePoint Framework](../sharepoint-framework-overview.md)
+- [SharePoint Framework development tools and libraries](../tools-and-libraries.md)
diff --git a/docs/spfx/known-issues-and-common-questions.md b/docs/spfx/known-issues-and-common-questions.md
index ceaaacc509..f497a3fc35 100644
--- a/docs/spfx/known-issues-and-common-questions.md
+++ b/docs/spfx/known-issues-and-common-questions.md
@@ -1,3 +1,10 @@
+---
+title: Known issues and frequently asked questions
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Known issues and frequently asked questions
 
 This page is for listing any known issues or to answer any frequently asked questions around SharePoint Framework. 
@@ -19,16 +26,15 @@ You should update your Yeoman template packages. We have updated certification c
 
 - *Date - 6th of June*
 
-SharePoint Extensions with additional customizations capabilities for the SharePoint Online is now available as Release Candiate release. We do not have public GA date currently. You can start learning how to build these extensions reading following tutorials.
+SharePoint Extensions with additional customizations capabilities for the SharePoint Online is now available for dev preview. We do not have public GA date currently. You can start learning how to build these extensions reading following tutorials.
 
 * [Getting started with SharePoint Framework Extensions](http://aka.ms/spfx-extensions)
 
 **Will SharePoint Framework be available in on-premises?**
 
 - *Date - 6th of June*
-- *Updated - 12th of September*
 
-SharePoint Framework client-side web parts are now available as part of the SharePoint 2016 Feature Pack 2 (FP2). 
+SharePoint Framework client-side web parts will be released to SharePoint 2016 as part of the Feature Pack 2 (FP2). 
 
 ## Additional resources
 Please use following resources to provide feedback, comments and questions towards SharePoint engineering. 
diff --git a/docs/spfx/roadmap.md b/docs/spfx/roadmap.md
index c4b96b51a1..269591cf5f 100644
--- a/docs/spfx/roadmap.md
+++ b/docs/spfx/roadmap.md
@@ -1,3 +1,10 @@
+---
+title: SharePoint Framework roadmap
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Framework roadmap
 
 First release of the SharePoint Framework will contain support for client-side web parts. This is however just a start on the journey for providing additional modern customization capabilities to SharePoint. This article lists the different areas which are in our backlog for the future releases of SharePoint Framework.
@@ -10,8 +17,7 @@ First release of the SharePoint Framework will contain support for client-side w
 - Similar feature capabilities as in SharePoint Online
 - Target is to provide common development platform across on-premises and the cloud
 - Leveraging modern toolchain and open source on on-premises environments
-
-> SharePoint 2016 support for client-side web parts was shipped with SharePoint 2016 Feature Pack 2 during September 2017.
+- Targeting SharePoint 2016 version during calendar year 2017
 
 ## General improvements
 
diff --git a/docs/spfx/set-up-your-developer-tenant.md b/docs/spfx/set-up-your-developer-tenant.md
index 44ffbbfbdd..0e3a139352 100644
--- a/docs/spfx/set-up-your-developer-tenant.md
+++ b/docs/spfx/set-up-your-developer-tenant.md
@@ -1,3 +1,10 @@
+---
+title: Set up your Office 365 tenant
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Set up your Office 365 tenant
 
 To build and deploy client-side web parts using the preview release of the SharePoint Framework, you will need a normal Office 365 tenant. 
@@ -64,4 +71,4 @@ https://your-sharepoint-site/_layouts/workbench.aspx
 ```
 
 ## Next steps
-Now that you have configured your SharePoint tenant, [set up your development environment](./set-up-your-development-environment) to build client-side web parts.
+Now that you have configured your SharePoint tenant, [set up your development environment](./set-up-your-development-environment.md) to build client-side web parts.
diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md
index 67952fe2df..bd866ef84c 100644
--- a/docs/spfx/set-up-your-development-environment.md
+++ b/docs/spfx/set-up-your-development-environment.md
@@ -1,13 +1,20 @@
+---
+title: Set up your SharePoint client-side web part development environment
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Set up your SharePoint client-side web part development environment
 
 You can use Visual Studio, or your own custom development environment to build SharePoint client-side web parts. You can use a Mac, PC, or Linux.
 
->**Note:** Before following the steps in this article, be sure to [Set up your Office 365 Tenant](./set-up-your-developer-tenant).
+>**Note:** Before following the steps in this article, be sure to [Set up your Office 365 Tenant](./set-up-your-developer-tenant.md).
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=_fxYexlUhe0&t=5s&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq&index=1). 
 
 <a href="https://www.youtube.com/watch?v=_fxYexlUhe0&t=5s&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-    <img src="../../images/spfx-youtube-tutorial0.png" alt="Screenshot of the YouTube video player for this tutorial" />
+    <img src="../images/spfx-youtube-tutorial0.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
@@ -65,7 +72,7 @@ Enter the following command to install the Yeoman SharePoint generator:
 ```
 npm install -g @microsoft/generator-sharepoint 
 ```
->**Note:** Yeoman generator for SharePoint can be installed both globally and locally. In this case we are installing the Yeoman generator for SharePoint to be available globally. 
+>**Note:** Yeoman generator for SharePoint is targeted to get deployed globally with the initial General Availability (GA) version. There are some known issues if it's installed locally to the project, which are planned to be addressed post GA.
 
 
 ## Optional tools
@@ -80,4 +87,4 @@ Here are some tools that might come in handy as well:
 
 ## Next steps
 
-You are now ready to [build your first client-side web part](web-parts/get-started/build-a-hello-world-web-part)!
+You are now ready to [build your first client-side web part](web-parts/get-started/build-a-hello-world-web-part.md)!
diff --git a/docs/spfx/sharepoint-2016-support.md b/docs/spfx/sharepoint-2016-support.md
index 045e7260b9..15aa5efb10 100644
--- a/docs/spfx/sharepoint-2016-support.md
+++ b/docs/spfx/sharepoint-2016-support.md
@@ -1,12 +1,15 @@
+---
+title: SharePoint Framework development with SharePoint 2016 Feature Pack 2
+ms.date: 09/25/2017
+---
+
 # SharePoint Framework development with SharePoint 2016 Feature Pack 2
 
 SharePoint 2016 Feature Pack 2 supports SharePoint Framework client-side web parts hosted in classic SharePoint pages. 
 
 An introduction to SharePoint Framework development in SharePoint 2016 using Feature Pack 2 is also covered in the following video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=LGLMxnmHk6U&list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG). 
 
-<a href="https://www.youtube.com/watch?v=LGLMxnmHk6U&list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG">
-<img src="../../images/spfx-fp2-youtube-video.png" alt="Screenshot of the YouTube video player for this tutorial" />
-</a>
+> [!VIDEO https://www.youtube.com/embed/LGLMxnmHk6U?list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG]
 
 ## Which version of the SharePoint Framework to use
 
diff --git a/docs/spfx/sharepoint-framework-overview.md b/docs/spfx/sharepoint-framework-overview.md
index 208cedfc4d..b8ae977182 100644
--- a/docs/spfx/sharepoint-framework-overview.md
+++ b/docs/spfx/sharepoint-framework-overview.md
@@ -1,8 +1,13 @@
-# Overview of the SharePoint Framework
+---
+title: Overview of the SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
 
-The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one. The SharePoint Framework works for SharePoint Online and also for on-premises (SharePoint 2016 Feature Pack 2).
+# Overview of the SharePoint Framework
 
-> See details around SharePoint Framework support in SharePoint 2016 from following article: [SharePoint Framework development with SharePoint 2016 Feature Pack 2](sharepoint-2016-support)
+The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready from day one. The SharePoint Framework works for SharePoint Online and soon also for on-premises (SharePoint 2016 Feature Pack 2).
  
 Key features of the SharePoint Framework include:
 
@@ -59,4 +64,4 @@ You can also post issues, questions, or feedback on the docs or the SharePoint F
 
 ## Additional resources
 
-- [Overview of SharePoint client-side web parts](./web-parts/overview-client-side-web-parts)
+- [Overview of SharePoint client-side web parts](./web-parts/overview-client-side-web-parts.md)
diff --git a/docs/spfx/team-based-development-on-sharepoint-framework.md b/docs/spfx/team-based-development-on-sharepoint-framework.md
index f9f135f52b..883ef33ff6 100644
--- a/docs/spfx/team-based-development-on-sharepoint-framework.md
+++ b/docs/spfx/team-based-development-on-sharepoint-framework.md
@@ -1,3 +1,10 @@
+---
+title: Team-based development on the SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Team-based development on the SharePoint Framework
 
 SharePoint Framework is a new development model for building SharePoint customizations. Unlike other SharePoint development models available to date, the SharePoint Framework focuses on client-side development and is built on top of popular open source tools such as gulp and webpack. One big benefit of this change is that developers on any platform can build SharePoint customizations.
diff --git a/docs/spfx/tenant-scoped-deployment.md b/docs/spfx/tenant-scoped-deployment.md
index 254debe612..63557090d1 100644
--- a/docs/spfx/tenant-scoped-deployment.md
+++ b/docs/spfx/tenant-scoped-deployment.md
@@ -1,3 +1,10 @@
+---
+title: Tenant-Scoped solution deployment for SharePoint Framework solutions
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Tenant-Scoped solution deployment for SharePoint Framework solutions
 
 You can configure your SharePoint Framework components to be immediately available cross the tenant when solution package is installed to tenant app catalog. This can be configured by using **skipFeatureDeployment** attribute in the **package-solution.json** file.
@@ -7,7 +14,7 @@ When solution has this attribute enabled, tenant administrator will be provided
 You can also see the tenant-wide deployment option demonstrated by watching following video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=pemHOZCSwZI).
 
 <a href="https://www.youtube.com/watch?v=pemHOZCSwZI&list=PLR9nK3mnD-OXZbEvTEPxzIOMGXj_aZKJG">
-<img src="../../images/tenant-deploy-youtube-video.png" alt="PnP Short Guidance video on tenant-wide deployment option" />
+<img src="../images/tenant-deploy-youtube-video.png" alt="PnP Short Guidance video on tenant-wide deployment option" />
 </a>
 
 > Notice. You have to update to latest SharePoint Framework Yeoman template version to be able to use this capability. You can update your global installation by executing `npm install -g @microsoft/generator-sharepoint`. 
@@ -24,7 +31,7 @@ When this option is used, any feature framework definitions in the SharePoint Fr
 
 SharePoint Framework Yeoman template will ask a specific question related on this option. This question will impact directly on the **skipFeatureDeployment** attribute in the **package-solution.json** file. 
 
-![Yeoman question around tenant deployed option](../../images/tenant-deploy-yeoman.png)
+![Yeoman question around tenant deployed option](../images/tenant-deploy-yeoman.png)
 
 In following example configuration, **skipFeatureDeployment** is set to true, which indicates that solution can be centrally deployed cross the tenant. 
 
@@ -49,7 +56,7 @@ When solution with **skipFeatureDeployment** attribute set to **true** is deploy
 
 By default, "**Make this solution available to all sites in the organization**" checkbox is unchecked. If the checkbox is checked by the administrator, components in the solutions will be automatically visible and available cross the tenant. 
 
-!["Make this solution available to all sites in the organization" setting visible when solution is deployed to app catalog](../../images/tenant-deploy-app-catalog.png)
+!["Make this solution available to all sites in the organization" setting visible when solution is deployed to app catalog](../images/tenant-deploy-app-catalog.png)
 
 Notice that since the solution and site -specific upgrade actions are only available when you use feature framework, there's no specific upgrade option for the centrally deployed solutions. These solutions can be simply updated by updating solution specific assets in the CDN and by updating package in the app catalog. This will update automatically all existing component instances cross the tenant to use the latest component assets, like JavaScript files and updated CSS files.
 
diff --git a/docs/spfx/toolchain/extending-webpack-in-build-pipeline.md b/docs/spfx/toolchain/extending-webpack-in-build-pipeline.md
index b43bcfea28..8a6fd3b306 100644
--- a/docs/spfx/toolchain/extending-webpack-in-build-pipeline.md
+++ b/docs/spfx/toolchain/extending-webpack-in-build-pipeline.md
@@ -1,3 +1,10 @@
+---
+title: Extending webpack in the SharePoint Framework toolchain
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Extending webpack in the SharePoint Framework toolchain
 
 [Webpack](https://webpack.github.io/) is a JavaScript module bundler that takes your JavaScript files and its dependencies and generates one or more JavaScript bundles so you can load different bundles for different scenarios.
diff --git a/docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md b/docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md
index 7df82ac602..e28c0a0e3c 100644
--- a/docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md
+++ b/docs/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md
@@ -1,3 +1,10 @@
+---
+title: Integrate gulp tasks in SharePoint Framework toolchain
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Integrate gulp tasks in SharePoint Framework toolchain
 
 SharePoint client-side development tools use [gulp](http://gulpjs.com/) as the build process task runner to:
@@ -20,7 +27,7 @@ gulp.task('somename', function() {
 
 When working with the SharePoint Framework toolchain, it is necessary to define your tasks in the framework's build pipeline. Once defined and registered with the pipeline, the task will be added to the toolchain.
 
-SharePoint Framework uses a [common build toolchain](sharepoint-framework-toolchain.md#common-build-tools-packages) which consists of a set of npm packages that share common build tasks. And hence, the default tasks are defined in the common package as opposed to your client-side project's `gulpfile.js`. To see the available tasks, you can execute the following command in a console within your project directory:
+SharePoint Framework uses a [common build toolchain](sharepoint-framework-toolchain.md#common-build-tool-packages) which consists of a set of npm packages that share common build tasks. And hence, the default tasks are defined in the common package as opposed to your client-side project's `gulpfile.js`. To see the available tasks, you can execute the following command in a console within your project directory:
 
 ```
 gulp --tasks
@@ -28,7 +35,7 @@ gulp --tasks
 
 The command above will list all the available tasks.
 
-![Available gulp tasks](../../../images/gulp-tasks-available.png)
+![Available gulp tasks](../../images/gulp-tasks-available.png)
 
 ## Custom gulp tasks
 To add your custom tasks, you will define the custom tasks in the `gulpfile.js`. Open the `gulpfile.js` in your code editor. The default code initializes the SharePoint Framework toolchain and the global `gulp` instance for the toolchain. Any custom tasks added should be defined before initializing the global `gulp` instance.
@@ -138,11 +145,11 @@ Now, you can execute this task from the gulp command line as follows:
 gulp resize-images
 ```
 
-![image-resize-task](../../../images/gulp-extend-image-resize-task.png)
+![image-resize-task](../../images/gulp-extend-image-resize-task.png)
 
 You will also see this `resize-images` task in the available tasks for your project when you execute `gulp --tasks`:
 
-![image-resize-task with available tasks](../../../images/gulp-extend-image-resize-available-tasks.png)
+![image-resize-task with available tasks](../../images/gulp-extend-image-resize-available-tasks.png)
 
 
 
diff --git a/docs/spfx/toolchain/optimize-builds-for-production.md b/docs/spfx/toolchain/optimize-builds-for-production.md
index 06550494e4..23a787772e 100644
--- a/docs/spfx/toolchain/optimize-builds-for-production.md
+++ b/docs/spfx/toolchain/optimize-builds-for-production.md
@@ -1,3 +1,10 @@
+---
+title: Optimize builds for production
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Optimize builds for production
 
 When deploying SharePoint Framework solutions to production you should always use a release build of your project which is optimized for performance. This article illustrates the main differences between debug and release builds and shows how you can optimize your bundle for use in production environments.
@@ -6,11 +13,11 @@ When deploying SharePoint Framework solutions to production you should always us
 
 When building a SharePoint Framework project, you can choose whether you want to build it in a debug or release mode. By default, SharePoint Framework projects are built in debug mode, which makes it easier for you to debug code. But when your code is finished and is working as expected, you should build it in release mode to optimize it for running in the production environment.
 
-> For more information about building your project in release mode, see the [SharePoint Framework Toolchain](./sharepoint-framework-toolchain) article.
+> For more information about building your project in release mode, see the [SharePoint Framework Toolchain](./sharepoint-framework-toolchain.md) article.
 
 The main difference between the output of a debug and release build is, that the release version of the generated bundle is minified and significantly smaller in size than its debug equivalent. To illustrate the difference, compare the size of the debug and release version of a SharePoint Framework project with a web part using Angular.
 
-![Image with two Explorer windows displayed side by side with the debug and release version of the generated bundle highlighted](../../../images/guidance-productionbuilds-debug-vs-ship-bundle.png)
+![Image with two Explorer windows displayed side by side with the debug and release version of the generated bundle highlighted](../../images/guidance-productionbuilds-debug-vs-ship-bundle.png)
 
 The debug version of the bundle is 1255 KB while its release equivalent is only 177 KB. The difference in size between the debug and release version of the generated bundle will differ depending on the libraries used in your project. Still, the release build will always be significantly smaller than a debug build, which is why you should always deploy the output of release builds to production.
 
@@ -20,7 +27,7 @@ When building SharePoint Framework solutions, you can benefit of many existing J
 
 By default, when referencing third party libraries in your project, SharePoint Framework will include them in the generated bundle. As a result, users working with your solution, would end up downloading the same library multiple times - once with each component. The total page size would grow significantly taking longer to load and leading to a poor user experience, particularly on slower networks.
 
-![Microsoft Edge developer tools showing on the network tab two web part bundles being loaded](../../../images/guidance-productionbuilds-two-bundles-with-libraries.png)
+![Microsoft Edge developer tools showing on the network tab two web part bundles being loaded](../../images/guidance-productionbuilds-two-bundles-with-libraries.png)
 
 When working with third party libraries, you should always consider loading them from an external location: either a public CDN or a hosting location owned by your organization. First of all, this allows you to exclude the library from your bundle, significantly decreasing its size. Additionally, if the hosting location from which you are loading the library is optimized for serving static assets, users working with your solution will need to load the library only once. On subsequent requests, or even when using your solution in the future, the web browser will reuse the previously cached copy of the library rather than downloading it again. As a result, the page with your solution will load significantly faster.
 
@@ -28,7 +35,7 @@ When working with third party libraries, you should always consider loading them
 
 When building your project in the debug mode, the SharePoint Framework provides you with the [Webpack Visualizer](https://chrisbateman.github.io/webpack-visualizer/) chart showing the different scripts included in the generated bundle. You can find this chart in the **./temp/stats/[solution-name].stats.html** file.
 
-![Webpack Visualizer chart illustrating the contents of a sample SharePoint Framework bundle](../../../images/guidance-productionbuilds-webpack-visualizer-angular.png)
+![Webpack Visualizer chart illustrating the contents of a sample SharePoint Framework bundle](../../images/guidance-productionbuilds-webpack-visualizer-angular.png)
 
 Using the Webpack Visualizer chart is a convenient way for you to verify, that the generated bundle doesn't contain any unnecessary scripts and how the included scripts affect the total bundle size. Keep in mind, that the displayed size reflects the debug build and would be significantly smaller for a release build.
 
@@ -38,7 +45,7 @@ More detailed information, used to generate the chart, is included in the **./di
 
 If there are multiple components on the same page, or even on different pages across the portal, and they all use the same library loaded from the same URL, the web browser will also reuse the copy it cached previously, which will lead to the portal loading faster. This is exactly why it is essential for organizations to rationalize which libraries and in which versions they use and where they load them from, not only for a specific project but for the whole organization. Such policy will let users working with the different applications be more productive by loading the applications faster. By reusing the previously downloaded assets, it will also limit the load on the network freeing its bandwidth for other purposes.
 
-> For more information about working with external libraries see the [Use existing JavaScript libraries in SharePoint Framework client-side web parts](../webparts/guidance/use-existing-javascript-libraries) article.
+> For more information about working with external libraries see the [Use existing JavaScript libraries in SharePoint Framework client-side web parts](../web-parts/guidance/use-existing-javascript-libraries.md) article.
 
 ## Reference only the necessary components
 
@@ -52,7 +59,7 @@ import * as _ from 'lodash';
 
 It would add 533 KB to your unoptimized bundle.
 
-![The complete Lodash library included in a bundle, highlighted in the Webpack Visualizer chart](../../../images/guidance-productionbuilds-import-lodash.png)
+![The complete Lodash library included in a bundle, highlighted in the Webpack Visualizer chart](../../images/guidance-productionbuilds-import-lodash.png)
 
 Instead, if you referenced only the specific Lodash method using the following code:
 
@@ -62,7 +69,7 @@ const at: any = require('lodash/at');
 
 It would add 42 KB to your unoptimized bundle.
 
-![Specific Lodash method included in a bundle, highlighted in the Webpack Visualizer chart](../../../images/guidance-productionbuilds-import-lodash-at.png)
+![Specific Lodash method included in a bundle, highlighted in the Webpack Visualizer chart](../../images/guidance-productionbuilds-import-lodash-at.png)
 
 Specifically with regards to Lodash, but which could also be the case with other libraries, referencing specific methods instead of the whole library comes with a price. Currently, Lodash doesn't support loading specific methods inside of SharePoint Framework projects using the **import** notation. Instead, you have to use a **require** statement which doesn't offer you the typesafety capabilities that using the **import** statement does. Eventually it is up to you to decide if loading significantly more code into your bundles is worth preserving the typesafety capabilities.
 
diff --git a/docs/spfx/toolchain/provision-sharepoint-assets.md b/docs/spfx/toolchain/provision-sharepoint-assets.md
index f2927c4eb7..d0762eef7b 100644
--- a/docs/spfx/toolchain/provision-sharepoint-assets.md
+++ b/docs/spfx/toolchain/provision-sharepoint-assets.md
@@ -1,3 +1,10 @@
+---
+title: Provision SharePoint assets with your solution package
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Provision SharePoint assets with your solution package
 
 At times, you may need to provision a SharePoint list or a document library along with your client-side solution package so that that list or library is available for your client-side components, such as web parts. SharePoint Framework toolchain allows you to package and deploy SharePoint items with your client-side solution package. These items are then provisioned when the client-side solution is installed on a site. 
@@ -5,7 +12,7 @@ At times, you may need to provision a SharePoint list or a document library alon
 You can also find details on the provisioning options from a SharePoint PnP webcast available from [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=r-UdJhhHlEQ&list=PLR9nK3mnD-OUnJytlXlO84fQnYt50iTmS). 
 
 <a href="https://www.youtube.com/watch?v=r-UdJhhHlEQ&list=PLR9nK3mnD-OUnJytlXlO84fQnYt50iTmS">
-<img src="../../../images/spfx-webcast-youtube-provision-feature-elements.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../images/spfx-webcast-youtube-provision-feature-elements.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
diff --git a/docs/spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md b/docs/spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md
index ded424cdc2..679b78c1fd 100644
--- a/docs/spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md
+++ b/docs/spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md
@@ -1,3 +1,10 @@
+---
+title: Scaffold projects using yeoman SharePoint generator
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Scaffold projects using yeoman SharePoint generator
 
 [Yeoman](http://yeoman.io/) helps you to kickstart new projects, prescribing best practices and tools to help you stay productive. Using the yeoman SharePoint generator, developers are able to scaffold new client-side solution projects to build, package and deploy SharePoint solutions. The generator provides common build tools, boilerplate code, and a common playground web site to host web parts for testing.
@@ -12,7 +19,7 @@ npm install @microsoft/generator-sharepoint -g
 
 >**Note:** Yeoman generator for SharePoint is targeted to get deployed globally with the initial General Availability (GA) version. There are some known issues if it's installed locally to the project, which are planned to be addressed post GA.
 
-It is recommended you follow the [set up your development environment](../spfx/set-up-your-development-environment.md) to configure your machine with the complete set of developer tools, including yeoman SharePoint generator. 
+It is recommended you follow the [set up your development environment](../set-up-your-development-environment.md) to configure your machine with the complete set of developer tools, including yeoman SharePoint generator. 
 
 ## Using the yeoman SharePoint generator
 
diff --git a/docs/spfx/toolchain/sharepoint-framework-toolchain.md b/docs/spfx/toolchain/sharepoint-framework-toolchain.md
index 3b71b2a828..8b1b24c49e 100644
--- a/docs/spfx/toolchain/sharepoint-framework-toolchain.md
+++ b/docs/spfx/toolchain/sharepoint-framework-toolchain.md
@@ -1,3 +1,10 @@
+---
+title: SharePoint Framework Toolchain
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Framework Toolchain
 
 The SharePoint Framework toolchain is the set of build tools, framework packages, and other items that manage building and deploying your client side projects. The toolchain helps you build client-side components like web parts. It also helps you test them in your local development environment with tools such as the SharePoint Workbench. And you can use the toolchain to package and deploy to SharePoint. The toolchain also provides you with a set of build commands that help you to complete key build tasks such as code compilation, packaging the client-side project into a SharePoint app package and more. 
@@ -66,7 +73,7 @@ Every time you create a new project using the generator, the generator installs
 ### package.json
 The `package.json` file in the client-side project specifies the list of dependencies the project depends on. The list defines what dependencies to install. As described earlier, each dependency could contain several more. npm allows you to define both runtime and build dependencies for your package using the `dependencies` and `devDependencies` properties. The `devDependencies` property is used when you want to use that module in your code as in the case of building web parts.
 
-The following is the `package.json` of the [helloworld-webpart](web-parts/get-started/build-a-hello-world-web-part).
+The following is the `package.json` of the [helloworld-webpart](../web-parts/get-started/build-a-hello-world-web-part.md).
 
 ```json 
 {
@@ -98,7 +105,7 @@ The following is the `package.json` of the [helloworld-webpart](web-parts/get-st
 }
 ```
 
-While there are lot of packages installed for the project, they are required only for building the web part in the dev environment. With the help of these packages, you can depend on the modules, and build, compile, bundle, and package your web part for deployment. The final minified bundled version of the web part that you deploy to a CDN server or SharePoint does not include any of these packages. That said, you can also configure to include certain modules depending on your requirements. For more information, see [Add an external library to a web part](web-parts/basics/add-an-external-library).
+While there are lot of packages installed for the project, they are required only for building the web part in the dev environment. With the help of these packages, you can depend on the modules, and build, compile, bundle, and package your web part for deployment. The final minified bundled version of the web part that you deploy to a CDN server or SharePoint does not include any of these packages. That said, you can also configure to include certain modules depending on your requirements. For more information, see [Add an external library to a web part](../web-parts/basics/add-an-external-library.md).
 
 ### Working with source control systems
 As project dependencies increase, the number of packages to install also increases. You don’t want to check the `node_modules` folder, which contains all of the dependencies, into your source control system. You should exclude the `node_modules` from the list of files to ignore during check-ins. 
@@ -147,7 +154,7 @@ gulp serve
 
 The `serve` runs the different tasks and finally launches SharePoint Workbench.
 
-![gulp serve task](../../../images/toolchain-gulp-serve-task.png)
+![gulp serve task](../../images/toolchain-gulp-serve-task.png)
 
 ### Build targets
 In the previous screenshot, you can see that the task indicates your build target as follows:
diff --git a/docs/spfx/toolchain/update-latest-packages.md b/docs/spfx/toolchain/update-latest-packages.md
index 4c32969da5..efe94b5b0b 100644
--- a/docs/spfx/toolchain/update-latest-packages.md
+++ b/docs/spfx/toolchain/update-latest-packages.md
@@ -1,3 +1,10 @@
+---
+title: Update SharePoint Framework packages 
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Update SharePoint Framework packages 
 
 SharePoint client-side development tools use the [npm](https://www.npmjs.com/) package manager to manage dependencies and other required JavaScript helpers. npm is typically included as part of Node.js setup.
@@ -121,4 +128,4 @@ npm ls @microsoft/generator-sharepoint -g --depth=0
 
 
 
- 
\ No newline at end of file
+ 
diff --git a/docs/spfx/tools-and-libraries.md b/docs/spfx/tools-and-libraries.md
index cd18e2a853..1bb6e41e22 100644
--- a/docs/spfx/tools-and-libraries.md
+++ b/docs/spfx/tools-and-libraries.md
@@ -1,3 +1,10 @@
+---
+title: SharePoint Framework development tools and libraries
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Framework development tools and libraries
 
 The SharePoint Framework includes several client-side JavaScript libraries that you can use to build your solutions. This article provides an overview of the tools and libraries that you can use to develop client-side web parts.
@@ -101,5 +108,5 @@ The [Office Dev Patterns and Practices / SharePoint Pattern and Practices (PnP)]
 
 ## Additional resources
 
-* [SharePoint Framework](sharepoint-framework-overview)
-* [Build a Hello World client-side web part](web-parts/get-started/build-a-hello-world-web-part)
+* [SharePoint Framework](sharepoint-framework-overview.md)
+* [Build a Hello World client-side web part](web-parts/get-started/build-a-hello-world-web-part.md)
diff --git a/docs/spfx/update-latest-packages.md b/docs/spfx/update-latest-packages.md
index 4c32969da5..308439f579 100644
--- a/docs/spfx/update-latest-packages.md
+++ b/docs/spfx/update-latest-packages.md
@@ -1,3 +1,10 @@
+---
+title: Update SharePoint Framework packages 
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Update SharePoint Framework packages 
 
 SharePoint client-side development tools use the [npm](https://www.npmjs.com/) package manager to manage dependencies and other required JavaScript helpers. npm is typically included as part of Node.js setup.
@@ -19,7 +26,7 @@ The command will list the following information about the packages your project
 * Version requested by your project (available in `package.json`)
 * Latest version available
 
-![NPM outdated packages](../../images/npm-outdated-packages-list.png)
+![NPM outdated packages](../images/npm-outdated-packages-list.png)
 
 To identify the SharePoint Framework packages, look for the package names that start with the following npm scope and prefix:
 
@@ -36,7 +43,7 @@ Open your project in your favorite code editor and locate the `package.json` fil
 
 In the `package.json` file, locate the package(s) under the `dependencies` and `devDependencies` section and update the version to the latest version available that was listed in the `npm outdated` command. For example, the image below highlights the version updates to SharePoint Framework packages, the left section referring to the old and the right section referring to the latest package versions.
 
-![Edit package versions in package.json file](../../images/npm-update-packagejson-versions.png)
+![Edit package versions in package.json file](../images/npm-update-packagejson-versions.png)
 
 Once you have updated the package versions, Save the `package.json` file.
 
@@ -95,7 +102,7 @@ The command will list the following information about the packages installed glo
 * Version requested by you when you installed
 * Latest version available
 
-![NPM outdated global packages](../../images/npm-outdated-global-packages-list.png)
+![NPM outdated global packages](../images/npm-outdated-global-packages-list.png)
 
 To identify the generator package, look for the following package name:
 
@@ -121,4 +128,4 @@ npm ls @microsoft/generator-sharepoint -g --depth=0
 
 
 
- 
\ No newline at end of file
+ 
diff --git a/docs/spfx/use-theme-colors-in-your-customizations.md b/docs/spfx/use-theme-colors-in-your-customizations.md
index 5be06d537e..a833e59608 100644
--- a/docs/spfx/use-theme-colors-in-your-customizations.md
+++ b/docs/spfx/use-theme-colors-in-your-customizations.md
@@ -1,3 +1,10 @@
+---
+title: Use theme colors in your SharePoint Framework customizations
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use theme colors in your SharePoint Framework customizations
 
 When building SharePoint Framework customizations you should use theme colors, so that your customizations looks like a part of the site. This article explains how can you refer to the theme colors of the context site in your SharePoint Framework solution.
@@ -8,7 +15,7 @@ When building SharePoint Framework customizations you should use theme colors, s
 
 When you scaffold a new SharePoint Framework client-side web part, it uses a fixed blue palette. When you add such web part on a modern site, using a different color scheme, it stands out and doesn't look like a part of the site.
 
-![SharePoint Framework client-side web part using the blue color scheme on a modern team site using the red theme](../../images/themed-styles-blue-web-part-red-site.png)
+![SharePoint Framework client-side web part using the blue color scheme on a modern team site using the red theme](../images/themed-styles-blue-web-part-red-site.png)
 
 When using fixed colors, you decide upfront which colors you want to use for which elements. This can lead to a situation like the one just illustrated, where a blue web part is displayed on a red team site, standing out unnecessarily. In most cases, you should strive to leverage the theme colors of the context site, so that your solution doesn't stand out but looks like a part of the site.
 
@@ -63,7 +70,7 @@ When you scaffold a new SharePoint Framework client-side web part, by default, i
 
 In the code editor open the **./src/webparts/helloWorld/components/HelloWorld.tsx** file and from the div with class **ms-Grid-row** remove the **ms-bgColor-themeDark** class.
 
-![The 'ms-bgColor-themeDark' class selected in Visual Studio Code editor](../../images/themed-styles-ms-bgcolor-themedark-class.png)
+![The 'ms-bgColor-themeDark' class selected in Visual Studio Code editor](../images/themed-styles-ms-bgcolor-themedark-class.png)
 
 Next, in the same folder, open the **HelloWorld.module.scss** file. Change the `.row` selector to:
 
@@ -74,7 +81,7 @@ Next, in the same folder, open the **HelloWorld.module.scss** file. Change the `
 }
 ```
 
-![The .row selector extended with background color](../../images/themed-styles-row-class.png)
+![The .row selector extended with background color](../images/themed-styles-row-class.png)
 
 In the `.button` selector, change the `background-color` and `border-color` properties to:
 
@@ -87,11 +94,11 @@ In the `.button` selector, change the `background-color` and `border-color` prop
 }
 ```
 
-![The .button selector updated with references to theme colors](../../images/themed-styles-button-class.png)
+![The .button selector updated with references to theme colors](../images/themed-styles-button-class.png)
 
 When you add the web part to a site, the colors used by the web part will automatically adapt to the theme colors used by the current site.
 
-![Side-by-side view of the same web part displayed in two sites using different colors. The web part follows the color scheme of each web site](../../images/themed-styles-side-by-side.png)
+![Side-by-side view of the same web part displayed in two sites using different colors. The web part follows the color scheme of each web site](../images/themed-styles-side-by-side.png)
 
 ## More information
 
diff --git a/docs/spfx/web-parts/basics/add-an-external-library.md b/docs/spfx/web-parts/basics/add-an-external-library.md
index f7db34c976..61ea409988 100644
--- a/docs/spfx/web-parts/basics/add-an-external-library.md
+++ b/docs/spfx/web-parts/basics/add-an-external-library.md
@@ -1,3 +1,10 @@
+---
+title: Add an external library to your SharePoint client-side web part
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add an external library to your SharePoint client-side web part
 
 You might want to include one or more JavaScript libraries in your web part. This article shows you how to bundle an external library and share libraries.
diff --git a/docs/spfx/web-parts/basics/design-considerations-for-web-parts.md b/docs/spfx/web-parts/basics/design-considerations-for-web-parts.md
index 5b7e2b0457..e3d0226c70 100644
--- a/docs/spfx/web-parts/basics/design-considerations-for-web-parts.md
+++ b/docs/spfx/web-parts/basics/design-considerations-for-web-parts.md
@@ -1,3 +1,10 @@
+---
+title: Design considerations for SharePoint client-side web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Design considerations for SharePoint client-side web parts
 
 To get started designing web parts, you will want to be familiar with [Office UI Fabric](http://dev.office.com/fabric). All of the styles from [Fabric Core](https://github.com/OfficeDev/office-ui-fabric-core) – including icons, typography, color usage, animation, and the responsive grid – are loaded by default and available to your web part. Do not import a copy of Fabric for your web part, as this may conflict with the global copy. These classes provide a foundation to your web part's styling, which you can always depart from if you require different visuals to match your company's brand.
@@ -8,7 +15,7 @@ Along with Office UI Fabric, you can use Office UI Fabric React components to bu
 
 The following To Do list example uses Fabric components in the property pane that lets the page author configure a web part.
 
-![Example of a Todo web part that uses Fabric](../../../../images/design-wp-todo-example.png)
+![Example of a Todo web part that uses Fabric](../../../images/design-wp-todo-example.png)
 
 You can find a complete list of the Office UI Fabric styles, typography, color, icons, and animations at [Office UI Fabric styles](http://dev.office.com/fabric/styles).
 
@@ -21,13 +28,13 @@ Pages in the new SharePoint authoring experience use the Office UI Fabric respon
 
 We recommend that all web parts use a 100% maximum width to ensure that they will re-flow and function properly on any page. The page and column widths are defined by the page template but can be modified by the author. If a max pixel value is set in the web part, there could be unexpected results in both functionality and layout when the page is seen at different widths.
 
-![Max width web part responsive behavior](../../../../images/design-wp-responsive-max-width.png)
+![Max width web part responsive behavior](../../../images/design-wp-responsive-max-width.png)
 
 ### Min width
 
 All web parts should be designed to reflow as the page/column width gets smaller down to a min width of 320 px.
 
-![Min width web part responsive behavior](../../../../images/design-wp-responsive-min-width.png)
+![Min width web part responsive behavior](../../../images/design-wp-responsive-min-width.png)
 
 ## Web part published mode vs edit mode
 
@@ -42,31 +49,31 @@ The new SharePoint page authoring experience has two modes:
 
 The add hint is a horizontal line with a plus icon that is visible when a web part is selected and on hover to indicate where page authors can add new web parts to their page. The toolbox opens when a user clicks/taps the plus icon. The toolbox contains all the web parts that can be added to a page.
 
-![Web part add hint and toolbox](../../../../images/design-wp-toolbox.png)
+![Web part add hint and toolbox](../../../images/design-wp-toolbox.png)
 
 #### Toolbar
 
 A vertical toolbar and bounding box is part of the framework for every web part and provided by the page. Each web part has an edit and delete action in the toolbar.
 
-![Web part vertical toolbar](../../../../images/design-wp-toolbar.png)
+![Web part vertical toolbar](../../../images/design-wp-toolbar.png)
 
 #### Contextual edits
 
 A WYSIWYG experience should be designed for web parts to fill in information or add content that will be displayed to the user when published. Entering this content should be done in page so the user understands how the viewer will see the content. For example, titles and descriptions should be filled out where the text displays or new tasks should be added and modified in context of the page.
 
-![Web part contextual edits](../../../../images/design-wp-contexual-edits.png)
+![Web part contextual edits](../../../images/design-wp-contexual-edits.png)
 
 #### Item-level edits
 
 UI can change within the web part; for example, turning text into a text field to fill out links or when displaying UI to reorder items or to check of tasks in a web part
 
-![Web part item level edits](../../../../images/design-wp-item-level-edits.png)
+![Web part item level edits](../../../images/design-wp-item-level-edits.png)
 
 ## Property panes
 
 Property panes are invoked via the edit action icon on the toolbar. Panes should primarily contain configuration settings that enable/disable features that either show on page or that make a call to a service to display content.
 
-![Web part property pane design](../../../../images/design-wp-pp.png)
+![Web part property pane design](../../../images/design-wp-pp.png)
 
 There are three types of property panes to enable you to design and develop web parts that fit your business or customer needs.
 
@@ -74,7 +81,7 @@ There are three types of property panes to enable you to design and develop web
 
 A single pane is used for simple web parts that only have a small number of properties to configure.
 
-![Web part single property pane design](../../../../images/design-wp-pp-single.png)
+![Web part single property pane design](../../../images/design-wp-pp-single.png)
 
 ### Accordion pane
 
@@ -82,11 +89,11 @@ A accordion pane is used for containing a group or groups of properties with man
 
 #### Accordion - One group open
 
-![Web part accordion property pane with one group open](../../../../images/design-wp-pp-accordion.png)
+![Web part accordion property pane with one group open](../../../images/design-wp-pp-accordion.png)
 
 #### Accordion- Two groups open and scrolled
 
-![Web part accordion property pane with two groups open and scrolled](../../../../images/design-wp-pp-accordion-groups.png)
+![Web part accordion property pane with two groups open and scrolled](../../../images/design-wp-pp-accordion-groups.png)
 
 
 ### Property pane steps/pages
@@ -94,43 +101,43 @@ A accordion pane is used for containing a group or groups of properties with man
 A steps pane is used for grouping properties in multiple steps or pages when you need the web part to be configured in a linear order or when choices made on the first step affect options that display on the second step.
 
 **Step 1 of 3**
-![Property pane with steps design 1 of 3](../../../../images/design-wp-pp-pages-step1.png)
+![Property pane with steps design 1 of 3](../../../images/design-wp-pp-pages-step1.png)
 
 **Step 2 of 3**
-![Property pane with steps design 2 of 3](../../../../images/design-wp-pp-pages-step2.png)
+![Property pane with steps design 2 of 3](../../../images/design-wp-pp-pages-step2.png)
 
 **Step 3 of 3**
-![Property pane with steps design 3 of 3](../../../../images/design-wp-pp-pages-step3.png)
+![Property pane with steps design 3 of 3](../../../images/design-wp-pp-pages-step3.png)
 
 
 ## Reactive vs non-reactive web parts
 
 Reactive web parts are designed to be full client-side web parts, which mean that each component that is configured in the properties pane will reflect as the change is made within the web part on the page. For the To-Do List web part, unchecking “Completed Tasks” will hide this view in the web part.
 
-![Reactive web part design](../../../../images/design-wp-pp-reactive.png)
+![Reactive web part design](../../../images/design-wp-pp-reactive.png)
 
 Non-reactive web parts are not fully client side and generally one or more properties need to make a call to set/pull or store data on a server. In this case, you should enable the Apply and Cancel buttons at the bottom of the properties pane.
 
-![Non-reactive web part design](../../../../images/design-wp-pp-non-reactive.png)
+![Non-reactive web part design](../../../images/design-wp-pp-non-reactive.png)
 
 ## Constructing the To-Do List property pane
 
 The To-Do List example uses the single pane and is a reactive web part. The following shows each Fabric React component and the resulting design.
 
 Adding a description for To-Do List
-![Adding a description for To-Do List](../../../../images/design-wp-todo-pp-description.png)
+![Adding a description for To-Do List](../../../images/design-wp-todo-pp-description.png)
 
 Drop down – to select tasks from an existing list
-![Drop down to select tasks from an existing list](../../../../images/design-wp-todo-pp-dropdown.png)
+![Drop down to select tasks from an existing list](../../../images/design-wp-todo-pp-dropdown.png)
 
 Checkbox– to allow authors to show or hide different views
-![Checkbox to allow authors to show or hide different views](../../../../images/design-wp-todo-pp-checkbox.png)
+![Checkbox to allow authors to show or hide different views](../../../images/design-wp-todo-pp-checkbox.png)
 
 Slider – to set the number of tasks visible
-![Slider to set the number of tasks visible](../../../../images/design-wp-todo-pp-slider.png)
+![Slider to set the number of tasks visible](../../../images/design-wp-todo-pp-slider.png)
 
 After selecting a list from the drop down the web part shows and indicator of items loading onto the page
-![Web part showing loading indicator to load items](../../../../images/design-wp-todo-loading-indicator.png)
+![Web part showing loading indicator to load items](../../../images/design-wp-todo-loading-indicator.png)
 
 When the new tasks are loaded the fade into view using animation styles from Office UI Fabric
-![Web part with fabric animations](../../../../images/design-wp-todo-fabric-animations.png)
+![Web part with fabric animations](../../../images/design-wp-todo-fabric-animations.png)
diff --git a/docs/spfx/web-parts/basics/integrate-with-property-pane.md b/docs/spfx/web-parts/basics/integrate-with-property-pane.md
index de2a71cca0..c74e4f5e72 100644
--- a/docs/spfx/web-parts/basics/integrate-with-property-pane.md
+++ b/docs/spfx/web-parts/basics/integrate-with-property-pane.md
@@ -1,10 +1,17 @@
+---
+title: Make your SharePoint client-side web part configurable
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Make your SharePoint client-side web part configurable
 
-The property pane allows end users to configure the web part with a bunch of properties. The article [Build your first web part](../get-started/build-a-hello-world-web-part) describes how the property pane is defined in the **HelloWorldWebPart** class. The property pane properties are defined in  **propertyPaneSettings**.
+The property pane allows end users to configure the web part with a bunch of properties. The article [Build your first web part](../get-started/build-a-hello-world-web-part.md) describes how the property pane is defined in the **HelloWorldWebPart** class. The property pane properties are defined in  **propertyPaneSettings**.
 
 The following figure shows an example of a property pane in SharePoint.
 
-![Property pane example](../../../../images/property-pane-example.png)
+![Property pane example](../../../images/property-pane-example.png)
 
 The property pane has three key metadata:
 
@@ -103,7 +110,7 @@ This is then available in your web part using **this.properties.targetProperty**
 <p class="ms-font-l ms-fontColor-white">${this.properties.description}</p>
 ```
 
-When the properties are defined, you can access them in your web part using the **this.properties.[property-name]**. For details, see [**render** method of the **HelloWorldWebPart**](../get-started/build-a-hello-world-web-part#web-part-render-method).
+When the properties are defined, you can access them in your web part using the **this.properties.[property-name]**. For details, see [**render** method of the **HelloWorldWebPart**](../get-started/build-a-hello-world-web-part.md#web-part-render-method).
 
 ## Handling field changes
 
@@ -124,4 +131,4 @@ protected get disableReactivePropertyChanges(): boolean {
 
 ## Custom property pane controls
 
-SharePoint Framework contains a set of standard controls for the property pane. But sometimes you need additional functionality beyond the basic controls. SharePoint Framework allows you to build custom controls to deliver the require functionality. To learn more, read the [Build custom controls for the property pane](../guidance/build-custom-property-pane-controls) guide.
\ No newline at end of file
+SharePoint Framework contains a set of standard controls for the property pane. But sometimes you need additional functionality beyond the basic controls. SharePoint Framework allows you to build custom controls to deliver the require functionality. To learn more, read the [Build custom controls for the property pane](../guidance/build-custom-property-pane-controls.md) guide.
diff --git a/docs/spfx/web-parts/basics/notes-on-solution-packaging.md b/docs/spfx/web-parts/basics/notes-on-solution-packaging.md
index e1eb898780..38f501260b 100644
--- a/docs/spfx/web-parts/basics/notes-on-solution-packaging.md
+++ b/docs/spfx/web-parts/basics/notes-on-solution-packaging.md
@@ -1,3 +1,10 @@
+---
+title: Notes on solution packaging
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Notes on solution packaging
 
 The **package-solution** gulp task looks at **/config/package-solution.json** for various configuration details, including some generic filepaths, as well as defining the relationship between components (_WebParts_ and _Applications_) in a package.
diff --git a/docs/spfx/web-parts/basics/working-with-requestdigest.md b/docs/spfx/web-parts/basics/working-with-requestdigest.md
index 9e2f915461..a9cc20332b 100644
--- a/docs/spfx/web-parts/basics/working-with-requestdigest.md
+++ b/docs/spfx/web-parts/basics/working-with-requestdigest.md
@@ -1,3 +1,10 @@
+---
+title: Working with __REQUESTDIGEST
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Working with __REQUESTDIGEST
 
 When executing non-GET REST requests to the SharePoint API, you must add a valid request digest to your request. This digest proves validity of your request to SharePoint. Because this token is valid only for a limited period of time, you have to ensure that the token you have is valid, before adding it to your request or the request will fail. This article describes the different approaches to obtain a valid request digest and pitfalls of some commonly used approaches.
diff --git a/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md b/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
index a791ec0c02..08f06dda20 100644
--- a/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
+++ b/docs/spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
@@ -1,13 +1,20 @@
+---
+title: Add jQueryUI Accordion to your SharePoint client-side web part
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Add jQueryUI Accordion to your SharePoint client-side web part
 
 This article describes how to add the jQueryUI Accordion to your web part project. This involves creating a new web part, as shown in the following image. 
 
-![Screenshot of a web part that includes a jQuery Accordion](../../../../images/jquery-accordion-wb.png)
+![Screenshot of a web part that includes a jQuery Accordion](../../../images/jquery-accordion-wb.png)
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=-3m__hRQxEI&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=-3m__hRQxEI&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial5.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial5.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Prerequisites
@@ -318,6 +325,6 @@ Gulp will execute the tasks and open the local SharePoint web part workbench.
 
 In the page canvas, choose the **+** (plus sign) to show the list of web parts, and add the jQuery web part. You should now see the jQueryUI Accordion!
 
-![Screenshot of a web part that includes a jQuery Accordion](../../../../images/jquery-accordion-wb.png)
+![Screenshot of a web part that includes a jQuery Accordion](../../../images/jquery-accordion-wb.png)
 
 In the console where you have `gulp serve` running, choose **Ctrl+C** to terminate the task.
diff --git a/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md b/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
index 715f178fb1..dc39835580 100644
--- a/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
+++ b/docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
@@ -1,3 +1,10 @@
+---
+title: Build your first SharePoint client-side web part (Hello World part 1)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build your first SharePoint client-side web part (Hello World part 1)
 
 Client-side web parts are client-side components that run inside the context of a SharePoint page. Client-side web parts can be deployed to SharePoint Online, and you can also use modern JavaScript tools and libraries to build them.
@@ -7,12 +14,12 @@ Client-side web parts support:
 * Building with HTML and JavaScript.
 * Both SharePoint online and on-premises environments.
 
->**Note:** Before following the steps in this article, be sure to [Set up your development environment](../../set-up-your-development-environment).
+>**Note:** Before following the steps in this article, be sure to [Set up your development environment](../../set-up-your-development-environment.md).
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=QbDtsMg88Js&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=QbDtsMg88Js&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial1.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial1.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
@@ -46,15 +53,15 @@ The next set of prompts will ask for specific information about your web part:
 * Accept the default **HelloWorld** as your web part name and choose **Enter**.
 * Accept the default **HelloWorld description** as your web part description and choose **Enter**.
 
-![Yeoman SharePoint generator prompts to create a web part client-side solution](../../../../images/yeoman-sp-prompts.png)
+![Yeoman SharePoint generator prompts to create a web part client-side solution](../../../images/yeoman-sp-prompts.png)
 
 At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** web part. This might take a few minutes. 
 
 When the scaffold is complete, you should see the following message indicating a successful scaffold:
 
-![SharePoint client-side solution scaffolded successfully](../../../../images/yeoman-sp-complete.png)
+![SharePoint client-side solution scaffolded successfully](../../../images/yeoman-sp-complete.png)
 
-For information about troubleshooting any errors, see [Known issues](../basics/known-issues).
+For information about troubleshooting any errors, see [Known issues](../../known-issues-and-common-questions.md).
 
 ### Using your favorite Code Editor
 Because the SharePoint client-side solution is HTML/TypeScript based, you can use any code editor that supports client-side development to build your web part, such as:
@@ -84,7 +91,7 @@ gulp serve
 
 This command will execute a series of gulp tasks to create a local, Node-based HTTPS server on 'localhost:4321' and launch your default browser to preview web parts from your local dev environment.
 
-![Gulp serve web part project](../../../../images/helloworld-wp-gulp-serve.png)
+![Gulp serve web part project](../../../images/helloworld-wp-gulp-serve.png)
 
 SharePoint client-side development tools use [gulp](http://gulpjs.com/) as the task runner to handle build process tasks such as:
 
@@ -100,21 +107,21 @@ Visual Studio Code provides built-in support for gulp and other task runners. Ch
 ### SharePoint Workbench
 SharePoint Workbench is a developer design surface that enables you to quickly preview and test web parts without deploying them in SharePoint. SharePoint Workbench includes the client-side page and the client-side canvas in which you can add, delete and test your web parts in development.
 
-![SharePoint Workbench running locally](../../../../images/sp-workbench.png)
+![SharePoint Workbench running locally](../../../images/sp-workbench.png)
 
 To add the HelloWorld web part, choose the **add** button. The add button opens the toolbox where you can see a list of web parts available for you to add. The list will include the **HelloWorld** web part as well other web parts available locally in your development environment.
    
-![SharePoint Workbench toolbox in localhost](../../../../images/sp-workbench-toolbox.png)
+![SharePoint Workbench toolbox in localhost](../../../images/sp-workbench-toolbox.png)
    
 Choose **HelloWorld** to add the web part to the page:
    
-![HelloWorld web part in SharePoint workbench](../../../../images/sp-workbench-helloworld-wp.png)
+![HelloWorld web part in SharePoint workbench](../../../images/sp-workbench-helloworld-wp.png)
 
 Congratulations! You have just added your first client-side web part to a client-side page.
    
 Now, choose the pencil icon on the far left of the web part to reveal the web part property pane.
    
-![HelloWorld web part property pane](../../../../images/sp-workbench-helloworld-pp.png)
+![HelloWorld web part property pane](../../../images/sp-workbench-helloworld-pp.png)
 
 The property pane is where you can define properties to customize your web part. The property pane is client-side driven and provides a consistent design across SharePoint. 
    
@@ -134,7 +141,7 @@ You can use Visual Studio Code to explore the web part project structure.
 code .
 ```
 
-![HelloWorld project structure](../../../../images/helloworld-wp-vscode-project-structure.png)
+![HelloWorld project structure](../../../images/helloworld-wp-vscode-project-structure.png)
 
 If you get an error, you might need to [install the code command in PATH](https://code.visualstudio.com/docs/editor/setup).
 
@@ -195,7 +202,7 @@ When the properties are defined, you can access them in your web part using `thi
 
 Notice that we are performing a HTML escape on the property's value to ensure a valid string.
 
-Read the [Integrating property pane with a web part](../basics/integrate-with-property-pane) article to learn more about how to work with the property pane and property pane field types.
+Read the [Integrating property pane with a web part](../basics/integrate-with-property-pane.md) article to learn more about how to work with the property pane and property pane field types.
 
 Lets now add few more properties - a checkbox, dropdown and a toggle - to the property pane. We first start by importing the respective property pane fields from the framework.
 
@@ -353,19 +360,19 @@ Go to the following URL: 'https://your-sharepoint-site/_layouts/workbench.aspx'
 
 >**Note:** If you do not have the SPFx developer certificate installed, then Workbench will notify you that it is configured not to load scripts from localhost. Stop currently running process in the console window, execute `gulp trust-dev-cert` command in your project directory console to install the developer certificate before running `gulp serve`command again.
 
-![SharePoint Workbench running in a SharePoint Online site](../../../../images/sp-workbench-o365.png)
+![SharePoint Workbench running in a SharePoint Online site](../../../images/sp-workbench-o365.png)
 
 Notice that the SharePoint workbench now has the Office 365 Suite navigation bar.
 
 Choose **add icon** in the canvas to reveal the toolbox. The toolbox now shows the web parts available on the site where the SharePoint workbench is hosted along with your **HelloWorldWebPart**.
 
-![Toolbox in SharePoint Workbench running in SharePoint Online site](../../../../images/sp-workbench-o365-toolbox.png)
+![Toolbox in SharePoint Workbench running in SharePoint Online site](../../../images/sp-workbench-o365-toolbox.png)
 
 Add **HelloWorldWebPart** from the toolbox. Now you're running your web part in a page hosted in SharePoint!
 
-![HelloWorld web part running in SharePoint Workbench running in a SharePoint Online site](../../../../images/sp-workbench-o365-helloworld-wp.png)
+![HelloWorld web part running in SharePoint Workbench running in a SharePoint Online site](../../../images/sp-workbench-o365-helloworld-wp.png)
 
 Because you are still developing and testing your web part, there is no need to package and deploy your web part to SharePoint. 
 
 ## Next steps
-Congratulations on getting your first Hello World web part running! Now that your web part is running, you can continue building out your Hello World web part in the next topic, [Connect to SharePoint](./connect-to-sharepoint). You will use the same Hello World web part project and add the ability to interact with SharePoint List REST APIs. Notice that the `gulp serve` command is still running in your console window (or in Visual Studio Code if you using the editor). You can continue to let it run while you go to the next article.
+Congratulations on getting your first Hello World web part running! Now that your web part is running, you can continue building out your Hello World web part in the next topic, [Connect to SharePoint](./connect-to-sharepoint.md). You will use the same Hello World web part project and add the ability to interact with SharePoint List REST APIs. Notice that the `gulp serve` command is still running in your console window (or in Visual Studio Code if you using the editor.md). You can continue to let it run while you go to the next article.
diff --git a/docs/spfx/web-parts/get-started/connect-to-sharepoint.md b/docs/spfx/web-parts/get-started/connect-to-sharepoint.md
index c7fed0fa67..89847dd549 100644
--- a/docs/spfx/web-parts/get-started/connect-to-sharepoint.md
+++ b/docs/spfx/web-parts/get-started/connect-to-sharepoint.md
@@ -1,11 +1,18 @@
+---
+title: Connect your client-side web part to SharePoint (Hello world part 2)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Connect your client-side web part to SharePoint (Hello world part 2)
 
-Connect your web part to SharePoint to access functionality and data in SharePoint and provide a more integrated experience for end users. This article continues building the hello world web part built in the previous article [Build your first web part](./build-a-hello-world-web-part).
+Connect your web part to SharePoint to access functionality and data in SharePoint and provide a more integrated experience for end users. This article continues building the hello world web part built in the previous article [Build your first web part](./build-a-hello-world-web-part.md).
 
 You can also follow follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=9VMwjb2pbQ8&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=9VMwjb2pbQ8&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial2.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial2.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
@@ -72,7 +79,7 @@ In your browser, switch to the local SharePoint Workbench tab. If you have alrea
 
 You should see the following in the web part:
 
-![SharePoint page context in localhost](../../../../images/sp-mock-localhost-wp.png)
+![SharePoint page context in localhost](../../../images/sp-mock-localhost-wp.png)
 
 Now, navigate to the SharePoint Workbench hosted in SharePoint. The full URL is `https://your-sharepoint-site-url/_layouts/workbench.aspx`. Notice that in the SharePoint Online side, you'll need to refresh the page to see the changes.
 
@@ -80,7 +87,7 @@ Now, navigate to the SharePoint Workbench hosted in SharePoint. The full URL is
 
 You should now see your SharePoint site title in the web part now that page context is available to the web part.
 
-![SharePoint page context in SharePoint site](../../../../images/sp-lists-spsiteurl-wp.png)
+![SharePoint page context in SharePoint site](../../../images/sp-lists-spsiteurl-wp.png)
 
 ## Define list model
 You need a list model to start working with SharePoint list data. To retrieve the lists, you need two models. 
@@ -347,16 +354,16 @@ Switch to your local workbench and add the HelloWorld web part.
 
 You should see the mock data returned.
 
-![Render lists data from localhost](../../../../images/sp-lists-render-localhost.png)
+![Render lists data from localhost](../../../images/sp-lists-render-localhost.png)
 
 Switch to the workbench hosted in SharePoint. Refresh the page and add the HelloWorld web part.
 
 You should see lists returned from the current site.
 
-![Render lists data from SharePoint](../../../../images/sp-lists-render-spsite.png)
+![Render lists data from SharePoint](../../../images/sp-lists-render-spsite.png)
 
 Now you can stop the server from running. Switch to the console and stop `gulp serve`. Choose `Ctrl+C` to terminate the gulp task.
 
 ## Next steps
 
-Congratulations on connecting your web part to SharePoint list data! You can continue building out your Hello World web part in the next topic [Deploy your web part to a SharePoint page](./serve-your-web-part-in-a-sharepoint-page). You will learn how to deploy and preview the Hello World web part in a classic SharePoint server-side page.
+Congratulations on connecting your web part to SharePoint list data! You can continue building out your Hello World web part in the next topic [Deploy your web part to a SharePoint page](./serve-your-web-part-in-a-sharepoint-page.md). You will learn how to deploy and preview the Hello World web part in a classic SharePoint server-side page.
diff --git a/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md b/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md
index 1e11ed28f1..5f5626e0b3 100644
--- a/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md
+++ b/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md
@@ -1,3 +1,10 @@
+---
+title: Deploy your SharePoint client-side web part to a CDN
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Deploy your SharePoint client-side web part to a CDN
 
 In this article, you will deploy the **HelloWorld** assets to a remote CDN instead of using the local environment. You'll use an Azure Storage account integrated with a CDN to deploy your assets. SharePoint Framework build tools provide out-of-the-box support for deploying to an Azure Storage account; however, you can also manually upload the files to your favorite CDN provider or to SharePoint.
@@ -5,16 +12,16 @@ In this article, you will deploy the **HelloWorld** assets to a remote CDN inste
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=FDGatKnjNeM&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=FDGatKnjNeM&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial4.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial4.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 ## Prerequisites
 
 Make sure that you have completed the following tasks before you begin:
 
-* [Build your first client-side web part](./build-a-hello-world-web-part)
-* [Connect your client-side web part to SharePoint](./connect-to-sharepoint)
-* [Deploy your client-side web part to a classic SharePoint page](./serve-your-web-part-in-a-sharepoint-page)
+* [Build your first client-side web part](./build-a-hello-world-web-part.md)
+* [Connect your client-side web part to SharePoint](./connect-to-sharepoint.md)
+* [Deploy your client-side web part to a classic SharePoint page](./serve-your-web-part-in-a-sharepoint-page.md)
 
 ## Configure Azure storage account
 
@@ -28,7 +35,7 @@ This is the name you used to create your storage account, as described in [Step
 
 For example, in the following screenshot, **spfxsamples** is the storage account name.
 
-![Screenshot that shows the Create a new storage account page](../../../../images/deploy-create-storage-account.png)
+![Screenshot that shows the Create a new storage account page](../../../images/deploy-create-storage-account.png)
 
 This will create a new storage account endpoint **spfxsamples.blob.core.windows.net**. 
 
@@ -44,13 +51,13 @@ Select the **+ Container** and create a new container with the following:
 * Name: **helloworld-webpart**
 * Access type: Container
 
-![Image that shows the option to create blob container](../../../../images/deploy-option-blob-container.png)
+![Image that shows the option to create blob container](../../../images/deploy-option-blob-container.png)
 
 ### Storage account access key
 
 In the storage account dashboard, choose **Access Key** in the dashboard and copy one of the access keys.
 
-![Image that shows the storage account access key](../../../../images/deploy-storage-account-accesskey.png)
+![Image that shows the storage account access key](../../../images/deploy-storage-account-accesskey.png)
 
 ### CDN profile and endpoint
 
@@ -60,13 +67,13 @@ Create a new CDN profile as described in [Step 2: Create a new CDN profile](http
 
 For example, in the following screenshot, **spfxwebparts** is the CDN profile name.
 
-![Screenshot of create a new CDN profile](../../../../images/deploy-create-cdn-profile.png)
+![Screenshot of create a new CDN profile](../../../images/deploy-create-cdn-profile.png)
 
 Create a CDN endpoint as described in [Step 3: Create a new CDN endpoint](https://azure.microsoft.com/en-us/documentation/articles/cdn-create-a-storage-account-with-cdn/#step-3-create-a-new-cdn-endpoint).
 
 For example, in the following screenshot, **spfxsamples** is the endpoint name, **Storage** is the origin type, and **spfxsamples.blob.core.windows.net** is the storage account.
 
-![Screenshot of create CDN endpoint](../../../../images/deploy-create-cdn-endpoint.png)
+![Screenshot of create CDN endpoint](../../../images/deploy-create-cdn-endpoint.png)
 
 The CDN endpoint will be created with the following URL: http://spfxsamples.azureedge.net
 
@@ -200,7 +207,7 @@ Upload or drag & drop the client-side solution package to the App Catalog.
 
 Because you already  deployed the package, you will be prompted as to whether to replace the existing package.
 
-![Screenshot of replace client-side solution package prompt](../../../../images/sp-app-replace-pkg.png)
+![Screenshot of replace client-side solution package prompt](../../../images/sp-app-replace-pkg.png)
 
 Choose **Replace It**.
 
@@ -228,4 +235,4 @@ As long as you are updating the **cdnBasePath** accordingly, your files are bein
 
 ## Next steps
 
-You can load jQuery, jQuery UI and build a jQuery Accordion web part. To continue, see [Add jQueryUI Accordion to your client-side web part](./add-jqueryui-accordion-to-web-part).
+You can load jQuery, jQuery UI and build a jQuery Accordion web part. To continue, see [Add jQueryUI Accordion to your client-side web part](./add-jqueryui-accordion-to-web-part.md).
diff --git a/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md b/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md
index 39f251079b..dbf9729d27 100644
--- a/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md
+++ b/docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md
@@ -1,3 +1,10 @@
+---
+title: Hosting client-side web part from Office 365 CDN
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Hosting client-side web part from Office 365 CDN
 
 This article describes how to host your client-side web part from Office 365 CDN. Office 365 CDN provide you easy solution to host your assets directly from your own Office 365 tenant. It can be used for hosting any static assets, which are used in SharePoint Online. You can find more details around the Office 365 CDN capability from following blog post.
@@ -28,7 +35,7 @@ Open up a browser and move to a site collection where you'd like to host your CD
 
 Create a new document library on your site collection called **CDN** and add a folder called **helloworld** to it.
 
-![helloworld-webpart folder in CDN library](../../../../images/cdn-helloworld-folder.png) 
+![helloworld-webpart folder in CDN library](../../../images/cdn-helloworld-folder.png) 
 
 Move back to your PowerShell console and add a new CDN origin. Update the provided URL below to match your own environment. 
 ```
@@ -40,7 +47,7 @@ Get-SPOTenantCdnOrigins -CdnType Public
 ```
 Notice that your newly added origin is listed as a valid CDN origin. Final configuration of the origin will take a while (approximately 15 minutes), so we can continue by creating your test web part, which will be hosted from the origin, when the deployment is completed. 
 
-![List of public origins in tenant](../../../../images/cdn-public-origins.png)
+![List of public origins in tenant](../../../images/cdn-public-origins.png)
 
 > When origin is listed without the *(configuration pending)* text, it is ready to be used in your tenant. This is the indication of an on-going configuration between SharePoint Online and CDN system. 
 
@@ -72,7 +79,7 @@ When prompted:
 * Use **HelloWord** for your web part name and choose **Enter**.
 * Accept the default **HelloWorld description** and choose **Enter**.
 
-![Yeoman generator questions around the newly created web part](../../../../images/cdn-create-webpart-yo.png)
+![Yeoman generator questions around the newly created web part](../../../images/cdn-create-webpart-yo.png)
 
 At this point, Yeoman will scaffold the solution files and install the required dependencies. This might take a few minutes. Yeoman will scaffold the project to include your custom web part as well.
 	
@@ -88,7 +95,7 @@ Update the *write-manifests.json* file (under *config* folder) as follow to poin
 https://publiccdn.sharepointonline.com/<tenant host name>/sites/site/library/folder
 ```
 
-![Updated write manifest content with path to CDN endpoint](../../../../images/cdn-write-manifest-json.png)
+![Updated write manifest content with path to CDN endpoint](../../../images/cdn-write-manifest-json.png)
 
 Save your changes.
 
@@ -109,7 +116,7 @@ This command will create a **sphosted-webpart.sppkg** package on the **sharepoin
 
 Upload or drag & drop the newly created client-side solution package to the app catalog in your tenant. 
 
-![Installation popup from app catalog for the SPFx solution](../../../../images/cdn-upload-solution-to-app-catalog.png)
+![Installation popup from app catalog for the SPFx solution](../../../images/cdn-upload-solution-to-app-catalog.png)
 
 Choose **Deploy**
 
@@ -117,7 +124,7 @@ Move to the site collection where the **CDN** library was created earlier in thi
 
 Upload all files from **temp/deploy** folder to the **CDN/helloworld** folder in your site collection. 
 
-![helloworld folder in SPO tenant with the web part assets copied from the temp/deploy folder](../../../../images/cdn-web-part-files-in-folder.png)
+![helloworld folder in SPO tenant with the web part assets copied from the temp/deploy folder](../../../images/cdn-web-part-files-in-folder.png)
 
 At this point the web part is ready to be used on a page
 
@@ -125,15 +132,15 @@ Open a site where you want to test the web part and go the **Site contents** pag
 
 Choose **Add – App** from the toolbar and choose the **sphosted-webpart-client-side-solution** app to be installed on the site
 
-![Adding web part solution to site](../../../../images/cdn-add-webpart-to-site.png)
+![Adding web part solution to site](../../../images/cdn-add-webpart-to-site.png)
 
 After the solution has been installed, chose **Add a page** from the *gear* menu and pick **HelloWorld** from the modern page web part picker
 
-![HelloWorld web part visible in web part picker for modern page](../../../../images/cdn-web-part-picker.png)
+![HelloWorld web part visible in web part picker for modern page](../../../images/cdn-web-part-picker.png)
 
 Notice how the web part is rendered even though you are not running the node.js service locally. 
 
-![HelloWorld web part rendering on a modern page, which is in edit mode](../../../../images/cdn-web-part-rendering.png)
+![HelloWorld web part rendering on a modern page, which is in edit mode](../../../images/cdn-web-part-rendering.png)
 
 Save changes on the page with web part on it.
 
@@ -141,7 +148,7 @@ Press **F12** to open up developer tools.
 
 Extend **publiccdn.sharepointonline.com** under the source and notice how the **hello-world.bundle** file is loaded from the CDN endpoint which we defined earlier in this tutorial.
 
-![HelloWorld web part bundle coming from public CDN URL in the sources tab of Chrome developer tools](../../../../images/cdn-web-part-f12-source.png)
+![HelloWorld web part bundle coming from public CDN URL in the sources tab of Chrome developer tools](../../../images/cdn-web-part-f12-source.png)
 
 Now you have deployed your custom web part to SharePoint Online and it's being hosted from the Office 365 CDN. 
 
diff --git a/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md b/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md
index 085b59bcfe..e4c782763c 100644
--- a/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md
+++ b/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md
@@ -1,3 +1,10 @@
+---
+title: Provisioning SharePoint assets from your SharePoint client-side web part
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Provisioning SharePoint assets from your SharePoint client-side web part
 
 This article describes how to provision SharePoint assets as part of the SharePoint Framework solution. These assets are deployed to SharePoint sites when the solution is installed on it. Article also covers needed steps for introducing possible updates as part of new versions of the package. This process is exactly the same as for add-in update.
@@ -11,7 +18,7 @@ Complete the following steps before you start to understand the basic flow of cr
 ## Resources
 See following resources for additional details around the covered topics in this tutorial.
 
-* [Provision SharePoint assets with your solution package](../../toolchain/provision-sharepoint-assets)
+* [Provision SharePoint assets with your solution package](../../toolchain/provision-sharepoint-assets.md)
 * [Sample solution - Deployment of SharePoint assets as part of SPFx package](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-feature-framework)
 
 ## Create a new web part project
@@ -62,7 +69,7 @@ We'll first need to create an **assets** folder where we will place all feature
 
 Your solution structure should be looking like in the following picture
 
-![Screenshot showing assets folder under sharepoint folder in the solution structure](../../../../images/tutorial-feature-solution-initial-structure.png)
+![Screenshot showing assets folder under sharepoint folder in the solution structure](../../../images/tutorial-feature-solution-initial-structure.png)
 
 ## Create feature framework files for initial deployment
 To be able to provision SharePoint assets to sites with feature framework elements, we'll need to create needed xml files to the asset folder. Supported elements for the SharePoint Framework solution packages are following:
@@ -259,7 +266,7 @@ asset-deployment-webpart.sppkg
 ```
 Before testing the package in the SharePoint, let's quickly have a look on the default structures created for the package around the defined feature framework elements. Move back to Visual Studio Code side and expand `sharepoint/solution/debug` folder, which contains the raw xml structures to be included in the actual **sppkg** package.
 
-![Screenshot showing debug folder under sharepoint folder in the solution structure](../../../../images/tutorial-feature-solution-debug-folder.png)
+![Screenshot showing debug folder under sharepoint folder in the solution structure](../../../images/tutorial-feature-solution-debug-folder.png)
 
 Next you need to deploy the package that was generated to the App Catalog.
 
@@ -267,7 +274,7 @@ Go to your site's App Catalog.
 
 Upload or drag and drop the asset-deployment-webpart.sppkg located in the `sharepoint/solution` folder  to the App Catalog. SharePoint will display a dialog and ask you to trust the client-side solution to deploy.
 
-![Trust dialog for the solution package deployment](../../../../images/tutorial-feature-solution-trust-app-catalog.png)
+![Trust dialog for the solution package deployment](../../../images/tutorial-feature-solution-trust-app-catalog.png)
 
 > Note. SharePoint validates the published package when it's deployed and you only see the trust dialog, if package is valid for deployment. You can also see the status around this validation from the 'Valid App Package' column in the app catalog.
 
@@ -277,17 +284,17 @@ Chose the gears icon on the top nav bar on the right and choose **Add an app** t
 
 In the **Search** box, enter **deployment** and choose **Enter** to filter your apps. 
 
-![Search for the app in the site](../../../../images/tutorial-feature-solution-add-app.png)
+![Search for the app in the site](../../../images/tutorial-feature-solution-add-app.png)
 
 Choose the **asset-deployment-webpart-client-side-solution** app to install the app on the site. When installation is completed, refresh the page by pressing **F5**.
 
-![New SPFx List and app being visible in site contents page after solution provisioning](../../../../images/tutorial-feature-solution-provision-app.png)
+![New SPFx List and app being visible in site contents page after solution provisioning](../../../images/tutorial-feature-solution-provision-app.png)
 
 Notice how the custom **SPFx List** has been also provisioned to site as part of the solution package deployment.
 
 Click **SPFx List** to move to the list
 
-![Default list view for a custom list showing additional fields by default](../../../../images/tutorial-feature-solution-list-view.png)
+![Default list view for a custom list showing additional fields by default](../../../images/tutorial-feature-solution-list-view.png)
 
 Notice how the custom fields **Amount** and **Cost Center** are visible automatically in the default view of the list. 
 
@@ -392,13 +399,13 @@ Go to your tenant's App Catalog.
 
 Upload or drag and drop the asset-deployment-webpart.sppkg located in the `sharepoint/solution` folder  to the App Catalog. SharePoint will request you to confirm overriding the existing version.
 
-![Replace question from the app catalog](../../../../images/tutorial-feature-solution-override-sppkg.png)
+![Replace question from the app catalog](../../../images/tutorial-feature-solution-override-sppkg.png)
 
 Click **Replace It** to updated latest version to App catalog.
 
 Notice that the App Version column for the **asset-deployment-webpart-client-side-solution** is now updated to be "2.0.0.0".
 
-![Close up for solution row in app catalog with updated version number](../../../../images/tutorial-feature-solution-version-2.png)
+![Close up for solution row in app catalog with updated version number](../../../images/tutorial-feature-solution-version-2.png)
 
 ### Update existing instance in the site
 Now that the package has been updated in the App Catalog, we can move to the actual SharePoint content site and perform the upgrade for the existing instance.
@@ -407,18 +414,18 @@ Move to site where you deployed first version of the SharePoint Framework soluti
 
 Chose **About** from the context menu of the **asset-deployment-webpart-client-side-solution** solution
 
-![Context menu of existing package in site](../../../../images/tutorial-feature-solution-hover-menu.png)
+![Context menu of existing package in site](../../../images/tutorial-feature-solution-hover-menu.png)
 
 This will present the current details around installed SharePoint Framework solution. This page also now shows a text as '*There is a new version of this app. Get it now*' to indicate that there's a new version available.
 
-![Context menu of existing package in site](../../../../images/tutorial-feature-solution-app-details.png)
+![Context menu of existing package in site](../../../images/tutorial-feature-solution-app-details.png)
 
 Click **GET IT** button to start update process for the package.
 
-![App status updated to updating in the site contents page](../../../../images/tutorial-feature-solution-updating-app.png)
+![App status updated to updating in the site contents page](../../../images/tutorial-feature-solution-updating-app.png)
 
 Update can take a while, but when the add-in status is moved to normal again, you can click **F5** to refresh the site contents page to confirm that new list has been successfully provisioned as part of the update process.
 
-![Site contents page with additional New List being created](../../../../images/tutorial-feature-solution-new-list.png)
+![Site contents page with additional New List being created](../../../images/tutorial-feature-solution-new-list.png)
 
 Now we have successfully upgrade this instance to the latest version. This Feature Framework option for SharePoint asset provisioning is pretty much the same as it is for the SharePoint add-in model. Key difference however is that the assets are being provisioned directly to normal SharePoint site, since there's no concept called app / add-in web with SharePoint Framework solutions. 
diff --git a/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md b/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md
index a41bf09534..db0a29bd06 100644
--- a/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md
+++ b/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md
@@ -1,22 +1,29 @@
+---
+title: Deploy your client-side web part to a SharePoint page (Hello world part 3)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Deploy your client-side web part to a SharePoint page (Hello world part 3)
 
-In this article you will learn how to deploy your client-side web part to SharePoint and see it working on a modern SharePoint server-side page. This article continues with the hello world web part built in the previous article [Connect your client-side web part to SharePoint](./connect-to-sharepoint).
+In this article you will learn how to deploy your client-side web part to SharePoint and see it working on a modern SharePoint server-side page. This article continues with the hello world web part built in the previous article [Connect your client-side web part to SharePoint](./connect-to-sharepoint.md).
 
 Be sure you have completed the procedures in the following articles before you start:
 
-* [Build your first SharePoint client-side web part](./build-a-hello-world-web-part)
-* [Connect your client-side web part to SharePoint](./connect-to-sharepoint)
+* [Build your first SharePoint client-side web part](./build-a-hello-world-web-part.md)
+* [Connect your client-side web part to SharePoint](./connect-to-sharepoint.md)
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=asmQIfgaKSw&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=asmQIfgaKSw&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial3.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial3.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
 ## Package the HelloWorld web part
 
-In the console window, go to the web part project directory created in [Build your first SharePoint client-side web part](./build-a-hello-world-web-part).
+In the console window, go to the web part project directory created in [Build your first SharePoint client-side web part](./build-a-hello-world-web-part.md).
 
 ```
 cd helloworld-webpart
@@ -77,11 +84,11 @@ Go to your site's App Catalog.
 
 Upload or drag and drop the **helloworld-webpart.sppkg** to the App Catalog.
 
-![Upload solution to app catalog](../../../../images/upload-solution-app-catalog.png) 
+![Upload solution to app catalog](../../../images/upload-solution-app-catalog.png) 
 
 This will deploy the client-side solution package. Since this is a full trust client-side solution, SharePoint will display a dialog and ask you to trust the client-side solution to deploy.
 
-![Trust client-side solution deployment](../../../../images/sp-app-deploy-trust.png) 
+![Trust client-side solution deployment](../../../images/sp-app-deploy-trust.png) 
 	
 Choose **Deploy**
 
@@ -93,11 +100,11 @@ Choose the gears icon on the top nav bar on the right and choose **Add an app**
 
 In the **Search** box, enter **helloworld** and choose **Enter** to filter your apps.
 	
-![Add app to site](../../../../images/install-app-your-site.png) 
+![Add app to site](../../../images/install-app-your-site.png) 
 	
 Choose the **helloworld-webpart-client-side-solution** app to install the app on the site.
 	
-![Trust app](../../../../images/app-installed-your-site.png) 
+![Trust app](../../../images/app-installed-your-site.png) 
 
 The client-side solution and the web part are installed on your developer site.
 
@@ -139,19 +146,19 @@ The web part assets will be loaded from the local environment. In order to load
 	
 You should see the **HelloWorld** web part you built in the previous article that retrieves lists from the current site. 
 
-![Hello World web part in modern page](../../../../images/sp-wp-modern-page.png)
+![Hello World web part in modern page](../../../images/sp-wp-modern-page.png)
 
 ## Edit web part properties
 
 Click the **Configure element** icon (pen) in the web part to open the property pane for the web part.
 
-![Edit web part](../../../../images/edit-webpart-modern-page.png)
+![Edit web part](../../../images/edit-webpart-modern-page.png)
 
 This is the same property pane you built and previewed in the workbench.
 	
 Edit the **Description** property and enter **Client-side web parts are awesome!**
 	
-![Hello World web part in modern page](../../../../images/sp-wp-modern-page-pp.png)
+![Hello World web part in modern page](../../../images/sp-wp-modern-page-pp.png)
 
 Notice that you still have the same behaviors such as a reactive pane where the web part is updated as you type.
 	
@@ -161,4 +168,4 @@ In the toolbar, choose **Save and close** to save the page.
 
 ## Next steps
 
-Congratulations! You have deployed a client-side web part to a modern SharePoint page. You can continue building out your Hello World web part in the next topic, [Deploy your client-side web part source to a CDN](./deploy-web-part-to-cdn), where you will learn how to deploy and load the web part assets from a CDN instead of localhost.
+Congratulations! You have deployed a client-side web part to a modern SharePoint page. You can continue building out your Hello World web part in the next topic, [Deploy your client-side web part source to a CDN](./deploy-web-part-to-cdn.md), where you will learn how to deploy and load the web part assets from a CDN instead of localhost.
diff --git a/docs/spfx/web-parts/get-started/use-fabric-react-components.md b/docs/spfx/web-parts/get-started/use-fabric-react-components.md
index 5eda3a3d05..7413153b78 100644
--- a/docs/spfx/web-parts/get-started/use-fabric-react-components.md
+++ b/docs/spfx/web-parts/get-started/use-fabric-react-components.md
@@ -1,3 +1,10 @@
+---
+title: Use Office UI Fabric React components in your SharePoint client-side web part
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use Office UI Fabric React components in your SharePoint client-side web part
 
 > **Important:** You must upgrade existing projects to use @microsoft/sp-build-web@1.0.1 or later to use Office UI Fabric React. Easiest way to achieve this is to ensure that you have latest package by running `npm install -g @microsoft/generator-sharepoint` in your console before completing this tutorial. 
@@ -6,17 +13,19 @@ This article describes how to build a simple web part that uses the DocumentCard
 
 The following image shows a DocumentCard component created with Office UI Fabric React.
 
-![Image of a DocumentCard Fabric component in a SharePoint workbench](../../../../images/fabric-components-doc-card-view-ex.png)
+![Image of a DocumentCard Fabric component in a SharePoint workbench](../../../images/fabric-components-doc-card-view-ex.png)
 
 You can also follow these steps by watching the video on the [SharePoint PnP YouTube Channel](https://www.youtube.com/watch?v=1N6kNvLxyg4&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq). 
 
 <a href="https://www.youtube.com/watch?v=1N6kNvLxyg4&list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq">
-<img src="../../../../images/spfx-youtube-tutorial6.png" alt="Screenshot of the YouTube video player for this tutorial" />
+<img src="../../../images/spfx-youtube-tutorial6.png" alt="Screenshot of the YouTube video player for this tutorial" />
 </a>
 
 
 ## Creating a new Web Part project
 
+Make sure you're using the latest version of . Run `yo` and follow the prompts to create a skeleton project,.
+
 Create a new project directory in your favorite location:
 
 ```
@@ -230,4 +239,4 @@ gulp serve
 	
 In the toolbox, select your `DocumentCardExample` web part to add:
 	
-![Image of a DocumentCard Fabric component in a SharePoint workbench](../../../../images/fabric-components-doc-card-view-ex.png)
+![Image of a DocumentCard Fabric component in a SharePoint workbench](../../../images/fabric-components-doc-card-view-ex.png)
diff --git a/docs/spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x.md b/docs/spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x.md
index 187fd29d99..d399e5668d 100644
--- a/docs/spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x.md
+++ b/docs/spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x.md
@@ -1,12 +1,19 @@
+---
+title: Build SharePoint Framework client-side web parts with Angular v1.x
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build SharePoint Framework client-side web parts with Angular v1.x
 
 If you are familiar with Angular, you can also use this extremely popular framework to build client-side web parts. Thanks to its modularity, it can be used for anything ranging from complex multi-view Single Page Applications to smaller components such as web parts. Many organizations have been using Angular for building SharePoint solutions in the past. This article shows how to use Angular v1.x to build a SharePoint Framework client-side web part and have it styled using [Office UI Fabric](http://dev.office.com/fabric). During this tutorial you will build a simple web part that manages to do items.
 
-![SharePoint Framework client-side web part built using Angular displayed in SharePoint workbench](../../../../images/ng-intro-hide-finished-tasks.png)
+![SharePoint Framework client-side web part built using Angular displayed in SharePoint workbench](../../../images/ng-intro-hide-finished-tasks.png)
 
 The source of the working web part is available on GitHub at [https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/angular-todo](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/angular-todo).
 
-> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment) for building SharePoint Framework solutions.
+> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment.md) for building SharePoint Framework solutions.
 
 ## Create new project
 
@@ -35,11 +42,11 @@ When prompted, define values as follows:
 - **To do** as your web part name
 - **Simple management of to do tasks** as your web part description
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/ng-intro-yeoman-generator.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/ng-intro-yeoman-generator.png)
 
 Once the scaffolding completes, open your project folder in your code editor. In this tutorial, you will use Visual Studio Code.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/ng-intro-project-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/ng-intro-project-visual-studio-code.png)
 
 ## Add Angular
 
@@ -52,7 +59,7 @@ In this tutorial you will load Angular from CDN. To do that, in the code editor,
 }
 ```
 
-![Angular added to the config.json file](../../../../images/ng-intro-angular-config.png)
+![Angular added to the config.json file](../../../images/ng-intro-angular-config.png)
 
 ## Add Angular typings for TypeScript
 
@@ -66,7 +73,7 @@ npm install @types/angular --save-dev
 
 With all prerequisites in place you can start implementing the sample Angular application. Because it will consist of a few files, create a separate folder for it called **app**.
 
-![The app folder highlighted in Visual Studio Code](../../../../images/ng-intro-app-folder.png)
+![The app folder highlighted in Visual Studio Code](../../../images/ng-intro-app-folder.png)
 
 ### Implement to do data service
 
@@ -180,7 +187,7 @@ export default class DataService implements IDataService {
 }
 ```
 
-![The DataService.ts file opened in Visual Studio Code](../../../../images/ng-intro-dataservice.png)
+![The DataService.ts file opened in Visual Studio Code](../../../images/ng-intro-dataservice.png)
 
 In the previous code snippet you implement three types: the **ITodo** interface which represents a to do item in your application, the **IDataService** interface which defines the signature of the data service and the **DataService** class which is responsible for retrieving and manipulating to do items. The data service implements simple methods for adding and modifying to do items. Even though the operations are instantaneous, for consistency each CRUD function returns a promise.
 
@@ -298,7 +305,7 @@ export default class HomeController {
 }
 ```
 
-![The HomeController.ts file opened in Visual Studio Code](../../../../images/ng-intro-homecontroller.png)
+![The HomeController.ts file opened in Visual Studio Code](../../../images/ng-intro-homecontroller.png)
 
 You start by loading the previously implemented data service. The controller needs it in order to get the list of items and modify items as requested by the user. Using Angular's dependency injection the service is injected into the controller. The controller implements a number of functions that are exposed to the view model and will be called from the template. Using these functions users will be able to add new items, mark items as finished, to do, or delete items.
 
@@ -318,7 +325,7 @@ todoapp
   .service('DataService', DataService);
 ```
 
-![The app-module.ts file opened in Visual Studio Code](../../../../images/ng-intro-app-module.png)
+![The app-module.ts file opened in Visual Studio Code](../../../images/ng-intro-app-module.png)
 
 You start by referencing Angular and by loading previously implemented controller and data service. Next, you define the module for your application. Finally, you register the controller and data service with your application.
 
@@ -335,7 +342,7 @@ import * as angular from 'angular';
 import './app/app-module';
 ```
 
-![Import statements in the ToDoWebPart.ts file highlighted in Visual Studio Code](../../../../images/ng-intro-web-part-import-angular.png)
+![Import statements in the ToDoWebPart.ts file highlighted in Visual Studio Code](../../../images/ng-intro-web-part-import-angular.png)
 
 This allows us to load a reference to Angular and your application, both of which you need to bootstrap your Angular application.
 
@@ -389,7 +396,7 @@ public render(): void {
 }
 ```
 
-![Web part's render function in Visual Studio Code](../../../../images/ng-intro-web-part-render-angular.png)
+![Web part's render function in Visual Studio Code](../../../images/ng-intro-web-part-render-angular.png)
 
 The code first assigns the template of your application directly to the web part's DOM element. On the root element you specify the name of the controller that will handle events and data binding in the template. Then, you bootstrap your application using the **todoapp** name you used previously when declaring the main module. Using the **renderedOnce** web part property you ensure that your Angular application is bootstrapped only once. Without it, if you changed one of the web part's properties, the **render** function would be invoked again bootstrapping the Angular application again, which would lead to an error.
 
@@ -637,7 +644,7 @@ You also need to implement CSS styles that you are using the template. In the co
 }
 ```
 
-![The ToDo.module.scss file open in Visual Studio Code](../../../../images/ng-intro-web-part-css.png)
+![The ToDo.module.scss file open in Visual Studio Code](../../../images/ng-intro-web-part-css.png)
 
 Run the following command to confirm that everything is working as expected:
 
@@ -647,7 +654,7 @@ gulp serve
 
 In the browser you should see your To do web part showing to do items.
 
-![To do web part showing to do items rendered using Office UI Fabric](../../../../images/ng-intro-workbench-office-ui-fabric.png)
+![To do web part showing to do items rendered using Office UI Fabric](../../../images/ng-intro-workbench-office-ui-fabric.png)
 
 ## Make web part configurable
 
@@ -661,7 +668,7 @@ Start by adding configuration property in the web part manifest. In the code edi
 "hideFinishedTasks": false
 ```
 
-![The hideFinishedTasks property highlighted in web part manifest](../../../../images/ng-intro-manifest-property.png)
+![The hideFinishedTasks property highlighted in web part manifest](../../../images/ng-intro-manifest-property.png)
 
 ### Update the signature of the web part properties interface
 
@@ -675,7 +682,7 @@ export interface IToDoWebPartProps {
 }
 ```
 
-![The IToDoWebPartProps.ts file open in Visual Studio Code](../../../../images/ng-intro-property-interface.png)
+![The IToDoWebPartProps.ts file open in Visual Studio Code](../../../images/ng-intro-property-interface.png)
 
 ### Add the property to the web part property pane
 
@@ -691,7 +698,7 @@ import {
 } from '@microsoft/sp-webpart-base';
 ```
 
-![PropertyPaneToggle import statement highlighted in Visual Studio Code](../../../../images/ng-intro-property-pane-toggle.png)
+![PropertyPaneToggle import statement highlighted in Visual Studio Code](../../../images/ng-intro-property-pane-toggle.png)
 
 Change the implementation of the `propertyPaneSettings` function to:
 
@@ -734,7 +741,7 @@ declare module 'toDoStrings' {
 }
 ```
 
-![The loc/mystrings.d.ts file open in Visual Studio Code](../../../../images/ng-intro-strings-interface.png)
+![The loc/mystrings.d.ts file open in Visual Studio Code](../../../images/ng-intro-strings-interface.png)
 
 Next, you need to provide the actual values for the newly defined strings. In the code editor open the **loc/en-us.js** file and change its contents to:
 
@@ -748,7 +755,7 @@ define([], function() {
 });
 ```
 
-![The loc/en-us.js file open in Visual Studio Code](../../../../images/ng-intro-strings.png)
+![The loc/en-us.js file open in Visual Studio Code](../../../images/ng-intro-strings.png)
 
 Run the following command to confirm that everything is working as expected:
 
@@ -758,7 +765,7 @@ gulp serve
 
 In the web part property pane you should see a toggle button for your newly defined property.
 
-![Toggle button displayed on the web part property pane](../../../../images/ng-intro-property-pane-toggle-browser.png)
+![Toggle button displayed on the web part property pane](../../../images/ng-intro-property-pane-toggle-browser.png)
 
 At this point clicking the toggle button doesn't have any effect on your web part as it hasn't been connected to Angular. You will do that in the next step.
 
@@ -774,7 +781,7 @@ In the code editor open the **ToDoWebPart.ts** file. Right before web part's con
 private $injector: angular.auto.IInjectorService;
 ```
 
-![$injector class variable highlighted in Visual Studio Code](../../../../images/ng-intro-injector-class-variable.png)
+![$injector class variable highlighted in Visual Studio Code](../../../images/ng-intro-injector-class-variable.png)
 
 Next, change the web part's **render** function to the following:
 
@@ -847,7 +854,7 @@ constructor(private dataService: IDataService, private $window: angular.IWindowS
 }
 ```
 
-![Constructor definition in the HomeController.ts file highlighted in Visual Studio Code](../../../../images/ng-intro-homecontroller-event.png)
+![Constructor definition in the HomeController.ts file highlighted in Visual Studio Code](../../../images/ng-intro-homecontroller-event.png)
 
 To verify that the Angular application is working as expected and correctly responds to property changed, in the command line run:
 
@@ -857,4 +864,4 @@ gulp serve
 
 If you toggle the value of the **Hide finished tasks** property, web part should show or hide finished tasks accordingly.
 
-![web part showing only unfinished task with the 'Hide finished tasks' option enabled](../../../../images/ng-intro-hide-finished-tasks.png)
\ No newline at end of file
+![web part showing only unfinished task with the 'Hide finished tasks' option enabled](../../../images/ng-intro-hide-finished-tasks.png)
diff --git a/docs/spfx/web-parts/guidance/build-custom-property-pane-controls.md b/docs/spfx/web-parts/guidance/build-custom-property-pane-controls.md
index 87690ba810..3b8852beaa 100644
--- a/docs/spfx/web-parts/guidance/build-custom-property-pane-controls.md
+++ b/docs/spfx/web-parts/guidance/build-custom-property-pane-controls.md
@@ -1,14 +1,21 @@
+---
+title: Build custom controls for the property pane
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Build custom controls for the property pane
 
 The SharePoint Framework contains a set of standard controls for the property pane. But sometimes you need additional functionality beyond the basic controls. You might need asynchronous updates to the data on a control, or a specific user interface. Build a custom control for the property pane to get the functionality you need.
 
 In this article you will learn how to build a custom control for the property pane. You will build a custom dropdown control that loads its data asynchronously from an external service without blocking the user interface of the web part.
 
-![Item dropdown loading available items after selecting a list in the list dropdown](../../../../images/custom-property-pane-control-cascading-loading-items.png)
+![Item dropdown loading available items after selecting a list in the list dropdown](../../../images/custom-property-pane-control-cascading-loading-items.png)
 
 The source of the working web part is available on GitHub at [https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-custompropertypanecontrols](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-custompropertypanecontrols).
 
-> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment) for building SharePoint Framework solutions.
+> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment.md) for building SharePoint Framework solutions.
 
 ## Create new project
 
@@ -38,11 +45,11 @@ When prompted, enter the following values:
 - **Shows list items from the selected list** as your web part description
 - **React** as the starting point to build the web part
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/custom-property-pane-control-yeoman.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/custom-property-pane-control-yeoman.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/custom-property-pane-control-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/custom-property-pane-control-visual-studio-code.png)
 
 ## Define web part property for storing the selected list
 
@@ -50,7 +57,7 @@ The Web part you are building will show list items from the selected SharePoint
 
 In the code editor open the **src/webparts/listItems/ListItemsWebPartManifest.json** file. Replace the default **description** property with a new property named `listName`.
 
-![Web part manifest with the 'listName' web part property highlighted](../../../../images/custom-property-pane-control-list-property-web-part-manifest.png)
+![Web part manifest with the 'listName' web part property highlighted](../../../images/custom-property-pane-control-list-property-web-part-manifest.png)
 
 Next, open the **src/webparts/listItems/IListItemsWebPartProps.ts** file and replace its contents with:
 
@@ -169,7 +176,7 @@ gulp serve
 
 In the web browser, add the **List items** web part to the canvas and open its properties. Verify that the value set for the **List** property is displayed in the web part body.
 
-![Web part showing the value of the 'listName' property](../../../../images/custom-property-pane-control-web-part-first-run.png)
+![Web part showing the value of the 'listName' property](../../../images/custom-property-pane-control-web-part-first-run.png)
 
 ## Create asynchronous dropdown property pane control
 
@@ -195,7 +202,7 @@ When creating a custom property pane control that uses React in the SharePoint F
 
 In the project **src** folder, create a hierarchy of three new folders so that your folder structure appears as **src/controls/PropertyPaneAsyncDropdown/components**.
 
-![Components folder highlighted in Visual Studio Code](../../../../images/custom-property-pane-control-components-folder.png)
+![Components folder highlighted in Visual Studio Code](../../../images/custom-property-pane-control-components-folder.png)
 
 #### Define asynchronous dropdown React component properties
 
@@ -481,7 +488,7 @@ import { IDropdownOption } from 'office-ui-fabric-react/lib/components/Dropdown'
 import { update, get } from '@microsoft/sp-lodash-subset';
 ```
 
-![References to the 'PropertyPaneAsyncDropdown' class and the 'IDropdownOption' interface highlighted in Visual Studio Code](../../../../images/custom-property-pane-control-web-part-imports.png)
+![References to the 'PropertyPaneAsyncDropdown' class and the 'IDropdownOption' interface highlighted in Visual Studio Code](../../../images/custom-property-pane-control-web-part-imports.png)
 
 #### Add method to load available lists
 
@@ -567,9 +574,9 @@ At this point you should be able to select a list using the newly created asynch
 gulp serve
 ```
 
-![Asynchronous dropdown property pane control loading its options without blocking the web part user interface](../../../../images/custom-property-pane-control-loading-options.png)
+![Asynchronous dropdown property pane control loading its options without blocking the web part user interface](../../../images/custom-property-pane-control-loading-options.png)
 
-![Selecting one of the options in the asynchronous dropdown property pane control](../../../../images/custom-property-pane-control-selecting-option.png)
+![Selecting one of the options in the asynchronous dropdown property pane control](../../../images/custom-property-pane-control-selecting-option.png)
 
 ## Implement cascading dropdowns using the asynchronous dropdown property pane control
 
@@ -588,7 +595,7 @@ In the code editor open the **src/webparts/listItems/ListItemsWebPart.manifest.j
 // ...
 ```
 
-![Web part manifest with the 'item' web part property highlighted](../../../../images/custom-property-pane-control-item-property-web-part-manifest.png)
+![Web part manifest with the 'item' web part property highlighted](../../../images/custom-property-pane-control-item-property-web-part-manifest.png)
 
 Change the code in the **src/webparts/listItems/IListItemsWebPartProps.ts** file to:
 
@@ -839,20 +846,20 @@ gulp serve
 
 After adding the web part to the page for the first time and opening its property pane, you should see both dropdowns disabled and loading their options.
 
-![Dropdowns in web part property pane loading their data](../../../../images/custom-property-pane-control-cascading-loading-lists.png)
+![Dropdowns in web part property pane loading their data](../../../images/custom-property-pane-control-cascading-loading-lists.png)
 
 After the options have been loaded, the list dropdown becomes enabled. Because no list has been selected yet, the item dropdown remains disabled.
 
-![List dropdown in web part property pane enabled. Item dropdown disabled](../../../../images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png)
+![List dropdown in web part property pane enabled. Item dropdown disabled](../../../images/custom-property-pane-control-cascading-lists-loaded-items-disabled.png)
 
 After selecting a list in the list dropdown the item dropdown will load items available in that list.
 
-![Item dropdown loading available items after selecting a list in the list dropdown](../../../../images/custom-property-pane-control-cascading-loading-items.png)
+![Item dropdown loading available items after selecting a list in the list dropdown](../../../images/custom-property-pane-control-cascading-loading-items.png)
 
 After the available items have been loaded, the item dropdown becomes enabled.
 
-![Selecting a list item from the item dropdown in the web part property pane](../../../../images/custom-property-pane-control-cascading-items-loaded-enabled.png)
+![Selecting a list item from the item dropdown in the web part property pane](../../../images/custom-property-pane-control-cascading-items-loaded-enabled.png)
 
 After selecting an item in the item dropdown the web part is refreshed showing the selected item in its body.
 
-![Selected list and item rendered in the web part](../../../../images/custom-property-pane-control-cascading-selected-list-item.png)
+![Selected list and item rendered in the web part](../../../images/custom-property-pane-control-cascading-selected-list-item.png)
diff --git a/docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md b/docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
index a05b02c4c0..70ae61d361 100644
--- a/docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
+++ b/docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
@@ -1,3 +1,10 @@
+---
+title: Call the Microsoft Graph API using OAuth from your web part
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Call the Microsoft Graph API using OAuth from your web part
 
 You can add lots of great functionality such as email, documents, and calendar to your web part by integrating with the Microsoft Graph. To call APIs on Microsoft Graph you will need to use the Active Directory Authentication Library (ADAL) for JavaScript library and authenticate using the OAuth flow. There are some design considerations and code modifications to make for your web part to use ADAL JS and call Microsoft Graph APIs correctly and securely.
diff --git a/docs/spfx/web-parts/guidance/connect-to-api-secured-with-aad.md b/docs/spfx/web-parts/guidance/connect-to-api-secured-with-aad.md
index 51f9ff0dee..0cc249532f 100644
--- a/docs/spfx/web-parts/guidance/connect-to-api-secured-with-aad.md
+++ b/docs/spfx/web-parts/guidance/connect-to-api-secured-with-aad.md
@@ -1,3 +1,10 @@
+---
+title: Connect to API secured with Azure Active Directory
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Connect to API secured with Azure Active Directory
 
 When building SharePoint Framework solutions you might need to connect to your custom API to retrieve some data or to communicate with line of business applications. Securing custom APIs with Azure Active Directory offers you a number of benefits and can be done in a number of ways. Once you have built the API, there are a number of ways in which you can access it. These ways vary in complexity and each have their specific considerations. This article discusses the different approaches and describes step-by-step the process of building and connecting to an API secured with Azure Active Directory.
@@ -14,7 +21,7 @@ When building custom APIs there are two main ways in which you can secure your A
 
 When deploying custom APIs to Azure App Service you can benefit of the App Service Authentication option to secure the API with Azure Active Directory. The biggest benefit of using App Service Authentication is its simplicity: by following the configuration steps available in the Azure Portal you can either have the wizard setup the authentication configuration for you. If you choose the basic setup, the wizard will create a new AAD application in the Azure Active Directory associated with the current subscription. In the advanced configuration, you can choose which AAD application should be used to secure the access to the App Service hosting the API.
 
-![App Service Authentication settings displayed in the Azure Portal](../../../../images/api-aad-azure-app-service-authentication.png)
+![App Service Authentication settings displayed in the Azure Portal](../../../images/api-aad-azure-app-service-authentication.png)
 
 Once App Service Authentication has been configured, users trying to access your API will be prompted to sign in with their organizational account that belongs to the same Azure Active Directory as the AAD application used to secure the API. After signing in, you will be able to access the information about the current user through the `HttpContext.Current.User` property. When using the Azure App Service Authentication there is no additional configuration required in your application.
 
@@ -24,7 +31,7 @@ Azure App Service Authentication is a feature available only in Microsoft Azure
 
 If you want to have the maximum flexibility with regards to where your API is hosted and how it is deployed, you should consider implementing the support for AAD authentication in ASP.NET. Visual Studio simplifies the implementation process significantly and after completing the authentication setup wizard, your API will require users to sign in using their organizational account.
 
-![Visual Studio authentication setup wizard](../../../../images/api-aad-visual-studio-authentication-wizard.png)
+![Visual Studio authentication setup wizard](../../../images/api-aad-visual-studio-authentication-wizard.png)
 
 During the configuration process, Visual Studio will add all the necessary references and settings to your ASP.NET Web API project, including registering a new AAD application to secure your API.
 
@@ -40,15 +47,15 @@ A commonly used approach for communicating with APIs secured with Azure Active D
 
 When using ADAL JS, client-side applications have full access to the identity information of the currently signed-in user. This is convenient for requirements such as displaying user name or profile picture in the application. When building solutions hosted in SharePoint, developers can retrieve extended profile information using the SharePoint API, but for standalone applications this isn't possible.
 
-Besides facilitating authentication against AAD, ADAL JS is capable of retrieving access tokens to specific resources. With these access tokens, applications can securely access APIs secured with AAD such as the [Microsoft Graph](./call-microsoft-graph-from-your-web-part) or other custom APIs. Before a client-side application can use ADAL JS, it has to be registered as an application in Azure Active Directory. In the registration process, developers specify a number of parameters such as the URL where the application is hosted and the resources to which the application requires access, either by itself or on behalf of the currently signed-in user.
+Besides facilitating authentication against AAD, ADAL JS is capable of retrieving access tokens to specific resources. With these access tokens, applications can securely access APIs secured with AAD such as the [Microsoft Graph](./call-microsoft-graph-from-your-web-part.md) or other custom APIs. Before a client-side application can use ADAL JS, it has to be registered as an application in Azure Active Directory. In the registration process, developers specify a number of parameters such as the URL where the application is hosted and the resources to which the application requires access, either by itself or on behalf of the currently signed-in user.
 
-![Registering new Azure Active Directory application in the Azure Portal](../../../../images/api-aad-create-new-aad-app.png)
+![Registering new Azure Active Directory application in the Azure Portal](../../../images/api-aad-create-new-aad-app.png)
 
 The first time the application is used, it prompts the user to grant it the necessary permissions. This is often referred to as consent flow. Once approved, the application can then request access tokens for the specific resources and communicate with them securely.
 
 #### Considerations when using ADAL JS to communicate with APIs secured with AAD
 
-ADAL JS has been designed to be used with single-page applications. As such, by default it doesn't work correctly when used with SharePoint Framework solutions. By [applying a patch](./call-microsoft-graph-from-your-web-part) however, it can be successfully used in SharePoint Framework projects.
+ADAL JS has been designed to be used with single-page applications. As such, by default it doesn't work correctly when used with SharePoint Framework solutions. By [applying a patch](./call-microsoft-graph-from-your-web-part.md) however, it can be successfully used in SharePoint Framework projects.
 
 When using ADAL JS and OAuth to access APIs secured with AAD, the authentication flow is facilitated by Microsoft Azure. Any errors are handled by the Azure sign-in page. Once the user has signed-in with her organizational account, the application will try to retrieve a valid access token. All errors that occur at this stage have to be explicitly handled by the developer of the application as retrieving access tokens is non-interactive and doesn't present any UI to the user.
 
@@ -214,19 +221,19 @@ Following is how you would use Azure Functions to create an API secured with Azu
 
 In the Azure Portal go to your Resource Group and add a Function App.
 
-![Function App highlighted in the list of available services that can be added to a Resource Group](../../../../images/api-aad-create-new-function-app.png)
+![Function App highlighted in the list of available services that can be added to a Resource Group](../../../images/api-aad-create-new-function-app.png)
 
 Once the Function App has been provisioned, open the newly created Function App and add a new function by clicking the plus icon next to the Functions label.
 
-![The plus icon next to the Functions label highlighted on the Function App blade](../../../../images/api-aad-add-function.png)
+![The plus icon next to the Functions label highlighted on the Function App blade](../../../images/api-aad-add-function.png)
 
 On the quick start screen, scroll down to the **Get started on your own** section and choose the **Custom function** option.
 
-![The Custom function link highlighted on the Add new function screen](../../../../images/api-aad-custom-function.png)
+![The Custom function link highlighted on the Add new function screen](../../../images/api-aad-custom-function.png)
 
 From the list of templates choose **HttpTrigger-JavaScript**. As the function name, use **Orders** and set the function Authorization level to **Anonymous** as you will use Azure AD to secure the access to the Azure Function. Confirm your selection by clicking the **Create** button.
 
-![New Azure Function configuration](../../../../images/api-aad-add-function-parameters.png)
+![New Azure Function configuration](../../../images/api-aad-add-function-parameters.png)
 
 #### Implement API code
 
@@ -299,7 +306,7 @@ Change the URL specified in the **Access-Control-Allow-Origin** header to match
 
 Save the changes to the function's code by clicking the **Save** button.
 
-![Save button highlighted on the Azure Function code screen](../../../../images/api-aad-function-code.png)
+![Save button highlighted on the Azure Function code screen](../../../images/api-aad-function-code.png)
 
 #### Change CORS settings
 
@@ -307,37 +314,37 @@ Azure Functions are hosted in Azure App Service which allows you to configure it
 
 In the Function App, select your Azure Function and navigate to the **Platform features** blade.
 
-![The Platform features link highlighted in the Azure Function settings](../../../../images/api-aad-platform-features.png)
+![The Platform features link highlighted in the Azure Function settings](../../../images/api-aad-platform-features.png)
 
 From the **API** section, choose the **CORS** option.
 
-![The CORS option highlighted on the Azure Function Platform features blade](../../../../images/api-aad-function-cors.png)
+![The CORS option highlighted on the Azure Function Platform features blade](../../../images/api-aad-function-cors.png)
 
 On the CORS settings blade, delete all entries so that the CORS configuration is empty.
 
-![The Delete option highlighted on the first CORS entry](../../../../images/api-aad-function-cors-delete.png)
+![The Delete option highlighted on the first CORS entry](../../../images/api-aad-function-cors-delete.png)
 
 Confirm the deletion by clicking the **Save** button.
 
-![The Save button highlighted on the CORS settings blade](../../../../images/api-aad-function-cors-save.png)
+![The Save button highlighted on the CORS settings blade](../../../images/api-aad-function-cors-save.png)
 
 #### Enable App Service Authentication
 
 In the Function App settings, go back to the Platform settings blade. From the **Networking** section, select the **Authentication / Authorization** option.
 
-![The Authentication / Authorization option highlighted on the Function App Platform settings blade](../../../../images/api-aad-function-authentication.png)
+![The Authentication / Authorization option highlighted on the Function App Platform settings blade](../../../images/api-aad-function-authentication.png)
 
 Enable the App Service Authentication by setting the **App Service Authentication** toggle to **On**.
 
-![The App Service Authentication toggle set to on](../../../../images/api-aad-function-authentication-on.png)
+![The App Service Authentication toggle set to on](../../../images/api-aad-function-authentication-on.png)
 
 To disallow anonymous access to the API and force authentication using Azure AD, set the value of the **Action to take when request is not authenticated** drop-down to **Login with Azure Active Directory**.
 
-![The 'Login with Azure Active Directory' option selected in the 'Action to take when request is not authenticated' drop-down](../../../../images/api-aad-function-authentication-login-aad.png)
+![The 'Login with Azure Active Directory' option selected in the 'Action to take when request is not authenticated' drop-down](../../../images/api-aad-function-authentication-login-aad.png)
 
 Next, in the list of authentication providers, select Azure Active Directory to configure it.
 
-![Azure Active Directory highlighted in the list of authentication providers](../../../../images/api-aad-function-authentication-aad.png)
+![Azure Active Directory highlighted in the list of authentication providers](../../../images/api-aad-function-authentication-aad.png)
 
 On the Active Directory Authentication blade, set the **Management mode** to **Express** and create a new AAD app.
 
@@ -349,15 +356,15 @@ On the Active Directory Authentication blade, set the **Management mode** to **E
 
 Because the app is only meant to secure the access to the Azure Function, it doesn't require any additional permissions. Confirm the selection by clicking the **OK** button.
 
-![Azure Active Directory authentication settings](../../../../images/api-aad-function-authentication-aad-app.png)
+![Azure Active Directory authentication settings](../../../images/api-aad-function-authentication-aad-app.png)
 
 When the Azure Active Directory blade closes, back on the **Authentication / Authorization** blade, click the **Save** button to confirm all changes to authentication settings.
 
-![The Save button highlighted on the Authentication / Authorization blade](../../../../images/api-aad-function-authentication-save.png)
+![The Save button highlighted on the Authentication / Authorization blade](../../../images/api-aad-function-authentication-save.png)
 
 If you try to navigate to your API URL in a new private window, you should be prompted to sign in using your Azure AD account.
 
-![Azure AD sign in page](../../../../images/api-aad-sign-in.png)
+![Azure AD sign in page](../../../images/api-aad-sign-in.png)
 
 At this point, the API is ready to be called securely from a SharePoint Framework client-side web part using the authentication cookie.
 
@@ -371,25 +378,25 @@ Following is how you would build an API using ASP.NET WebAPI, deploy it to Azure
 
 In Visual Studio, from the **File** menu, choose the **New / Project** option. In the **New Project** dialog, select C# Web templates and from the list of available templates, select the **ASP.NET Web Application** template.
 
-![The 'ASP.NET Web Application' project template selected in the New Project dialog](../../../../images/api-aad-webapi-vs-web-application.png)
+![The 'ASP.NET Web Application' project template selected in the New Project dialog](../../../images/api-aad-webapi-vs-web-application.png)
 
 As the type of ASP.NET Web Application project, select **Web API**.
 
-![Web API selected as the type of ASP.NET Web Application project to create](../../../../images/api-aad-webapi-vs-webapi.png)
+![Web API selected as the type of ASP.NET Web Application project to create](../../../images/api-aad-webapi-vs-webapi.png)
 
 Because you will use Azure App Service Authentication to secure the access to the API, click the **Change Authentication** button and select the **No Authentication** option.
 
-![The 'No Authentication' option selected as the authentication option for the newly created ASP.NET Web Application](../../../../images/api-aad-webapi-vs-no-authentication.png)
+![The 'No Authentication' option selected as the authentication option for the newly created ASP.NET Web Application](../../../images/api-aad-webapi-vs-no-authentication.png)
 
 Confirm your choice by clicking the **OK** button.
 
 Visual Studio allows you to easily deploy your WebAPI to Azure App Service. To benefit of this capability, in the **New ASP.NET Web Application** dialog, in the **Microsoft Azure** section, select the **Host in the cloud** section and in the drop-down select the **App Service** option.
 
-![App Service selected as the hosting platform for the Web Application](../../../../images/api-aad-webapi-vs-host-app-service.png)
+![App Service selected as the hosting platform for the Web Application](../../../images/api-aad-webapi-vs-host-app-service.png)
 
 In the **Create App Service** dialog, specify the name for the web app to be created and select your Azure subscription, Resource Group and App Service Plan that you want to use for this application.
 
-![App Service creation settings dialog](../../../../images/api-aad-webapi-vs-create-app-service.png)
+![App Service creation settings dialog](../../../images/api-aad-webapi-vs-create-app-service.png)
 
 Confirm your choice by clicking the **Create** button. At this point, Visual Studio will create a new Azure Web App to host your web application.
 
@@ -397,11 +404,11 @@ Confirm your choice by clicking the **Create** button. At this point, Visual Stu
 
 By default, APIs created using the ASP.NET Web Application project template don't support CORS and cannot be called by client-applications hosted on different domains. To add support for CORS to your WebAPI, click right on the project, and from the context menu choose the **Manage NuGet Packages...** option.
 
-![The 'Manage NuGet Packages' option highlighted in the project context menu in Visual Studio](../../../../images/api-aad-webapi-vs-manage-nuget.png)
+![The 'Manage NuGet Packages' option highlighted in the project context menu in Visual Studio](../../../images/api-aad-webapi-vs-manage-nuget.png)
 
 On the **Manage NuGet Packages** tab, search for a package named **Microsoft.AspNet.WebApi.Cors** and install it in your project.
 
-![The 'Microsoft.AspNet.WebApi.Cors' package highlighted on the 'Manage NuGet Packages' tab](../../../../images/api-aad-webapi-vs-cors-nuget.png)
+![The 'Microsoft.AspNet.WebApi.Cors' package highlighted on the 'Manage NuGet Packages' tab](../../../images/api-aad-webapi-vs-cors-nuget.png)
 
 #### Add data model
 
@@ -569,33 +576,33 @@ At this point, the API is code complete and can be published to the Azure Web Ap
 
 In Visual Studio, right click on the project, and from the context menu choose the **Publish...** option.
 
-![The Publish option highlighted in the project context menu](../../../../images/api-aad-webapi-vs-publish.png)
+![The Publish option highlighted in the project context menu](../../../images/api-aad-webapi-vs-publish.png)
 
 In the Publish dialog, verify that all information is correct and click the **Publish** button to start the publishing process.
 
-![Publish dialog with publish information](../../../../images/api-aad-webapi-vs-publish-settings.png)
+![Publish dialog with publish information](../../../images/api-aad-webapi-vs-publish-settings.png)
 
 Once the publishing process completes, navigate in your web browser to the API URL, eg. _http://pnp-aad-api.azurewebsites.net/api/orders_. At this point the API is not secured and can be accessed by anonymous users.
 
-![API response displayed in web browser for an anonymous user](../../../../images/api-aad-webapi-response-anonymous.png)
+![API response displayed in web browser for an anonymous user](../../../images/api-aad-webapi-response-anonymous.png)
 
 #### Secure the API using Azure App Service
 
 To secure the API using Azure AD go to the Azure Portal and open the Web App hosting your API. From the **Settings** group, select the **Authentication / Authorization** option.
 
-![Azure App Service Authentication / Authorization page displayed in the Azure Portal](../../../../images/api-aad-webapi-authentication.png)
+![Azure App Service Authentication / Authorization page displayed in the Azure Portal](../../../images/api-aad-webapi-authentication.png)
 
 To enable authentication for your Web App, set the **App Service Authentication** toggle to **On**.
 
-![The 'App Service Authentication' toggle set to On for the Web App hosting the WebAPI](../../../../images/api-aad-webapi-authentication-on.png)
+![The 'App Service Authentication' toggle set to On for the Web App hosting the WebAPI](../../../images/api-aad-webapi-authentication-on.png)
 
 To disallow anonymous access to the API, in the **Action to take when request is not authenticated** drop-down, select the **Login with Azure Active Directory** option.
 
-![The 'Login with Azure Active Directory' option selected in the 'Action to take when request is not authenticated' drop-down in Web App Authentication settings](../../../../images/api-aad-webapi-authentication-aad-login.png)
+![The 'Login with Azure Active Directory' option selected in the 'Action to take when request is not authenticated' drop-down in Web App Authentication settings](../../../images/api-aad-webapi-authentication-aad-login.png)
 
 Finally, configure Azure Active Directory authentication by from the list of authentication providers selecting **Azure Active Directory**.
 
-![Azure Active Directory highlighted in the list of authentication providers](../../../../images/api-aad-webapi-authentication-aad.png)
+![Azure Active Directory highlighted in the list of authentication providers](../../../images/api-aad-webapi-authentication-aad.png)
 
 On the Active Directory Authentication blade, set the **Management mode** to **Express** and create a new AAD app.
 
@@ -607,15 +614,15 @@ On the Active Directory Authentication blade, set the **Management mode** to **E
 
 Because the app is only meant to secure the access to the Azure Function, it doesn't require any additional permissions. Confirm the selection by clicking the **OK** button.
 
-![Azure Active Directory authentication settings](../../../../images/api-aad-webapi-authentication-aad-ok.png)
+![Azure Active Directory authentication settings](../../../images/api-aad-webapi-authentication-aad-ok.png)
 
 When the Azure Active Directory blade closes, back on the **Authentication / Authorization** blade, click the **Save** button to confirm all changes to authentication settings.
 
-![The Save button highlighted on the Authentication / Authorization blade](../../../../images/api-aad-webapi-authentication-save.png)
+![The Save button highlighted on the Authentication / Authorization blade](../../../images/api-aad-webapi-authentication-save.png)
 
 If you try to navigate to your API URL in a new private window, you should be prompted to sign in using your Azure AD account.
 
-![Azure AD sign in page](../../../../images/api-aad-webapi-azure-sign-in.png)
+![Azure AD sign in page](../../../images/api-aad-webapi-azure-sign-in.png)
 
 At this point, the API is ready to be called securely from a SharePoint Framework client-side web part using the authentication cookie.
 
@@ -668,7 +675,7 @@ namespace PnP.Aad.Api {
 
 If you would try to access either the API or any other resource in your web application, you would get a 401 Unauthorized response.
 
-![Unauthorized response when trying to access the API](../../../../images/api-aad-webapi-anonymous-unauthorized.png)
+![Unauthorized response when trying to access the API](../../../images/api-aad-webapi-anonymous-unauthorized.png)
 
 At this point, the web application requires that all requests to its resources are authenticated, but it doesn't start the AAD login flow. In the following steps you will extend the web application so that it would redirect the user to the Azure AD login page, if she wasn't previously authenticated.
 
@@ -680,23 +687,23 @@ If you don't have an existing AAD application yet, you can create one in the Azu
 
 > **Important:** the Azure AD application, used to secure the API, should be created in the same Azure Active Directory which is used by your organization to access Office 365.
 
-![Azure Active Directory blade open in the Azure Portal](../../../../images/api-aad-webapi-azure-aad.png)
+![Azure Active Directory blade open in the Azure Portal](../../../images/api-aad-webapi-azure-aad.png)
 
 On the Azure Active Directory blade, navigate to the **App registrations** blade.
 
-![App registrations section highlighted on the Azure Active Directory blade](../../../../images/api-aad-webapi-azure-app-registrations.png)
+![App registrations section highlighted on the Azure Active Directory blade](../../../images/api-aad-webapi-azure-app-registrations.png)
 
 On the **App registrations** blade, click the **New application registration** button to register a new Azure AD application.
 
-![The 'New application registration' button highlighted on the App registrations blade](../../../../images/api-aad-webapi-azure-new-app-registration.png)
+![The 'New application registration' button highlighted on the App registrations blade](../../../images/api-aad-webapi-azure-new-app-registration.png)
 
 On the **Create** blade, provide the information about your application and confirm the creation by clicking the **Create** button.
 
-![The Create button highlighted on the Create new application registration blade](../../../../images/api-aad-webapi-azure-new-app-registration-create.png)
+![The Create button highlighted on the Create new application registration blade](../../../images/api-aad-webapi-azure-new-app-registration-create.png)
 
 After the application registration is successfully created, select it in the list to view its details.
 
-![Application registration information displayed in the Azure Portal](../../../../images/api-aad-webapi-azure-app-details.png)
+![Application registration information displayed in the Azure Portal](../../../images/api-aad-webapi-azure-app-details.png)
 
 From the application registration information, copy the **Application ID** and store it as you will need it when configure Azure AD authentication for your web application.
 
@@ -767,4 +774,4 @@ This concludes the configuration process. If you start your web application, bef
 ## See also
 
 - [
-Call custom APIs secured with Azure Active Directory without ADAL JS (code sample)](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/aad-api-spo-cookie)
\ No newline at end of file
+Call custom APIs secured with Azure Active Directory without ADAL JS (code sample)](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/aad-api-spo-cookie)
diff --git a/docs/spfx/web-parts/guidance/connect-to-sharepoint-using-jsom.md b/docs/spfx/web-parts/guidance/connect-to-sharepoint-using-jsom.md
index 203bd6cab0..a0a97ea31f 100644
--- a/docs/spfx/web-parts/guidance/connect-to-sharepoint-using-jsom.md
+++ b/docs/spfx/web-parts/guidance/connect-to-sharepoint-using-jsom.md
@@ -1,8 +1,15 @@
+---
+title: Connect to SharePoint using the JavaScript Object Model (JSOM)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Connect to SharePoint using the JavaScript Object Model (JSOM)
 
 In the past, when building SharePoint customizations you might have used the SharePoint JavaScript Object Model (JSOM) to communicate with SharePoint. This is no longer the recommended path (see **Considerations** below), but there are still valid use cases such as code migration. This article demonstrates how to use SharePoint JSOM when building solutions on the SharePoint Framework.
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint Framework development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint Framework development environment](../../set-up-your-development-environment.md).
 
 ## Create a New Project
 
@@ -33,11 +40,11 @@ When prompted, enter the following values:
 - **SharePoint lists** as your web part name.
 - **Shows names of lists in the current site** as your web part description.
 
-![The SharePoint Framework Yeoman generator with the default choices](../../../../images/tutorial-spjsom-yo-sharepoint.png)
+![The SharePoint Framework Yeoman generator with the default choices](../../../images/tutorial-spjsom-yo-sharepoint.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![The SharePoint Framework project open in Visual Studio Code](../../../../images/tutorial-spjsom-vscode.png)
+![The SharePoint Framework project open in Visual Studio Code](../../../images/tutorial-spjsom-vscode.png)
 
 To open the directory in Visual Studio Code, from the console type:
 ```sh
@@ -228,7 +235,7 @@ export default class SharePointLists extends React.Component<ISharePointListsPro
 
 The sample client-side web part used in this article loads information about SharePoint lists in the current site after clicking a button.
 
-![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../../images/tutorial-spjsom-web-part-list-titles.png)
+![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../images/tutorial-spjsom-web-part-list-titles.png)
 
 In the code editor, open the **./src/webparts/sharePointLists/components/SharePointLists.tsx** file. In the `SharePointLists` class add a new method named `getListsTitles`:
 
@@ -346,7 +353,7 @@ gulp serve --nobrowser
 
 As you are using SharePoint JSOM to communicate with SharePoint, you have to test the web part using the hosted version of the SharePoint workbench (which is why the `--nobrowser` parameter is specified to prevent the automatic loading of the local workbench).
 
-![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../../images/tutorial-spjsom-web-part-list-titles.png)
+![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../images/tutorial-spjsom-web-part-list-titles.png)
 
 Referencing SharePoint JSOM scripts declaratively as external scripts is convenient and allows you to keep your code clean. One disadvantage, however, is that it requires specifying absolute URLs to the location from which SharePoint JSOM scripts should be loaded. If you're using separate SharePoint tenants for development, testing, and production, then it will require some additional work to change these URLs for the different environments accordingly. In such cases, you may consider referencing JSOM imperatively by using the [SPComponentLoader](https://dev.office.com/sharepoint/reference/spfx/sp-loader/spcomponentloader) to load the scripts in the SPFx component's code.
 
@@ -572,7 +579,7 @@ gulp serve --nobrowser
 
 Just as before, the web part should show the titles of SharePoint lists in the current site.
 
-![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../../images/tutorial-spjsom-web-part-list-titles.png)
+![SharePoint Framework client-side web part showing titles of SharePoint lists in the current site](../../../images/tutorial-spjsom-web-part-list-titles.png)
 
 While using the `SPComponentLoader` requires some additional effort, it allows you to use server-relative URLs which is beneficial in scenarios when you're using different tenants for development, testing, and production.
 
diff --git a/docs/spfx/web-parts/guidance/governance-considerations.md b/docs/spfx/web-parts/guidance/governance-considerations.md
index 2964a17eb3..72b92f1d95 100644
--- a/docs/spfx/web-parts/guidance/governance-considerations.md
+++ b/docs/spfx/web-parts/guidance/governance-considerations.md
@@ -1,12 +1,19 @@
+---
+title: SharePoint Framework solutions governance considerations
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # SharePoint Framework solutions governance considerations
 
 Using the SharePoint Framework organizations can easily build solutions that make better use of capabilities available in SharePoint and Office 365. Additionally, by default, SharePoint Framework solutions work across the different devices even including the SharePoint mobile app. In order to benefit of SharePoint Framework solutions, organizations should have an actionable governance plan covering the most important considerations.
 
 ## Anatomy of SharePoint Framework solutions
 
-![Diagram illustrating the composition of SharePoint Framework solutions](../../../../images/guidance-governance-spfx-structure-schema.png)
+![Diagram illustrating the composition of SharePoint Framework solutions](../../../images/guidance-governance-spfx-structure-schema.png)
 
-SharePoint Framework solutions consist of two parts: code (often referred to as web part bundle), deployed to a URL, and an .sppkg file that contains web part manifest with a URL pointing to the location where the web part code is deployed. There are no particular restrictions with regards to where the code is deployed to, as long as users working with the web part can access the web part code. Organizations can choose for example to have their web parts deployed to the [Office 365 public CDN](https://dev.office.com/blogs/office-365-public-cdn-developer-preview-release), [Azure storage](../get-started/deploy-web-part-to-cdn) or a privately owned web server.
+SharePoint Framework solutions consist of two parts: code (often referred to as web part bundle), deployed to a URL, and an .sppkg file that contains web part manifest with a URL pointing to the location where the web part code is deployed. There are no particular restrictions with regards to where the code is deployed to, as long as users working with the web part can access the web part code. Organizations can choose for example to have their web parts deployed to the [Office 365 public CDN](https://dev.office.com/blogs/office-365-public-cdn-developer-preview-release), [Azure storage](../get-started/deploy-web-part-to-cdn.md) or a privately owned web server.
 
 ## Web part code hosting location
 
@@ -52,4 +59,4 @@ In Office 365 organizations can use the no-script setting to disable script-base
 
 The no-script setting is meant for organizations to apply an additional layer of control and security to either the whole tenant or specific site collections. Customizing SharePoint using script embedding and injecting is not without risks and particularly on sites containing sensitive information should be thoroughly evaluated.
 
-In the past developers used script embedding and injecting techniques for building powerful SharePoint customizations. In some cases, these customizations relied on specific page structure and when it changed, the particular customization would not work correctly anymore. To guide developers to build more robust solutions, the SharePoint engineering team decided, that all modern sites should have the no-script setting enabled. This means that embedding and injecting scripts on these sites is not possible and using the SharePoint Framework is currently the only option to customize these sites. The expectation is, that all modern sites in the future will use the no-script setting and alternatives to script embedding and injecting will become available for developers to support the different scenarios.
\ No newline at end of file
+In the past developers used script embedding and injecting techniques for building powerful SharePoint customizations. In some cases, these customizations relied on specific page structure and when it changed, the particular customization would not work correctly anymore. To guide developers to build more robust solutions, the SharePoint engineering team decided, that all modern sites should have the no-script setting enabled. This means that embedding and injecting scripts on these sites is not possible and using the SharePoint Framework is currently the only option to customize these sites. The expectation is, that all modern sites in the future will use the no-script setting and alternatives to script embedding and injecting will become available for developers to support the different scenarios.
diff --git a/docs/spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint.md b/docs/spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint.md
index aa96d5b3da..9045788d5c 100644
--- a/docs/spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint.md
+++ b/docs/spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint.md
@@ -1,3 +1,10 @@
+---
+title: Integrate web part properties with SharePoint
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Integrate web part properties with SharePoint
 
 When building classic web parts, web part properties were isolated from SharePoint and their values were managed by end-users. SharePoint Frameworks offers you a new set of capabilities that simplify managing web part properties' values and integrate them with SharePoint Search. This article explains how you can use these capabilities when building SharePoint Framework client-side web parts.
@@ -10,9 +17,9 @@ When building SharePoint Framework client-side web parts, you can define propert
 
 Comparing to classic web parts, there are some differences in how the SharePoint Framework handles web parts properties. The following schema illustrates how web part properties values flow through the different layers of SharePoint.
 
-![Schema illustrating how the SharePoint Framework handles web part properties](../../../../images/integrate-webpart-properties-schema.png)
+![Schema illustrating how the SharePoint Framework handles web part properties](../../../images/integrate-webpart-properties-schema.png)
 
-Before accepting values for web part properties from the end-users you should always [validate them](./validate-web-part-property-values). This will not only allow you to ensure that your web parts are user-friendly, but will also help you prevent storing invalid data in the web part's configuration. Additionally, you should consider that the SharePoint Framework doesn't support personalization and all users see the same configuration of the particular web part.
+Before accepting values for web part properties from the end-users you should always [validate them](./validate-web-part-property-values.md). This will not only allow you to ensure that your web parts are user-friendly, but will also help you prevent storing invalid data in the web part's configuration. Additionally, you should consider that the SharePoint Framework doesn't support personalization and all users see the same configuration of the particular web part.
 
 ## Specify web part property value type
 
@@ -66,4 +73,4 @@ If you specify the web part property as `isSearchablePlainText`, it will be incl
 
 When a web part property is defined as `isHtmlString`, SharePoint will first of all remove any unsafe HTML, such as `script` tags, from the property value. The HTML that remains can be considered safe to render on a page. If the value contains any URLs pointing to files stored in SharePoint, as soon as one of these files is renamed or moved, SharePoint will automatically update the URL stored in the web part property. This significantly simplifies managing URLs across all web parts and pages in your tenant. HTML web part properties are also searchable, so users can look for any keywords included in the property value.
 
-Property value types `isImageSource` and `isLink` are meant to be used for web part properties than include nothing else but a link to an image or a file stored in SharePoint. In both cases, SharePoint Search includes the content in the full-text index and keeps the specified URL up-to-date in case the referenced file is renamed or moved. Additionally, image sources may get additional processing to help images download faster. If the page has a title image and the image is amongst the first 5 images on the page or the image is in the first two rows on the page, the image will be preloaded.
\ No newline at end of file
+Property value types `isImageSource` and `isLink` are meant to be used for web part properties than include nothing else but a link to an image or a file stored in SharePoint. In both cases, SharePoint Search includes the content in the full-text index and keeps the specified URL up-to-date in case the referenced file is renamed or moved. Additionally, image sources may get additional processing to help images download faster. If the page has a title image and the image is amongst the first 5 images on the page or the image is in the first two rows on the page, the image will be preloaded.
diff --git a/docs/spfx/web-parts/guidance/localize-web-parts.md b/docs/spfx/web-parts/guidance/localize-web-parts.md
index 7c6c67990f..67d12157ce 100644
--- a/docs/spfx/web-parts/guidance/localize-web-parts.md
+++ b/docs/spfx/web-parts/guidance/localize-web-parts.md
@@ -1,8 +1,15 @@
+---
+title: Localize SharePoint Framework client-side web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Localize SharePoint Framework client-side web parts
 
 You can broaden the appeal of your SharePoint Framework client-side web part by localizing it for different languages spoken by SharePoint users all over the world. In this article, you will localize a web part to the Dutch (Netherlands) locale, and verify that the localized values are displayed correctly.
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment.md).
 
 ## Prepare the project
 
@@ -34,11 +41,11 @@ When prompted, enter the following values:
 - **Greets the user** as your web part description.
 - **React** as the starting point to build the web part.
 
-![The SharePoint Framework Yeoman generator with the default choices](../../../../images/localization-yo-sharepoint.png)
+![The SharePoint Framework Yeoman generator with the default choices](../../../images/localization-yo-sharepoint.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![The SharePoint Framework project open in Visual Studio Code](../../../../images/localization-visual-studio-code.png)
+![The SharePoint Framework project open in Visual Studio Code](../../../images/localization-visual-studio-code.png)
 
 ### Replace the default code
 
@@ -192,13 +199,13 @@ gulp serve
 
 In the SharePoint workbench add the web part to the page and open its configuration.
 
-![Greeting web part added to the page with its property pane open](../../../../images/localization-initial-changes.png)
+![Greeting web part added to the page with its property pane open](../../../images/localization-initial-changes.png)
 
 ## Localize the web part manifest
 
 Every SharePoint Framework client-side web part consists of code, and a manifest. The manifest provides information about the web part such as its title, description, and icon. When adding a web part to the page, the information from the web part manifest is displayed to users. Using this information users decide if the web part is the one that they are looking for. Providing a title and description that correctly reflect the web part's functionality is essential if you want your web part to be used. If your web part will be used in non-English sites, then localizing its metadata can improve the user experience even further.
 
-Some properties defined in the web part manifest, such as title or description, support specifying localized values. For the complete list of all web part manifest properties that support localization read the [Simplify adding web parts with preconfigured entries](./simplify-adding-web-parts-with-preconfigured-entries#properties-of-a-preconfiguredentries-array-item) article. Properties that support localization are of type **ILocalizedString**. Each localized string must specify at least the default value and optionally values for other locales.
+Some properties defined in the web part manifest, such as title or description, support specifying localized values. For the complete list of all web part manifest properties that support localization read the [Simplify adding web parts with preconfigured entries](./simplify-adding-web-parts-with-preconfigured-entries.md#properties-of-a-preconfiguredentries-array-item) article. Properties that support localization are of type **ILocalizedString**. Each localized string must specify at least the default value and optionally values for other locales.
 
 ### Add localized values for title, description, and group name
 
@@ -237,15 +244,15 @@ The web part property pane consists of sections. Each section has a header and o
 
 The localization files used by the web part are stored in the **./src/webparts/greeting/loc** folder.
 
-![Localization files used by a SharePoint Framework client-side web part highlighted in Visual Studio Code](../../../../images/localization-loc-folder.png)
+![Localization files used by a SharePoint Framework client-side web part highlighted in Visual Studio Code](../../../images/localization-loc-folder.png)
 
 The **loc** folder contains a TypeScript type definition file (**./src/webpart/greeting/loc/mystrings.d.ts**) that informs TypeScript of the different strings included in the localized files. Using the information from this file, your code editor can provide you with IntelliSense when working with strings in code. Additionally, while building your project, TypeScript can verify that you're not referring to a string that hasn't been defined.
 
-![IntelliSense for localized strings in Visual Studio Code](../../../../images/localization-intellisense.png)
+![IntelliSense for localized strings in Visual Studio Code](../../../images/localization-intellisense.png)
 
 For each locale supported by your web part, there is also a plain JavaScript file (not TypeScript) named in lowercase after the locale (for example **en-us.js**) containing the translated strings.
 
-![Standard localization file scaffolded with a new SharePoint Framework project](../../../../images/localization-standard-locale-file.png)
+![Standard localization file scaffolded with a new SharePoint Framework project](../../../images/localization-standard-locale-file.png)
 
 > **Important:** You should pay extra attention to verifying that all keys specified in the TypeScript type definition file for localization have translations in all localization JavaScript files.
 
@@ -267,7 +274,7 @@ define([], function() {
 
 Verify that the keys in the TypeScript type definition file for localization match the contents of the locale files for US English and Dutch (Netherlands).
 
-![TypeScript type definition file for localization and locale files for US English and Dutch (Netherlands) open in Visual Studio Code side by side](../../../../images/localization-keys-comparison.png)
+![TypeScript type definition file for localization and locale files for US English and Dutch (Netherlands) open in Visual Studio Code side by side](../../../images/localization-keys-comparison.png)
 
 ### Verify the localized web part property pane strings
 
@@ -292,7 +299,7 @@ gulp serve
 
 When you add the web part to the page and open its configuration you will see the strings in the web part property pane displayed in Dutch (Netherlands).
 
-![Web part property pane string displayed in Dutch (Netherlands)](../../../../images/localization-property-pane-nl-nl.png)
+![Web part property pane string displayed in Dutch (Netherlands)](../../../images/localization-property-pane-nl-nl.png)
 
 #### Specify the locale to be tested using the command line argument
 
@@ -304,7 +311,7 @@ gulp serve --locale=nl-nl
 
 Once again, when you open your web part's configuration you will see that all property pane strings are displayed in Dutch (Netherlands) rather than the default US English.
 
-![Web part property pane string displayed in Dutch (Netherlands)](../../../../images/localization-property-pane-nl-nl.png)
+![Web part property pane string displayed in Dutch (Netherlands)](../../../images/localization-property-pane-nl-nl.png)
 
 ## Localize web part contents
 
@@ -405,7 +412,7 @@ Confirm that the translated string is correctly displayed by running the followi
 gulp serve --locale=nl-nl
 ```
 
-![The label of the learn more button displayed in Dutch Netherlands instead of the default US English](../../../../images/localization-learn-more-nl-nl.png)
+![The label of the learn more button displayed in Dutch Netherlands instead of the default US English](../../../images/localization-learn-more-nl-nl.png)
 
 ## Improve globalizing and localizing web parts using pseudo-locales
 
@@ -444,11 +451,11 @@ gulp serve --locale=qps-ploc
 
 After adding the web part to the page, you can quickly see that there are two strings in the web part body that have not been internationalized and are still displayed in US English rather than in the base pseudo-locale.
 
-![Two strings in the web part body displayed in US English despite testing using the base pseudo-locale](../../../../images/localization-web-part-body-qps-ploc.png)
+![Two strings in the web part body displayed in US English despite testing using the base pseudo-locale](../../../images/localization-web-part-body-qps-ploc.png)
 
 If you open the web part property pane, you can confirm that all strings and their special characters are displayed properly and that they fit in the available space correctly.
 
-![Web part property pane open when testing the web part in the local workbench using the base pseudo-locale](../../../../images/localization-web-part-property-pane-qps-ploc.png)
+![Web part property pane open when testing the web part in the local workbench using the base pseudo-locale](../../../images/localization-web-part-property-pane-qps-ploc.png)
 
 ## Localize web part settings values
 
@@ -458,11 +465,11 @@ Web parts used on multilingual sites should automatically detect the currently u
 
 Values configured through web part properties are not stored in resource files. By default, the configured value is used as-is, which might lead to inconsistencies such as greeting the user in English when the user's preferred language is Dutch.
 
-![Greeting message displayed in US English despite the workbench being set to use Dutch (Netherlands)](../../../../images/localization-english-greeting-dutch-workbench.png)
+![Greeting message displayed in US English despite the workbench being set to use Dutch (Netherlands)](../../../images/localization-english-greeting-dutch-workbench.png)
 
 Using the building blocks provided with the SharePoint Framework, you can extend your web part with support for storing web part configuration values in multiple languages. For each of the supported languages the property pane will display a separate text field in which the user can enter the translated value for that property.
 
-![Multiple text fields rendered in the web part property pane to allow translation of the web part values](../../../../images/localization-multilingual-properties.png)
+![Multiple text fields rendered in the web part property pane to allow translation of the web part values](../../../images/localization-multilingual-properties.png)
 
 > **Note:** The SharePoint site used to test the web part shown in this article is a multilingual site with the US English, Dutch, and German languages enabled. For more information about enabling additional languages in SharePoint sites see the [Choose the languages you want to make available for a site’s user interface](https://support.office.com/en-us/article/Choose-the-languages-you-want-to-make-available-for-a-site-s-user-interface-16d3a83c-05ab-4b50-8fbb-ff576a3351e8) support article.
 
@@ -790,7 +797,7 @@ When the user opens the web part property pane, the method will load the informa
 
 Once text fields for all enabled languages are constructed, the method refreshes the property pane by calling the **refreshPropertyPane** method. Finally, the method clears the web part loading indicator and re-renders the web part body.
 
-![Text fields for all enabled languages displayed in the web part property pane](../../../../images/localization-multilingual-properties.png)
+![Text fields for all enabled languages displayed in the web part property pane](../../../images/localization-multilingual-properties.png)
 
 ### Show the greeting for the preferred user language
 
@@ -912,4 +919,4 @@ Examining the latest web part manifest generated in a release build, you can see
 }
 ```
 
-When loading the web part on the page, the SharePoint Framework will automatically load the resource file for the corresponding locale by using the information from the context site. If no matching resource file is found, the SharePoint Framework will load the file specified in the **defaultPath** property. By keeping the resource files separate, the SharePoint Framework minimizes the amount of data loaded on the page to the locale that matches the one used in the site.
\ No newline at end of file
+When loading the web part on the page, the SharePoint Framework will automatically load the resource file for the corresponding locale by using the information from the context site. If no matching resource file is found, the SharePoint Framework will load the file specified in the **defaultPath** property. By keeping the resource files separate, the SharePoint Framework minimizes the amount of data loaded on the page to the locale that matches the one used in the site.
diff --git a/docs/spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework.md b/docs/spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework.md
index 70702131d0..efaef73d20 100644
--- a/docs/spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework.md
+++ b/docs/spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework.md
@@ -1,10 +1,17 @@
+---
+title: Migrate Angular v1.x applications to SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Migrate Angular v1.x applications to SharePoint Framework
 
 > Note. This article has not yet been verified with SPFx GA version, so you might have challenges on making this work as such with the latest release.
 
 Many organizations have been using Angular for building SharePoint solutions in the past. This article shows how to migrate an existing Angular v1.x application styled using [ngOfficeUIFabric](http://ngofficeuifabric.com) - Angular directives for Office UI Fabric, to a SharePoint Framework client-side web part. The sample application used for this tutorial manages to do items stored in a SharePoint list.
 
-![Angular application for managing to do items stored in a SharePoint list](../../../../images/ng-migration-original-angular-application.png)
+![Angular application for managing to do items stored in a SharePoint list](../../../images/ng-migration-original-angular-application.png)
 
 The source of the Angular application is available on GitHub at [https://github.com/SharePoint/sp-dev-fx-webparts/tree/dev/samples/angular-migration/angular-todo](https://github.com/SharePoint/sp-dev-fx-webparts/tree/dev/samples/angular-migration/angular-todo).
 
@@ -43,11 +50,11 @@ When prompted, define values as follows:
 - **Simple management of to do tasks** as your web part description
 - **No JavaScript web framework** as the starting point to build the web part
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/ng-migration-yeoman-generator.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/ng-migration-yeoman-generator.png)
 
 Once the scaffolding completes, open your project folder in your code editor. In this tutorial, you will use Visual Studio Code.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/ng-migration-project-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/ng-migration-project-visual-studio-code.png)
 
 ### Add Angular and ngOfficeUIFabric
 
@@ -61,7 +68,7 @@ In this tutorial you will load both Angular and ngOfficeUIFabric from CDN. To do
 "ng-office-ui-fabric": "https://cdnjs.cloudflare.com/ajax/libs/ngOfficeUiFabric/0.12.3/ngOfficeUiFabric.js"
 ```
 
-![Angular and ngOfficeUIFabric added to the config.json file](../../../../images/ng-migration-angular-ngofficeuifabric-config.png)
+![Angular and ngOfficeUIFabric added to the config.json file](../../../images/ng-migration-angular-ngofficeuifabric-config.png)
 
 ### Add Angular typings for TypeScript
 
@@ -85,17 +92,17 @@ In progress
 Completed
 ```
 
-![Todo SharePoint list](../../../../images/ng-migration-todo-list.png)
+![Todo SharePoint list](../../../images/ng-migration-todo-list.png)
 
 ### Copy Angular application files to the web part project
 
 In the web part project, in the **src/webparts/toDo** folder create a new folder called `app`.
 
-![App folder highlighted in Visual Studio Code Explorer pane](../../../../images/ng-migration-app-folder-visual-studio-code.png)
+![App folder highlighted in Visual Studio Code Explorer pane](../../../images/ng-migration-app-folder-visual-studio-code.png)
 
 From the source application copy the contents of the **app** folder, to the newly created **app** folder in the web part project.
 
-![App files highlighted in Visual Studio Code Explorer pane](../../../../images/ng-migration-app-files-visual-studio-code.png)
+![App files highlighted in Visual Studio Code Explorer pane](../../../images/ng-migration-app-files-visual-studio-code.png)
 
 ### Load the Angular application in the client-side web part
 
@@ -108,7 +115,7 @@ import * as angular from 'angular';
 import 'ng-office-ui-fabric';
 ```
 
-![Import statements to load Angular and ngOfficeUIFabric](../../../../images/ng-migration-angular-ngofficeuifabric-import.png)
+![Import statements to load Angular and ngOfficeUIFabric](../../../images/ng-migration-angular-ngofficeuifabric-import.png)
 
 Change the contents of the **render** method to:
 
@@ -161,7 +168,7 @@ export default class ToDoWebPart extends BaseClientSideWebPart<IToDoWebPartProps
 
 In the code editor open the **./src/webparts/toDo/app/app.config.js** file. Change the value of the **sharepointApi** constant to the server-relative URL of the SharePoint site where you created the Todo list, followed by `/_api/`.
 
-![Web URL highlighted in the app.config.js file in Visual Studio Code](../../../../images/ng-migration-app-config-web-url.png)
+![Web URL highlighted in the app.config.js file in Visual Studio Code](../../../images/ng-migration-app-config-web-url.png)
 
 ### Trust the development certificate
 
@@ -183,19 +190,19 @@ gulp serve --nobrowser
 
 In the **./temp** folder copy the **workbench.html** file and rename it to **workbench.aspx**. Inside the **workbench.aspx** file change the value of the **webAbsoluteUrl** property to the full URL of the SharePoint site in which you created the Todo list.
 
-![Web URL highlighted in the workbench.aspx file in Visual Studio Code](../../../../images/ng-migration-workbench-weburl.png)
+![Web URL highlighted in the workbench.aspx file in Visual Studio Code](../../../images/ng-migration-workbench-weburl.png)
 
 Upload the **workbench.aspx** file to the document library in your SharePoint site.
 
-![Web URL highlighted in the workbench.aspx file in Visual Studio Code](../../../../images/ng-migration-workbench-aspx-doclib.png)
+![Web URL highlighted in the workbench.aspx file in Visual Studio Code](../../../images/ng-migration-workbench-aspx-doclib.png)
 
 If you followed all steps correctly, you should see the web part in the browser showing the form to add to do items.
 
-![Migrated Angular application displayed in the SharePoint workbench uploaded to SharePoint](../../../../images/ng-migration-first-run.png)
+![Migrated Angular application displayed in the SharePoint workbench uploaded to SharePoint](../../../images/ng-migration-first-run.png)
 
 Add a few todo items to verify that the web part is working as expected.
 
-![Migrated Angular application incorrectly styled](../../../../images/ng-migration-old-office-ui-fabric.png)
+![Migrated Angular application incorrectly styled](../../../images/ng-migration-old-office-ui-fabric.png)
 
 ### Fix web part styling
 
@@ -274,7 +281,7 @@ export default class ToDoWebPart extends BaseClientSideWebPart<IToDoWebPartProps
 
 If you refresh the web part in the web browser, you will see that it is now correctly styled.
 
-![Migrated Angular application correctly marking completed items in the web part](../../../../images/ng-migration-correct-styling.png)
+![Migrated Angular application correctly marking completed items in the web part](../../../images/ng-migration-correct-styling.png)
 
 ## Upgrade the Angular application to TypeScript
 
@@ -663,7 +670,7 @@ gulp serve --nobrowser
 
 In the web browser refresh the SharePoint workbench which should display your web part just as previously.
 
-![Migrated Angular application correctly marking completed items in the web part](../../../../images/ng-migration-correct-styling.png)
+![Migrated Angular application correctly marking completed items in the web part](../../../images/ng-migration-correct-styling.png)
 
 Even though the way the web part works hasn't changed, your code is improved. In case of a future update you can more easily verify the correctness and integrity of your code already during development.
 
@@ -682,7 +689,7 @@ In the code editor open the **./src/webparts/toDo/ToDoWebPart.manifest.json** fi
 }
 ```
 
-![Web part manifest extended with new properties for the Angular application](../../../../images/ng-migration-angular-web-part-properties.png)
+![Web part manifest extended with new properties for the Angular application](../../../images/ng-migration-angular-web-part-properties.png)
 
 Change the contents of the **./src/webparts/toDo/IToDoWebPartProps.ts** file to:
 
@@ -705,7 +712,7 @@ import {
 } from '@microsoft/sp-client-preview';
 ```
 
-![Import statement updated to load the PropertyPaneToggle property pane control](../../../../images/ng-migration-import-propertypanetoggle.png)
+![Import statement updated to load the PropertyPaneToggle property pane control](../../../images/ng-migration-import-propertypanetoggle.png)
 
 Next, in the same file, change the **propertyPaneSettings** method to:
 
@@ -998,7 +1005,7 @@ export default class ToDoWebPart extends BaseClientSideWebPart<IToDoWebPartProps
 }
 ```
 
-![Injector property highlighted in the ToDoWebPart class](../../../../images/ng-migration-injector-property.png)
+![Injector property highlighted in the ToDoWebPart class](../../../images/ng-migration-injector-property.png)
 
 In the same file, update the **render** method to:
 
@@ -1227,4 +1234,4 @@ gulp serve --nobrowser
 
 In your web browser navigate to the SharePoint workbench and add the web part to canvas. If you toggle the **Hide finished tasks** option you should see completed tasks being displayed or hidden accordingly.
 
-![Angular application hiding finished tasks as configured in web part properties](../../../../images/ng-migration-finished-tasks-hidden.png)
\ No newline at end of file
+![Angular application hiding finished tasks as configured in web part properties](../../../images/ng-migration-finished-tasks-hidden.png)
diff --git a/docs/spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md b/docs/spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md
index 93428e2694..46c296178a 100644
--- a/docs/spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md
+++ b/docs/spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md
@@ -1,3 +1,10 @@
+---
+title: Migrate jQuery and DataTables solution built using Script Editor Web Part to SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Migrate jQuery and DataTables solution built using Script Editor Web Part to SharePoint Framework
 
 One of the frequently used jQuery plugins is [DataTables](https://datatables.net/). With DataTables you can easily build powerful data overviews of data coming both from SharePoint and external APIs. This article illustrates how you would migrate a SharePoint customization using DataTables built with the Script Editor Web Part to the SharePoint Framework.
@@ -6,7 +13,7 @@ One of the frequently used jQuery plugins is [DataTables](https://datatables.net
 
 To illustrate the process of migrating a SharePoint customization using DataTables to the SharePoint Framework you will use the following solution that shows an overview of IT support requests retrieved from a SharePoint list.
 
-![Overview of IT support requests displayed on a SharePoint page](../../../../images/datatables-sewp.png)
+![Overview of IT support requests displayed on a SharePoint page](../../../images/datatables-sewp.png)
 
 The solution is built using the standard SharePoint Script Editor Web Part. Following is the code used by the customization.
 
@@ -113,11 +120,11 @@ First, the customization loads the libraries it uses: jQuery, DataTables and Mom
 
 Thanks to using DataTables, end-users get a powerful solution where they can easily filter, sort and page through the results without any additional development effort.
 
-![The list of IT support requests displayed using DataTables filtered by requests assigned to Lidia sorted descending by the due date](../../../../images/datatables-sewp-filter.png)
+![The list of IT support requests displayed using DataTables filtered by requests assigned to Lidia sorted descending by the due date](../../../images/datatables-sewp-filter.png)
 
 ## Migrate the IT requests overview solution from the Script Editor Web Part to the SharePoint Framework
 
-> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment) for building SharePoint Framework solutions.
+> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment.md) for building SharePoint Framework solutions.
 
 Transforming this customization to the SharePoint Framework offers a number of benefits such as more user-friendly configuration and centralized management of the solution. Following is a step-by-step description of how you would migrate the solution to the SharePoint Framework. First, you will migrate the solution to the SharePoint Framework with as few changes to the original code as possible. Later, you will transform the solution's code to TypeScript to benefit of its development-time type safety features.
 
@@ -150,11 +157,11 @@ When prompted, define values as follows:
 - **IT requests** as your web part name
 - **Shows overview of IT support requests** as your web part description
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/datatables-yeoman.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/datatables-yeoman.png)
 
 Once the scaffolding completes, open your project folder in your code editor. In this tutorial, you will use Visual Studio Code.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/datatables-vscode.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/datatables-vscode.png)
 
 ### Load JavaScript libraries
 
@@ -189,7 +196,7 @@ export default class ItRequestsWebPart extends BaseClientSideWebPart<IItRequests
   public render(): void {
     this.domElement.innerHTML = `
       <link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/1.10.15/css/jquery.dataTables.min.css" />
-      <table id="requests" class="display ${styles.itRequests}" cellspacing="0" width="100%">
+      <table id="requests" class="display ${styles.helloWorld}" cellspacing="0" width="100%">
         <thead>
             <tr>
                 <th>ID</th>
@@ -340,7 +347,7 @@ gulp serve --nobrowser
 
 Because the web part loads its data from SharePoint, you have to test the web part using the hosted SharePoint Framework workbench. Navigate to **https://yourtenant.sharepoint.com/_layouts/workbench.aspx** and add the web part to the canvas. You should now see the IT requests displayed using the DataTables jQuery plugin.
 
-![IT requests displayed in a SharePoint Framework client-side web part](../../../../images/datatables-spfx.png)
+![IT requests displayed in a SharePoint Framework client-side web part](../../../images/datatables-spfx.png)
 
 ## Add support for configuring the web part through web part properties
 
@@ -350,7 +357,7 @@ In the previous steps you migrated the IT requests solutions from Script Editor
 
 Start with defining a web part property to store the name of the list from which IT requests should be loaded. In the code editor, open the **./src/webparts/itRequests/ItRequestsWebPart.manifest.json** file and rename the default **description** property to **listName** and clear its value.
 
-![The listName property in the web part manifest highlighted in Visual Studio Code](../../../../images/datatables-spfx-listname-property.png)
+![The listName property in the web part manifest highlighted in Visual Studio Code](../../../images/datatables-spfx-listname-property.png)
 
 Next, update the web part properties interface to reflect the changes in the manifest. In the code editor, open the **./src/webparts/itRequests/IItRequestsWebPartProps.ts** file and change its contents to:
 
@@ -492,7 +499,7 @@ gulp serve --nobrowser
 
 Navigate to the hosted workbench and add the web part to the canvas. Open the web part property pane, specify the name of the list with IT requests and click the **Apply** button to confirm the changes. You should now see IT requests displayed in the web part.
 
-![IT requests loaded from the configured list and displayed in a SharePoint Framework client-side web part](../../../../images/datatables-spfx-list-configured.png)
+![IT requests loaded from the configured list and displayed in a SharePoint Framework client-side web part](../../../images/datatables-spfx-list-configured.png)
 
 ## Transform the plain JavaScript code to TypeScript
 
@@ -505,7 +512,7 @@ To function properly, TypeScript requires type definitions for the different lib
 Start by installing type definitions for jQuery and DataTables by executing in the command line:
 
 ```sh
-npm install --save-dev @types/jquery@1 @types/datatables.net
+npm install --save-dev @types/jquery @types/jquery.datatables
 ```
 
 Type definitions for Moment.js are distributed together with the Moment.js package. Even though, you're loading Moment.js from a URL, in order to use its typings, you still need to install the Moment.js package in the project.
@@ -530,7 +537,7 @@ Having defined **$** as jQuery you can now remove the local definition of **$**
 var $: any = (window as any).$;
 ```
 
-Because DataTables is a jQuery plugin that attaches itself to jQuery you cannot load its type definition directly. Instead, you have to add it to the list of types loaded globally. In the code editor, open the **./tsconfig.json** file and to the **types** array add **datatables.net**:
+Because DataTables is a jQuery plugin that attaches itself to jQuery you cannot load its type definition directly. Instead, you have to add it to the list of types loaded globally. In the code editor, open the **./tsconfig.json** file and to the **types** array add **jquery.datatables**:
 
 ```json
 {
@@ -544,7 +551,7 @@ Because DataTables is a jQuery plugin that attaches itself to jQuery you cannot
     "types": [
       "es6-promise",
       "es6-collections",
-      "datatables.net",
+      "jquery.datatables",
       "webpack-env"
     ]
   }
@@ -607,7 +614,7 @@ export default class ItRequestsWebPart extends BaseClientSideWebPart<IItRequests
       },
       columnDefs: [{
         targets: 4,
-        render: ($.fn as any).dataTable.render.moment('YYYY/MM/DD')
+        render: $.fn.dataTable.render.moment('YYYY/MM/DD')
       }]
     });
   }
@@ -629,7 +636,7 @@ import * as $ from 'jquery';
 import * as moment from 'moment';
 
 /* tslint:disable:no-function-expression */
-($.fn as any).dataTable.render.moment = function (from: string, to: string, locale: string): (d: any, type: string, row: any) => string {
+$.fn.dataTable.render.moment = function (from: string, to: string, locale: string): (d: any, type: string, row: any) => string {
 /* tslint:enable */
     // Argument shifting
     if (arguments.length === 1) {
@@ -659,4 +666,4 @@ To confirm that everything is working as expected, in the command line execute:
 gulp serve --nobrowser
 ```
 
-Navigate to the hosted workbench and add the web part to the canvas. Although visually nothing has changed, the new code base uses TypeScript and its type definitions to help you maintain the solution.
\ No newline at end of file
+Navigate to the hosted workbench and add the web part to the canvas. Although visually nothing has changed, the new code base uses TypeScript and its type definitions to help you maintain the solution.
diff --git a/docs/spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx.md b/docs/spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx.md
index 743633f26d..8412a103cd 100644
--- a/docs/spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx.md
+++ b/docs/spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx.md
@@ -1,3 +1,10 @@
+---
+title: Migrate jQuery and FullCalendar solution built using Script Editor Web Part to SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Migrate jQuery and FullCalendar solution built using Script Editor Web Part to SharePoint Framework
 
 When building SharePoint solutions, SharePoint developers often use the [FullCalendar](https://fullcalendar.io) jQuery plugin to display data in calendar view. FullCalendar is a great alternative to the standard SharePoint calendar view, as it allows you to render as calendar data from multiple calendar lists, data from non-calendar lists or even data from outside of SharePoint. This article illustrates how you would migrate a SharePoint customization using FullCalendar built with the Script Editor Web Part to the SharePoint Framework.
@@ -6,7 +13,7 @@ When building SharePoint solutions, SharePoint developers often use the [FullCal
 
 To illustrate the process of migrating a SharePoint customization using FullCalendar to the SharePoint Framework you will use the following solution that shows a calendar view of tasks retrieved from a SharePoint list.
 
-![Calendar view of tasks displayed on a SharePoint page](../../../../images/fullcalendar-sewp.png)
+![Calendar view of tasks displayed on a SharePoint page](../../../images/fullcalendar-sewp.png)
 
 The solution is built using the standard SharePoint Script Editor Web Part. Following is the code used by the customization.
 
@@ -149,11 +156,11 @@ First, the customization loads the libraries it uses: jQuery, Moment.js and Full
 
 Using the FullCalendar jQuery plugin, with little effort users get rich solutions capable of things such as using different colors to mark different events or using drag and drop to reorganize events.
 
-![Dragging events in FullCalendar to reschedule underlying tasks](../../../../images/fullcalendar-sewp-draganddrop.png)
+![Dragging events in FullCalendar to reschedule underlying tasks](../../../images/fullcalendar-sewp-draganddrop.png)
 
 ## Migrate the Tasks calendar solution from the Script Editor Web Part to the SharePoint Framework
 
-> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment) for building SharePoint Framework solutions.
+> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment.md) for building SharePoint Framework solutions.
 
 Transforming a Script Editor Web Part-based customization to the SharePoint Framework offers a number of benefits such as more user-friendly configuration and centralized management of the solution. Following is a step-by-step description of how you would migrate the solution to the SharePoint Framework. First, you will migrate the solution to the SharePoint Framework with as few changes to the original code as possible. Later, you will transform the solution's code to TypeScript to benefit of its development-time type safety features and replace some of the code with the SharePoint Framework API to fully benefit of its capabilities and simplify the solution even further.
 
@@ -185,13 +192,13 @@ When prompted, define values as follows:
 - **WebPart** as the client-side component to create
 - **Tasks calendar** as your web part name
 - **Shows tasks in the calendar view** as your web part description
-- **No JavaScript web framework** as the starting point to build the web part
+- **No javaScript web framework** as the starting point to build the web part
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/fullcalendar-yeoman.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/fullcalendar-yeoman.png)
 
 Once the scaffolding completes, open your project folder in your code editor. In this tutorial, you will use Visual Studio Code.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/fullcalendar-vscode.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/fullcalendar-vscode.png)
 
 ### Load JavaScript libraries
 
@@ -365,7 +372,7 @@ function updateTask(id, startDate, dueDate) {
 }
 ```
 
-This code is almost identical with the original code of the Script Editor Web Part customization. The only difference is that where the original code retrieved the URL of the current web from the global **\_spPageContextInfo** variable set by SharePoint (lines 8, 45, 96 and 104), the code in the SharePoint Framework uses a custom variable that you will have to set in the web part. SharePoint Framework client-side web parts can be used both on classic and modern pages. While the **\_spPageContextInfo** variable is present on classic pages, it's not available on modern pages which is why you can't rely on it and need a custom property that you can control yourself instead.
+This code is almost identical with the original code of the Script Editor Web Part customization. The only difference is that where the original code retrieved the URL of the current web from the global **\_spPageContextInfo** variable set by SharePoint (lines 8, 45, 96 and 104), the code in the SharePoint Framework uses a custom variable that you will have to set in the web part. SharePoint Framework client-side web parts can be used both on classic and modern pages. While the **_spPageContextInfo** variable is present on classic pages, it's not available on modern pages which is why you can't rely on it and need a custom property that you can control yourself instead.
 
 In order to reference this file in the web part, in the code editor, open the **./src/webparts/tasksCalendar/TasksCalendarWebPart.ts** file and change the **render** method to:
 
@@ -393,7 +400,7 @@ gulp serve --nobrowser
 
 Because the web part loads its data from SharePoint, you have to test the web part using the hosted SharePoint Framework workbench. Navigate to **https://yourtenant.sharepoint.com/_layouts/workbench.aspx** and add the web part to the canvas. You should now see the tasks displayed in a calendar view using the FullCalendar jQuery plugin.
 
-![Tasks displayed in a calendar view in a SharePoint Framework client-side web part](../../../../images/fullcalendar-spfx.png)
+![Tasks displayed in a calendar view in a SharePoint Framework client-side web part](../../../images/fullcalendar-spfx.png)
 
 ## Add support for configuring the web part through web part properties
 
@@ -403,7 +410,7 @@ In the previous steps you migrated the Tasks calendar solutions from Script Edit
 
 Start with defining a web part property to store the name of the list from which tasks should be loaded. In the code editor, open the **./src/webparts/tasksCalendar/TasksCalendarWebPart.manifest.json** file and rename the default **description** property to **listName** and clear its value.
 
-![The listName property in the web part manifest highlighted in Visual Studio Code](../../../../images/fullcalendar-spfx-listname-property.png)
+![The listName property in the web part manifest highlighted in Visual Studio Code](../../../images/fullcalendar-spfx-listname-property.png)
 
 Next, update the web part properties interface to reflect the changes in the manifest. In the code editor, open the **./src/webparts/tasksCalendar/ITasksCalendarWebPartProps.ts** file and change its contents to:
 
@@ -652,7 +659,7 @@ gulp serve --nobrowser
 
 Navigate to the hosted workbench and add the web part to the canvas. Open the web part property pane, specify the name of the list with tasks and click the **Apply** button to confirm the changes. You should now see tasks displayed in a calendar view in the web part.
 
-![Tasks loaded from the configured list and displayed in a SharePoint Framework client-side web part](../../../../images/fullcalendar-spfx-list-configured.png)
+![Tasks loaded from the configured list and displayed in a SharePoint Framework client-side web part](../../../images/fullcalendar-spfx-list-configured.png)
 
 ## Transform the plain JavaScript code to TypeScript
 
@@ -1054,4 +1061,4 @@ To confirm that everything is working as expected, in the command line execute:
 gulp serve --nobrowser
 ```
 
-Navigate to the hosted workbench and add the web part to the canvas. Although there are still no visual changes, the new code uses the SharePoint Framework SPHttpClient which simplifies your code and maintaining your solution.
\ No newline at end of file
+Navigate to the hosted workbench and add the web part to the canvas. Although there are still no visual changes, the new code uses the SharePoint Framework SPHttpClient which simplifies your code and maintaining your solution.
diff --git a/docs/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations.md b/docs/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations.md
index bb3ae8d1de..38bbeab74c 100644
--- a/docs/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations.md
+++ b/docs/spfx/web-parts/guidance/migrate-script-editor-web-part-customizations.md
@@ -1,3 +1,10 @@
+---
+title: Migrate existing Script Editor Web Part customizations to the SharePoint Framework
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Migrate existing Script Editor Web Part customizations to the SharePoint Framework
 
 SharePoint Framework is a new model for building SharePoint customizations. If you have been building client-side SharePoint solutions using the Script Editor Web Part in the past, you might be wondering what the possible advantages are of migrating them to the new SharePoint Framework. This article highlights the different benefits of migrating existing client-side customizations to the new SharePoint Framework and points out a number of considerations that you should take into account when planning the migration.
diff --git a/docs/spfx/web-parts/guidance/office-ui-fabric-integration.md b/docs/spfx/web-parts/guidance/office-ui-fabric-integration.md
index eef5a41d22..eb2f83f60a 100644
--- a/docs/spfx/web-parts/guidance/office-ui-fabric-integration.md
+++ b/docs/spfx/web-parts/guidance/office-ui-fabric-integration.md
@@ -1,3 +1,10 @@
+---
+title: Using Office UI Fabric Core and Fabric React in SPFx client-side web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Using Office UI Fabric Core and Fabric React in SPFx client-side web parts
 
 #### **Important:** You must upgrade existing projects to use *@microsoft/sp-build-web@1.0.1* or later in order to use the Office UI Fabric React components. See the instructions at the end of this article for additional information.
diff --git a/docs/spfx/web-parts/guidance/reference-third-party-css-styles.md b/docs/spfx/web-parts/guidance/reference-third-party-css-styles.md
index 17627bcdd0..ea09a4230b 100644
--- a/docs/spfx/web-parts/guidance/reference-third-party-css-styles.md
+++ b/docs/spfx/web-parts/guidance/reference-third-party-css-styles.md
@@ -1,10 +1,17 @@
+---
+title: Reference third-party CSS styles in SharePoint Framework web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Reference third-party CSS styles in SharePoint Framework web parts
 
 There are many third-party libraries that you can leverage to build rich SharePoint Framework client-side web parts. In addition to scripts, these libraries often contain additional assets such as stylesheets. This article shows two different approaches to include third-party CSS styles in web parts and how each approach affects the resulting web part bundle. The example web part discussed in this article uses jQuery and jQuery UI to display an accordion.
 
-![jQuery UI accordion rendered by a SharePoint Framework client-side web part](../../../../images/thirdpartycss-accordion-styled.png)
+![jQuery UI accordion rendered by a SharePoint Framework client-side web part](../../../images/thirdpartycss-accordion-styled.png)
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment.md).
 
 ## Prepare the project
 
@@ -36,11 +43,11 @@ When prompted, enter the following values:
 - **jQuery accordion** as your web part name
 - **Shows jQuery accordion** as your web part description
 
-![The SharePoint Framework Yeoman generator with the default choices](../../../../images/thirdpartycss-yeoman.png)
+![The SharePoint Framework Yeoman generator with the default choices](../../../images/thirdpartycss-yeoman.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![The SharePoint Framework project open in Visual Studio Code](../../../../images/thirdpartycss-visual-studio-code.png)
+![The SharePoint Framework project open in Visual Studio Code](../../../images/thirdpartycss-visual-studio-code.png)
 
 ### Add test content
 
@@ -142,7 +149,7 @@ gulp serve
 
 After adding the web part to the canvas you should see the accordion working.
 
-![jQuery UI accordion without styles rendered by a SharePoint Framework client-side web part](../../../../images/thirdpartycss-accordion-not-styled.png)
+![jQuery UI accordion without styles rendered by a SharePoint Framework client-side web part](../../../images/thirdpartycss-accordion-not-styled.png)
 
 At this point you have referenced only the jQuery UI scripts which explains why the accordion is not styled. Next you will add the missing CSS stylesheets to brand the accordion.
 
@@ -168,7 +175,7 @@ gulp serve
 
 The accordion should be displayed correctly and branded using the standard jQuery UI theme.
 
-![jQuery UI accordion branded using the default jQuery UI theme rendered by a SharePoint Framework client-side web part](../../../../images/thirdpartycss-accordion-styled.png)
+![jQuery UI accordion branded using the default jQuery UI theme rendered by a SharePoint Framework client-side web part](../../../images/thirdpartycss-accordion-styled.png)
 
 ### Analyze the contents of the generated web part bundle
 
@@ -176,7 +183,7 @@ The easiest way to use third-party libraries and their resources is by including
 
 To see the impact of the libraries on the size of the generated web part bundle, after bundling the project open the **./temp/stats/js-thirdpartycss.stats.html** file in the web browser. Move your mouse over the chart and you will see, for example, that the jQuery UI CSS files referenced by the web part make up over 6% of the total web part bundle size.
 
-![jQuery UI CSS highlighted in the chart illustrating the size of the different pieces of the generated web part bundle](../../../../images/thirdpartycss-jquery-ui-css-size.png)
+![jQuery UI CSS highlighted in the chart illustrating the size of the different pieces of the generated web part bundle](../../../images/thirdpartycss-jquery-ui-css-size.png)
 
 As mentioned in the disclaimer below the chart, the sizes are indicative and reflect the size of the debug version of the bundle. The release version of the bundle would be significantly smaller. Still it's good to realize which different pieces compose the web part bundle and what's their relative size compared to other elements in the bundle.
 
@@ -238,11 +245,11 @@ gulp serve
 
 After adding the web part to the canvas you should see the accordion working.
 
-![jQuery UI accordion without styles rendered by a SharePoint Framework client-side web part](../../../../images/thirdpartycss-accordion-not-styled.png)
+![jQuery UI accordion without styles rendered by a SharePoint Framework client-side web part](../../../images/thirdpartycss-accordion-not-styled.png)
 
 In your web browser, open the developer tools, switch to the tab showing the network requests, and reload the page. You should see how both jQuery and jQuery UI are loaded from the CDN.
 
-![jQuery and jQuery UI request highlighted in Microsoft Edge developer tools](../../../../images/thirdpartycss-libraries-cdn.png)
+![jQuery and jQuery UI request highlighted in Microsoft Edge developer tools](../../../images/thirdpartycss-libraries-cdn.png)
 
 At this point you have referenced only the jQuery UI scripts which explains why the accordion is not styled. Next you will add the missing CSS stylesheets to brand the accordion.
 
@@ -281,8 +288,8 @@ gulp serve
 
 The accordion should be displayed correctly and branded using the standard jQuery UI Theme.
 
-![jQuery UI accordion branded using the default jQuery UI theme rendered by a SharePoint Framework client-side web part](../../../../images/thirdpartycss-accordion-styled.png)
+![jQuery UI accordion branded using the default jQuery UI theme rendered by a SharePoint Framework client-side web part](../../../images/thirdpartycss-accordion-styled.png)
 
 ### Analyze the contents of the generated web part bundle loading resources from URL
 
-After building the project in the web browser open the **./temp/stats/js-thirdpartycss.stats.html** file. Notice how the overall bundle is significantly smaller (7KB compared to over 300KB when including jQuery and jQuery UI in the bundle) and how jQuery and jQuery UI are not listed in the chart since they are loaded at runtime.
\ No newline at end of file
+After building the project in the web browser open the **./temp/stats/js-thirdpartycss.stats.html** file. Notice how the overall bundle is significantly smaller (7KB compared to over 300KB when including jQuery and jQuery UI in the bundle) and how jQuery and jQuery UI are not listed in the chart since they are loaded at runtime.
diff --git a/docs/spfx/web-parts/guidance/share-data-between-web-parts.md b/docs/spfx/web-parts/guidance/share-data-between-web-parts.md
index 4ab72dd589..4f4bb950f3 100644
--- a/docs/spfx/web-parts/guidance/share-data-between-web-parts.md
+++ b/docs/spfx/web-parts/guidance/share-data-between-web-parts.md
@@ -1,12 +1,21 @@
+---
+title: Share Data Between Client-Side Web Parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Share Data Between Client-Side Web Parts
 
+> **Note.** This article has not yet been verified with the SPFx GA version, so you might have challenges making this work as described using the latest release.
+
 When building client-side web parts, loading data once and reusing it across different web parts will help you improve the performance of your pages and decrease the load on your network. This article describes a number of approaches that you can use to share data across multiple web parts.
 
 ## Why Share Data Between Web Parts
 
 Often, when building web parts, a number of them will be used together on one page. If you consider each web part as a standalone part of the page, then you may end up in a situation where you are loading a similar or even the same set of data multiple times on the same page. This will unnecessarily slow down the loading of the page and increase traffic on your network.
 
-![Two web parts on one page loading similar sets of data separately](../../../../images/guidance-sharingdata-loading-data-separately.png)
+![Two web parts on one page loading similar sets of data separately](../../../images/guidance-sharingdata-loading-data-separately.png)
 
 A sample service responsible for loading the data could look like the following:
 
@@ -124,11 +133,11 @@ Notice how loading the data has been moved from the specific methods to the `ens
 
 If you look at the log in the developer tools, you will notice that the remote API is now called only once.
 
-![One log statement referring to loading data for both web parts](../../../../images/guidance-sharingdata-reusing-data-global-variable-loading-message.png)
+![One log statement referring to loading data for both web parts](../../../images/guidance-sharingdata-reusing-data-global-variable-loading-message.png)
 
 Looking at the informational messages, you can confirm that when the second web part tries to load the data it detects that the data is already being loaded. Once the data is loaded, it reuses the existing data rather than loading it itself.
 
-![Information message from the log showing how the second web part waits on data to be loaded](../../../../images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png)
+![Information message from the log showing how the second web part waits on data to be loaded](../../../images/guidance-sharingdata-reusing-data-global-variable-waiting-message.png)
 
 Using a globally-scoped variable is the easiest way to exchange data between different web parts on the page. One downside of using this approach, however, is that the data is exposed not only to web parts but also to all other elements on the page. This introduces the risk of other elements on the page using the same variable as you to store their data potentially overwriting your data.
 
@@ -201,15 +210,15 @@ In the example above the [js-cookie](https://www.npmjs.com/package/js-cookie) pa
 
 When you load the page in Microsoft Edge the first time, you will see that the data is retrieved once and reused by both web parts.
 
-![Log messages showing data being loaded once and the other web part waiting for the data to be loaded on the first request in Microsoft Edge](../../../../images/guidance-sharingdata-cookie-edge-first-request.png)
+![Log messages showing data being loaded once and the other web part waiting for the data to be loaded on the first request in Microsoft Edge](../../../images/guidance-sharingdata-cookie-edge-first-request.png)
 
 On subsequent requests, a web part can directly reuse the previously loaded data without calling the remote API.
 
-![Log message showing data being loaded directly without calling the remote API on subsequent requests in Microsoft Edge](../../../../images/guidance-sharingdata-cookie-edge-subsequent-request.png)
+![Log message showing data being loaded directly without calling the remote API on subsequent requests in Microsoft Edge](../../../images/guidance-sharingdata-cookie-edge-subsequent-request.png)
 
 When loading the page in Google Chrome, you would see that the data is loaded twice from the remote API and is not being cached at all.
 
-![Log message showing data being loaded twice from the remote API despite using cookies](../../../../images/guidance-sharingdata-cookie-chrome.png)
+![Log message showing data being loaded twice from the remote API despite using cookies](../../../images/guidance-sharingdata-cookie-chrome.png)
 
 Different web browsers have different limits regarding how much data can be stored in a cookie. In this example, the retrieved data exceeds the maximum length of what can be stored in a cookie in Google Chrome. As a result, no cookie is being set and the data is loaded twice.
 
@@ -325,14 +334,12 @@ SharePoint Framework services can be built using the same project build system a
 
 ```json
 {
-  "$schema": "https://dev.office.com/json-schemas/spfx/client-side-library-manifest.schema.json",
+  "$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/clientSideComponentManifestSchema.json",
 
   "id": "69b1aacd-68f2-4147-8433-8efb08eae331",
   "alias": "DocumentsService",
   "componentType": "Library",
-
-  // The "*" signifies that the version should be taken from the package.json
-  "version": "*",
+  "version": "0.0.1",
   "manifestVersion": 2
 }
 ```
diff --git a/docs/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries.md b/docs/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries.md
index 890c7e3183..8eebc99ce3 100644
--- a/docs/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries.md
+++ b/docs/spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries.md
@@ -1,8 +1,15 @@
+---
+title: Simplify adding web parts with preconfigured entries
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Simplify adding web parts with preconfigured entries
 
 More complex SharePoint Framework client-side web parts will likely have many properties that the user must configure. You can help users by adding preconfigured property entries for specific scenarios. A preconfigured entry will initialize the web part with preset values. In this article you will learn how you to use preconfigured entries in a SharePoint Framework client-side web part to provide users with preconfigured versions of your web part.
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment.md).
 
 ## What are web part preconfigured entries
 
@@ -47,17 +54,17 @@ title                   |ILocalizedString|yes     |The web part title that is di
 description             |ILocalizedString|yes     |The web part description that is displayed in the toolbox tooltips.|`"description": { "default": "Shows weather in the given location", "nl-nl": "Toont weerbericht voor de opgegeven locatie" } `
 officeFabricIconFontName|string          |no      |The icon for the web part that is displayed in the toolbox. Its value must be one of the [Office UI Fabric icon names](https://dev.office.com/fabric#/styles/icons). If this property has a value, the **iconImageUrl** property will be ignored.|`"officeFabricIconFontName": "Sunny"`
 iconImageUrl            |string          |no      |The icon for the web part that is displayed in the toolbox and is represented by an image URL. The image at the URL must be exactly 40 x 28 px. If the **officeFabricIconName** property does not have a value, this property must have a value.|`"iconImageUrl": "https://cdn.contoso.com/weather.png"`
-groupId                 |string          |yes     |The group ID determines which toolbox group will contain the web part. The client-side framework has reserved group IDs for predefined groups. The developer can pick one of those groups.|`"groupId": "cf066440-0614-43d6-98ae-0b31cf14c7c3"`
-group                   |ILocalizedString|no      |This field is used to determine which toolbox group will contain the web part in the authoring experience. On classic pages, the web part gallery is equivalent to the toolbox. When you choose a GUID as a group ID (as in the table below), use the corresponding classic page category name from the predefined group.|`"group": { "default": "Media and Content" }`
+groupId                 |string          |yes     |The group id determines which toolbox group will contain the web part. The SharePoint Framework reserves group ids for default groups. The developer can pick one of those groups. If a group id is specified, then the **group** property will be ignored. Alternatively, the developer can pick a completely unique id and a group name. The toolbox will then show the web part in its own group.|`"groupId": "6737645a-4443-4210-a70e-e5e2a219133a"`
+group                   |ILocalizedString|no      |The name of the group in the toolbox in which the web part will be displayed. If no value is provided, then the web part will be displayed in the **Custom** group.|`"group": { "default": "Content", "nl-nl": "Inhoud" }`
 dataVersion             |string          |no      |Use this field to specify the data version of the pre-configured data provided to the web part. Note that data version is different from the version field in the manifest. The manifest version is used to control the versioning of the web part code, while data version is used to control the versioning of the serialized data of the web part. Refer to dataVersion field of your web part for more information. Supported values format: MAJOR.MINOR version|`"dataVersion": "1.0"`
 properties              |TProperties     |yes     |A Key-value pair object with default values for web part properties.|`"properties": { "location": "Redmond", "numberOfDays": 3, "showIcon": true }`
 
 Out of the box Categories are following, which can be used for the `groupId` property.
 
-Category Name |Guid |Corresponding classic page category name |Description        
+Category Name |Guid |Map to web part picker |Description        
 --- |--- |--- |---
 Text, media, and content | `cf066440-0614-43d6-98ae-0b31cf14c7c3`| Media and Content  |This category includes web parts that display text, multi-media, documents, information from the web, and other rich content.   
-Discovery | `1edbd9a8-0bfb-4aa2-9afd-14b8c45dd489`| Discovery  |This category includes web parts that organize, group, and filter content to help users discover information. 
+Discover | `1edbd9a8-0bfb-4aa2-9afd-14b8c45dd489`| Discovery  |This category includes web parts that organize, group, and filter content to help users discover information. 
 Communication and collaboration | `75e22ed5-fa14-4829-850a-c890608aca2d`| Social Collaboration |This category includes web parts that facilitate information sharing, team work, and social interactions.
 Planning and process | `1bc7927e-4a5e-4520-b540-71305c79c20a`| Business Data | This category includes web parts that empower team productivity with the use of planning and process tools. 
 Business and intelligence | `4aca9e90-eff5-4fa1-bac7-728f5f157b66`| Business Data | This category includes web parts for tracking and analyzing data, and for integrating business flow with pages. 
@@ -93,7 +100,7 @@ A **ILocalizedString** value that is not valid because the **default** key is mi
 
 To see how you can use preconfigured entries when building web parts, you will build a sample gallery web part. Using several properties, users can configure this web part to show items from a selected list in a specific way. For brevity, you will omit the actual implementation of the web part logic and will focus on using the **preconfiguredEntries** property to provide preconfigured versions of the gallery web part.
 
-![Web part property pane showing the different properties users need to configure for the web part to work](../../../../images/preconfiguredentries-needs-configuration.png)
+![Web part property pane showing the different properties users need to configure for the web part to work](../../../images/preconfiguredentries-needs-configuration.png)
 
 ### Create a new project
 
@@ -123,11 +130,11 @@ When prompted, enter the following values:
 - **Shows items from the selected list** as your web part description
 - **React** as the starting point to build the web part
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/preconfiguredentries-yeoman.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/preconfiguredentries-yeoman.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/preconfiguredentries-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/preconfiguredentries-visual-studio-code.png)
 
 ### Add web part properties
 
@@ -388,7 +395,7 @@ gulp serve
 
 In the web browser add the web part to the canvas and open its property pane. You should see all properties available for users to configure.
 
-![Web part property pane showing the different properties users need to configure for the web part to work](../../../../images/preconfiguredentries-needs-configuration.png)
+![Web part property pane showing the different properties users need to configure for the web part to work](../../../images/preconfiguredentries-needs-configuration.png)
 
 Because you didn't specify any default values for the web part, every time users add the web part to the page they have to configure it first. You can simplify this experience by providing default values for the most common scenarios.
 
@@ -427,11 +434,11 @@ gulp serve
 
 When you open the web part toolbox to add the web part to the canvas, you will see that its name and icon changed to reflect the preconfigured settings.
 
-![Web part toolbox showing the preconfigured version of the web part](../../../../images/preconfiguredentries-recent-images-toolbox.png)
+![Web part toolbox showing the preconfigured version of the web part](../../../images/preconfiguredentries-recent-images-toolbox.png)
 
 After adding the web part to the page, it works immediately using the preconfigured settings.
 
-![Preconfigured web part working immediately after being added to the page](../../../../images/preconfiguredentries-recent-images-canvas.png)
+![Preconfigured web part working immediately after being added to the page](../../../images/preconfiguredentries-recent-images-canvas.png)
 
 ### Specify multiple preconfigured web part entries
 
@@ -481,11 +488,11 @@ gulp serve
 
 When you open the web part toolbox to add the web part to the canvas, you will see that there are two web parts for you to choose from.
 
-![Web part toolbox showing the preconfigured version of the web part](../../../../images/preconfiguredentries-multiple-web-parts-toolbox.png)
+![Web part toolbox showing the preconfigured version of the web part](../../../images/preconfiguredentries-multiple-web-parts-toolbox.png)
 
 After adding the **Recent documents** web part to the page, it works immediately using its specific preconfigured settings.
 
-![Preconfigured recent documents web part working immediately after being added to the page](../../../../images/preconfiguredentries-recent-documents-canvas.png)
+![Preconfigured recent documents web part working immediately after being added to the page](../../../images/preconfiguredentries-recent-documents-canvas.png)
 
 ### Specify an unconfigured instance of the web part
 
@@ -550,4 +557,4 @@ gulp serve
 
 When you open the web part toolbox to add the web part to the canvas, you will see that there are now three web parts that users can choose from.
 
-![Web part toolbox showing the preconfigured version of the web part](../../../../images/preconfiguredentries-three-configurations-toolbox.png)
+![Web part toolbox showing the preconfigured version of the web part](../../../images/preconfiguredentries-three-configurations-toolbox.png)
diff --git a/docs/spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable.md b/docs/spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable.md
index 3db9451b70..50bf41929b 100644
--- a/docs/spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable.md
+++ b/docs/spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable.md
@@ -1,10 +1,17 @@
+---
+title: Share Data Between Web Parts Using a Global Variable (Tutorial)
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Share Data Between Web Parts Using a Global Variable (Tutorial)
 
 > Note: This article has not yet been verified with the SPFx GA version, so you might have challenges making this work as described using the latest release.
 
 When building client-side web parts, loading data once and reusing it across different web parts will help improve the performance of your pages and decrease the load on your network. This tutorial illustrates step-by-step how to share data between web parts using a global variable.
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment.md).
 
 ## Prepare the Project
 
@@ -37,17 +44,17 @@ When prompted, use the following values:
 - **Shows recently modified documents** as your web part description.
 - **React** as the framework to use.
 
-![The SharePoint Framework Yeoman generator with the default choices](../../../../images/tutorial-sharingdata-yo-sharepoint-recent-documents.png)
+![The SharePoint Framework Yeoman generator with the default choices](../../../images/tutorial-sharingdata-yo-sharepoint-recent-documents.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots, but you can use any editor you prefer.
 
-![The SharePoint Framework project open in Visual Studio Code](../../../../images/tutorial-sharingdata-vscode.png)
+![The SharePoint Framework project open in Visual Studio Code](../../../images/tutorial-sharingdata-vscode.png)
 
 ## Show the Recently Modified Documents
 
 The Recent documents web part shows information about the most recently modified documents displayed as cards using the Office UI Fabric.
 
-![The Recent documents web part showing three small document cards representing the three most recently modified documents](../../../../images/tutorial-sharingdata-recent-documents.png)
+![The Recent documents web part showing three small document cards representing the three most recently modified documents](../../../images/tutorial-sharingdata-recent-documents.png)
 
 ### Remove the Standard _description_ Property
 
@@ -62,21 +69,14 @@ Remove the standard `description` property from the web part manifest. Open the
 
 ```json
 {
-  "$schema": "https://dev.office.com/json-schemas/spfx/client-side-web-part-manifest.schema.json",
+  "$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/clientSideComponentManifestSchema.json",
 
   "id": "7a7e3aa9-5d8a-4155-936b-0b0e06e9ca11",
   "alias": "RecentDocumentsWebPart",
   "componentType": "WebPart",
-
-  // The "*" signifies that the version should be taken from the package.json
-  "version": "*",
+  "version": "0.0.1",
   "manifestVersion": 2,
 
-  // If true, the component can only be installed on sites where Custom Script is allowed.
-  // Components that allow authors to embed arbitrary script code should set this to true.
-  // https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
-  "requiresCustomScript": false,
-
   "preconfiguredEntries": [{
     "groupId": "7a7e3aa9-5d8a-4155-936b-0b0e06e9ca11",
     "group": { "default": "Under Development" },
@@ -339,13 +339,13 @@ gulp serve
 
 In the SharePoint workbench add the Recent Documents web part to the canvas.
 
-![The recent documents web part showing three most recently modified documents as document cards](../../../../images/tutorial-sharingdata-recent-documents.png)
+![The recent documents web part showing three most recently modified documents as document cards](../../../images/tutorial-sharingdata-recent-documents.png)
 
 ## Show the Most Recently Modified Document
 
 The Recent document web part shows information about the most recently modified document.
 
-![The Recent document web part showing one big document card with information about the most recently modified document](../../../../images/tutorial-sharingdata-recent-document.png)
+![The Recent document web part showing one big document card with information about the most recently modified document](../../../images/tutorial-sharingdata-recent-document.png)
 
 ### Add the Second Web Part
 
@@ -364,7 +364,7 @@ When prompted, enter the following values:
 - **Recent document** as your web part name.
 - **Shows information about the most recently modified document** as your web part description.
 
-![The SharePoint Framework Yeoman generator with information to scaffold the second web part](../../../../images/tutorial-sharingdata-yo-sharepoint-recent-document.png)
+![The SharePoint Framework Yeoman generator with information to scaffold the second web part](../../../images/tutorial-sharingdata-yo-sharepoint-recent-document.png)
 
 ### Remove the Standard _description_ Property
 
@@ -379,21 +379,14 @@ Remove the standard `description` property from the web part manifest. Open the
 
 ```json
 {
-  "$schema": "https://dev.office.com/json-schemas/spfx/client-side-web-part-manifest.schema.json",
+  "$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/clientSideComponentManifestSchema.json",
 
   "id": "71a6f643-1ac1-47ee-a9f1-502ef52f26d4",
   "alias": "RecentDocumentWebPart",
   "componentType": "WebPart",
-
-  // The "*" signifies that the version should be taken from the package.json
-  "version": "*",
+  "version": "0.0.1",
   "manifestVersion": 2,
 
-  // If true, the component can only be installed on sites where Custom Script is allowed.
-  // Components that allow authors to embed arbitrary script code should set this to true.
-  // https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
-  "requiresCustomScript": false,
-
   "preconfiguredEntries": [{
     "groupId": "71a6f643-1ac1-47ee-a9f1-502ef52f26d4",
     "group": { "default": "Under Development" },
@@ -456,7 +449,7 @@ The Recent document web part displays information about the most recently modifi
 
 In Visual Studio Code, activate the Explorer pane, and from the **./src/webparts/recentDocuments** folder, move the **IDocument.ts** and **IDocumentActivity.ts** files one level up, to the **./src/webparts** folder.
 
-![Visual Studio Code Explorer pane with the IDocument.ts and IDocumentActivity.ts files highlighted](../../../../images/tutorial-sharingdata-interfaces.png)
+![Visual Studio Code Explorer pane with the IDocument.ts and IDocumentActivity.ts files highlighted](../../../images/tutorial-sharingdata-interfaces.png)
 
 #### Update References to the Moved Files
 
@@ -504,19 +497,19 @@ import {
   DocumentCard,
   DocumentCardPreview,
   DocumentCardTitle,
-  DocumentCardActivity
-} from 'office-ui-fabric-react/lib/DocumentCard';
-import { ImageFit } from 'office-ui-fabric-react/lib/Image';
+  DocumentCardActivity,
+  ImageFit
+} from 'office-ui-fabric-react';
 import { IDocument } from '../../IDocument';
 import styles from './RecentDocument.module.scss';
 import { IRecentDocumentProps } from './IRecentDocumentProps';
 
-export default class RecentDocument extends React.Component<IRecentDocumentProps, {}> {
+export default class RecentDocument extends React.Component<IRecentDocumentProps, void> {
   public render(): React.ReactElement<IRecentDocumentProps> {
     const document: IDocument = this.props.document;
 
     return (
-      <div className={styles.recentDocument}>
+      <div className={styles.helloWorld}>
         <DocumentCard onClickHref={document.url}>
           <DocumentCardPreview previewImages={[{
             name: document.title,
@@ -610,7 +603,7 @@ gulp serve
 
 In the SharePoint workbench add the Recent document web part to the canvas.
 
-![The recent document web part showing a document card with the information about the most recently modified document](../../../../images/tutorial-sharingdata-recent-document.png)
+![The recent document web part showing a document card with the information about the most recently modified document](../../../images/tutorial-sharingdata-recent-document.png)
 
 The current implementation is a typical example of two web parts being developed independently. If they were both placed on the same page and were loading data from SharePoint, they would execute two separate requests to retrieve similar information. If, at some point, you had to change where the information about the recently modified documents is loaded from, you would have to update both web parts. To improve the performance of loading the page and simplify maintaining the web part code, you can centralize the logic of retrieving the data and make the once retrieved data available to both web parts.
 
@@ -622,7 +615,7 @@ To centralize loading the information about recently modified documents, build a
 
 In the project folder create the **./src/services/documentsService** folder path. From the **./src/webparts** folder, move the **IDocument.ts** and **IDocumentActivity.ts** files to the **./src/services/documentsService** folder.
 
-![The IDocument.ts and IDocumentActivity.ts files highlighted in the Explorer pane in Visual Studio Code](../../../../images/tutorial-sharingdata-interfaces-documentsservice.png)
+![The IDocument.ts and IDocumentActivity.ts files highlighted in the Explorer pane in Visual Studio Code](../../../images/tutorial-sharingdata-interfaces-documentsservice.png)
 
 ### Build the Data Access Service
 
@@ -733,7 +726,7 @@ import { IDocument } from '../services/documentsService';
 instead of:
 
 ```ts
-import { IDocument } from '../services/documentsService/IDocument';
+import { IDocument } from '../services/documentsService/IDocument.ts';
 ```
 
 If at some point you decided that it's better to move the **IDocument.ts** file to a subfolder or merge a few files together, the only thing that you would change is the path in the barrel definition (**./src/services/documentsService/index.ts**). All elements in the project could still use the exact same relative path to the **documentsService** folder to reference the `IDocument` interface.
@@ -796,7 +789,7 @@ Verify that your changes work as expected, by running the following command from
 gulp serve
 ```
 
-![The Recent document and Recent documents web parts showing information about recently modified documents](../../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
+![The Recent document and Recent documents web parts showing information about recently modified documents](../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
 
 ### Load Web Part Data Using the Data Service
 
@@ -874,7 +867,7 @@ Confirm that both web parts are working correctly by running the following comma
 gulp serve
 ```
 
-![The Recent document and Recent documents web parts showing information about recently modified documents](../../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
+![The Recent document and Recent documents web parts showing information about recently modified documents](../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
 
 ### Share Data Between Web Parts
 
@@ -1003,12 +996,12 @@ Confirm that both web parts are working correctly by running the following comma
 gulp serve
 ```
 
-![The Recent document and Recent documents web parts showing information about recently modified documents](../../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
+![The Recent document and Recent documents web parts showing information about recently modified documents](../../../images/tutorial-sharingdata-recent-document-recent-documents.png)
 
 If you were to add logging statements in the different parts of the `DocumentsService.ensureRecentDocuments` method, you would see that the data is loaded once and reused for the second web part!
 
-![Developer console showing different logging statements in Microsoft Edge](../../../../images/tutorial-sharingdata-console-log.png)
+![Developer console showing different logging statements in Microsoft Edge](../../../images/tutorial-sharingdata-console-log.png)
 
 ## See Also
 
-- [Share Data Between Client-Side Web Parts](./share-data-between-web-parts)
+- [Share Data Between Client-Side Web Parts](./share-data-between-web-parts.md)
diff --git a/docs/spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties.md b/docs/spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties.md
index d201607c55..983f9a8107 100644
--- a/docs/spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties.md
+++ b/docs/spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties.md
@@ -1,12 +1,19 @@
+---
+title: Use cascading dropdowns in web part properties
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use cascading dropdowns in web part properties
 
 When designing the property pane for your SharePoint client-side web parts, you may have one web part property that displays its options based on the  value selected in another property. This scenario typically occurs when implementing cascading dropdown controls. In this article, you will learn how to create cascading dropdown controls in the web part property pane without developing a custom property pane control.
 
-![Item dropdown disabled and web part placeholder communicating loading updated list of item options](../../../../images/react-cascading-dropdowns-loading-indicator-when-loading-items.png)
+![Item dropdown disabled and web part placeholder communicating loading updated list of item options](../../../images/react-cascading-dropdowns-loading-indicator-when-loading-items.png)
 
 The source of the working web part is available on GitHub at [https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-custompropertypanecontrols](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-custompropertypanecontrols).
 
-> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment).
+> **Note:** Before following the steps in this article, be sure to [set up your SharePoint client-side web part development environment](../../set-up-your-development-environment.md).
 
 ## Create new project
 
@@ -36,11 +43,11 @@ When prompted, enter the following values:
 - **List items** as your web part name
 - **Shows list items from the selected list** as your web part description
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/react-cascading-dropdowns-yo-sharepoint.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/react-cascading-dropdowns-yo-sharepoint.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/react-cascading-dropdowns-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/react-cascading-dropdowns-visual-studio-code.png)
 
 ## Define a web part property to store the selected list
 
@@ -48,7 +55,7 @@ You will build a web part that displays list items from a selected SharePoint li
 
 In the code editor, open the **src/webparts/listItems/ListItemsWebPartManifest.json** file. Replace the default **description** property with a new property named `listName`.
 
-![Web part manifest with the list web part property highlighted](../../../../images/react-cascading-dropdowns-listname-property-web-part-manifest.png)
+![Web part manifest with the list web part property highlighted](../../../images/react-cascading-dropdowns-listname-property-web-part-manifest.png)
 
 Next, open the **src/webparts/listItems/IListItemsWebPartProps.ts** file, and replace its contents with:
 
@@ -166,7 +173,7 @@ gulp serve
 
 In the web browser, add the **List items** web part to the canvas and open its properties. Verify that the value set for the **List** property is displayed in the web part body.
 
-![Web part showing the value of the listName property](../../../../images/react-cascading-dropdowns-web-part-first-run.png)
+![Web part showing the value of the listName property](../../../images/react-cascading-dropdowns-web-part-first-run.png)
 
 ## Populate the dropdown with SharePoint lists to choose from
 
@@ -242,7 +249,7 @@ Run the following command to verify that it's working as expected:
 gulp serve
 ```
 
-![The listName property rendered in the web part property pane using a dropdown control](../../../../images/react-cascading-dropdowns-listname-property-pane-dropdown.png)
+![The listName property rendered in the web part property pane using a dropdown control](../../../images/react-cascading-dropdowns-listname-property-pane-dropdown.png)
 
 ### Show available lists in the list dropdown
 
@@ -303,7 +310,7 @@ export default class ListItemsWebPart extends BaseClientSideWebPart<IListItemsWe
 
 The **onPropertyPaneConfigurationStart** method is called by the SharePoint Framework after the web part property pane for the web part has been opened. First, the method checks if the information about the lists available in the current site has been loaded. If the list information is loaded, then the list dropdown will be enabled. If the list information about lists has not been loaded yet, the loading indicator is displayed which informs the user that the web part is loading information about lists.
 
-![Loading indicator displayed in web part while loading information about available lists](../../../../images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png)
+![Loading indicator displayed in web part while loading information about available lists](../../../images/react-cascading-dropdowns-loading-indicator-when-loading-list-info.png)
 
 After the information about available lists has been loaded the method assigns the retrieved data to the **lists** class variable, from which it can be used by the list dropdown. Next, the dropdown is enabled allowing the user to select a list. By calling  **this.context.propertyPane.refresh()** the web part property pane is refreshed and it reflects the latest changes to the list dropdown. Once list information is loaded, the loading indicator is removed by a call to the **clearLoadingIndicator** method. Since calling this method clears the web part user interface, the **render** method is called to force the web part to re-render.
 
@@ -315,13 +322,13 @@ gulp serve
 
 When you add a web part to the canvas and open its property pane, you should see the lists dropdown filled with available lists for the user to choose from.
 
-![List dropdown in the web part property pane showing the available lists](../../../../images/react-cascading-dropdowns-list-dropdown-available-lists.png)
+![List dropdown in the web part property pane showing the available lists](../../../images/react-cascading-dropdowns-list-dropdown-available-lists.png)
 
 ## Allow users to select an item from the selected list
 
 When building web parts you often need to allow users to choose an option from a set of values determined by a previously selected value, such as choosing a country based on the selected continent or choosing a list item from a selected list. This user experience is often referred to as cascading dropdowns. Using the standard SharePoint Framework client-side web parts capabilities you can build cascading dropdowns in the web part property pane. To learn how to do it you will extend the previously built web part with the ability to choose a list item based on the previously selected list.
 
-![List item dropdown open in the web part property pane](../../../../images/react-cascading-dropdowns-item-dropdown-list-items.png)
+![List item dropdown open in the web part property pane](../../../images/react-cascading-dropdowns-item-dropdown-list-items.png)
 
 ### Add item web part property
 
@@ -338,7 +345,7 @@ In the code editor open the **src/webparts/listItems/ListItemsWebPart.manifest.j
 }
 ```
 
-![Web part manifest with the itemName web part property highlighted](../../../../images/react-cascading-dropdowns-itemname-property-web-part-manifest.png)
+![Web part manifest with the itemName web part property highlighted](../../../images/react-cascading-dropdowns-itemname-property-web-part-manifest.png)
 
 Change the code in the **src/webparts/listItems/IListItemsWebPartProps.ts** file to:
 
@@ -493,7 +500,7 @@ Run the following command to verify that it's working as expected:
 gulp serve
 ```
 
-![The itemName property rendered in the web part property pane using a dropdown control](../../../../images/react-cascading-dropdowns-itemname-property-pane-dropdown.png)
+![The itemName property rendered in the web part property pane using a dropdown control](../../../images/react-cascading-dropdowns-itemname-property-pane-dropdown.png)
 
 ### Show items available in the selected list in the item dropdown
 
@@ -595,7 +602,7 @@ gulp serve
 
 As required, initially the item dropdown is disabled, requiring users to select a list first. But at this point, even after a list has been selected, the item dropdown remains disabled.
 
-![Item dropdown disabled even after a list has been selected](../../../../images/react-cascading-dropdowns-list-selected-item-disabled.png)
+![Item dropdown disabled even after a list has been selected](../../../images/react-cascading-dropdowns-list-selected-item-disabled.png)
 
 #### Update web part property pane after selecting a list
 
@@ -662,4 +669,4 @@ Once the items for the selected list are loaded they are assigned to the **items
 > isDisabled: newProps.isDisabled !== undefined ? newProps.isDisabled : newProps.disabled
 > ```
 
-![Item dropdown in the web part property pane showing available list items for the selected list](../../../../images/react-cascading-dropdowns-item-dropdown-list-items.png)
+![Item dropdown in the web part property pane showing available list items for the selected list](../../../images/react-cascading-dropdowns-item-dropdown-list-items.png)
diff --git a/docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md b/docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md
index 304a66e0f9..413f4cd72f 100644
--- a/docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md
+++ b/docs/spfx/web-parts/guidance/use-existing-javascript-libraries.md
@@ -1,3 +1,10 @@
+---
+title: Use existing JavaScript libraries in SharePoint Framework client-side web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use existing JavaScript libraries in SharePoint Framework client-side web parts
 
 When building client-side web parts on the SharePoint Framework you can benefit from using existing JavaScript libraries to build powerful solutions. There are however some considerations that you should take into account to ensure that your web parts won't negatively impact the performance of SharePoint pages that they are being used on.
@@ -53,7 +60,7 @@ export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorld
 
 SharePoint Framework uses a build toolchain based on open-source tooling such as gulp and Webpack. When building SharePoint Framework projects, these build tools automatically combine all referenced resources into a single JavaScript file in the process called bundling.
 
-![Command window with the gulp bundle task visible next to the SharePoint Framework dist folder containing the output files](../../../../images/external-scripts-gulp-bundle.png)
+![Command window with the gulp bundle task visible next to the SharePoint Framework dist folder containing the output files](../../../images/external-scripts-gulp-bundle.png)
 
 Bundling offers you a number of benefits. First of all, all resources required by your web part are available in one single JavaScript file. This simplifies the deployment as the web part consists of a single file and it's impossible to miss a dependency in the deployment process.
 As your web part uses different resources, it's important that they are loaded in the right order. The web part bundle, generated by Webpack during the build, manages loading the different resources for you including resolving any dependencies between these resources.
@@ -61,11 +68,11 @@ Bundling web parts has also its benefits for the end-users: generally speaking i
 
 When bundling existing JavaScript frameworks in the SharePoint Framework, all referenced scripts are included in the generated bundle file. Following the Angular example, an optimized web part bundle including Angular is over 170KB.
 
-![Bundle file size highlighted in Explorer](../../../../images/external-scripts-bundle-size.png)
+![Bundle file size highlighted in Explorer](../../../images/external-scripts-bundle-size.png)
 
 If you add another web part to your project, that also uses Angular, and you build the project, you get two bundle files - one for each web part, each of them being over 170KB.
 
-![Two bundle files highlighted in Explorer](../../../../images/external-scripts-two-bundles-size.png)
+![Two bundle files highlighted in Explorer](../../../images/external-scripts-two-bundles-size.png)
 
 If you would add these web parts to a page, each user would be downloading Angular multiple times - once with each web part on the page. This approach is inefficient and slows down loading the page.
 
@@ -148,23 +155,23 @@ export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorld
 
 If you build your project now and take a look at the size of the generated bundle file, you will notice that it's only 6KB.
 
-![Bundle file size highlighted in Explorer](../../../../images/external-scripts-external-angular-bundle-size.png)
+![Bundle file size highlighted in Explorer](../../../images/external-scripts-external-angular-bundle-size.png)
 
 If you add another web part to your project, that also uses Angular, and you build the project again, both bundles would be 6KB each.
 
-![Two bundle files highlighted in Explorer](../../../../images/external-scripts-external-angular-two-bundles-size.png)
+![Two bundle files highlighted in Explorer](../../../images/external-scripts-external-angular-two-bundles-size.png)
 
 It isn't correct to assume that you have just saved over 300KB. Both web parts still need Angular and will load it the first time the user visits the page where one of the web parts is placed.
 
-![Angular highlighted in the developer tools for a page with one web part on it](../../../../images/external-scripts-browser-loading-angular.png)
+![Angular highlighted in the developer tools for a page with one web part on it](../../../images/external-scripts-browser-loading-angular.png)
 
 Even if you add both Angular web parts to the page, SharePoint Framework still downloads Angular only once.
 
-![Angular highlighted in the developer tools for a page with two web parts on it](../../../../images/external-scripts-browser-loading-angular-two-web-parts.png)
+![Angular highlighted in the developer tools for a page with two web parts on it](../../../images/external-scripts-browser-loading-angular-two-web-parts.png)
 
 The real benefit of referencing existing JavaScript libraries as external resources is if your organization has a centralized location for all commonly-used scripts or you use a CDN. In such cases there is a chance that the particular JavaScript library is already present in the user's browser cache. As a result, the only thing that needs to be loaded is the web part bundle which makes the page load significantly faster.
 
-![Developer tools network tab not showing Angular despite two web parts on the page using it](../../../../images/external-scripts-browser-loading-angular-from-cache.png)
+![Developer tools network tab not showing Angular despite two web parts on the page using it](../../../images/external-scripts-browser-loading-angular-from-cache.png)
 
 The example above shows how to load Angular from a CDN, but using a public CDN is not required. In the configuration you can point any location: from a public CDN, a privately-hosted repository to a SharePoint Document Library. As long as users working with your web parts are able to access the specified URLs, your web parts will work as expected.
 
@@ -215,7 +222,7 @@ Imagine now, that you wanted to use jQuery with a jQuery plugin that itself is d
 
 loading the web part would very likely result in an error: there is a chance that both scripts would be loaded in parallel and the plugin wouldn't be able to register itself with jQuery.
 
-![Error when trying to load a web part using a non-module jQuery plugin](../../../../images/external-scripts-non-amd-no-deps-error.png)
+![Error when trying to load a web part using a non-module jQuery plugin](../../../images/external-scripts-non-amd-no-deps-error.png)
 
 As mentioned before, SharePoint Framework allows you to specify dependencies for non-module plugins. These dependencies are specified using the **globalDependencies** property:
 
@@ -232,7 +239,7 @@ Each dependency specified in the **globalDependencies** property must point to a
 
 If you would try to build the project now, you would get another error, this time stating that you can't specify a dependency to a non-module script.
 
-![Error while trying to build a SharePoint Framework with a non-module script specifying a dependency to a script that is a module](../../../../images/external-scripts-non-amd-deps-error.png)
+![Error while trying to build a SharePoint Framework with a non-module script specifying a dependency to a script that is a module](../../../images/external-scripts-non-amd-deps-error.png)
 
 To solve this problem, all you need to do is to register jQuery as a non-module script:
 
diff --git a/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md b/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
index 5e47cb1c18..9c697ceeed 100644
--- a/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
+++ b/docs/spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
@@ -1,3 +1,10 @@
+---
+title: Use sp-pnp-js with SharePoint Framework Web Parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Use sp-pnp-js with SharePoint Framework Web Parts
 
 You may opt to use the [sp-pnp-js](https://www.npmjs.com/package/sp-pnp-js) library when building your SharePoint Framework (SPFx) web parts. This library provides a fluent API to make building your REST queries intuitive and supports batching and caching. You can learn more on the [project's homepage](https://github.com/SharePoint/PnP-JS-Core) which has links to documentation, samples, and other resources to help you get started.
@@ -36,7 +43,7 @@ Enter the following values when prompted during the setup of the new project:
 - **SPPnPJSExample** as the name of the web part
 - **Example of using sp-pnp-js within SPFx** as the description
 
-![Completed Project Scaffolding](../../../../images/sp-pnp-js-guide-completed-setup.png)
+![Completed Project Scaffolding](../../../images/sp-pnp-js-guide-completed-setup.png)
 
 
 Once the scaffolding completes, open the project in the code editor of your choosing. The screenshots shown here demonstrate [Visual Studio Code](https://code.visualstudio.com/). To open the directory within Visual Studio Code, enter the following in the console:
@@ -45,7 +52,7 @@ Once the scaffolding completes, open the project in the code editor of your choo
 code .
 ```
 
-![Project as first opened in visual studio code](../../../../images/sp-pnp-js-guide-first-open.png)
+![Project as first opened in visual studio code](../../../images/sp-pnp-js-guide-first-open.png)
 
 ## Install And Setup sp-pnp-js
 
@@ -340,7 +347,7 @@ Start the sample and add the web part to your SharePoint hosted workbench (/_lay
 gulp serve --nobrowser
 ```
 
-![Project as it appears on first run](../../../../images/sp-pnp-js-guide-first-run.png)
+![Project as it appears on first run](../../../images/sp-pnp-js-guide-first-run.png)
 
 You can delete existing items by clicking on the trashcan icon, or add new items by putting values in both fields and clicking the add button.
 
@@ -493,7 +500,7 @@ Finally, type `gulp serve` in the console to bring up the local workbench, which
 gulp serve
 ```
 
-![Project as it appears running in the local workbench with mock data](../../../../images/sp-pnp-js-guide-with-mock-data.png)
+![Project as it appears running in the local workbench with mock data](../../../images/sp-pnp-js-guide-with-mock-data.png)
 
 
 ## Download Full Example Code
diff --git a/docs/spfx/web-parts/guidance/validate-web-part-property-values.md b/docs/spfx/web-parts/guidance/validate-web-part-property-values.md
index aed3877ceb..3857c41cd3 100644
--- a/docs/spfx/web-parts/guidance/validate-web-part-property-values.md
+++ b/docs/spfx/web-parts/guidance/validate-web-part-property-values.md
@@ -1,8 +1,15 @@
+---
+title: Validate web part property values
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Validate web part property values
 
 When working with web parts, users can configure them to meet their needs using their properties. By validating the provided configuration values you can make it easier for users to configure the web part and improve the overall user experience of working with your web part. In this article you will learn how to validate web part property values in SharePoint Framework client-side web parts.
 
-> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment) for building SharePoint Framework solutions.
+> **Note:** Before following the steps in this article, be sure to [set up your development environment](../../set-up-your-development-environment.md) for building SharePoint Framework solutions.
 
 ## Create new project
 
@@ -32,11 +39,11 @@ When prompted, enter the following values:
 - **List info** as your web part name
 - **Shows information about the selected list** as your web part description
 
-![SharePoint Framework Yeoman generator with the default choices](../../../../images/property-validation-yeoman-generator.png)
+![SharePoint Framework Yeoman generator with the default choices](../../../images/property-validation-yeoman-generator.png)
 
 Once the scaffolding completes, open your project folder in your code editor. This article uses Visual Studio Code in the steps and screenshots but you can use any editor you prefer.
 
-![SharePoint Framework project open in Visual Studio Code](../../../../images/property-validation-visual-studio-code.png)
+![SharePoint Framework project open in Visual Studio Code](../../../images/property-validation-visual-studio-code.png)
 
 ## Validate web part property values in the SharePoint Framework
 
@@ -114,15 +121,15 @@ gulp serve
 
 In the workbench, add the web part to canvas and open its properties. If you remove the description you should see the first validation error.
 
-![Validation error displayed on a required property without a value specified](../../../../images/property-validation-empty-description-error.png)
+![Validation error displayed on a required property without a value specified](../../../images/property-validation-empty-description-error.png)
 
 Next, try providing a value that's longer than 40 characters. You should see another validation error displayed below the text field.
 
-![Validation error displayed when the provided value is longer than allowed](../../../../images/property-validation-description-too-long-error.png)
+![Validation error displayed when the provided value is longer than allowed](../../../images/property-validation-description-too-long-error.png)
 
 Notice, that when providing an invalid value, the web part is rendered showing the last valid value. Additionally, in the non-reactive property pane mode, if one of the web part properties is invalid, the **Apply** button is disabled, preventing the user from applying the invalid configuration.
 
-![Disabled Apply button rendered when a web part property has an invalid value](../../../../images/property-validation-description-error-apply-disabled.png)
+![Disabled Apply button rendered when a web part property has an invalid value](../../../images/property-validation-description-error-apply-disabled.png)
 
 ### Validate web part property values using remote APIs
 
@@ -243,7 +250,7 @@ Run the following command to verify that the project is running and that the new
 gulp serve
 ```
 
-![The list name property displayed in the web part property pane](../../../../images/property-validation-list-name-property.png)
+![The list name property displayed in the web part property pane](../../../images/property-validation-list-name-property.png)
 
 #### Validate the name of the list using the SharePoint REST API
 
@@ -344,21 +351,21 @@ Because the list name validation method communicates with the SharePoint REST AP
 
 Add the web part to the canvas and open its properties. Because you haven't specified a default value for the list name, which is a required property, you will see a validation error.
 
-![Validation error displayed on a required property without a value specified](../../../../images/property-validation-empty-list-name-error.png)
+![Validation error displayed on a required property without a value specified](../../../images/property-validation-empty-list-name-error.png)
 
 If you provide a name of a list that doesn't exist, the web part will display a validation error stating that the list you specified doesn't exist in the current site.
 
-![Validation error displayed after providing a name of a list that doesn't exist in the current site](../../../../images/property-validation-invalid-list-name-error.png)
+![Validation error displayed after providing a name of a list that doesn't exist in the current site](../../../images/property-validation-invalid-list-name-error.png)
 
 If you specify a name of an existing list, the validation error will disappear.
 
-![No validation error displayed for a valid list name](../../../../images/property-validation-valid-list-name.png)
+![No validation error displayed for a valid list name](../../../images/property-validation-valid-list-name.png)
 
 #### Optimize validation using remote APIs
 
 When validating web part properties using remote APIs, SharePoint Framework monitors changes in the property pane controls and sends updated values for validation to the specified validation handler. By default, the SharePoint Framework waits 200ms before triggering the validation process. If the user hasn't changed the particular value for 200ms, the SharePoint Framework will start the validation process. When the validation handler uses a remote API, each time the validation process starts, that method will issue a web request to the API to validate the specified value. If users don't type fast enough, this will result in partially completed values being sent over for validation unnecessarily stressing the network and the API. In such cases you should consider increasing the validation delay.
 
-![Network tools in Microsoft Edge showing web requests with partial list name being sent over for validation](../../../../images/property-validation-partial-list-name-validation.png)
+![Network tools in Microsoft Edge showing web requests with partial list name being sent over for validation](../../../images/property-validation-partial-list-name-validation.png)
 
 You can configure the validation delay for each property separately, depending on the type of value that users need to provide. Following steps illustrate how to increase the validation delay for the **listName** property.
 
@@ -407,4 +414,4 @@ Run the following command to see that the applied delay is working as expected:
 
 ```sh
 gulp serve --nobrowser
-```
\ No newline at end of file
+```
diff --git a/docs/spfx/web-parts/overview-client-side-web-parts.md b/docs/spfx/web-parts/overview-client-side-web-parts.md
index 3fcfc2ef0f..3bf40de958 100644
--- a/docs/spfx/web-parts/overview-client-side-web-parts.md
+++ b/docs/spfx/web-parts/overview-client-side-web-parts.md
@@ -1,3 +1,10 @@
+---
+title: Overview of SharePoint client-side web parts
+ms.date: 09/25/2017
+ms.prod: sharepoint
+---
+
+
 # Overview of SharePoint client-side web parts
 
 SharePoint client-side web parts are controls that appear inside a SharePoint page but run locally in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern script development tools and the SharePoint workbench (a development test surface), and you can deploy your client-side web parts to classic web part pages in Office 365 Developer tenants.  In addition to plain JavaScript projects, you can build web parts alongside common scripting frameworks, such as AngularJS and React. For example, you can use React along with components from Office UI Fabric React to quickly create experiences based on the same components used in Office 365.
diff --git a/docs/toc.yml b/docs/toc.yml
new file mode 100644
index 0000000000..e50a579575
--- /dev/null
+++ b/docs/toc.yml
@@ -0,0 +1,1195 @@
+- name: SharePoint development
+  href: index.md
+- name: SharePoint Framework
+  items:
+  - name: Overview
+    href: spfx/sharepoint-framework-overview.md
+  - name: Roadmap
+    href: spfx/roadmap.md
+  - name: Known issues and FAQ
+    href: spfx/known-issues-and-common-questions.md
+  - name: Tools and libraries
+    href: spfx/tools-and-libraries.md
+  - name: Set up your Office 365 tenant
+    href: spfx/set-up-your-developer-tenant.md
+  - name: Set up your development environment
+    href: spfx/set-up-your-development-environment.md
+  - name: SharePoint 2016 support
+    href: spfx/sharepoint-2016-support.md
+  - name: Debug solutions with VS Code
+    href: spfx/debug-in-vscode.md
+  - name: Enterprise Guidance
+    href: spfx/enterprise-guidance.md
+  - name: Team-based development
+    href: spfx/team-based-development-on-sharepoint-framework.md
+  - name: Using GraphHttpClient
+    href: spfx/call-microsoft-graph-using-graphhttpclient.md
+  - name: Tenant-Scoped deployment
+    href: spfx/tenant-scoped-deployment.md
+  - name: Use theme colors in your solution
+    href: spfx/use-theme-colors-in-your-customizations.md
+  - name: Working with CSS
+    href: spfx/css-recommendations.md
+  - name: Toolchain
+    href: spfx/toolchain/sharepoint-framework-toolchain.md
+    items:
+    - name: SharePoint Framework Toolchain
+      href: spfx/toolchain/sharepoint-framework-toolchain.md
+    - name: Yeoman Sharepoint generator
+      href: spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator.md
+    - name: Update SharePoint Framework packages
+      href: spfx/toolchain/update-latest-packages.md
+    - name: Optimize builds for production
+      href: spfx/toolchain/optimize-builds-for-production.md
+    - name: Integrate gulp tasks in SharePoint Framework toolchain
+      href: spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md
+    - name: Extending Webpack in SharePoint Framework toolchain
+      href: spfx/toolchain/extending-webpack-in-build-pipeline.md
+    - name: Provision SharePoint assets
+      href: spfx/toolchain/provision-sharepoint-assets.md
+  - name: Extensions (Preview)
+    items:
+    - name: Overview
+      href: spfx/extensions/overview-extensions.md
+    - name: Changes in the RC release
+      href: spfx/extensions/changes-between-dev-preview-and-rc.md
+    - name: Get started
+      items:
+      - name: Build your first extension
+        href: spfx/extensions/get-started/build-a-hello-world-extension.md
+      - name: Using page placeholders
+        href: spfx/extensions/get-started/using-page-placeholder-with-extensions.md
+      - name: Deploy your extension to SharePoint
+        href: spfx/extensions/get-started/serving-your-extension-from-sharepoint.md
+      - name: Hosting extension from CDN
+        href: spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
+      - name: Build FieldCustomizer
+        href: spfx/extensions/get-started/building-simple-field-customizer.md
+      - name: Build ListView Command Set
+        href: spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md
+    - name: Guidance
+      items:
+      - name: Use custom dialog boxes
+        href: spfx/extensions/guidance/using-custom-dialogs-with-spfx.md
+  - name: Web parts
+    items:
+    - name: Overview
+      href: spfx/web-parts/overview-client-side-web-parts.md
+    - name: Get started
+      items:
+      - name: Build your first web part
+        href: spfx/web-parts/get-started/build-a-hello-world-web-part.md
+      - name: Connect to SharePoint
+        href: spfx/web-parts/get-started/connect-to-sharepoint.md
+      - name: Deploy your web part to a SharePoint page
+        href: spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page.md
+      - name: Deploy to a Azure CDN
+        href: spfx/web-parts/get-started/deploy-web-part-to-cdn.md
+      - name: Add jQueryUI Accordion
+        href: spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part.md
+      - name: Use Office UI Fabric React components
+        href: spfx/web-parts/get-started/use-fabric-react-components.md
+      - name: Provisioning assets from solution
+        href: spfx/web-parts/get-started/provision-sp-assets-from-package.md
+      - name: Deploy to Office 365 CDN
+        href: spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md
+    - name: Basics
+      items:
+      - name: Design considerations
+        href: spfx/web-parts/basics/design-considerations-for-web-parts.md
+      - name: Add properties to the property pane
+        href: spfx/web-parts/basics/integrate-with-property-pane.md
+      - name: Add an external library
+        href: spfx/web-parts/basics/add-an-external-library.md
+      - name: Working with the original __RequestDigest
+        href: spfx/web-parts/basics/working-with-requestdigest.md
+      - name: Notes on solution packaging
+        href: spfx/web-parts/basics/notes-on-solution-packaging.md
+    - name: Guidance
+      items:
+      - name: SharePoint Framework solutions governance considerations
+        href: spfx/web-parts/guidance/governance-considerations.md
+      - name: Use existing JavaScript libraries
+        href: spfx/web-parts/guidance/use-existing-javascript-libraries.md
+      - name: Reference third-party CSS styles
+        href: spfx/web-parts/guidance/reference-third-party-css-styles.md
+      - name: Using preconfigured entries
+        href: spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries.md
+      - name: Integrate web part properties with SharePoint
+        href: spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint.md
+      - name: Using JSOM in web part
+        href: spfx/web-parts/guidance/connect-to-sharepoint-using-jsom.md
+      - name: Validate property pane entries
+        href: spfx/web-parts/guidance/validate-web-part-property-values.md
+      - name: Use cascading dropdowns in property pane
+        href: spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties.md
+      - name: Build custom controls for the property pane
+        href: spfx/web-parts/guidance/build-custom-property-pane-controls.md
+      - name: Share data between web parts
+        href: spfx/web-parts/guidance/share-data-between-web-parts.md
+      - name: Sharing data between web parts (tutorial)
+        href: spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable.md
+      - name: Migrating Script Editor Web Part customizations
+        href: spfx/web-parts/guidance/migrate-script-editor-web-part-customizations.md
+      - name: Migrating jQuery and DataTables solution
+        href: spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx.md
+      - name: Migrating jQuery and FullCalendar solution
+        href: spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx.md
+      - name: Connect to API secured with Azure Active Directory
+        href: spfx/web-parts/guidance/connect-to-api-secured-with-aad.md
+      - name: Office UI Fabric integration
+        href: spfx/web-parts/guidance/office-ui-fabric-integration.md
+      - name: Build web parts with SP PnP JS
+        href: spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts.md
+      - name: Build web parts with Angular v1.x
+        href: spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x.md
+      - name: Migrating Angular applications
+        href: spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework.md
+      - name: Localization
+        href: spfx/web-parts/guidance/localize-web-parts.md
+      - name: Call the Microsoft Graph API
+        href: spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
+- name: SharePoint APIs
+  items:
+  - name: REST
+    items:
+    - name: SharePoint REST service
+      href: apis/rest/get-to-know-the-sharepoint-rest-service.md
+    - name: Basic operations
+      href: apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md
+    - name: Lists and list items
+      href: apis/rest/working-with-lists-and-list-items-with-rest.md
+    - name: Folders and files
+      href: apis/rest/working-with-folders-and-files-with-rest.md
+    - name: REST endpoint URIs
+      href: apis/rest/determine-sharepoint-rest-service-endpoint-uris.md
+    - name: OData query operations
+      href: apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md
+    - name: Navigate data structure
+      href: apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
+    - name: Synchronize SharePoint items
+      href: apis/rest/synchronize-sharepoint-items-using-the-rest-service.md
+    - name: Upload a file
+      href: apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md
+    - name: Manage permissions
+      href: apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
+    - name: Batch requests
+      href: apis/rest/make-batch-requests-with-the-rest-apis.md
+  - name: Webhooks
+    items:
+    - name: Overview
+      href: apis/webhooks/overview-sharepoint-webhooks.md
+    - name: Get started
+      href: apis/webhooks/get-started-webhooks.md
+    - name: Reference implementation
+      href: apis/webhooks/webhooks-reference-implementation.md
+    - name: Azure Functions and SharePoint webhooks
+      href: apis/webhooks/sharepoint-webhooks-using-azure-functions.md
+    - name: SharePoint lists
+      items:
+      - name: Overview
+        href: apis/webhooks/lists/overview-sharepoint-list-webhooks.md
+      - name: Create a subscription
+        href: apis/webhooks/lists/create-subscription.md
+      - name: Update a subscription
+        href: apis/webhooks/lists/update-subscription.md
+      - name: Delete a subscription
+        href: apis/webhooks/lists/delete-subscription.md
+      - name: Get subscriptions
+        href: apis/webhooks/lists/get-subscription.md
+- name: SharePoint development overview
+  href: general-development/sharepoint-development-overview.md
+  items:
+  - name: What's new for developers in SharePoint
+    href: general-development/what-s-new-for-developers-in-sharepoint.md
+  - name: Protocol handler error in SharePoint 2016
+    href: general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016.md
+  - name: Programming models
+    href: general-development/programming-models-in-sharepoint.md
+    items:
+    - name: SharePoint Add-ins compared with SharePoint solutions
+      href: general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md
+    - name: Build farm solutions
+      href: general-development/build-farm-solutions-in-sharepoint.md
+      items:
+      - name: 'How to: Customize a field type using client-side rendering'
+        href: general-development/how-to-customize-a-field-type-using-client-side-rendering.md
+      - name: URLs and tokens in SharePoint
+        href: general-development/urls-and-tokens-in-sharepoint.md
+      - name: Virtual directories in SharePoint solutions
+        href: general-development/virtual-directories-in-sharepoint-solutions.md
+    - name: Access SharePoint from mobile and native device apps
+      href: general-development/access-sharepoint-from-mobile-and-native-device-apps.md
+    - name: Build Windows Phone apps that access SharePoint
+      href: general-development/build-windows-phone-apps-that-access-sharepoint.md
+      items:
+      - name: 'How to: Set up an environment for developing mobile apps for SharePoint'
+        href: general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint.md
+      - name: Overview of Windows Phone SharePoint application templates in Visual Studio
+        href: general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio.md
+      - name: Architecture of the Windows Phone SharePoint List Application template
+        href: general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md
+      - name: 'How to: Create a Windows Phone SharePoint list app'
+        href: general-development/how-to-create-a-windows-phone-sharepoint-list-app.md
+      - name: 'How to: Store and retrieve SharePoint list items on a Windows Phone'
+        href: general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone.md
+      - name: 'How to: Implement business logic and data validation in a Windows Phone app for SharePoint'
+        href: general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s.md
+      - name: 'How to: Support and convert SharePoint field types for Windows Phone apps'
+        href: general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps.md
+      - name: 'How to: Customize list item queries and filter data for Windows Phone apps'
+        href: general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps.md
+      - name: 'How to: Customize the user interface of a SharePoint list app for Windows Phone'
+        href: general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph.md
+      - name: 'How to: Use multiple SharePoint lists in a Windows Phone app'
+        href: general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app.md
+      - name: 'How to: Configure and use push notifications in SharePoint apps for Windows Phone'
+        href: general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows.md
+      - name: 'How to: Create a mobile app in SharePoint that contains data from an external data source'
+        href: general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa.md
+      - name: 'How to: Integrate maps with Windows Phone apps and SharePoint lists'
+        href: general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists.md
+      - name: 'How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces'
+        href: general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res.md
+      - name: Overview of the SharePoint mobile object model
+        href: general-development/overview-of-the-sharepoint-mobile-object-model.md
+      - name: Overview of the SharePoint mobile client authentication object model
+        href: general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md
+      - name: 'How to: Export the Name field in a Document Library list to a mobile app'
+        href: general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app.md
+      - name: Build localized applications for Windows Phone based on the SharePoint templates
+        href: general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates.md
+      - name: Language support for Windows Phone in SharePoint
+        href: general-development/language-support-for-windows-phone-in-sharepoint.md
+      - name: Build mobile apps for other platforms using SharePoint
+        href: general-development/build-mobile-apps-for-other-platforms-using-sharepoint.md
+    - name: Build reusable components for SharePoint
+      href: general-development/build-reusable-components-for-sharepoint.md
+    - name: Build sites for SharePoint
+      href: general-development/build-sites-for-sharepoint.md
+      items:
+      - name: What's new with SharePoint site development
+        href: general-development/what-s-new-with-sharepoint-site-development.md
+      - name: Develop the site design in SharePoint
+        href: general-development/develop-the-site-design-in-sharepoint.md
+        items:
+        - name: Overview of Design Manager
+          href: general-development/overview-of-design-manager-in-sharepoint.md
+        - name: Overview of the SharePoint page model
+          href: general-development/overview-of-the-sharepoint-page-model.md
+        - name: Master pages, the Master Page Gallery, and page layouts
+          href: general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint.md
+          items:
+          - name: 'How to: Map a network drive to the Master Page Gallery'
+            href: general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery.md
+          - name: 'How to: Apply a master page to a site'
+            href: general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint.md
+          - name: 'How to: Create a page layout'
+            href: general-development/how-to-create-a-page-layout-in-sharepoint.md
+          - name: 'How to: Customize page layouts for a catalog-based site'
+            href: general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint.md
+          - name: 'How to: Apply styles to page fields'
+            href: general-development/how-to-apply-styles-to-page-fields-in-sharepoint.md
+          - name: 'How to: Resolve errors and warnings when previewing a page'
+            href: general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint.md
+          - name: 'How to: Convert an HTML file into a master page'
+            href: general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint.md
+          - name: 'How to: Create a minimal master page'
+            href: general-development/how-to-create-a-minimal-master-page-in-sharepoint.md
+          - name: 'How to: Change the preview page in Design Manager'
+            href: general-development/how-to-change-the-preview-page-in-sharepoint-design-manager.md
+          - name: SharePoint Online Suite Navigation control
+            href: general-development/sharepoint-online-suite-navigation-control.md
+        - name: 'How to: Retrieve the URL of a Pages library'
+          href: general-development/how-to-retrieve-the-url-of-a-pages-library.md
+        - name: Branding and design capabilities
+          href: general-development/sharepoint-design-manager-branding-and-design-capabilities.md
+          items:
+          - name: Design packages
+            href: general-development/sharepoint-design-manager-design-packages.md
+          - name: Device channels
+            href: general-development/sharepoint-design-manager-device-channels.md
+          - name: Display templates
+            href: general-development/sharepoint-design-manager-display-templates.md
+          - name: Image renditions
+            href: general-development/sharepoint-design-manager-image-renditions.md
+          - name: Snippets
+            href: general-development/sharepoint-design-manager-snippets.md
+            items:
+            - name: 'How to: Add a Device Channel Panel snippet'
+              href: general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint.md
+            - name: 'How to: Add an Edit Mode Panel snippet'
+              href: general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint.md
+            - name: 'How to: Add a Web Part zone snippet'
+              href: general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint.md
+            - name: 'How to: Add a Security Trim snippet'
+              href: general-development/how-to-add-a-security-trim-snippet-in-sharepoint.md
+            - name: 'How to: Brand snippets by using CSS'
+              href: general-development/how-to-brand-snippets-by-using-css-in-sharepoint.md
+          - name: Themes
+            href: general-development/themes-overview-for-sharepoint.md
+            items:
+            - name: 'How to: Create a master page preview file'
+              href: general-development/how-to-create-a-master-page-preview-file-in-sharepoint.md
+            - name: 'How to: Deploy a custom theme'
+              href: general-development/how-to-deploy-a-custom-theme-in-sharepoint.md
+            - name: 'How to: Make custom CSS files themable'
+              href: general-development/how-to-make-custom-css-files-themable-in-sharepoint.md
+            - name: Upgrade custom themes and CSS
+              href: general-development/upgrade-custom-themes-and-css-to-sharepoint.md
+            - name: Color palettes and fonts
+              href: general-development/color-palettes-and-fonts-in-sharepoint.md
+      - name: Managed metadata and navigation in SharePoint
+        href: general-development/managed-metadata-and-navigation-in-sharepoint.md
+        items:
+        - name: Managed navigation in SharePoint
+          href: general-development/managed-navigation-in-sharepoint.md
+        - name: Content Search Web Part in SharePoint
+          href: general-development/content-search-web-part-in-sharepoint.md
+        - name: 'How to: Use code to pin terms to navigation term sets in SharePoint'
+          href: general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint.md
+      - name: Publish SharePoint sites
+        href: general-development/publish-sharepoint-sites.md
+        items:
+        - name: Cross-site publishing in SharePoint
+          href: general-development/cross-site-publishing-in-sharepoint.md
+      - name: User segmentation in SharePoint
+        href: general-development/user-segmentation-in-sharepoint.md
+      - name: Minimal Download Strategy overview
+        href: general-development/minimal-download-strategy-overview.md
+      - name: Modify SharePoint components for MDS
+        href: general-development/modify-sharepoint-components-for-mds.md
+      - name: Optimize page performance
+        href: general-development/optimize-page-performance-in-sharepoint.md
+      - name: Optimize SharePoint stie accessibility
+        href: general-development/optimize-sharepoint-site-accessibility.md
+  - name: Add SharePoint capabilities
+    href: general-development/add-sharepoint-capabilities.md
+    items:
+    - name: Workflows
+      href: general-development/workflows-in-sharepoint.md
+      items:
+      - name: Get started with workflows in SharePoint
+        href: general-development/get-started-with-workflows-in-sharepoint.md
+      - name: SharePoint workflow fundamentals
+        href: general-development/sharepoint-workflow-fundamentals.md
+      - name: What's new in workflows for SharePoint
+        href: general-development/what-s-new-in-workflows-for-sharepoint.md
+      - name: Prepare to set up and configure a SharePoint workflow development environment
+        href: general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md
+      - name: 'How to: Configure MSMQ for SharePoint workflows'
+        href: general-development/how-to-configure-msmq-for-sharepoint-workflows.md
+      - name: Workflow initiation and configuration properties
+        href: general-development/workflow-initiation-and-configuration-properties.md
+      - name: SharePoint workflow development best practices
+        href: general-development/sharepoint-workflow-development-best-practices.md
+      - name: Debugging SharePoint Server workflows
+        href: general-development/debugging-sharepoint-server-workflows.md
+      - name: Using the pairing cmdlet Register-SPWorkflowService
+        href: general-development/using-the-pairing-cmdlet-register-spworkflowservice.md
+      - name: SharePoint workflow samples
+        href: general-development/sharepoint-workflow-samples.md
+      - name: Develop SharePoint workflows using Visual Studio
+        href: general-development/develop-sharepoint-workflows-using-visual-studio.md
+        items:
+        - name: Create a SharePoint workflow app using Visual Studio 2012
+          href: general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012.md
+        - name: 'How to: Create SharePoint Workflows using Visual Studio'
+          href: general-development/how-to-create-sharepoint-workflows-using-visual-studio.md
+        - name: Working with the SharePoint Workflow Services Client Side Object Model
+          href: general-development/working-with-the-sharepoint-workflow-services-client-side-object-model.md
+        - name: Working with Web Services in SharePoint Workflows using Visual Studio 2012
+          href: general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012.md
+        - name: Working with Tasks in SharePoint Workflows using Visual Studio 2012
+          href: general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md
+        - name: 'How to: Create Custom SharePoint Server Workflow Forms with Visual Studio 2012'
+          href: general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20.md
+        - name: 'How to: Build and deploy workflow custom actions'
+          href: general-development/how-to-build-and-deploy-workflow-custom-actions.md
+        - name: Use workflow interop for SharePoint
+          href: general-development/use-workflow-interop-for-sharepoint.md
+        - name: Common error messages in SharePoint workflow development
+          href: general-development/common-error-messages-in-sharepoint-workflow-development.md
+        - name: SharePoint workflow object model
+          href: general-development/sharepoint-workflow-object-model.md
+      - name: Workflow development in SharePoint Designer and Visio
+        href: general-development/workflow-development-in-sharepoint-designer-and-visio.md
+        items:
+        - name: What's changed in SharePoint Designer
+          href: general-development/what-s-changed-in-sharepoint-designer.md
+        - name: Creating a workflow by using SharePoint Designer and the SharePoint Workflow platform
+          href: general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo.md
+        - name: Shapes in the SharePoint Server workflow template in Visio
+          href: general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio.md
+        - name: Troubleshooting SharePoint Server workflow validation errors in Visio
+          href: general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio.md
+        - name: Understanding Dictionary actions in SharePoint Designer 2013
+          href: general-development/understanding-dictionary-actions-in-sharepoint-designer.md
+        - name: Understanding Coordination actions in SharePoint Designer 2013
+          href: general-development/understanding-coordination-actions-in-sharepoint-designer.md
+        - name: Understanding Task Actions in SharePoint Designer 2013
+          href: general-development/understanding-task-actions-in-sharepoint-designer.md
+        - name: Understanding Eventing Actions in SharePoint Designer 2013
+          href: general-development/understanding-eventing-actions-in-sharepoint-designer.md
+        - name: Getting familiar with Visual Designer for workflow in SharePoint Designer 2013
+          href: general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer.md
+        - name: Working with Web Services in SharePoint Workflows using SharePoint Designer 2013
+          href: general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer.md
+        - name: Understanding how to package and deploy workflow in SharePoint
+          href: general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint.md
+        - name: Create a workflow with elevated permissions by using the SharePoint Workflow platform
+          href: general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo.md
+        - name: Matching the SharePoint Designer version with the farm version
+          href: general-development/matching-the-sharepoint-designer-version-with-the-farm-version.md
+        - name: Transfer a workflow between SharePoint Designer 2013 and Visio Professional 2013 (SharePoint 2010 Workflow platform)
+          href: general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional.md
+      - name: Workflow actions and activities reference
+        href: general-development/workflow-actions-and-activities-reference-for-sharepoint.md
+        items:
+        - name: Workflow activity classes
+          href: general-development/workflow-activity-classes-in-sharepoint.md
+        - name: Workflow actions quick reference (SharePoint Workflow platform)
+          href: general-development/workflow-actions-quick-reference-sharepoint-workflow-platform.md
+        - name: Workflow actions available using the workflow interop bridge
+          href: general-development/workflow-actions-available-using-the-workflow-interop-bridge.md
+        - name: Workflow conditions quick reference (SharePoint 2010 Workflow platform)
+          href: general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform.md
+        - name: Workflow actions quick reference (SharePoint 2010 Workflow platform)
+          href: general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform.md
+        - name: 'Visio shapes in SharePoint Designer 2013: A quick reference guide (SharePoint 2010 Workflow platform)'
+          href: general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010.md
+        - name: Validation issues in Visio (SharePoint 2010 Workflow platform)
+          href: general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform.md
+    - name: Social and collaboration
+      href: general-development/social-and-collaboration-features-in-sharepoint.md
+      items:
+      - name: What's new for developers in social and collaboration features
+        href: general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201.md
+      - name: Get started developing with social features
+        href: general-development/get-started-developing-with-social-features-in-sharepoint.md
+        items:
+        - name: 'How to: Learn to read and write to the social feed by using the .NET client object model'
+          href: general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object.md
+        - name: 'How to: Learn to read and write to the social feed by using the REST service'
+          href: general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s.md
+        - name: Social feed REST API reference
+          href: general-development/social-feed-rest-api-reference-for-sharepoint.md
+        - name: Following people and content REST API reference
+          href: general-development/following-people-and-content-rest-api-reference-for-sharepoint.md
+      - name: Work with social feeds
+        href: general-development/work-with-social-feeds-in-sharepoint.md
+        items:
+        - name: 'How to: Create and delete posts and retrieve the social feed by using the .NET client object model'
+          href: general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli.md
+        - name: 'How to: Create and delete posts and retrieve the social feed by using the JavaScript object model'
+          href: general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr.md
+        - name: 'How to: Include mentions, tags, and links to sites and documents in posts'
+          href: general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep.md
+        - name: 'How to: Embed images, videos, and documents in posts'
+          href: general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server.md
+        - name: Reference threads and digest threads in social feeds
+          href: general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md
+      - name: Follow people
+        href: general-development/follow-people-in-sharepoint.md
+        items:
+        - name: 'How to: Follow people by using the .NET client object model'
+          href: general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint.md
+        - name: 'How to: Follow people by using the JavaScript object model'
+          href: general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint.md
+      - name: Follow content
+        href: general-development/follow-content-in-sharepoint.md
+        items:
+        - name: 'How to: Follow documents and sites by using the .NET client object model'
+          href: general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep.md
+        - name: 'How to: Follow documents, sites, and tags by using the REST service'
+          href: general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2.md
+      - name: Work with user profiles
+        href: general-development/work-with-user-profiles-in-sharepoint.md
+        items:
+        - name: 'How to: Retrieve user profile properties by using the .NET client object model'
+          href: general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in.md
+        - name: 'How to: Retrieve user profile properties by using the JavaScript object model'
+          href: general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in.md
+        - name: 'How to: Work with user profiles by using the server object model'
+          href: general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md
+    - name: Integrating location and map functionality
+      href: general-development/integrating-location-and-map-functionality-in-sharepoint.md
+      items:
+      - name: 'How to: Add a Geolocation column to a list programmatically in SharePoint'
+        href: general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md
+      - name: Create a map view for the Geolocation field in SharePoint
+        href: general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint.md
+      - name: 'How to: Set the Bing Maps key at the web and farm level in SharePoint'
+        href: general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md
+      - name: 'How to: Extend the Geolocation field type using client-side rendering'
+        href: general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering.md
+    - name: Search in SharePoint
+      href: general-development/search-in-sharepoint.md
+      items:
+      - name: What's new in SharePoint search for developers
+        href: general-development/what-s-new-in-sharepoint-search-for-developers.md
+      - name: Searching new content with SharePoint Search
+        href: general-development/searching-new-content-with-sharepoint-search.md
+        items:
+        - name: Search connector framework
+          href: general-development/search-connector-framework-in-sharepoint.md
+          items:
+          - name: Enhancing the BDC model file for Search
+            href: general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint.md
+          - name: 'How to: Crawl associated external content types'
+            href: general-development/how-to-crawl-associated-external-content-types-in-sharepoint.md
+          - name: 'How to: Crawl binary large objects (BLOBs)'
+            href: general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint.md
+          - name: 'How to: Configure item-level security'
+            href: general-development/how-to-configure-item-level-security-in-sharepoint.md
+      - name: Configure search in SharePoint
+        href: general-development/configure-search-in-sharepoint.md
+        items:
+        - name: Custom word breakers in SharePoint Server
+          href: general-development/custom-word-breakers-in-sharepoint-server.md
+        - name: Custom content processing with the Content Enrichment web service callout
+          href: general-development/custom-content-processing-with-the-content-enrichment-web-service-callout.md
+          items:
+          - name: 'How to: Use the Content Enrichment web service callout for SharePoint Server'
+            href: general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server.md
+          - name: Trigger expression syntax
+            href: general-development/trigger-expressions-syntax-in-sharepoint.md
+      - name: Building search queries in SharePoint
+        href: general-development/building-search-queries-in-sharepoint.md
+        items:
+        - name: Keyword Query Language (KQL) syntax reference
+          href: general-development/keyword-query-language-kql-syntax-reference.md
+        - name: FAST Query Language (FQL) syntax reference
+          href: general-development/fast-query-language-fql-syntax-reference.md
+        - name: Using the SharePoint search Query APIs
+          href: general-development/using-the-sharepoint-search-query-apis.md
+      - name: SharePoint Search REST API overview
+        href: general-development/sharepoint-search-rest-api-overview.md
+        items:
+        - name: Retrieving query suggestions using the Search REST service
+          href: general-development/retrieving-query-suggestions-using-the-search-rest-service.md
+      - name: Search add-ins in SharePoint
+        href: general-development/search-add-ins-in-sharepoint.md
+      - name: Customizing search results in SharePoint
+        href: general-development/customizing-search-results-in-sharepoint.md
+      - name: Sorting search results in SharePoint
+        href: general-development/sorting-search-results-in-sharepoint.md
+      - name: Customizing ranking models to improve relevance
+        href: general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint.md
+      - name: Custom security trimming for Search in SharePoint Server
+        href: general-development/custom-security-trimming-for-search-in-sharepoint-server.md
+        items:
+        - name: 'How to: Use a custom security trimmer for SharePoint Server search results'
+          href: general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results.md
+      - name: Exporting and importing search configuration settings programmatically
+        href: general-development/exporting-and-importing-search-configuration-settings-in-sharepoint.md
+      - name: Query Refinement in SharePoint
+        href: general-development/query-refinement-in-sharepoint.md
+    - name: Business Connectivity Services
+      href: general-development/business-connectivity-services-in-sharepoint.md
+      items:
+      - name: What's new in Business Connectivity Services
+        href: general-development/what-s-new-in-business-connectivity-services-in-sharepoint.md
+      - name: Get started with Business Connectivity Services
+        href: general-development/get-started-with-business-connectivity-services-in-sharepoint.md
+        items:
+        - name: Setting up a development environment for BCS
+          href: general-development/setting-up-a-development-environment-for-bcs-in-sharepoint.md
+      - name: External content types
+        href: general-development/external-content-types-in-sharepoint.md
+        items:
+        - name: 'How to: Create external content types for SQL Server'
+          href: general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint.md
+        - name: Create associations in SharePoint
+          href: general-development/create-associations-in-sharepoint.md
+        - name: Add-in-scoped external content types
+          href: general-development/add-in-scoped-external-content-types-in-sharepoint.md
+          items:
+          - name: 'How to: Create an add-in-scoped external content type'
+            href: general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint.md
+          - name: 'How to: Convert an add-in-scoped external content type to tenant-scoped'
+            href: general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped.md
+          - name: 'How to: Access external data using REST'
+            href: general-development/how-to-access-external-data-with-rest-in-sharepoint.md
+      - name: Using OData sources with Business Connectivity Services
+        href: general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md
+        items:
+        - name: 'How to: Create an external content type from an OData source'
+          href: general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint.md
+        - name: 'How to: Create an OData data service for use as a BCS external system'
+          href: general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system.md
+        - name: 'How to: Create an external list using an OData data source'
+          href: general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint.md
+      - name: External events and alerts
+        href: general-development/external-events-and-alerts-in-sharepoint.md
+        items:
+        - name: 'How to: Create external event receivers'
+          href: general-development/how-to-create-external-event-receivers.md
+      - name: Get started using the client object model with external data
+        href: general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint.md
+        items:
+        - name: 'How to: Use the client code library to access external data'
+          href: general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint.md
+      - name: Business Connectivity Services programmers reference
+        href: general-development/business-connectivity-services-programmers-reference-for-sharepoint.md
+        items:
+        - name: BCS REST API reference
+          href: general-development/bcs-rest-api-reference-for-sharepoint.md
+        - name: BCS client object model reference
+          href: general-development/bcs-client-object-model-reference-for-sharepoint.md
+        - name: Changes in the BDC model schema for SharePoint
+          href: general-development/changes-in-the-bdc-model-schema-for-sharepoint.md
+        - name: BDC model schema reference
+          href: general-development/bdc-model-schema-reference-for-sharepoint.md
+      - name: Create hybrid connectivity apps for SharePoint
+        href: general-development/create-hybrid-connectivity-apps-for-sharepoint.md
+      - name: Developing with Duet Enterprise 2.0
+        href: general-development/developing-with-duet-enterprise-2-0.md
+        items:
+        - name: 'How to: Use SAP workflow with Duet Enterprise 2.0'
+          href: general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0.md
+        - name: 'How to: Use SAP Reporting with Duet Enterprise 2.0'
+          href: general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0.md
+    - name: Office and SharePoint application services
+      href: general-development/office-and-sharepoint-application-services.md
+      items:
+      - name: Excel Services in SharePoint
+        href: general-development/excel-services-in-sharepoint.md
+        items:
+        - name: Getting Started with Excel Services
+          href: general-development/getting-started-with-excel-services.md
+          items:
+          - name: Excel Services Overview
+            href: general-development/excel-services-overview.md
+          - name: Excel Services Architecture
+            href: general-development/excel-services-architecture.md
+          - name: Excel Services Development Roadmap
+            href: general-development/excel-services-development-roadmap.md
+          - name: Supported and Unsupported Features
+            href: general-development/supported-and-unsupported-features.md
+          - name: Excel Services Blogs, Forums, and Resources
+            href: general-development/excel-services-blogs-forums-and-resources.md
+        - name: Excel Web Services
+          href: general-development/excel-web-services.md
+          items:
+          - name: What's New in Excel Web Services
+            href: general-development/what-s-new-in-excel-web-services.md
+          - name: Accessing the SOAP API
+            href: general-development/accessing-the-soap-api.md
+          - name: Loop-Back SOAP Calls and Direct Linking
+            href: general-development/loop-back-soap-calls-and-direct-linking.md
+          - name: 'Walkthrough: Developing a Custom Application Using Excel Web Services'
+            href: general-development/walkthrough-developing-a-custom-application-using-excel-web-services.md
+            items:
+            - name: 'Step 1: Creating the Web Service Client Project'
+              href: general-development/step-1-creating-the-web-service-client-project.md
+            - name: 'Step 2: Adding a Web Reference'
+              href: general-development/step-2-adding-a-web-reference.md
+            - name: 'Step 3: Accessing the Web Service'
+              href: general-development/step-3-accessing-the-web-service.md
+            - name: 'Step 4: Building and Testing the Application'
+              href: general-development/step-4-building-and-testing-the-application.md
+          - name: Excel Services Error Codes
+            href: general-development/excel-services-error-codes.md
+          - name: 'How to: Get Values from Ranges'
+            href: general-development/how-to-get-values-from-ranges.md
+          - name: 'How to: Set Values of Ranges'
+            href: general-development/how-to-set-values-of-ranges.md
+          - name: 'How to: Specify a Range Address and Sheet Name'
+            href: general-development/how-to-specify-a-range-address-and-sheet-name.md
+          - name: 'How to: Get an Entire Workbook or a Snapshot'
+            href: general-development/how-to-get-an-entire-workbook-or-a-snapshot.md
+          - name: 'How to: Use the CloseWorkbook Method Call Asynchronously'
+            href: general-development/how-to-use-the-closeworkbook-method-call-asynchronously.md
+          - name: 'How to: Set Various Credentials'
+            href: general-development/how-to-set-various-credentials.md
+          - name: 'How to: Refresh Data'
+            href: general-development/how-to-refresh-data.md
+          - name: 'How to: Use the SubCode Property to Capture Error Codes'
+            href: general-development/how-to-use-the-subcode-property-to-capture-error-codes.md
+        - name: Excel Services User-Defined Functions
+          href: general-development/excel-services-user-defined-functions.md
+          items:
+          - name: Understanding Excel Services UDFs
+            href: general-development/understanding-excel-services-udfs.md
+          - name: 'Walkthrough: Developing a Managed-Code UDF'
+            href: general-development/walkthrough-developing-a-managed-code-udf.md
+            items:
+            - name: 'Step 1: Creating a Project and Adding a UDF Reference'
+              href: general-development/step-1-creating-a-project-and-adding-a-udf-reference.md
+            - name: 'Step 2: Creating a Managed-Code UDF'
+              href: general-development/step-2-creating-a-managed-code-udf.md
+            - name: 'Step 3: Deploying and Enabling UDFs'
+              href: general-development/step-3-deploying-and-enabling-udfs.md
+            - name: 'Step 4: Testing and Calling UDFs from Cells'
+              href: general-development/step-4-testing-and-calling-udfs-from-cells.md
+          - name: Frequently Asked Questions About Excel Services UDFs
+            href: general-development/frequently-asked-questions-about-excel-services-udfs.md
+          - name: 'How to: Enable UDFs'
+            href: general-development/how-to-enable-udfs.md
+          - name: 'How to: Create a UDF That Calls a Web Service'
+            href: general-development/how-to-create-a-udf-that-calls-a-web-service.md
+          - name: 'How to: Access an External Data Source from a UDF'
+            href: general-development/how-to-access-an-external-data-source-from-a-udf.md
+          - name: 'How to: Deploy UDFs Using SharePoint Foundation Solutions'
+            href: general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions.md
+          - name: 'How to: Restrict UDF Code Access Security Permissions'
+            href: general-development/how-to-restrict-udf-code-access-security-permissions.md
+        - name: Excel Web Access
+          href: general-development/excel-web-access.md
+          items:
+          - name: 'How to: Programmatically Add an Excel Web Access Web Part to a Page'
+            href: general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page.md
+          - name: 'How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll'
+            href: general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc.md
+        - name: Excel Services ECMAScript (JavaScript, JScript)
+          href: general-development/excel-services-ecmascript-javascript-jscript.md
+          items:
+          - name: 'Walkthrough: Developing Using the Content Editor Web Part'
+            href: general-development/walkthrough-developing-using-the-content-editor-web-part.md
+            items:
+            - name: 'Step 1: Creating a ECMAScript Text File'
+              href: general-development/step-1-creating-a-ecmascript-text-file.md
+            - name: 'Step 2: Adding the Content Editor and Excel Services Web Parts'
+              href: general-development/step-2-adding-the-content-editor-and-excel-services-web-parts.md
+          - name: Excel Services ECMAScript Overview
+            href: general-development/excel-services-ecmascript-overview.md
+          - name: JavaScript user-defined functions overview
+            href: general-development/javascript-user-defined-functions-overview.md
+          - name: Working with the Excel Services JavaScript object model
+            href: general-development/working-with-the-excel-services-javascript-object-model.md
+          - name: 'How to: Create a mashup that uses an embedded workbook and Bing Maps'
+            href: general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps.md
+        - name: Excel Services REST API
+          href: general-development/excel-services-rest-api.md
+          items:
+          - name: Excel Services REST API Overview
+            href: general-development/excel-services-rest-api-overview.md
+          - name: Basic URI Structure and Path
+            href: general-development/basic-uri-structure-and-path.md
+          - name: Discovery in Excel Services REST API
+            href: general-development/discovery-in-excel-services-rest-api.md
+          - name: Resources URI for Excel Services REST API
+            href: general-development/resources-uri-for-excel-services-rest-api.md
+          - name: Getting Ranges Using Atom Feed and HTML Fragment
+            href: general-development/getting-ranges-using-atom-feed-and-html-fragment.md
+          - name: Sample URI For Excel Services REST API
+            href: general-development/sample-uri-for-excel-services-rest-api.md
+          - name: Accessing a Schema
+            href: general-development/accessing-a-schema.md
+          - name: Unsupported Features in Excel Services REST API
+            href: general-development/unsupported-features-in-excel-services-rest-api.md
+          - name: Advanced Scenarios and Additional Samples
+            href: general-development/advanced-scenarios-and-additional-samples.md
+          - name: Using OData with Excel Services REST in SharePoint
+            href: general-development/using-odata-with-excel-services-rest-in-sharepoint.md
+          - name: Requesting Excel workbook data from SharePoint Server using OData
+            href: general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata.md
+        - name: General Guidelines
+          href: general-development/general-guidelines.md
+          items:
+          - name: Excel Services Alerts
+            href: general-development/excel-services-alerts.md
+          - name: Excel Services Known Issues and Tips
+            href: general-development/excel-services-known-issues-and-tips.md
+          - name: Excel Services Best Practices
+            href: general-development/excel-services-best-practices.md
+          - name: 'How to: Trust a Location'
+            href: general-development/how-to-trust-a-location.md
+          - name: 'How to: Save from Excel Client to the Server'
+            href: general-development/how-to-save-from-excel-client-to-the-server.md
+          - name: 'How to: Save to the Server to Prepare for Programmatic Access'
+            href: general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access.md
+          - name: 'How to: Catch Exceptions'
+            href: general-development/how-to-catch-exceptions.md
+        - name: Removing Excel Interactive View from a webpage
+          href: general-development/removing-excel-interactive-view-from-a-webpage.md
+      - name: Machine Translation Services in SharePoint
+        href: general-development/machine-translation-services-in-sharepoint.md
+      - name: PerformancePoint Services in SharePoint
+        href: general-development/performancepoint-services-in-sharepoint.md
+        items:
+        - name: 'How to: Create report renderers for PerformancePoint Services'
+          href: general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint.md
+        - name: 'How to: Create report editors for PerformancePoint Services'
+          href: general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint.md
+        - name: 'How to: Create filter data providers for PerformancePoint Services'
+          href: general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint.md
+        - name: 'How to: Create filter editors for PerformancePoint Services'
+          href: general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint.md
+        - name: 'How to: Create tabular data source providers for PerformancePoint Services'
+          href: general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha.md
+        - name: 'How to: Create tabular data source editors#for PerformancePoint Services'
+          href: general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share.md
+        - name: 'How to: Create scorecard transforms for PerformancePoint Services'
+          href: general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2.md
+      - name: PowerPoint Automation Services in SharePoint
+        href: general-development/powerpoint-automation-services-in-sharepoint.md
+      - name: Develop Access web apps
+        href: general-development/develop-access-web-apps.md
+        items:
+        - name: What's new in Access
+          href: general-development/what-s-new-in-access.md
+      - name: Visio Services in SharePoint
+        href: general-development/visio-services-in-sharepoint.md
+      - name: What's new in Word Automation Services for developers
+        href: general-development/what-s-new-in-word-automation-services-for-developers.md
+      - name: Extend the fixed-format export feature in Word Automation Services
+        href: general-development/extend-the-fixed-format-export-feature-in-word-automation-services.md
+    - name: Authentication, authorization, and security in SharePoint
+      href: general-development/authentication-authorization-and-security-in-sharepoint.md
+      items:
+      - name: Authorization, users, groups, and the object model in SharePoint
+        href: general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md
+      - name: Role, inheritance, elevation of privilege, and password changes in SharePoint
+        href: general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint.md
+      - name: Claims-based identity in SharePoint
+        href: general-development/claims-based-identity-in-sharepoint.md
+        items:
+        - name: 'Incoming claims: Signing into SharePoint'
+          href: general-development/incoming-claims-signing-into-sharepoint.md
+        - name: Claims provider in SharePoint
+          href: general-development/claims-provider-in-sharepoint.md
+        - name: 'How to: Create a claims provider in SharePoint'
+          href: general-development/how-to-create-a-claims-provider-in-sharepoint.md
+        - name: 'How to: Deploy a claims provider in SharePoint'
+          href: general-development/how-to-deploy-a-claims-provider-in-sharepoint.md
+      - name: Claims-based identity and concepts in SharePoint
+        href: general-development/claims-based-identity-and-concepts-in-sharepoint.md
+        items:
+        - name: Sample delegation, federation, and authentication scenario in SharePoint
+          href: general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint.md
+        - name: Claims-based identity term definitions
+          href: general-development/claims-based-identity-term-definitions.md
+      - name: Configuration, administration, and resources in SharePoint
+        href: general-development/configuration-administration-and-resources-in-sharepoint.md
+    - name: eDiscovery
+      href: general-development/ediscovery-in-sharepoint.md
+      items:
+      - name: What's new in SharePoint eDiscovery and compliance
+        href: general-development/what-s-new-in-sharepoint-ediscovery-and-compliance.md
+    - name: CMIS in SharePoint
+      href: general-development/content-management-interoperability-services-cmis-in-sharepoint.md
+    - name: The XLIFF interchange file format in SharePoint
+      href: general-development/the-xliff-interchange-file-format-in-sharepoint.md
+  - name: Create SharePoint no-code solutions
+    href: general-development/create-sharepoint-no-code-solutions.md
+    items:
+    - name: SharePoint Composites Handbook
+      href: general-development/sharepoint-composites-handbook.md
+    - name: Save, download, and upload a SharePoint site as a template
+      href: general-development/save-download-and-upload-a-sharepoint-site-as-a-template.md
+  - name: Upgrade site customizations
+    href: general-development/upgrade-site-customizations-for-sharepoint.md
+    items:
+    - name: Upgrade web templates
+      href: general-development/upgrade-web-templates-for-sharepoint.md
+    - name: Use Feature upgrade to apply new SharePoint master pages when upgrading from SharePoint 2010
+      href: general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md
+  - name: Set up a general development environment for SharePoint
+    href: general-development/set-up-a-general-development-environment-for-sharepoint.md
+  - name: How-tos for SharePoint
+    href: general-development/how-tos-for-sharepoint.md
+  - name: Code samples for SharePoint
+    href: general-development/code-samples-for-sharepoint.md
+  - name: Choose the right API set in SharePoint
+    href: general-development/choose-the-right-api-set-in-sharepoint.md
+  - name: Set up and configure SharePoint Workflow Manager
+    href: general-development/set-up-and-configure-sharepoint-workflow-manager.md
+  - name: SharePoint Server Application Lifecycle Management
+    href: general-development/sharepoint-server-application-lifecycle-management.md
+  - name: Accessibility in SharePoint
+    href: general-development/accessibility-in-sharepoint.md
+  - name: 'How to: Detect the installed SKU of SharePoint'
+    href: general-development/how-to-detect-the-installed-sku-of-sharepoint.md
+  - name: 'How to: Avoid getting throttled or blocked in SharePoint Online'
+    href: general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md
+  - name: Overview of SharePoint and the Volume Shadow Copy Service
+    href: general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service.md
+    items:
+    - name: SharePoint VSS Writer
+      href: general-development/sharepoint-vss-writer.md
+    - name: VSS requestors and SharePoint
+      href: general-development/vss-requestors-and-sharepoint.md
+    - name: 'How to: Create a VSS requestor for use with SharePoint'
+      href: general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint.md
+    - name: 'How to: Back up and restore SharePoint using a VSS requestor'
+      href: general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md
+    - name: 'How to: Back up and restore a search service application in SharePoint using VSS'
+      href: general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md
+- name: SharePoint Add-ins
+  href: sp-add-ins/sharepoint-add-ins.md
+  items:
+  - name: New name for apps for SharePoint
+    href: sp-add-ins/new-name-for-apps-for-sharepoint.md
+  - name: Get started creating SharePoint-hosted SharePoint Add-ins
+    href: sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins.md
+    items:
+    - name: 1. Deploy and install a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in.md
+    - name: 2. Add custom columns to a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in.md
+    - name: 3. Add a custom content type to a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in.md
+    - name: 4. Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md
+    - name: 5. Add a workflow to a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in.md
+    - name: 6. Add a custom page and style to a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in.md
+    - name: 7. Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in
+      href: sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in.md
+    - name: 8. Create a custom ribbon button in the host web of a SharePoint Add-in
+      href: sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in.md
+    - name: 9. Use the SharePoint JavaScript APIs to work with SharePoint data
+      href: sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data.md
+    - name: 10. Work with host web data from JavaScript in the add-in web
+      href: sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web.md
+  - name: Get started creating provider-hosted SharePoint Add-ins
+    href: sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md
+    items:
+    - name: 1. Give your provider-hosted add-in the SharePoint look-and-feel
+      href: sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel.md
+    - name: 2. Include a custom button in the provider-hosted add-in
+      href: sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in.md
+    - name: 3. Get a quick overview of the SharePoint object model
+      href: sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model.md
+    - name: 4. Add SharePoint write operations to the provider-hosted add-in
+      href: sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in.md
+    - name: 5. Include an add-in part in the provider-hosted add-in
+      href: sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in.md
+    - name: 6. Handle add-in events in the provider-hosted add-in
+      href: sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in.md
+    - name: 7. Add first-run logic to the provider-hosted add-in
+      href: sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in.md
+    - name: 8. Programmatically deploy a custom button in the provider-hosted add-in
+      href: sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in.md
+    - name: 9. Handle list item events in the provider-hosted add-in
+      href: sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in.md
+  - name: Design
+    href: sp-add-ins/design-sharepoint-add-ins.md
+    items:
+    - name: Three ways to think about design options for SharePoint Add-ins
+      href: sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins.md
+    - name: Important aspects of the SharePoint Add-in architecture and development landscape
+      href: sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap.md
+      items:
+      - name: Choose patterns for developing and hosting your SharePoint Add-in
+        href: sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in.md
+      - name: Host webs, add-in webs, and SharePoint components
+        href: sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md
+    - name: Secure data access and client object models for SharePoint Add-ins
+      href: sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins.md
+    - name: UX design for SharePoint Add-ins
+      href: sp-add-ins/ux-design-for-sharepoint-add-ins.md
+      items:
+      - name: SharePoint Add-ins UX design guidelines
+        href: sp-add-ins/sharepoint-add-ins-ux-design-guidelines.md
+  - name: Develop
+    href: sp-add-ins/develop-sharepoint-add-ins.md
+    items:
+    - name: Explore the app manifest structure and the package of a SharePoint Add-in
+      href: sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md
+      items:
+      - name: URL strings and tokens in SharePoint Add-ins
+        href: sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins.md
+    - name: SharePoint .NET Server, CSOM, JSOM, and REST API index
+      href: sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index.md
+    - name: Complete basic operations using SharePoint client library code
+      href: sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md
+    - name: Complete basic operations using JavaScript library code in SharePoint
+      href: sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md
+    - name: Get to know the SharePoint REST service
+      href: sp-add-ins/get-to-know-the-sharepoint-rest-service.md
+      items:
+      - name: Complete basic operations using SharePoint REST endpoints
+        href: sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints.md
+      - name: Working with lists and list items with REST
+        href: sp-add-ins/working-with-lists-and-list-items-with-rest.md
+      - name: Working with folders and files with REST
+        href: sp-add-ins/working-with-folders-and-files-with-rest.md
+      - name: Determine SharePoint REST service endpoint URIs
+        href: sp-add-ins/determine-sharepoint-rest-service-endpoint-uris.md
+      - name: Use OData query operations in SharePoint REST requests
+        href: sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md
+      - name: Navigate the SharePoint data structure represented in the REST service
+        href: sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service.md
+      - name: Synchronize SharePoint items using the REST service
+        href: sp-add-ins/synchronize-sharepoint-items-using-the-rest-service.md
+      - name: Upload a file by using the REST API and jQuery
+        href: sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery.md
+      - name: Set custom permissions on a list by using the REST interface
+        href: sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface.md
+      - name: Make batch requests with the REST APIs
+        href: sp-add-ins/make-batch-requests-with-the-rest-apis.md
+    - name: Create UX components in SharePoint
+      href: sp-add-ins/create-ux-components-in-sharepoint.md
+      items:
+      - name: Use a SharePoint website's style sheet in add-ins
+        href: sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins.md
+      - name: Use the client chrome control in add-ins
+        href: sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins.md
+      - name: Create add-in parts to install with your SharePoint Add-in
+        href: sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md
+      - name: Create custom actions to deploy with SharePoint Add-ins
+        href: sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins.md
+      - name: Customize a list view in SharePoint Add-ins using client-side rendering
+        href: sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering.md
+      - name: Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins
+        href: sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md
+      - name: Highlight content and enhance the functionality of SharePoint-hosted SharePoint Add-ins with the callout control
+        href: sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint.md
+      - name: Include a Web Part in a webpage on the add-in web
+        href: sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md
+      - name: Office Web Widgets - Experimental overview
+        href: sp-add-ins/office-web-widgetsexperimental-overview.md
+        items:
+        - name: Use the experimental People Picker widget in SharePoint Add-ins
+          href: sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins.md
+        - name: Use the experimental Desktop List View widget in SharePoint Add-ins
+          href: sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins.md
+        - name: Office Web Widgets - Experimental License Terms
+          href: sp-add-ins/office-web-widgetsexperimental-license-terms.md
+    - name: Work with external data in SharePoint
+      href: sp-add-ins/work-with-external-data-in-sharepoint.md
+      items:
+      - name: Create a custom proxy page for the cross-domain library
+        href: sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint.md
+      - name: Query a remote service using the web proxy
+        href: sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint.md
+    - name: Handle events in SharePoint Add-ins
+      href: sp-add-ins/handle-events-in-sharepoint-add-ins.md
+      items:
+      - name: Create a remote event receiver
+        href: sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins.md
+      - name: Create an add-in event receiver
+        href: sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins.md
+      - name: Debug and troubleshoot a remote event receiver
+        href: sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in.md
+    - name: Create a provider-hosted add-in that includes a custom SharePoint list and content type
+      href: sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md
+    - name: Get user identity and properties in SharePoint
+      href: sp-add-ins/get-user-identity-and-properties-in-sharepoint.md
+    - name: Localize SharePoint Add-ins
+      href: sp-add-ins/localize-sharepoint-add-ins.md
+    - name: Authorization and authentication of SharePoint Add-ins
+      href: sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins.md
+      items:
+      - name: Add-in permissions in SharePoint
+        href: sp-add-ins/add-in-permissions-in-sharepoint.md
+      - name: Register SharePoint Add-ins
+        href: sp-add-ins/register-sharepoint-add-ins.md
+      - name: Add-in authorization policy types in SharePoint
+        href: sp-add-ins/add-in-authorization-policy-types-in-sharepoint.md
+      - name: Three authorization systems for SharePoint Add-ins
+        href: sp-add-ins/three-authorization-systems-for-sharepoint-add-ins.md
+        items:
+        - name: Creating SharePoint Add-ins that use low-trust authorization
+          href: sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization.md
+          items:
+          - name: Context Token OAuth flow for SharePoint Add-ins
+            href: sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md
+          - name: Authorization Code OAuth flow for SharePoint Add-ins
+            href: sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md
+          - name: Handle security tokens in provider-hosted low-trust SharePoint Add-ins
+            href: sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins.md
+          - name: Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site
+            href: sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on.md
+          - name: Replace an expiring client secret in a SharePoint Add-in
+            href: sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in.md
+        - name: Creating SharePoint Add-ins that use high-trust authorization
+          href: sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization.md
+          items:
+          - name: Create high-trust add-ins
+            href: sp-add-ins/create-high-trust-sharepoint-add-ins.md
+          - name: Create and use access tokens in provider-hosted high-trust SharePoint Add-ins
+            href: sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md
+          - name: Troubleshooting high-trust SharePoint Add-ins
+            href: sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins.md
+          - name: Package and publish high-trust SharePoint Add-ins
+            href: sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md
+            items:
+            - name: High-trust configuration scripts for SharePoint
+              href: sp-add-ins/high-trust-configuration-scripts-for-sharepoint.md
+        - name: Creating SharePoint Add-ins that use the cross-domain library
+          href: sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library.md
+          items:
+          - name: Access SharePoint data from add-ins using the cross-domain library
+            href: sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library.md
+          - name: Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins
+            href: sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z.md
+    - name: Create SharePoint Add-ins that can be used by anonymous users
+      href: sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users.md
+    - name: Convert an autohosted SharePoint Add-in to a provider-hosted add-in
+      href: sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md
+    - name: Create SharePoint Add-ins for the SAP Gateway for Microsoft
+      href: sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga.md
+    - name: Create a SharePoint Add-in that contains a document template and a task pane add-in
+      href: sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add.md
+  - name: Publish
+    href: sp-add-ins/publish-sharepoint-add-ins.md
+    items:
+    - name: 'Deploying and installing SharePoint Add-ins: methods and options'
+      href: sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options.md
+    - name: Tenancies and deployment scopes for SharePoint Add-ins
+      href: sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins.md
+    - name: SharePoint Add-ins update process
+      href: sp-add-ins/sharepoint-add-ins-update-process.md
+      items:
+      - name: Update SharePoint Add-ins
+        href: sp-add-ins/update-sharepoint-add-ins.md
+        items:
+        - name: Update add-in web components in SharePoint
+          href: sp-add-ins/update-add-in-web-components-in-sharepoint.md
+        - name: Update host web components in SharePoint
+          href: sp-add-ins/update-host-web-components-in-sharepoint.md
+        - name: Update remote components in SharePoint Add-ins
+          href: sp-add-ins/update-remote-components-in-sharepoint-add-ins.md
+        - name: Create a handler for the update event in SharePoint Add-ins
+          href: sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins.md
+    - name: Publish SharePoint Add-ins by using Visual Studio
+      href: sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio.md
+  - name: Tools
+    href: sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins.md
+    items:
+    - name: Set up a development environment for SharePoint Add-ins on Office 365
+      href: sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md
+    - name: Create a developer site on an existing Office 365 subscription
+      href: sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md
+    - name: Set up an on-premises development environment for add-ins
+      href: sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md
+    - name: Create SharePoint Add-ins in Visual Studio
+      href: sp-add-ins/create-sharepoint-add-ins-in-visual-studio.md
+    - name: What's new in Office Developer Tools for Visual Studio 2013
+      href: sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio.md
+  - name: Create cloud business add-ins
+    href: sp-add-ins/create-cloud-business-add-ins.md
+    items:
+    - name: Start
+      href: sp-add-ins/get-started-developing-cloud-business-add-ins.md
+      items:
+      - name: 'Incident manager: A cloud business add-in tutorial'
+        href: sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial.md
+      - name: Create a cloud business add-in with a social newsfeed
+        href: sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed.md
+    - name: Develop
+      href: sp-add-ins/develop-cloud-business-add-ins.md
+      items:
+      - name: Create a cloud business add-in
+        href: sp-add-ins/create-a-cloud-business-add-in.md
+      - name: Associate a document library with an entity
+        href: sp-add-ins/associate-a-document-library-with-an-entity.md
+        items:
+        - name: Troubleshooting document libraries
+          href: sp-add-ins/troubleshooting-document-libraries.md
+      - name: Enable a newsfeed for a cloud business add-in
+        href: sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in.md
+      - name: Provide a template for a document library in a cloud business add-in
+        href: sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in.md
+      - name: Create a cloud business add-in that uses the SAP Gateway
+        href: sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway.md
+    - name: Publish
+      href: sp-add-ins/publish-cloud-business-add-ins.md
+      items:
+      - name: Publish a cloud business add-in to SharePoint
+        href: sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint.md
diff --git a/general-development/docfx.json b/general-development/docfx.json
new file mode 100644
index 0000000000..45b7c43bec
--- /dev/null
+++ b/general-development/docfx.json
@@ -0,0 +1,37 @@
+{
+  "build": {
+    "content": [
+      {
+        "files": [
+          "**/*.md"
+        ],
+        "exclude": [
+          "**/obj/**",
+          "**/includes/**",
+          "README.md",
+          "LICENSE",
+          "LICENSE-CODE",
+          "ThirdPartyNotices"
+        ]
+      }
+    ],
+    "resource": [
+      {
+        "files": [
+          "**/*.png",
+          "**/*.jpg"
+        ],
+        "exclude": [
+          "**/obj/**",
+          "**/includes/**"
+        ]
+      }
+    ],
+    "overwrite": [],
+    "externalReference": [],
+    "globalMetadata": {},
+    "fileMetadata": {},
+    "template": [],
+    "dest": "sharepoint-developer"
+  }
+}
\ No newline at end of file
diff --git a/images/spfx-fp2-youtube-video.png b/images/spfx-fp2-youtube-video.png
deleted file mode 100644
index 655f061ed4999152d5cc552b390f99a68f36abfb..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 65307
zcmXt;Q;;T2+pXKSIjw2iw%z?q+qP}nwr$(Cd)l^b?|Hu+|3PL|T)8sqATuIY#l6B6
z<iz1&aA1IdfZ!!1L;yfQz%>8f%b_6t_3^Gi75^U4b`t82KtKpX|25!bY6RSW5YkCf
zRupm%8V-g7nsu9R^nXZH%}LPN$;{RPsJv!M;va%@`iDe}9St4K?VQYQZGcdriAer&
znE$x2t)07rxv7~GP!-}7*FTEzKk8tt|DTl5$=uo)i1h^#`rioje<OcvO`Kfy9gKmr
z?SB4~!~Sn^b4Nof{eMyipw_;o*nb%6Kdh?nU}J7$3e<;t9Quzz{{Q*T4u-}+Pd|Yd
z|0ff+wYE04aRPdtO6mQ_ApVmnnLAk-1C?DbkOKh`0!fMpD!FA%b-T7{i@V?aq&F<D
zUp*GsNVXVHrc`dyZm7{=SuwCd7}P<N3c$2$`9Mq3^(vtd7TNh9qG*61u%;OphT*nN
zv`Nr4ShbhAo=I?duPhyZGg{tsKl6QzH4wR9^UP9uUQymO-FWS|Zl{wTSE(5j8-_&#
z5g`lR?qEcv-<|f>KdNF^8D(dTVu6-dU}ZcZ2|39<M&z^3s>WC+{5DxOYN&P&c2gE*
zSuAEYn{-@WxQI3YLe?}dz>>$sKr|WWTxdB^gdyaLN)lUZG$z48PNXQg3%(+b_rNiX
zI*n^m7dvSuHX#@)Y5x2CdG5VxRq6rRoucF6++XCAo`M|p)jQ8lrfeIJb2;*jO#H^b
zh4AEJy==H#BX^G~L<mP%?+Xsr6I;XSPD~OO-6Z<G(kff&RAP+B`cZLp6EDPdt(e4N
zxlWRj=>*VZpP_g(JJAZQ;+9}z{!th9-Xt*hi+ncc)2zg|wp@T<GI@R@UH=9V!oKGe
zwDrYwhp$gZE+&%oWV_l`$%UJKZ}oS)ujDK@15w3|OY`ud{7l5J_{+&cZqXUU3@qIQ
ztfFb=Yggp*g+3VNlBSHs=-5>fQi0Ym4;F30hLqT3ZuLPnqGw?Cj7LjYS|q`jDYmmz
z!OCJrtb{7^(@80ZD~1DhteUWwjPip?bYHvRA};k3;U1ArpbH%cclG0haHTtmu+vR;
zZ$@6hKop!6ctXLzNUScUi4l;pmI$(ma1`-dcacaaThLj{=sYssoVGMR(TuH90(v<d
zIRm?4g+CI4uyumf5ZX#|{d2RuHtO_K%jqx=f1y;`l2FE@y{0h!i{`@qoJKW`Yy%C1
zGJ!*gFzPCrLvEc-u9+3YC{T`ch!p%th&UOXlt@6rKM94lNC+#Ku~yOXjTMqP5b)Cx
z{7w%><7U18%~kO#<?fV&DUOhRdRjSMXxQT-M1dMV+tH>Wj5g2Z4RETo23cFuY}pNv
zD3^y1NkVZcIW@PdG*wcC5S=^`%Q*fV`i)x7TLfI6T^_04SFEn2?R@_Db;+gV;cp9~
z%zc`cexdBCj*qR9kXeU#0Yr@gkz@l(Brt(Sh%KxInYD_va*@k26@|kpfRu#9Rtuqt
z8pI_4Ti##Brae-0kB*Ovbk2tSXGP7lOsSTvNR=$!LhoVS;oTOoRusJ|RM$BFRoUXB
zLi1S}&83J7+Yqv`l2w}%v0BOSNY<b!$s90MD(EaD<ugB`G$q5AkkbRNSC`(}Kr9j=
zk&(hb{bSmSI#VTx(rXw{qD1!8?zo8!V?qM1CW8r;ge0k1gz?=mHF9iyUZ(leq1~NR
z>;UhOY+*_H8=kq^><Tr?SjFBdZed>nZ<Kba7PJb<&uV=R7mF}68A+%h9wkcZRFjt=
zkb!Y%TDjH`9H-ZGQ7{HgV{s~smQ@UjyUkQHecg0ev7AesQ8qfgSV~-C<JF?2AvP!P
zr?uF-nTcRn#Da_)#Q-{t<UXe$Zk~daL8u!b*fbNiyuY3v!024E6ty(dAVX!NeIq@}
zWDPf|KoHRgq=M@xvC(f*E06n_W^ygw4Gl~Pj`ATqASVJKN6iGIflF)aN5Z{tna)%R
zNtRHBOu%4+1dON5jucUZ$S^Bf^0JGu8LWhcXVrHsA=j-1lBFk7CfBV^+2b)QDNNmr
zv%D&Y(wKg}T)>DyJx6`urNuBvT-E?W7r22`BDv-n@$mI1ivij3`>)xkc%n6p!yFlc
zoSy5t<(ulLuGiM_I3(h94LLoIzym<`V*;t-uFJxiP>v#%E*Z2_MmVy!<$)sHYR)F`
z1y_N37$j}xGyWv&AsQi)-nG@)E={E7KXl+~_EvSr7V|JVk}K&-8tF#MW^Y5spn66Y
z3%JRLn!d|0z2<c&@W))JRX8Y-MK$4G4T1T8p!%cWyJIZnyV);j=JjN<R+qu0s91!6
zVJxHNxwzOKkMQI)7h*{=(3-u2-<v~=P>2E&eB-nWje{0w@fWH3E%jZ*iNu5|jVCL1
z+?{jPO~{Q8C31a}o6ekS^EXGJF7w`<q&DK?rvWt*8-R5oD+Q^AKV$ptI0G{YEw`EP
zUe`vaaw^V-mpy)xe=C|c#4Iaj^8P?pxtJuycn{g<g3tgDrI~2V8==t_vu7-S8-gKe
zZp1PkqpPXl7FU|8y3$His#4-u*iW%3AO!{KuPVeAD{;gu0!4KIcmJtvvK!|r!;QbD
z`;gJ-v(T@K=D7M)BimUqW`kF6zG25!S(yG?{USu!q;#5;PZM)M1_2X)THAQGIsKfa
zI4cJ?hxI8HEYQJ$4M~J9B&E3~7T8RlG`;?zTo$A-=5H1IavlIY(AE<Godht0Ua|-u
z!!+u2zy~<J=OQr8CegAn>Z7#|DM}Rt6&Vgf1M3SEYl#{)7->f{HrCCJ_?gkN$B<Z_
z$bnN@^Iq65ih+E5NCdV7Mm2&N67#4oX3yp&fjw4f_!b5stU(h&Q5jd{6Q)iQiY7{?
zwU}7q7lNRID^c;qqzX=^NwM}#8rv6{RXSU0o9sn7Q~o(m$&Z0Ge+y<%qDGH$7&Gn?
z%Y*@Lwg@LgF?vwPO9X64Jc)kTNvJ%yJT-%(ihAPthZ{y5!FYFX!9618H4O}fNEJ_Q
zdw(DS_T6<VW>E>Hs<nwpRU4-lt9toj`i2;#$}!wcG+A)qiO<EnHA9whqLuVmh=Hj=
zF(8`)7jR1D<f8@6qpNDs^5tn^>^Eg#2+kA5*tjZYVnjM2626f}lcJ68ic{^quCRZt
zGK47L5V4A#BLwzdIZm72m7m;)+Nw>t_Bi9p<2eYF9{eJ`KtU-$B0fDIUre13@}J!^
zhz76@RyfuiSNxIoI_|U#Pkx~Cax_64!Q!btn}lsjkbqOfW8_mGR)tZm#NHqEkJYiG
z$?e#)%IUhXxpu3GI^nc-u6I|BKp%5E#M?@1h7cZ^Kg0`Hk!64xz)5Uwf??o3#rsN_
z^M4&>+;R`?35YDb1aWuLP6Dz`Fh&A%s@0m#3>kGhoIfcSaW?|ov?1)mN6A|M5(O?E
z5US~TheP0dk#0%FxLcOSxV`LtsV7Nj1GFR=HX<{JCIF!ZD_Qc%u|<+(P^sXR{;dmn
zL~ho=#O(Q&g~Rj731zb)nel*DlZ@ehf>D8!xjW5xLSt4}0_cE(oz2Nz`7Kk`f7RMd
zN*O_eOqS`m-ckK)qBLp@1hWre1!3i9lx#d7c)e{uzz9)Mag#@y_h!fHwwrQMEK9c_
z1r!A;k^fXtsb^+gwulA5YO<K9;unAE^gB4rk)#gHqN)38Qz&UP`ZsEOLuB0HbWO&_
zm}YtGxMRCnBBl-%2arNS#?+|J+i*~WUm4A+<FI7VkV)pHP{ffHt)3jKS@o;1_^z~6
z<gEAhP7p|vi4lmyz$L(AS_E){py@_h;+r7Kk)?>5TRc3`$lv|6&lGT)ls&_Vp$gE*
zm3PaG7_g8KRJYwgeScb*^8loo@jQ<Y8?URX>~%(GoSR-pg5SrumQYPXRKX_{L4Fi)
zcY_?rk_Q%|cx$G53_=O^EMzfd;K&emc%gNG{f5@A9AB>;^dy8|!~)E7xhLtlJCg+7
zU&zmyGz%iM?w02LTISISIDvUMI7NOGY*6KM0Hn+?YSmoPx8P|WKIC0vJO+horM5Fy
zpTyW&zMMfr)FFw6oJm7O-^iVxV;5o?O~v(oWrZhUgFtO(ZR@o<0u)$(Nj%`@LLwMw
zLr}ne2MR418Pnf@xG}#Zl-YR^#bB?ILh4LGQQ-V=D{Y1#eK4W?WWp$+g0TuxDa+19
zv<-iHzd6KlJXfyD6x)L{=UIhl^brw?VtWm>79zO8A=7ya_~9BNm70z?*+Sga7WG{Y
z1Px9zeavWv7DIV+NK$xvG!#+7y7LUBmY#uW`}Ocij?aZj8IE5u36!FgWN<<S9=MdD
z64ZF&`S{Vx5fU)_9C-j2EWTqIm28HAMnpbQQEDSJ6fuY(nK2=ld@~DaT0PdlUo8-*
z8}<%^8`~4-(z>RsrC^(d6a}4?nUnOrQHk<=;hH^f)-KnZqI9XvUpoO3E;;N#oXR%b
zNN+u}!I)WyBe$o9v42jf2-h)!#FpU?dbBxk7nPurq_9#XfKvqhqT&I>&0^4VQu$qY
zTRF3TUOxSvK6sC_9e&yNT$8;n(^hex9)MD<4C>AF*UHqp76dJ_itv+C<qJYZ&m4`P
zr<ISJ+dVv@GlkVjnOmTU_?KxEpW`Mef$59<Z0ch?o|LPUtabUK?9+UKZn-fH+&MUP
zB745XGU}*YZneboe=LZVP-jea@j;X$b#lHlN6gPNK4V@0rS7eYcDsQ^$wN|HHTn`0
zvcXiaV&phb>bl*m@!TfY-qX*fU~!nE?|i&|tak1_@UZjEn9ZARZ*sytnxto>8O$2N
ziBQnbQjQ+pL9Kb}1qd&N)ok;?@<LNI$PGPzp}uzXjYoEjq0~9<aD;xQ3E8r59YDVR
zE$ta!<Qgm>Eqw@%)gB!cYq^gnxFKQZ=rb4QOoCqZ)Jqub0WE}lz3kl*RDeA_KQk;t
zQVhpGMq?Q+r*x4O$?_U7_`W;1F@D6|+1qlpJybAL&k~$l<oCn!j^Y3M?2Z!YHe!*H
zlV$qL9@>RjxCJNZo?&eWEPVpc7>6z+FI)eh03SbDXD0`Y9E8^47*;n@16s)OC5*Rt
zp+G0sXxb!}hb9R2aDu>8nwN${VEAA*)RnI<mu9N~AS{-yt%RB|t{5QNSPBlDJye2D
zKQpM?B{Iz2SBhs?Hlr73s}DC~Mqnyas0o6CBSLTtc@L`;r4lq4WMow4|Gl^*Pec;_
ziSp+_ISE;5QaR}FUotkwldTP8ib_Q{@DP|^VCZC}CD4U%YcdFe0#!_CTEgxg5eYYS
zMsMX^5AW1!FU|ChvwP-Ibv58nfdqb;7sb>kdY?>*e@J;&Ouy)TW0)969K(Wy<#h?v
z@$<_SD*hsApok#XB%0>&N5WA>$z$~20k|#9n_nazo6NbHM-(d1+CLkXv|QFKEShn0
zF79`~5F1@@__m*FaG?X^9NMQg+a25AN?h;hb-$^O0NA7U8dBzIE$bo-lpAHNg4h#F
zRBKi#u3cZ&uY!GxvsI;?of{oAzb%XwyMGVQicD0>{4T*JQl=hc0uhOd!>MM`z%nRS
z1R#YfQynRmOoAiueFJU5@{e(*X3cE<xDd1-Vcz+(Yx|W!9Cm`(e5KOg{Vu%^Wrw%B
zVE5_c;~i37*_pb%&b`fU=G^ue)Kp7K+@(UO>J8N-*tP&qO3<J^e3Y&^oV4wU(`uH=
z-#CaN_~iDzP0sFmA?cm|@$$yxc1=p-_DwshwrsyX_>sD4w>^A*$)5e#d7zBA@kMma
z*%>SeH1>E8y&GY_&-C?zm5*|MnCE{Z^mQ5s;ubGCyUrOre73!R@AXPbI0I+lee((7
zb+cLIW3$N!sdjz%cw^db3p|fZZ#@*Td5d(1dwGd3zutTKd9SRxlRt#@b>hWD#Ica`
zUnnVc|0uOF{#LI&(CmE?V`|0;ZQ&d8<om%|@jd<8?BbD@2#Lqc*&UJp3X?LrEseC=
z<{E%)2cf_8NV@4UMz2(*5#_zU3+C@kpZqYOqM96PF@5bb^_hy4o;@k`ZO_>F{<d|m
z`}DYepOU;><rH-7iTuSlV%qBt32Le%)5?gZk~<yjiSSTJj+l=RE@cRpRDy8-8o5CM
z5twHP1@ZQ^<BsTSzX;^RxSz@2kxD+r=yg0jNug@!VU*tcHmdphtTS!O|E4&@fQknN
zCj8~z!qW=uyNeZbc4i>gGP3ivNb99PO_8eQ%KGDUkRGNHL_P90>Dv~(*}igr=V;+|
zHp!oVlV$lj=RDbVft!2q9p2t`v(+nD_l)~#w&At?5mT97X@SK)`no*&`hA5s*SIgW
z?fhhsl{YbT&AO>s@$YQ^>DfP|-X3wD1o3$v<X(;Ub8N<7{Ar48-)mrIOvcfXtNZTJ
zZ1)aD#1i5+F&j7bdet6vJmL3FHua1>$hP$cjco8cX}CD!ew~?hsdHHBbRQ&DN4TtA
z*jSNvyH)r39*WGedp{eJNYQbk8${%tI5qNHj>sTb=sdKtX?y2!&=)A79(^voKHm6g
zkHz&l>4vlZ;neN)1f{lh<6g<)${nAFb{HHC+IU6<BiimlbsOENHR!?3Z<;(Nzdnr7
zwGlF6qBLNN)aNj6K~poK@zbatxy{n2>p3Ofrx+Mwj9I?iXpNQCWGgKCErpgSRXk7-
z49od)+1U2e4~e{xoo}$rUb;}cB1jGcV$l<O;-2MvjE&dnL@6b;?Y-DJr_s3AesXqw
z-E!_}6<rSBk}~lptOQwyG8#>4@l2dD`hX*aiW{f6>W^x@$ttU&;lVSpJg<FPgu~n0
zGKi{{3z4PoCo7%T#?S8H4sRd)jT<wG=1PO`l<8UB5axs0GQr*FyW~vgqXk67?0xd=
z55Df_H|iAk0ZfeUrtog43of%S-p_$`YU9&3!QBX=cSh#V7xwnswX4I{oi<jsAi?Iu
zDF2<S*7J{d=6b`!+fS{U99bDrvJgnj#on;t=XB{eqV4OV@4;=?qWj63I|O}uTCDc=
zG&$c_ulogoPdLFP?R=s$5+J|<i8EC;bNSvCG4?Js_k-H!y*$%xCHbNKhW}=tKZif;
zlr9ds^z~h}XX4`L^P?+Gec}m|Kz`*eax98xxS8M!t&;!Vdh^fBUaNdoAe=sf=241f
z&j@_3PgrA(FYXOK*ATbQOKsaONo$_G?(pbLE~20S-sr0jJQb05B&OY-SFHBO#OE>h
z_P_;GXWN^vcg)Jqa4bcR9dK^PGl!B=BaIqXkrQPba;xvlPW!RE&EEEe*0$F%L+<xN
zbr*-C!SsvI48DBK?r|ejv7mVYM*%}ySgV!;My;+lm2Hn1_LerznMpXg%iZ43Q>@o_
zy15Fi^Xn+Rm%lRm7ig=^AFo5%llmdVu|wXLo>!!s*Hiwx($=0abk(Z;H&35FT;G$*
z&6cgb5Lmgrq5h-KX<1XpkCpHAhwU#)zL%!S+@23&gqy7p94v!*FUi>g!_#YgBR4&0
z$1acuCgm2J$M*dSb|!{ye_QV_ORq0T#CXj+E|pp=!WaV>o#;}ZJNzE+(LZQ|G-L}|
zPUD(wCZZ{<u0K)ui6K^GfeCpqqxT_`vxbM`+^_4sKH0f^Yy;^h+EbrZEjp`G#K9tz
zfdnr0XXv(ho|lq*KZv=<jyu|u3lH0U_j|vH@tS<YLTx`(`CbTKkZ1S<+pmASZh7(-
z@1tGZbmR&j7zb!11M0^_ia5U$q_OF0jv{{^)qB1ZOUGu_2R^GHg^(bTg<<J;E0Q1F
zFI#Hwd~MpZo9X2bxDr+=?ao+L=Q|&WzONT^k9B=+Daf^)NU0%N>f<<KM(i(bat_G&
zV{E=pjjk;qtMQu}jsq!T)P43HARr;22IeM!-O_1-z4~VYLpZgOf{049U8vr)fGJsH
z4)!_dG`QidP9F{Tv5Hw!t2Bmhd`<(sZoh6$rkH2*l;{pTe%*B3v8%a{oc%jSqw}Y~
zvoF>^t2c3~S*55y3X8nSPzpUkvt$cUsIo;EL^R0X4W}l#5glh612o3<=gWZ=X^q}r
zgK5$d$sH%&KA%Qs@@&lzz8>I63Q<4rgNaYzri(8T6S7yQq}LB7h69Zv9otXOTM364
z)Y&69mQ0<`7{u^9gNV9Q<@vrTKFA#}ecj;s-=ZDe21U25Fj!rBn{rKCmne>Nk6>qG
z?&ljJPCa-Cq2R@+ismlY->_b;ei5CY@AV6ldNhVqrp)Fy?15i<7?DGs9-U+&*k3sW
zTZ2N&h3MS_{oIbzKU^kb+Fezke_rKk4H5LbLb3ba`xK1TInDz2ya3|M*rr=jrJbB#
z>~{B9y+~Rk5Vt;Yu?$b|^JdjTxSZYCEpvSRvkOP<pX*`mnGL;8v)Pdj9pH?ZX*h`{
z3;zIbCm4Ue>Gs418map%*iUiZvJmL94~Oz|g^DlN?9FdMbkTlJ{&S(BjVbXPJVHn#
zSbKR*hqq%;J03O(gQ34Q*<|YT_-$Q*!P6v=U?5e^J0YY*(LxSG<&Il-=H-i+$M%2e
zY~C{vBe=Uf{PMX6U^i^M?O%nw=s2MJdTYclrg*gBqHh6ELX=&sHzsoGQ94JS8%;lc
z<#@UALzckP<F5`=4(M-Fjy4o&I$Uz5-nWvE(D1U!`?}D1Z!9}7T$<R;!(hNIyWO@U
zLtxSx^xz4|+UQIB{5qMLzFip9#Cl<!&!?^0>WOGfrPm*Hku-Lo|9HO2!*fau2Xzp}
zbT~knUUc<}BzOILihn7dmd1e57Ma47SL$wb0mYFKFN^5-;ZNg#Eg9oWQG}94NO+z(
zIN-k3wiwy=C~G_X6k@-H2kW@?7izWBm0xqzyI|aW1o0h;-IBc$Y)D_mWE@+|Wx{|5
zxzYAw@zVEOoeDFje`9BRbmofQ?gEjWSwE!!9Bd%}rENGY9G|DrGh&sVfl=i*6%>yx
zk@T_Cfl{j7bo1BgHW42C;2bexv$}eU)=so^rEW^eZ(mL9RGH7T4j6De@jtMiBR0Nx
zqayZE2`Hn^x85Jw;f5X^o_5T1BTz|6(VypRRnPeS8r2hXeS|AoUl1v|ZXotnSD}hn
z>)P5oqt4pf?g!Cc2bn)JG1;ACM-G&jF~@R&k`<;v`fvcrCIuWBi_mc(`=~kSduU<2
z4m0cMNm2e1HT%9~8nw09taYfI$S7fiSlRks3T$fL;apzlwEA#itIeLkR$UL^Ugw6%
zMtPnAGs)eKgggKl99)fO9Qm)ci7~fm(Ht?Q<gITO46iu^iEs#FBGe;wq9oV}B9IF;
zz)N~U3mw4Si1}Y30WO|lsGe8U#z3GgPpgwU3@o4440kZVaduyZcV^b-8|j6wD@LA9
zXUaOaJDp#vJzH1FatM$(d6FK(JhrM(@s{O2&Fb~W9(%OR{Y(FfsJ}v*I0`^WDn`N7
z4q|j~R9tk3$;ohq`f>YY`xDhHkB-g9Esgdb6{U<dj+4{-#ovArpSpTZOMD?!Ar#;u
zXxX_#*bJ@?CIK%+7(|>(D?k<*0nP|=)g}SP2t$G&<Zua=h#*HcxmVqL2<q!e;CaBu
zgU`s9LUcjd<j_C=i0_G_`*~n#$5wkljd)GeX~pRntW1fVw}p3j@0J70XqFt>wKW}1
z;y=a()jM+NmLA_{d{|E2ZvBEVawI4w1#Ft*fz7o!z#DsWRA4!CFl5+(#{LzcM&TKz
zLaDVv;?%?&N{+4}fs|lXBT$niDh;Vm=4SB)_8`X}Iov6Z6$_5NBAPaI$I${?cR^JY
zo}NX8a{L}YP=QBPUko)XIF{C?MEq!oM#A$MnYzYu<(O5fxK5Nhi7H07usRJdzA>yL
z6&xX4p-i9@1;{9$j(r%c|H`sksIO{!<(lELCfRwP85tQ#N_hSqYRAhIADRLZXGR`L
zR)C`dWuWJf#M-+$;U5kcTqQ!f5vqu${z3p(4@?WLh(@wBm2KRKd`vboC%d75CQ75-
zkY<{rKKs(+Oa0GYVS9ghzq00v+zig!07lXD!iOpen_+Rlh}yMcT6KK!NAWw8G^#_8
zK&n~d>oQ3t!T}Li+%5`K$>Sys6y+$V_3q=3tg6w|>cZ73qQuG*Cz5N>gjWb^*(scI
z4IgA^+U-2u!8EBocTzq#10XNk-TvjK;@Gs3Q>QLH@6)-rSF9UQvSF2m&pmbNcDG7&
zYMX<o^fr2vDT7IfA8m5cskz^z7dcxpoH2J$@c<HS%<daPRGPz%#+l+?Ak!>gVB5<|
zhn;ntc>A<Yr#RzCJO~V$6Ia#8f3DCxLK(3d^;Qvul9Vi7UCRH&?AraBA^lIP<C*)z
z8MRTHkvaYPUtoCyufc-F*@KT<AH*9@Qv`2bIz@`|SH(d`HA(XW>fodVtZ{Q{jKs{%
zDOy+Fk#*h>nPo}5(*zQf1#sT+MH19Ulix2py&=6ncU(Et0XLR*JgdF2wx1W>pG&>9
zdy$AY`myK1fOJzfS^K?-qpB=&EUmgE#BA=+)Z8t>b`w`k>k}zY1*P?OX=Cq02{i{*
z`H-BbmS-SyWgki~091t-AO@dG%rGf12_+v)B)}augu`&v?!~)zH>Xs*e4GZGltGMC
zoZpB^$I4SW`H&u5gK|W7dp2!MakDdh*5`%Kr^}w7s&pLTc(u84EP)vVMJ}3=sUa7%
zS&%L>*Z3o!xI*oC*KMfbAa&tH)aiv_Qautj%4#Q8DMop(sKJI^F2ru%{n~Ta^wM5#
z_gq>v0h)>sJ?4Z6k-%ue$?^V^NCb(g>C(%l%>&&VOoXg{P$Jw8Z}UuYgj@(u`KX<o
zU~m43UXc-`P-ejdCA*9Q08<3uh!LX<^^(W5Fkrv<<r~Es%QNx5#Y*RM!QHMWm>%lm
z!tKi65S%|u&P0FV2c#-!eDh0YmNBa(5BA994F7aM5vF{ELoH$~f_Rqi8_F_gLkt-{
zKJY+2S?1plUw&p)rd8Mxv&7llk}_eTsNpu75_R#N7Us?ibio`>7r0WT@(iCRDZyvo
z2R1(Lfwb-$m3)=9rR#HYkrI`LN#UY9Ws(xSu1vb00$OO-bwZ?i%cYxvAyi>l{hhtb
z_4e@UD~FU+Lpoe$tJPjh?xtWnfGBZ#72lxRu4yq&eaSaT8M4}ZLXd>T8FC72r;acM
zilSeH4uIpuJ7)W}EZ)BNrGEU>x%rcAd)K>yPgWY?bvKH5KknL<8%mcgfZ<@J-WkG8
zFhf}JvBs-xqGO#kc3Yk1_J3J`ba@r|yKc?iQE{IO{LRPhqoimtnH&AXISLJ|qD1mp
zogSAJu5H)pjkn=q^p5xY&%;pu-Ovs1@4lhKl$zb#pLfL5Z04xm6Z37)AD4G}4g^|}
z0b(#Aiy#L9O1QX5Q|xY2_@9>N-+T`zzI~z3@(YVQ!p5dXt~yECX7by2f4;3|oIi&N
ze8YBd=@Tvp@|p}meLMB}O|=pP!!xE=>MMd&5;lD9C<r(nG_K!I60u?PRQ<STg}Gq-
zMJNy(5O%)qa8$m(m%Kh6eEag54hI<ddY(8huqw4+wgOLU=<XNJ9U^da-`0e)-u9?p
z`%U>|)Q`%q++z^8J9F*krJB&7vIU1Q?2HEng3u(ckVFz7+0fq-5qp#QU#^c)|6KrM
zrd8c?Fq2K2aB`;_b@B@^`3i45^tNl`>?^gqh6EoRH#roA5FWSED6R5_#F@X+Io@D^
zCqU6PUm&mS^=>9V-|#2jJ|VXUack)Jjqq|jAAy%4&_6*v(`ab-=l%j46k}~T#_jv*
zRVWp;mPV4V@b+g-&g_k3%KvtORdV5(PUN;glN(>_;G(N3v`3ey?en{M7!tPRyk3vw
zc=>C;Y@I#g+%VMa&C_r#s?&Qu-SrVgl^!tK((KAatA$57UlVwtmPczORpt4aO5^q=
z>a`m<S&oBP(#rgOPZ0w`#9DJgOza7^^3d?=Gt?6?`o`W9e7haG#-l9EozXyWe?J4N
z<=x->xlJjmL^c}(FK;JcE;kQDpIgjz$8^z>H8#A`6Z&VA><*&g)ss}6-C&EvGTn1n
zwChIL6iFi0&5GF);kp2Y;^H^~e>b7Bme}h|u;mO@t$XaGhaA!Ithn@UfZk{7J#d!;
zC6UW2Yu0qF)0G|-74^}{6*c5JOb~CFhWnc%g@!L=^q)OK9Zfs5dq1AeWK;~wbk@Yu
z%vQ$+6@sy7rW&Qw8K{7z(=+hOdcw^yyxH!)-0IC83`MY?55~MtvD}%Grth7az3z%+
zh`_1P8+4Q|>KeuAC^4_&E@m<Ke)83ya891{V@x0{v!6kU#hu9#mcx-jLzNs)vVA=o
z@s>%=2hcSb-w0yRT^<CWKOhV3Uf_K^NBzm5s&~EtJMfumpM2-MNiw9sU!U~9BbLUX
zH#n)u-aS<FULHSGmND;;pjByW=i!`?feg5*-I^(}AKv!|X`W!2y}>5Wz}ZFh^+4@q
zv?bqpAC6>5GhFEr-t6{Cs!*i4q^ooN;kZ-ae=rWO4)r3wVkqSwG*CCXE8v84YUdy`
zYC^NSJhDBwI`^UbKGZ0|5}^pb^H#_>l0IR|QXW$5n+Z(3q^CT7bY@J0U2|!ZLX%8^
zqez)Xwc=MZ<~lXduN7}sD#G%l__J>}Z7kSo@MD&KHb(Sl>9$5Qd2&299tIjpzQ%>j
z_*Ydg2D8z#NM^~t-lj_>_{ox$Nt;vd*Gz#--wf!#Z%Aj=z)64Lm5h{9jB3-I2jYiL
zg5{gkkxT2St}){5nlNXvu!|deWmqQ?)dSKvO!C;pdn@W4X$bo&wCpLc&d1|iy<DP#
zk%G-;4c9h7bd>aqjK<vU^cqG4<k=P7Bf3S$j(9L!D8&#`(nT2NGK)jgwnC|8NH~3L
z*c~4d?hk(tD7hU>fICG(tvE9*p#b9)qN$TYSMV)3-&L|2kW0&Ni;D3T8^lYrNvx1u
zV0~&NkC_o)0TlR}H6*GbbW|}p)$`TD;{c$@$r?eaH^ev41sdUJ1zYYkhdcom@fwE<
z$%(H=Fv$!M|JIrjMFmhMmklH6utlcu9a;D>BCJJ$+9w+<<!Qy{WRX#z-zmboMo7^P
zO`}t^p%~;YIE5>?8Qo($DHUowl|#$&>Gq-WDf5fKilV(H4PqS~QyAeF-BDsjf(;DM
z!x$O}k&GKLhiSwM{Hucs*W<-cdIq6ylrZ0@GoqD7W_ez7YWb{Lc=4NYtr}cu#atkX
zLr{{2BH-`y+k64{+#Iyo;Kr!sF@|@FV1a4bzgcv2dbXWxd#0ylh(Lv(7*k+GYS~?L
zX4wre*>oP1{<YxCIbo}9lCsjT{)mPqWW6*_2p@+Y3c%&lpQvB#V=@Hu*>&7TiEYhh
z4fS$(6oXl1)j3S@)HT`(60{6`^NzTn=R}alZMnubts-;3FBVpsVAK%{gi_zUsW*~H
z`~x!Uh)tiO?sEy!VzU(!mtlxGW4M<EtOae4MCL+09J_3DvTZ6>RV`^@M=Epl`XS$y
z>*~_m$Nl{tYBhVpc@fn9h~cn#H%TiaFKx&A3Ot0u6Rv=Au#(0dcVwNaI}}~3Ir1Gn
zYbSu<aCI@W%inuv>vcH88?;8p0OH?Wp-M4Y!6UTGfg>*+z%Ud`cwtc#ZZ}B0lEqJe
z4eRsyDo92$3NZI~?m}lw?%Qq0$$peT(-@t{x&X_tN6Xh08^?hSg_S`kDUpI9%`m0-
zVi-asiDC$+f!Pm>AW-iN3M+#Msk$Hx?ne|NCK>ODV1O%oXPj6vYHEguA-etYLy{a(
zjP|DmlhhDgZf;3ufU7R7jH3V+gW{>a4Ft-^W70qpMP6bUam05@5Dz0fFcY!*$}1St
znQMJ7qO0Mn$6Y~$8i2}Y(SY8k_$`wag?fRfsN~uKR?Y&Dl-ZXlZ*GBDWBAR|5=%%1
zGdOhD^n_%C7P6eHrtu_(bO1>t#7TjS90YM>rUbA-TGOmga<OY7gb_9{#8*RR)YrQb
zm(qy+Sk+TbOEKgL@8@hmo#A>H!UDs}pVQDU2xC~oFPGOTZgSR%4mcc35uhB+0hW2w
z2^IvBBH9ldgGxdfQp|dlcWJ|zSdE1LB-~w)raP`;p6$~+s%0iCMyt7SaC1uHzUj&Y
zg%lq%X>9E9SaZyTp!{8$<G>`(+ns}D$87Vp$=0k9eJ$iaHk34pt~DyFT68pJ_^>d<
zve<x&`|nCHD{65es7p;;a)oYg;VNc<Ur(Jp8pFIl1kDsw?bolX&6MSSvEO0t45!%T
z;5<daLPq^Set_s~Ka3K6G)C`<|NI<JEmQKMQ*-CibRpOc#{aNm{v{pqfxKQndRX@i
zoIdS;ps(<ZkSjBFY)#*2qZja{911$@m%8t*)qD<i{B(4Bmf&QJMmE7<+ZO9kJR;qR
zz#J~lmuYD64&>{o8Qq%IkjAOgml(^_$IdQ?+`(yC#qL+nj&IViHuOqg*E7i&qjabo
z<RJ8^u<x!8Qxka;>Q<AdD;Wk}KR>ka%k<nqs0ju-ZYbW_XHuG;lM_wPfS_79<(XQg
z7SCkbk;E$NKD=2V4NE?-l2rc^8I~bj7X}c&^c1snn2Fonrt=W!f*!2GW_w_ShX1Rz
zsJe8;#t^XrxuFAFUQ(2=+4jH#rq#zzQb?s83iSYBXww>6N{WM-jUjLm!sA>vFLz;2
zVhB{Md9*AyY08al0#SO^4y<&LF8pqJ#o=}q2GZ2hFf^j4aN2QOUtb~R9ndUmRlNma
zUKSWIO`WbPwb$YvvO-?H029ka(bO3nY4YLJk*$}qD2EaB&zZktg(4D|43CpDv#^9+
zbPU<clq(q=j9|KXd^O6*$SrIwZI!XJ_!ph+>F5G^=WN~b)STouwKz-IprK>;AO1zt
zA(Q6IEcD^nN=x5O+D&A&3_ET^4JbJ%W9V4(6C*Y<LL9J&uE~8!fWDVDMohOD7ojz9
z>X<kqr^`p-tn#!EDu=-;W+Vn78aL8@?`Swgi;6`@R-7u>^Er0HOmm#L<4J#7?eYvd
zIEE*!Ozem9pTmj2Y*3#lV_3t9<$06-B=weQ!$B5vI%;UMf!K*vZ^=t-Or6zVoDmj@
zpFJaopHEh<TC;<K6ilUVzuJauJ6UFe#WZn0I7gQ;w{#Wcdd9%jzmRGGCNc=`%M(p5
z2F*B%d>=PL?;I7<S?7sB&d7nw>a9xU9PE~n|EStvn#p$<+O+A%9(`n(OD)73$cZ;+
zyQEUI!&9NVF8CKE%j*r5s-6<)*Ed&1u-|70o<ie(mT~wD;5$ZeF$Cl3^~|si{S@<L
z5!d?=`1U1jvT@6V^59XMJJ_{=6m$wo5?3r$?J&MJ8;F|xNT6A7kTVp`J`8&dRHZr&
z%Q-DFlABpCI=r}bDp8=-&6tTbpQvhP?Xz9)3fAs?nOj^;yad9jSi&(hJTMbq+}hfT
zlP7Dblk)?Qn>N9HiD*uxE*?6&PPaEIwdt|=%jX`~gID15sxGiUR>Lw>uFTr5B}-wM
z?26Kd0?5mzNFReZ;*e3A+-!7#wdFZctI=vt+UudS@wFoN(TkHXD2@kcj{YH{{6N-G
zVcc8{4&{AkZtczO{usTCkw5rMZ8B|^Xt@a{!~lsROT01|@AA=cT^AAplg5CrGi;jZ
zF`vHU5=W!VS!WvA7XDLJ6N2Y^$+K*m-UlUV%Qu;9O0Ulq#bL7tv^X60Rmd8Y*{?Ty
z2%X><Htx<F^gDw1y#XOLn>$v@KH&<I?6weu*xpW)V|BQ{f+(g!tIi-SBg)<5L9j-{
z9d3~K7yT7pDSM^+qB`vSJ5Z>2WEGb=@DkzVSd;vnUb2Rj>yr?uK9=2egO41q4V}C-
zp9p2s#yv*mc`1s9N0VXNc;q+rfYni{;L<O#U+0s|y}g*?!{O4BCv)E}xndj{uva?Z
zdg*L^6`;zvis|^c0CN*V<|khhblz;&$!J_>--;4@&*h*-@I{#9E5G@J4iWvap~E8Q
zg5eI+$H(X2<A2IgQ$wBs@YcIaAZoIG)(w4Z(#aC#0g|RHH7VvPen_hisS?)Yg5616
zgMex{X^Bo{D%5}5wAaDu5-ops<(a!TvQ%onZvWusaKT6R@<yl?^jD?XNt=an5R}(y
zvn6zX-2DA`Ha|dbrGN183FCJ2_zDtY@>l_e<m#zi2r4Rq5pdw99s>E1UNKy?!_^Pl
zS$ZpraAuN5AujV*D{65vsn#xtcf%@Zz#bnW<b6(gT-tM@tIaULAgkVmE<uwh3cM;L
zGPItL3n1*eU95q2$)RAd(k8FEJbb4$V#$bTg;$KDf_;8rP_}Z=)=oD%eX%#w-0Ajs
zBpKpxo7wF?qqRPnvA{CmxW<3{kT{B<7_--w4?|9mZ?g4lpR=xV(D87RFzJ~z7zfWS
ztz^vpn_VO=DZF7ZA_YPGg(^Uow9Da}k+B{L?)eyN%yW6f4NNZ`zAi(xD$V2_8+9-F
zh%vgTnsx=x_v(mk(pF!!5hL!?TD(VH2){(cAzOi)gVo03l)~E5%-dVc65o^w&r+)v
z_pdL0f7&DdgL9w7d1>t@j^I2-DS{etKS?oCy^T{4Bg#IKx+`8aXbOrMK5?>;gs1mN
zz^_opS>67<_(3CBcVbG$@RvH242kw6kp3Fs#i@%)#Z#(0yx8!H*_3)>`QEl@4w$yb
z%fvgpQJl`;J|-IQinAiK1Y;>~y29kJT;Ar?c$6UysASMHl4KDsE_*8Fp%`a=0m`5Q
zg($EWp5|EZ#fUkxIrSnoEaWxN-DuQ(CeDJQs)#C<KTA}Ie5@lCiIDAQ6Z*^68HaDy
zp?1jy0BERvkT9Bj#Wpz^*X`}1I^VzI#_wfPxr4=i{o5cKm<%KOM#Kepm<)hCe1apc
zQ>$O(se9?xtPVQykuzEY=Hw$hkDnBoh$@U67`&!dKQrq;wY*bY;|ufz958-i!VWRJ
zY5jB!QYhxZoB?#Ks7?zsh3G8ny6p^xLM&Jc7F+VbDP=q7imv6?3g*J7Rp+is;qT}}
zWcbv{BTYZdo@Setn(X0Chsl3crzW^Hg|fQ1Dn%QsHvG8`71%R=D)QZh&B(#q%Fmq*
zzRpaoKP%&Pr1WDiS)#7tHA)4_j_0#5`Woblp*%UgPDkMmnX}xt&68w@yk~C=PWF&!
zt3#XZS%wp4Te2bD-$)7g*&g8@7q(UgJ5Jc^^{(;cba+DZueF2?Jk7INJ4pWJ2m#Qb
z0B)BJ&9)(pz-J^yFyg)?l&iL91X@xk{AhdasHU8&fjcOp5C!NU7X}G9Mg{spA4I?w
z5r7>IO3c%0^N;>ZkE~WhL9Fzw)|8QZguw4k;f3Km1vw1LiX<;P?brhhC&%4k^A7FQ
zx4>?hBshDsSyyNh1^^0nbUX+iq%jB!a$?UufA03+T_^gAt{YEk6_&}z-qx%0?57c_
zRQ&afV9#?u$49Zpy>hwEz|f;dUEWF~I}3%R)9;Yv_Zrb7zrP%^_cjtqQz1@0WbFo+
zA7okYQo6n8?RN<qN%QRK8ck>*E-xI4vNS#8F|u=Ry}}O7il8DJ>cW$7){tv$iY?~5
zWgJw|YUM5-DOBgm=`T84ZIYlWCpWsvHq1E^l;<lys~b4y@U&6cRaauJ`M;$gmr*qW
z9Pmb{`S>*&6MH@dsYdL~IwX)x?SjEbpa;YD{D0B$nKFj{%ao~9EHJMQzem$IIQ27B
z%JCzIhA~8-a?vOZG_WMQZE7aZtpcMCI<Xr4h>&t7?33wiGg1tTaQc<UDX8^Py=TOm
z3lcK@B_7YG%$4}<+AKXRqmf;vF~B7cQ%=YRW<RB8n=&bfQ^dn2Cto|7M4!g=D?gLy
z85E9DpQfBrmZI?zi}jL2ZSUSOwNB42>su%%r-la6YEyPeBFH7Ine3j0%!NW3Ua_eC
zwQ1O`9lEPZeEUo^)VS!tq3rTNIu;94yVY>XRG!#lH2)sQ2HVP)UMLi+=;qz0n6NNz
z?;3A#OT8#S4eGHn&*#c->CM}3e0?)Q6^kU1eL`=Gor?{yaB>!O^~TO}TQZRlv#jU#
zyNZ-8`s8<FJ8<Cfn4j_b4DhnGUUpqxH?4@&O!|(qo?6KwD=RanJh{%_isa0{@=~wZ
z<FOb}n(b;|&-$JODpi15AL*H+^24O2e{sPDmk(X6s3fofeVPP3yjsHOf%soFVA!xi
z`rYO{v}g22X}<d)IhzfkPxLlNtE8iK_d&zU?9ky0RA-nM=LF<zzdavG+O-fpjf_sl
zz(_*LDaByQ!53ByncJ|JZ>We~RG@<c@A00aA){&uicvh2$h@yTyf7Dg1Sn)T8FX5;
zb<8wJf5|6AU|kpj;PneEPO(q*i!ka<wgg*ZEjIC4MUeKWF$)cHw)uh;LeBCcxpVQ3
z4vWD<Jb4jPDtYc+(QuzboSfTv+RUTyQGo}Z6p&?-&=70*rxrxPLCzGi%I5g#V_iJl
zPJ<=cE-R2IF)1^?X`TB}`l7UN#FBlSJ9bito}jlEOqhiVB>u(E7&bGD=}!vwDb_eR
zJlfY?i*R(7@g3qDDCO}sUeKIsge$GZp#(?Sv)L^Es6t<nXO<|BKy08kxO=+d9$08;
zrP{Q#P<Lx4RXl6AyR@4avt$ET!prF(*JbGa-pHuNW_Mp>zT#!l{1=`z8^I{JBUY|N
zVH<HaXjH5?3k@dXlt=S-3Qsa-sjpL7i&sxVrXZGXRc^>A$2#KR&`ALlPdR3~+TS;j
zW_5Zg8s0AXSA6$YG1DZM1vVg1pcLidNKf<tQ&w*T*0ay!0x!n<k8Ow21sjX`C=(`L
z_#?j8E3+4ggvpUDqYYM624N-n71*}f9<XTO?vJUl%3-?swDPXSWI`f8d|nfBW-gEB
zXbf#*QoG58GcbwNN7{R)K^gp7SL)CCcu*iKAk)fOKWOyXK_fyzrDh|bAc=d89~#4p
zkwLIzXM+)akY#I(3R>HS%lh5wtIJ$6ji4bU5fvUL8&;}kqni^|sF*L&^j8&F?M!km
zUfUVr%G7TWu&xR7uj*Hh&oJqeF!{?kF^8>09F*n{9MxA>J*(|bz~((nAD3P;Y$A+(
z1dAr8X}K2jWFbs7pf!B12Wd*rkqn(1{_&~z$$c?JS4uSNjjC1^3i?4tQ03hNd!w;s
z@Z1#oYHy)Ks;p=z`B`Vw4-1u&m~<XW>vH@7LtdG<C;{y&4nMTSeeWn03-5BT3Kb(R
zIRq)bs;NM9gluqO`Jx+GE#Q3`Mu?P;sHtbUCnp;m5Qv2EG~6|RSTA|0lI>Ldo0$?<
zFWpDeHjGSYbpyG`TE@Iddpt2FT-0JXC1bTM$xvWLGM<(_WtmkG#(zFz3=0lHUt58)
z3|Q|{Ox$szXh^oYKwM9)(bC0Pj$boq1t-Y397{&;bV4!)dqR_+FR?8Kj|gwv=U%E{
z210>$C;VMap0C7jL*U>u+YGd7nR9c5OolgCMIa#@nTPj?dm^ij0DAd)dF*)XBd3vd
zDJr#a!6^LcbAJ`YaVuJYEE7t+Nte}5a!Mz^1;EY6C-nU+Z^^xE>s=R9SZ{GU?wqVZ
zk(@QbrUwQP;yZD8hISlt!7N{b`*Rc)af1r^4CWix)R6RS%_YQ*msM8x+&+!BsJgqE
z7+Xw!fQ%hzap^GyMnhUPuMHK9?Ch+_#?|uO5GBVgTM*MlJ8ACdhePQfHdCDqfEIP|
z6!p;L$X3q|hc?7F-{^L!F2fiD*w$9#K5K3x7@WtzG(H_#;a)c}F16J9rQ7~Uth78>
z=(aA7iZ@fZB&f4G#EJ^os-_GN@>1wu@<rqy$<8){NFVgqLMqChoU>h1+dcvsBuWm_
zm4ZrAU8HC&AS=1B*h0!AuL4>JEIcTsUL~kC&lJ8=*ePbKD5GEAnh&?U8sWo+*tAs7
zF0Xx<pJ{4^GKZs0T;ejlr(EEi(-Yj6>oCb=)L@GxZcx^(KbN%!JV-wt=-72#V1@|`
zv|!WI=os0Q^_`gXUiPRwN2HS`SSx%4Nd4-Rj)vY~+wGrVI<ystN7$*{g{`-G=D6&F
z%{s)=-j(Tu1VAdPEnIN*pi#a|jw4wvqV?AftDJ_u#~$hSrbe0%1&bhZ&1u@MT28TT
zcPwP0!M?$ssWOT*xj_5kwSZ)p%|jCmkY{zau%*SM;4-ETmO{a%;5h)yt?a_SGs2?4
zLwPdy2Gbsw*hfu#W{O7ZS2DF?V{3k$K01unqB;5G?AW6CbtXOgTTLRhk*PEXe)(Is
z)^}qpR(emWlS|_DX4sGAm$(wETz%)0sY>O;Y-`0?d)sj?`!es9>Au{0&StSnVF1`t
z^P!u+yXC{#WLT_|)jwg&9K@U%ff8vlOhGc)`jVa;e<sNQ)FfjtlD^A261E{QSfKh=
zP{hKdQRy_0csRL6vu^2MkfWT&`UKsah~@)_35=ehiCbniwn>M-$cd1gTSMLzlistH
z8y$SO$2792xLHz8!JKHZBZBlvjZ1O=w1`=|%wIl~=x^}vS4J;VY*H2$uAW=QE+A=6
z&usodts_0Ngs3pt6T%52EHsEApxTv;8=(^$NCPWN)Tdn+??-k}5r4gBg<vI-Uwj57
zd&*$YCn)NX1{C8oBo3Nv0aC~eN2nOax%p#{Ww+T*5fbqY&5&wEiW&a0Lm4&r#Sd(^
zEUY($V}x){#u#>^i{R(3U+Rk^oCSB}*jmuBB5!W<m;B2aTm;NLW;RZZ=-^i>GD$g0
zEOM;H$@-}TL}55}2JCem2epF>6<K$2jHIP;C^jZZ=u~C{a2L?ygw`jIPzK!|a?XYX
zNHq>hGn%ZGFNaiuz++T1`p1n!TC4%?pH%c_yeN9z1}8ljJ3%S@;^;3cm~cWtSfK8z
z4R(Z!WrYB$`WMn?)Jvij4CVJQ&Q@<9bg@^LL0fIn3Vz#PBh@Dh*mW89nrm0oz$%6S
z5**=iy-YEwHI847zi%F~on<qL6S_n<T%)_b={;|ryvF0V-n`{Zl(#&6zgND5Kg8I(
z();y*rs5jGLQGu7wG~4Qstibjg^0S(L}9*QVR%pVf53Uq1d%m(&6*3aIyHnNxTPH!
zn7My#7ka<UW?EKIJ)9CXPBmKt#VHMu?HBmIs3;$gS4}1EINoCw0DSeMS(;+lS?q;{
zRW;kUzg<<h(Hoa54ity~g#Ue7m4EDnK}o~P{2K-Jn~NV(vv>%{%5qxnZt(f8AqW>f
zLJ{6PDoQYVxKglq9B0eI+QK11Vop<(U_dGt4Z}+snu?((ZV)UXJe*A#V;~e`paSjY
zYWxA6k)|DS@SZv477ZgaaJAACqq4ns69s{1fbxEMo#|v*cw6dE{)NdA+rC64yGaWg
z*px@(B0C*QUgZz$Qd*O_IZ2dCg=;+5h5Ocd(t<Zi3El5}(tDQK^;cI`44=z3xsr={
zdmQpJvlF<gK}1lx^R@wAhDdB#rYgyvH3Yb_`s$8$Q6af*LD>~vbE*Y8F(ISXxHs(Z
zNX1(-INGcrub|{JzZU)7$E5i(H1;6WMu=<6s#Z?qD&!rwbCDnbm?^D}j8c~>MI|fx
z2}9L*w*9i-G`)2Qx<Lc~U+jm0dqUzpo`z$d4KnNdg}-ujZQ=CIWd=k0#$#vELCvJn
z2Ht;vAhjooUKgi=CDC|wM&@`0b8y%h(+X*9niYR8aN{ZCwuGpavsq8sP`N71o7nik
zA{7Cd6X$Drv-f3-;U`8Bf+{fg?-<#K+|5yJqMEE2Pva&crq+5)lJ`mZc9o0-ADU-5
zpF-T}>Qf398DyE|ADSEbYe*Dyr}cf2!b9;Aw=rxbT=r(_Epk*hBOwNC^@vn|!9LI<
zGm!H8B?1(#CYWg!E6FM)ReD!BWh@1g{5&{={vQBLK(oK>1Wf9%zEE!Z`-y}L-|?f1
zgmb@trA6>6q)DH1rxI3r7F$ZKLLeG+whzqOOh=WNEMdB+*YPFTLT43PYm_RXRNGw>
zcS-7h)He*Ww#TX&m<RPiRGSc6CzYvMTl2<W7NGG-MY_hef-Xxc{e0vj74_r0(<JkS
zD#lcMuyg{Y#ePO+FZEmxzgID@%nXFJaI=mGuJS1GQ!KJgQkd&)gw`0-3eycY?TZMB
zsmxR*IJW4%7ytku07*naRHO<*7ojK|*N;YI#@F&_i<!rU9;CGIy1(=+B9z9^FFj%n
zm<&wi$u%hwR+F=;S|g&HkFewcL_#sac($@7Y7uu|`sbIg0AY>YbDzsIuHXM{JX)y^
zK6;tu%42KvqK{-nf;W-n%mu--JEK&5zX_>3rLeD<&%}UKvO)b#B<NQsK|9nz62rna
z%r`e_C<|(prcYyZwZuOWsTo6kS)**CA?tZ%>QbE&&a&dFM7lB1Ak*TqRi^Yw<LIxU
z&rF%{%<Jv!A0yepws7u{X`oYDHUjaF_NhA)r<5ipI!S_>D2iQ@VAPP<4sTu0`G<e>
zAxL#f*vQt+ZaAU9ZZnViUuAr}W#Z<^XB}SP`jKa4>mp*hATBcA=6)}N!L*)Jz(dWj
z#_z9NU#Kq%%Rn_Khnd(_?;jdtQPua+VJ#p_W;`p*-;Ap3i@pPmW9^q-gwmC)EvGzv
z;S?Pk9G)xoZ&YzQzHr(!E)wP^mGd+89zqDl*e(i<|5=5!%*=C?nk>^gl{Py5Y@14r
zm`Sy^VQZhFO_DL?46W0rgO%BYR>z1_U5re1%B^R7_E&UiYn?RL!{4S3Ycr1eCI}jD
zV{-1){ib1F;{?}|P_1B(5Bm1AZLzoguA^s5LR|P&Bug)r!uGh8d#>Ljnxtrjx8vgz
zvtexI%%ZgYk|VQ|=@%acA}}7YDM>FxeL%~2ThjrRS!hXHv^)aBs@s^}(dO4k)1QUg
z(qd+}h!@T^!jQ0yRMgI7N)N%*9;(c1ux_*D;;Al|mos|4#M?A3k8o;ShvO!S6G|Nq
zy<S`oK%vaJPbWB5Ep4>Iv{YhSeH>Kju<8}mdM}gnRZNRBR2w+0-@-qW!7|#WQ4^h*
zF3y824!9w93OlyiY8YV{?^vIhD29$FV{ID^j*&-Y{?_!fy>Y0vg!D0FIZkV>BODWP
z4R(xrjs2O73l=6^Qu*j1f=W=jOA>?n5tQds3ubEjYJZ=Y$&*J0G9GHR{cODn(pa;5
z6rpmFX(*XLpDRe&-fP;I7l>C=DDWZ5{TS94P=GBINvZ>hMG$;p-H%puVSkn7OnBkq
z8XJirb3!2@l#deDMH?A3JG;b0x7FAC<3E`*u4<==vlFM0bsZAymo$1T*d!db__jzE
z7i_c4s9&kJ$6uO%h2WYaV||VFEa;kZF47h0T{LB-`F9!>QAuDGw~lU-m0@*c4%KP@
zeVo6?+GYG8!kB8zh<%?#ej22f$$C|1N)TgxkT4d;#$+zRUm_YyDu{SO<k2~XYzt@k
z<kmaMu&RG&!QA%$q<-mPKIjxWnl+#GK02%~riWTkzCwm|-*%BH0N0F-PJD057cvlC
z&|meAr9`>1)giM6^%56fWUdlpszs5kl8DuVnkG=*eAR7>jLC&Dwu_G=fq9@%kZ8W6
zHL41Kw$Q(}EixycpZ>YlrP&FlD$|R9lK$G>@ge4_S8W0l)-<%=QRtLZaIIw$Q8|In
zR&;ur+<`5|OUt^w&Im0t$Jo!(x3y?&bZpb!167bjuZs6BCT}sp_DL%xbDa{t?&@SK
z6F<y2y&L<x&9G$r--&0(ApY2{@gU02iRb?+%e>VvcEeZEZqx9DVEzEle!+I<F)US9
zQsKf%4<i!IQz}|p;uBF%VS?VU%5hg2BI*RwozvR%w-(wNpNTV<)3~Q*OR^bTJ7#>I
zYWwCIfK4;F02s$l5GM^~$LUv?fez=DM)^*~lV;+B(5DHe6Untn?1N6uph}0v)S9o}
z)ueKKR<Tm0qG$S5wg9ARh-5szSyi=%?};~pI*BhNy3ACWa^^v`DGC>egmVzqERhfz
zk#K6Z&1iVmK<PYDaKSTQM!ByJ>ptd;k4o45oH^PCiqqE~z2PP%W<^IpN1}?=f(vUI
z7kXX9yYM@~i(wq^XmmUdtE^I>Yc0Mwnw@{%J00&p`vflV$kuh07Obr1NjoBg*0+T}
z+6-vHU{s4eieKSaKO9Jf>DVyo%ARo^!<zEp)A{0~Y6yI(C^o8dd?cb0e#Zi|$mH|k
zUlUL4Dx=l0A)9E^Rptl_=FJpJs+fHxdeV$_TS!;H7@ZlGOc2r}Bk@S|FA6%W#zkM4
zI@YhBo}_jGgSs!mn#9trXC7rS{WXBA(C+={{mNM77kKm$#~7G3FEp;mj!~{Ww#-Um
z!54_}NX&@bW}j_+&e*|OEl;(l@`DjNHS^}ovo?C0bhLe-C>0Z@d?3-jtR)Ln3~MF@
z^XYHjx0p{xiX%ETm|*K1*N{XTthR_aM#BV-@UbuRR9TbnZ()a8byQ(&noBzK@2b*S
z%sg1S3rT>dm03gEOu@|G+3veA?~kzN>XKRvYYG57&>LTju)ebL*QLXHz=b?ZU-htN
z8rrI7+J{dNai|DcYI*MB21}h3>k33XKBiHtPNu>_i+{&?H)T_0=4_Y?N*gaVbxI|}
zM8s0fYb8h&k%3lG8(RHsh#8-alY*$CL9`tok|~Du(EGyzlNXB#D666;ir4iT@=9Y!
zJzd6Dw>I|D?b3Eh5<>ohcE`N;)J6pDid&_Qw_kT@fdn*XP6pp%AqigG68cuRHV6I8
zqv&A})>PfI+IXZ_``29VNAKT2g!QG;6#P(8&vFJ=wpOqvT5i*b9JQ5uB_>tqW<oh0
ze|%^vd`tYAR+<DT7wmgN%(g&{jwzw%^>1R;wJynQ5GadR!k1IpV4xZ6`s?I9lSL!S
ziQq&hbXkqAF1|w_lmS&dvl=D0DVo^4AEwU>MP(t_VFhupqCXC+z}#cyg(6|7g?2r&
z)WK~eH*vKZuSw&y#wc%2v-NNHn|O~}7VP%-QwV)U{L0LuDYob0AG2(E9^@1*+&2TE
z&FGI&@V?;ER>qk%!BOA@3`sQckp_qwsbdS)CqdQJsO^GcLl1$PCq=-qK29vM<`b?>
zjmMa+k<7gYjKw`0n+X$-)r@;4%`?h`7&q-?EfdYe)AYCw0;-)~eXO+o&kXygF>>0?
z&OTVYUxU*@;+jjb$*D1kdcP1NISRgND(SmoHgg7Y$`0!hP}0KPteQlR@a%mj_ZJb(
z7Q{TL9kl<Zl`n~=`&1*96S6CK^4uEBodnep7zts9ButxXrxYXgG@4Xd&0N4TFO=PQ
zX~!iWuVx0ypV-_MF^(yQHF<pjW%pxH4<njS2Muh~(EQNCne&&ij3=s?74cziSp?ed
z^ZcT#QnQ}%225q?-tgxpEGZZk8|h5!E@L^H+xI*o(y3<Vglt@KUnW|aUBMS$s4X%W
zKg+0?`b0#(zv9yNF`M6dxH3zTydZk=Ll+^aOuDJz%GMH@XoxycJ1d9mIl&NFVwmL6
zi~Eay5=EC<Tl4^cD~^t|-<{Cp{HiKw-eDDwY9<BuCGoHF{p<8!(RQmH`Qd)TMy2<f
z0?!d`F6KKAuZL>gu=vsphE=&KC2AzjnQ%(jW(5^|Z<cBZ9bu_<$6!>iMyZ642WD8(
z)Ed4w0Y|ikwDTTq1K|4cit78U!bNYPvX?PY$087QeD(C!V1=xci0YvxY&iB7G&-CH
zw<s6Up;@qS+BMX${2?}%M=h0_X6|+Mh&tAL2^ZFuFzWE$2SingEv;AMD{eA2y7B!@
zq6TS1sY>6pc$bd#)_ySU%36O*D*{O+4lPhnFO&)Hv;QtC4<_v1zs4{|O=tas);weG
zHsD~+BMYh?vr+q!O7&h6F(JmflOXRlFJ=-&ffEoMXn|-7@u=GP5*0JyzqR-kkH-V@
zQD3F?Bo8~r^z#Arw4Rlq1Qbo`--GYtoB^9Vj<rH1h{ur`OU%M65>7+}j~IiilSx$I
z`(YVFWr5<OOH`HZCro}b=WM-cO=%1gXSc5P8=XhNgR!#;2+h=GwR)3y&-s;v3#%Cx
zhmQ$FLZ`H)E|OMXDl|}uGCFpB%z9gb-b-hof?1_Hm1N9Hy|txk^*?R>K4;G9`1h%M
z7Q&JHP`f~<GktI6R%6;f)yT8SqExvRJy4|&-hM2Ld!&o2T!^qVBCOC#?O~wdT_zQR
zXtuv*2{u$I;OR&~H!UzmC`->UA5tpVq@9YZ-K7UXSOM9ocoO4TTg^D`7mUi;&nrxY
zDz?7btX+I*cK)DD>EBxPN-&-k0jHjBub^vkv`iT0hSd$rXlUt=LS&0Eec40ts|s-#
z1V?I)NE0YZI2k(B_OK?K`O<A<LXIRPk;RXteOJIak2Qj|Nh`a`mxr{fcE)-m!O!dB
zddhm&VzeB82QBOEW?F^u3sY~>l3W{xRim-?bMxqvvD=yxFqq`F?O0J`c3_jGLSHgx
z9~{#g%_|FZTo3VT8i}HkM(SU}f2M^*sm6K^Zmg#6WW<LBK8010)|gCPqk3uc9$s)s
zCU0q>b1{Ko1vx(CvZ=Uzd*AV@h!*_D3#+Vb7>){051~}y{cDF@yL$r3Qmqr2Qh3IS
zX7PNDJEm$#Sn%xSW#0c}pJ73x6l`^(y}O1D(&90Q_dNCZGQ&~H=XZ)2DYfbI<QTR0
z)bK;ZJ7P$r;G0jSEN^vC=NKLv-u+;or!MxmyJz_LdKu&M_zLokB`g)Fbu>CL9-&=_
zQNcO5blUN?r<cgfl8#9j4m>}8Z^TKFgg&(Dbl$VIk#g=-hqpiL<GrDZ99i{IjF4Fy
z7i$wu>C0eP71FA{)Ch?{Lt^2%OPeeu0)EPyWuk=GWx>O+vCE#Bji$}37$55?8l`QC
z<rkSDRl8hMZ^OUp%K{;4(ZY}kIu^}f#tl>bn05U@injhzjUETyhc!@FRY?gNiEphK
z5rT23Hb41@YDG}5weMe>vdIlfn#ZSlZD`H+d4kT^I8XGyl5`k1A~hl;ZQm_w{XlDy
z$9PsoJXg;y^YP8QynUn3M#pgBT#w)U#s)w9<qjX*DG{Hbt_bnlCBfQi5Ir7?l3;v^
z^Cc$h;mQK*^MGt@LRXaK#K%zTCEk@`(K^KuGQWB?I3ILLw#@M+MI|LO3Hy5^Tv?Df
zi*X(+f>XyxOOm7$cAs)Ut{x{Ii(sTnVxlpe2Ykshmou)OO?mUJZTfkL4+fT=E67wR
z{Sa$<sDs32parfRVbmjpIQBw<c!xIyUIeQKU-+N{vn39X+79Q|VKo*0;;p-^Bq^`G
zc#hY<-sSs0*<qMxRAKKDlaWZmXk^&mA7PxsImKy?kr7rciOm=lIWN7i%1K{&?~{Eb
zTc)zHnVuD2UJ)E!Tk_=A3LSiyk!DQYT{l@vEtQX9J?kS<Y292gjqwF@zo_k@7#as%
zDzsJCIYacDuper|uh8g*W=cErW08-EX%8rQExavWbly|>EC(A(KX$!|HWg$hi7KD)
zYIJND)yS<QFB{j1wl>2`f9M%!SnbU#G~RZ>ng%FwK*JBFQAM@%2ULi$t|4x~N%cb;
zQMCz;?IT_(y|QyG+}`W5YvKKy_jrBO=UXqH<Aa;G$*l6qGs|q9>TvgHz|TL};q2Br
z{l2nu7=r6{JFvNGxN~sA^N)9V_WT)+hXw!k!#!N-z$v&AQyg>QbcYwOo?$slxpwD}
zw?99@ryb6%b?91n^6VyR6W;!GpWC}RiKb8%tY-ylOBokVbvVDZ&h<M7ynSuRNeNwZ
z%&SkG;?$`Xj!y>My_d7SKj3K8Lyf^|$%V}h2m1rA-3G~4K!j!EF?q?E)bYD7En$|{
z`QX|iw|5<)Bc47BPhL39sBrxJgFOz9g^ODqR0mwWxW#AJj~I>|uRgUw*0H>M>n`uy
z9#Cq^@o|ScJIma1Ij%h9yT5*l_3j~;R<^i&ehoF2n>zzOy4J_~4yJTu#&LS3!^R3+
zxp<n<an3s*?z6m{@_WyB7>qpYro+!}I7U7}#!$(Z%d9|g#fWofGS01}B)FJzUB?YM
zE4V_)h}2dunbv$$m?BXYe4AH942c<EIywoX9;Vir%qo=02&Ywhk5m?jy!9nx>Y$cY
zq|jODv|jXMh{m*ENDD<ZVXLL7AYO}KMB~YCo2b}!T~XjBGY`PDbqk@o`anlx)Cu)t
zn~D<9m9O`}TESfj@~wZVj!Wa2g9-7otTotVg^zFb(W1}!t&*>Q&2svT=h~gyoH+x}
zJ=^8t*@CC8WQZSO{E){lTCSWIp4!TJ?#c>xw(ntW&bMD$!<qrP^JrP{waZJq{_+J5
zP6ph#yU(*%H+lJ)bynqsKm5)X-*|GJdppPYV#s&Daf+?(F;8DKTsUjl*c|bDub*OT
zbHryiuJP2RjITe{rN<G!{?cQd-RiQveaO~Q!XJM33};t|pam+1JV|-~&N1gst?>1y
zmaz61m17)7tgi|$zi<xCJ>|(huRgcT#?lE(Yr>gxtK8k)MfHeZf3C;6-Qn9Wba>;X
zi}Vjp=w*&?fAbWFd7quVeZKbeY0j=$oO2jF>I+0+W4*($D0uwxD&PFZ8BT^ncK7yp
z<>@Zpxav67+vV9Ox=3=&Z+~l@m!IC??wv!H*DTL}Z3CwTM+3+H(U8ObFvcg6uk@oT
zc;~ph)nTohfUBZ<N0Fp*%Z=HH+tD-|Tl02=&53(jpUQD~-lvl5L_$biV`I8Dkvhz-
zL^qEw<I`p&?N7xl+V|=MeOP$iBQaWQBSJTfNU+A%*@>*N;k$(Xnm8ua@75S>91n#M
zFW-li?y8SM>1oZQD*c|+A2m|@^^Avxu0(X9c03oUX%!Pi*J|86VUE<otWtfef*K?Z
z3v8k_v_>FKp2~GcS^}&=O^=Zl42LJYa4}``bjrW{!H4W0l-%3d<?An9=GLuk&Y$06
zb!A9Cf)_8W^YLeQ`NpL!e)0A#-n(|hM(-YPeET9-w+zOXWL?MCo;kyfo4fq*y<^lV
zH+M(;&MW8HzqdnXlwZ7mmv^rZ$dVm?_gklV;p!@0bHsXV0?xpXKG@~cn<pHPl$T%F
z;JBZ1@obNO@`F3vIm)<reVesaL)x)e@i?O>DW7jUe)Qo!-+X?Zt5-Vw;1{<!IvF9o
zbw0Rr$X~p3f}`N?e9Q6FDdpeZ81NTAKf?73&aZfW|2vm>Y<<X5a>(_2DL;8<hwprI
zgX8@}e)QIDN>}iD_cAYBT;+K04(Cp7^6HB#tgK{Q*zEDa$M<;h$`<c@xWmss9O0cO
zAMNq#(@Xs7qXP<4VAC9x0Y7{Hh@XBq<kF7kcV6A(-LmBETgU7lE5Eunz%DP*#LE8a
zN}3w3JhsAe3hK&QW|(c0GydBoWqQ9;v$@*wx&pi_$J^J&okSj_j;Sgu`>$~&*DM`R
z{S1nCF=!$BKyRQ9=K{<!a;}33wiN4A#-G}{k7f*-O=7am5VJ}{=#08gRW=;FB3@#c
zVu{H*T48Of{<o%?)cVM9>OU4YbAqYW1R1Dw$<y;Dsz#dQk@iPv7?{?-SG>xL#~DlM
z!O$Tw9hPLkOBc>#UooWCV3U+%4EJ`9c;-TvOQ)efu&4@02PMyc`wUCnC0=@3=}1n}
z6>e=GA|kBzgj@@5>>QCL%lJ-*{o_6+FWBq}ckkxhJrtz3&Zy|KbCPm#v%~S>A&G-T
z9XGc<`^74q<u&&E1;&(|y|~71f5_pnC(SnKyAhx5I7;WSl3~<hL=nk&|7M@<!yCNz
z%qf2N)r<VAA6;knSh=|`6lo9ZEyJNBNgb&l@WK<PxxBT>vOQvBBf}=k4D*Edt{);x
z9WI?sIkURPxy?-wWo>Plk8kXv&a>2A;mqbLgQDPvzr0787rgMeXM4NEm<~%x#=&7p
zG4gD#^)Obj#&B)F<i;V`^)*hMN4;aUSCSeq$qJHsAZfkV@t6N)6^~;*EqLm5m#%d<
zFL7s`w?xP3nG^x#e&G`CXNg@Qtr@>9dh(0J?Dslh_0$r58XfWdO3UXm)H->2TyHbQ
zd1A1<TEEmfc9Dt!G0m)l=v4b}Rn=AknVKrwXRscu#I`m`4Y+9#a#NS5?I|EFadeW7
z+Q$@~qEjIT@S7Te>B<a3>J?jhoCoI}MsqHm>QQQsdq*Q~+&kvYx9?EeWvpZzmdfr)
zhugc#lV{ff!`q+tIW9XKo|OFfoo#l838^g@xPru3zP6D-o<SMpY*(6)NYr|K>Pa1R
zi~*Zc<U)dyroyODEEX#+z9a)=AO>fGomb&XQq#p_@oorigf%_9C_x1;ASL(`5Oz*F
z{Ke1i@gKf^k#lEOD81mdi>C~1KoYdr=d~wS=&c(5{GDs`^oYOr+GPxeQDJdd3h^A~
zj+@u-@z#x;o-83c<ly9pubo@w&fR_9{K)~iW(=HgYITW@SQ1rAgn<HL@y0U5vLXp!
zD6qH~y;CLF$ypq!Dy7fJHKRMW0e$&JqXP9*&#|>6s4r_{^1se9i}`#}jJXJz&BcUO
zOw0!wk&4ML&|ys|(iSCf9kX?;7+uUd)V_b*-x8+7*N#`;Mrrk|YSE#sK2%jr8?jF6
z+KA_SS`#~_c8%s5rqVG4?bob<in210A)M<PF7=d)OP+6D>F~@G>-_waKA+ty**iJG
z8qe+RUA7O7C>%(V@z!TYoH@PDxve#B?Ufvk;QID1S*KwC;2wwl6Z)Dl)D)8#j!z7O
ze#*0tZ?c+fv&v1Lx?<Qb3ho^iTt3&~g$u%lIpFb4$JzCi&u<)n%_u7CYDogrl>+C7
z7=^pH4p{G`JhA2IxjS5XEa%CKJ)A%(pr!yuEU#ErR-h|6t34Y`u8Ka1G)KhMi%YFx
zbFIhr&NjEUcUf9pWn*K5(#L@R)>8P48~Z8CJ<FiK&&{13j)ysl4Whp>3^gH_6lXi^
z4ib*ajOU+RW<A+qCE4ZbCCflkwofdoO6dcVQ4Mjro%iunETP1*x|Flh8^sumUsY(E
zIG0qpa(bCls~OHa#Cud-&_{TtK3}DD`eo>&9;se4=X1a76ZaZ1@nc(`Wb7kiTc3w$
zLnIn6HKrt!vQ_Pn9zR9|8$Sku353SjTVlq>P6!~)(CSA#U@@&vWkNCasZaUlzlSIi
zR#dj3dZQo%gHyxyu;9fP&T#%pu+F}<v%{Oey36f7L+LH=UF-8(uUz5a<OnCLd~hS@
zqgz9c@`6wAj!=QY&{2B$!6)0i@y$y-`{WAFr+l_=c<0(KJGpRTQr>)fo7Z1n<L|tF
zHl)^0m-)+|9^ie4yZs?gUs&de3ki}Ye0FWf^=;4QR?2ail9!IXqk@quQItY0+sBrh
zyO4c)%x`_`B7>toqLzGk5)fRp2@>zPv@X2-^kYz*kS0rfa_5+v+e)Wr=;y&8QpIpE
zg3@)kG4#Cp!d0$Z8j$yuPi~DkD!S|(d%RjCv3&S>!IPV(_)lM7;h>+B4|@Fc!#f;}
zV7s4Cnl7bS6w3(1pT51#>o2YI@4ayrOTw_|@cp;$(CcNK3=N(x{h<U~EF6kq`&ij4
zQu?=YzWeP{l--0M|8hi8urRUbqZF-?n**Qo+~qCSdl|kMhAh1mlbpc_zKE~c-_-Ku
zP&_HNFVc{G2`$&+;X~A4X9<}$<(O1Fj9qJ8a7??N)$9iu6KShrVthV%=^y@F?;Trm
zo1$WZEs+N4*PED2P8BHVSw}Ymqe0{vj0#51Af$LaR!6KaS!`k`z0e<daxY*EnRvWF
z>4Tr1s$;pA&`kyJlzyS)B_zh+o#4unZsJ+$g@MU)<)H65vu^miubtsv{p1eLE6yqh
zCkakdvP7fuFxX(_UQsn9Qj%DuaEef}zHC7~nfCd$Z=C06AD(dYZWpXUq#(hulo_n?
zI5iv%JXlL&73YP*8NiW>#~UcUu-3DrRv8RSoRg4v!9b}dxTtto7G=2`UPPY5u<*e)
z%s}BSUIJo5KwUvE_4K+47U&O^lUzwsLt+$HhAc3pLP<z8n^{NUgYn<Wk_EB!hk`E3
z6!eJ2MJs*Pf~?%<fBX-g<aeH2r7Q{zilItC_SGu;AEr!4I(T&29_HD}OvvMkby$Re
zCzEm9FY?29EUW4MPNi$C^-c5YozOR`8@oQ8#;np^jqB|m*qT3%%~Z4oG2FX%x6)xj
zEjzafsCAbLVmWcbabK~OAD!4>&FlkY^pdeNfZ8Xq%3_OQ;BC!C!-;Id;XpYU5bF}G
z1oxD1Ic4Z!cpT^wd;|K@jFZB$GY~Yjq*z2?Sb{{?o6?62A)<owke5o=Di=076vF{|
zQS$85k71IO8@nEFQ&I&L&&UabV?|@V#-<2@E2CqwgwzEiwb8*+**}T>mJ9$ZN=O42
zG-{%Tz7tN4;?N2hNpK$2YZF?f8g7#@D3yNuek*}VJH-Np2Q|J1_M<XHjTM1|lMsp0
z&Pn<HWfW0x<%kO#Dd*NZfl);rNM)>Ga9>&b|E@e_nNU%W8MMx0D3PH}rgvz&1dV^6
zXlquL3z&UvkUHh<pq0|Sf_Srb!>F;ZxTy)QJEqMprOGiEqBw-~WYQoz2`;*`B$COj
zwej}my3~gc0Yj)VDB=B^eN+>Y)T7p5U3;~g*56g=T8rQ@#&P*f#_821(lnt!dGl8{
zD147Zf~HP2(A7rDo)9X<8WWjql>cj51#C55jXaMu28ANwp33WT>?F5RkJj~tt9BA|
z$4d&Rsh+e@F~!#X$ydUtS`a-dM%5KOeyYo3Ydu7R%Td_q7Wpv#%|TuNe=iS(8igi-
zHI1HpQjs5T1;DEd*Xqr8yqzj&L6g8jrcfb_tH&3;{aLg?6Bj-i|GCAuTJx;-N%Ee=
z3W<6!!6m@C#>`6)j1Qgg5Pbw~tKLbHZH%_yV{_38S{rJ7T++rvBEr$A<cIHUllU%a
z0?wB}3bhDAJR!94mlC8vRB_Jp)<?$-N<)@f3O8ctQ?kTjTp1aWX|?Kc0*oa1uK)lb
z07*naR4YA2T*9z$6@}qcj*uQrG(>R-;dg9wl66>ZwgV8XdMv^3t2!#Kra>7E1C4@c
zftEQoNiZgeiNRQ~WGPi_l5sHdSd}V2CO&5K4T{gNf+6VmzvA#HMwG`-FSDA3EH_~%
zeh^Xc5p^$LN#FimSzM+en1}@R%f#v61BuFy_zFd2l3`U>Cb_mpe9p^Hu5$WJhrB2d
z5pLfqxOV*nCrMZ^@x&mUpaoQf+JIbIr)%|JKE;RwDN*rwafBFANgWfaMjlczB#XlY
zBLrunm|3Ad#aAmB!T8FdJD5i-r-tvmaFIWI=aBuAoSsz@D<KxSsp4@(r4rG~))YK{
z(K0&eaFFMSfxCBeyn#G5I4qe95hJ`9Toid579DC$t;0AMB6FH(xm*o51~uSB5C@6C
zb5~Z_-s`j9SCEVnOI{9n?rg@zi|hQepWj6^BN4^Lv}{oo$|Ey_xkZ^~LSeElC5Ee~
zmgyQrOIP1x7G`aJbo3WA6puFJ@2BklB08<VuCh2v>KE@%g_<UQZ0xNjq_78RbD>DM
z=s9Xj_nCP@VhN&{QO`>kR=IX?hmY>=(vuGT!!D}AsPGtTFxF5SD(HpBVN(qYvUI_c
zRs$n2-3<H?<Kjxoz>}g1Wtk)Du{O9Bc&CUBN@Q`4R19KGfQf}Cu_l`JYuNd<j0T_y
z;yqps<Rw`L&Y!aMGRMI{899%rkR%dMR)f;MD9h*pFLWg5RMufXS9VTZOj@is@5sv%
z>r+%SM7mg2L<f|4AMXX1by0*R&3XRuj5~Kq?i{6P)*x5`yp~Xo5DK7+8X+$n&Uw^J
zfaPw4&riq<oLv=+Q=C^+hp2J!SUVwr<{2r$A98ZcEiJkgSnnAwY-A+rqPD6Q8WvR2
z-mxE^iZ6?;%vON>)za`czf3Fji@cyH3%cDdUy0G(yveGN;41~G#5lTP=L}hqOv7Q-
zQ#j?uZNn!wmsw6Syj8kO%GnII)+}BVKHna3@v)3ED_wRD`h0YIA2mJBt_$m3*xKCW
z=G{F$xpS9io;bzhr<S;NYmZOvI7%|o)bsR{9oAPeKHom#?%t5)ZimC;kWzbdCFn+W
zPn6Wc#)f78V8C+bc;@0N>nlCB_m24R#sRs{IJIKvEL$F1UE$<tpHW%TADtjR=lq#v
z4*M|5tB^V#Uyiu6DO^3bf{5dz&krd)<S2V5Bg6=WH)L7P8&9vX)LG(_>qp$#9<kC*
z>7+w8*Ok+on_S=Ze0F`0m#%jByWd#mgX<^!=+l&s?<tb_=;H>IeXc$xT)udU-9z~3
z+A%waBSwW%mIaTkD9>D3V~~5grXbH9QhJtC$8(oEtgdEU+wODi-UuaxmYFhUo})^d
zIoB%lmipi7cT;~?pj6L=vr9aE;S_62O6hvFmcvnwwNvXfv?V&!eq>?Jc@4g7W06J2
zcH`)EIECIGjU8*F;hkH{+-D!+fhj=oC33qj^W<|@siL<w^?UNXAkT9;oo-931w=jS
z7e0NR^>~~&NthZQ)K*Uforp>u0kh8OMoHIt60dkXxPprt!tZ|j67StO=F>aJoI5RC
zzPQR@?}%?cvrO0a`Q+L*fB%i=**$T5e)pK~d~J<apX`tuI2j%CjTd_iid}a0`@Htz
zSyq=j93Bt(TQ98h_6PU4^!PGA{?&kcJAHob*Vh5zkH3GHb7y)y`_u-%eCrN>>zfxS
z3&Y9DkY}ISU~MDe$G^J88{c>WyCi&kr=U0*;k-lrkQXmyJp1%%zW=j5hNF10SPppp
zqVU{PTio4sWVT0lDJM4tBQ3aezJr(ncWxf@YhOQ$v6fMu^Q{+GdGp72xo~QkzxDD(
zKHocF_o(EXPp{G`4_N9HAeJ)eV69@xA&SKdc;|Tjyzt_aJq~im%2Jn}dR~8ilea#)
z!LVEM?UygJyPwlbGG2S;40}6DuRP?H=g)KDRLZ@h0k6KWK{q|%z0V6Uwt44^7USgH
zFcwT2Ed70nlp~}ZKrukden5e41Z57sAT0-QnDVD?g&*jMvUHK@cvLjlW0`0;XiRjN
zPf3!5G|k959Xg#Zoo<(2w?}uWN3XX;r_&)x5|T8bEJ~bnL1A1gbjSPf=<2X>ab}@4
zdJ8z#6x3+5QgX~$Y%>1yG_z|xKS|?Q<4o^FbDnsxYf;Qs#*Js&W7_Ic=$~N4B5JVM
z)<)FSy(naNrJSEj<-7|T^vg-y$ZA^*jTdW+Zk3>Sah_%4`OOzMxq7}}B$l7Qd%&uc
z^ibaX<z4O#4QH3(`mF=@c8~b(OQ(3|>UnnW?Xzw?Z+>{l58mGAw_jN0_kZgW|MUO#
z9zVa{=X<ZL@YJOh*47G6t(5%npMK2V$n*L)PI2z^5*;0}wqn`e^PFD`6TX)@POlis
z!#!TSyuuQmfAZ!X4s*k~^?m;RH!gGc-Y%zBQ{KO}!$1GYE>E0Zq6fV8#1iXU8~psO
zJq`|rn8boA>%Efap4jBAPxko5#}4Z{taX%2=Tk(K<y27_a`j3^S?u%uH;*{V4Zr)!
zV?6W3I_2>RD;@aZFK+Y6osw_A@EBJfU*<1=`VmV@J>Gm***}6)tA<{p6q0f8Fz4~J
z>*RwW|LiZW(OueP#VBiCPtW#w?%8wP-5c?*ezc3F;B+c%t@L>MOv<?x$G`mkN8BC4
zH=f<(iHlo&e)Eu%5@b>;oG}r`nN<Si2z%>I%)NIo$9IwZ7|Kz@z_bMKs7%&VUvTfk
zlz;q}P?iO?LvFR6MIs<;TVoqcj3{8O4WGo4*n}iW=yW@*tgQ0bnRC4G(o4Mj%4>mf
zm1WJaD%vXt+xdKEo_Jc#?QsX*ChW?Ln&NSF@YS2(lC{Eewy&a2T&Yck>Us^$FB8vB
zv^B0zYP6u^_s{A8tw^F;e>ar`B|0AC3T=?Oh6ubU7%bi^d7e|24r_x=qi>DnB7mi;
zu;>JP9zzxZsTo!{iE5waX(YI^DHDNGm0S0Y`TTZ)w;BBrc$0E#?})MxGGp;>#7kG!
zIrs8;E}im}#$c0#TRVMr4?NxOY3>~k`1HmRJBJzF?kb~E$?BS?x28OQZUz0$B}~?#
zw`AGL3vO=jvA(p#>CGWG?(C2y9nNeT)|X*t@0iEWuXFA5ZH#tV?RD8d+~?%D;Phsf
zqoL!@9xSC9i5kwIUSf4+i+}X}&$)fvivu1UI=5DZqm!J^Zjb17GNcU1(tE{w$X$pg
zarV?2S2k8z`;9G1XE?W+@cC}ea3s8Y?U>_!!ut9Wdj}&PKM%cLmn`eh>3GtC^7NHu
zE}b!yHsx2Jz^^{p;q{l#^Sy6de)8cSgP~BWr;{YC_15^|FK^N5En!eTyH${!w_MmV
zymDm=b%LfDOG}oKcO(|t(pWuF7Kwx=L5dU7pZ%}c&;K%BXj`gJh=vG=B}omPPDUqH
zIzF8_*(R0b?eESzoGZ~$oN=o4Vt(iCxA^{_{R!WB<GcKW|Kh)*x3o;@%DN-oE2zU*
zgQ&DZLARMhn9)*;x0RwessJkHS1)8YpJ7d+pt#A`%&5(zr^euZVq1f38gZF1<@WsA
z#@X^%-7`e-`d!9;iv%+sg@BByVp4^NDmR*{jeJ;86eVSu<M;RJb-O?lrF2$Iu7*15
zgSiJq#S%@35I7zVNg7fr<@*db&e(pghWBnB@{7+E=^50Q6q?faA!g2cr{FtZ-y+Z9
zy&Fdy9V-{lcQB&l0woSFLT)_+HRO^6Fqd@@3+1rj-u3~X+&DziHHxy}cK-;B=hvQ2
zS<5`1+{;Of^6dEzy-va}KOS-6Y=L@%bHPDaGyyeuJbB^CeTLN(O3z@JbC?fVUb3*?
zM{Nf&X|NqLF^rD$K@l!#7!9SiLounx8qb}(eLlKXV3U-OZh3C*4|wWQ#*iLfdWZ%m
z;NVS_#JYq0|G{TDpWil=!0|xo4=jKF)*jDZ$@r~TPV=*O4=GinUltT5=)1~tL~bmS
zT1MXR>2AsUxB8?>PGK^(PmbvqCfLHweud+c0m3^MA$jkgVn6*pq&=pr1ZNc0aM+O~
zkr7N<T({epI%TR_ZVXWxnwoo^bNrkC_fOb7y~Q8=C;vG{HHe3G8`26*9O!V)w?s9?
zRAHtgT$t&JGC^K#K_(M71@2Cpxz-<vS7sR;`tc^GnwOg3@qw%P%Q!llG}>&JNlDXd
zWJFrU5{nli&8opP34+T^6%T7t^sdIuqeyB=(<L0r(3L<H=gc<@YYxn+#&&)WCI_b(
zivDO6%^E7ETelIchXe!SP~%Y-EVFHAi83ogU^G9Xbe>V3FjC>{s^RQr%0K<f&$zxb
z;_A09u)fkE*Km4R$bg|u7#S$6P-dR8=!2|aJFD#69kMa9ymx({6Ll<g5{z+-#Pit3
zDb~8D`SGVW$vU3jeqoba`;NV#GAM+rPi*ni>(|K3jB_i(QsUX(RnBducryZ0Y~r|c
zG~x&E-{r+;&d@V^ymPYv0%N*+EPQRP$KzXvynlOuVE}1{(!&~0YCUBkY~MTL;_4>v
ze0GSJgte6p{Ss7zdyNytl^*W|i=lLu(m66Sz@(O)6Y#?n!U(gxl5zL&n7co@#eepD
z&v9|RLs~+a8%_p&E}iRg@a`^&crIQz$I4pDFF$c~P7e8KdzbzI=&X@-GRm-3HVfx|
z3S}{v!<*R8{~VHx*(-WhQBosVtwN1VGOWtmP{zJ5q=gnDkYK2srWrr@*MG*hzw<h0
z&Yr`SWvf2HyU@oP?X-0%G%@0<oP%{Ry>^>zT~=Jgjg3)D9E&OODsifc^;9o@1l)|2
z_f_CR#?eO|f4;TQn@?*zVw)8+mx@O3fMBd$n-k4QAkl<U4##V?F=&fX#su_@A!zj`
z#?lsnNkh1zK!d07t~G}7xrtCa)woyHR18r}+Z6Tw#i8@U%TR}U5RGyF#BeyW49XrQ
z$D~>!stiiQ!NB6A!;QU?JG-9WdF?Fw$0cW$*0^_|6m-}d8U`f+VR_5$Aef696Wnof
z2k+iG=Je@R{-eMBEPJC7*j3*D@E)Jt>vQeMvFS68hp=W6`ntr&x9%dk#9JTdY<|7q
z_kZUsgQF2!OKW_5?U2uIj<|eD=oc=8ml5HFgd2MveRrEzzJ7rt23)%{1S1?A2_JoS
zz;C>Ckr$slp(qTWTsxu|I)<g<#8Ju$pWN(o`PCkO__r@`G8iG*3O{^nm;TT&D1+~y
zs^WaYuuSRa8Fvqcy#DGIZ-3_b#V3Q>ptSIw%jcGO;Zm0(@3MD1;?~XqPh8mGuw3Dn
z@0{@3x3;*n0nQsvul3kIQ9iy`a^_sg-~Zkd+}S-qlU3gRWRK5p2Uns8F2-WE-$zD=
zGZbG79z*FQ!G|%dr}pA*i-6<e;J5~62J4!DBGx7x9PIP{yYH}d_FNDPtA#spdlP?P
zygH5l3uw6&y0=CRmFN+Qk4(cwWI|+yO&~<6f2Y>XHDcCOm$c>VJGPHBhL;rrs@iHK
zx#)dS^@SLdDn=zyLg@1GURR7)qo^DiEtNR!8-}L@^xxu3<BU~W&jYyecvvlwt=*qV
zakO1r{J}`@oT<lb;emouxDt8kfBLE38YC1ZMN|lmG{K)*ZM3A;5W;t(BMeK+v3FPu
zMh%@*NUd;~TfCO6r6-)*1V_U0foG&CrBk{YoD_jsbwuf<%25&GdiN5~k|{YHlq_Wl
zkFBS8@thQn{lk)xvve|tHOgR^k%_R@$vGKWN|%tU(o6fC*)pUyB_Arc_Df0<R=X*K
z(o>d@O37MB*dGC<<Mc{G?lTTYiZ=<?I}!$*-{{d@?vR&oxIe(Fqfn2C!<in3MZ!ut
z;M|5_Y{Kynb`CvVlaN|Ve-tKjDoQU?jz&t_$=O<8;$)bzeWbW55~C_>ndSUSiLpa&
zoG62lWuudEJW~89=hV7qX~k1`IPNQj?{YFw){;JFHw=(4DlK;oN=B}Okt8O!g-W42
zGxIZm?a}$^|3doFKSz`9f(g@}I*{NvvzoG!hTL(J$J_H*(`<=s`reik2!r8}@BO{s
z=O6r+|23oj05phtNN|#`?hgp4rKyQQ1f7fel}fybi@mNR>TW8AR7M4JrPuMk@?)(I
z4@^ts8IM}vD#SsP6S7*6W060@A7dlcMj@yVdb;WtF=K}gZNvrO-LzQlox}Ntu@Dht
z9R<||_T;_R5sa&QeWko^_o0OntHTZ<hMu-2)Ef_8gtk;TzG>CGQ=}GGn{f>9K>fIT
zk0A8>Cl$gPCvLJRiW<YtFvhyEQLL7XVIlN$utrHl=;sL^-5z1_Sn1-$kee<?LnRZB
zQ5Y!<hZ+wH0s=ZwC9}do3ETGs<5R>Z7!v~P<tLpmq6y@x><lfMWFZm*Fe=yi<Ytaj
zFp0$^9lWvZj)?hs9J#{w35e;T*0Fsw0x2K~%o<54N%?d~@VkJxkWohsVjO6S(=L)&
z4xHuSjzhd7wL)rB24%t^m(VYxj1&d~FjjFx%cp%4#?J_9G;VH&;{kkhWDqiZmO_$p
zXCSB)B&p^0p@X9nL@g>ERFqVNev$Fv9gjmOO^P*3B-YK<A50Z7h#Mh;-TOQ<ft-}k
z=Sntd&7NwZj_W8IHZ|5tTkM&fb8WqiS9Z6z8T1Ds0fKs*3;VPyUEO9Ke~M~>hByhn
zbPW=Ui@Ge!5bxZ^c;*p}sQQ|@SL~x5nkO(H*Yr=M#aLRaD2j<js<iJq&ahfyXl*S{
z_}i7PW(KugQw!ydE#+F|9ano*btj2!m~Rw~jg9VdF(Vd9ptW=jV>Yc5UlH&|YsPC#
zbE@ehgGNJs((0ZuhCRV}G@`$vEI}bj(z<^&^Rn%C5XD(Bvs`nkE=Ogh1P}@)nCTF*
zA_roEg|(F^5~w1i7?Yq$KxbA3q$G{D8>)_q+2ggIWNIu<6GVj6np$6=J{|;AgKQ#)
z?*t>pG5};0!P*WsDi#$*JmFMAQxu2O9BWK;8!?cigv6>5D#s+MCY=n-7^0qrsH>jR
z5kt`k7#p0FHB3&a!^y@t)-f8WNQO<I%3#|*c@e9K4GdFM!RK_n0STw9K20$Ki8BZZ
zUP@FH(N2h#AtA?~p}@o#gT6lHs}{qI_~2sD;u!Md`@r$Z2R$7tByo_OD=CVSEKMV7
zq24VgPt_`B(vnc7l*p5$7$Y1X9Wm(l=`AhcU6lmY<J1RRFKeQBSGA`NLyR0ms^0;O
z;MCU&XCNx{HN-BbVXn0wNDEn1OrR3ue0<(i2`&)4ca&QB$qH2xj*4-4?`pIq2v{QG
z2!Rh9MAwW_o{tz61tOL-O(}{ZwrepWl-`jg3EqWqNfL|qP&x-OIfZK2)SPp8?=jY5
z5?h}R22oM#cLo(>_J|QI!2_jqWiU4}ra@XJc%YQ7tj$(j=_sS_F-a06v6N*QGpUC*
ztTFY0N^o?J?;+ObB3hgdFEa<q*Yin(t4$@d0^{}@(U!%>IL-!GOGC#>pN1OaacZct
zs-wxS(ePyfV}jB!HW>!IqRQ9Ip%x{o(~wB6c!Lv<vxAVOrpP!tj*8pp{|L=#RckM8
z{!+ywlpeaKAoW3imnI3B6-Ff}X_Vy~$lm_97Rkgn*^H}V#?+j6??@ep_Y?^s@IQj6
z4G+cz=;Ok-g^-Eh?QFEt;2ashE(R$ENO6oV)L%8DQ~5=tHi#&re8{)H^%{?DZSgPu
z#lNIK7_ijqHEoS4!3ko(Bz3b47Td#P41@j&qtTG1l@)wZM1^h4h(pUhYXT|OO7<~j
zw?wqjKE9Kf_%$ZrZOJs%&flP<ana0Li$<j3Tp2cT8<v*(3K><Widr)@uOUf=vCa2t
zGc(elzDj%z&stIor4LL%M98uXkiZl)n0#0h#>TsVs)89vFzBriqw}ubVDdb#<94YA
zh?3Y8RTsv|Yh;QBS2`T7KA0$qA|NblNt1-UDDY8~E{n1rhrpl&yr*<78U%;ATb2d+
zC=Z8u6>^XBqC(L{QA~uFsUYIa2_^NEoxI5i<G%{n2vfV6;cHiy`RLjScaJ<W!>ytL
zk3w6ZkO+%?M0+OcB-$Zan_6h#acg%9?9lP@rHm&pZSejL;pk|;>R1iN1CAVDG1YJs
zWywl6<=M+UdP^2l=DhdO4&CL1tLK*Zx9{FV%<`N?-)0ic7`9PFwUE6Fy22;VCR{k3
zQWgby>AAg=v$G3o(r{uc)#3z<;fV_=d4I^wgA!~SYitP!6&f%yjuu3M<$5vTK};El
zOf@w^nuK>T8jZMm<qH4(fA`<=-8Ww6fBQ%OJ3s&VF91lh3{xqp;~bh9W@Li7Pl}Mn
z3d7-mlR=+TaUrYoEfFi8YPWPSRXtS*Bj;Q#ZkQ@ua3$JA<kLoY6>}Q5E2`QHn@T_v
zP!yw>`p)8O_mH;e7k1pntN_Z=k>@!@k&{I0e`{?^3~NMNRf1nBK`b*yFj$JRBu&Hn
zc1}?hL@erq{@GW$I|zQh(G$U@0gc%t3CzG1<YieiFl%f83eHiu5a_^&;Jk~raG^d|
zx<(R0Yt&SYS5XvHmhDMuNs_?C%NCMS)exy9GN_748<AS<PizQcV5A+bL11$0mwHF_
zIOju*1S9wulGnuR9#83%L<~4ZOE9T|5lkYSUiEw`o>39<Kbs`vi?e7DktBq!seBrP
zf=>cRuN42zQ@R|RrC_U5IM-q{j>pff&>t1t-Wk$034+0slVvA-{i!qj>mOg|_U<xR
zi*p5D1!qFCO&g)PM=6{mF_4-d3TD>wYcH;`*(-SO`aO(Iv58?dD>=7X;ENH3>0(St
zA{NA;7Q8E>2y78+qZm`7J_JFu)>10?vP8TGF<2wKdUch4d5cevk9hj*d7is^jz9U)
zF5CNMt-mp1v9^ONppyu6K%GNHDawEzO(KYgrA#?{uE({TeVh+AZ)!A%tS(2&(M)7B
ztEei8rDj+n5_VYNyKlU~w_baVfA;_UbN-Ki{D1P{haZt<DOsA<x|i9O+7*~-P|KJi
zUJUtYgm)!Lnv#~~m_1gt5UM#_D}<w{Ub?W5k|d!z+_N^I)#}77FuX=ogKE<=^~PB-
z3;-i3VhqkjTC}=X>b|OK$Pbv<dhD9(C0Uk{Wr5+SDoL7z1zYLdA|t5yw>2T4njoYm
zq2q(D%Q+uVd6w4gs1G_NF;b7M7!&4TE!~9QRiTr0YQz)}U>K*wCRC?@T8$Ug>0<y9
zCJ74n(g!qEiG_(x>TysFrXo$etmb`t?`v@~j8Vhvz4w$Ti3#gxc6b?xF`WW56fIdx
zbMhi(;4_RZSne7ILxWSrCM7mClt%-uY<4-jvC5s}W3KNN7*bS6B=(5sFRrtadOp9~
z=dkQzB^YdalulM)e9lV8^5nTSb`Bk%-5cVZC9@@$PG_ujQtllU+}a<IB!+G>WMw&}
z+g)Nb81lVm;UE|O&HIkS1CP2M9q)N&!*hAbacLvvZ~#a7fTu24)|R{6KF+zhJ;1mw
zy-cy$fVI^wM+eHu$WY+f=nBuC&-lmR|Cn1xDIIHYxv;ei9iOw+RUW&r#^7Yg&Fww~
z8CG+yJZ9Nk$+)>a<kr5&B!-nVXRVvC(p~1(-2uxz%f*X54iEc$yq%*Mmb~Y)+a*8!
z#BlAidwlQLgfnMhXK$a&TNxXxON@rf_3eVA!t(izK4PHPwTM4p<FPKw%S+taK4E_V
z&zwv7jTePCCFi5vl>K26akW95LtMdwaIET%#G0rpoVGdY^?Ll_fBXl$@y6@?(I5Ta
z{Lvr(F}H5srrYh1B<Ymna$}Fvk{%=atJ@XR?ADdOu%6sal2GSeE#_6ssVocfyuezE
zh>06ja4N5ukdKOdRmCPrjckIej?@SvEOtM}klJFR_b!ND6@#%BYfW@V3I-tF`Pv;x
zy|$2F7>j%~3dqkl3{*AfN0YQl*%lVRv4IYYAl)=Dl_+MqIEEqUW+ORB6<9I;l%`pY
zFs&GpG!3XHnvb+k?yBOQXOxd>(K5@jz{rd0eT74)s$UgztHvvUGC`7{vzDlTgGLYN
zS|^;|d9We<ggx`O|C|5exHQ2+ypE3vDiTBB2}R!Ll_xW{HhO%vJz%YC_=DegjJw;1
z?4JyH{^}~HmkKtQgx9`)nw6!3i%<5*3(wJh!3$SX&TknuRxOv$7@obd!mZl}408*n
z!^n+z`l97GUp~vJwS?14o)@mJ)5|P(ZtnB=<10M-RFAD?c;@2r|Hs~Ywrg@-XL|Pz
zRrQ7wJ7;8oNCdzD5+pU0G?FH0#^ERUlRx?|_>(=JKjO=lJ-#ko3L{bSa43otDFPr!
zHUf#%4WPSEcb|OTP*pql!`i#5PNM;kGh<6KwMlgMId7=6_u6Yc>silYXLpa0_WX-4
zUf|+pfr>EEjxRklW;}{)&6nIg@<dlKQJ&`?G(7X*I!Co<zioN^;VF+?teB|CW0xmr
z)39~(fPeD&O`d+RV0~0_v=0Y!jW-${mppv2q%?4AYYAZrq2SCk@Wn^hm`um4PBf2S
znb7#a&D}$ucyP+&4^*s=0*_o-<@U}Yl?wdJuU_H8$pS*d)V6%-@iitR$KwxgqD<uW
z-Cdr!u+FW$hIe-?Iv5@}WAV!wXV(qSeeM)RrMPl_#OjLT#+^Gn`|K%Vs5yT!@U`bo
zvbkY7v1)ke;wrlUt3Xu02Q`nJw>))W%G^ipEENZb7L>5>&EYMI>wlfF$6v;1MJ9!2
zQb@4gG&N5@^%P%w>7`@un@%RY@WS(a<;52vM&5h>8V835T^JU8=yu$UcO3Jw`gKnX
z0q-2ozVIbZoH$9_G&t`iWO0tBX&?#?(>ASqDq$u~)8L)M78dEwMI!(JAOJ~3K~zO#
zxmeQFb!VWI*7E({F`Lb4>Lu0|$!N)9^UfthAf13h+WBKh7*qn;g)Si($hP(3`6Ul@
zxm@DC$6C{Q8Oz0j<+AP;bnu>K-AKnJt#BcvFw9f8Ep02tc3Cgk-P`5x@Q}rFi4T%I
zXq%=3w?RD1HsMJ=pL+_!r0cUhZ><d>$i0M!Ydy}jV)zm;@4Zj=(s!O?h(SPqCnZub
z_7sw1%A+cIS26cU>=O_mJvLFK5L3EQ=V6Q_7mP8qt;3x8o&WxSJZe*;gnJAY>7hje
z<5KbTqpQ4kbBE2<lHdFMIqvT6vAuhjryg2`=7@(bt?=C+U+3E|e?-&FdE~)$wzm)X
z^5dtuy;Jk2e|v{tTsz{C%Nwk(Xg;{LB<K~qYkBH|<;6!&@#nAH<hwuF;c#cpOHZC+
zXMfKABJkGRclq(v57}I;xOk!B@L<N*p1;EPUcJf7?;NsquwXngT>bEXzxnwQg;__d
zinjG^?QAh!(frBxZ?U?*!Xp<ZeCuzvc<tT5;r@~@Jh{fvY>O8j-Jo6;{OR}aaMTzm
z6kdaC9kat3&poux#S<fD%bML;%lS2U;fYiH_0=8z><2d}Mw-VTJHZFHxA9T)`rEtw
z?Q7RLwK3+(#W9EbbH4ukCBF0WhrEAlo3B25f*-$gi$DCqb#CqL^X%j692_2T<?JR)
z->~#8&p$BX@~JiU4r)I4*aqME=??$#r!zjfeaPn@ngEBK*c{W$7Mz|29=LptKm6`Z
z{`QUAJa~SC=~VH?&pu#O7X0}uJKWw^SZ#<pfG)&fUHj`k3;P*EtH`v}R7Sj#x~_Tp
z$tU^x*S>b&_it`&@b#~Kjpv?wj>U4$_VzYS({}Du7s4?-e8!IYGBNKR&wcSl&YnFd
zY5zpujwz$mVIK*<^Ul-Mb!Wg7NLzMsL#WD%swy!`OHCcBTcD%`txz<}CG*(=tz}_l
zY)SO`V`l(-TD$<-T8b0~i}7k{np!-$bUh&%KA{*0j^;w3@h!8(g2p*%P(lLdNydZ7
zvaPAxhBk%98N6>AF&@E7+dk(Vt#5IzrEO|CW{BbmCWD_<ew(IYxvXjGMl$8egAGxP
zX4AAR=5rQ{MVFb35nR(!H#II9^%!Eei5w%KMrlRYHVw;q*^zR+_Z<MA?^XVM{$1WI
z=8J`dghR|zJU|HrLvnq!t$6?Lf-e)fasnnRjyK-A#-%mQ&8cC{T9y<%d+99ALF5Y$
zKEPxGld0vzM6q``<E?88A}4V~uKs+<i=Uq`8qJxtF5v+a-n+iwqmMMz<QyN~-Da_9
zIB~M%=9{<q{G(^teEtk4r;%m5fB;)NHP?3>p;`mo;L0(!EU3zn2vI~!Fe9Q}C7O!0
zX~~6?hPOXFVAf73*EYGndzVM<9`WSE8yqZ_ynQ3m>M3QZQlCPLqTs`=1%I;tA<sW`
zlHdK>DZcf+>jYEq^Q}YPz1c8X-{jUFJgyz<lZNfB1&=*=mJ`oxa&A=-qN6gAt-CYc
zyEEgFE9*RPc7?s8mh<ONf^RsvTCp}RP^RIj&s|{sf<rGB{P^{4)=#gqH(&6<orY?B
zn!AgAb`Dz}IKNKQ1_~rQ^wT$Y*gJr#+T_EVHJ2}VilQXg0!mA4G+uk5Kcq!>-%QJW
zMg)vP3asNGLGw%CU(bF1Sw8>lv;0s0=HKwA|NhSsc0;#YtJD`@nB?p2nEY>4l~^NQ
zuPp?}BrW=kr3uC+nZu@4DI`lq%sY(H6y+otIKir_szfOmPpXbrl?ka;RbmTKk}w$q
z0?N_?ks=DJ(xe3(W1zHF`cbxmIhJL~Xe^{$=NyZA*@d4FIhxH_EEde?b5M$6RN?DD
zh@O?{N&?pD7Pu`6Mk!qLN##{bgG<4cjY?szJfkepQ=+g&LRTLp%MAwSY5<Btqm+Q-
zt#j1PGCf*Nt{v41$)?7D)fQ6~Ear}Su^^Ns)*3WgjPG)Z)<SKt#$r@zNfKqFamjnL
z#&#rLo$kL*xS4YzOHT5H?J!2~pw58>%Wj+VnyuX#=Qj+St0S(yx6RWJp5^h2XIU=6
z#1X*-+SU;Dh}|R2Tes#M)CG-i2+^ag#s}9mq=*`n@|YNi&Zkb!DN~{ytyWCRiWi?h
z#dut>H*-|VQ5c0q)3yrlD@0k;p#qp_geT&`x`>N0xxNab$LdJyEWrh$n&YS;L~JNH
zoWY`QDPx)FSwf)GTH#d5wvT-4wL^X@6nx{EbNuY>Etah#M1wBIv>~!=9hKF5{R?M^
z+OT`HV61DV)rb%x%SO{WIsfG{a4-*)szj+3UU_TIt({2wkm1$0Zt$}YS~=GxeC2Gx
zyxzry8eg>3Mzc_gQB)`oI!ZBh+obzo3@Sz}EzUGV0xB3{)F~nCQS=>m2HVvq3`vU@
zR#94M@s+Wo&ypSn`03BC@&|wLfAGpHuTT~PkUVA1hM8z`hAsotL5jbX%6ZDfic^Us
zjPTz=&|RwE7KWmf<Af*%$or5&J$a@ok&<Pxh<D&x`TS^HCPL^C$C2<fBsJVjG>r)m
zud0$5BZW?>eeZ>wnnFfvErl(pn?|s<^u1+K&@5}FlL^&mL{W-&Rum;=QS^0<3UrWA
z&v{Q-mgrI0;dUxzD!mT`-y5;QSOKi9#TrZNTDr`12%sZnQ2<3U)&XO*C^5vGMHPC4
zH8zENDZ}R^^KXs8q%3q<78KU9T-K1hKNnlH(g}!%x)H3-s1((uY@$M%ujFuF0Xoqo
zN?Twv$xVPn)lH)Opfbqm(Y$+W$v=PoJiGgj>${rEXFbn7eu+Q%;WYxDYr8Z4_PyI|
z&yTPutcA@<;KIojPMw(X^X+|BRL$oexWJ8_hFR?>OrQxZg;rcSKV@yQ$KKL&V$%|e
zKsi#ZuCMX$zw<V;nc??ey1>M`lv)-OD+WIbXc!&-s76&2jB@zYx?T}kwvnSn<jT1T
zZ+~!?WqZJxiDPr)6z^Q$;ry8q+C;QL_$r7;fq_CvZ0}pe?ylp3lWQ^&m1I11>aOd2
zWPNjmwKJ>y*|*<h_n_flf9(pB(xRB5m10_sm>o83EgY|ZwBTrafl-lWWYHdsE;&4e
z-Mz?kIwoq*!TyqmFK)6v+GE@8vuZr6<%He+hSjRV=mKjzQOS;`FsXRh5DRIsRyvRJ
zGQos{Ca%BIW{Asv!jOAdS}g`Eru&olSf4bmUBAx%`S1QOzV#P>!T$a}qiU4W_x<5w
zH|LJSyFKkd7Q|#UW-=NPy+8ihWJt79*c93ZFB_GB@)2VTf=;y3l%?tbkW`xEoKG|Z
zOAJO7I#R2+{8pnysyhd?AxR!sr76lvcwxzVkr30Nwdsr<N?}Lil)V#=X=F>LBau4F
z88$Ik1xo1@8q1aTc;A#<$(g?=OS~8bUIk3@3SIh4>sy*2SXNFr$okjf)g+37P(D&;
zX#~d$-qW@YpEd*ryt3)aRKn-B6^|Ch;o%|GsA4i6cUjDQ6H8rSjd*hTdP!?I(>g+u
zrBZnwL<#9FYA{caCj$oaSAjCz-fJ0+SNP!Pci3N+>@EzZu-w`4%xvWBe#5{1jR(1T
z_lQ!haC3Xc&Aa;?)QZnPahi?w14ed*as)qqZHK5Uc?i}pcY(<`@H<~U$@amF%~Pj%
z@8$v5K3MSEU%AY0f9V{pgH!8@!=pfprFI%^tu$tJilar~sYfU595uXu!_jE)q~;J&
z<8;B>A0F|W=QsHMubyOo_YUVypXKJf;OBQN=PplhrpD<+BGdt&XaQe;Vgq9&qjF-h
z%1?i>hmQrQ0^Kcmi!udAM>Q%0zWK$oEEaHjZAEnIb&2z!t>UA@mJe<(_-8L&W_xR&
zX<2dONb&0Hw^%d*RcLIfiQZvC<oec}D`!{vmoHuBqrF2;O(!T{^78e&eEG>!1Uzks
z1dM3AD@DN2#FF{UGIxrve(4OayzjVi#}TPeu|OEPX0Y_{KO$0kRTaI*@M)3c-R*7u
z=#T!GKl<Z8=ElvNjH-&2>GVEx>z<>kK0DSOI~k&~EGdf;SGFHNzu2?+^3TVn@8GqZ
zn!o1)F-l7~moj=v_gt;~@w}*v(kNrQ%-8VSIv$s`C{>|Q9kn8my+_2j8IALvLJz#v
z4nNMNMm@jJYn7@$@^a0YIMW%1Hbx3<u!Th{0n|f`I4nW+nO0J^j-dJttH{wv=rW4l
z2OM<ZxI$<%Ah=WvVjPR21R}4#`eVNHo$v5lzx~_1@ceU#p^d$#ILIC<MWTJE&RBs|
zH|P|CXP%vFn@^xM3=~HbsE;w0+K>2me|?+Xg9ge8S8q9P9p2y|j&MQo@|#NzE?P#_
z3fr^5M>~!qH{p+du*<ZJoIEkbN6klX9kDwfp-f2#8bgbUmaFd{@WzJ+Ojl2E{cXqf
zn~u7v_zyqY<<j{ToDW=m|A-J3N6m;IzO{{0(!^C4maFeCn6;WljqtW1q=hwiWB%&(
zh9zs%i@<+)WsfUor&xWG*RHj^fBT3gRJ`)mA??yYp$RI74~o_Y-rriXxjsfIxc1S4
z>sx_pTygmGB~BOU2#ZC{t5+Sf!;0B#kF%#I)HS^E-XThB=F1V^dt;ZSFKE%c{MMY?
zdoZ08+@3jZZP!qY`Toxjm^B`4L@z8BilbQY-K#SmxUxbqKFLShk?S8Gvb&t{>N`hx
z7cu(~Y0#!1D#eZ6z|K5S`wd=sCvxsgiF068O!C)3$f%|OU*C5s^m8I&EmSEx_({fU
zxm@z+-}+X^!?M;MGgRG5`;^huI%K>yMvAheC<ODdreDClZM#qD(Gc_<3>|yV?b!S8
zqqK1EImg5%Rs*9lTxfJf!gK(=oU=yR9HM4*PFekxu~McJ5}o7Nc^y9|9l<B-(m@?S
zuo{(&&9U}dgN$5Iu{VaOF5{Vxm$S6;w@t~`NHmd96v-n?A$AlFmiM0TegFGRCsUq%
z_8B5@`pjuw{K}VETU`YZepv$h^LhDHzLT@T5)Bkx5`vUr3{LJ<VJ+Hxtd?+qq8{sp
zk#+?N-oNY6ra+f)&_?#QJ%ur-2#ZGZ%G(Pv8(t|3MsfGRvlRmG-dQBVV~I}W&ycLW
zQ3bVH;p(+*tgZ37LhBWD5xKeVxw+q96lgUD6)*~Bdo9N1V`&a*#gE>YVXP4VG0FpS
zq2QxkkI@y{!0s$^=j~a_2nm2{tYT+Bpp>+zPgjjr!kmBmW(_x5NaaSRC}<nluO;S=
z1RCeLeK%n3gsp?XhuceH%w-yqu07oK7*k@Dry=szM=d@yf^isw(IvMJBTAJNS({yf
z#&Q%QKY6=FsTNXKAX}7d&xG5eS}9}7PQg*FI9wR4U1fK!x&8Aw#t6=#qhN2Cl4wel
zTYicmk$GXY!s_D-DnbVe|MmC2$N%=f{{cVw$!o+InM}s?U-~J=;4{Gc7y_fwh^nm8
zvmU(Glegq6ehED7Ge^z@9?JmaQ&b;2PlclE*`BExdGXU5j=rw*-uGqI&v^VZ_Zvo~
ziVud?n(Q=@JVR2r)@5TAkc^^9oTeD1llkx-#&q4e<(&fQK`Psn%x5M3&~jOG=gwVT
ze)(lSxPG0lef{fPx_FUGmoM?nZ~hb60FuE(fid!(M7dt0N^&KD)`IaJ)6EJVQy7Y}
zB>2=5H5cs48&hGh_<Y^{=*n?a#1^Kz$tHzP`6Eg}Y4h%v@=pqs)u{+t3=8Sv<>4!o
zw#?gt!$pBEHzdr<6DE?f8N*J<vddeekj_5cG@vYPmtKvzN1+CTLaL!PS}O`;D9pg!
zPcd>o>s0?jq$Bg8as__!JXQY{D3e;lO9O_ovi(Dk!pApCqg3b?MPV&PLR2ztXq86F
zERONL#b6i536n~RIz)G`V=h*gyOb|cD<~^F44NeQQH-FNz;d5Y8u?BXR;NPmzUHzj
zORiu4fdA#+{#*XyFaMI|vSvIUk)>Vw!+o;hI%coBh2D=4BjfRe@p#;Mz5TcKnZ+EY
z_LKg2?PNwg;^5C?*O@tDF{B{lKE^M8l3mS~Cxuz@*i{{SPnTa9zVazH>fVt#Pahkq
zJB4(Ga?DOPMjOz5t!>D1(}O3V5Rg0f&2&z(pLs@wbgov*239ZUy!4e9dG@I%r76o|
z$<Cd-__k#<9x<vas;WxZU&6)HIbv*g&Wh~eX4z)ldD2F#9V1&D_pk;I)qRI>UfM*c
z(^7f^qQVe7N_j#Q1EiFKfRq{Nh&VzKNLd!8h-iYg*dp@b%{g0l3<V|5H?quQN(dO;
z8_{e`6ex5mnwGL2g#gJxg(TJ{ooRGTOE_<Wd9zchGm45#<51|Rl0HLLVw4Yu5K>2w
zbf>IF8F{bi424eEK$<*VSR)fvtCXgVIvMah8FXsr7>Ln}XXlNufIE4U``|m-oj>OI
z+;2(UEAj@!KrF|^YJxhrk2Ln+o3sj)#-Pa!ZDowAidSEKm9}ju%7V#cGB75e=Ivzj
zK?mArZ*u5)fM6Zd>6Gzg46*OVqjj2N3FFAupXFZecl7(-nPh;~VE;O1bME<kf3}}|
zeaAkUAO0XryYJ{=n9s0Y_j$cH(#P+5ByVE*Y!wWC{+Q7o{2h^J<J0kUI>&sUrsFYB
zKlQYbLP^}YAf<N8#Me?<QQ9IUchVWezK$?&P)h6MfgPXYnO_%Erq@ckGC#CWyHSyi
zvf;wXl9lP0{YA^Qtr@L@sZw0HIAU#c%)w#Jhg%Kvwj%l^=T;SEHRblsOhf=z;Ov<-
zimGB~;d$@Y5*;<Z(af5fvnL$qPFkEUAz1eIT5j*PxFFdmF#sanES)|CloWzps&ZEz
zhXFN0sfdcT7_BJXl_TQu1*Ifx%#Su2q8bs2m^deD-_7C}1M6#%E2q~*_PAd1(e|AE
zwvh7zzz|~cj`EX<AvIoAtgdJtzF6`4dk1)z-QSQj_7utmR*J}(bB1bS33K@1=8R>i
zWOwYQjSvGvURlGZ)Nic-g!^fXr-=uMcU7)J^!I-svIwk>jI7S0L&rLK8*96aj(l&w
z33T;?158x*ihk*L25#V$sI<Y!d=9K{th2eXNlwLgvMZri2F->ilOur+qsi^ZRFYg#
zs+Th%d;008>_xWT<AbL#HUZALAXz5{xF^>dMxVs{BAsU-*|wyYl{d#^Dn4ejx@nls
zl_Wot1^BY}-x)u;uqJ|J?~n~PboW9@Jz+8?Qf|{5H?6W>Y@RoLxsi0JQADFLrf)Kl
z69zJp#8YDX8=I35nqp<roqOIuhBcl!kq`!%!Tz<O|D5Jo2q>eZYtCnl7{L&D_R)20
zSaP&D<oO5Ixv*~e?$tXyda2@(2TI<%vCA`;RyjS<eE;=B9=b5%pM3r#`}>+d`QaXF
z)bf?*&oW;u*xHL2B^kbep|J+%_Ict;!MT&3H*ajCixIYxj7$inbXg%L0$Z}^s-+F0
zv1PQuJI94HmO8Y2c(<Xn7KMW-1=~?2k$r5EyD-F<L<wCa#s;5bZ2*%WY0DFrr(8Pe
zxpn&vXHTy2+{35%_NzPGJ{;k+BTy%IR?_K#6#GX_6Fg_ej>j)<@Xp(JI7&K1N=014
zg(kY;nTMu~#x*;$10KAx#`(=L-@n?>Mswed`CbF{D~%Y4c1#$b7}Pl2e*zezDXl>b
z0*K*I$Bd`yUH#r|>I_<bZ|5EMpBny=420~yXV0ByI$dG8TwoFln<(m_0&5)4ocSPe
z^01ywG}v`lES(pwN!%jm+V1@-8z?7GL8csla2BmKiOr4hYtpfODzfg60Yzat!*;K9
zN*>3${tPzJY*hQtA5R#B<oPetcNjS#d~lRi$#^p9FfSi`q9_Q>p>Aq489S09?d;Ly
z=q5ieA$ca<wq##~=VhggCs8(tk#2uV2EMLqT-FLp&pXo`s?sK>udk~dDn3Z)Dr-<^
z4e6pk&B0X(3;Nl+OPb{ob?e!>Tk}u9`T*}-zsbc5oBZglyIjAuVE<srV~?HX()o&w
z&5~byc%9Oo!UWHA51(S$XukdGHcdOm+A3uQ9A0}OEhZ{%Y&l+iYbk1p%76*L0jJkW
z3Z>XNba-C?o|Ve8I*KfvW@pw=mX0q!w#lqMVs?0lXN30(k0mNasTwRT!Hm&Sdflz8
zOxZt}VQt{#T8WR5odZW5Z3hNu1-4LpaPyF#{-UAOclfOrBhNiD<}ZJ^!{!M?IaTb;
z0!K9%H6qrIQ)>n5Q^Vc)3=?Z~IDv{S+8C@A>?%vVIaTt;^%)_|Skw(S?i}$izWO<S
z_Wmy0vm6fR$C&>cgoO8bcAurvu2h7LOCn2ipM@k}p71N92Etx3P0oA5)WOR+&gz1d
zfis&wpFg9}DViRH1BeGz79|f{c~HddQmtC{oQCpa8IJ|9T2kem_EqS)OggJ9#FU*H
zB!DFS9x<h4rE<2)dnpG}$?H%`Q5B_}OYkX_H<YEKC`)-V-EoIEM2z7vQym$2js5jY
z|Hk7_P$_jxsX`^sW@;@yiRon{s*UM*VIYP%S}CV#V-$@mW3bvt8B8rgfSKGWg~+KS
zNs|OAlXs@Yz-g@sl&OX>hjj7S^Bz^B&Hyz{!(u*9nw)}DEtd<5qF^+hr282<Du$4G
zTWnDfS|`xb&>ikDgnV;5PhPP<_n0t-(Bf2}jxB2|W5(r}+k1D3X2P9A&x5Tagqpv(
zI_L3=E$7Z@lr>yAHRYAJu5)UAiq&Jbb{x^i1oT_9stBrJ*(#0}C6zUd3PV{edG4tb
zTs&ndRpjOl{NN`$6oujQPoHG7YKc|JTkq|$IBa?5;tGvZ>>oOg<}h<5?`}ymjmxJC
zR;s|(_L65GKg-g$c&mB;7YBUqp;MgRm=e6_`mG~geQ!z4h)k{n@KMu5#o?l1Yk$s}
z6YE^KVtL`w4UBR$rsRjO?{MSpf+sJG_}n9_M6I}c5ZJ!$2rd#r!{tjWoI1V9TW{_Y
z>xfd)A92wJl-i&n5W|enx<M%M|H23!f9eVBXbqMJpzdY5h?Mmx@!j&I$foj_&&s6`
z?jC$9zb60xc%0;%V{`Kak3Ieb^>W!2_x36YbPHV_3xE56i=du4b|1w95*$oe>mFnB
z!jke95P6l%o~HwakAJu5S<#16gY(NZh1qKeAq+yQjOnCeWGj5W;dkUAlmPj6XRxv(
zszqhNX7RiHnRL9N$0GXchDvLysuE04Yh3GTT_XT{QkQVf;k|<-D`k|Cq(V%a1KsV!
z8k;;U1uA>9_dZY6(HF8um46QD-(@LeSz`<+!NBXL>CVS$r4j(%yMKAIs4fGT&Pp2`
zj<s>i=bu>PgX?!FT8~x2sZf+OjisG6j3a0-N(c%^SwNv{9(!PgWf-wGsknY?$*b?o
z@hLkQLqTauE?ih)|47{G-JJt2ovzrR<q!Y-eIlOUdFcudT(aES_Wb<A8P~3FbMBPk
zE6<+iZ+>vZtG_s8|LBnK{dkXWJio?7S>C%Xr6e2Eg41iB`R*alTwdcp{$z`n-@VIM
zo>-%;=lrjKc8y5^|J64hVf#q)=2pO3EmQ^tRT-F!7hE`7arV?Y?_S%Zb_L&g<&ayq
zZ}88*agHa>tl{Q6Jooq-ue^1KtG5EBt$6t42;~|sp71>QK*`(h&REQf<XU^2^#oNC
zePB{FJoE4gKHS>jXdX~%%>9PSX_sS5^j8?(6W1=_ue^kP{SS$S?r=Mx%Lt8)O8C`4
zZt*_Gs@L=;B`8vZhc09robM1^&3MH<i?pt5e&d_J$=P$~sOyHjLONqLEK0s#`i*;!
z)xVxIx;YdX&i&{GZ;?e*re-YJ;P&bN`yC?}Zi~a3aW8qzCkdLannd>xuip>SJ<3Wj
zIXp_Clc<TxFS7rZ7k~beoXAiqTvo|=i6Ux`hlw$j%wVZU$BsXpj(hb5J)lz{m@bhH
z|Ble90_Qr-971PrD_@6AOoD8<hW8C5G|!ua){60X)ZvmgX8j)Sv+?yWNhwC_IJMgH
z#b;0AmJL6CeTOUOr(hIH_033?Qc}>E06`Tam4P!S#=L)LkH7lG9;a3fzxU!5K01ti
zxK&dqi*xdjPfiOSJTWHN5zWyNUw-rydwVmUd*}>W8`efsPOLS&{{8`l3Vh*_GptP<
zYa^&eil|G1u25!#QPQzmGa#fzAwljP9`MGsJtm`y2T!lC+}q`=PhJGqa(ZpV+M2<C
zbU<N^ROh#zCm*@M$@3?e7`S=8=Iv_^Z8Vq8Ou2ma66dChdIry2thlzl;QiY*Rk^`o
zs91)UD`%z{dyyZ#cgXb{ifC5xI-pdWG9fLilO<n%@&qGe_~B2Nv~l{0iKYMiAyg0d
z#P6f#JLv1*PY=AGY+8Yep5Xg1^xpI7<V5o1r6)*grBWT$aAF?+y937)3q5+#5C5&-
z`Cb0ifAilSON^<m<R&l3-WYu>-GA&n<2}EWYjN%q^uPul+wp&8)!2JTqYMnG>hYjB
zOgbn{2rgl+Vi>w`zUy$44S(;+GBCIuV?^~vB$Gh%yL>vY4hd5E8R<dfKZF+U*?@vb
zp-ZXF;O@oD6H8Lk#Ga9k81#^m6<IG|r|XaD*?KQU={9+k&b35hx|UR<=sm%^&O?<F
zC9ok5&?_|z2J;RnCly1>l~bN)A6e(_UdyZRE|}{LmL#=66$wG1Q_*Q%FF_UEP7^}l
z?xE-1n+qCc*_zedIA}O?y5fV|NBCHvtit=iE5EqS|NXN$MKxv|8>({5c-3;om6S@e
zSVV4YEqLhs3Qt~M2UlQGRMAtYCN;TCe5oj4T~x9i_!Jw1VphY_DNasdV^ZPb26j?W
zJI_0}9k;d{ip(oh;%eNyv&ZY#cQ`yy9PF>p4d?&>AOJ~3K~xp2jSHT7bi!(72(DtR
z0-l<cQOm8PNE-@FknPer&DzR@t)nAuY`1v50yZQJt01^Jr#D)@_}Ch=*@7RvRkLuT
z)Y;{@l0moI4=2;d#(lC;_Zz_x%N3e0{&$%3&!KN$MIGKjHAm3S8CQYT)spB%4=IGu
z$>HX3LzGYjCpy-iDun?i)m!Ff2~x!`^<ueMfwcu?RWY4TIeYdTpMU-ZzVg+V7){1B
zbqmO1j|7aCBui9~oFO6}l{CzA1UJlXb<0!r4HG~MwsWtc%l9;WDA(R4cd=W%!#cx!
z9Qm8hs|Yc6onlZ4D0iL~x{Relcu_;in(iD22Cr*!;yu1`seE0bjf8sQsrgR+1wg0&
zDP=KckO_?aIUd8$6zQD$zLWWnuB<W3Z7Y$#=``r+L*qWVLYI6|X+Ef^gvB0}(4uhC
z;5FUDswnWf-;@e#?vY65_#TrOR_Vz(s!H*NXEu57y)9mQw<XvKN(bhP08Pv02=)(V
ztgVh1ms9qZ1s#DgYUZ`0j*-#WqPCZerZ6fLv%?w<cs%F^r7gi$M5{ns+6dS7=e+UW
zM|}T{yNs=7R1}y|!8g8ef)8%*^YUAJT-+G(doP{F#~Q5z!8OdAn!~o_<SNh{(Rf&0
z*<@rjD%BSntyngS+Xpk=e&;Sfxz=E`CuoHkZDNa&7(XBunj1TFu6@)H^^|BV7tR)3
zIA!_c?|sDne$9XV;#pQ#3Xb*yr&la*xh1U!Ydi+U)%Om#b-3i~&tKp>uij<fL0PO2
zy`d@_zVNvTyC3ay_01VgF(nisb@@qKNftpPFQQKy$F}}YeJ8#JQ{o@^2LAF(5Ne{E
zGg@x*&8JKL)st(q`+F>wOPV@q8adIL3Lz$`;Lw$Y$N~(hs8(aGh_ID~r7T5#v@8pX
zqGU3iGM!EsPo~0XuSTM5P)c}QFB`#QVx&pj9<0W>7GtHjIi?OwI^B~P=!E$~TKsZe
zl048_It^udgt4}}T`DcYEGL|?AR*~$d@8io#>gh<{UEFv-u)EzDe+3$wk0CqxAzTA
z-4Ls?lYGf5FZWGUnGk$zqmmztDQI0_b~KX(J{nP!bY7oNeGR03QApNZv3~5m#1N&Z
zzwsj8CqTboLDF0zcF#`5<lRQ$RD}fGXIw5TYFJyMqe-+0Xxav)6lGD#MiP<?bWEF!
z)>u^}?>c24L!i)B_*oc&i}==K<8U5#?v+aFfZ}^P?>W0Z;?jvRi=C3mbL$ie?jCxs
z-Pq^G)`D+7dyexTZSml_4Q}tWY|kvwfJ5PxVbMC?e&;q{dgK%*$J?y0jnQ?(2Ol2b
zLJ1}iVnfRW7n1;eQPE=g@jF{Q|HNskv1i!?)~Zwd?EPK#j#?hQI6<-G!nxB-rzP_c
zxxP2!;R`D~HEX$X(DKLwB`-d0nIA<SJ-5p4U70vuX<}P)&_>?7G2`i{FJV@;g~eO0
z@cQ+d{iRPGYBjAlI4YD`A*wN61@0^z){OYl6Dzo|$^)0z_+Y!?t?Lb6d0~@(`bEp_
z0}pD%e759J8Gdken-`uneEEy(eD~$Mv`vYQmJ=r|4{S^*50_NWuR>wiTSnfz*3dee
zN^XYC?jA3?{}|*I@3mK57&iD_2#C(D0u5ekCL0?({^TVtJvgHB9@jX02nl}(Y3o!}
zm9%%0Zb`DsHcdm*HsV2L8Qd6?p1RZ>woSuyWkpi!<OM2Se(NK_G1|7_=;(+L1B>~b
z5Ck-Lt&>wV0y-CEDW06sESF1+HjK+EwYn0~xw5K=su1ihwjG|M#KO`f)lL_3YbnoS
zS<^N(g|SSg6ZUrZnJ?#DzI2(>r%rVgh8U#nSf&kRZwSD(EsMHFXcZ>)0rc$Oxr=KZ
zqtS@9^>xak5Kvwzd;mWXG0a{a5oXPjrfoX2ST`-pdP&_j!W}Eil#yF>8(dYCtgo+A
z7%7SIsq1pxG&D|BTy0S%)d{$@b(6!xBMMtEDoW0sK24S6kek-CzbE%$b$uOe49j}i
zlYmvEs-*CHdv}|gw{Eeqeu9;i6{^uly2j7vtgcR3TVJEJ1%}*{DH4;iY1=j|mrI-z
zJkzQuQXE0Y?&5WfbS;4hXy9nS;fGg`sPu|hO%-W^V#$~vy<78K)SNnVmTOxzZ@ymx
z6CiMR*D{~aX!Hs%zthsTGftgdV{g`S_01y=o3g`8lqz}i`V#MT%IXBb@Xn1$X<IIx
zzCi6@XQ!q1@bhak*33yRY+PdN=A3ul*`an*-n>>*=!z2?r@8*lHn07B#+8dFp@i>V
z-C=puFt10<-`K^e0;d(PeX!3#+~e}u6ZkrCd%I>?XP#EXE6uytmoyGgV^9@F!=2qD
zUi-zIhcBFDe>UgaFK@ByMtoGSpk6=V>4!Erb8^hiZp)nmSiZf-+!uWB^=%%$Jf$>H
zFXt$2I5_gW@|Iy*PH;*SqQVgfF>8n)w>mLG{8Y!O5AgeT;G|ICct-2v9}VbGb7Bl<
zS1S$=k65-&ddvlnHHH|Z(~96RCM~j%JS$P)j3HvINQu~icDF*h5yj*+WsXjcr6i@@
zdkM>BE$yXJxK!7*7?<QhDWxE>skJdQ&QVyyq^Od<yXZ1aMx&14DA_30Q3YJvvRo`h
zQ8R(@K1y1>?*Ie)2L~J-9kH{!%f$;9*x1~}THAG6R$7{7w7$h!=^eP3&k0e)>Wr~T
zx5_b_&6v;Ulx4-r{+<*7Coji4N5}$zl}OhJ&gt3PJD_Q5%Bn;u>4?+1mbzJX5;;xN
zQrAmzbC;&6sYWAKR@brG(6mh|L6X4FB@UUf;@Rx&?XrJx03lGBf`g+&s!BAnobw#c
zj#$)7rbqjP7}?w3r)?ThZ!jutTySu3$j#d~nNC)juC6edOhpXQdp6cr+1OZTb!CN8
zTY(9T!L^Qhx#WZEA8>edh;xqB)m7B9|MQRI*22(g3E{Mog2-$o6#|;a81St_#n45z
zT8q3(hzi1zs0(}>vAQ4{k+O)i#NdP%6Evn3a^+IBI9pK#E6jAOMFrD|<ZW(Ls*<<o
z+lawol*i#PWlGul3KK1n07g^jKnNP&dXz4RTBF+;n1Hhu2dG$}qb0CF7o`}25Kuu=
zX+!iaE;>|ENLf%?M<P9IP^yF!eAu{@&NC>y6C5IFi!U_Vd5Q>Ld0I3<mnh#-8IRMB
z);DNVVpNF%l#j$l!j_;#oiP|iVO4VDKW?2q-C)7-49v%W{^Su*?E$~>@QDB6pFPS+
z=Fm31M;1US*I^%>RBsekboNwCk~ztlJUsyOGl?=wltBOW(jtC{!3|V2k@?uRuGcWn
zp&QwQOUFpybk=DyspWgdX^astH%l!O>AgfHv@`D<ZPRwC_@<R>Qz<21SjqJI7;(N8
zITq(S(YzR?oT$jv0Lf|6MpM|L1Eez(T{PB1(vTN}FZHytak<vvT#qAml>|zG67$rx
zs0VzI3~b#txEQdxRE8c_@Eot7G%31@K4m+JsKo2)<b~4k(NjA|>%_3T)}e?rtz)^Y
znJ*TgU}d_(Xf*D!kcF|L!l1zvRy4AbQLdLY&9dfbc0}l8ltT&$2M|e49>l1+Iy}%s
zrBPLK+M-T|B=HCppr_KM!wBdXlox+Z*-lePp@`L(7&S&YM71)e5}EWx)}(*?ZURT8
zP^G9vc(mYLD3lJONt6IW02cz$K-7uEA0nYFQ97WNmG<gL`HWU0RLl&k0%HrgUaQa)
z_|#6mOP3o_B@h5nc<f#oloi)kSu0AVF=C?h2$Y^{f?pXGL0dx9C=AwC5KU_5lp1E1
zil_`(ImFNxSl@U2GN3yBMEs<m?;SBJDx-Mp>?%_{I=EyUB@?G~pVWv^2#A{A5E`v<
zt&=uTxkgM5ESaVb;1wQJCoz%VbL?dLbCRr{cy(ps5#@}b0NMgF5ARK9tUDtuFXVc}
z5G1puNY|wLC6U4M+(bbQJkxy6BIhd$Kg2*AT-Q@C|DnX9%8>^NlfLb{7;tR_AkTP?
z${sN??|k(5LI8C?pebans(g9F+Ct}Ku`8`4i=Xgmtz`|@ZA;@?0cy2Qece+DR7{Ud
z$vV_&gHj1x%OU(UhnVTwa)wmAVi6ZCY$*nMF!FQD8(7BGG>Xz%Ha9mq4&CA5;U~BG
zIyP5S4<P1;IGhm24o-eAUBPkg92mPf8I#pEc%3py-G+a^BHW$}lDXS*UWVT9$X?;`
zbCINm?FxwdQ&$kvu9Yq_MiE#u-8H1Tz4R${pL3LJ)7`ESiD^>zHS-@c4k~4*jyXA|
zGyb{R?6GtG6#Md7zS6Helz1Fd1Lrp^h4K*0;Q4miw8{SD^a`CJs)|yW;5l73^z4R<
z9w24#x{O$QZOG{EP7IP<Pap2)vl7;IZw%5I9{+R~2Gj9;<XDE7G{$3$opC0emsVY_
zt;5=momtMhDNBjP<*qO}E*c&?pK<!R>+xrFXTa<yN!7(jC_<tQcw)42ZdpP)8P5Km
zODCHc!m&HiWd)U#4z(`zY)pxW7^U$?R!JorEBbqO{JgSZ&-4Z*u+pHFS#HuA<Dk4N
z-RtZL=Xq6BnoxwkRhrVcrWFq>AHLfW2Imv=mT<pi5%tG^2VI)BzdiSTll=WL`y`9t
zvmA#{di`GGpzk@w?n*v(g0b8A{P2CT&zAmD&Wt*~NIvCle?LbGDU^3?j3O5|M~O6;
zya*N1QKt>2PlxxZ@}aSyo9t@vUtYw$_bQ|7L7u+LXv0vQBgRA{u)U6aZWk8QR;|_W
zyZU2lE!}Zq@LdDm7$N$eyOmqW=WtMI(Up&>4pD1au)|uv<JU?TW_3?kcUO?Sj&#pD
zT`|>tfl3BO+RERv-Uj!{q|nK0)A1hfRXE7}$`~U$Dq?EOMWpKknKRBtDOAz-5$v24
zYr5Zw_oq6KAl!2gLXhHe(bvj%M2o`dz{JaGYK~q0;J#&**BI^K7Q`;B{sc45XJR9N
zr{l9y^vB+M%>SahI|EE8-_Xy5b$(q&j6lnU&64wLYiL@~OEF~R-g1!J!ezrWEJ2BB
zhgWdippjYFxru47><V-thJr2>=y9u<s$+)jzx+MrE;4jsWq}3>PqmT7Eozyb+yg>%
z?M;S%WT-S#v`!(RMupflQ;jhjw_fv0cQz&p1mF!QNnFL43gLAW0mXX^On=)G^IQ!S
zL(@&k^LIE!tub9`=e-pKUBlWKyYOzX3n!x_uUS(F-rRYDbf1rd@6QC?7>*17DP&&{
zAtXF9t+SYnrpo$ps>i?v_u%-ornxm>)hh&tQ%Z}xOuh^E-oi*kh2uAAIFt_ey#H4p
z>OSt}ul!w~V!)1r%L<|%gm(A5*5N9;3kZMN^BCSoIi>${7XSWARlnT$r2Bj9J#iRT
zOAow4IWC`AW8Er7t|6e4?@3p(B_2)Q5%0-5W)CV~gO_F?XvLy#P)K(bok*j>`wnB0
z&)v&f7r;KKwA|8!H`<^=CUy4j?>i+W^^9~EwLUH~DW{ZhBmv>N(1sXN{a|{YooqH_
zu%RzGGO59b{1j<A(rS!i+_aIJT4GM3(0#Y}uJgV+%y+<IkEzTlH*M%t91>RKoD|gO
z`__l;@;y=vo+VuzotTtL1YD9nd)h>@zWk8MpN)LS^4I;nQ%ZGN(o86pdn%;QA*zv$
zl{M0SK3{vk7Y$0AQbBxKnA9z+8_E0*=C}G!u|WSHj9<kV+^+!hKJV)OycZeywHrz%
z%gDl`=hm56P;J7LG=i_izE%zByPYruk!9qDon2U#p_RetCU|oDvj>)q9>~H_M%u2$
z)UkyeTB+k<)bV2H-gD_ZxttjshDaHQNL^}N2*iZFbhUxdc?bD>LoSTY#|{u_v9_kP
z2G@9M*PwJE1YvC@Yv*I)YstDZDJ$-M=o&CcLZI)CEjSQBe-6eN@uF0psnseQg&aD|
ztnL};(vmCVC6Z9cK5rl9XQqAjEIU6h$h{jDSG%@NT4VND=jLvX44#d2%aQUupSt+O
zDEC_wH$MLCa<R3|VsN>bQjvDtggp%1@B7T|PkHU{=eU2UE9vj3hGhu9o+B^hNu_z{
z)Ec-pmAE)U5D5`$a~>%z+}`^?4kRmC6edmjC@-WQcrtvNq|%x!8-z6BhwYzon3jNF
z(tOQ)Dxra;jVCRb+zj>JvXhS7cuzBm?oXxqrm0E^<t4v<AKXBU30P&B&5!u@xBr~|
z{hK`c=tDek=@KV4H$-^OwV0w3-eafFMFP0x=Wg@Nn4Ff|pp(a#!%k!RmiH)?*yxtN
zTXu#y28GsxFbgHhW-;_0l+i}?+Es3^n~b&Y<-;XItfc!>2)M+<D+)`9QWvNOURS3L
zm!4(jSpmtrlJ;R8G>{?!t+UZI34aW|9@ek*3cb(xb@s9};Dh7*$q^@~f#_Qzo=ylr
zNm68hUZpi1x(re7)tC)f<hb5b2DiJcP@34p6yl`pQa*w<rYrgBcIsma4W#qvndP|!
zI_W#a69FP!tE)bFH_UFu&Nv0{JL8p)$H1$|^F-48N?7BwLyETH`s;7;>R<g8RaJ5M
zfd}}_-}-HydEv!`>CoMWTwfSd2~#?wbiex2p-dBi9&;NGm2jV-ewHYmib3i<mVAgF
z{2%sz%pst(FOUqQYdyql{7J-DP1M6UPi~s`CP~r^vx%`If=d}!o1Uu}ukm=4xMi-F
zQtragki16Os6La{@Q>sF|D*F>qCy9S4UR|7tunGLF*caONVg+WN;>qRLk7JwP@NZG
z27A=ND0SmrBNHPbRrZH&VF`XDi#jjVLGy*oy~^J+ln_pT53#h&bQeLoUcy)@C1J_H
zi|a9@REswVNyr#e_U6)et0)*-eQ>~N?>4{x)D;SSg=@DDc=g>6`N=D<@yrWf5uTQJ
zeJ$O<Ncau|lk2g@V9bD$laHAU*u7y>{&)U6OTz^3QCjK`wH}0qy8lczh+POgc%BNR
z*m(e!=MY-QzNe)&ilR`EG~_@yU|C%>8&fg7s%za9BZSi9Q#noq5o%1KxUrV9C@HIo
z)V880UaIboe;mJVBPwta#yaxIsWBrP35^r4qJublpj|7OfLZA?lFMyE=Z$4L1oYEt
zNP)<BlN!D!Ws_6_b@Swx)VA)tlsI@l&@rMrFUa?O@Hz~O-WcT}8MfGAR2lzrX?M@v
znsOFQ4=@@5iY1(}#!816SF_l8pZ&!V%Y|a1pwybZ?K^Coy+~mUE~@VQq-S63JUW2r
zTD&&ISQCP$8da1<*@cE8=PY1-HduX|EJfS4Nt94<A|azT-3Ajv6!{$0--Ba@NQtLo
zOp(-1=pleE?DuF(2OW7Y2Bs`atSvf272|R7L}A&>cV$(H7$e#mOe&ZTsRf@1{0Y~r
zuom03i$a9kvQyo0Nj?SOzE3#+kK-Tkh)VK+YvYoKHpY}WRLa%(AxYz^T#X=7#8Dg3
z${*;GXYa~~fatQPav9Y{4;}t;Z<$aRW-*jE&I={iwa84(B|p+iz1L(%NljsH6rq!d
z-4Ha-e~YYen)^y6m51EYJsH@1ZBbNE^Evt;=cJ-|FsDwRVtsRyW_g1cO5XbERlfK7
z`&6&J#>EG(@b%w4PgPVX0uCk0B01@hvX^3*rK`GP;Kkz6T1t5;Eyc}8M@wQ13CK1H
z`-w@e$50dn-dib|NiDl_iBk-rTkYwVi6pUe-G*STWx6t9RE^PE(=-i-hlkxpBT5z7
zQ--{;WURBQDsoAa_ddI%5_X0_(>AnD8md;K5vGuganm$JAE~O6Xp<C?8Z=Ukga2~Z
zz+r0i*Jb=l*ZZry`5%OFkLXx)a#gc2GDNqKNf-yXP6+s9b&SffU&?sJA%L68xAG1?
zc&|<1uqSPLG2`>H;6jX@_t6nkA%%Bou?<v$^RcS3>Yho)KD<-C!Gk0X!!e^J%A@_}
z9D;ah(S^>d>hU)t9!JV*TCGq@42#hU#$z6Q;YIdNOnCpNKj!S_DW1LJdE%w7^THRN
zlfvkx#recQPhpRQR1)TDr6>w1Le^T-rs8Xn4Nks^)>NYr>&hg+S`2jdSVSPtc6>1j
zH$BD}s!FuzTi4RGQv0YNmDb1u>AWfLiC(<b;3VT~6CS95#eB|ku@njCbUzDQP!t7a
zRZ^A}QZ*#uyz>s{gqocVv4Hj^Dh7(eGM$WB8cXZiW8u3tS|pNXF2wG?%xB1K4%L~m
zd&l36IlFg99*)nVJbW5eqvs?25<`9Vv4-Q*&iU`lh%r#=1(#1wS*gUsF-bYL-xy<O
zJX~s0FbwCi$Adx&hKW=~mAn|4U*35R4)&<)hVgjJWIRS$%X~3QQX-DFZJA6aj7B3-
zozzMS(Q}A52=!tJXw)(9i4?{ZNt4~XRNJRiH>*k4<8vsMLSChl!3(|%jr7oHhB#2a
z5H40GXDVws`^*cRe)vI-mH~gb<a3XFj>lg54K_D6Q+J!pc$drRGJ-0fMob=&6hj})
zX2dAnuM1nEmBNJ_G6|1OJSma3$=8&@@0_hG%Q876$+JxStWjAd&2&#wFC|<|G>e#s
zpm_svO^a_`m(|oL@q$uV*ES7p+jP|d3K)$>XsuYxmMoSF@gR+qJB>%99>Z%ru4yrd
zv9*O2!N?eBl5w@-`=uSGtAtL^V(2QS37Nh-ZAL250lFFgF%WFvq07&M9NgetgJtts
zM&Q#K>7Qj7e%(CAUuJY6f)41=aB1}fZZ>Dm5}PWo+qR`Bq*1EKe~31@U_7bWYs@um
zsv|cpmkW-<kxWu;7>%lqk7cc;EK8cU;b?c4yLaw%QZrRmQI;i(#e(haZ83bK5oJ|E
zlzw{|`wAhTBb@>0)lWIra%)Hh$f^q=Nvdd*3W!nC43yq02tkxU%pe07b@KLtcuJmt
zR>G`rU1VHMc=Va)Sy?VQxw?WWD)v6uqP#dpX^T!R$8@Tt%`}Ih<B*+)vb2)*bZs(1
z$xvxS+xqnR4rJ`GpZpoE4P{v*<%sN@Bq<rw-$$(_jBJ~hWmDr~NOY6_c{<k$AvPVy
z7(+FxI)#j;ZfM$?q9~}!3YGX)+GxsAN$bUHGAaD6MwJ-XR*1!QT@zBFwrd@A(+Kdc
z4fDmEzE^a{tcJ#;b4L;tU-H@L&<Bh86Uk<$T`2!vR2|bd$UCCyWNU_|ad_-|O-^@)
zvPI@S{vXGGsgXjhCbX>RmdhI>^s=GVH57)nam?p)l!C=#fi{|Y(O`_FtV%}JsGHcN
zRD4r6+`fIAx~{v!D5aQAr)Z;@j3=zEt)i6T=%}WtYl^bKmPJP#t?QbV>6Gbo%F%4b
z;n5LgU39x&VGC&#suV>EQ!;<5O~%MMFA^}NXoGhQ?m<=zBBd@<c1%iV3R|F+gkzAv
z;Slffssj=kCP`*tjrJMWYQpOJ8OGy+$!N-Kwq(AyM{)90TCjaG!FDPJvHP76Gd&PG
z>d5e3hGd+D=alg&pTbv@3{~!@I4EO^vAYMu>#^3Lb-`#fX6%K=;F4xp&a#rhefn%;
zQA!ACv|&6N(WX9yxd-CHFNF@F4Wnw*RR9#W5RWiKY$@N_x|X`GiNqw(DA~j=v5;${
z7~HPxDo35nQh>@RnxOE}Q<{dht?*HLpAkJt(?xD3S$;NP3lA6;O+aJNLCPdDz$<No
zG(j1(iYVW9K&iYeQZPg*a@D3ltJJ9AKJL<IhH3v9w(cK7SofbYloGX!(g&`bS>wTT
z6E^JvTqT=BsaPx4sFzC?^M&YJB@wzjWPu5}FCz4Wm6a7%R#pfhuvjec-ien`2MU{u
zZ55Nrl<9N@>5|jXG&M~lo|cb+mFbkpWWsDVV_7fLIg5yl9fWMT2cJ@kq9_x0tL`#!
zKFJVEcr|7+nH<X^LNXzV^qQNedN1O5nX+LrnK8!X_4G|NP*5p@p4Hrb?*_{|du*IL
z!|wiV%CiP_cnB+Ngy{$uTWkOoRH~Ir=b$C)YREN<g6&AgErI=ByvTq~0CtaOWZJ+n
z3IZ`Tc@f>MuE~W;VZToEASqKAYf}4oBO;9m*GvWRn6lTJ#TxT*v$0Y!mERN=V~rT5
zWZYaUT46;|fCBFXjMqw27G<aNm9w=XeXZrV_npDn5~KoQ?`qCnT4isqW`A$NV~?(I
z{i8Xv+7f-Bw2q)GF&JzV!8)%r3eU>eQx=9>cN&x`uu(4FDKL1nQ<PQ3EG)6DVWb^i
zJA8{|mXsz01xBH*p>^4x`#bit{-N8h-Yph9E(Qwcc=YTl8!HCuAp}u4Kuc&f8jZRd
zHfsv3?JN94@H9;yvM8mPOeWnT9FNBxz?v6I+X^e%7%Qo3U1CxQXKf?jqa{mbjAc9?
zi?U~8JxeB1>_qUMm}>2ml2Bz_j+l%mosp4jmUtt^N~+vBcU%aMBx{pA97r{fO3^ys
zwY$nBNS9PlbEQO47P#4*+i$!{dvlApdq^CQnC<UjS649e5%s}cTzP`1G};?t>&06_
zyrrU$tXQTCgpL8<=~)mX9j+FTa-5<lQA#DRsQ1PM3(H|9N&Y--GQlUprb?MbD*|lJ
zLvjp=(6}Z&2ZJe6%_5P)^gRaibMF9hWkvgaQ2S_=6>pbbs4(i-0rLM(dvDex$&uvw
z{mjhW<H)<R?ke2q#`IvW?Vg?;QdYQ!P=q3U;rj}OABx|A-+_Ev?gKBO%+8XW*_oa`
zrW=i;3U%fgmmg-j4{B!a5gA!10Nn(p8wN>KW`rN+=4NWDe^vb}L`~0C_{gGaW2Aft
z0cD&su@pvBX?09YUuN7Gy0+%-p=C!5w+=@fj2$y?IK8a7b994Go}AOR4e#FH=W^EZ
zi$}E<nh7iJAMP@7dpxUKV5I;6AOJ~3K~#G2lJCDgq3sL-r9E20PhKo|_x1?s1eq8v
zFKQ;8;m+NgoGn+Fpo3GCmXq@pyNCO<UCYzwb3Q*4#9q%A^s4q9hD8q;r=c=}5U7mj
zof{KM@zky0;x37R;?hE*jMjia=`jlH7>_M&YjfEwC9zZ1&E&!BJy*T62goK$inB`I
zJ8N97xZ_+j?ebex7rY<t#&N-0>vD;xv`~G}g<Dk>*1D{54WrIe1bb@EX(ePA%enW9
zT!oXd2I)e!OoA8AUOeOEvtM)D8cr@x`Sj;6x&P)v4kjh%t4roj7aZ(5>KZQ2SL_|%
zA{a~4d1V)k+Efxzh|OUHm?Thr)@nmY?4GNrU6vVymx1RG$YBU&(GzQ`7qSECqGvMI
zDP1=sLkL)BX`5EXg*BMcWGx8D468ZLD)M%<T^n)3mdRwSMO-0betLi1d{pzQqVP0M
zGYAq_SYfhLaJc0XU1sVoEsBEYPZm7*{yw)4_i5Xfy<$Yu)r`x42@6KW0wYkGg2NqU
z6s0p5@7XCGer$Qcl2K`xRF=`rlKl#nCh*f=e$IpA18y7^Ji9z&u?qb72M>Ar>;z*y
zI|uOc{F3wYbM_7=*qPAz^(wdDwJ+D!O(7Ln)5`GX!H8)A(m5p}^d3lBOEJKG$nJDp
z?`2Mlr7t(GT0`>s48sZ1@2S+ghBm0@XjF~X`kUgieB`rA^HtMS`dl^WnMC_&aP4nd
zB#x!^*snxGlLS}(JObg%)hc30GH@z*>Xib*WvRl<7=tTH4v!A;hf`*cKBJsiipJBe
z7A((Cnclp?lg~b*oju~^%g3D0YX0=U{<oOvF-1{ftOnnPV5zD?u`RU&6`YRL%r=_i
z##-vtD)x=2F?v?38s}_wl0c6~rQeh3Sd=B>vCG)ta=DBepJeBTVpKM!*2F470qUmC
zeEq{Q^+6-o6K<#+_3F8->smdOQJWr{F~~~$V|%l-C<;o-ED*=z@l}&>u<7PcBp8~u
zWWKQMObR}Ee9F<T;c~X(<YEp-V;<Z+;QV62Y_VcIE^%RnH5Gfi$DCgjxT@vmQGv&B
zdQ$Vw!#DW&;};z4TK4u2X-&yV9k^Vy7!RixEoYa)$*d!c3Opm0zF`zb7-{=@X&X9|
zkxZPir5TKQMKbpn$iEaN{cUb3q#(7dO>H|)kBH$0ftyDK_jgN5A84(^y52<|Q1e7}
z`JVZ}CNEtS5<PZeGyVgy;&IalfND@<MG80+2{As0y!exF80NYeYhu_#GjLZA^6*Ry
zR*mLfx>qX131nu7RJ@{a3DiY3hq%C1TL>CA)%B&ktW}IBgg_#sa)nb)^0LBC#x(U3
zmKThz(1~zauV~IrI2xCfvvZg~;=?<ECnF(rFDUIXWjTtBpRrz*7+v&OMD&?czFk#~
zm3h^8M&k)(*@sD_XH42v3ZY0^S}G6keW0#ux>$zGx<bQM(ml$QP^~d(26af-!bY6h
zWPU44`dwFM-89sV3Z}BEGAOS#DpiYa+qTE9Mpf3@BuEC|gM<w5uU0DxP`VCGin@x*
zm1vb%o&Q3xj-Neg_~d27vTkWZLn$EMvRWBF{%D4CC6jT%>1jtnMKu{QUlu%jcERp$
zOF5qK$y4FvEO5H`oO%iM%2VxCJUbVBFc>PNYgqil3#zflTbP{*ZSZ(0I6t>Yu+fs=
z5LP5bx?iNKJSJ@-d33(h%+{M=jpzPR#lhHu?*NTWvexC@Tw4qVjb0<~14S`Np50=S
z4?S|5T1>BL4Nb%W$5Wi-sqktt6-73=!S%jHQRPsFG!=pf<sc4BL^Q&>X$R-C=1AxR
zMGHnFjqnypQRy*pH}-9)EgEB}7b~88{+PXXNf{ic=NDW|91jm3AR#ak;rXNI9I!_#
zC8M&StO~klf?K0;_r^fz0;|;`hF?UcgD8xLxLe9MbWZCgI%6q{k(!l>TPluy&%5Pf
z2{hfX+NRC|FVWbDBy3V)qptIrvbZP;CX?~n^MeY@)v9K-Tt#nYU^E(OJk_enwp@y@
z%jTs~U_S&Eq;1p2Qf5%sHH-No(#s(IPkhM&m|!D;mLPOAp+(w`PAZ<h^tj*=nJ`=F
zPE=K3FJRSa`SaDva6Z@Cam!Pc#HAUtS32g)CB74$UUtaL)5#tI7gamUqHVCt21|zz
zQ-YM>tY(f6XfhHXbjtTq!E53U8W%w1GSWC3$piGNrmpF{jy4VE-?1hjp7-wDWI9sL
zse%AfAZ#WJ>lxO7xX>p)2gzn2B*D|?2@Zu-iv3Aot<n!$j2Y1Miey?9b=eEX6xnPn
z%UIPrUq4lNj^5>gR;FLX$BY_;h;mQ~eYil5xr*S?kYPge^vLl}2?S22XRKgA2!ZKj
z!rkLr%zpkHTR6s(DQB}e%d-nk+jFdM@w0-@etyZ$dvCKd*`>7(;~jwz=c_(Hm}p`v
zc9!lhk`ju0tuJK+NIWKmWTXu|#a#{8{Ae_an$~LV9T}r#!K_t}>v-&9FzbS@^H{4J
zP!+YOv=OXoEt6)A;o$Hf;+tx+&t`MFw#}wz=R0<Hc9~2kT1#@d;_~v6<!VJ;ujpER
zPt~Z(-0%e{c1Gmtij2ZQg6H7C@!-x5T`PS2curS$U@bxG!GLiXS5r+Z&QDrO(;`84
z12HW^K`EBw{gMawCM?X9k3Ko$Vy4l-LckGA6q$gy04*3_QW}p$e(yFIJVIdumOzK#
zYyqN!^6tZ3maC4(&*$t^aPQVWkDgw#^c?|<2}O>I&L(9fmNZWD-n_<IP}qPMOGpAy
zOkeHgcc2B+!`CC{dH3d+ozf6iF!V+xFH%35)k~Iy2S7PibRp%eX?~dGn47do*eJZZ
zNbHw{gu&nn8wEoGw`~?0eNJKTj#mMa7Vb9ExI~bb{_ZtEXB{?{&I%Dm=n3!0m0mCd
zf3zf?revz-wbzen5Q=fd!JS()pH1jm%@MqK{+yGtWPJNJg>~H6zd`6Ouzo>%`5Z>K
z(3H9^0_{mCrZ9~n3T&GNfCk8Rh$OD7l=GO1NVIE0sO!2I!eFxrtj8(i=TN&$0=aEH
zUFX@^+0nwN#xR@BqKWKTtrCMq45di@MhI=7YrANEddA}sZs0j?8m%CXfysE1y@AeI
z_I7tM)@IKBrfwsbJpmsdcHNljoA(`uM`LVg`1sc^F~x|7H!F;FEanZjZ|qTbHC<D4
z;ahfgE%%Rh32k7toHN~<^5W96xNMNI=kZyCGb`S{V^|&Saxz;o9amIk!TI?G#un`E
z?o;_1X&P*?%k#6EgIz-?ESGi1&4UqMI$G;!gX7t=C3V~K?yZv6!>5lgc=P@NA3Q8s
zT?CkpY3n7{I`&38v|Y!^#Ra3C9h`AA%NctIyNpJb7bi2khlBkIt5r)?2vs@Zv!@Mh
zxXMNJO|~nTmB?#zDhp0s=>+cYm)xCNOuN$DF$y$cF9GZ+*)<^2MTUZ&NKTmnN~&t4
zc*<%O83R-prEVsUsze(jB#_*$#WoEm<1nZ)7n2>Bd&y;=j!BxGUXzHCCGTDj@Ov-W
z>;>JJldWN`(JIGDODA${C5BNG;fDc^mK+#Z$AW<0tq2zl;bO^-EwFg@Zy!*Uj?>GZ
zvs!-68+!(G{uA8J9SnB}wnMNv>0IA&65JN&Bx8ozj1Dpwhu%C^Ew+E(YWgLuOW#@B
z>SmOZl+#$&b)9j$5CV(ELcMoY#lgX04tEggwN2*~uPR~+P<l^wU28#I=OP1y%PCK7
zs~*Ru)v$@tctjb>>@k*7pKm&uB04KcQ4Cv~+L{F~o?o#4V4wFNOjvfpouet%2bx{s
z#;)PxM;E;N?kyf)EI6IDG>ZkhyJK$M9<f@LJU!_U0%8NlM|;dp8m1CBz5xXjTxFTf
zE_w6b4#7`&`s4)<9!$A;W0#*l5$czhOe({>Zyj(l8!?+NDXW5o7ghp0Q%Ae%I6Gf*
zW8d<|%_$(fn9Z@)b7QyU)}4y;)sn?(MOj!(@C19ty?cj@%?`hOyrP&^ymf2D$QZi9
zF}*orRJ8o+X-%tY*cZuxe=<!iAA@+$o5v$=?o|+4#dAb8u;f5arW7PITPU0zgbswk
zLZUDHDV|g}FoEkzO{^@L7!wy}Uk<9*3QX4UQaVZMPmeM67*Yc8fvkmSh((`%q;7hj
zF`fQ8E^}&yn5PHiek83f<6w~!EY$<d^eliFqg9k`!M%GoIV;ZS&O7$@#;oQiOm6S8
z{}3LG4mrAAae4X#A3kCK{w?Ot(IQ$UJ63@<DU^X>wEH?vtD9(YeDnf*2*juGjv))^
zaI;9)^gcvWk9_ZhV=1O-^E*u@bP=)6B9>qa19?){HLlbscVje~JqMVkcbNV&3PCuh
zJo6$wzx=2gsld7}1XBU{7@X#Xk3agHzxdz|^UhP)ip5-Se8Gx~iw?Y_vW~(SE*Epk
zX<)x7d3nBIxs*tcTHwX-{N)OEOQs$?Q@W;Mu~_in)(&0Kv0Po!wj)Akcy@Bi!Hts1
zuB9phqw$DOpD!sp%WBzRCs35Ck}iG6YU%mGJ4gKT@d>prczA0{u#WxFh?f^jK0j-i
zPDb3iF`=@;)WPmvLH+T9(K4{VJ7((Ovh~asE4qo}<gz1(!&$jrx_?tm*3FjJZ3d5s
zMpVCbyu;z7z_taTMGs6Y=xJR~j;HA>nuL|OzH@#<Hrv$1R{Tj9P)JozV*F3fxgJYt
zi9qa65?XcL3_yD6^W}&k2F@|wi0eu?YzkIv+azS;Gnw8)nl&O=!_`9Qt9|zxRy56`
zwl@q5F_;W&6UW3A6*K|HhH8JrUb%z!3r?TSFyq@4tZ0`@KK*II;ymCE{sRZWF?#Qh
zX}y}xWyIJ7qPMQso`!wUe%OI<?cZ=ZE(?6=@viZBJOJXgT6Y%SrbJmDRKSl$qX^Qc
z@$T=E>mJ7I`k2d^?z6MItK>bgABk1enIVoTxzA;(Ii~7KR7J-b4Xx-ktgTa8hs$@K
z$+YCborj!UT0TEpa&!o7W0<cDvrbr=5syzi=SyL}67IcmAK$e+etb#WSgZ?REc1nD
zxtwv)cF<K6b5A`#<<0xY+_`(7k3YX)Jhi;><}uUVF{dv*VO0>Sf>kl)SLdF~dBb_@
zD8wM4#H@s-1LG{`3&;7%k{d^k^BFiR+}InlXbqp93a7Jzrcw2JUKE(=n6sJZ^kUBK
z{V~Tkb~rm*@N_Qh?(K0lTVfUg-?<*x-#S{qMIm<GrL&BZzDr-iJD}Q%uv@@8hZDxB
zDvr^cS~LzPO)x_YDTrL@5;2otQp9<WEva^tG^;*@AZbs1KxZG<Rk%Vmu7ThKGPcs2
zEWM^NOrPn8%jEASlL<-Kr9jG|mZDW(Og8m~j)go<L*cY0?9#LK*EFKIZQH=&{E}r+
zQtdd(x@I|>A=5F|R<sv;{Q7S{#h8}quH)k3*Hj<;0Xv1EvSr4qatZL*hH-GIsbZMu
zhttO32AEtrzF;_ahgk}G9hXydQaD8ad7t9bbI%Vvl(xv{xtN$O0z$~4FG^!$7?l;(
zAgI?zc2R(`DsiTV2W(kJisYDz1=k6y{u}2U^Vyuo9W-XbMGenqGj>Oo)e1x!Y%$^&
zpDp8*xA-SZ>ZYY>BF~R?Ac3><B>@3jadJ^(tjAFC^G`1+%aVEtca39j$8ypHKKZ=m
ztgh%@cAV8Kyw`j)Rna?2=c0#7ccG^*J4~o}a@K+wGhZ1VpR6dWLfyk&!Nz6VaB<<8
zj64>>gpLPy#u}-7-tg#o%|TnTSasBOi!m-vo-NLaJXF6Op><stMlw%eeYYLH&{u_U
zDEUXrtqHubUs43GX&%;sXmYJ{Nq^D{J8L5KNWR0G_sqGJ@0PrGdQ1^dNSaS?{)KF=
z6-ALv%%t(;M;bbXq<^ktf^M>au0ORB<$*d-%%CsH>_GY`@b$2Z!TlkV-fg<_d-`T&
zuP9v=sdhZUuUO5`X*<Kkyy0H4&ti4Na<+pTJ4QEe^X{Mgh<ktdW0uxY*n(7KE<`|E
z&G6Wv1ml@h88T^6>XA1l2^D}o{%rUxX(Jhq@21}(nT|kyUqkxn;j{PuCgZLzW*Z{)
zv5Dgod@2MIsjpE4Jw#m8OQ*EdDaOn8bD=;~wcjiXu1^7}cxG8u%<DjBf>zd$mZnj1
z{#3rLPiin+&YO%ANJ!9+$%Q3LQ*!rcLfr%|nn2qLZP(z8rSXpQrQ^lPoQsu3q6#{j
zH!+W^&^rZU20d6)WK&ISa^32}^DQ)u{%xXpp?I2QUMoH_8I74WW6mG7oSX|36{qKm
zsJ%pOzyyY#q;I+<Ol3`meu=&r0!C`?9a#1zj@Gx>m_(aQoz#*L=rJQ0iUp-f8Jbz!
zDkS%%qt+tLH^K@wg#oa2p`>$$xK|z*k&WY{S5I7DWR!j(I_C!W-q1plDJl%^WtF)k
zxe5oGp(`AF`%~tXqbP;Ns;0j5P&*C}_6VmP)5Cj|@7CP@;CsCJm;V*hn-8dcN`hA6
zfP{?+S_slaOfSVtrgviEx-yX>Id2B^rfkCCl9}5F><)#Sem?~3hZ?X%S+P0CQlN0U
z&bkIDTi%7x4XOksh@dEnNW3_x{1fGK8uuc9v8AO1N8fcke7M8j&X~Xd$vKq~{`^ml
z_{T>J&Swe4Oq~T0O&-lVm4Jl7gbSYWSh#=WIJ@+;&a$X&vOsxu*7D?}rmzNUg<u+#
zzBw^Mc>48{=mpmoSc+^;FHO4=F#)6W8%O|K0+vN%`1tW$t49@;l21s&KT>`hgK6?D
zYhOW#8a(1xymk8~2NN5sndo~kZX>`}XF173meMYU;J0>T-F!*)byBebN!J+&nDv;c
zFCO2aK+3pC);!Gcz>RaVY{}X}_Eu)uDlyI|RmmYu>MR7TF{G3>lkStWo_M`gy}+B6
z*|Mc>J%yQ4VtIIQpAZV{t=oL>hd<)@?e}P?IPW|LM*{9`zOL1|ZBtf3k4Gglt7|)4
zk)8$RlZu;J8iL`7<}zEEL{KXnrP#!wxvQpWy25&;py4|Up^LerQS&psGo;s)hu0Or
zt!cD6zWuu~X5FD;jG-9H!Zk9!ICaE8urMkd4-OoU#-6Hxdq+E*zHD$!V0<vfP7GMh
z%0FE!I2e^6f%&|lEDM&6V1r{isj$Xlm~(tsa^vQNow@LLzgUoR)=UA8R01jOG{au?
z>STJasjtJ{_w%)v*eQ-mFo^BdWoHFbrK3%}R#aBkfXwR+=x<|tl{P41m^j1RM>`yp
zhNA7Uhi!OGz9#01DYorc7dh2M65esW2DN#uVa(L<SvK#JC$n}e-s@^M!_fVn3YDhF
zdHp_W6G3uOiL`?Tq9<&S3%U8M615m>z;uDLvl*YfIAbvpLMM!hU2fgG!D3QS`<C(U
zA-CTCkTzH(bc&B!vnE)KL}<qVK|OEAn3%o-i2yKZc`3#%dv4JZ?_JkrO}whAY?kZ!
zrZ@XdioZ&!Jn?NCVm8Bi4yGW8PeLZvH<f4xh7dKuVXD^fU75^?+G~7D>(gg7*nA%o
zpFIn#t=v*k9Tik+KYQ_lo3~+FmAtsPq^N}BTO%fn_=nFPb9`@?E;yj$^5OzI;m+M-
zyl=7M+1r`$(W95_?2dSFZ<ohUPm!YHq6sl{IvW!i5>n+iN$9w(t<B@~M%R6vNr<H<
zx%zA|W+gxWx+`{F@#b3S>RaDl(P=AiZ*Ro=x2Ehk15#-W^cF$E#^=|WXxlrGqRU_B
z`1N~k-uJrW62_wety|7D$r*4pz_d4&VnrSxu^|`)6IoY7X!CSPX(b`@O2w0~*0HJ^
z&YO<a&H=NL=Wu6_@noNNG~w}Ti5pFL_vURH(GAn0DJe!0_R~+cL<OD7kYxd2qgig&
zt6V1mlRU7-`%J|HWYbq7rV>QCriNpcJgO<fpe$YQDPF5H5~+4j2TKC#4TjG9%!xJB
zz(t4-0Tq<W>!rb^)~aXF#=zmMapw(>LGrWF0kb5>#9&v9l%>yR4R;QA8I3DmE?0P0
z;PI43-MB7TE>7o)`4F&W#bV`o@%)l^-?~d-1y=;Tw5;lmrtvK6CEksap4kJ0ga2P`
z;T7L$+gNg2kGVccT0d7{(CXa`7<mPLW%@z=vMmFuU!f%v?KO{%@;#b1zTxcy%l+K~
ze5(ZqP>)&XJBq5x6HYg+fvKcD&t}%9OzDB`-kqL?Xq!OvA<))!HV1~(#zSqZx7@B4
zNLh10Y?!7wPd0WU5uj|EmPRzDNY(l_Z)(<Pwd1;0b^>+DhbT}IH<#w-eRlGali7^%
z?Yoo{i?2%NI2OhbcBb5U<1G%~d5cw15PXBHwH{>Xd~g0mIu(=p8a=fse={$Ev@@$W
zfe<`iL|G3+f3Q|HK%?tflc&q9aVBqI8k<~gISL_@#?ETB=m8|D&y8w(no6Y~7lk9G
zE2RmVoE$#RqXg0?%*tA$v_;YM?CT&BwPHt+mYM4}3B9}|g;*c%?5w5p6;Hars-1&%
zSfgnelhKO3!;;H+N8JRBIF63@afRji%N4dNd33s>TQ%(N?$P;{k3K!ec_9=9t|-;?
z3&SbN+QWWxEt(i{BAE@f_@8pKq2Zn518!76*XD?62_e(ciYVIv#9DDSI$Ab>)V{=g
z)Hsrc5J6X+^qLE*lq_YBDPbd~MZ{o~9imNzMUy#^H5t84G86RQ-gB8;<;E!KV>-tV
zQh}Van$i`YLHns*DjPK&Q@CEpiBJZm94-=Pln^UM>&Aw0_#m8}Jcl6cPWP}*s6z)P
zU|fMQjxZWyTtz{^xK3%IJ39cP$=I0~17hf!I#=(p)@IY)=V*A-%P;YY^(KQPGfEV3
z47JbJSULg{*%?yRp7b7#v9w*ws$No!${ZA$H>`y3=_`tMkV#7>)Apo~ix{F2ydn5b
zD;kMlf--e1=L?*58uDN@uz2X?DXpVO6DuTpS(Lwh2w@vr@baR?n3A)FC|iPw>Y8z!
z&pp;gwgsbXgqNQyiJOQ@M=vYoZg!g7*-4@Hu5~c)FwykPY>0VTZ4(aLX<ojz9J%KF
zHP`Vq2YnsS;g{2rzG54w)w&r4M%MH2sA9JeoHt0J3yxB<Rs|`hN}x#NuEHnv-Fw9^
ztWgX|wRIIl7NPN-lJNn?D(+!Jm*cLW!x}UdCfz}VL}wFaRzwY=sbiwnVG=FOdOni4
zG=EjQYnv82t@2|58v^3n{0w3Q@0WnkwGDOC;+zK0x~Or98LSEe7{L(0D8r|76PC-C
z<=H7aRf*}AbgLzS1~;wnT}RtAtS-)(y?8;fHzly3^-AG1#F_@u7l|gdm!23ey^|o4
zO+2L-E~B%lHv<!ASQj;@rfz6kPf;pULtWQdtJTWb5kJb9mPcAgvt^EJ#h`R6>7ke?
z%yn0a@pv(KSZUSua}cCc_6%zs<!DT3+BmN)9@|IzuV#JVXr72y6dZ}bUlA2G!Prgx
z-{C`Av^u3iaQVfCR71`v^J)UuNv1^5`{Wb8X{G9Sz9~|&Kk~eBJYqaHgrz6oRU?UF
zBfrfE!fIlkZWku6Tfq}4a<d1kr_6QEQ5pg7an9om-~=C9e5WR$YOWSPkOlb~#!xti
zm%wtVi~=s26Y2~JS&$`=7y1oE7qt@KC49$3a64%yeRO!5;TmtInn|GbO37@jO~z3y
zF6+T~jA?NQ)_dkppA+UM6t=<B(Mm@!o{E53&S9~D)2GPd6uaxd1RYjOj}vWe%2SZ@
z2BkN(HDxK8hC$zmXqKp+6V_N}O%N;|>C{_W*$_=oRW?k*)v)SBC<am}w{*RnRMTHS
z{_czgo6LEQgiqR6hJ2zzQ;fhB0cSko`f!oZfp4OK?q<q3np8)-VV<VyHp6LtoyOA(
z-!x$cdeYz`TNRP(1k_L~SUdhTvwMHT?b{N6_0?L$TB3*v!E^7p<ajDv&R#-2hhPvB
zle@(v`vQ|9!%aUClLtu`PGmO-JqP&J*qeBX_*uflhDp0&VBX|tccY|nm_(tR%BSlb
z)1c3g**CIPFx-YsASrWw3>gZt=f^Tg^hyPjbVJRY&a=?u3xX^3dsG{#jHkVv^Ze&O
zL0&$i@_|OcgpSHNCSF*copIy>oPUmKUQ!f?G$CMc*a-M<Zw4_jq@akxAq>`*=v&pd
ztkg4MfcvF@P3YHij|mREv3c=FuUxh#uG%}gsif-+>~w}PdQro&Nh^uKTe`PNLRU3(
z=?tx~b}ijBoSMcVX;_jk59sxiz`E8>`mX&GY-!SZOt<2#TN7^YTWn}?l~tM@=y8q+
zDqEMQdE99GI5>%mrAUNt={B!YlMN9IbQ!nG0iY2((d(y4A5Tj-P1F!2Z`HkU-CSU)
zCr08mqc<)IK=OSCJ<ix#|6Lk8Jur=uE-Gsbg@MbH=hUBnN;$uTwq?F*m>%BZ@Zg9~
zfA$Yd!jkFngvvCSu*A?Q)a1=8Ml0Sogs9oBI}3)IO?*HkiqceO)Y2z5Z&M;tAZ_0Z
z$rjHQgDd}Q5HVSk?vIwib;962J-b9drUr~htUBqyWRGlqH%_k;f?!R1P1T&Ww(+3(
z=D&aKb=>P;@`}8AL--Aj^I$R?2~5qBcaL^B92s0AAi9gW!Q?ifgN>yWFOxU8;ZomN
z_Sd$og{5mH4M&o8p6+#3!%p=FG-goa<z%>wBof~Z--pm^>q&bQGgvq2hGF9ghCclD
zC(twt{oERZG%L;@{hD%qL0HYHXEThi`QX3!5%=HvkS9O?Im@$4WWQuQDz&Od>oL|{
zv0{2lW)Q5JyrO9{*zlT$9JG}LG#eV$p!c?aE)l`gYqo2TxTTpqmfGyF_r_?<TK=-f
ze6zzO%S#ic-`3>-03DJ^L_t*FrFs)XW;{+$9|(i|n?S&u&<m{LKC<3kN5dKpxomv?
zbv3l_G`zlT8;dU|C@o6tc5}Dj?b`>K5VS}xF<BWyk0+-1w+$2AZ12hIzA42-6E@l}
zlpOh%w1|!K`oLzx#yaVbH72dr!2xz{VO<r3y@(k6xqk1Bd#2TAF%-c3=`&t_{3)T+
zx|)qKeE&y(!3RJ55tE%8{J{_Zl)w3RPgpKi?5#S&s>6DTo-?jrLh;_ibfF&j{i>~B
z?KzP1+Cw(ia~g-FO$~E6*8_Hi;l7bH+u_yvaW`cBJ>SX<1*5STF%-%COXKm?#KYzz
z3$J_wuYK8Xm$3TgF|6yx<8}L`!l~&z$9pCB52pk_kEPiM&}jxL2CDmSu&MQCA_g_c
z0Yq}u=ggp);-d`u*+7dJnt{XEFlUA)kRF|KNP!rjxvob=M}Ib_uJoCWOJcwT#n(E|
z<6r!W+0*BgP6Iq|zWEm4|I2@g-`S_FEDzp)mw){0Bf4%*v#hy%dB(vzfwFXXl38ZA
z=#=ShgJ&}2;uqNyc;$G><Fm;Ip3Af(jZ$90@n)|3^QyowS32Ko&4aEEI}$%n?|-<d
ztkbz_l)SrY5?&pwS54O6#sc1y=)bS+%V?*sI&SdNMKE+20uK(S+}*L*(7j5%zH*J<
zOzWeu6A%uHwXAOny=IXGRI(*a|M!|Hx^Aluuhc6Gn~#%~N;5D~H`?YkBjLZrV1poa
zM`;Yscql6#{@ITh-M&LD9`T;THy?2S!w>l6|M?G$FIU(n&$xGS$!I#oZ|iXG^|qVq
zXz7rczJJ3rEo<7*n)+adV<s^)`t@4Mugs?2CjXXMzvobE+SKLpxssl!7rQAybxlJv
zW>a999&CJ-e$4B9_f^{0H+jCOee+t<tJ)WsVy`^sx;E6omEL&bg!gXja9}%J(9nTo
zgqh8Aw*LL~+fcL0cNzTMCpeom0g_C!evWSRcpK!}UzE+m(zzLFxo&<885|-gZAArE
zX)SxZQ|6PBu5Q`8cb}Vo@B>0&F>Rppg54SM&;FZ#&En#W`Qy)+&dxdc^ds&b?_)+2
z5<=c9De1SceJyU7L|1w(>t^im5`CoOx&|ilMe}XgyDg^d@blQmwXel)9vu4?-}6wz
zk`QC;1{*FLn&frr=r`BonxEg-_VvdjVAv}IZyt}RT(k-lxmNRP@bk)^Y#h7!^F?hl
z3xD(Hx?}PLHRg(d+xGW$iPqct^JSYsSwPx)#cFnrGeQ>(hqvxC-Pz47s|F3w+&jL>
zhkx;77&&GaFF1Mh3C-yV1u8VGiA6_^>1+Lc!8i>mj%|)lvsb92`y}!7U;N(MoQk6y
zW-bP5x}-l2e&T<xJ66%Tk$+w>_S@$`A2yPHw_iN<W$SnAK8oLF`%Yl>?Q4#O7=jmW
z?Ug*dF+##1vif&qSg)I_ulIP@Z3x>ne^rV+Pe1>R`S~*}9`6bcZ{Gz;OdxT&i(?gp
z@vR%UaY5TIsV`5MJ%54?F#_MDI-u)6S3cOV!Zv@*#=lp8(wD=F^a6`0pk96B*KJ?*
z+`)O$|6b(H)c^!c0429Wy)~lhukvo2m{l%#=QUnSTu#Fn#%--BgHh+cKG}Gq#SHQg
zRqst(_?3_Otv30-;bsi9OCIbx-q^E*rY2E%0DbC_^nXLorkTvRZCZ;l<P?$Ncb)IB
z#$II)ePuUaLnFH8*r9gz+D#;KvR^e*x8GY?Oss{lob&wGzhpT-!*nam!3}oq-;E{I
zl16C2SiHda@HXZ22Fuek0yUTO6Q=bF-wDo^6mBET;aU?lb$u|F(aKA?j~LVQYF&9`
zJ$QJ2hQnlIy<O)?{0+4)lbc&4Vb#NWlI>#;SR)h?Fd<M%L*+e15EfOSac%TnObAS(
ze?=vsR$N)PKVRpeRpiA;Xk#O`xs?y~yY{7;L4r`4hVR|I$#Ef=Hmq#})}@Ntv86!F
zD1=g#-fc~DMpGnxFZ2?T+i&hEUi0rQaL;wkIu{G4UZ+i6ht>-hC(k&4@+s2R2$q{~
zzQg#&v63f5ucOK>gOP&K<dC}$-{+T)KBj4F>Sn=wF=OSIROOh%{ryNVIYid_yJv_l
zeK<%$2q`Mxn4ZtX7`AymQ-#NEEz`l|VBT#*lEAaqc(-36$=7W8_X;1D5wce%81UAB
z1Pb4>+b#G(`w{QdpA&rGv)cvdcV1#GESB%_+1Yzs_(Ob1)Dp@SWUb2#jn}>QD;+gj
z9Fxu~X_<9bT(iHM?Ta3A+xM?KFd9&KG#&BY{UcoH^t0iFlYSxS;xP2-8NITQw5WcQ
zQ%y?i%@HS)e!h)=D)&6vKVODkC$ULfCkVG{ScaSxVvSW60f8LYl?2L`p-k+a$_CLV
ze+xqJ4NpJ*2)kU+24Qk^kM}?Pp;m_SF{&(uo1?<sSi{5j-{q6P`@fmb=IqTD>`f*d
zO^@(iaK_*}EspAJffo-ZuBm~hlM12?>7LV28$+Z*x_%t3QA!^P0qc6E)A)Eges;U|
zBf2}SrT@ILMU5{fL-)7Ig6L|K-mJ|>%k`1&$%fVU>DlXM{FjTr<KLYBN9M-!f8HDO
z<jy1PsO81Uk2yKp!|fa~s!Cp-&2ScO-P}P$ST(}wxt7T?27HV%7JQtvmf$7Q=mrQY
z3Os-C_7NcnzxZ^46k16{<h2dU-@*3vq_z)%qe;d6{SuJ|>jfnklHQa{<{(!mYr<p{
z8?n7G5-1~;Zb~R#>-9A&XIL3$+cDen5sfi1+y9z}9GXf4mBd)BSiD>=m`-*WjYn#x
zn*LbTf(%2wQ%MUV$9a5yjNlwBPtQ1g{3*8WsHXe8|7ZW4$<ZxVbqg*Pe@*dIF<%lm
zynBa(o42`q@-e3I6u~ogmSBZtt!8>rl&Ya+j{RO(LL|9+#Y*@>#mB?~Bhd`Drk5p&
zw|z4ZblXtBwmCO2Q`dOQ*xX#q+OLDZuojB!ZAcyjv0#*k$R#`6DhM|YExX+rxWHIE
z6S+X#DYkr0)6MzgTLu5^zj%lL>3{iqgogkA-`wD5zk1C7`-#Ub4LA13Eb0zpD?|dL
zabUh$a=C=vg9)?RGOa8|Jo~2Ozx!wVgl5U#-hlu8=L?qYC_c|`N8S2*ri<ZK{o4Lw
zH_sV@yoRgcfZN>8ufFfvaZ>YOAMWmg(B;XIx|T{vscE?Bb&DDEArJ)GdYKcHg9v3=
zP?n>pNc1~t$`jOmX~>g4c;q!DPv}~W4J%wvNu2N{8|h5eCjGT*#?ZD6i8i<_OAOP@
z=d}%olOR2vkcrq95;d8i<ai=X8qe7;KVtR#C7n0C`G-H^_6I+p30f)L#mYm5$Z2KL
z(*>&i9ggnaWBK$k(zLwz>@#?IO5Fu6W()QYkGXsAA*0EZBBTN+sjoU<A+3WXa8Zik
zRB0Pyu$y58!zO^SIA<taL0LFL=m=4p4AOJkTMRxHpG_|{G1GpTHM3r>ZCi(8GW#n8
zWwHH<qFNmXqB8~O)eiq@|3j!?6=pm)4ZF)ZrPRD!RWvAn_pK3paBoCwD{fW|^U0FM
z(TE?vf6U4+K}sGT?@`Y>YF2ciq%Z}g4gBKqC2u^qP057A0`Bd$Pz20$pa1yLf?1;^
zV_z#P;rFx&P?(OlZ|-tqT3{MMQrR++>2n>11EK5izNT$z&Q4Bg+lHoXXqtwm?btgw
z;?BJ{*xB8USXcBe=X!y$CgI@U`0-jx@n9hc9-rAMol9lI1}p@u3oQM<7d)7r!+a>T
zI`6U9U<}Hap0GQkR4n2VtHR2+Eurf;`Sr(q{I~y!X0hV<jrV!`!#^Puj*+!Id-ROY
zo_x-SAO10ASwR$9#wcN(ILFQV4|w*ozo%(hO6R~?+7LK8zQK69n>Ujn>oVO30SPp1
ztAcYf(Xk~#Cw(>ml9I{SpLLix9fI)e#dA(iPpF#(Muf}DOQzEu?%cXVSrimy!DuqU
z4H;mqS-aNewYOE*`EqSt3roLW2^`G_ODruUDzKi9_xX1>{ssR>@ncN$89&<l8~%r*
zUvby%@K^SLzcPX!mHdC7e$IOjcJQv`Cm%oM_GHALymNzE4FB{0_EY}okKX6ACuiK<
ztN7)we$9i2_qcg9qU>sZ`1X_+s|AlAJ>`uL-{a#Kb1u7cX5l9D`I1r!L`uTfNDBUT
zdlA1#Tl(tHEdrAw@bKn{9am&d@Wh|3$7}$p(vO#MO5-~!D<;)cJ;@>@c_G$eiz;{D
znCMZqYC`2FG$t-8z+_!UHHBE>N<@$#bfM$?{EX>z%FfQNYB~bGZAnzhKo(|6<LLj5
zqZW&eq{pfTRa!!j%w3-1l!y)nXAJdh#pR1<Ovfc<VR2o@^74|$Kl>^5az=UMh_`?A
zBg*M6UF&J2rS&acTQi$qu)DL1aRt_CMQznw9Y=TXz;w*ASy7F5IDYeOS`oZ05L<va
zx{xSu`W?D(j<#)a)^62UOniT@W2#weSu7U(`+xtx@{^zZ9p~rg>`bRvW7*x=;laK8
zc<-6+?eeF8`llS<ItC0?RpH7))15?ewVaHL#m!;p86LJF&bTR%(xyXn+-UJzts1{Y
zV5Kune&+@qwAvLs8{H;MEFz8{?EH#1Ck^k1me28wftiQDf7)>*9j#e1TN=K1XP1+g
zGj878<B$LB54l_!K6=*i`8@E!pZqZwi-y1ce8szW_gG#mD90st-+zn0eY9j%IOfYS
zcOUF>aHHkPNy65?Yp>IW@TL!*n|mc6+}n%M?J-wxaQv{e($!`$Rw;5_Df!&wnaZXg
z%5a%5AuT;Ota~>!@e)d`b1m^{?d(=j%Mqs2DP>szu^fDm$hqF*AI`d5voAk!!hYiQ
zRY1mHM0>C0)I+37HqntFYbMxaI_0$M_{YEbDZ37Q=$J2O`1%67Tk+nX|2c>6y-V;Y
z7k;M&72f~e_ZW@GYF0(PF~nd^u?6G3BdYxamM1Tn&t@Fq2xtMjkfPqL%|oZkul8*|
zpR-&pxpnK-`upBk{BakE&abPXC?N#KqcQ*LU;Rt|`CtB+<zh+O>1N=pqpB*^u&Rpb
zbi!yn#u`Ielq4@$u0)-nr6{DX!z2}2u<^X)%iIL-Wx$QrYtACP0(6)7gHm~nS}-2E
z;OUBjr9I|z`4H!B^U^+~byI%wQA1%1oG1nsDEX^@T+(%cvYJzjD(a@yog;Mo!wb)R
zzNGP<zy8IX)oQ_H;wg%Pi;D%uRTwPOPcNyv5;85uSA*Sq$$lNh^7SUs*KOZ~W~Twh
z9zzRF!@V8PyL*nVzQDv1;%TDgb0ij^rQZQJQ#RB~6ceT+He;eA#bVdT*91gtq#Y4V
z*jPA8t6`wwNUw<{ek25}abOi=k^Xen@&pIh?VqPNk@|<wd62ZTRPaFPaXAS>HJNh%
z``=?eyWsN4r}$<`y}V$)y5QCuZ}Rr{{s`O{Z#*McFaoA~dr`}Ym9AAE1uV{Le&k{`
zry7qidsFJ=Il%{PHA0KqCV{UNdkhwd#V4$_92^|5zrVlL1G^bl6})IHoOMy~ug^v6
zEO+kR)3G-|TDt=+M??u46KP-~jR_*OU6&bP`*+ft?#39}wk7y3QZjokXXjj8T(DTo
zxN&rYqZ_v{#wux|C~g?SdQ70T%DuHkVD-30`r9BB2!3%%xePd3e&r7NA0Ph(V>9Q>
zA8=-l5lR|wFaysBL9?#w)*x+&sxcVjc=}Rn5rSn^2aK80c&n~<y9+Tdx4!hzTl2aA
z^B1+>j!^oxwc(o_yN<VRPT47;t6O!bIJW^a^ozV#&9`6JNG~i%g3H8rKbWw+3t@1~
ztFFD#dS*<B5+Dj2?TGHYfx+Acw8BbevwX$P!XQXF(U}-xjXx{22(}vW{tth|#f!U~
zKl+T*$DcCuo?CCcPgzZsH8f#1111QG9knJpusk%g8NdAGXFU1UPgtIxP$I16b5^Sr
zlWK~K9Ok6wjltN~SqfWZOllL)+csX7m?s$D@p{49!5BnlS0qM2_C5ka@VTl^9^L3f
zaK>QDQa!`QtOdOe;RP-Jk<x{<|2sQV%F0rWs;u}1Bo_)v?;)x066v?E!LSB@4-h}M
zs`XQ;IN<^R7e^?`zeVh%2ij6uC4-jZNe{sQ9tp~uP0G-BHs3F~SkrVj`Q`Pt@7HNx
zCbIUQa!b&W2lk!k58gPUDjm)jkv47JH9jQPQ~fFC!sUXN@&EBfs#ke%LrDc8RHH~(
z6!Ze-RgvgdO%}yQGFB!^WQPzl{RaV-V(BXvM-QD*yl5T3-S+MUE$|Zh^V2sWC@$j)
z_U}C4_MJN{-+PyPrxzR^-=Xz}V8ei-r9W5KwZj;pTh%O2&Uo_CM||?p-*b8Tm}yl|
z?e5XF!m4hVq?oO>ipCk3Aq6vLGwhmiOlN_b=T#Lqk!WTm@H{z2`g3|}YJK-Hj?(s<
zLb|v_jm%n0Xxm6#?Xtro!2?*!bTS!eydLKY+P22JShyE3qGiIW(rT%);5D>k(C_hh
zdc8^5=PD*?r_{P3CL#(`ytNn!2rfQu66L*`zoxry8Pfj$DNJ$r`TF3eYrRTdeUU8s
zR%7nJh2{X7mct3WdpyC0kV9D3*KVAwY_Ldfv{X4}@V2)$)lw`J>TZ|dAql}DxU}Vk
z<qahQ7g^}RMxO^B!_2LfaIr7ilwR?S*<G&!E`&hnqSw-b-96;?{%s_fSji?;DIZ+b
z7&Tpkr}G_k*C3_i-g|Fz=bd{r%@SjvDoTo?VzhsdA5AMy+ksUPA6&R1Zinep>wQnp
zn8qZsvx>wh{Pi&qQPZ*CprUY(&y>t?ErpieBw!7rvBSks2p@cYU%Fv=%A(ig4UVF$
zV$dmAS4JT$xLB3RT7#p|O-D;D>1MT!4@;Xqpi0>RovKxOU1O80+JSLfUVT4c*(@;|
zLTC*~N_)3oJ8tu3^;iGu66?2{74_|FCRkkOd9YvdaHph@CVF?Y7NBIRU(**56`vK_
z^ahjG6=FTOl)W#Qt-FB3#>i%+30W6VG3PL0Wzoz@b@_(cgTZJ8o4jME8I^YI^uBvw
zU&J#Ev`nR{^xK40g^h(h7&FsrV<O2J5x|sjDvAQ*1}#$;*hp`KywOK2Zf9qT-P?;*
znp3r#fp7`Ec9%@j^^yv`8J5lCfpfr`&GDeWUi{A4eoQun6~rnxNo$p$$XgJ+gu%Lr
zp37{O>a%!2#OQb=+bBMhWVZv+M0QLj<AF&V$Ou?=JI8YOQM#r+z6PiJM*EU1pkL4U
z`u#B7etXS;Se!Auc|7LkUV-s7##$UYv4VK4vvi$De5XQ80!3LM0&Uk|P;k~+hd~27
z8}D&NiF4{<Q?n|>R3FV{Qyi&JrNNl!{gJ%;Cbg-qYudJ>EDNewaeA0+4P=)&5hPFd
z)fVdqChalCBMF|a>uB4yFUATntfMzihjc8PVIC<gLKoutV%G&M5c6I$wiF}_MGb(}
zqeH~IhB97An{z@0w{6;kztcD-A-?6fVY`~(+>c$lw>1VEi|6V)((wxtogGnW2$G<J
zsQrk|-x2YtB7*x8;elQjNgl^A{CxO)N%F^WSEq|^7)4Qh1%dTt+wYe`^DSxp6bMFe
zR=9IeQA)tK4I$J>hc0j@blx+c&j@vcbRDg4IXXJTSi@?yLTk#YPUW1{vhtm0Jep9A
zMhG#-PlDzX#`=9-*U~gvtkhaZ;fi%foka66V^3tEvB?OLgo^i`-~&Y!oj0W2-Z7tF
zvRGUoz`_0@);gRkw1}%IvsMs%$k<)>OulB@j2%iH?-fWDXvRjfIEPzYho6y4l;t8E
zSFD8IQyZeTlLU9X?V6Asj@|b3s{VQs?@xpS@*~CPh@~h=5eNw`u+FYsJB?=u0pBSG
z<y;YieiJ_3o7f_fX{+;?#X%fuxLG@NS_S&IFR;FA|35Za`&W$6hL)RC;oUp?(AK1y
zbx6b`qG?i96=E%2+hRgND?)+8l_SMqniXBQq9{w8bvRcd2I{UQ#FFw_EjR)BDj0~l
zpIT<!V~vYNGPS3wacI2Lx;byw%$&Au)f9^uN!P_>-&k;>>pJRY!D4xV5GYF(l4UWb
zC@NjtLHlT(jj>6|b2ZS6B$<%CInp1qE*Mle$Uq1v7L$RHEI8JMRZ*-jyX;Y2m*$ES
zNw1Oinx@YS-WrpWkcYZo(iqchP#kJ~14!C$h}X75%`%z9gX7gC)xP_zeVX`=GccwJ
z+wsmJ1e&JSjl(9vobnfkW#RfcJd6gI&*yZVXEK>k*Y$S->vym9i$ev)io;RO_wOGt
zDQm<P%I)rK^y=!u8jVJSOK2=iT%q{RQ#2!lsqS*FP;A5+d>1fQBe2y>NX(QL<4PFC
zMU&E9kShx(MAm@xciLS;S^=U9!#b<jk)YL_Ln_V*B08xjlQBSF#W<zfh+--U-%>z4
zAhFtViug})Si?o6qGQl!h_TgC6HG^B4Kc~yUTa_r*5{*Hx26?|MB#3FAUz&$Z34Dq
zCF+g0p2t(v<Z>|*oq-_A_*XW6`zv_g(>U27=DcYIuibF{<75(+Rf)mSd5^?Gw`p!j
ztXG(|TbqpSVeVtZtcoH#0YV7h39R4AmT^X*pyBNsV{TL))71n#Vg_+T)@GAzJvGPm
zo-b#qCKHfKO^C>gWsISy6nO4Ukm%vs@HM7voE%z^Ze{xgo)M{B`YNV=NFc;wnqV|7
zB{E~G7GjXDBZyYr(ZJ6L)+1n($I`_GY%(ZsZ0{X4R<%NtG%7m`pj9(6fCex+r6Nv?
zycp!!^{%FVT=Q63+w*Rz+LNi50x>Kkex5w_B5DfyE|3B%ee2cyE)vKcO|p1r%?gNG
zs_Dl*>0t&fN+P1qn>C$$&rOX_|M6LSUw?1w#VGo@WUZwt%K;UQ<T3Ajr{kN(2@O)W
z@%(`1g2u@}RaF#%%N`E0TA3!)cANXV_APIN*EVs&4;~({8ydvdco#5MFsZ(qO=Zc4
z(>~6DIFW*lg-cVJ)r5bf2^}Y%ph6;;ScxT@LwdzElW(|v+jZQ=L`*1|ne}qTa=Bzw
zRe0}td2+(R;U32~ZV*KAkp%Fkegz-YbRwvmJS`}jm`R9&O&3htDc0tqxvCn}`utDJ
zs`DMrRx#bBPjSkRWY-=L@$?HegYE;IDXshvR7fS0*_b}0BjP;<i*=5!>v|z!O!fep
zXl5l-do9u`;*e?2@IEG&%en>$qR&6T>r!7cB~U&*I#`TZcVv(>Q`N3>VOL{x3;=>^
zf~k)-#@4AkA7FCy*DkD7RH3GeRaTua;5GY}1_68>Ir?>F@CFzReVouY?_pSfxXycy
zE6*R^+GEFf904E6E+i^fY67K6nE=?h*~U^<rAyjFqDmf2S{bPFCZ^M5W>U#AD&>&{
zBx@Au8riG2DK4!7>f`AS)kxjoK6s9;qpC`R#KmV+%R_{^siX2@utkY02BvNvC0&R<
zEux4wr4dw3%_51)24XZb7_p4UMgP1-N+*%5;hBW#Kz1sur_snj+cZ6xZTrtd2zcLt
zNH)K14%INYvWzBV(r)_x1G!(@rbyZhf)((B`2PLtJ9HbKOv(IPtK|~!1Cz-(^O7Yf
zK!sq4#W&Ohx7K2vj+Zq<VP|l*H;Kstj{&L?aX|zd3?Uebo6RG}%|cbn2x(-@FfG7u
zdL4e7nhXQ)7%aGNvQyidL43zU3GjTEpDtE}u+m8ibZx7<@UYs-z}q!sF3>3F7zil|
ztBD7$nLc3+6Cq+e{qV$nHy-4DKY`6qo5%`>8aN@S8BsWw6RWeyvH{emNj^-p6-g*m
zf2>3eqc?;5ZYRwy37JfoV0xS?X9a|GQWP{Bm+K{7ucbiBAn5y&tQ-AX)&xcxiy_7%
zSy1)ws>j;4?aE1KmZa1o5@?!^(D^*Rik%HowuCiJS^343tE_1nx~^j~ov2AH>JV71
zR&>6ja0OL0q9~LAvF+N($YJ8VGrcM7EJcJCR73QH5U7_ce5W|r$;m1I8TI@F=0DfI
Qk^lez07*qoM6N<$f&?hQsQ>@~

diff --git a/misc/SharePointDocumentationToc.xml b/misc/SharePointDocumentationToc.xml
deleted file mode 100644
index dfae203091..0000000000
--- a/misc/SharePointDocumentationToc.xml
+++ /dev/null
@@ -1,662 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<Menu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SupportedProduct="|SharePoint" SupportedVersion="|V1.0|">
-	<Item text="SharePoint Framework" url="spfx" SEODescription="">
-		<Item text="Overview" url="spfx/sharepoint-framework-overview" SEODescription="The SharePoint Framework provides a modern developer experience for extending SharePoint."/>
-		<Item text="Roadmap" url="spfx/roadmap" SEODescription="Planned roadmap for the future SharePoint Framework versions."/>
-		<Item text="Known issues and FAQ" url="spfx/known-issues-and-common-questions" SEODescription="Known issues and frequently asked questions around SharePoint Framework."/>
-		<Item text="Tools and libraries" url="spfx/tools-and-libraries" SEODescription="Learn about the tools and libriaries you will need to use to build your SharePoint Framework solutions."/>
-		<Item text="Set up your Office 365 tenant" url="spfx/set-up-your-developer-tenant" SEODescription="Set up an Office 365 tenant so that you can test and debug your SharePoint client-side web parts" />
-		<Item text="Set up your development environment" url="spfx/set-up-your-development-environment" SEODescription="Set up and configure your development environment to build SharePoint client-side web parts" />
-		<Item text="SharePoint 2016 support" url="spfx/sharepoint-2016-support" SEODescription="SharePoint Framework development with SharePoint 2016 Feature Pack 2" />
-		<Item text="Debug solutions with VS Code" url="spfx/debug-in-vscode" SEODescription="Debug SharePoint Framework solutions in Visual Studio Code" />
-		<Item text="Enterprise Guidance" url="spfx/enterprise-guidance" SEODescription="SharePoint Framework Enterprise architecture and development guidance." />
-		<Item text="Team-based development" url="spfx/team-based-development-on-sharepoint-framework" SEODescription="Team-based development on SharePoint Framework." />
-		<Item text="Using GraphHttpClient" url="spfx/call-microsoft-graph-using-graphhttpclient" SEODescription="Call Microsoft Graph using the SharePoint Framework GraphHttpClient." />
-		<Item text="Tenant-Scoped deployment" url="spfx/tenant-scoped-deployment" SEODescription="Tenant-Scoped deployment option for SharePoint Framework solutions (skipFeatureDeployment)." />
-		<Item text="Use theme colors in your solution" url="spfx/use-theme-colors-in-your-customizations" SEODescription="Use theme colors in your SharePoint Framework customizations." />
-		<Item text="Working with CSS" url="spfx/css-recommendations" SEODescription="Recommendations for working with CSS in SharePoint Framework solutions." />
-		<Item text="Toolchain" url="spfx/toolchain/sharepoint-framework-toolchain" SEODescription="">
-			<Item text="SharePoint Framework Toolchain" url="spfx/toolchain/sharepoint-framework-toolchain" SEODescription="The SharePoint Framework toolchain is the set of build tools, framework packages, and other items that manage building and deploying your client side projects." />
-			<Item text="Yeoman Sharepoint generator" url="spfx/toolchain/scaffolding-projects-using-yeoman-sharepoint-generator" SEODescription="Create new client-side solution projects using yeoman SharePoint generator." />
-			<Item text="Update SharePoint Framework packages" url="spfx/toolchain/update-latest-packages" SEODescription="Process how to update SharePoint Framework packages to latest versions in your solutions." />
-			<Item text="Optimize builds for production" url="spfx/toolchain/optimize-builds-for-production" SEODescription="Optimizing SharePoint Framework builds for production deployment." />
-			<Item text="Integrate gulp tasks in SharePoint Framework toolchain" url="spfx/toolchain/integrate-gulp-tasks-in-build-pipeline" SEODescription="Integrate custom gulp tasks in the build pipeline used in SharePoint Framework solutions." />
-			<Item text="Extending Webpack in SharePoint Framework toolchain" url="spfx/toolchain/extending-webpack-in-build-pipeline" SEODescription="Extend Webpack in the build pipeline used in SharePoint Framework solutions." />
-			<Item text="Provision SharePoint assets" url="spfx/toolchain/provision-sharepoint-assets" SEODescription="SharePoint Framework toolchain allows you to package and deploy SharePoint fields, content types, list instances with your client-side solution package." />
-		</Item>
-		<Item text="Extensions (Preview)" url="spfx/extensions" SEODescription="">
-			<Item text="Overview" url="spfx/extensions/overview-extensions" SEODescription="Develop SharePoint Solution extensions to customize experience for SharePoint."/>
-			<Item text="Changes in the RC release" url="spfx/extensions/changes-between-dev-preview-and-rc" SEODescription="Changes between Dev Preview and Release Candidate for SharePoint Framework Extensions (preview)."/>
-			<Item text="Get started" url="spfx/extensions/get-started">
-				<Item text="Build your first extension" url="spfx/extensions/get-started/build-a-hello-world-extension" SEODescription="Build a hello world SharePoint Framework extension." />
-				<Item text="Using page placeholders" url="spfx/extensions/get-started/using-page-placeholder-with-extensions" SEODescription="Using page placeholders from Application Customizer." />
-				<Item text="Deploy your extension to SharePoint" url="spfx/extensions/get-started/serving-your-extension-from-sharepoint" SEODescription="Deploying your extension to SharePoint site collection." />	
-				<Item text="Hosting extension from CDN" url="spfx/extensions/get-started/hosting-extension-from-office365-cdn" SEODescription="Hosting extension from Office 365 CDN." />	
-				<Item text="Build FieldCustomizer" url="spfx/extensions/get-started/building-simple-field-customizer" SEODescription="Building simple field customizer and associating that to SharePoint site." />
-				<Item text="Build ListView Command Set" url="spfx/extensions/get-started/building-simple-cmdset-with-dialog-api" SEODescription="Build a ListView Command Set, which uses dialog API." />
-			</Item>
-			<Item text="Guidance" url="spfx/extensions/get-started">
-				<Item text="Use custom dialog boxes" url="spfx/extensions/guidance/using-custom-dialogs-with-spfx" SEODescription="Using Custom Dialogs with SharePoint Framework Extensions." />
-			</Item>
-		</Item>
-		<Item text="Web parts" url="spfx/web-parts" SEODescription="">
-			<Item text="Overview" url="spfx/web-parts/overview-client-side-web-parts" SEODescription="Develop SharePoint client-side web parts to provide a better customized experience for SharePoint."/>
-			<Item text="Get started" url="spfx/web-parts/get-started">
-				<Item text="Build your first web part" url="spfx/web-parts/get-started/build-a-hello-world-web-part" SEODescription="Build a hello world SharePoint client-side web part." />
-				<Item text="Connect to SharePoint" url="spfx/web-parts/get-started/connect-to-sharepoint" SEODescription="Connect your SharePoint client-side web part to SharePoint by using page context." />
-				<Item text="Deploy your web part to a SharePoint page" url="spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page" SEODescription="Deploy your SharePoint client-side web part to a SharePoint page." />
-				<Item text="Deploy to a Azure CDN" url="spfx/web-parts/get-started/deploy-web-part-to-cdn" SEODescription="Deploy your SharePoint client-side web part assets to a CDN instead of using a local host." />
-				<Item text="Add jQueryUI Accordion" url="spfx/web-parts/get-started/add-jqueryui-accordion-to-web-part" SEODescription="Add the jQueryUI Accordian to your SharePoint client-side web part project." />
-				<Item text="Use Office UI Fabric React components" url="spfx/web-parts/get-started/use-fabric-react-components" SEODescription="Build a SharePoint client-side web part that uses the DocumentCard Office UI Fabric component." />
-				<Item text="Provisioning assets from solution" url="spfx/web-parts/get-started/provision-sp-assets-from-package" SEODescription="How to use SharePoint Framework to provision SharePoint assets to sites when solution is installed." />
-				<Item text="Deploy to Office 365 CDN" url="spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn" SEODescription="How to host SharePoint Framework client-side web part from Office 365 CDN." />
-			</Item>
-			<Item text="Basics" url="spfx/web-parts/basics" SEODescription="">
-				<Item text="Design considerations" url="spfx/web-parts/basics/design-considerations-for-web-parts" SEODescription="Design your SharePoint client-side web parts to use Office UI Fabric React components, be responsive, and handle publish and edit modes." />
-				<Item text="Add properties to the property pane" url="spfx/web-parts/basics/integrate-with-property-pane" SEODescription="Set up properties for your SharePoint client-side web part and manage them through the property pane." />
-				<Item text="Add an external library" url="spfx/web-parts/basics/add-an-external-library" SEODescription="Add an external JavaScript library to your SharePoint client-side web part such as small libraries, non-AMD modules, and localized resources." />
-				<Item text="Working with the original __RequestDigest" url="spfx/web-parts/basics/working-with-requestdigest" SEODescription="Learn how to use the __REQUESTDIGEST form field in a web part in the SharePoint Framework" />
-				<Item text="Notes on solution packaging" url="spfx/web-parts/basics/notes-on-solution-packaging" SEODescription="Understand definition details for files used for packaging web parts in solutions in the SharePoint Framework" />
-			</Item>
-			<Item text="Guidance" url="spfx/web-parts/guidance" SEODescription="">
-				<Item text="SharePoint Framework solutions governance considerations" url="spfx/web-parts/guidance/governance-considerations" SEODescription="Governance considerations for organizations around SharePoint Framework." />
-				<Item text="Use existing JavaScript libraries" url="spfx/web-parts/guidance/use-existing-javascript-libraries" SEODescription="Best practices for using existing JavaScript libraries in your SharePoint client-side web parts." />
-				<Item text="Reference third-party CSS styles" url="spfx/web-parts/guidance/reference-third-party-css-styles" SEODescription="Reference third party CSS styles in your SharePoint Framework client-side web parts." />
-				<Item text="Using preconfigured entries" url="spfx/web-parts/guidance/simplify-adding-web-parts-with-preconfigured-entries" SEODescription="Simplify adding web parts with preconfigured entries." />
-				<Item text="Integrate web part properties with SharePoint" url="spfx/web-parts/guidance/integrate-web-part-properties-with-sharepoint" SEODescription="SharePoint Frameworks offers you a new set of capabilities that simplify managing web part properties' values and integrate them with SharePoint Search." />			
-				<Item text="Using JSOM in web part" url="spfx/web-parts/guidance/connect-to-sharepoint-using-jsom" SEODescription="Connect to SharePoint using the JavaScript Object Model (JSOM)." />
-				<Item text="Validate property pane entries" url="spfx/web-parts/guidance/validate-web-part-property-values" SEODescription="Validate property pane entries from end users." />
-				<Item text="Use cascading dropdowns in property pane" url="spfx/web-parts/guidance/use-cascading-dropdowns-in-web-part-properties" SEODescription="Using cascading dropdowns in property pane of your SharePoint Framework client-side web part." />
-				<Item text="Build custom controls for the property pane" url="spfx/web-parts/guidance/build-custom-property-pane-controls" SEODescription="Build custom controls for additional functionality for the property pane of your SharePoint Framework client-side web part." />
-				<Item text="Share data between web parts" url="spfx/web-parts/guidance/share-data-between-web-parts" SEODescription="Options and practices on sharing data cross multiple web parts in single page." />
-				<Item text="Sharing data between web parts (tutorial)" url="spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable" SEODescription="Share data between web parts using a global variable (tutorial)." />
-				<Item text="Migrating Script Editor Web Part customizations" url="spfx/web-parts/guidance/migrate-script-editor-web-part-customizations" SEODescription="Migrate existing Script Editor Web Part customizations to the SharePoint Framework." />
-				<Item text="Migrating jQuery and DataTables solution" url="spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx" SEODescription="Migrate jQuery and DataTables solution built using Script Editor Web Part to SharePoint Framework." />
-				<Item text="Migrating jQuery and FullCalendar solution" url="spfx/web-parts/guidance/migrate-jquery-fullcalendar-script-to-spfx" SEODescription="Migrate jQuery and FullCalendar solution built using Script Editor Web Part to SharePoint Framework." />
-				<Item text="Connect to API secured with Azure Active Directory" url="spfx/web-parts/guidance/connect-to-api-secured-with-aad" SEODescription="Call securely APIs from client-side web parts, which are secured using Azure Active Directory." />				
-				<Item text="Office UI Fabric integration" url="spfx/web-parts/guidance/office-ui-fabric-integration" SEODescription="Using Office UI Fabric Core and Fabric React in SPFx client-side web parts." />
-				<Item text="Build web parts with SP PnP JS" url="spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts" SEODescription="Using SharePoint PnP JS library in your SharePoint Framework client-side web part implementation." />
-				<Item text="Build web parts with Angular v1.x" url="spfx/web-parts/guidance/build-client-side-web-parts-with-angular-1-x" SEODescription="Use Angular 1.x to build a simple SharePoint Framework client-side web part." />
-				<Item text="Migrating Angular applications" url="spfx/web-parts/guidance/migrate-angular-1-x-applications-to-sharepoint-framework" SEODescription="Migrating existing Angular v1.x applications to SharePoint Framework client-side web parts." />
-				<Item text="Localization" url="spfx/web-parts/guidance/localize-web-parts" SEODescription="Localize SharePoint Framework client-side web parts." />
-				<Item text="Call the Microsoft Graph API" url="spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part" SEODescription="Call the Microsoft Graph API from your SharePoint Framework client-side web part using OAuth." />
-			</Item>
-		</Item>
-	</Item>
-	<Item text="SharePoint APIs" url="apis" SEODescription="">
-		<Item text="REST" url="apis/rest" SEODescription="">
-			<Item text="SharePoint REST service" url="apis/rest/get-to-know-the-sharepoint-rest-service" SEODescription="Get to know the SharePoint REST service."/>
-			<Item text="Basic operations" url="apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints" SEODescription="Complete basic operations using SharePoint REST endpoints."/>
-			<Item text="Lists and list items" url="apis/rest/working-with-lists-and-list-items-with-rest" SEODescription="Working with lists and list items with SharePoint REST."/>
-			<Item text="Folders and files" url="apis/rest/working-with-folders-and-files-with-rest" SEODescription="Working with folders and files with SharePoint REST."/>
-			<Item text="REST endpoint URIs" url="apis/rest/determine-sharepoint-rest-service-endpoint-uris" SEODescription="Determine SharePoint REST service endpoint URIs."/>
-			<Item text="OData query operations" url="apis/rest/use-odata-query-operations-in-sharepoint-rest-requests" SEODescription="Use OData query operations in SharePoint REST requests."/>
-			<Item text="Navigate data structure" url="apis/rest/navigate-the-sharepoint-data-structure-represented-in-the-rest-service" SEODescription="Navigate the SharePoint data structure represented in the REST service."/>
-			<Item text="Synchronize SharePoint items" url="apis/rest/synchronize-sharepoint-items-using-the-rest-service" SEODescription="Synchronize SharePoint items using the REST service."/>
-			<Item text="Upload a file" url="apis/rest/upload-a-file-by-using-the-rest-api-and-jquery" SEODescription="Upload a file by using the REST API and jQuery."/>
-			<Item text="Manage permissions" url="apis/rest/set-custom-permissions-on-a-list-by-using-the-rest-interface" SEODescription="Set custom permissions son a list by using the REST interface."/>
-			<Item text="Batch requests" url="apis/rest/make-batch-requests-with-the-rest-apis" SEODescription="Make batch requests with the SharePoint REST APIs."/>
-		</Item>
-		<Item text="Webhooks" url="apis/webhooks" SEODescription="">
-			<Item text="Overview" url="apis/webhooks/overview-sharepoint-webhooks" SEODescription="SharePoint webhooks allow developers to build service integrations which subscribe to receive notifications on specific events that occur in SharePoint."/>
-			<Item text="Get started" url="apis/webhooks/get-started-webhooks" SEODescription="Get started building your own application that can add and handle SharePoint webhook requests."/>
-			<Item text="Reference implementation" url="apis/webhooks/webhooks-reference-implementation" SEODescription="A SharePoint PnP sample reference implementation that shows how to use SharePoint webhooks using various Azure components such as Azure Web Jobs, Azure SQL Server and Azure Storage Queues."/>
-			<Item text="Azure Functions and SharePoint webhooks" url="apis/webhooks/sharepoint-webhooks-using-azure-functions" SEODescription="Explains how to use Azure Functions for hosting your SharePoint webhooks"/>
-			<Item text="SharePoint lists" url="apis/webhooks/lists">
-				<Item text="Overview" url="apis/webhooks/lists/overview-sharepoint-list-webhooks" SEODescription="SharePoint list webhooks notify your application about the events corresponding to list item changes for a given SharePoint list or a document library." />
-				<Item text="Create a subscription" url="apis/webhooks/lists/create-subscription" SEODescription="Create a SharePoint webhook subscription using an HTTP POST request." />
-				<Item text="Update a subscription" url="apis/webhooks/lists/update-subscription" SEODescription="Update a SharePoint webhook subscription using an HTTP PATCH request." />
-				<Item text="Delete a subscription" url="apis/webhooks/lists/delete-subscription" SEODescription="Delete a SharePoint webhook subscription using an HTTP DELETE request." />
-				<Item text="Get subscriptions" url="apis/webhooks/lists/get-subscription" SEODescription="Get one or more SharePoint webhook subscriptions using an HTTP GET request." />
-			</Item>
-		</Item>
-	</Item>
-	<Item text="Additional SharePoint Resources" url="external" SEODescription="">
-		<Item text="SharePoint Add-ins Docs" url="https://msdn.microsoft.com/en-us/library/office/fp179930.aspx" IsExternal="true" SEODescription="" />
-	</Item>
-	<Item text="SharePoint Framework Reference" url="https://dev.office.com/sharepoint/reference/spfx/sharepoint-framework-reference-overview" IsExternal="true" SEODescription="SharePoint Framework API reference" />
-	<Item text="SharePoint Framework Code Samples" url="http://aka.ms/spfx-samples" IsExternal="true" SEODescription="SharePoint Framework Code Samples" />
-	<Item text="SharePoint development overview" url="general-development/sharepoint-development-overview" SEODescription="">
-		<Item text="What's new for developers in SharePoint" url="general-development/what-s-new-for-developers-in-sharepoint" SEODescription=""/>
-		<Item text="Protocol handler error due to deprecated interface SharePoint 2016" url="general-development/protocol-handler-error-due-to-deprecated-interface-in-sharepoint-2016" SEODescription=""/>
-		<Item text="Programming models" url="general-development/programming-models-in-sharepoint" SEODescription="">
-			<Item text="SharePoint Add-ins compared with SharePoint solutions" url="general-development/sharepoint-add-ins-compared-with-sharepoint-solutions" SEODescription=""/>
-			<Item text="Build farm solutions" url="general-development/build-farm-solutions-in-sharepoint" SEODescription="">
-				<Item text="How to: Customize a field type using client-side rendering" url="general-development/how-to-customize-a-field-type-using-client-side-rendering" SEODescription=""/>
-				<Item text="URLs and tokens in SharePoint" url="general-development/urls-and-tokens-in-sharepoint" SEODescription=""/>
-				<Item text="Virtual directories in SharePoint solutions" url="general-development/virtual-directories-in-sharepoint-solutions" SEODescription=""/>
-			</Item>
-			<Item text="Access SharePoint from mobile and native device apps" url="general-development/access-sharepoint-from-mobile-and-native-device-apps" SEODescription=""/>
-			<Item text="Build Windows Phone apps that access SharePoint" url="general-development/build-windows-phone-apps-that-access-sharepoint" SEODescription="">
-				<Item text="How to: Set up an environment for developing mobile apps for SharePoint" url="general-development/how-to-set-up-an-environment-for-developing-mobile-apps-for-sharepoint" SEODescription=""/>
-				<Item text="Overview of Windows Phone SharePoint application templates in Visual Studio" url="general-development/overview-of-windows-phone-sharepoint-application-templates-in-visual-studio" SEODescription=""/>
-				<Item text="Architecture of the Windows Phone SharePoint List Application template" url="general-development/architecture-of-the-windows-phone-sharepoint-list-application-template" SEODescription=""/>
-				<Item text="How to: Create a Windows Phone SharePoint list app" url="general-development/how-to-create-a-windows-phone-sharepoint-list-app" SEODescription=""/>
-				<Item text="How to: Store and retrieve SharePoint list items on a Windows Phone" url="general-development/how-to-store-and-retrieve-sharepoint-list-items-on-a-windows-phone" SEODescription=""/>
-				<Item text="How to: Implement business logic and data validation in a Windows Phone app for SharePoint" url="general-development/how-to-implement-business-logic-and-data-validation-in-a-windows-phone-app-for-s" SEODescription=""/>
-				<Item text="How to: Support and convert SharePoint field types for Windows Phone apps" url="general-development/how-to-support-and-convert-sharepoint-field-types-for-windows-phone-apps" SEODescription=""/>
-				<Item text="How to: Customize list item queries and filter data for Windows Phone apps" url="general-development/how-to-customize-list-item-queries-and-filter-data-for-windows-phone-apps" SEODescription=""/>
-				<Item text="How to: Customize the user interface of a SharePoint list app for Windows Phone" url="general-development/how-to-customize-the-user-interface-of-a-sharepoint-list-app-for-windows-ph" SEODescription=""/>
-				<Item text="How to: Use multiple SharePoint lists in a Windows Phone app" url="general-development/how-to-use-multiple-sharepoint-lists-in-a-windows-phone-app" SEODescription=""/>
-				<Item text="How to: Configure and use push notifications in SharePoint apps for Windows Phone" url="general-development/how-to-configure-and-use-push-notifications-in-sharepoint-apps-for-windows" SEODescription=""/>
-				<Item text="How to: Create a mobile app in SharePoint that contains data from an external data source" url="general-development/how-to-create-a-mobile-app-in-sharepoint-that-contains-data-from-an-externa" SEODescription=""/>
-				<Item text="How to: Integrate maps with Windows Phone apps and SharePoint lists" url="general-development/how-to-integrate-maps-with-windows-phone-apps-and-sharepoint-lists" SEODescription=""/>
-				<Item text="How to: Build search-driven mobile apps with the Navigation and Event Logging REST interfaces" url="general-development/how-to-build-search-driven-mobile-apps-with-the-navigation-and-event-logging-res" SEODescription=""/>
-				<Item text="Overview of the SharePoint mobile object model" url="general-development/overview-of-the-sharepoint-mobile-object-model" SEODescription=""/>
-				<Item text="Overview of the SharePoint mobile client authentication object model" url="general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model" SEODescription=""/>
-				<Item text="How to: Export the Name field in a Document Library list to a mobile app" url="general-development/how-to-export-the-name-field-in-a-document-library-list-to-a-mobile-app" SEODescription=""/>
-				<Item text="Build localized applications for Windows Phone based on the SharePoint templates" url="general-development/build-localized-applications-for-windows-phone-based-on-the-sharepoint-templates" SEODescription=""/>
-				<Item text="Language support for Windows Phone in SharePoint" url="general-development/language-support-for-windows-phone-in-sharepoint" SEODescription=""/>
-				<Item text="Build mobile apps for other platforms using SharePoint" url="general-development/build-mobile-apps-for-other-platforms-using-sharepoint" SEODescription=""/>
-			</Item>
-			<Item text="Build reusable components for SharePoint" url="general-development/build-reusable-components-for-sharepoint" SEODescription=""/>
-			<Item text="Build sites for SharePoint" url="general-development/build-sites-for-sharepoint" SEODescription="">
-				<Item text="What's new with SharePoint site development" url="general-development/what-s-new-with-sharepoint-site-development" SEODescription=""/>
-				<Item text="Develop the site design in SharePoint" url="general-development/develop-the-site-design-in-sharepoint" SEODescription="">
-					<Item text="Overview of Design Manager" url="general-development/overview-of-design-manager-in-sharepoint" SEODescription=""/>
-					<Item text="Overview of the SharePoint page model" url="general-development/overview-of-the-sharepoint-page-model" SEODescription=""/>
-					<Item text="Master pages, the Master Page Gallery, and page layouts" url="general-development/master-pages-the-master-page-gallery-and-page-layouts-in-sharepoint" SEODescription="">
-						<Item text="How to: Map a network drive to the Master Page Gallery" url="general-development/how-to-map-a-network-drive-to-the-sharepoint-master-page-gallery" SEODescription=""/>
-						<Item text="How to: Apply a master page to a site" url="general-development/how-to-apply-a-master-page-to-a-site-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Create a page layout" url="general-development/how-to-create-a-page-layout-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Customize page layouts for a catalog-based site" url="general-development/how-to-customize-page-layouts-for-a-catalog-based-site-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Apply styles to page fields" url="general-development/how-to-apply-styles-to-page-fields-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Resolve errors and warnings when previewing a page" url="general-development/how-to-resolve-errors-and-warnings-when-previewing-a-page-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Convert an HTML file into a master page" url="general-development/how-to-convert-an-html-file-into-a-master-page-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Create a minimal master page" url="general-development/how-to-create-a-minimal-master-page-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Change the preview page in Design Manager" url="general-development/how-to-change-the-preview-page-in-sharepoint-design-manager" SEODescription=""/>
-						<Item text="SharePoint Online Suite Navigation control" url="general-development/sharepoint-online-suite-navigation-control" SEODescription=""/>
-					</Item>
-					<Item text="How to: Retrieve the URL of a Pages library" url="general-development/how-to-retrieve-the-url-of-a-pages-library" SEODescription=""/>
-					<Item text="Branding and design capabilities" url="general-development/sharepoint-design-manager-branding-and-design-capabilities" SEODescription="">
-						<Item text="Design packages" url="general-development/sharepoint-design-manager-design-packages" SEODescription=""/>
-						<Item text="Device channels" url="general-development/sharepoint-design-manager-device-channels" SEODescription=""/>
-						<Item text="Display templates" url="general-development/sharepoint-design-manager-display-templates" SEODescription=""/>
-						<Item text="Image renditions" url="general-development/sharepoint-design-manager-image-renditions" SEODescription=""/>
-						<Item text="Snippets" url="general-development/sharepoint-design-manager-snippets" SEODescription="">
-							<Item text="How to: Add a Device Channel Panel snippet" url="general-development/how-to-add-a-device-channel-panel-snippet-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Add an Edit Mode Panel snippet" url="general-development/how-to-add-an-edit-mode-panel-snippet-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Add a Web Part zone snippet" url="general-development/how-to-add-a-web-part-zone-snippet-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Add a Security Trim snippet" url="general-development/how-to-add-a-security-trim-snippet-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Brand snippets by using CSS" url="general-development/how-to-brand-snippets-by-using-css-in-sharepoint" SEODescription=""/>
-						</Item>
-						<Item text="Themes" url="general-development/themes-overview-for-sharepoint" SEODescription="">
-							<Item text="How to: Create a master page preview file" url="general-development/how-to-create-a-master-page-preview-file-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Deploy a custom theme" url="general-development/how-to-deploy-a-custom-theme-in-sharepoint" SEODescription=""/>
-							<Item text="How to: Make custom CSS files themable" url="general-development/how-to-make-custom-css-files-themable-in-sharepoint" SEODescription=""/>
-							<Item text="Upgrade custom themes and CSS" url="general-development/upgrade-custom-themes-and-css-to-sharepoint" SEODescription=""/>
-							<Item text="Color palettes and fonts" url="general-development/color-palettes-and-fonts-in-sharepoint" SEODescription=""/>
-						</Item>
-					</Item>
-				</Item>
-				<Item text="Managed metadata and navigation in SharePoint" url="general-development/managed-metadata-and-navigation-in-sharepoint" SEODescription="">
-					<Item text="Managed navigation in SharePoint" url="general-development/managed-navigation-in-sharepoint" SEODescription=""/>
-					<Item text="Content Search Web Part in SharePoint" url="general-development/content-search-web-part-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Use code to pin terms to navigation term sets in SharePoint" url="general-development/how-to-use-code-to-pin-terms-to-navigation-term-sets-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Publish SharePoint sites" url="general-development/publish-sharepoint-sites" SEODescription="">
-					<Item text="Cross-site publishing in SharePoint" url="general-development/cross-site-publishing-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="User segmentation in SharePoint" url="general-development/user-segmentation-in-sharepoint" SEODescription=""/>
-				<Item text="Minimal Download Strategy overview" url="general-development/minimal-download-strategy-overview" SEODescription=""/>
-				<Item text="Modify SharePoint components for MDS" url="general-development/modify-sharepoint-components-for-mds" SEODescription=""/>
-				<Item text="Optimize page performance" url="general-development/optimize-page-performance-in-sharepoint" SEODescription=""/>
-				<Item text="Optimize SharePoint stie accessibility" url="general-development/optimize-sharepoint-site-accessibility" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="Add SharePoint capabilities" url="general-development/add-sharepoint-capabilities" SEODescription="">
-			<Item text="Workflows" url="general-development/workflows-in-sharepoint" SEODescription="">
-				<Item text="Get started with workflows in SharePoint" url="general-development/get-started-with-workflows-in-sharepoint" SEODescription=""/>
-				<Item text="SharePoint workflow fundamentals" url="general-development/sharepoint-workflow-fundamentals" SEODescription=""/>
-				<Item text="What's new in workflows for SharePoint" url="general-development/what-s-new-in-workflows-for-sharepoint" SEODescription=""/>
-				<Item text="Prepare to set up and configure a SharePoint workflow development environment" url="general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment" SEODescription=""/>
-				<Item text="How to: Configure MSMQ for SharePoint workflows" url="general-development/how-to-configure-msmq-for-sharepoint-workflows" SEODescription=""/>
-				<Item text="Workflow initiation and configuration properties" url="general-development/workflow-initiation-and-configuration-properties" SEODescription=""/>
-				<Item text="SharePoint workflow development best practices" url="general-development/sharepoint-workflow-development-best-practices" SEODescription=""/>
-				<Item text="Debugging SharePoint Server workflows" url="general-development/debugging-sharepoint-server-workflows" SEODescription=""/>
-				<Item text="Using the pairing cmdlet Register-SPWorkflowService" url="general-development/using-the-pairing-cmdlet-register-spworkflowservice" SEODescription=""/>
-				<Item text="SharePoint workflow samples" url="general-development/sharepoint-workflow-samples" SEODescription=""/>
-				<Item text="Develop SharePoint workflows using Visual Studio" url="general-development/develop-sharepoint-workflows-using-visual-studio" SEODescription="">
-					<Item text="Create a SharePoint workflow app using Visual Studio 2012" url="general-development/create-a-sharepoint-workflow-app-using-visual-studio-2012" SEODescription=""/>
-					<Item text="How to: Create SharePoint Workflows using Visual Studio" url="general-development/how-to-create-sharepoint-workflows-using-visual-studio" SEODescription=""/>
-					<Item text="Working with the SharePoint Workflow Services Client Side Object Model" url="general-development/working-with-the-sharepoint-workflow-services-client-side-object-model" SEODescription=""/>
-					<Item text="Working with Web Services in SharePoint Workflows using Visual Studio 2012" url="general-development/working-with-web-services-in-sharepoint-workflows-using-visual-studio-2012" SEODescription=""/>
-					<Item text="Working with Tasks in SharePoint Workflows using Visual Studio 2012" url="general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012" SEODescription=""/>
-					<Item text="How to: Create Custom SharePoint Server Workflow Forms with Visual Studio 2012" url="general-development/how-to-create-custom-sharepoint-server-workflow-forms-with-visual-studio-20" SEODescription=""/>
-					<Item text="How to: Build and deploy workflow custom actions" url="general-development/how-to-build-and-deploy-workflow-custom-actions" SEODescription=""/>
-					<Item text="Use workflow interop for SharePoint" url="general-development/use-workflow-interop-for-sharepoint" SEODescription=""/>
-					<Item text="Common error messages in SharePoint workflow development" url="general-development/common-error-messages-in-sharepoint-workflow-development" SEODescription=""/>
-					<Item text="SharePoint workflow object model" url="general-development/sharepoint-workflow-object-model" SEODescription=""/>
-				</Item>
-				<Item text="Workflow development in SharePoint Designer and Visio" url="general-development/workflow-development-in-sharepoint-designer-and-visio" SEODescription="">
-					<Item text="What's changed in SharePoint Designer" url="general-development/what-s-changed-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Creating a workflow by using SharePoint Designer and the SharePoint Workflow platform" url="general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo" SEODescription=""/>
-					<Item text="Shapes in the SharePoint Server workflow template in Visio" url="general-development/shapes-in-the-sharepoint-server-workflow-template-in-visio" SEODescription=""/>
-					<Item text="Troubleshooting SharePoint Server workflow validation errors in Visio" url="general-development/troubleshooting-sharepoint-server-workflow-validation-errors-in-visio" SEODescription=""/>
-					<Item text="Understanding Dictionary actions in SharePoint Designer 2013" url="general-development/understanding-dictionary-actions-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Understanding Coordination actions in SharePoint Designer 2013" url="general-development/understanding-coordination-actions-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Understanding Task Actions in SharePoint Designer 2013" url="general-development/understanding-task-actions-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Understanding Eventing Actions in SharePoint Designer 2013" url="general-development/understanding-eventing-actions-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Getting familiar with Visual Designer for workflow in SharePoint Designer 2013" url="general-development/getting-familiar-with-visual-designer-for-workflow-in-sharepoint-designer" SEODescription=""/>
-					<Item text="Working with Web Services in SharePoint Workflows using SharePoint Designer 2013" url="general-development/working-with-web-services-in-sharepoint-workflows-using-sharepoint-designer" SEODescription=""/>
-					<Item text="Understanding how to package and deploy workflow in SharePoint" url="general-development/understanding-how-to-package-and-deploy-workflow-in-sharepoint" SEODescription=""/>
-					<Item text="Create a workflow with elevated permissions by using the SharePoint Workflow platform" url="general-development/create-a-workflow-with-elevated-permissions-by-using-the-sharepoint-workflo" SEODescription=""/>
-					<Item text="Matching the SharePoint Designer version with the farm version" url="general-development/matching-the-sharepoint-designer-version-with-the-farm-version" SEODescription=""/>
-					<Item text="Transfer a workflow between SharePoint Designer 2013 and Visio Professional 2013 (SharePoint 2010 Workflow platform)" url="general-development/transfer-a-workflow-between-sharepoint-designer-and-visio-professional" SEODescription=""/>
-				</Item>
-				<Item text="Workflow actions and activities reference" url="general-development/workflow-actions-and-activities-reference-for-sharepoint" SEODescription="">
-					<Item text="Workflow activity classes" url="general-development/workflow-activity-classes-in-sharepoint" SEODescription=""/>
-					<Item text="Workflow actions quick reference (SharePoint Workflow platform)" url="general-development/workflow-actions-quick-reference-sharepoint-workflow-platform" SEODescription=""/>
-					<Item text="Workflow actions available using the workflow interop bridge" url="general-development/workflow-actions-available-using-the-workflow-interop-bridge" SEODescription=""/>
-					<Item text="Workflow conditions quick reference (SharePoint 2010 Workflow platform)" url="general-development/workflow-conditions-quick-reference-sharepoint-2010-workflow-platform" SEODescription=""/>
-					<Item text="Workflow actions quick reference (SharePoint 2010 Workflow platform)" url="general-development/workflow-actions-quick-reference-sharepoint-2010-workflow-platform" SEODescription=""/>
-					<Item text="Visio shapes in SharePoint Designer 2013: A quick reference guide (SharePoint 2010 Workflow platform)" url="general-development/visio-shapes-in-sharepoint-designer-a-quick-reference-guide-sharepoint-2010" SEODescription=""/>
-					<Item text="Validation issues in Visio (SharePoint 2010 Workflow platform)" url="general-development/validation-issues-in-visio-sharepoint-2010-workflow-platform" SEODescription=""/>
-				</Item>
-			</Item>
-			<Item text="Social and collaboration" url="general-development/social-and-collaboration-features-in-sharepoint" SEODescription="">
-				<Item text="What's new for developers in social and collaboration features" url="general-development/what-s-new-for-developers-in-social-and-collaboration-features-in-sharepoint-201" SEODescription=""/>
-				<Item text="Get started developing with social features" url="general-development/get-started-developing-with-social-features-in-sharepoint" SEODescription="">
-					<Item text="How to: Learn to read and write to the social feed by using the .NET client object model" url="general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-net-client-object" SEODescription=""/>
-					<Item text="How to: Learn to read and write to the social feed by using the REST service" url="general-development/how-to-learn-to-read-and-write-to-the-social-feed-by-using-the-rest-service-in-s" SEODescription=""/>
-					<Item text="Social feed REST API reference" url="general-development/social-feed-rest-api-reference-for-sharepoint" SEODescription=""/>
-					<Item text="Following people and content REST API reference" url="general-development/following-people-and-content-rest-api-reference-for-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Work with social feeds" url="general-development/work-with-social-feeds-in-sharepoint" SEODescription="">
-					<Item text="How to: Create and delete posts and retrieve the social feed by using the .NET client object model" url="general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-net-cli" SEODescription=""/>
-					<Item text="How to: Create and delete posts and retrieve the social feed by using the JavaScript object model" url="general-development/how-to-create-and-delete-posts-and-retrieve-the-social-feed-by-using-the-javascr" SEODescription=""/>
-					<Item text="How to: Include mentions, tags, and links to sites and documents in posts" url="general-development/how-to-include-mentions-tags-and-links-to-sites-and-documents-in-posts-in-sharep" SEODescription=""/>
-					<Item text="How to: Embed images, videos, and documents in posts" url="general-development/how-to-embed-images-videos-and-documents-in-posts-in-sharepoint-server" SEODescription=""/>
-					<Item text="Reference threads and digest threads in social feeds" url="general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds" SEODescription=""/>
-				</Item>
-				<Item text="Follow people" url="general-development/follow-people-in-sharepoint" SEODescription="">
-					<Item text="How to: Follow people by using the .NET client object model" url="general-development/how-to-follow-people-by-using-the-net-client-object-model-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Follow people by using the JavaScript object model" url="general-development/how-to-follow-people-by-using-the-javascript-object-model-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Follow content" url="general-development/follow-content-in-sharepoint" SEODescription="">
-					<Item text="How to: Follow documents and sites by using the .NET client object model" url="general-development/how-to-follow-documents-and-sites-by-using-the-net-client-object-model-in-sharep" SEODescription=""/>
-					<Item text="How to: Follow documents, sites, and tags by using the REST service" url="general-development/how-to-follow-documents-sites-and-tags-by-using-the-rest-service-in-sharepoint-2" SEODescription=""/>
-				</Item>
-				<Item text="Work with user profiles" url="general-development/work-with-user-profiles-in-sharepoint" SEODescription="">
-					<Item text="How to: Retrieve user profile properties by using the .NET client object model" url="general-development/how-to-retrieve-user-profile-properties-by-using-the-net-client-object-model-in" SEODescription=""/>
-					<Item text="How to: Retrieve user profile properties by using the JavaScript object model" url="general-development/how-to-retrieve-user-profile-properties-by-using-the-javascript-object-model-in" SEODescription=""/>
-					<Item text="How to: Work with user profiles by using the server object model" url="general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj" SEODescription=""/>
-				</Item>
-			</Item>
-			<Item text="Integrating location and map functionality" url="general-development/integrating-location-and-map-functionality-in-sharepoint" SEODescription="">
-				<Item text="How to: Add a Geolocation column to a list programmatically in SharePoint" url="general-development/how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint" SEODescription=""/>
-				<Item text="Create a map view for the Geolocation field in SharePoint" url="general-development/create-a-map-view-for-the-geolocation-field-in-sharepoint" SEODescription=""/>
-				<Item text="How to: Set the Bing Maps key at the web and farm level in SharePoint" url="general-development/how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint" SEODescription=""/>
-				<Item text="How to: Extend the Geolocation field type using client-side rendering" url="general-development/how-to-extend-the-geolocation-field-type-using-client-side-rendering" SEODescription=""/>
-			</Item>
-			<Item text="Search in SharePoint" url="general-development/search-in-sharepoint" SEODescription="">
-				<Item text="What's new in SharePoint search for developers" url="general-development/what-s-new-in-sharepoint-search-for-developers" SEODescription=""/>
-				<Item text="Searching new content with SharePoint Search" url="general-development/searching-new-content-with-sharepoint-search" SEODescription="">
-					<Item text="Search connector framework" url="general-development/search-connector-framework-in-sharepoint" SEODescription="">
-						<Item text="Enhancing the BDC model file for Search" url="general-development/enhancing-the-bdc-model-file-for-search-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Crawl associated external content types" url="general-development/how-to-crawl-associated-external-content-types-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Crawl binary large objects (BLOBs)" url="general-development/how-to-crawl-binary-large-objects-blobs-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Configure item-level security" url="general-development/how-to-configure-item-level-security-in-sharepoint" SEODescription=""/>
-					</Item>
-				</Item>
-				<Item text="Configure search in SharePoint" url="general-development/configure-search-in-sharepoint" SEODescription="">
-					<Item text="Custom word breakers in SharePoint Server" url="general-development/custom-word-breakers-in-sharepoint-server" SEODescription=""/>
-					<Item text="Custom content processing with the Content Enrichment web service callout" url="general-development/custom-content-processing-with-the-content-enrichment-web-service-callout" SEODescription="">
-						<Item text="How to: Use the Content Enrichment web service callout for SharePoint Server" url="general-development/how-to-use-the-content-enrichment-web-service-callout-for-sharepoint-server" SEODescription=""/>
-						<Item text="Trigger expression syntax" url="general-development/trigger-expressions-syntax-in-sharepoint" SEODescription=""/>
-					</Item>
-				</Item>
-				<Item text="Building search queries in SharePoint" url="general-development/building-search-queries-in-sharepoint" SEODescription="">
-					<Item text="Keyword Query Language (KQL) syntax reference" url="general-development/keyword-query-language-kql-syntax-reference" SEODescription=""/>
-					<Item text="FAST Query Language (FQL) syntax reference" url="general-development/fast-query-language-fql-syntax-reference" SEODescription=""/>
-					<Item text="Using the SharePoint search Query APIs" url="general-development/using-the-sharepoint-search-query-apis" SEODescription=""/>
-				</Item>
-				<Item text="SharePoint Search REST API overview" url="general-development/sharepoint-search-rest-api-overview" SEODescription="">
-					<Item text="Retrieving query suggestions using the Search REST service" url="general-development/retrieving-query-suggestions-using-the-search-rest-service" SEODescription=""/>
-				</Item>
-				<Item text="Search add-ins in SharePoint" url="general-development/search-add-ins-in-sharepoint" SEODescription=""/>
-				<Item text="Customizing search results in SharePoint" url="general-development/customizing-search-results-in-sharepoint" SEODescription=""/>
-				<Item text="Sorting search results in SharePoint" url="general-development/sorting-search-results-in-sharepoint" SEODescription=""/>
-				<Item text="Customizing ranking models to improve relevance" url="general-development/customizing-ranking-models-to-improve-relevance-in-sharepoint" SEODescription=""/>
-				<Item text="Custom security trimming for Search in SharePoint Server" url="general-development/custom-security-trimming-for-search-in-sharepoint-server" SEODescription="">
-					<Item text="How to: Use a custom security trimmer for SharePoint Server search results" url="general-development/how-to-use-a-custom-security-trimmer-for-sharepoint-server-search-results" SEODescription=""/>
-				</Item>
-				<Item text="Exporting and importing search configuration settings programmatically" url="general-development/exporting-and-importing-search-configuration-settings-in-sharepoint" SEODescription=""/>
-				<Item text="Query Refinement in SharePoint" url="general-development/query-refinement-in-sharepoint" SEODescription=""/>
-			</Item>
-			<Item text="Business Connectivity Services" url="general-development/business-connectivity-services-in-sharepoint" SEODescription="">
-				<Item text="What's new in Business Connectivity Services" url="general-development/what-s-new-in-business-connectivity-services-in-sharepoint" SEODescription=""/>
-				<Item text="Get started with Business Connectivity Services" url="general-development/get-started-with-business-connectivity-services-in-sharepoint" SEODescription="">
-					<Item text="Setting up a development environment for BCS" url="general-development/setting-up-a-development-environment-for-bcs-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="External content types" url="general-development/external-content-types-in-sharepoint" SEODescription="">
-					<Item text="How to: Create external content types for SQL Server" url="general-development/how-to-create-external-content-types-for-sql-server-in-sharepoint" SEODescription=""/>
-					<Item text="Create associations in SharePoint" url="general-development/create-associations-in-sharepoint" SEODescription=""/>
-					<Item text="Add-in-scoped external content types" url="general-development/add-in-scoped-external-content-types-in-sharepoint" SEODescription="">
-						<Item text="How to: Create an add-in-scoped external content type" url="general-development/how-to-create-an-add-in-scoped-external-content-type-in-sharepoint" SEODescription=""/>
-						<Item text="How to: Convert an add-in-scoped external content type to tenant-scoped" url="general-development/how-to-convert-an-add-in-scoped-external-content-type-to-tenant-scoped" SEODescription=""/>
-						<Item text="How to: Access external data using REST" url="general-development/how-to-access-external-data-with-rest-in-sharepoint" SEODescription=""/>
-					</Item>
-				</Item>
-				<Item text="Using OData sources with Business Connectivity Services" url="general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint" SEODescription="">
-					<Item text="How to: Create an external content type from an OData source" url="general-development/how-to-create-an-external-content-type-from-an-odata-source-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create an OData data service for use as a BCS external system" url="general-development/how-to-create-an-odata-data-service-for-use-as-a-bcs-external-system" SEODescription=""/>
-					<Item text="How to: Create an external list using an OData data source" url="general-development/how-to-create-an-external-list-using-an-odata-data-source-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="External events and alerts" url="general-development/external-events-and-alerts-in-sharepoint" SEODescription="">
-					<Item text="How to: Create external event receivers" url="general-development/how-to-create-external-event-receivers" SEODescription=""/>
-				</Item>
-				<Item text="Get started using the client object model with external data" url="general-development/get-started-using-the-client-object-model-with-external-data-in-sharepoint" SEODescription="">
-					<Item text="How to: Use the client code library to access external data" url="general-development/how-to-use-the-client-code-library-to-access-external-data-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Business Connectivity Services programmers reference" url="general-development/business-connectivity-services-programmers-reference-for-sharepoint" SEODescription="">
-					<Item text="BCS REST API reference" url="general-development/bcs-rest-api-reference-for-sharepoint" SEODescription=""/>
-					<Item text="BCS client object model reference" url="general-development/bcs-client-object-model-reference-for-sharepoint" SEODescription=""/>
-					<Item text="Changes in the BDC model schema for SharePoint" url="general-development/changes-in-the-bdc-model-schema-for-sharepoint" SEODescription=""/>
-					<Item text="BDC model schema reference" url="general-development/bdc-model-schema-reference-for-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Create hybrid connectivity apps for SharePoint" url="general-development/create-hybrid-connectivity-apps-for-sharepoint" SEODescription=""/>
-				<Item text="Developing with Duet Enterprise 2.0" url="general-development/developing-with-duet-enterprise-2-0" SEODescription="">
-					<Item text="How to: Use SAP workflow with Duet Enterprise 2.0" url="general-development/how-to-use-sap-workflow-with-duet-enterprise-2-0" SEODescription=""/>
-					<Item text="How to: Use SAP Reporting with Duet Enterprise 2.0" url="general-development/how-to-use-sap-reporting-with-duet-enterprise-2-0" SEODescription=""/>
-				</Item>
-			</Item>
-			<Item text="Office and SharePoint application services" url="general-development/office-and-sharepoint-application-services" SEODescription="">
-				<Item text="Excel Services in SharePoint" url="general-development/excel-services-in-sharepoint" SEODescription="">
-					<Item text="Getting Started with Excel Services" url="general-development/getting-started-with-excel-services" SEODescription="">
-						<Item text="Excel Services Overview" url="general-development/excel-services-overview" SEODescription=""/>
-						<Item text="Excel Services Architecture" url="general-development/excel-services-architecture" SEODescription=""/>
-						<Item text="Excel Services Development Roadmap" url="general-development/excel-services-development-roadmap" SEODescription=""/>
-						<Item text="Supported and Unsupported Features" url="general-development/supported-and-unsupported-features" SEODescription=""/>
-						<Item text="Excel Services Blogs, Forums, and Resources" url="general-development/excel-services-blogs-forums-and-resources" SEODescription=""/>
-					</Item>
-					<Item text="Excel Web Services" url="general-development/excel-web-services" SEODescription="">
-						<Item text="What's New in Excel Web Services" url="general-development/what-s-new-in-excel-web-services" SEODescription=""/>
-						<Item text="Accessing the SOAP API" url="general-development/accessing-the-soap-api" SEODescription=""/>
-						<Item text="Loop-Back SOAP Calls and Direct Linking" url="general-development/loop-back-soap-calls-and-direct-linking" SEODescription=""/>
-						<Item text="Walkthrough: Developing a Custom Application Using Excel Web Services" url="general-development/walkthrough-developing-a-custom-application-using-excel-web-services" SEODescription="">
-							<Item text="Step 1: Creating the Web Service Client Project" url="general-development/step-1-creating-the-web-service-client-project" SEODescription=""/>
-							<Item text="Step 2: Adding a Web Reference" url="general-development/step-2-adding-a-web-reference" SEODescription=""/>
-							<Item text="Step 3: Accessing the Web Service" url="general-development/step-3-accessing-the-web-service" SEODescription=""/>
-							<Item text="Step 4: Building and Testing the Application" url="general-development/step-4-building-and-testing-the-application" SEODescription=""/>
-						</Item>
-						<Item text="Excel Services Error Codes" url="general-development/excel-services-error-codes" SEODescription=""/>
-						<Item text="How to: Get Values from Ranges" url="general-development/how-to-get-values-from-ranges" SEODescription=""/>
-						<Item text="How to: Set Values of Ranges" url="general-development/how-to-set-values-of-ranges" SEODescription=""/>
-						<Item text="How to: Specify a Range Address and Sheet Name" url="general-development/how-to-specify-a-range-address-and-sheet-name" SEODescription=""/>
-						<Item text="How to: Get an Entire Workbook or a Snapshot" url="general-development/how-to-get-an-entire-workbook-or-a-snapshot" SEODescription=""/>
-						<Item text="How to: Use the CloseWorkbook Method Call Asynchronously" url="general-development/how-to-use-the-closeworkbook-method-call-asynchronously" SEODescription=""/>
-						<Item text="How to: Set Various Credentials" url="general-development/how-to-set-various-credentials" SEODescription=""/>
-						<Item text="How to: Refresh Data" url="general-development/how-to-refresh-data" SEODescription=""/>
-						<Item text="How to: Use the SubCode Property to Capture Error Codes" url="general-development/how-to-use-the-subcode-property-to-capture-error-codes" SEODescription=""/>
-					</Item>
-					<Item text="Excel Services User-Defined Functions" url="general-development/excel-services-user-defined-functions" SEODescription="">
-						<Item text="Understanding Excel Services UDFs" url="general-development/understanding-excel-services-udfs" SEODescription=""/>
-						<Item text="Walkthrough: Developing a Managed-Code UDF" url="general-development/walkthrough-developing-a-managed-code-udf" SEODescription="">
-							<Item text="Step 1: Creating a Project and Adding a UDF Reference" url="general-development/step-1-creating-a-project-and-adding-a-udf-reference" SEODescription=""/>
-							<Item text="Step 2: Creating a Managed-Code UDF" url="general-development/step-2-creating-a-managed-code-udf" SEODescription=""/>
-							<Item text="Step 3: Deploying and Enabling UDFs" url="general-development/step-3-deploying-and-enabling-udfs" SEODescription=""/>
-							<Item text="Step 4: Testing and Calling UDFs from Cells" url="general-development/step-4-testing-and-calling-udfs-from-cells" SEODescription=""/>
-						</Item>
-						<Item text="Frequently Asked Questions About Excel Services UDFs" url="general-development/frequently-asked-questions-about-excel-services-udfs" SEODescription=""/>
-						<Item text="How to: Enable UDFs" url="general-development/how-to-enable-udfs" SEODescription=""/>
-						<Item text="How to: Create a UDF That Calls a Web Service" url="general-development/how-to-create-a-udf-that-calls-a-web-service" SEODescription=""/>
-						<Item text="How to: Access an External Data Source from a UDF" url="general-development/how-to-access-an-external-data-source-from-a-udf" SEODescription=""/>
-						<Item text="How to: Deploy UDFs Using SharePoint Foundation Solutions" url="general-development/how-to-deploy-udfs-using-sharepoint-foundation-solutions" SEODescription=""/>
-						<Item text="How to: Restrict UDF Code Access Security Permissions" url="general-development/how-to-restrict-udf-code-access-security-permissions" SEODescription=""/>
-					</Item>
-					<Item text="Excel Web Access" url="general-development/excel-web-access" SEODescription="">
-						<Item text="How to: Programmatically Add an Excel Web Access Web Part to a Page" url="general-development/how-to-programmatically-add-an-excel-web-access-web-part-to-a-page" SEODescription=""/>
-						<Item text="How to: Locate and Copy Microsoft.Office.Excel.WebUI.dll and Microsoft.Office.Excel.WebUI.Internal.dll" url="general-development/how-to-locate-and-copy-microsoft-office-excel-webui-dll-and-microsoft-office-exc" SEODescription=""/>
-					</Item>
-					<Item text="Excel Services ECMAScript (JavaScript, JScript)" url="general-development/excel-services-ecmascript-javascript-jscript" SEODescription="">
-						<Item text="Walkthrough: Developing Using the Content Editor Web Part" url="general-development/walkthrough-developing-using-the-content-editor-web-part" SEODescription="">
-							<Item text="Step 1: Creating a ECMAScript Text File" url="general-development/step-1-creating-a-ecmascript-text-file" SEODescription=""/>
-							<Item text="Step 2: Adding the Content Editor and Excel Services Web Parts" url="general-development/step-2-adding-the-content-editor-and-excel-services-web-parts" SEODescription=""/>
-						</Item>
-						<Item text="Excel Services ECMAScript Overview" url="general-development/excel-services-ecmascript-overview" SEODescription=""/>
-						<Item text="JavaScript user-defined functions overview" url="general-development/javascript-user-defined-functions-overview" SEODescription=""/>
-						<Item text="Working with the Excel Services JavaScript object model" url="general-development/working-with-the-excel-services-javascript-object-model" SEODescription=""/>
-						<Item text="How to: Create a mashup that uses an embedded workbook and Bing Maps" url="general-development/how-to-create-a-mashup-that-uses-an-embedded-workbook-and-bing-maps" SEODescription=""/>
-					</Item>
-					<Item text="Excel Services REST API" url="general-development/excel-services-rest-api" SEODescription="">
-						<Item text="Excel Services REST API Overview" url="general-development/excel-services-rest-api-overview" SEODescription=""/>
-						<Item text="Basic URI Structure and Path" url="general-development/basic-uri-structure-and-path" SEODescription=""/>
-						<Item text="Discovery in Excel Services REST API" url="general-development/discovery-in-excel-services-rest-api" SEODescription=""/>
-						<Item text="Resources URI for Excel Services REST API" url="general-development/resources-uri-for-excel-services-rest-api" SEODescription=""/>
-						<Item text="Getting Ranges Using Atom Feed and HTML Fragment" url="general-development/getting-ranges-using-atom-feed-and-html-fragment" SEODescription=""/>
-						<Item text="Sample URI For Excel Services REST API" url="general-development/sample-uri-for-excel-services-rest-api" SEODescription=""/>
-						<Item text="Accessing a Schema" url="general-development/accessing-a-schema" SEODescription=""/>
-						<Item text="Unsupported Features in Excel Services REST API" url="general-development/unsupported-features-in-excel-services-rest-api" SEODescription=""/>
-						<Item text="Advanced Scenarios and Additional Samples" url="general-development/advanced-scenarios-and-additional-samples" SEODescription=""/>
-						<Item text="Using OData with Excel Services REST in SharePoint" url="general-development/using-odata-with-excel-services-rest-in-sharepoint" SEODescription=""/>
-						<Item text="Requesting Excel workbook data from SharePoint Server using OData" url="general-development/requesting-excel-workbook-data-from-sharepoint-server-using-odata" SEODescription=""/>
-					</Item>
-					<Item text="General Guidelines" url="general-development/general-guidelines" SEODescription="">
-						<Item text="Excel Services Alerts" url="general-development/excel-services-alerts" SEODescription=""/>
-						<Item text="Excel Services Known Issues and Tips" url="general-development/excel-services-known-issues-and-tips" SEODescription=""/>
-						<Item text="Excel Services Best Practices" url="general-development/excel-services-best-practices" SEODescription=""/>
-						<Item text="How to: Trust a Location" url="general-development/how-to-trust-a-location" SEODescription=""/>
-						<Item text="How to: Save from Excel Client to the Server" url="general-development/how-to-save-from-excel-client-to-the-server" SEODescription=""/>
-						<Item text="How to: Save to the Server to Prepare for Programmatic Access" url="general-development/how-to-save-to-the-server-to-prepare-for-programmatic-access" SEODescription=""/>
-						<Item text="How to: Catch Exceptions" url="general-development/how-to-catch-exceptions" SEODescription=""/>
-					</Item>
-					<Item text="Removing Excel Interactive View from a webpage" url="general-development/removing-excel-interactive-view-from-a-webpage" SEODescription=""/>
-				</Item>
-				<Item text="Machine Translation Services in SharePoint" url="general-development/machine-translation-services-in-sharepoint" SEODescription=""/>
-				<Item text="PerformancePoint Services in SharePoint" url="general-development/performancepoint-services-in-sharepoint" SEODescription="">
-					<Item text="How to: Create report renderers for PerformancePoint Services" url="general-development/how-to-create-report-renderers-for-performancepoint-services-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create report editors for PerformancePoint Services" url="general-development/how-to-create-report-editors-for-performancepoint-services-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create filter data providers for PerformancePoint Services" url="general-development/how-to-create-filter-data-providers-for-performancepoint-services-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create filter editors for PerformancePoint Services" url="general-development/how-to-create-filter-editors-for-performancepoint-services-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create tabular data source providers for PerformancePoint Services" url="general-development/how-to-create-tabular-data-source-providers-for-performancepoint-services-in-sha" SEODescription=""/>
-					<Item text="How to: Create tabular data source editors#for PerformancePoint Services" url="general-development/how-to-create-tabular-data-source-editors-for-performancepoint-services-in-share" SEODescription=""/>
-					<Item text="How to: Create scorecard transforms for PerformancePoint Services" url="general-development/how-to-create-scorecard-transforms-for-performancepoint-services-in-sharepoint-2" SEODescription=""/>
-				</Item>
-				<Item text="PowerPoint Automation Services in SharePoint" url="general-development/powerpoint-automation-services-in-sharepoint" SEODescription=""/>
-				<Item text="Develop Access web apps" url="general-development/develop-access-web-apps" SEODescription="">
-					<Item text="What's new in Access" url="general-development/what-s-new-in-access" SEODescription=""/>
-				</Item>
-				<Item text="Visio Services in SharePoint" url="general-development/visio-services-in-sharepoint" SEODescription=""/>
-				<Item text="What's new in Word Automation Services for developers" url="general-development/what-s-new-in-word-automation-services-for-developers" SEODescription=""/>
-				<Item text="Extend the fixed-format export feature in Word Automation Services" url="general-development/extend-the-fixed-format-export-feature-in-word-automation-services" SEODescription=""/>
-			</Item>
-			<Item text="Authentication, authorization, and security in SharePoint" url="general-development/authentication-authorization-and-security-in-sharepoint" SEODescription="">
-				<Item text="Authorization, users, groups, and the object model in SharePoint" url="general-development/authorization-users-groups-and-the-object-model-in-sharepoint" SEODescription=""/>
-				<Item text="Role, inheritance, elevation of privilege, and password changes in SharePoint" url="general-development/role-inheritance-elevation-of-privilege-and-password-changes-in-sharepoint" SEODescription=""/>
-				<Item text="Claims-based identity in SharePoint" url="general-development/claims-based-identity-in-sharepoint" SEODescription="">
-					<Item text="Incoming claims: Signing into SharePoint" url="general-development/incoming-claims-signing-into-sharepoint" SEODescription=""/>
-					<Item text="Claims provider in SharePoint" url="general-development/claims-provider-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Create a claims provider in SharePoint" url="general-development/how-to-create-a-claims-provider-in-sharepoint" SEODescription=""/>
-					<Item text="How to: Deploy a claims provider in SharePoint" url="general-development/how-to-deploy-a-claims-provider-in-sharepoint" SEODescription=""/>
-				</Item>
-				<Item text="Claims-based identity and concepts in SharePoint" url="general-development/claims-based-identity-and-concepts-in-sharepoint" SEODescription="">
-					<Item text="Sample delegation, federation, and authentication scenario in SharePoint" url="general-development/sample-delegation-federation-and-authentication-scenario-in-sharepoint" SEODescription=""/>
-					<Item text="Claims-based identity term definitions" url="general-development/claims-based-identity-term-definitions" SEODescription=""/>
-				</Item>
-				<Item text="Configuration, administration, and resources in SharePoint" url="general-development/configuration-administration-and-resources-in-sharepoint" SEODescription=""/>
-			</Item>
-			<Item text="eDiscovery" url="general-development/ediscovery-in-sharepoint" SEODescription="">
-				<Item text="What's new in SharePoint eDiscovery and compliance" url="general-development/what-s-new-in-sharepoint-ediscovery-and-compliance" SEODescription=""/>
-			</Item>
-			<Item text="CMIS in SharePoint" url="general-development/content-management-interoperability-services-cmis-in-sharepoint" SEODescription=""/>
-			<Item text="The XLIFF interchange file format in SharePoint" url="general-development/the-xliff-interchange-file-format-in-sharepoint" SEODescription=""/>
-		</Item>
-		<Item text="Create SharePoint no-code solutions" url="general-development/create-sharepoint-no-code-solutions" SEODescription="">
-			<Item text="SharePoint Composites Handbook" url="general-development/sharepoint-composites-handbook" SEODescription=""/>
-			<Item text="Save, download, and upload a SharePoint site as a template" url="general-development/save-download-and-upload-a-sharepoint-site-as-a-template" SEODescription=""/>
-		</Item>
-		<Item text="Upgrade site customizations" url="general-development/upgrade-site-customizations-for-sharepoint" SEODescription="">
-			<Item text="Upgrade web templates" url="general-development/upgrade-web-templates-for-sharepoint" SEODescription=""/>
-			<Item text="Use Feature upgrade to apply new SharePoint master pages when upgrading from SharePoint 2010" url="general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro" SEODescription=""/>
-		</Item>
-		<Item text="Set up a general development environment for SharePoint" url="general-development/set-up-a-general-development-environment-for-sharepoint" SEODescription=""/>
-		<Item text="How-tos for SharePoint" url="general-development/how-tos-for-sharepoint" SEODescription=""/>
-		<Item text="Code samples for SharePoint" url="general-development/code-samples-for-sharepoint" SEODescription=""/>
-		<Item text="Choose the right API set in SharePoint" url="general-development/choose-the-right-api-set-in-sharepoint" SEODescription=""/>
-		<Item text="Set up and configure SharePoint Workflow Manager" url="general-development/set-up-and-configure-sharepoint-workflow-manager" SEODescription=""/>
-		<Item text="SharePoint Server Application Lifecycle Management" url="general-development/sharepoint-server-application-lifecycle-management" SEODescription=""/>
-		<Item text="Accessibility in SharePoint" url="general-development/accessibility-in-sharepoint" SEODescription=""/>
-		<Item text="How to: Detect the installed SKU of SharePoint" url="general-development/how-to-detect-the-installed-sku-of-sharepoint" SEODescription=""/>
-		<Item text="How to: Avoid getting throttled or blocked in SharePoint Online" url="general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online" SEODescription=""/>
-		<Item text="Overview of SharePoint and the Volume Shadow Copy Service" url="general-development/overview-of-sharepoint-and-the-volume-shadow-copy-service" SEODescription="">
-			<Item text="SharePoint VSS Writer" url="general-development/sharepoint-vss-writer" SEODescription=""/>
-			<Item text="VSS requestors and SharePoint" url="general-development/vss-requestors-and-sharepoint" SEODescription=""/>
-			<Item text="How to: Create a VSS requestor for use with SharePoint" url="general-development/how-to-create-a-vss-requestor-for-use-with-sharepoint" SEODescription=""/>
-			<Item text="How to: Back up and restore SharePoint using a VSS requestor" url="general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor" SEODescription=""/>
-			<Item text="How to: Back up and restore a search service application in SharePoint using VSS" url="general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using" SEODescription=""/>
-		</Item>
-	</Item>
-	<Item text="SharePoint Add-ins" url="sp-add-ins/sharepoint-add-ins" SEODescription="">
-		<Item text="New name for apps for SharePoint" url="sp-add-ins/new-name-for-apps-for-sharepoint" SEODescription=""/>
-		<Item text="Get started creating SharePoint-hosted SharePoint Add-ins" url="sp-add-ins/get-started-creating-sharepoint-hosted-sharepoint-add-ins" SEODescription="">
-			<Item text="1. Deploy and install a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/deploy-and-install-a-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-			<Item text="2. Add custom columns to a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-custom-columns-to-a-sharepoint-hostedsharepoint-add-in" SEODescription=""/>
-			<Item text="3. Add a custom content type to a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-a-custom-content-type-to-a-sharepoint-hostedsharepoint-add-in" SEODescription=""/>
-			<Item text="4. Add a Web Part to a page in a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-			<Item text="5. Add a workflow to a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-a-workflow-to-a-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-			<Item text="6. Add a custom page and style to a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-a-custom-page-and-style-to-a-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-			<Item text="7. Add custom client-side rendering to a SharePoint-hosted SharePoint Add-in" url="sp-add-ins/add-custom-client-side-rendering-to-a-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-			<Item text="8. Create a custom ribbon button in the host web of a SharePoint Add-in" url="sp-add-ins/create-a-custom-ribbon-button-in-the-host-web-of-a-sharepoint-add-in" SEODescription=""/>
-			<Item text="9. Use the SharePoint JavaScript APIs to work with SharePoint data" url="sp-add-ins/use-the-sharepoint-javascript-apis-to-work-with-sharepoint-data" SEODescription=""/>
-			<Item text="10. Work with host web data from JavaScript in the add-in web" url="sp-add-ins/work-with-host-web-data-from-javascript-in-the-add-in-web" SEODescription=""/>
-		</Item>
-		<Item text="Get started creating provider-hosted SharePoint Add-ins" url="sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins" SEODescription="">
-			<Item text="1. Give your provider-hosted add-in the SharePoint look-and-feel" url="sp-add-ins/give-your-provider-hosted-add-in-the-sharepoint-look-and-feel" SEODescription=""/>
-			<Item text="2. Include a custom button in the provider-hosted add-in" url="sp-add-ins/include-a-custom-button-in-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="3. Get a quick overview of the SharePoint object model" url="sp-add-ins/get-a-quick-overview-of-the-sharepoint-object-model" SEODescription=""/>
-			<Item text="4. Add SharePoint write operations to the provider-hosted add-in" url="sp-add-ins/add-sharepoint-write-operations-to-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="5. Include an add-in part in the provider-hosted add-in" url="sp-add-ins/include-an-add-in-part-in-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="6. Handle add-in events in the provider-hosted add-in" url="sp-add-ins/handle-add-in-events-in-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="7. Add first-run logic to the provider-hosted add-in" url="sp-add-ins/add-first-run-logic-to-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="8. Programmatically deploy a custom button in the provider-hosted add-in" url="sp-add-ins/programmatically-deploy-a-custom-button-in-the-provider-hosted-add-in" SEODescription=""/>
-			<Item text="9. Handle list item events in the provider-hosted add-in" url="sp-add-ins/handle-list-item-events-in-the-provider-hosted-add-in" SEODescription=""/>
-		</Item>
-		<Item text="Design" url="sp-add-ins/design-sharepoint-add-ins" SEODescription="">
-			<Item text="Three ways to think about design options for SharePoint Add-ins" url="sp-add-ins/three-ways-to-think-about-design-options-for-sharepoint-add-ins" SEODescription=""/>
-			<Item text="Important aspects of the SharePoint Add-in architecture and development landscape" url="sp-add-ins/important-aspects-of-the-sharepoint-add-in-architecture-and-development-landscap" SEODescription="">
-				<Item text="Choose patterns for developing and hosting your SharePoint Add-in" url="sp-add-ins/choose-patterns-for-developing-and-hosting-your-sharepoint-add-in" SEODescription=""/>
-				<Item text="Host webs, add-in webs, and SharePoint components" url="sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint" SEODescription=""/>
-			</Item>
-			<Item text="Secure data access and client object models for SharePoint Add-ins" url="sp-add-ins/secure-data-access-and-client-object-models-for-sharepoint-add-ins" SEODescription=""/>
-			<Item text="UX design for SharePoint Add-ins" url="sp-add-ins/ux-design-for-sharepoint-add-ins" SEODescription="">
-				<Item text="SharePoint Add-ins UX design guidelines" url="sp-add-ins/sharepoint-add-ins-ux-design-guidelines" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="Develop" url="sp-add-ins/develop-sharepoint-add-ins" SEODescription="">
-			<Item text="Explore the app manifest structure and the package of a SharePoint Add-in" url="sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in" SEODescription="">
-				<Item text="URL strings and tokens in SharePoint Add-ins" url="sp-add-ins/url-strings-and-tokens-in-sharepoint-add-ins" SEODescription=""/>
-			</Item>
-			<Item text="SharePoint .NET Server, CSOM, JSOM, and REST API index" url="sp-add-ins/sharepoint-net-server-csom-jsom-and-rest-api-index" SEODescription=""/>
-			<Item text="Complete basic operations using SharePoint client library code" url="sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code" SEODescription=""/>
-			<Item text="Complete basic operations using JavaScript library code in SharePoint" url="sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint" SEODescription=""/>
-			<Item text="Get to know the SharePoint REST service" url="sp-add-ins/get-to-know-the-sharepoint-rest-service" SEODescription="">
-				<Item text="Complete basic operations using SharePoint REST endpoints" url="sp-add-ins/complete-basic-operations-using-sharepoint-rest-endpoints" SEODescription=""/>
-				<Item text="Working with lists and list items with REST" url="sp-add-ins/working-with-lists-and-list-items-with-rest" SEODescription=""/>
-				<Item text="Working with folders and files with REST" url="sp-add-ins/working-with-folders-and-files-with-rest" SEODescription=""/>
-				<Item text="Determine SharePoint REST service endpoint URIs" url="sp-add-ins/determine-sharepoint-rest-service-endpoint-uris" SEODescription=""/>
-				<Item text="Use OData query operations in SharePoint REST requests" url="sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests" SEODescription=""/>
-				<Item text="Navigate the SharePoint data structure represented in the REST service" url="sp-add-ins/navigate-the-sharepoint-data-structure-represented-in-the-rest-service" SEODescription=""/>
-				<Item text="Synchronize SharePoint items using the REST service" url="sp-add-ins/synchronize-sharepoint-items-using-the-rest-service" SEODescription=""/>
-				<Item text="Upload a file by using the REST API and jQuery" url="sp-add-ins/upload-a-file-by-using-the-rest-api-and-jquery" SEODescription=""/>
-				<Item text="Set custom permissions on a list by using the REST interface" url="sp-add-ins/set-custom-permissions-on-a-list-by-using-the-rest-interface" SEODescription=""/>
-				<Item text="Make batch requests with the REST APIs" url="sp-add-ins/make-batch-requests-with-the-rest-apis" SEODescription=""/>
-			</Item>
-			<Item text="Create UX components in SharePoint" url="sp-add-ins/create-ux-components-in-sharepoint" SEODescription="">
-				<Item text="Use a SharePoint website's style sheet in add-ins" url="sp-add-ins/use-a-sharepoint-website-s-style-sheet-in-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Use the client chrome control in add-ins" url="sp-add-ins/use-the-client-chrome-control-in-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Create add-in parts to install with your SharePoint Add-in" url="sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in" SEODescription=""/>
-				<Item text="Create custom actions to deploy with SharePoint Add-ins" url="sp-add-ins/create-custom-actions-to-deploy-with-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Customize a list view in SharePoint Add-ins using client-side rendering" url="sp-add-ins/customize-a-list-view-in-sharepoint-add-ins-using-client-side-rendering" SEODescription=""/>
-				<Item text="Use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins" url="sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in" SEODescription=""/>
-				<Item text="Highlight content and enhance the functionality of SharePoint-hosted SharePoint Add-ins with the callout control" url="sp-add-ins/highlight-content-and-enhance-the-functionality-of-sharepoint-hosted-sharepoint" SEODescription=""/>
-				<Item text="Include a Web Part in a webpage on the add-in web" url="sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web" SEODescription=""/>
-				<Item text="Office Web Widgets - Experimental overview" url="sp-add-ins/office-web-widgetsexperimental-overview" SEODescription="">
-					<Item text="Use the experimental People Picker widget in SharePoint Add-ins" url="sp-add-ins/use-the-experimental-people-picker-widget-in-sharepoint-add-ins" SEODescription=""/>
-					<Item text="Use the experimental Desktop List View widget in SharePoint Add-ins" url="sp-add-ins/use-the-experimental-desktop-list-view-widget-in-sharepoint-add-ins" SEODescription=""/>
-					<Item text="Office Web Widgets - Experimental License Terms" url="sp-add-ins/office-web-widgetsexperimental-license-terms" SEODescription=""/>
-				</Item>
-			</Item>
-			<Item text="Work with external data in SharePoint" url="sp-add-ins/work-with-external-data-in-sharepoint" SEODescription="">
-				<Item text="Create a custom proxy page for the cross-domain library" url="sp-add-ins/create-a-custom-proxy-page-for-the-cross-domain-library-in-sharepoint" SEODescription=""/>
-				<Item text="Query a remote service using the web proxy" url="sp-add-ins/query-a-remote-service-using-the-web-proxy-in-sharepoint" SEODescription=""/>
-			</Item>
-			<Item text="Handle events in SharePoint Add-ins" url="sp-add-ins/handle-events-in-sharepoint-add-ins" SEODescription="">
-				<Item text="Create a remote event receiver" url="sp-add-ins/create-a-remote-event-receiver-in-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Create an add-in event receiver" url="sp-add-ins/create-an-add-in-event-receiver-in-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Debug and troubleshoot a remote event receiver" url="sp-add-ins/debug-and-troubleshoot-a-remote-event-receiver-in-a-sharepoint-add-in" SEODescription=""/>
-			</Item>
-			<Item text="Create a provider-hosted add-in that includes a custom SharePoint list and content type" url="sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte" SEODescription=""/>
-			<Item text="Get user identity and properties in SharePoint" url="sp-add-ins/get-user-identity-and-properties-in-sharepoint" SEODescription=""/>
-			<Item text="Localize SharePoint Add-ins" url="sp-add-ins/localize-sharepoint-add-ins" SEODescription=""/>
-			<Item text="Authorization and authentication of SharePoint Add-ins" url="sp-add-ins/authorization-and-authentication-of-sharepoint-add-ins" SEODescription="">
-				<Item text="Add-in permissions in SharePoint" url="sp-add-ins/add-in-permissions-in-sharepoint" SEODescription=""/>
-				<Item text="Register SharePoint Add-ins" url="sp-add-ins/register-sharepoint-add-ins" SEODescription=""/>
-				<Item text="Add-in authorization policy types in SharePoint" url="sp-add-ins/add-in-authorization-policy-types-in-sharepoint" SEODescription=""/>
-				<Item text="Three authorization systems for SharePoint Add-ins" url="sp-add-ins/three-authorization-systems-for-sharepoint-add-ins" SEODescription="">
-					<Item text="Creating SharePoint Add-ins that use low-trust authorization" url="sp-add-ins/creating-sharepoint-add-ins-that-use-low-trust-authorization" SEODescription="">
-						<Item text="Context Token OAuth flow for SharePoint Add-ins" url="sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Authorization Code OAuth flow for SharePoint Add-ins" url="sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Handle security tokens in provider-hosted low-trust SharePoint Add-ins" url="sp-add-ins/handle-security-tokens-in-provider-hosted-low-trust-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Use an Office 365 SharePoint site to authorize provider-hosted add-ins on an on-premises SharePoint site" url="sp-add-ins/use-an-office-365-sharepoint-site-to-authorize-provider-hosted-add-ins-on-an-on" SEODescription=""/>
-						<Item text="Replace an expiring client secret in a SharePoint Add-in" url="sp-add-ins/replace-an-expiring-client-secret-in-a-sharepoint-add-in" SEODescription=""/>
-					</Item>
-					<Item text="Creating SharePoint Add-ins that use high-trust authorization" url="sp-add-ins/creating-sharepoint-add-ins-that-use-high-trust-authorization" SEODescription="">
-						<Item text="Create high-trust add-ins" url="sp-add-ins/create-high-trust-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Create and use access tokens in provider-hosted high-trust SharePoint Add-ins" url="sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Troubleshooting high-trust SharePoint Add-ins" url="sp-add-ins/troubleshooting-high-trust-sharepoint-add-ins" SEODescription=""/>
-						<Item text="Package and publish high-trust SharePoint Add-ins" url="sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins" SEODescription="">
-							<Item text="High-trust configuration scripts for SharePoint" url="sp-add-ins/high-trust-configuration-scripts-for-sharepoint" SEODescription=""/>
-						</Item>
-					</Item>
-					<Item text="Creating SharePoint Add-ins that use the cross-domain library" url="sp-add-ins/creating-sharepoint-add-ins-that-use-the-cross-domain-library" SEODescription="">
-						<Item text="Access SharePoint data from add-ins using the cross-domain library" url="sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-domain-library" SEODescription=""/>
-						<Item text="Work with the cross-domain library across different Internet Explorer security zones in SharePoint Add-ins" url="sp-add-ins/work-with-the-cross-domain-library-across-different-internet-explorer-security-z" SEODescription=""/>
-					</Item>
-				</Item>
-			</Item>
-			<Item text="Create SharePoint Add-ins that can be used by anonymous users" url="sp-add-ins/create-sharepoint-add-ins-that-can-be-used-by-anonymous-users" SEODescription=""/>
-			<Item text="Convert an autohosted SharePoint Add-in to a provider-hosted add-in" url="sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in" SEODescription=""/>
-			<Item text="Create SharePoint Add-ins for the SAP Gateway for Microsoft" url="sp-add-ins/create-provider-hosted-sharepoint-add-ins-to-access-sap-data-by-using-the-sap-ga" SEODescription=""/>
-			<Item text="Create a SharePoint Add-in that contains a document template and a task pane add-in" url="sp-add-ins/create-a-sharepoint-add-in-that-contains-a-document-template-and-a-task-pane-add" SEODescription=""/>
-		</Item>
-		<Item text="Publish" url="sp-add-ins/publish-sharepoint-add-ins" SEODescription="">
-			<Item text="Deploying and installing SharePoint Add-ins: methods and options" url="sp-add-ins/deploying-and-installing-sharepoint-add-ins-methods-and-options" SEODescription=""/>
-			<Item text="Tenancies and deployment scopes for SharePoint Add-ins" url="sp-add-ins/tenancies-and-deployment-scopes-for-sharepoint-add-ins" SEODescription=""/>
-			<Item text="SharePoint Add-ins update process" url="sp-add-ins/sharepoint-add-ins-update-process" SEODescription="">
-				<Item text="Update SharePoint Add-ins" url="sp-add-ins/update-sharepoint-add-ins" SEODescription="">
-					<Item text="Update add-in web components in SharePoint" url="sp-add-ins/update-add-in-web-components-in-sharepoint" SEODescription=""/>
-					<Item text="Update host web components in SharePoint" url="sp-add-ins/update-host-web-components-in-sharepoint" SEODescription=""/>
-					<Item text="Update remote components in SharePoint Add-ins" url="sp-add-ins/update-remote-components-in-sharepoint-add-ins" SEODescription=""/>
-					<Item text="Create a handler for the update event in SharePoint Add-ins" url="sp-add-ins/create-a-handler-for-the-update-event-in-sharepoint-add-ins" SEODescription=""/>
-				</Item>
-			</Item>
-			<Item text="Publish SharePoint Add-ins by using Visual Studio" url="sp-add-ins/publish-sharepoint-add-ins-by-using-visual-studio" SEODescription=""/>
-		</Item>
-		<Item text="Tools" url="sp-add-ins/tools-and-environments-for-developing-sharepoint-add-ins" SEODescription="">
-			<Item text="Set up a development environment for SharePoint Add-ins on Office 365" url="sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365" SEODescription=""/>
-			<Item text="Create a developer site on an existing Office 365 subscription" url="sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription" SEODescription=""/>
-			<Item text="Set up an on-premises development environment for add-ins" url="sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins" SEODescription=""/>
-			<Item text="Create SharePoint Add-ins in Visual Studio" url="sp-add-ins/create-sharepoint-add-ins-in-visual-studio" SEODescription=""/>
-			<Item text="What's new in Office Developer Tools for Visual Studio 2013" url="sp-add-ins/what-s-new-in-office-developer-tools-for-visual-studio-2013" SEODescription=""/>
-		</Item>
-		<Item text="Create cloud business add-ins" url="sp-add-ins/create-cloud-business-add-ins" SEODescription="">
-			<Item text="Start" url="sp-add-ins/get-started-developing-cloud-business-add-ins" SEODescription="">
-				<Item text="Incident manager: A cloud business add-in tutorial" url="sp-add-ins/incident-manager-a-cloud-business-add-in-tutorial" SEODescription=""/>
-				<Item text="Create a cloud business add-in with a social newsfeed" url="sp-add-ins/create-a-cloud-business-add-in-with-a-social-newsfeed" SEODescription=""/>
-			</Item>
-			<Item text="Develop" url="sp-add-ins/develop-cloud-business-add-ins" SEODescription="">
-				<Item text="Create a cloud business add-in" url="sp-add-ins/create-a-cloud-business-add-in" SEODescription=""/>
-				<Item text="Associate a document library with an entity" url="sp-add-ins/associate-a-document-library-with-an-entity" SEODescription="">
-					<Item text="Troubleshooting document libraries" url="sp-add-ins/troubleshooting-document-libraries" SEODescription=""/>
-				</Item>
-				<Item text="Enable a newsfeed for a cloud business add-in" url="sp-add-ins/enable-a-newsfeed-for-a-cloud-business-add-in" SEODescription=""/>
-				<Item text="Provide a template for a document library in a cloud business add-in" url="sp-add-ins/provide-a-template-for-a-document-library-in-a-cloud-business-add-in" SEODescription=""/>
-				<Item text="Create a cloud business add-in that uses the SAP Gateway" url="sp-add-ins/create-a-cloud-business-add-in-that-uses-the-sap-gateway" SEODescription=""/>
-			</Item>
-			<Item text="Publish" url="sp-add-ins/publish-cloud-business-add-ins" SEODescription="">
-				<Item text="Publish a cloud business add-in to SharePoint" url="sp-add-ins/publish-a-cloud-business-add-in-to-sharepoint" SEODescription=""/>
-			</Item>
-		</Item>
-	</Item>
-</Menu>
diff --git a/misc/SharePointReferenceToc.xml b/misc/SharePointReferenceToc.xml
deleted file mode 100644
index b565e808b3..0000000000
--- a/misc/SharePointReferenceToc.xml
+++ /dev/null
@@ -1,225 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<Menu xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" SupportedProduct="|SharePoint" SupportedVersion="|V1.0|">
-	<Item text="SharePoint Framework Reference" url="spfx" SEODescription="Reference documentation for the SharePoint Framework">
-		<Item text="Overview" url="spfx/sharepoint-framework-reference-overview" SEODescription="Reference documentation for the SharePoint Framework"/>
-		<Item text="sp-application-base" url="spfx/sp-application-base-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-application-base/class" SEODescription="">
-				<Item text="ApplicationCustomizerContext" url="spfx/sp-application-base/class/applicationcustomizercontext" SEODescription=""/>
-				<Item text="BaseApplicationCustomizer" url="spfx/sp-application-base/class/baseapplicationcustomizer" SEODescription=""/>
-				<Item text="Placeholder" url="spfx/sp-application-base/class/placeholder" SEODescription=""/>
-				<Item text="PlaceholderCollection" url="spfx/sp-application-base/class/placeholdercollection" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-application-base" SEODescription="">
-				<Item text="IPlaceholderAttachOptions" url="spfx/sp-application-base/interface/iplaceholderattachoptions" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-component-base" url="spfx/sp-component-base-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-component-base" SEODescription="">
-				<Item text="BaseComponent" url="spfx/sp-component-base/class/basecomponent" SEODescription=""/>
-				<Item text="BaseComponentContext" url="spfx/sp-component-base/class/basecomponentcontext" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-component-base" SEODescription="">
-				<Item text="IClientSideComponentContext" url="spfx/sp-component-base/interface/iclientsidecomponentcontext" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-core-library" url="spfx/sp-core-library-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-core-library" SEODescription="">
-				<Item text="Environment" url="spfx/sp-core-library/class/environment" SEODescription=""/>
-				<Item text="Guid" url="spfx/sp-core-library/class/guid" SEODescription=""/>
-				<Item text="Log" url="spfx/sp-core-library/class/log" SEODescription=""/>
-				<Item text="RandomNumberGenerator" url="spfx/sp-core-library/class/randomnumbergenerator" SEODescription=""/>
-				<Item text="ServiceKey" url="spfx/sp-core-library/class/servicekey" SEODescription=""/>
-				<Item text="ServiceScope" url="spfx/sp-core-library/class/servicescope" SEODescription=""/>
-				<Item text="Session" url="spfx/sp-core-library/class/session" SEODescription=""/>
-				<Item text="Text" url="spfx/sp-core-library/class/text" SEODescription=""/>
-				<Item text="TimeProvider" url="spfx/sp-core-library/class/timeprovider" SEODescription=""/>
-				<Item text="UrlQueryParameterCollection" url="spfx/sp-core-library/class/urlqueryparametercollection" SEODescription=""/>
-				<Item text="Validate" url="spfx/sp-core-library/class/validate" SEODescription=""/>
-				<Item text="Version" url="spfx/sp-core-library/class/version" SEODescription=""/>
-			</Item>
-			<Item text="Enumerations" url="spfx/sp-core-library" SEODescription="">
-				<Item text="DisplayMode" url="spfx/sp-core-library/enum/displaymode" SEODescription=""/>
-				<Item text="EnvironmentType" url="spfx/sp-core-library/enum/environmenttype" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-core-library" SEODescription="">
-				<Item text="IRandomNumberGenerator" url="spfx/sp-core-library/interface/irandomnumbergenerator" SEODescription=""/>
-				<Item text="IServiceCollection" url="spfx/sp-core-library/interface/iservicecollection" SEODescription=""/>
-				<Item text="ITimeProvider" url="spfx/sp-core-library/interface/itimeprovider" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-dialog" url="spfx/sp-dialog-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-dialog" SEODescription="">
-				<Item text="BaseDialog" url="spfx/sp-dialog/class/basedialog" SEODescription=""/>
-				<Item text="Dialog" url="spfx/sp-dialog/class/dialog" SEODescription=""/>
-				<Item text="SecondaryDialog" url="spfx/sp-dialog/class/secondarydialog" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-dialog" SEODescription="">
-				<Item text="IAlertOptions" url="spfx/sp-dialog/interface/ialertoptions" SEODescription=""/>
-				<Item text="IDialogConfiguration" url="spfx/sp-dialog/interface/idialogconfiguration" SEODescription=""/>
-				<Item text="IDialogShowingOptions" url="spfx/sp-dialog/interface/idialogshowingoptions" SEODescription=""/>
-				<Item text="IPromptOptions" url="spfx/sp-dialog/interface/ipromptoptions" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-extension-base" url="spfx/sp-extension-base-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-extension-base" SEODescription="">
-				<Item text="BaseExtension" url="spfx/sp-extension-base/class/baseextension" SEODescription=""/>
-				<Item text="ExtensionContext" url="spfx/sp-extension-base/class/extensioncontext" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-http" url="spfx/sp-http-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-http" SEODescription="">
-				<Item text="GraphClientResponse" url="spfx/sp-http/class/graphclientresponse" SEODescription=""/>
-				<Item text="GraphHttpClient" url="spfx/sp-http/class/graphhttpclient" SEODescription=""/>
-				<Item text="GraphHttpClientConfiguration" url="spfx/sp-http/class/graphhttpclientconfiguration" SEODescription=""/>
-				<Item text="HttpClient" url="spfx/sp-http/class/httpclient" SEODescription=""/>
-				<Item text="HttpClientConfiguration" url="spfx/sp-http/class/httpclientconfiguration" SEODescription=""/>
-				<Item text="HttpClientResponse" url="spfx/sp-http/class/httpclientresponse" SEODescription=""/>
-				<Item text="ODataVersion" url="spfx/sp-http/class/odataversion" SEODescription=""/>
-				<Item text="SPHttpClient" url="spfx/sp-http/class/sphttpclient" SEODescription=""/>
-				<Item text="SPHttpClientCommonConfiguration" url="spfx/sp-http/class/sphttpclientcommonconfiguration" SEODescription=""/>
-				<Item text="SPHttpClientConfiguration" url="spfx/sp-http/class/sphttpclientconfiguration" SEODescription=""/>
-				<Item text="SPHttpClientResponse" url="spfx/sp-http/class/sphttpclientresponse" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-http" SEODescription="">
-				<Item text="IGraphHttpClientConfiguration" url="spfx/sp-http/interface/igraphhttpclientconfiguration" SEODescription=""/>
-				<Item text="IGraphHttpClientConfigurations" url="spfx/sp-http/interface/igraphhttpclientconfigurations" SEODescription=""/>
-				<Item text="IGraphHttpClientOptions" url="spfx/sp-http/interface/igraphhttpclientoptions" SEODescription=""/>
-				<Item text="IHttpClientConfiguration" url="spfx/sp-http/interface/ihttpclientconfiguration" SEODescription=""/>
-				<Item text="IHttpClientConfigurations" url="spfx/sp-http/interface/ihttpclientconfigurations" SEODescription=""/>
-				<Item text="IHttpClientOptions" url="spfx/sp-http/interface/ihttpclientoptions" SEODescription=""/>
-				<Item text="ISPHttpClientCommonConfiguration" url="spfx/sp-http/interface/isphttpclientcommonconfiguration" SEODescription=""/>
-				<Item text="ISPHttpClientConfiguration" url="spfx/sp-http/interface/isphttpclientconfiguration" SEODescription=""/>
-				<Item text="ISPHttpClientConfigurations" url="spfx/sp-http/interface/isphttpclientconfigurations" SEODescription=""/>
-				<Item text="ISPHttpClientOptions" url="spfx/sp-http/interface/isphttpclientoptions" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-listview-extensibility" url="spfx/sp-listview-extensibility-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-listview-extensibility" SEODescription="">
-				<Item text="BaseFieldCustomizer" url="spfx/sp-listview-extensibility/class/basefieldcustomizer" SEODescription=""/>
-				<Item text="BaseListViewCommandSet" url="spfx/sp-listview-extensibility/class/baselistviewcommandset" SEODescription=""/>
-				<Item text="CellFormatter" url="spfx/sp-listview-extensibility/class/cellformatter" SEODescription=""/>
-				<Item text="ColumnAccessor" url="spfx/sp-listview-extensibility/class/columnaccessor" SEODescription=""/>
-				<Item text="FieldCustomizerContext" url="spfx/sp-listview-extensibility/class/fieldcustomizercontext" SEODescription=""/>
-				<Item text="ListViewAccessor" url="spfx/sp-listview-extensibility/class/listviewaccessor" SEODescription=""/>
-				<Item text="ListViewCommandSetContext" url="spfx/sp-listview-extensibility/class/listviewcommandsetcontext" SEODescription=""/>
-				<Item text="RowAccessor" url="spfx/sp-listview-extensibility/class/rowaccessor" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-listview-extensibility" SEODescription="">
-				<Item text="IFieldCustomizerCellEventParameters" url="spfx/sp-listview-extensibility/interface/ifieldcustomizercelleventparameters" SEODescription=""/>
-				<Item text="IListViewCommandSetExecuteEventParameters" url="spfx/sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters" SEODescription=""/>
-				<Item text="IListViewCommandSetRefreshEventParameters" url="spfx/sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-odata-types" url="spfx/sp-odata-types-module" SEODescription="">
-			<Item text="Interfaces" url="spfx/sp-odata-types" SEODescription="">
-				<Item text="IODataBasePermission" url="spfx/sp-odata-types/interface/iodatabasepermission" SEODescription=""/>
-				<Item text="IODataChangeToken" url="spfx/sp-odata-types/interface/iodatachangetoken" SEODescription=""/>
-				<Item text="IODataContextWebInformation" url="spfx/sp-odata-types/interface/iodatacontextwebinformation" SEODescription=""/>
-				<Item text="IODataList" url="spfx/sp-odata-types/interface/iodatalist" SEODescription=""/>
-				<Item text="IODataListItem" url="spfx/sp-odata-types/interface/iodatalistitem" SEODescription=""/>
-				<Item text="IODataNavigationNode" url="spfx/sp-odata-types/interface/iodatanavigationnode" SEODescription=""/>
-				<Item text="IODataNavigationNodeCollection" url="spfx/sp-odata-types/interface/iodatanavigationnodecollection" SEODescription=""/>
-				<Item text="IODataUser" url="spfx/sp-odata-types/interface/iodatauser" SEODescription=""/>
-				<Item text="IODataUserCustomAction" url="spfx/sp-odata-types/interface/iodatausercustomaction" SEODescription=""/>
-				<Item text="IODataWeb" url="spfx/sp-odata-types/interface/iodataweb" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-page-context" url="spfx/sp-page-context-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-page-context" SEODescription="">
-				<Item text="CultureInfo" url="spfx/sp-page-context/class/cultureinfo" SEODescription=""/>
-				<Item text="PageContext" url="spfx/sp-page-context/class/pagecontext" SEODescription=""/>
-				<Item text="SPField" url="spfx/sp-page-context/class/spfield" SEODescription=""/>
-				<Item text="SPList" url="spfx/sp-page-context/class/splist" SEODescription=""/>
-				<Item text="SPListItem" url="spfx/sp-page-context/class/splistitem" SEODescription=""/>
-				<Item text="SPPermission" url="spfx/sp-page-context/class/sppermission" SEODescription=""/>
-				<Item text="SPSite" url="spfx/sp-page-context/class/spsite" SEODescription=""/>
-				<Item text="SPUser" url="spfx/sp-page-context/class/spuser" SEODescription=""/>
-				<Item text="SPWeb" url="spfx/sp-page-context/class/spweb" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="sp-webpart-base" url="spfx/sp-webpart-base-module" SEODescription="">
-			<Item text="Classes" url="spfx/sp-webpart-base" SEODescription="">
-				<Item text="BaseClientSideWebPart" url="spfx/sp-webpart-base/class/baseclientsidewebpart" SEODescription=""/>
-			</Item>
-			<Item text="Enumerations" url="spfx/sp-webpart-base" SEODescription="">
-				<Item text="PropertyPaneButtonType" url="spfx/sp-webpart-base/enum/propertypanebuttontype" SEODescription=""/>
-				<Item text="PropertyPaneFieldType" url="spfx/sp-webpart-base/enum/propertypanefieldtype" SEODescription=""/>
-			</Item>
-			<Item text="Functions" url="spfx/sp-webpart-base" SEODescription="">
-				<Item text="PropertyPaneButton" url="spfx/sp-webpart-base/function/propertypanebutton" SEODescription=""/>
-				<Item text="PropertyPaneCheckbox" url="spfx/sp-webpart-base/function/propertypanecheckbox" SEODescription=""/>
-				<Item text="PropertyPaneChoiceGroup" url="spfx/sp-webpart-base/function/propertypanechoicegroup" SEODescription=""/>
-				<Item text="PropertyPaneCustomField" url="spfx/sp-webpart-base/function/propertypanecustomfield" SEODescription=""/>
-				<Item text="PropertyPaneDropdown" url="spfx/sp-webpart-base/function/propertypanedropdown" SEODescription=""/>
-				<Item text="PropertyPaneHorizontalRule" url="spfx/sp-webpart-base/function/propertypanehorizontalrule" SEODescription=""/>
-				<Item text="PropertyPaneLabel" url="spfx/sp-webpart-base/function/propertypanelabel" SEODescription=""/>
-				<Item text="PropertyPaneLink" url="spfx/sp-webpart-base/function/propertypanelink" SEODescription=""/>
-				<Item text="PropertyPaneSlider" url="spfx/sp-webpart-base/function/propertypaneslider" SEODescription=""/>
-				<Item text="PropertyPaneTextField" url="spfx/sp-webpart-base/function/propertypanetextfield" SEODescription=""/>
-				<Item text="PropertyPaneToggle" url="spfx/sp-webpart-base/function/propertypanetoggle" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/sp-webpart-base" SEODescription="">
-				<Item text="IClientSideWebPartStatusRenderer" url="spfx/sp-webpart-base/interface/iclientsidewebpartstatusrenderer" SEODescription=""/>
-				<Item text="IPlaceholderSpinnerProps" url="spfx/sp-webpart-base/interface/iplaceholderspinnerprops" SEODescription=""/>
-				<Item text="IPropertyPaneAccessor" url="spfx/sp-webpart-base/interface/ipropertypaneaccessor" SEODescription=""/>
-				<Item text="IPropertyPaneButtonProps" url="spfx/sp-webpart-base/interface/ipropertypanebuttonprops" SEODescription=""/>
-				<Item text="IPropertyPaneCheckboxProps" url="spfx/sp-webpart-base/interface/ipropertypanecheckboxprops" SEODescription=""/>
-				<Item text="IPropertyPaneChoiceGroupOption" url="spfx/sp-webpart-base/interface/ipropertypanechoicegroupoption" SEODescription=""/>
-				<Item text="IPropertyPaneChoiceGroupOptionIconProps" url="spfx/sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops" SEODescription=""/>
-				<Item text="IPropertyPaneChoiceGroupProps" url="spfx/sp-webpart-base/interface/ipropertypanechoicegroupprops" SEODescription=""/>
-				<Item text="IPropertyPaneConfiguration" url="spfx/sp-webpart-base/interface/ipropertypaneconfiguration" SEODescription=""/>
-				<Item text="IPropertyPaneCustomFieldProps" url="spfx/sp-webpart-base/interface/ipropertypanecustomfieldprops" SEODescription=""/>
-				<Item text="IPropertyPaneDropdownOption" url="spfx/sp-webpart-base/interface/ipropertypanedropdownoption" SEODescription=""/>
-				<Item text="IPropertyPaneDropdownProps" url="spfx/sp-webpart-base/interface/ipropertypanedropdownprops" SEODescription=""/>
-				<Item text="IPropertyPaneField" url="spfx/sp-webpart-base/interface/ipropertypanefield" SEODescription=""/>
-				<Item text="IPropertyPaneGroup" url="spfx/sp-webpart-base/interface/ipropertypanegroup" SEODescription=""/>
-				<Item text="IPropertyPaneLabelProps" url="spfx/sp-webpart-base/interface/ipropertypanelabelprops" SEODescription=""/>
-				<Item text="IPropertyPaneLinkProps" url="spfx/sp-webpart-base/interface/ipropertypanelinkprops" SEODescription=""/>
-				<Item text="IPropertyPanePage" url="spfx/sp-webpart-base/interface/ipropertypanepage" SEODescription=""/>
-				<Item text="IPropertyPanePageHeader" url="spfx/sp-webpart-base/interface/ipropertypanepageheader" SEODescription=""/>
-				<Item text="IPropertyPaneSliderProps" url="spfx/sp-webpart-base/interface/ipropertypanesliderprops" SEODescription=""/>
-				<Item text="IPropertyPaneTextFieldProps" url="spfx/sp-webpart-base/interface/ipropertypanetextfieldprops" SEODescription=""/>
-				<Item text="IPropertyPaneToggleProps" url="spfx/sp-webpart-base/interface/ipropertypanetoggleprops" SEODescription=""/>
-				<Item text="ISerializedServerProcessedData" url="spfx/sp-webpart-base/interface/iserializedserverprocesseddata" SEODescription=""/>
-				<Item text="ISerializedWebPartData" url="spfx/sp-webpart-base/interface/iserializedwebpartdata" SEODescription=""/>
-				<Item text="IWebPartContext" url="spfx/sp-webpart-base/interface/iwebpartcontext" SEODescription=""/>
-				<Item text="IWebPartData" url="spfx/sp-webpart-base/interface/iwebpartdata" SEODescription=""/>
-				<Item text="IWebPartPropertiesMetadata" url="spfx/sp-webpart-base/interface/iwebpartpropertiesmetadata" SEODescription=""/>
-			</Item>
-		</Item>
-	</Item>
-	<Item text="horizontalline" url="/" IsSeparation="true" SEODescription=""/>
-	<Item text="External packages" url="spfx" SEODescription="" >
-		<Item text="web-apis" url="spfx/web-apis-module" SEODescription="">
-			<Item text="Classes" url="spfx/web-apis" SEODescription="">
-				<Item text="Body" url="spfx/web-apis/class/body" SEODescription=""/>
-				<Item text="Headers" url="spfx/web-apis/class/headers" SEODescription=""/>
-				<Item text="Promise" url="spfx/web-apis/class/promise" SEODescription=""/>
-				<Item text="Request" url="spfx/web-apis/class/request" SEODescription=""/>
-				<Item text="Response" url="spfx/web-apis/class/response" SEODescription=""/>
-			</Item>
-			<Item text="Interfaces" url="spfx/web-apis" SEODescription="">
-				<Item text="HeadersMap" url="spfx/web-apis/interface/headersmap" SEODescription=""/>
-				<Item text="RequestInit" url="spfx/web-apis/interface/requestinit" SEODescription=""/>
-				<Item text="ResponseInit" url="spfx/web-apis/interface/responseinit" SEODescription=""/>
-				<Item text="Thenable" url="spfx/web-apis/interface/thenable" SEODescription=""/>
-				<Item text="Window" url="spfx/web-apis/interface/window" SEODescription=""/>
-			</Item>
-		</Item>
-		<Item text="es6-collections" url="spfx/es6-collections-module" SEODescription="">
-			<Item text="Interfaces" url="spfx/es6-collections" SEODescription="">
-				<Item text="ForEachable" url="spfx/es6-collections/interface/foreachable" SEODescription=""/>
-				<Item text="Iterator" url="spfx/es6-collections/interface/iterator" SEODescription=""/>
-				<Item text="IteratorResult" url="spfx/es6-collections/interface/iteratorresult" SEODescription=""/>
-				<Item text="Map" url="spfx/es6-collections/interface/map" SEODescription=""/>
-				<Item text="MapConstructor" url="spfx/es6-collections/interface/mapconstructor" SEODescription=""/>
-				<Item text="Set" url="spfx/es6-collections/interface/set" SEODescription=""/>
-				<Item text="SetConstructor" url="spfx/es6-collections/interface/setconstructor" SEODescription=""/>
-				<Item text="WeakMap" url="spfx/es6-collections/interface/weakmap" SEODescription=""/>
-				<Item text="WeakMapConstructor" url="spfx/es6-collections/interface/weakmapconstructor" SEODescription=""/>
-				<Item text="WeakSet" url="spfx/es6-collections/interface/weakset" SEODescription=""/>
-				<Item text="WeakSetConstructor" url="spfx/es6-collections/interface/weaksetconstructor" SEODescription=""/>
-			</Item>
-		</Item>
-	</Item>
-</Menu>
\ No newline at end of file
diff --git a/misc/SharepointBreadcrumbs.json b/misc/SharepointBreadcrumbs.json
deleted file mode 100644
index 4aca25ee33..0000000000
--- a/misc/SharepointBreadcrumbs.json
+++ /dev/null
@@ -1,41 +0,0 @@
-{
-  "Cat": "SharePoint",
-  "parentLink": "/sharepoint",
-  "DropdownOptions": [
-    {
-      "Title": "SharePoint Framework",
-      "URL": "/sharepoint/docs/spfx/sharepoint-framework-overview",
-      "Index": "/sharepoint/docs/spfx"
-    },
-    {
-      "Title": "SharePoint Framework Reference",
-      "URL": "https://dev.office.com/sharepoint/reference/spfx/sharepoint-framework-reference-overview",
-      "Index": "external"
-    },
-    {
-      "Title": "SharePoint Framework Code Samples",
-      "URL": "http://aka.ms/spfx-samples",
-      "Index": "external"
-    },      
-    {
-      "Title": "SharePoint General Development",
-      "URL": "/sharepoint/docs/general-development/sharepoint-development-overview",
-      "Index": "/sharepoint/docs/general-development"
-    },
-    {
-      "Title": "SharePoint Add-ins",
-      "URL": "/sharepoint/docs/sp-add-ins/sharepoint-add-ins",
-      "Index": "/sharepoint/docs/sp-add-ins"
-    },
-    {
-      "Title": "SharePoint REST APIs",
-      "URL": "https://msdn.microsoft.com/en-us/library/office/jj860569.aspx",
-      "Index": "external"
-    },
-    {
-      "Title": "Patterns and Practices",
-      "URL": "https://msdn.microsoft.com/en-us/pnp_articles/office-365-development-patterns-and-practices-solution-guidance",
-      "Index": "external"
-    }
-  ]
-}
diff --git a/reference/spfx/es6-collections-module.md b/reference/spfx/es6-collections-module.md
deleted file mode 100644
index fe0e247474..0000000000
--- a/reference/spfx/es6-collections-module.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# es6-collections package
-
-
-
-
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`ForEachable`](./es6-collections/interface/foreachable.md)   |   |
-| [`Iterator`](./es6-collections/interface/iterator.md)   |   |
-| [`IteratorResult`](./es6-collections/interface/iteratorresult.md)   |   |
-| [`Map`](./es6-collections/interface/map.md)   |   |
-| [`MapConstructor`](./es6-collections/interface/mapconstructor.md)   |   |
-| [`Set`](./es6-collections/interface/set.md)   |   |
-| [`SetConstructor`](./es6-collections/interface/setconstructor.md)   |   |
-| [`WeakMap`](./es6-collections/interface/weakmap.md)   |   |
-| [`WeakMapConstructor`](./es6-collections/interface/weakmapconstructor.md)   |   |
-| [`WeakSet`](./es6-collections/interface/weakset.md)   |   |
-| [`WeakSetConstructor`](./es6-collections/interface/weaksetconstructor.md)   |   |
-
-
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/__new-mapconstructor.md b/reference/spfx/es6-collections/interface/__new-mapconstructor.md
deleted file mode 100644
index 6c0c77b24d..0000000000
--- a/reference/spfx/es6-collections/interface/__new-mapconstructor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# new()
-
-
-
-
-
-**Signature:** _new < K, V >(): [Map](../../es6-collections/interface/map.md)<K, V>;_
-
-**Returns**: [`Map`](../../es6-collections/interface/map.md)<K, V>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/__new-setconstructor.md b/reference/spfx/es6-collections/interface/__new-setconstructor.md
deleted file mode 100644
index 642451bd6c..0000000000
--- a/reference/spfx/es6-collections/interface/__new-setconstructor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# new()
-
-
-
-
-
-**Signature:** _new < T >(): [Set](../../es6-collections/interface/set.md)<T>;_
-
-**Returns**: [`Set`](../../es6-collections/interface/set.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/__new-weakmapconstructor.md b/reference/spfx/es6-collections/interface/__new-weakmapconstructor.md
deleted file mode 100644
index 228a48a985..0000000000
--- a/reference/spfx/es6-collections/interface/__new-weakmapconstructor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# new()
-
-
-
-
-
-**Signature:** _new < K, V >(): [WeakMap](../../es6-collections/interface/weakmap.md)<K, V>;_
-
-**Returns**: [`WeakMap`](../../es6-collections/interface/weakmap.md)<K, V>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/__new-weaksetconstructor.md b/reference/spfx/es6-collections/interface/__new-weaksetconstructor.md
deleted file mode 100644
index c3a29cbc06..0000000000
--- a/reference/spfx/es6-collections/interface/__new-weaksetconstructor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# new()
-
-
-
-
-
-**Signature:** _new < T >(): [WeakSet](../../es6-collections/interface/weakset.md)<T>;_
-
-**Returns**: [`WeakSet`](../../es6-collections/interface/weakset.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/add-set.md b/reference/spfx/es6-collections/interface/add-set.md
deleted file mode 100644
index f40686acb2..0000000000
--- a/reference/spfx/es6-collections/interface/add-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# add()
-
-
-
-
-
-**Signature:** _add(value: T): [Set](../../es6-collections/interface/set.md)<T>;_
-
-**Returns**: [`Set`](../../es6-collections/interface/set.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/add-weakset.md b/reference/spfx/es6-collections/interface/add-weakset.md
deleted file mode 100644
index 7529e50406..0000000000
--- a/reference/spfx/es6-collections/interface/add-weakset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# add()
-
-
-
-
-
-**Signature:** _add(value: T): [WeakSet](../../es6-collections/interface/weakset.md)<T>;_
-
-**Returns**: [`WeakSet`](../../es6-collections/interface/weakset.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/clear-map.md b/reference/spfx/es6-collections/interface/clear-map.md
deleted file mode 100644
index 19c4c4a857..0000000000
--- a/reference/spfx/es6-collections/interface/clear-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clear()
-
-
-
-
-
-**Signature:** _clear(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/clear-set.md b/reference/spfx/es6-collections/interface/clear-set.md
deleted file mode 100644
index 19c4c4a857..0000000000
--- a/reference/spfx/es6-collections/interface/clear-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clear()
-
-
-
-
-
-**Signature:** _clear(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/clear-weakmap.md b/reference/spfx/es6-collections/interface/clear-weakmap.md
deleted file mode 100644
index 19c4c4a857..0000000000
--- a/reference/spfx/es6-collections/interface/clear-weakmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clear()
-
-
-
-
-
-**Signature:** _clear(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/clear-weakset.md b/reference/spfx/es6-collections/interface/clear-weakset.md
deleted file mode 100644
index 19c4c4a857..0000000000
--- a/reference/spfx/es6-collections/interface/clear-weakset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clear()
-
-
-
-
-
-**Signature:** _clear(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/delete-map.md b/reference/spfx/es6-collections/interface/delete-map.md
deleted file mode 100644
index 372fff2ff4..0000000000
--- a/reference/spfx/es6-collections/interface/delete-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# delete()
-
-
-
-
-
-**Signature:** _delete(key: K): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/delete-set.md b/reference/spfx/es6-collections/interface/delete-set.md
deleted file mode 100644
index e3c11443c4..0000000000
--- a/reference/spfx/es6-collections/interface/delete-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# delete()
-
-
-
-
-
-**Signature:** _delete(value: T): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/delete-weakmap.md b/reference/spfx/es6-collections/interface/delete-weakmap.md
deleted file mode 100644
index 372fff2ff4..0000000000
--- a/reference/spfx/es6-collections/interface/delete-weakmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# delete()
-
-
-
-
-
-**Signature:** _delete(key: K): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/delete-weakset.md b/reference/spfx/es6-collections/interface/delete-weakset.md
deleted file mode 100644
index e3c11443c4..0000000000
--- a/reference/spfx/es6-collections/interface/delete-weakset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# delete()
-
-
-
-
-
-**Signature:** _delete(value: T): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/entries-map.md b/reference/spfx/es6-collections/interface/entries-map.md
deleted file mode 100644
index 8e1df1308c..0000000000
--- a/reference/spfx/es6-collections/interface/entries-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# entries()
-
-
-
-
-
-**Signature:** _entries(): [Iterator](../../es6-collections/interface/iterator.md)<[K, V]>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<[K, V]>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/entries-set.md b/reference/spfx/es6-collections/interface/entries-set.md
deleted file mode 100644
index a7830a6b09..0000000000
--- a/reference/spfx/es6-collections/interface/entries-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# entries()
-
-
-
-
-
-**Signature:** _entries(): [Iterator](../../es6-collections/interface/iterator.md)<[T, T]>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<[T, T]>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/foreach-foreachable.md b/reference/spfx/es6-collections/interface/foreach-foreachable.md
deleted file mode 100644
index d31a310bc6..0000000000
--- a/reference/spfx/es6-collections/interface/foreach-foreachable.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# forEach()
-
-
-
-
-
-**Signature:** _forEach(callbackfn: (value: T) => void): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/foreach-map.md b/reference/spfx/es6-collections/interface/foreach-map.md
deleted file mode 100644
index e857aff22e..0000000000
--- a/reference/spfx/es6-collections/interface/foreach-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# forEach()
-
-
-
-
-
-**Signature:** _forEach(callbackfn: (value: V, index: K, map: [Map](../../es6-collections/interface/map.md)<K, V>) => void, thisArg?: any): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/foreach-set.md b/reference/spfx/es6-collections/interface/foreach-set.md
deleted file mode 100644
index 8afdbd0150..0000000000
--- a/reference/spfx/es6-collections/interface/foreach-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# forEach()
-
-
-
-
-
-**Signature:** _forEach(callbackfn: (value: T, index: T, set: [Set](../../es6-collections/interface/set.md)<T>) => void, thisArg?: any): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/foreachable.md b/reference/spfx/es6-collections/interface/foreachable.md
deleted file mode 100644
index 39009dfe9d..0000000000
--- a/reference/spfx/es6-collections/interface/foreachable.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# ForEachable <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`forEach()`](foreach-foreachable.md)      | `void` |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/get-map.md b/reference/spfx/es6-collections/interface/get-map.md
deleted file mode 100644
index 21d4a79086..0000000000
--- a/reference/spfx/es6-collections/interface/get-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# get()
-
-
-
-
-
-**Signature:** _get(key: K): V;_
-
-**Returns**: `V`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/get-weakmap.md b/reference/spfx/es6-collections/interface/get-weakmap.md
deleted file mode 100644
index 21d4a79086..0000000000
--- a/reference/spfx/es6-collections/interface/get-weakmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# get()
-
-
-
-
-
-**Signature:** _get(key: K): V;_
-
-**Returns**: `V`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/has-map.md b/reference/spfx/es6-collections/interface/has-map.md
deleted file mode 100644
index f047fe9b35..0000000000
--- a/reference/spfx/es6-collections/interface/has-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# has()
-
-
-
-
-
-**Signature:** _has(key: K): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/has-set.md b/reference/spfx/es6-collections/interface/has-set.md
deleted file mode 100644
index b7c0715a4d..0000000000
--- a/reference/spfx/es6-collections/interface/has-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# has()
-
-
-
-
-
-**Signature:** _has(value: T): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/has-weakmap.md b/reference/spfx/es6-collections/interface/has-weakmap.md
deleted file mode 100644
index f047fe9b35..0000000000
--- a/reference/spfx/es6-collections/interface/has-weakmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# has()
-
-
-
-
-
-**Signature:** _has(key: K): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/has-weakset.md b/reference/spfx/es6-collections/interface/has-weakset.md
deleted file mode 100644
index b7c0715a4d..0000000000
--- a/reference/spfx/es6-collections/interface/has-weakset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# has()
-
-
-
-
-
-**Signature:** _has(value: T): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/iterator.md b/reference/spfx/es6-collections/interface/iterator.md
deleted file mode 100644
index b07b32819b..0000000000
--- a/reference/spfx/es6-collections/interface/iterator.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# Iterator <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`next()`](next-iterator.md)      | [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T> |  |
-|[`return()`](return-iterator.md)      | [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T> |  |
-|[`throw()`](throw-iterator.md)      | [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/iteratorresult.md b/reference/spfx/es6-collections/interface/iteratorresult.md
deleted file mode 100644
index 3deb612408..0000000000
--- a/reference/spfx/es6-collections/interface/iteratorresult.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IteratorResult <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`done`      | `boolean` |  |
-|`value`      | `T` |  |
-
-
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/keys-map.md b/reference/spfx/es6-collections/interface/keys-map.md
deleted file mode 100644
index f13699488d..0000000000
--- a/reference/spfx/es6-collections/interface/keys-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# keys()
-
-
-
-
-
-**Signature:** _keys(): [Iterator](../../es6-collections/interface/iterator.md)<K>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<K>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/keys-set.md b/reference/spfx/es6-collections/interface/keys-set.md
deleted file mode 100644
index edc49bd9a8..0000000000
--- a/reference/spfx/es6-collections/interface/keys-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# keys()
-
-
-
-
-
-**Signature:** _keys(): [Iterator](../../es6-collections/interface/iterator.md)<T>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/map.md b/reference/spfx/es6-collections/interface/map.md
deleted file mode 100644
index c39c872aaa..0000000000
--- a/reference/spfx/es6-collections/interface/map.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Map <K, V> interface
-
-
-
-_Type parameters: `<K, V>`_
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`size`      | `number` |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`clear()`](clear-map.md)      | `void` |  |
-|[`delete()`](delete-map.md)      | `boolean` |  |
-|[`entries()`](entries-map.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<[K, V]> |  |
-|[`forEach()`](foreach-map.md)      | `void` |  |
-|[`get()`](get-map.md)      | `V` |  |
-|[`has()`](has-map.md)      | `boolean` |  |
-|[`keys()`](keys-map.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<K> |  |
-|[`set()`](set-map.md)      | [`Map`](../../es6-collections/interface/map.md)<K, V> |  |
-|[`values()`](values-map.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<V> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/mapconstructor.md b/reference/spfx/es6-collections/interface/mapconstructor.md
deleted file mode 100644
index 3f6f19950e..0000000000
--- a/reference/spfx/es6-collections/interface/mapconstructor.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# MapConstructor interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`prototype`      | [`Map`](../../es6-collections/interface/map.md)<any, any> |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`new()`](__new-mapconstructor.md)      | [`Map`](../../es6-collections/interface/map.md)<K, V> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/next-iterator.md b/reference/spfx/es6-collections/interface/next-iterator.md
deleted file mode 100644
index b40a128efb..0000000000
--- a/reference/spfx/es6-collections/interface/next-iterator.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# next()
-
-
-
-
-
-**Signature:** _next(value?: any): [IteratorResult](../../es6-collections/interface/iteratorresult.md)<T>;_
-
-**Returns**: [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/return-iterator.md b/reference/spfx/es6-collections/interface/return-iterator.md
deleted file mode 100644
index d1065a5cb4..0000000000
--- a/reference/spfx/es6-collections/interface/return-iterator.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# return()
-
-
-
-
-
-**Signature:** _return ?(value?: any): [IteratorResult](../../es6-collections/interface/iteratorresult.md)<T>;_
-
-**Returns**: [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/set-map.md b/reference/spfx/es6-collections/interface/set-map.md
deleted file mode 100644
index 5bf8d99c35..0000000000
--- a/reference/spfx/es6-collections/interface/set-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# set()
-
-
-
-
-
-**Signature:** _set(key: K, value?: V): [Map](../../es6-collections/interface/map.md)<K, V>;_
-
-**Returns**: [`Map`](../../es6-collections/interface/map.md)<K, V>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/set-weakmap.md b/reference/spfx/es6-collections/interface/set-weakmap.md
deleted file mode 100644
index e443175355..0000000000
--- a/reference/spfx/es6-collections/interface/set-weakmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# set()
-
-
-
-
-
-**Signature:** _set(key: K, value?: V): [WeakMap](../../es6-collections/interface/weakmap.md)<K, V>;_
-
-**Returns**: [`WeakMap`](../../es6-collections/interface/weakmap.md)<K, V>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/set.md b/reference/spfx/es6-collections/interface/set.md
deleted file mode 100644
index 7712214f43..0000000000
--- a/reference/spfx/es6-collections/interface/set.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# Set <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`size`      | `number` |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`add()`](add-set.md)      | [`Set`](../../es6-collections/interface/set.md)<T> |  |
-|[`clear()`](clear-set.md)      | `void` |  |
-|[`delete()`](delete-set.md)      | `boolean` |  |
-|[`entries()`](entries-set.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<[T, T]> |  |
-|[`forEach()`](foreach-set.md)      | `void` |  |
-|[`has()`](has-set.md)      | `boolean` |  |
-|[`keys()`](keys-set.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<T> |  |
-|[`values()`](values-set.md)      | [`Iterator`](../../es6-collections/interface/iterator.md)<T> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/setconstructor.md b/reference/spfx/es6-collections/interface/setconstructor.md
deleted file mode 100644
index 95d91babf0..0000000000
--- a/reference/spfx/es6-collections/interface/setconstructor.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# SetConstructor interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`prototype`      | [`Set`](../../es6-collections/interface/set.md)<any> |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`new()`](__new-setconstructor.md)      | [`Set`](../../es6-collections/interface/set.md)<T> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/throw-iterator.md b/reference/spfx/es6-collections/interface/throw-iterator.md
deleted file mode 100644
index 05332b8856..0000000000
--- a/reference/spfx/es6-collections/interface/throw-iterator.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# throw()
-
-
-
-
-
-**Signature:** _throw ?(e?: any): [IteratorResult](../../es6-collections/interface/iteratorresult.md)<T>;_
-
-**Returns**: [`IteratorResult`](../../es6-collections/interface/iteratorresult.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/values-map.md b/reference/spfx/es6-collections/interface/values-map.md
deleted file mode 100644
index d0cd88e100..0000000000
--- a/reference/spfx/es6-collections/interface/values-map.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# values()
-
-
-
-
-
-**Signature:** _values(): [Iterator](../../es6-collections/interface/iterator.md)<V>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<V>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/values-set.md b/reference/spfx/es6-collections/interface/values-set.md
deleted file mode 100644
index d910367414..0000000000
--- a/reference/spfx/es6-collections/interface/values-set.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# values()
-
-
-
-
-
-**Signature:** _values(): [Iterator](../../es6-collections/interface/iterator.md)<T>;_
-
-**Returns**: [`Iterator`](../../es6-collections/interface/iterator.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/es6-collections/interface/weakmap.md b/reference/spfx/es6-collections/interface/weakmap.md
deleted file mode 100644
index 1042b09919..0000000000
--- a/reference/spfx/es6-collections/interface/weakmap.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# WeakMap <K, V> interface
-
-
-
-_Type parameters: `<K, V>`_
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`clear()`](clear-weakmap.md)      | `void` |  |
-|[`delete()`](delete-weakmap.md)      | `boolean` |  |
-|[`get()`](get-weakmap.md)      | `V` |  |
-|[`has()`](has-weakmap.md)      | `boolean` |  |
-|[`set()`](set-weakmap.md)      | [`WeakMap`](../../es6-collections/interface/weakmap.md)<K, V> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/weakmapconstructor.md b/reference/spfx/es6-collections/interface/weakmapconstructor.md
deleted file mode 100644
index 00a0f2246d..0000000000
--- a/reference/spfx/es6-collections/interface/weakmapconstructor.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# WeakMapConstructor interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`prototype`      | [`WeakMap`](../../es6-collections/interface/weakmap.md)<any, any> |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`new()`](__new-weakmapconstructor.md)      | [`WeakMap`](../../es6-collections/interface/weakmap.md)<K, V> |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/weakset.md b/reference/spfx/es6-collections/interface/weakset.md
deleted file mode 100644
index 0ef36eff19..0000000000
--- a/reference/spfx/es6-collections/interface/weakset.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# WeakSet <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`add()`](add-weakset.md)      | [`WeakSet`](../../es6-collections/interface/weakset.md)<T> |  |
-|[`clear()`](clear-weakset.md)      | `void` |  |
-|[`delete()`](delete-weakset.md)      | `boolean` |  |
-|[`has()`](has-weakset.md)      | `boolean` |  |
-
-
-
-
diff --git a/reference/spfx/es6-collections/interface/weaksetconstructor.md b/reference/spfx/es6-collections/interface/weaksetconstructor.md
deleted file mode 100644
index 9ca84e9595..0000000000
--- a/reference/spfx/es6-collections/interface/weaksetconstructor.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# WeakSetConstructor interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`prototype`      | [`WeakSet`](../../es6-collections/interface/weakset.md)<any> |  |
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`new()`](__new-weaksetconstructor.md)      | [`WeakSet`](../../es6-collections/interface/weakset.md)<T> |  |
-
-
-
-
diff --git a/reference/spfx/sharepoint-framework-reference-overview.md b/reference/spfx/sharepoint-framework-reference-overview.md
deleted file mode 100644
index 0060fc8c66..0000000000
--- a/reference/spfx/sharepoint-framework-reference-overview.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# SharePoint Framework Reference
-
-The SharePoint Framework object model is built in TypeScript. Use this section to learn more about the classes, methods, and other types available for building your SharePoint Framework solutions.
diff --git a/reference/spfx/sp-application-base-module.md b/reference/spfx/sp-application-base-module.md
deleted file mode 100644
index c2133c3123..0000000000
--- a/reference/spfx/sp-application-base-module.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# sp-application-base package
-
-
-
-
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`ApplicationCustomizerContext`](./sp-application-base/class/applicationcustomizercontext.md)     | This object provides contextual information for BaseApplicationCustomizer. |
-| [`BaseApplicationCustomizer`](./sp-application-base/class/baseapplicationcustomizer.md)     | This is the base class that third parties should extend when implementing a client-side extension that runs when an application is first starting. In the component manifest, the "extensionType" should be set to "ApplicationCustomizer". |
-| [`Placeholder`](./sp-application-base/class/placeholder.md)     | A content placeholder is a designated region on the page (i.e. empty HTML "div" element) where third party extensions can inject HTML content. |
-| [`PlaceholderCollection`](./sp-application-base/class/placeholdercollection.md)     | Exposes a collection of content placeholders for use by third parties. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IPlaceholderAttachOptions`](./sp-application-base/interface/iplaceholderattachoptions.md)   | Options for the PlaceholderCollection.tryAttach() method.  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-application-base/class/applicationcustomizercontext.md b/reference/spfx/sp-application-base/class/applicationcustomizercontext.md
deleted file mode 100644
index 7fbeaca40d..0000000000
--- a/reference/spfx/sp-application-base/class/applicationcustomizercontext.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# ApplicationCustomizerContext class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This object provides contextual information for BaseApplicationCustomizer.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`pageContext`     | `public` | [`PageContext`](../../sp-page-context/class/pagecontext.md) | _Read-only._ The page context provides standard definitions for common SharePoint objects that need to be shared between the client-side application, web parts, and other components. |
-|`placeholders`     | `public` | [`PlaceholderCollection`](../../sp-application-base/class/placeholdercollection.md) | _Read-only._ Exposes a collection of content placeholders for use by third parties. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-application-base/class/baseapplicationcustomizer.md b/reference/spfx/sp-application-base/class/baseapplicationcustomizer.md
deleted file mode 100644
index bcd20ca4aa..0000000000
--- a/reference/spfx/sp-application-base/class/baseapplicationcustomizer.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# BaseApplicationCustomizer <TProperties> class
-
-
-
-_Type parameters: `<TProperties>`_
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This is the base class that third parties should extend when implementing a client-side extension that runs when an application is first starting. In the component manifest, the "extensionType" should be set to "ApplicationCustomizer".
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`context`     | `public` | [`ApplicationCustomizerContext`](../../sp-application-base/class/applicationcustomizercontext.md) | Use context object to access common services and state associated with the component. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`onRender()`](onrender-baseapplicationcustomizer.md)     | `public` | `void` | This lifecycle event occurs after the shell has constructed the initial page DOM, after the application's onRender() event has occurred. |
-
-
-
-
-
diff --git a/reference/spfx/sp-application-base/class/dispose-placeholder.md b/reference/spfx/sp-application-base/class/dispose-placeholder.md
deleted file mode 100644
index e974900149..0000000000
--- a/reference/spfx/sp-application-base/class/dispose-placeholder.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# dispose()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Diposes the attached DOM tree.
-
-**Signature:** _public dispose(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
-### Remarks
-
-This method can be called to immediately dispose the attached DOM element. Otherwise, it will be disposed by the application when the placeholder is disposed. Calling dispose() invokes the IPlaceholderAttachOptions.onDispose() callback, removes the attached DOM element from the DOM, and assigns DOM element to undefined.
-
diff --git a/reference/spfx/sp-application-base/class/onrender-baseapplicationcustomizer.md b/reference/spfx/sp-application-base/class/onrender-baseapplicationcustomizer.md
deleted file mode 100644
index 923c4e0e33..0000000000
--- a/reference/spfx/sp-application-base/class/onrender-baseapplicationcustomizer.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onRender()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This lifecycle event occurs after the shell has constructed the initial page DOM, after the application's onRender() event has occurred.
-
-**Signature:** _@virtual public onRender(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-application-base/class/placeholder.md b/reference/spfx/sp-application-base/class/placeholder.md
deleted file mode 100644
index a5f6bf89bb..0000000000
--- a/reference/spfx/sp-application-base/class/placeholder.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Placeholder class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-A content placeholder is a designated region on the page (i.e. empty HTML "div" element) where third party extensions can inject HTML content.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`domElement`     | `public` | `HTMLDivElement` | _Read-only._ The HTML element on which the placeholder will be attached. This property is undefined if PlaceHolderCollection.tryAttach() was not been called, or if dispose() was called after the last call to PlaceHolderCollection.tryAttach(). |
-|`name`     | `public` | `string` | _Read-only._ A symbolic name used to identify the placeholder. Example: "PageHeader" |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`dispose()`](dispose-placeholder.md)     | `public` | `void` | Diposes the attached DOM tree. |
-
-
-
-
-
diff --git a/reference/spfx/sp-application-base/class/placeholdercollection.md b/reference/spfx/sp-application-base/class/placeholdercollection.md
deleted file mode 100644
index e38bd02639..0000000000
--- a/reference/spfx/sp-application-base/class/placeholdercollection.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# PlaceholderCollection class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Exposes a collection of content placeholders for use by third parties.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`placeholderNames`     | `public` | `ReadonlyArray<string>` | _Read-only._ Returns the names of the currently available placeholders. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`tryAttach(name,options)`](tryattach-placeholdercollection.md)     | `public` | [`Placeholder `](../../sp-application-base/class/placeholder.md),` undefined` | Searches for a content placeholder with the specified name. If none is found, then the function returns undefined. If one is found, we try to attach to it. If the caller tries to re-attached a placeholder, an exception will be thrown. A dispose has to happen before re-attach can happen. |
-
-
-
-
-
diff --git a/reference/spfx/sp-application-base/class/tryattach-placeholdercollection.md b/reference/spfx/sp-application-base/class/tryattach-placeholdercollection.md
deleted file mode 100644
index cadb101efb..0000000000
--- a/reference/spfx/sp-application-base/class/tryattach-placeholdercollection.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# tryAttach(name,options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Searches for a content placeholder with the specified name. If none is found, then the function returns undefined. If one is found, we try to attach to it. If the caller tries to re-attached a placeholder, an exception will be thrown. A dispose has to happen before re-attach can happen.
-
-**Signature:** _public tryAttach(name: string,
-    options?: [I[Placeholder](../../sp-application-base/class/placeholder.md)AttachOptions](../../sp-application-base/interface/iplaceholderattachoptions.md)): Placeholder | undefined;_
-
-**Returns**: [`Placeholder `](../../sp-application-base/class/placeholder.md),` undefined`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `name`    | `string` | logical name of the placeholder. This name should not be confused with the DOM id or the attribute value of the placeholder. |
-| `options`    | [`IPlaceholderAttachOptions`](../../sp-application-base/interface/iplaceholderattachoptions.md) | _Optional._ placeholder options. |
-
-
-### Remarks
-
-The host application makes no guarantees about the availability of a given placeholder. In situations where an expected placeholder is not available, the third party extension must handle it gracefully, e.g. by not rendering anything, or by choosing an alternative placeholder.
-
diff --git a/reference/spfx/sp-application-base/interface/iplaceholderattachoptions.md b/reference/spfx/sp-application-base/interface/iplaceholderattachoptions.md
deleted file mode 100644
index d0e62e495a..0000000000
--- a/reference/spfx/sp-application-base/interface/iplaceholderattachoptions.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IPlaceholderAttachOptions interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Options for the PlaceholderCollection.tryAttach() method.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`onDispose`      | `(placeholder: Placeholder) => void` | An event handler that will be invoked when the Placeholder.dispose() is called. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-component-base-module.md b/reference/spfx/sp-component-base-module.md
deleted file mode 100644
index 51d65c3224..0000000000
--- a/reference/spfx/sp-component-base-module.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# sp-component-base package
-
-SharePoint Framework support for building client-side components
-
-This package supports development of client-side components (e.g. web parts, client-side extensions, and applications) built using the SharePoint Framework. It defines the base classes/interfaces that represent the functionality that is common across all client-side component types.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`BaseComponent`](./sp-component-base/class/basecomponent.md)     | Base class for client-side components such as BaseClientSideWebPart, BaseExtension, etc. |
-| [`BaseComponentContext`](./sp-component-base/class/basecomponentcontext.md)     | The base class for context objects for client-side components. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IClientSideComponentContext`](./sp-component-base/interface/iclientsidecomponentcontext.md)   | The base context interface for client-side components.  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-component-base/class/basecomponent.md b/reference/spfx/sp-component-base/class/basecomponent.md
deleted file mode 100644
index 8bac842a28..0000000000
--- a/reference/spfx/sp-component-base/class/basecomponent.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# BaseComponent class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Base class for client-side components such as BaseClientSideWebPart, BaseExtension, etc.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`context`     | `public` | [`BaseComponentContext`](../../sp-component-base/class/basecomponentcontext.md) | Use context object to access common services and state associated with the component. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`onProvideServices()`](onprovideservices-basecomponent.md)     | `protected` | `void` | Constructs the object that will be returned by the "services" property. |
-
-
-
-
-
-### Remarks
-
-The constructor for this class is marked as internal; third party code should not inherit directly from this base class.
-
diff --git a/reference/spfx/sp-component-base/class/basecomponentcontext.md b/reference/spfx/sp-component-base/class/basecomponentcontext.md
deleted file mode 100644
index 6fe7d73a48..0000000000
--- a/reference/spfx/sp-component-base/class/basecomponentcontext.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# BaseComponentContext class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The base class for context objects for client-side components.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`manifest`     | `public` | `IClientSideComponentManifest` | _Read-only._ Manifest for the client side component. |
-|`serviceScope`     | `public` | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | _Read-only._ Service scope instance that is scoped to this particular web part. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`getBaseManifest()`](getbasemanifest-basecomponentcontext.md)     | `protected` | `IClientSideComponentManifest` | The child class's overridden "manifest" property should call this method. |
-
-
-
-
-
-### Remarks
-
-A "context" object is a collection of well-known services and other objects that are likely to be needed by any business logic working with the associated component. Each component type has its own specialized subclass ofClientSideComponentContext, e.g. WebPartContext for web parts, ExtensionContext for client-side extensions, etc. The constructor for this class is marked as internal; third party code should not inherit directly from this base class.
-
diff --git a/reference/spfx/sp-component-base/class/getbasemanifest-basecomponentcontext.md b/reference/spfx/sp-component-base/class/getbasemanifest-basecomponentcontext.md
deleted file mode 100644
index b8a1d7f267..0000000000
--- a/reference/spfx/sp-component-base/class/getbasemanifest-basecomponentcontext.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# getBaseManifest()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The child class's overridden "manifest" property should call this method.
-
-**Signature:** _protected getBaseManifest(): IClientSideComponentManifest;_
-
-**Returns**: `IClientSideComponentManifest`
-
-
-
-
-
-#### Parameters
-None
-
-
-### Remarks
-
-This is a workaround for a TypeScript/ES5 limitation, which prevents a subclass using "super" to access properties from the base class (even though functions work okay). It will be fixed in TypeScript/ES6.
-
diff --git a/reference/spfx/sp-component-base/class/onprovideservices-basecomponent.md b/reference/spfx/sp-component-base/class/onprovideservices-basecomponent.md
deleted file mode 100644
index 7bb109469d..0000000000
--- a/reference/spfx/sp-component-base/class/onprovideservices-basecomponent.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# onProvideServices()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Constructs the object that will be returned by the "services" property.
-
-**Signature:** _@virtual protected onProvideServices(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
-### Remarks
-
-Child classes can expose additional services by extending the IExtensionServiceCollection interface, and then overriding consumeServices() function and the "services" property.
-
diff --git a/reference/spfx/sp-component-base/interface/iclientsidecomponentcontext.md b/reference/spfx/sp-component-base/interface/iclientsidecomponentcontext.md
deleted file mode 100644
index 6ed0b4fba5..0000000000
--- a/reference/spfx/sp-component-base/interface/iclientsidecomponentcontext.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# IClientSideComponentContext interface
-
-
-
-
-
-
-
-The base context interface for client-side components.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`manifest`      | `IClientSideComponentManifest` | Manifest for the client side component. |
-|`serviceScope`      | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | Service scope instance that is scoped to this particular web part. |
-
-
-
-
-
-
-### Remarks
-
-A "context" object is a collection of well-known services and other objects that are likely to be needed by any business logic working with a component. Each component type has its own specialized extension of this interface, e.g. IWebPartContext for web parts, IExtensionContext for client-side extensions, etc.
-
diff --git a/reference/spfx/sp-core-library-module.md b/reference/spfx/sp-core-library-module.md
deleted file mode 100644
index 3276a4ef88..0000000000
--- a/reference/spfx/sp-core-library-module.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# sp-core-library package
-
-SharePoint Framework core libraries
-
-This package provides a core foundation of common definitions that ensure a consistent character across all the other SharePoint Framework APIs. Because this package is a dependency of every other package, it is effectively mandatory, so its design goals are small code size and broad applicability, versus flexibility or richness of features.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`Environment`](./sp-core-library/class/environment.md)     | This class contains contextual information about the enviroment that is hosting the framework and its components. |
-| [`Guid`](./sp-core-library/class/guid.md)     | This class represents a globally unique identifier, as described by IETF RFC 4122. The input string is normalized and validated, which provides important guarantees that simplify other code that works with the GUID. This class also provides basic support for generating a pseudo-random GUID; however, be aware that the uniqueness depends on the browser's Math.random() function and may be not be suitable for some applications. |
-| [`Log`](./sp-core-library/class/log.md)     | The Log class provides static methods for logging messages at different levels (verbose, info, warning, error) and with context information. Context information helps identify which component generated the messages and makes the messages useful and filterable. |
-| [`RandomNumberGenerator`](./sp-core-library/class/randomnumbergenerator.md)     | This is the default implementation of IRandomNumberGenerator that simply calls Math.random(). |
-| [`ServiceKey`](./sp-core-library/class/servicekey.md)     | The ServiceKey is a lookup key that is used when calling ServiceScope.consume() to fetch a dependency. The key also defines a default implementation of the dependency, which will be autocreated by the root scope if the dependency is not found. Providing a default implementation ensures that new dependencies can be safely introduced without inadvertently breaking components that are loaded by an older host (that does not provide the new dependency). |
-| [`ServiceScope`](./sp-core-library/class/servicescope.md)     | ServiceScope provides a formalized way for components to register and consume dependencies ("services"), and to enable different implementations to be registered in different scopes. This improves modularity by decoupling components from their dependencies in an extensible way. For example, suppose that various components need access to an IPageManager instance. We could simply make the PageManager a singleton (i.e. global variable), but this will not work e.g. if we need to create a pop-up dialog that requires a second PageManager instance. A better solution would be to add the PageManager as a constructor parameter for each component that requires it, however then we immediately face the problem that any code that calls these constructors also needs a PageManager parameter. In an application with many such dependencies, business logic that ties together many subsystems would eventually pick up a constructor parameter for every possible dependency, which is unwieldy. A natural solution would be to move all the dependencies into a class with name like "ApplicationContext", and then pass this around as our constructor parameter. This enables the PageManager to be passed to classes that need it without cluttering the intermediary classes that don't. However, it still has a design problem that "ApplicationContext" has hard-coded dependencies on many unrelated things. A more flexible approach is to make it a dictionary that can look up items for consumers/providers who know the right lookup key (i.e. ServiceKey). This is the popular "service locator" design pattern, familiar from the SPContext API in classic SharePoint. ServiceScope takes this idea a step further in two important ways: First, it provides a scoping mechanism so that e.g. if we had two different pages, they could each consume a unique PageManager instance while still sharing other common dependencies. Secondly, it allows for a ServiceKey to provide a default implementation of the dependency. This is important for API stability in our modular client-side environment: For example, suppose that version 2.0 of our application introduced a new IDiagnosticTracing interface that a version 2.0 component will expect to consume. If the version 2.0 component gets loaded by an older 1.0 application, it would fail. We could fix this by requiring each consumer to check for any missing dependencies and handle that case, but it would require a lot of checks. A better solution is to ensure that a default implementation always exists, perhaps just a trivial behavior, so that components don't have to worry about it. Usage: ServiceScope instances are created by calling either ServiceScope.startNewRoot() or ServiceScope.startNewChild(). They are initially in an "unfinished" state, during which provide() can be called to register service keys, but consume() is forbidden. After ServiceScope.finish() is called, consume() is allowed and provide() is now forbidden. These semantics ensure that ServiceScope.consume() always returns the same result for the same key, and does not depend on order of initialization. It also allows us to support circular dependencies without worrying about infinite loops, even when working with external components that were implemented by third parties. To avoid mistakes, it's best to always call consume() inside a callback from serviceScope.whenFinished(). |
-| [`Session`](./sp-core-library/class/session.md)     | This class contains contextual information about the application's current session. |
-| [`Text`](./sp-core-library/class/text.md)     | Common helper functions for working with strings. These utilities are intended to be simple, small, and very broadly applicable. |
-| [`TimeProvider`](./sp-core-library/class/timeprovider.md)     | This is the default implementation of ITimeProvider that simply calls the real browser APIs. |
-| [`UrlQueryParameterCollection`](./sp-core-library/class/urlqueryparametercollection.md)     | Class for storing and retrieving query parameters. The URL can be server-relative and it will parse empty/null strings. The query parameters must start with ? to indicate the first query parameter and use & for all subsequent parameters. The class also supports fragments. Edge cases behavior: Empty value (www.example.com/?test=) stores key and empty value No equals in queryParam (www.example.com/?test) stores key and undefined value Empty queryParam (www.example.com/?&debug=on) stores undefined key and value Query param with only equals (www.example.com/?=&debug=on stores empty string key and value |
-| [`Validate`](./sp-core-library/class/validate.md)     | This class implements provides a standard way to validate properties and function parameters. Unlike debug assertions, Validate checks are always performed and will always throw an error, even in a production release. As such, be careful not to overuse these checks in a way that might impact performance. |
-| [`Version`](./sp-core-library/class/version.md)     | This class represents versions that follow the string format of MAJOR.MINOR[.PATCH[.REVISION]] where MAJOR, MINOR, PATCH and REVISION are integers. PATCH and REVISION are optional. Leading zeros are allowed, but have no meaning in comparisons. Examples: 1.0, 1.0.0, 1.0.0.0, 1.01, 01.02.03, 001.002.003.004 |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IRandomNumberGenerator`](./sp-core-library/interface/irandomnumbergenerator.md)   | This is a ServiceScope interface that enables unit tests to provide a deterministic source of pseudorandom numbers.  |
-| [`IServiceCollection`](./sp-core-library/interface/iservicecollection.md)   | A shorthand pattern for extracting well-known services from a ServiceScope.  |
-| [`ITimeProvider`](./sp-core-library/interface/itimeprovider.md)   | This is a ServiceScope interface that enables unit tests to simulate the system clock.  |
-
-
-
-## Enumerations
-
-| Enumeration	   | Description|
-|:-----------|:------------|
-|[`DisplayMode`](./sp-core-library/enum/displaymode.md)    | DisplayMode indicates the mode in which a page and/or its contents (e.g. text and web parts) are dislayed. |
-|[`EnvironmentType`](./sp-core-library/enum/environmenttype.md)    | An enum that describes which type of enviroment the framework is running in. |
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/compare-version.md b/reference/spfx/sp-core-library/class/compare-version.md
deleted file mode 100644
index 7d187a39e1..0000000000
--- a/reference/spfx/sp-core-library/class/compare-version.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# compare(v1,v2)
-
-
-
-Compares two Version classes
-
-**Signature:** _public static compare(v1: [Version](../../sp-core-library/class/version.md), v2: Version): number;_
-
-**Returns**: `number`
-
-
-
--1 if the first input is less than the second input, 0 if the first input is equal to the second input, 1 if the first input is greater than the second input.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `v1`    | [`Version`](../../sp-core-library/class/version.md) | The first version class for comparison |
-| `v2`    | [`Version`](../../sp-core-library/class/version.md) | The second version class for comparison |
-
-
diff --git a/reference/spfx/sp-core-library/class/consume-servicescope.md b/reference/spfx/sp-core-library/class/consume-servicescope.md
deleted file mode 100644
index ba89018758..0000000000
--- a/reference/spfx/sp-core-library/class/consume-servicescope.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# consume(serviceKey)
-
-
-
-Components should call this function to "consume" a dependency, i.e. look up the serviceKey and return the registered service instance. If the instance cannot be found, then a default instance will be autocreated and registered with the root ServiceScope.
-
-**Signature:** _public consume < T >(serviceKey: [ServiceKey](../../sp-core-library/class/servicekey.md)<T>): T;_
-
-**Returns**: `T`
-
-
-
-- the service instance
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `serviceKey`    | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | the key that was used when provide() was called to register the service |
-
-
diff --git a/reference/spfx/sp-core-library/class/create-servicekey.md b/reference/spfx/sp-core-library/class/create-servicekey.md
deleted file mode 100644
index 10e51e2d1e..0000000000
--- a/reference/spfx/sp-core-library/class/create-servicekey.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# create(name,serviceClass)
-
-
-
-Constructs a new ServiceKey whose default implementation will be a new instance of a TypeScript class that accepts the standard constructor parameter. If you want to specify custom constructor parameters, use createCustom() instead.
-
-**Signature:** _public static create < T >(name: string,
-    serviceClass: { new (serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md)); }): [ServiceKey](../../sp-core-library/class/servicekey.md)<T>;_
-
-**Returns**: [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T>
-
-
-
-- the newly created ServiceKey
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `name`    | `string` | A name such as "MyApplication.IMyService" which should be unique within your application. |
-| `serviceClass`    | `{ new (serviceScope: ServiceScope); }` | the TypeScript class that implements the service. |
-
-
diff --git a/reference/spfx/sp-core-library/class/createandprovide-servicescope.md b/reference/spfx/sp-core-library/class/createandprovide-servicescope.md
deleted file mode 100644
index cd705406b4..0000000000
--- a/reference/spfx/sp-core-library/class/createandprovide-servicescope.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# createAndProvide(serviceKey,simpleServiceClass)
-
-
-
-This is a shorthand function that its equivalent to constructing a new instance of the simpleServiceClass, then registering it by calling ServiceScope.provide().
-
-**Signature:** _public createAndProvide < T >(serviceKey: [ServiceKey](../../sp-core-library/class/servicekey.md)<T>,
-    simpleServiceClass: { new (serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md)); }): T;_
-
-**Returns**: `T`
-
-
-
-- a newly constructed instance of simpleServiceClass
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `serviceKey`    | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | the key that can be used later to consume the service |
-| `simpleServiceClass`    | `{ new (serviceScope: ServiceScope); }` | the TypeScript class to be constructed |
-
-
diff --git a/reference/spfx/sp-core-library/class/createcustom-servicekey.md b/reference/spfx/sp-core-library/class/createcustom-servicekey.md
deleted file mode 100644
index 79a14ebf87..0000000000
--- a/reference/spfx/sp-core-library/class/createcustom-servicekey.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# createCustom(name,defaultCreator)
-
-
-
-Constructs a new ServiceKey whose default implementation will be obtained by invoking the specified callback.
-
-**Signature:** _public static createCustom < T >(name: string, defaultCreator: ServiceCreator<T>): [ServiceKey](../../sp-core-library/class/servicekey.md)<T>;_
-
-**Returns**: [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T>
-
-
-
-- the newly created ServiceKey
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `name`    | `string` | A name such as "MyApplication.IMyService" which should be unique within your application. |
-| `defaultCreator`    | `ServiceCreator<T>` | A callback that returns an object that implements the T interface |
-
-
diff --git a/reference/spfx/sp-core-library/class/createdefaultandprovide-servicescope.md b/reference/spfx/sp-core-library/class/createdefaultandprovide-servicescope.md
deleted file mode 100644
index 4fea9b5069..0000000000
--- a/reference/spfx/sp-core-library/class/createdefaultandprovide-servicescope.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# createDefaultAndProvide(serviceKey)
-
-
-
-This is a shorthand function that constructs the default implementation of the specified serviceKey, and then registers it by calling ServiceScope.provide().
-
-**Signature:** _public createDefaultAndProvide < T >(serviceKey: [ServiceKey](../../sp-core-library/class/servicekey.md)<T>): T;_
-
-**Returns**: `T`
-
-
-
-- a service instance that was constructed using ServiceKey.defaultCreator
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `serviceKey`    | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | the key that can be used later to consume the service |
-
-
diff --git a/reference/spfx/sp-core-library/class/environment.md b/reference/spfx/sp-core-library/class/environment.md
deleted file mode 100644
index 83edd1ae48..0000000000
--- a/reference/spfx/sp-core-library/class/environment.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# Environment class
-
-
-
-
-
-
-
-This class contains contextual information about the enviroment that is hosting the framework and its components.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`type`     | `public` | [`EnvironmentType`](../../sp-core-library/enum/environmenttype.md) | _Read-only._ An enum that describes which type of enviroment the framework is running in. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/equals-guid.md b/reference/spfx/sp-core-library/class/equals-guid.md
deleted file mode 100644
index 6dc7f94e8d..0000000000
--- a/reference/spfx/sp-core-library/class/equals-guid.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# equals()
-
-
-
-Compare this instance to another Guid instance
-
-**Signature:** _public equals(guid: [Guid](../../sp-core-library/class/guid.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-True if this instance and the specified Guid object represent the same value.
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/equals-version.md b/reference/spfx/sp-core-library/class/equals-version.md
deleted file mode 100644
index ef463dce84..0000000000
--- a/reference/spfx/sp-core-library/class/equals-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# equals(compareWith)
-
-
-
-Checks if this version is equal to the input parameter. Missing patch number is treated as zero. Examples: 1.0.0 equals 1.0.0 -> true 2.0.1 equals 2.0.0 -> false 3.0 equals 3.0.0 -> true 04.01 equals 4.1 -> true
-
-**Signature:** _public equals(compareWith: [Version](../../sp-core-library/class/version.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-A boolean indicating if this version is equal to the input parameter
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `compareWith`    | [`Version`](../../sp-core-library/class/version.md) | The version to compare with |
-
-
diff --git a/reference/spfx/sp-core-library/class/error-log.md b/reference/spfx/sp-core-library/class/error-log.md
deleted file mode 100644
index 62df42e61b..0000000000
--- a/reference/spfx/sp-core-library/class/error-log.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# error(source,error,scope)
-
-
-
-Logs an error
-
-**Signature:** _public static error(source: string, error: Error, scope?: [ServiceScope](../../sp-core-library/class/servicescope.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `source`    | `string` | the source from where the error is logged, e.g., the class name. The source provides context information for the logged error. If the source's length is more than 20, only the first 20 characters are kept. |
-| `error`    | `Error` | the error to be logged |
-| `scope`    | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | _Optional._ the service scope that the source uses. A service scope can provide more context information (e.g., web part information) to the logged error. |
-
-
diff --git a/reference/spfx/sp-core-library/class/finish-servicescope.md b/reference/spfx/sp-core-library/class/finish-servicescope.md
deleted file mode 100644
index 0bec2cc195..0000000000
--- a/reference/spfx/sp-core-library/class/finish-servicescope.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# finish()
-
-
-
-When a ServiceScope is first started, it is in an "unfinished" state where provide() is allowed but consume() is not allowed. After calling finish(), then consume() is allowed but provide() is not allowed. This formalism completely eliminates a number of tricky bugs such as: Scope2 is a child of Scope1, and Scope1 provides instance A1 of interface A; if someone consumes A1 from Scope2 (via inheritance) before Scope2.provide() is called with A2, then a subsequent call to Scope2.consume() might return a different result than the previous call, which would be very confusing for developers.
-
-**Signature:** _public finish(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/format-text.md b/reference/spfx/sp-core-library/class/format-text.md
deleted file mode 100644
index 74b8be43cd..0000000000
--- a/reference/spfx/sp-core-library/class/format-text.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# format()
-
-
-
-String Format, like C# string format. Usage Example: StringUtilities.format("hello {0}!", "mike") will return "hello mike!"
-
-**Signature:** _public static format(s: string, ...values: any[]): string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/generate-randomnumbergenerator.md b/reference/spfx/sp-core-library/class/generate-randomnumbergenerator.md
deleted file mode 100644
index 8c0376fdfb..0000000000
--- a/reference/spfx/sp-core-library/class/generate-randomnumbergenerator.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# generate()
-
-
-
-
-
-**Signature:** _public generate(): number;_
-
-**Returns**: `number`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/getdate-timeprovider.md b/reference/spfx/sp-core-library/class/getdate-timeprovider.md
deleted file mode 100644
index 11ea30c726..0000000000
--- a/reference/spfx/sp-core-library/class/getdate-timeprovider.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getDate()
-
-
-
-
-
-**Signature:** _public getDate(): Date;_
-
-**Returns**: `Date`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/getparent-servicescope.md b/reference/spfx/sp-core-library/class/getparent-servicescope.md
deleted file mode 100644
index 93646c4a57..0000000000
--- a/reference/spfx/sp-core-library/class/getparent-servicescope.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getParent()
-
-
-
-Returns the parent of the current ServiceScope, or undefined if this is a root scope.
-
-**Signature:** _public getParent(): [ServiceScope](../../sp-core-library/class/servicescope.md) | undefined;_
-
-**Returns**: [`ServiceScope `](../../sp-core-library/class/servicescope.md),` undefined`
-
-
-
-- the parent service scope
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/gettimestamp-timeprovider.md b/reference/spfx/sp-core-library/class/gettimestamp-timeprovider.md
deleted file mode 100644
index 99524a1b7b..0000000000
--- a/reference/spfx/sp-core-library/class/gettimestamp-timeprovider.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getTimestamp()
-
-
-
-
-
-**Signature:** _public getTimestamp(): number;_
-
-**Returns**: `number`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/getvalue-urlqueryparametercollection.md b/reference/spfx/sp-core-library/class/getvalue-urlqueryparametercollection.md
deleted file mode 100644
index 2ce514d02f..0000000000
--- a/reference/spfx/sp-core-library/class/getvalue-urlqueryparametercollection.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# getValue(param)
-
-
-
-Returns the value of the first matching query parameter or undefined if the key doesn't exist. Examples: this._queryParameterList = [ {key: TEST, value: done}, {key: DEBUG, value: false}, {key: TEST, value: notdone}] getValue('TEST') ---> 'done' getValue('debug') ---> 'false' getValue('lost') ---> undefined
-
-**Signature:** _public getValue(param: string): string | undefined;_
-
-**Returns**: `string `,` undefined`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `param`    | `string` | the case insensitive key for the desired query parameter value. |
-
-
diff --git a/reference/spfx/sp-core-library/class/getvalues-urlqueryparametercollection.md b/reference/spfx/sp-core-library/class/getvalues-urlqueryparametercollection.md
deleted file mode 100644
index 8feda7d7db..0000000000
--- a/reference/spfx/sp-core-library/class/getvalues-urlqueryparametercollection.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# getValues(param)
-
-
-
-Returns the values of all of the matching query parameters or undefined if the key doesn't exist. Examples: this._queryParameterList = [ {key: TEST, value: done}, {key: DEBUG, value: false}, {key: TEST, value: notdone}] getValues('TEST') ---> ['done', 'notdone'] getValues('debug') ---> ['false'] getValues('lost') ---> undefined
-
-**Signature:** _public getValues(param: string): (string | undefined)[] | undefined;_
-
-**Returns**: `(string `,` undefined)[] `,` undefined`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `param`    | `string` | the case insensitive key for the desired query parameter value. |
-
-
diff --git a/reference/spfx/sp-core-library/class/greaterthan-version.md b/reference/spfx/sp-core-library/class/greaterthan-version.md
deleted file mode 100644
index 1b222e0859..0000000000
--- a/reference/spfx/sp-core-library/class/greaterthan-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# greaterThan(compareWith)
-
-
-
-Checks if this version is greater (i.e. newer) than the input parameter. Missing patch number is treated as zero Examples: 1.0.0 greaterThan 0.0.9 -> true 2.0 greaterThan 2.0.0 -> false 3.0.1 greaterThan 3.0 -> true
-
-**Signature:** _public greaterThan(compareWith: [Version](../../sp-core-library/class/version.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-A boolean indicating if this version is greater than the input parameter
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `compareWith`    | [`Version`](../../sp-core-library/class/version.md) | The version to compare with |
-
-
diff --git a/reference/spfx/sp-core-library/class/guid.md b/reference/spfx/sp-core-library/class/guid.md
deleted file mode 100644
index 816889cfb1..0000000000
--- a/reference/spfx/sp-core-library/class/guid.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Guid class
-
-
-
-
-
-
-
-This class represents a globally unique identifier, as described by IETF RFC 4122. The input string is normalized and validated, which provides important guarantees that simplify other code that works with the GUID. This class also provides basic support for generating a pseudo-random GUID; however, be aware that the uniqueness depends on the browser's Math.random() function and may be not be suitable for some applications.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`empty`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | Returns a new empty Guid instance. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`equals()`](equals-guid.md)     | `public` | `boolean` | Compare this instance to another Guid instance |
-|[`isValid(guid)`](isvalid-guid.md)     | `public, static` | `boolean` | Indicates whether a guid is valid, i.e. whether it would be successfully parsed by Guid.tryParse(). This function is cheaper than Guid.tryParse() because it does not construct a Guid object. |
-|[`newGuid()`](newguid-guid.md)     | `public, static` | [`Guid`](../../sp-core-library/class/guid.md) | Returns a new Guid instance with a pseudo-randomly generated Guid, according to the version 4 UUID algorithm from RFC 4122. |
-|[`parse(guid)`](parse-guid.md)     | `public, static` | [`Guid`](../../sp-core-library/class/guid.md) | Parses the input string to construct a new Guid object. If the string cannot be parsed, then an error is thrown. |
-|[`toString()`](tostring-guid.md)     | `public` | `string` | Object.prototype.toString override |
-|[`tryParse(guid)`](tryparse-guid.md)     | `public, static` | [`Guid `](../../sp-core-library/class/guid.md),` undefined` | Attempts to parse the input string to construct a new Guid object. If the string cannot be parsed, then undefined is returned. |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/info-log.md b/reference/spfx/sp-core-library/class/info-log.md
deleted file mode 100644
index 52aac22418..0000000000
--- a/reference/spfx/sp-core-library/class/info-log.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# info(source,message,scope)
-
-
-
-Logs an informational message
-
-**Signature:** _public static info(source: string, message: string, scope?: [ServiceScope](../../sp-core-library/class/servicescope.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `source`    | `string` | the source from where the message is logged, e.g., the class name. The source provides context information for the logged message. If the source's length is more than 20, only the first 20 characters are kept. |
-| `message`    | `string` | the message to be logged If the message's length is more than 100, only the first 100 characters are kept. |
-| `scope`    | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | _Optional._ the service scope that the source uses. A service scope can provide more context information (e.g., web part information) to the logged message. |
-
-
diff --git a/reference/spfx/sp-core-library/class/isnonemptystring-validate.md b/reference/spfx/sp-core-library/class/isnonemptystring-validate.md
deleted file mode 100644
index bc990b6f09..0000000000
--- a/reference/spfx/sp-core-library/class/isnonemptystring-validate.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# isNonemptyString(value,variableName)
-
-
-
-Throws an exception if the specified string is null, undefined, or an empty string.
-
-**Signature:** _public static isNonemptyString(value: string | undefined | null, variableName: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `value`    | `string `,` undefined `,` null` | the value to check |
-| `variableName`    | `string` | the program variable name, which will be mentioned in the error message |
-
-
diff --git a/reference/spfx/sp-core-library/class/isnotnullorundefined-validate.md b/reference/spfx/sp-core-library/class/isnotnullorundefined-validate.md
deleted file mode 100644
index e1f3446330..0000000000
--- a/reference/spfx/sp-core-library/class/isnotnullorundefined-validate.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# isNotNullOrUndefined(value,variableName)
-
-
-
-Throws an exception if the specified value is null or undefined.
-
-**Signature:** _public static isNotNullOrUndefined(value: any, variableName: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `value`    | `any` | the value to check |
-| `variableName`    | `string` | the program variable name, which will be mentioned in the error message |
-
-
diff --git a/reference/spfx/sp-core-library/class/istrue-validate.md b/reference/spfx/sp-core-library/class/istrue-validate.md
deleted file mode 100644
index 516bf4be5f..0000000000
--- a/reference/spfx/sp-core-library/class/istrue-validate.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# isTrue(value,variableName)
-
-
-
-Throws an exception if the specified value is not true.
-
-**Signature:** _public static isTrue(value: boolean | undefined | null, variableName: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `value`    | `boolean `,` undefined `,` null` | the value to check |
-| `variableName`    | `string` | the program variable name, which will be mentioned in the error message |
-
-
diff --git a/reference/spfx/sp-core-library/class/isvalid-guid.md b/reference/spfx/sp-core-library/class/isvalid-guid.md
deleted file mode 100644
index 72444e4b99..0000000000
--- a/reference/spfx/sp-core-library/class/isvalid-guid.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# isValid(guid)
-
-
-
-Indicates whether a guid is valid, i.e. whether it would be successfully parsed by Guid.tryParse(). This function is cheaper than Guid.tryParse() because it does not construct a Guid object.
-
-**Signature:** _public static isValid(guid: string | undefined | null): boolean;_
-
-**Returns**: `boolean`
-
-
-
-true, if the Guid is valid.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `guid`    | `string `,` undefined `,` null` | The input string. |
-
-
diff --git a/reference/spfx/sp-core-library/class/isvalid-version.md b/reference/spfx/sp-core-library/class/isvalid-version.md
deleted file mode 100644
index 0137387b3d..0000000000
--- a/reference/spfx/sp-core-library/class/isvalid-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# isValid(versionString)
-
-
-
-Indicates whether a version string is valid
-
-**Signature:** _public static isValid(versionString: string | undefined | null): boolean;_
-
-**Returns**: `boolean`
-
-
-
-Value indicating whether the version is valid.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `versionString`    | `string `,` undefined `,` null` | The version string |
-
-
diff --git a/reference/spfx/sp-core-library/class/lessthan-version.md b/reference/spfx/sp-core-library/class/lessthan-version.md
deleted file mode 100644
index ac053b3ea4..0000000000
--- a/reference/spfx/sp-core-library/class/lessthan-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# lessThan(compareWith)
-
-
-
-Checks if this version is less (i.e. older) than the input parameter. Missing patch number is treated as zero Examples: 0.9.9 lessThan 1.0.0 -> true 2.0 lessThan 2.0.0 -> false 3.0 lessThan 3.0.1 -> true 04.01 lessThan 4.1 -> false
-
-**Signature:** _public lessThan(compareWith: [Version](../../sp-core-library/class/version.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-A boolean indicating if this version is less than the input parameter
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `compareWith`    | [`Version`](../../sp-core-library/class/version.md) | The version to compare with |
-
-
diff --git a/reference/spfx/sp-core-library/class/log.md b/reference/spfx/sp-core-library/class/log.md
deleted file mode 100644
index 48e2510f9e..0000000000
--- a/reference/spfx/sp-core-library/class/log.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Log class
-
-
-
-
-
-
-
-The Log class provides static methods for logging messages at different levels (verbose, info, warning, error) and with context information. Context information helps identify which component generated the messages and makes the messages useful and filterable.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`error(source,error,scope)`](error-log.md)     | `public, static` | `void` | Logs an error |
-|[`info(source,message,scope)`](info-log.md)     | `public, static` | `void` | Logs an informational message |
-|[`verbose(source,message,scope)`](verbose-log.md)     | `public, static` | `void` | Logs a verbose message |
-|[`warn(source,message,scope)`](warn-log.md)     | `public, static` | `void` | Logs a warning |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/newguid-guid.md b/reference/spfx/sp-core-library/class/newguid-guid.md
deleted file mode 100644
index 20bd662ba8..0000000000
--- a/reference/spfx/sp-core-library/class/newguid-guid.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# newGuid()
-
-
-
-Returns a new Guid instance with a pseudo-randomly generated Guid, according to the version 4 UUID algorithm from RFC 4122.
-
-**Signature:** _public static new[Guid](../../sp-core-library/class/guid.md)(randomNumberGenerator?: [IRandomNumberGenerator](../../sp-core-library/interface/irandomnumbergenerator.md)): Guid;_
-
-**Returns**: [`Guid`](../../sp-core-library/class/guid.md)
-
-
-
-A new unique Guid object
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/parse-guid.md b/reference/spfx/sp-core-library/class/parse-guid.md
deleted file mode 100644
index e64349ea13..0000000000
--- a/reference/spfx/sp-core-library/class/parse-guid.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# parse(guid)
-
-
-
-Parses the input string to construct a new Guid object. If the string cannot be parsed, then an error is thrown.
-
-**Signature:** _public static parse(guidString: string | undefined | null): [Guid](../../sp-core-library/class/guid.md);_
-
-**Returns**: [`Guid`](../../sp-core-library/class/guid.md)
-
-
-
-A valid Guid object
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `guid`    |  | The input string. |
-
-
-### Remarks
-
-Example syntaxes accepted by this function: 'd5369f3b-bd7a-412a-9c0f-7f0650bb5489' '{d5369f3b-bd7a-412a-9c0f-7f0650bb5489}' '/Guid(d5369f3b-bd7a-412a-9c0f-7f0650bb5489)'
-
diff --git a/reference/spfx/sp-core-library/class/parse-version.md b/reference/spfx/sp-core-library/class/parse-version.md
deleted file mode 100644
index 31615ee9c0..0000000000
--- a/reference/spfx/sp-core-library/class/parse-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# parse(versionString)
-
-
-
-Constructs a new Version instance using the version string. tryParse validates the input version string and throws error if it is invalid
-
-**Signature:** _public static parse(versionString: string | undefined | null): [Version](../../sp-core-library/class/version.md);_
-
-**Returns**: [`Version`](../../sp-core-library/class/version.md)
-
-
-
-If valid, a new Version instace
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `versionString`    | `string `,` undefined `,` null` | A version string |
-
-
diff --git a/reference/spfx/sp-core-library/class/provide-servicescope.md b/reference/spfx/sp-core-library/class/provide-servicescope.md
deleted file mode 100644
index 731f24c490..0000000000
--- a/reference/spfx/sp-core-library/class/provide-servicescope.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# provide(serviceKey,service)
-
-
-
-ServiceScope.provide() is used to register an implemententation of the given serviceKey for the current scope. It may only be used when the ServiceScope is in an "unfinished" state, i.e. before finish() has been called.
-
-**Signature:** _public provide < T >(serviceKey: [ServiceKey](../../sp-core-library/class/servicekey.md)<T>, service: T): T;_
-
-**Returns**: `T`
-
-
-
-- the same object that was passed as the "service" parameter
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `serviceKey`    | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | the key that will later be used to consume the service |
-| `service`    | `T` | the service instance that is being registered |
-
-
diff --git a/reference/spfx/sp-core-library/class/randomnumbergenerator.md b/reference/spfx/sp-core-library/class/randomnumbergenerator.md
deleted file mode 100644
index 0a2208371c..0000000000
--- a/reference/spfx/sp-core-library/class/randomnumbergenerator.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# RandomNumberGenerator class
-
-_Implements: [`IRandomNumberGenerator`](../../sp-core-library/interface/irandomnumbergenerator.md)_
-
-
-
-
-
-This is the default implementation of IRandomNumberGenerator that simply calls Math.random().
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`IRandomNumberGenerator`](../../sp-core-library/interface/irandomnumbergenerator.md)> | The service key for IRandomNumberGenerator. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`generate()`](generate-randomnumbergenerator.md)     | `public` | `number` |  |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/satisfies-version.md b/reference/spfx/sp-core-library/class/satisfies-version.md
deleted file mode 100644
index 38e6ff670d..0000000000
--- a/reference/spfx/sp-core-library/class/satisfies-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# satisfies(compareWith)
-
-
-
-Checks if this version satisfies the input parameter, therefore it's backwards compatible. They have to share the same major version, and the input parameter must be an equal or more recent version. Examples: 1.0.0 satisfies 1.0.0 -> true 1.1.0 satisfies 1.0.0 -> true 2.0.0 satisfies 1.0.0 -> false 1.0.0 satisfies 1.1.0 -> false
-
-**Signature:** _public satisfies(compareWith: [Version](../../sp-core-library/class/version.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-A boolean indicating if this version is compatible with the input parameter
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `compareWith`    | [`Version`](../../sp-core-library/class/version.md) | The version to compare with |
-
-
diff --git a/reference/spfx/sp-core-library/class/servicekey.md b/reference/spfx/sp-core-library/class/servicekey.md
deleted file mode 100644
index c5a0c82ae5..0000000000
--- a/reference/spfx/sp-core-library/class/servicekey.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# ServiceKey <T> class
-
-
-
-_Type parameters: `<T>`_
-
-
-
-The ServiceKey is a lookup key that is used when calling ServiceScope.consume() to fetch a dependency. The key also defines a default implementation of the dependency, which will be autocreated by the root scope if the dependency is not found. Providing a default implementation ensures that new dependencies can be safely introduced without inadvertently breaking components that are loaded by an older host (that does not provide the new dependency).
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`defaultCreator`     | `public` | `ServiceCreator<T>` |  |
-|`id`     | `public` | `string` |  |
-|`name`     | `public` | `string` |  |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`create(name,serviceClass)`](create-servicekey.md)     | `public, static` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | Constructs a new ServiceKey whose default implementation will be a new instance of a TypeScript class that accepts the standard constructor parameter. If you want to specify custom constructor parameters, use createCustom() instead. |
-|[`createCustom(name,defaultCreator)`](createcustom-servicekey.md)     | `public, static` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<T> | Constructs a new ServiceKey whose default implementation will be obtained by invoking the specified callback. |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/servicescope.md b/reference/spfx/sp-core-library/class/servicescope.md
deleted file mode 100644
index e1d4187939..0000000000
--- a/reference/spfx/sp-core-library/class/servicescope.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# ServiceScope class
-
-
-
-
-
-
-
-ServiceScope provides a formalized way for components to register and consume dependencies ("services"), and to enable different implementations to be registered in different scopes. This improves modularity by decoupling components from their dependencies in an extensible way. For example, suppose that various components need access to an IPageManager instance. We could simply make the PageManager a singleton (i.e. global variable), but this will not work e.g. if we need to create a pop-up dialog that requires a second PageManager instance. A better solution would be to add the PageManager as a constructor parameter for each component that requires it, however then we immediately face the problem that any code that calls these constructors also needs a PageManager parameter. In an application with many such dependencies, business logic that ties together many subsystems would eventually pick up a constructor parameter for every possible dependency, which is unwieldy. A natural solution would be to move all the dependencies into a class with name like "ApplicationContext", and then pass this around as our constructor parameter. This enables the PageManager to be passed to classes that need it without cluttering the intermediary classes that don't. However, it still has a design problem that "ApplicationContext" has hard-coded dependencies on many unrelated things. A more flexible approach is to make it a dictionary that can look up items for consumers/providers who know the right lookup key (i.e. ServiceKey). This is the popular "service locator" design pattern, familiar from the SPContext API in classic SharePoint. ServiceScope takes this idea a step further in two important ways: First, it provides a scoping mechanism so that e.g. if we had two different pages, they could each consume a unique PageManager instance while still sharing other common dependencies. Secondly, it allows for a ServiceKey to provide a default implementation of the dependency. This is important for API stability in our modular client-side environment: For example, suppose that version 2.0 of our application introduced a new IDiagnosticTracing interface that a version 2.0 component will expect to consume. If the version 2.0 component gets loaded by an older 1.0 application, it would fail. We could fix this by requiring each consumer to check for any missing dependencies and handle that case, but it would require a lot of checks. A better solution is to ensure that a default implementation always exists, perhaps just a trivial behavior, so that components don't have to worry about it. Usage: ServiceScope instances are created by calling either ServiceScope.startNewRoot() or ServiceScope.startNewChild(). They are initially in an "unfinished" state, during which provide() can be called to register service keys, but consume() is forbidden. After ServiceScope.finish() is called, consume() is allowed and provide() is now forbidden. These semantics ensure that ServiceScope.consume() always returns the same result for the same key, and does not depend on order of initialization. It also allows us to support circular dependencies without worrying about infinite loops, even when working with external components that were implemented by third parties. To avoid mistakes, it's best to always call consume() inside a callback from serviceScope.whenFinished().
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`consume(serviceKey)`](consume-servicescope.md)     | `public` | `T` | Components should call this function to "consume" a dependency, i.e. look up the serviceKey and return the registered service instance. If the instance cannot be found, then a default instance will be autocreated and registered with the root ServiceScope. |
-|[`createAndProvide(serviceKey,simpleServiceClass)`](createandprovide-servicescope.md)     | `public` | `T` | This is a shorthand function that its equivalent to constructing a new instance of the simpleServiceClass, then registering it by calling ServiceScope.provide(). |
-|[`createDefaultAndProvide(serviceKey)`](createdefaultandprovide-servicescope.md)     | `public` | `T` | This is a shorthand function that constructs the default implementation of the specified serviceKey, and then registers it by calling ServiceScope.provide(). |
-|[`finish()`](finish-servicescope.md)     | `public` | `void` | When a ServiceScope is first started, it is in an "unfinished" state where provide() is allowed but consume() is not allowed. After calling finish(), then consume() is allowed but provide() is not allowed. This formalism completely eliminates a number of tricky bugs such as: Scope2 is a child of Scope1, and Scope1 provides instance A1 of interface A; if someone consumes A1 from Scope2 (via inheritance) before Scope2.provide() is called with A2, then a subsequent call to Scope2.consume() might return a different result than the previous call, which would be very confusing for developers. |
-|[`getParent()`](getparent-servicescope.md)     | `public` | [`ServiceScope `](../../sp-core-library/class/servicescope.md),` undefined` | Returns the parent of the current ServiceScope, or undefined if this is a root scope. |
-|[`provide(serviceKey,service)`](provide-servicescope.md)     | `public` | `T` | ServiceScope.provide() is used to register an implemententation of the given serviceKey for the current scope. It may only be used when the ServiceScope is in an "unfinished" state, i.e. before finish() has been called. |
-|[`startNewChild()`](startnewchild-servicescope.md)     | `public` | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | Constructs a new ServiceScope that is a child of the current scope. For any keys that are not explicitly provided by the child scope, the parent hierarchy will be consulted. |
-|[`startNewRoot()`](startnewroot-servicescope.md)     | `public, static` | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | Create a new root-level ServiceScope. Only root-level scopes have the ability to autocreate default implementations of ServiceKeys. |
-|[`whenFinished(callback)`](whenfinished-servicescope.md)     | `public` | `void` | It is an error to call ServiceScope.consume() before finish() has been called. The most reliable way to protect your component against this error is to perform the consume() calls inside a whenFinished() callback. If the service scope is already finished, then the callback will be executed immediately; otherwise, it will be executed later when the scope is finished. |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/session.md b/reference/spfx/sp-core-library/class/session.md
deleted file mode 100644
index 552ac1a353..0000000000
--- a/reference/spfx/sp-core-library/class/session.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Session class
-
-
-
-
-
-
-
-This class contains contextual information about the application's current session.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`applicationId`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ A unique identifier used to correlate logging and other diagnostic information. Its lifetime persists for the duration of the client-side application instance, i.e. it begins with the server request that renders the page, and ends e.g. when the browser tab is closed or F5 is pressed to reload the page. Note that if the application's router supports in-place navigation (via the history.pushState() API), the application session persists across these transitions. |
-|`pageId`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ A unique identifier used to correlate logging and other diagnostic information. Whereas the applicationId tracks the entire lifetime of the client-side application instance, the pageId tracks an individual "page" that is rendered. For example, suppose that the application initially loads PageA, then the user does in-place navigation (via the history.pushState() API) to PageB, then navigates back to PageA, and finally they close the browser tab. During this sequence, the applicationId will remain the same, however the pageId will change on each navigation. The 3 different pageId values are used by the diagnostics e.g. to track success/failure statistics for PageA independently of PageB. The concept of a "page" is application-defined. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/startnewchild-servicescope.md b/reference/spfx/sp-core-library/class/startnewchild-servicescope.md
deleted file mode 100644
index 215afda4b3..0000000000
--- a/reference/spfx/sp-core-library/class/startnewchild-servicescope.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# startNewChild()
-
-
-
-Constructs a new ServiceScope that is a child of the current scope. For any keys that are not explicitly provided by the child scope, the parent hierarchy will be consulted.
-
-**Signature:** _public startNewChild(): [ServiceScope](../../sp-core-library/class/servicescope.md);_
-
-**Returns**: [`ServiceScope`](../../sp-core-library/class/servicescope.md)
-
-
-
-- the newly created root ServiceScope
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/startnewroot-servicescope.md b/reference/spfx/sp-core-library/class/startnewroot-servicescope.md
deleted file mode 100644
index 8fc2f3ab82..0000000000
--- a/reference/spfx/sp-core-library/class/startnewroot-servicescope.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# startNewRoot()
-
-
-
-Create a new root-level ServiceScope. Only root-level scopes have the ability to autocreate default implementations of ServiceKeys.
-
-**Signature:** _public static startNewRoot(): [ServiceScope](../../sp-core-library/class/servicescope.md);_
-
-**Returns**: [`ServiceScope`](../../sp-core-library/class/servicescope.md)
-
-
-
-- the newly created root ServiceScope
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/text.md b/reference/spfx/sp-core-library/class/text.md
deleted file mode 100644
index 677dbfb1bf..0000000000
--- a/reference/spfx/sp-core-library/class/text.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Text class
-
-
-
-
-
-
-
-Common helper functions for working with strings. These utilities are intended to be simple, small, and very broadly applicable.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`format()`](format-text.md)     | `public, static` | `string` | String Format, like C# string format. Usage Example: StringUtilities.format("hello {0}!", "mike") will return "hello mike!" |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/timeprovider.md b/reference/spfx/sp-core-library/class/timeprovider.md
deleted file mode 100644
index 8b810cd72d..0000000000
--- a/reference/spfx/sp-core-library/class/timeprovider.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# TimeProvider class
-
-_Implements: [`ITimeProvider`](../../sp-core-library/interface/itimeprovider.md)_
-
-
-
-
-
-This is the default implementation of ITimeProvider that simply calls the real browser APIs.
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`ITimeProvider`](../../sp-core-library/interface/itimeprovider.md)> | The service key for ITimeProvider.<br/> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._ |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`getDate()`](getdate-timeprovider.md)     | `public` | `Date` |  |
-|[`getTimestamp()`](gettimestamp-timeprovider.md)     | `public` | `number` |  |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/tostring-guid.md b/reference/spfx/sp-core-library/class/tostring-guid.md
deleted file mode 100644
index 5b088f3c71..0000000000
--- a/reference/spfx/sp-core-library/class/tostring-guid.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# toString()
-
-
-
-Object.prototype.toString override
-
-**Signature:** _public toString(): string;_
-
-**Returns**: `string`
-
-
-
-The GUID value in lowercase hexadecimal without braces. Example: 'd5369f3b-bd7a-412a-9c0f-7f0650bb5489'
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/tostring-version.md b/reference/spfx/sp-core-library/class/tostring-version.md
deleted file mode 100644
index 434e456f25..0000000000
--- a/reference/spfx/sp-core-library/class/tostring-version.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# toString()
-
-
-
-Object.prototype.toString override The version string in MAJOR.MINOR[.PATCH[.REVISION]]
-
-**Signature:** _public toString(): string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/class/tryparse-guid.md b/reference/spfx/sp-core-library/class/tryparse-guid.md
deleted file mode 100644
index e805146498..0000000000
--- a/reference/spfx/sp-core-library/class/tryparse-guid.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# tryParse(guid)
-
-
-
-Attempts to parse the input string to construct a new Guid object. If the string cannot be parsed, then undefined is returned.
-
-**Signature:** _public static tryParse(guid: string | undefined | null): [Guid](../../sp-core-library/class/guid.md) | undefined;_
-
-**Returns**: [`Guid `](../../sp-core-library/class/guid.md),` undefined`
-
-
-
-The Guid object, or undefined if the string could not be parsed.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `guid`    | `string `,` undefined `,` null` | The input string. |
-
-
-### Remarks
-
-Example syntaxes accepted by this function: 'd5369f3b-bd7a-412a-9c0f-7f0650bb5489' '{d5369f3b-bd7a-412a-9c0f-7f0650bb5489}' '/Guid(d5369f3b-bd7a-412a-9c0f-7f0650bb5489)'
-
diff --git a/reference/spfx/sp-core-library/class/tryparse-version.md b/reference/spfx/sp-core-library/class/tryparse-version.md
deleted file mode 100644
index e0391bb57e..0000000000
--- a/reference/spfx/sp-core-library/class/tryparse-version.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# tryParse(versionString)
-
-
-
-Tries to construct a new Version instance using the version string. Returns undefined if not successful.
-
-**Signature:** _public static tryParse(versionString: string | undefined | null): [Version](../../sp-core-library/class/version.md) | undefined;_
-
-**Returns**: [`Version `](../../sp-core-library/class/version.md),` undefined`
-
-
-
-If valid, a new Version instace. Otherwise, undefined.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `versionString`    | `string `,` undefined `,` null` | A version string |
-
-
diff --git a/reference/spfx/sp-core-library/class/urlqueryparametercollection.md b/reference/spfx/sp-core-library/class/urlqueryparametercollection.md
deleted file mode 100644
index a4170ad475..0000000000
--- a/reference/spfx/sp-core-library/class/urlqueryparametercollection.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# UrlQueryParameterCollection class
-
-
-
-
-
-
-
-Class for storing and retrieving query parameters. The URL can be server-relative and it will parse empty/null strings. The query parameters must start with ? to indicate the first query parameter and use & for all subsequent parameters. The class also supports fragments. Edge cases behavior: Empty value (www.example.com/?test=) stores key and empty value No equals in queryParam (www.example.com/?test) stores key and undefined value Empty queryParam (www.example.com/?&debug=on) stores undefined key and value Query param with only equals (www.example.com/?=&debug=on stores empty string key and value
-
-
-## Constructor
-
-
-**Signature:** _constructor(url: string);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`getValue(param)`](getvalue-urlqueryparametercollection.md)     | `public` | `string `,` undefined` | Returns the value of the first matching query parameter or undefined if the key doesn't exist. Examples: this._queryParameterList = [ {key: TEST, value: done}, {key: DEBUG, value: false}, {key: TEST, value: notdone}] getValue('TEST') ---> 'done' getValue('debug') ---> 'false' getValue('lost') ---> undefined |
-|[`getValues(param)`](getvalues-urlqueryparametercollection.md)     | `public` | `(string `,` undefined)[] `,` undefined` | Returns the values of all of the matching query parameters or undefined if the key doesn't exist. Examples: this._queryParameterList = [ {key: TEST, value: done}, {key: DEBUG, value: false}, {key: TEST, value: notdone}] getValues('TEST') ---> ['done', 'notdone'] getValues('debug') ---> ['false'] getValues('lost') ---> undefined |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/validate.md b/reference/spfx/sp-core-library/class/validate.md
deleted file mode 100644
index 6f22119cef..0000000000
--- a/reference/spfx/sp-core-library/class/validate.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# Validate class
-
-
-
-
-
-
-
-This class implements provides a standard way to validate properties and function parameters. Unlike debug assertions, Validate checks are always performed and will always throw an error, even in a production release. As such, be careful not to overuse these checks in a way that might impact performance.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`isNonemptyString(value,variableName)`](isnonemptystring-validate.md)     | `public, static` | `void` | Throws an exception if the specified string is null, undefined, or an empty string. |
-|[`isNotNullOrUndefined(value,variableName)`](isnotnullorundefined-validate.md)     | `public, static` | `void` | Throws an exception if the specified value is null or undefined. |
-|[`isTrue(value,variableName)`](istrue-validate.md)     | `public, static` | `void` | Throws an exception if the specified value is not true. |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/verbose-log.md b/reference/spfx/sp-core-library/class/verbose-log.md
deleted file mode 100644
index c560cf8e0f..0000000000
--- a/reference/spfx/sp-core-library/class/verbose-log.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# verbose(source,message,scope)
-
-
-
-Logs a verbose message
-
-**Signature:** _public static verbose(source: string, message: string, scope?: [ServiceScope](../../sp-core-library/class/servicescope.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `source`    | `string` | the source from where the message is logged, e.g., the class name. The source provides context information for the logged message. If the source's length is more than 20, only the first 20 characters are kept. |
-| `message`    | `string` | the message to be logged If the message's length is more than 100, only the first 100 characters are kept. |
-| `scope`    | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | _Optional._ the service scope that the source uses. A service scope can provide more context information (e.g., web part information) to the logged message. |
-
-
diff --git a/reference/spfx/sp-core-library/class/version.md b/reference/spfx/sp-core-library/class/version.md
deleted file mode 100644
index 41735436ae..0000000000
--- a/reference/spfx/sp-core-library/class/version.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Version class
-
-
-
-
-
-
-
-This class represents versions that follow the string format of MAJOR.MINOR[.PATCH[.REVISION]] where MAJOR, MINOR, PATCH and REVISION are integers. PATCH and REVISION are optional. Leading zeros are allowed, but have no meaning in comparisons. Examples: 1.0, 1.0.0, 1.0.0.0, 1.01, 01.02.03, 001.002.003.004
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`major`     | `public` | `number` | _Read-only._ The first number in the version string indicating the major version |
-|`minor`     | `public` | `number` | _Read-only._ The second number in the version string indicating the minor version |
-|`patch`     | `public` | `number `,` undefined` | _Read-only._ The thrid number in the version string indicating the patch number in a semantic version or the build number in a .NET System.Version class Set to undefined if the third number does not exist |
-|`revision`     | `public` | `number `,` undefined` | _Read-only._ The fourth number in the version string indicating the revision number Set to undefined if the fourth number does not exist |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`compare(v1,v2)`](compare-version.md)     | `public, static` | `number` | Compares two Version classes |
-|[`equals(compareWith)`](equals-version.md)     | `public` | `boolean` | Checks if this version is equal to the input parameter. Missing patch number is treated as zero. Examples: 1.0.0 equals 1.0.0 -> true 2.0.1 equals 2.0.0 -> false 3.0 equals 3.0.0 -> true 04.01 equals 4.1 -> true |
-|[`greaterThan(compareWith)`](greaterthan-version.md)     | `public` | `boolean` | Checks if this version is greater (i.e. newer) than the input parameter. Missing patch number is treated as zero Examples: 1.0.0 greaterThan 0.0.9 -> true 2.0 greaterThan 2.0.0 -> false 3.0.1 greaterThan 3.0 -> true |
-|[`isValid(versionString)`](isvalid-version.md)     | `public, static` | `boolean` | Indicates whether a version string is valid |
-|[`lessThan(compareWith)`](lessthan-version.md)     | `public` | `boolean` | Checks if this version is less (i.e. older) than the input parameter. Missing patch number is treated as zero Examples: 0.9.9 lessThan 1.0.0 -> true 2.0 lessThan 2.0.0 -> false 3.0 lessThan 3.0.1 -> true 04.01 lessThan 4.1 -> false |
-|[`parse(versionString)`](parse-version.md)     | `public, static` | [`Version`](../../sp-core-library/class/version.md) | Constructs a new Version instance using the version string. tryParse validates the input version string and throws error if it is invalid |
-|[`satisfies(compareWith)`](satisfies-version.md)     | `public` | `boolean` | Checks if this version satisfies the input parameter, therefore it's backwards compatible. They have to share the same major version, and the input parameter must be an equal or more recent version. Examples: 1.0.0 satisfies 1.0.0 -> true 1.1.0 satisfies 1.0.0 -> true 2.0.0 satisfies 1.0.0 -> false 1.0.0 satisfies 1.1.0 -> false |
-|[`toString()`](tostring-version.md)     | `public` | `string` | Object.prototype.toString override The version string in MAJOR.MINOR[.PATCH[.REVISION]] |
-|[`tryParse(versionString)`](tryparse-version.md)     | `public, static` | [`Version `](../../sp-core-library/class/version.md),` undefined` | Tries to construct a new Version instance using the version string. Returns undefined if not successful. |
-
-
-
-
-
diff --git a/reference/spfx/sp-core-library/class/warn-log.md b/reference/spfx/sp-core-library/class/warn-log.md
deleted file mode 100644
index 3125d7ca32..0000000000
--- a/reference/spfx/sp-core-library/class/warn-log.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# warn(source,message,scope)
-
-
-
-Logs a warning
-
-**Signature:** _public static warn(source: string, message: string, scope?: [ServiceScope](../../sp-core-library/class/servicescope.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `source`    | `string` | the source from where the message is logged, e.g., the class name. The source provides context information for the logged message. If the source's length is more than 20, only the first 20 characters are kept. |
-| `message`    | `string` | the message to be logged If the message's length is more than 100, only the first 100 characters are kept. |
-| `scope`    | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | _Optional._ the service scope that the source uses. A service scope can provide more context information (e.g., web part information) to the logged message. |
-
-
diff --git a/reference/spfx/sp-core-library/class/whenfinished-servicescope.md b/reference/spfx/sp-core-library/class/whenfinished-servicescope.md
deleted file mode 100644
index 0dbdabf534..0000000000
--- a/reference/spfx/sp-core-library/class/whenfinished-servicescope.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# whenFinished(callback)
-
-
-
-It is an error to call ServiceScope.consume() before finish() has been called. The most reliable way to protect your component against this error is to perform the consume() calls inside a whenFinished() callback. If the service scope is already finished, then the callback will be executed immediately; otherwise, it will be executed later when the scope is finished.
-
-**Signature:** _public whenFinished(callback: () => void): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `callback`    | `() => void` | A block of code that needs to call ServiceScope.consume() |
-
-
diff --git a/reference/spfx/sp-core-library/enum/displaymode.md b/reference/spfx/sp-core-library/enum/displaymode.md
deleted file mode 100644
index 444b9b2397..0000000000
--- a/reference/spfx/sp-core-library/enum/displaymode.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# DisplayMode enumeration
-DisplayMode indicates the mode in which a page and/or its contents (e.g. text and web parts) are dislayed.
-
-| Member	   | Description|
-|:-------------|:-------|
-|`Edit` :=2      |  |
-|`Read` :=1      |  |
diff --git a/reference/spfx/sp-core-library/enum/environmenttype.md b/reference/spfx/sp-core-library/enum/environmenttype.md
deleted file mode 100644
index 12c7cae4d0..0000000000
--- a/reference/spfx/sp-core-library/enum/environmenttype.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# EnvironmentType enumeration
-An enum that describes which type of enviroment the framework is running in.
-
-| Member	   | Description|
-|:-------------|:-------|
-|`ClassicSharePoint`       | Indicates that the framework was loaded from a classic server-rendered SharePoint page |
-|`Local`       | Represents the scenario of the framework hosted on a localhost server, which typically cannot access any SharePoint REST APIs. Example: A developer uses gulp serve command to test their changes in their browser of choice. |
-|`SharePoint`       | Indicates that the framework was loaded by a client-rendered SharePoint page |
-|`Test`       | Represents the scenario of the framework hosted in a unit/integration test. Example: A developer running a unit test to verify changes to their web part. |
diff --git a/reference/spfx/sp-core-library/interface/generate-irandomnumbergenerator.md b/reference/spfx/sp-core-library/interface/generate-irandomnumbergenerator.md
deleted file mode 100644
index ab8c93c6ad..0000000000
--- a/reference/spfx/sp-core-library/interface/generate-irandomnumbergenerator.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# generate()
-
-
-
-Returns a psuedorandom number between 0 (inclusive) and 1 (exclusive), following the contract of Math.random().
-
-**Signature:** _generate(): number;_
-
-**Returns**: `number`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/interface/getdate-itimeprovider.md b/reference/spfx/sp-core-library/interface/getdate-itimeprovider.md
deleted file mode 100644
index 8ba2fd43eb..0000000000
--- a/reference/spfx/sp-core-library/interface/getdate-itimeprovider.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getDate()
-
-
-
-Returns the current date/time.
-
-**Signature:** _getDate(): Date;_
-
-**Returns**: `Date`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/interface/gettimestamp-itimeprovider.md b/reference/spfx/sp-core-library/interface/gettimestamp-itimeprovider.md
deleted file mode 100644
index a307cc1ae4..0000000000
--- a/reference/spfx/sp-core-library/interface/gettimestamp-itimeprovider.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getTimestamp()
-
-
-
-Returns a DOMHighResTimeStamp timing measurement, as defined by the standard performance.now() API.
-
-**Signature:** _getTimestamp(): number;_
-
-**Returns**: `number`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-core-library/interface/irandomnumbergenerator.md b/reference/spfx/sp-core-library/interface/irandomnumbergenerator.md
deleted file mode 100644
index 754d151fec..0000000000
--- a/reference/spfx/sp-core-library/interface/irandomnumbergenerator.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IRandomNumberGenerator interface
-
-
-
-
-
-
-
-This is a ServiceScope interface that enables unit tests to provide a deterministic source of pseudorandom numbers.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`generate()`](generate-irandomnumbergenerator.md)      | `number` | Returns a psuedorandom number between 0 (inclusive) and 1 (exclusive), following the contract of Math.random(). |
-
-
-
-
diff --git a/reference/spfx/sp-core-library/interface/iservicecollection.md b/reference/spfx/sp-core-library/interface/iservicecollection.md
deleted file mode 100644
index 41e563a60f..0000000000
--- a/reference/spfx/sp-core-library/interface/iservicecollection.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# IServiceCollection interface
-
-
-
-
-
-
-
-A shorthand pattern for extracting well-known services from a ServiceScope.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`serviceScope`      | [`ServiceScope`](../../sp-core-library/class/servicescope.md) | Returns the underlying ServiceScope that the members belong to. |
-
-
-
-
-
-
-### Remarks
-
-Reusable library components typically declare their service dependencies by calling ServiceScope.consume() using the corresponding ServiceKey for each service. For application business logic or small-sized projects, this formalism may be unnecessary and would increase the learning curve for developers. As a lightweight alternative, the IServiceCollection pattern allows the common services for a particular scenario to be passed around as a simple, convenient collection. For example, a widget feature might introduce an interface like this: interface IWidgetServiceCollection extends IServiceCollection { spHttpClient: SPHttpClient; widgetManager: IWidgetManager; } Then the Widget class might initialize a "services" property, like this: class Widget { private _services: IWidgetServiceCollection; constructor(serviceScope: ServiceScope) { serviceScope.whenFinished(() => { this._services = { serviceScope, spHttpClient: serviceScope.consume(SPHttpClient.serviceKey), widgetManager: serviceScope.consume(WidgetManager.ServiceKey), }; }); } public get services(): IWidgetServiceCollection { return this._services; } } For a group of components that all have these dependencies, this "services" object can be passed around instead of the abstract ServiceScope. This enables direct references such as services.widgetManager, services.spHttpClient, etc. For atypical dependencies, the services.serviceScope is still available for use. IMPORTANT: To keep the pattern clean and understandable, IServiceCollection should NOT be extended with any additional members that are not ServiceScope services.
-
diff --git a/reference/spfx/sp-core-library/interface/itimeprovider.md b/reference/spfx/sp-core-library/interface/itimeprovider.md
deleted file mode 100644
index 2a3e3a43c3..0000000000
--- a/reference/spfx/sp-core-library/interface/itimeprovider.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# ITimeProvider interface
-
-
-
-
-
-
-
-This is a ServiceScope interface that enables unit tests to simulate the system clock.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`getDate()`](getdate-itimeprovider.md)      | `Date` | Returns the current date/time. |
-|[`getTimestamp()`](gettimestamp-itimeprovider.md)      | `number` | Returns a DOMHighResTimeStamp timing measurement, as defined by the standard performance.now() API. |
-
-
-
-
diff --git a/reference/spfx/sp-dialog-module.md b/reference/spfx/sp-dialog-module.md
deleted file mode 100644
index 831d247c11..0000000000
--- a/reference/spfx/sp-dialog-module.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# sp-dialog package
-
-SharePoint Framework support for accessibility features such as keyboard navigation and screen reader
-
-
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`BaseDialog`](./sp-dialog/class/basedialog.md)     | The base class for implementing dialogs in SharePoint Framework. This provides a supported way for showing dialogs to the user inside SharePoint Framework components. |
-| [`Dialog`](./sp-dialog/class/dialog.md)     | Static Dialog class to provide API for showing static dialogs such as alert and prompt |
-| [`SecondaryDialog`](./sp-dialog/class/secondarydialog.md)     | This class handles calls to show a secondary dialog. It's only available by calling this.secondaryManager inside a dialog. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IAlertOptions`](./sp-dialog/interface/ialertoptions.md)   | Options for showing an alert dialog  |
-| [`IDialogConfiguration`](./sp-dialog/interface/idialogconfiguration.md)   | The interface for dialog configuration  |
-| [`IDialogShowingOptions`](./sp-dialog/interface/idialogshowingoptions.md)   | Options for showing a dialog  |
-| [`IPromptOptions`](./sp-dialog/interface/ipromptoptions.md)   | Options for showing an prompt dialog  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-dialog/class/alert-dialog.md b/reference/spfx/sp-dialog/class/alert-dialog.md
deleted file mode 100644
index a9f96ff59b..0000000000
--- a/reference/spfx/sp-dialog/class/alert-dialog.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# alert(message)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Alerts a message to the user with a user-friendly interface. Calling this method sends a request to application to show the alert dialog.
-
-**Signature:** _public static alert(message: string, options?: [IAlertOptions](../../sp-dialog/interface/ialertoptions.md)): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `message`    | `string` | The message to alert |
-
-
-### Remarks
-
-There might be a delay until the dialog is approved and shown by the application, for example, if there is another dialog currently being shown. The returned promise resolves when the dialog is successfully shown and closed. The promise rejects if the application rejects the request for any reason.
-
diff --git a/reference/spfx/sp-dialog/class/alert-secondarydialog.md b/reference/spfx/sp-dialog/class/alert-secondarydialog.md
deleted file mode 100644
index 7cf8129a48..0000000000
--- a/reference/spfx/sp-dialog/class/alert-secondarydialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# alert(options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Similar to
-
-**Signature:** _public alert(message: string, options?: [IAlertOptions](../../sp-dialog/interface/ialertoptions.md)): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `options`    | [`IAlertOptions`](../../sp-dialog/interface/ialertoptions.md) | _Optional._ Dialog showing options |
-
-
diff --git a/reference/spfx/sp-dialog/class/basedialog.md b/reference/spfx/sp-dialog/class/basedialog.md
deleted file mode 100644
index 8394ec7908..0000000000
--- a/reference/spfx/sp-dialog/class/basedialog.md
+++ /dev/null
@@ -1,56 +0,0 @@
-# BaseDialog class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The base class for implementing dialogs in SharePoint Framework. This provides a supported way for showing dialogs to the user inside SharePoint Framework components.
-
-
-## Constructor
-Constructor for the BaseDialog class. It is important to keep the constructor lightweight. Use onOpen() for doing heavy-weight initializations that are needed for rendering the dialog such as resource allocations and asynchronous calls to fetch data. You can use the constructor to set initial parameters of your dialog such as references to resources in your application. The reason for this is that dialogs are usually constructed upon a UI event e.g. a button click, but the dialog may not always be shown right after construction. Keeping the constructor lightweight ensures smooth user experience and avoids doing throw-away work in case the dialog is not shown later e.g. if the framework rejects it. Another benefit of doing this is avoiding memory leaks by doing all the allocations and disposals in symmetric onOpen() and onClose() events. If you allocate unmanaged resources in the constructor, you have a memory leak because there is no guarantee onClose() will get called, and onClose() is your only opportunity to dispose. Example: constructor(cacheReference: any) { super(); this._cache = cacheReference; // This is okay. Keeping a reference to my internal cache. this._cache.refresh(); // This is bad practice. // If you need to refresh the cache (or fetch data) for rendering, do it in onOpen() }
-
-**Signature:** _constructor();_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`domElement`     | `public` | `HTMLElement` | _Read-only._ Use this property to access the container element provided by the framework for rendering. |
-|`isHidden`     | `public` | `boolean` | _Read-only._ If the dialog is visually hidden. This happens when the dialog goes behind a secondary dialog. Note that this is different from closed, because the dialog still has the permission to show and will eventually unhide. This returns false if the dialog is closed. |
-|`isOpen`     | `public` | `boolean` | _Read-only._ If the dialog is visually open. This returns true during onOpen() because there is a visual component. It returns false when the dialog is hidden. |
-|`isSecondary`     | `public` | `boolean` | _Read-only._ If the dialog is a secondary dialog. This means that there is another dialog hidden behind this dialog. |
-|`secondaryDialog`     | `public` | [`SecondaryDialog `](../../sp-dialog/class/secondarydialog.md),` undefined` | _Read-only._ An active dialog is permitted to show a secondary dialog on top of itself. By design, only two layers of dialogs are permitted. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`close()`](close-basedialog.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<void> | Close the dialog. This will void the permission to show for this dialog. Every dialog should have a mechanism to eventually close to avoid blocking the user interface. If called on an inactive dialog it will abort the request to show. |
-|[`getConfig()`](getconfig-basedialog.md)     | `public` | [`IDialogConfiguration`](../../sp-dialog/interface/idialogconfiguration.md) | Optionally, subclasses can override the getConfig() method to customize various configuration settings that affect how a dialog is displayed. |
-|[`onClose()`](onclose-basedialog.md)     | `protected` | `void` | This method is called after the dialog is visually closed and gives an opprotunity for doing clean up. The dialog lifecycle completes after closing and there should be no unmanaged resources left inside the object. Even though the dialog may be revived again for a new lifecycle using show() method, this is considered a whole new lifecycle that should reallocate its own resources. If there are any resources that you would like to keep for multiple lifecycles, consider allocating it outside the dialog object and passing its reference to the dialog constructor. |
-|[`onOpen()`](onopen-basedialog.md)     | `protected` | [`Promise`](../../web-apis/class/promise.md)<void> | This method is called before the render method and can be overridden to make preparations for rendering. The loading indicator is displayed during the lifetime of this method. |
-|[`render()`](render-basedialog.md)     | `protected` | `void` | The render method must be implemented to render the content of the dialog in the conrainer element provided by the framework. Use this.domElement to access this container. The container is inside a modal rendered in the center of the page on top of a dark overlay. |
-|[`show(options)`](show-basedialog.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<void> | Request the framework to show this dialog. |
-
-
-
-
-
-### Remarks
-
-Extend this class to create dialogs for SharePoint Framework. By following the guidelines in implementation, the framework can ensure that the dialogs are shown in a user-friendly manner. While the content of the dialog is controlled by this class by implementing the render method, the framework can decide when to show the dialog and how to render the overlay and modal. The application on the page can also have control on allowing dialogs to show. Refer to the documentation of the individual methods and properties to learn more about how to extend and use this class.
-
diff --git a/reference/spfx/sp-dialog/class/close-basedialog.md b/reference/spfx/sp-dialog/class/close-basedialog.md
deleted file mode 100644
index 388926d6aa..0000000000
--- a/reference/spfx/sp-dialog/class/close-basedialog.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# close()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Close the dialog. This will void the permission to show for this dialog. Every dialog should have a mechanism to eventually close to avoid blocking the user interface. If called on an inactive dialog it will abort the request to show.
-
-**Signature:** _public close(): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-A promise that resolves when the dialog is visually closed, or if it was already closed
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-dialog/class/dialog.md b/reference/spfx/sp-dialog/class/dialog.md
deleted file mode 100644
index 2d0e791b79..0000000000
--- a/reference/spfx/sp-dialog/class/dialog.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Dialog class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Static Dialog class to provide API for showing static dialogs such as alert and prompt
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`alert(message)`](alert-dialog.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<void> | Alerts a message to the user with a user-friendly interface. Calling this method sends a request to application to show the alert dialog. |
-|[`prompt(message,defaultValue)`](prompt-dialog.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<string ,` undefined>` | Prompts the user for a string value with a user-friendly interface. Calling this method sends a request to application to show the dialog. |
-
-
-
-
-
diff --git a/reference/spfx/sp-dialog/class/getconfig-basedialog.md b/reference/spfx/sp-dialog/class/getconfig-basedialog.md
deleted file mode 100644
index 49d5e1715b..0000000000
--- a/reference/spfx/sp-dialog/class/getconfig-basedialog.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getConfig()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Optionally, subclasses can override the getConfig() method to customize various configuration settings that affect how a dialog is displayed.
-
-**Signature:** _@virtual public getConfig(): [IDialogConfiguration](../../sp-dialog/interface/idialogconfiguration.md);_
-
-**Returns**: [`IDialogConfiguration`](../../sp-dialog/interface/idialogconfiguration.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-dialog/class/onclose-basedialog.md b/reference/spfx/sp-dialog/class/onclose-basedialog.md
deleted file mode 100644
index 725ffd8f97..0000000000
--- a/reference/spfx/sp-dialog/class/onclose-basedialog.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onClose()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This method is called after the dialog is visually closed and gives an opprotunity for doing clean up. The dialog lifecycle completes after closing and there should be no unmanaged resources left inside the object. Even though the dialog may be revived again for a new lifecycle using show() method, this is considered a whole new lifecycle that should reallocate its own resources. If there are any resources that you would like to keep for multiple lifecycles, consider allocating it outside the dialog object and passing its reference to the dialog constructor.
-
-**Signature:** _@virtual protected onClose(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-dialog/class/onopen-basedialog.md b/reference/spfx/sp-dialog/class/onopen-basedialog.md
deleted file mode 100644
index cd13c83e4f..0000000000
--- a/reference/spfx/sp-dialog/class/onopen-basedialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# onOpen()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This method is called before the render method and can be overridden to make preparations for rendering. The loading indicator is displayed during the lifetime of this method.
-
-**Signature:** _@virtual protected onOpen(): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-A promise that resolves when the operations are done and the dialog is ready to render. If the promise is rejected, the dialog will not be rendered and onClose() will not be called.
-
-#### Parameters
-None
-
-
-### Remarks
-
-All resource allocations in onOpen() should be properly disposed in onClose() to a avoid memory leak.
-
diff --git a/reference/spfx/sp-dialog/class/prompt-dialog.md b/reference/spfx/sp-dialog/class/prompt-dialog.md
deleted file mode 100644
index b223fc455e..0000000000
--- a/reference/spfx/sp-dialog/class/prompt-dialog.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# prompt(message,defaultValue)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Prompts the user for a string value with a user-friendly interface. Calling this method sends a request to application to show the dialog.
-
-**Signature:** _public static prompt(message: string, options?: [IPromptOptions](../../sp-dialog/interface/ipromptoptions.md)): [Promise](../../web-apis/class/promise.md)<string | undefined>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<string ,` undefined>`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `message`    | `string` | The message for prompt dialog |
-| `defaultValue`    |  | The default value for the input text field |
-
-
-### Remarks
-
-There might be a delay until the dialog is approved and shown by the application, for example, if there is another dialog currently being shown. The returned promise resolves when the dialog is successfully shown and closed. The promise rejects if the application rejects the request for any reason.
-
diff --git a/reference/spfx/sp-dialog/class/prompt-secondarydialog.md b/reference/spfx/sp-dialog/class/prompt-secondarydialog.md
deleted file mode 100644
index 8aea67e32b..0000000000
--- a/reference/spfx/sp-dialog/class/prompt-secondarydialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# prompt(options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Similar to
-
-**Signature:** _public prompt(message: string, options?: [IPromptOptions](../../sp-dialog/interface/ipromptoptions.md)): [Promise](../../web-apis/class/promise.md)<string>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<string>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `options`    | [`IPromptOptions`](../../sp-dialog/interface/ipromptoptions.md) | _Optional._ Dialog showing options |
-
-
diff --git a/reference/spfx/sp-dialog/class/render-basedialog.md b/reference/spfx/sp-dialog/class/render-basedialog.md
deleted file mode 100644
index 1c4eace5ae..0000000000
--- a/reference/spfx/sp-dialog/class/render-basedialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# render()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The render method must be implemented to render the content of the dialog in the conrainer element provided by the framework. Use this.domElement to access this container. The container is inside a modal rendered in the center of the page on top of a dark overlay.
-
-**Signature:** _protected abstract render(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
-### Remarks
-
-The render method is called once after the modal element is created and opened. It is recommended to use onOpen() for doing non-UI preperations for your rendering that might take a long time. This will ensure that the framework can show a friendly UI such as a spinner to let the user know that the dialog is being prepared. If you choose to do your initialization or other costly operations inside render method, make sure to have a friendly UI so the user is informed about the state of your dialog. Otherwise, an empty element is shown to the user which is a bad user experience practice.
-
diff --git a/reference/spfx/sp-dialog/class/secondarydialog.md b/reference/spfx/sp-dialog/class/secondarydialog.md
deleted file mode 100644
index 7bfa386d4b..0000000000
--- a/reference/spfx/sp-dialog/class/secondarydialog.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# SecondaryDialog class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This class handles calls to show a secondary dialog. It's only available by calling this.secondaryManager inside a dialog.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`alert(options)`](alert-secondarydialog.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<void> | Similar to |
-|[`prompt(options)`](prompt-secondarydialog.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<string> | Similar to |
-|[`show(options)`](show-secondarydialog.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<void> | Similar to |
-
-
-
-
-
-### Remarks
-
-Secondary dialogs do not need to request permission from dialog manager, because the primary dialog already has permission. Therefore, the secondary dialog will be immediately shown. This causes the primary dialog to hide until the secondary dialog is closed. There can be only one secondary dialog at a time. Additional requests to show more secondary dialogs are rejected.
-
diff --git a/reference/spfx/sp-dialog/class/show-basedialog.md b/reference/spfx/sp-dialog/class/show-basedialog.md
deleted file mode 100644
index 58f8c549f8..0000000000
--- a/reference/spfx/sp-dialog/class/show-basedialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# show(options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Request the framework to show this dialog.
-
-**Signature:** _public show(options?: [IDialogShowingOptions](../../sp-dialog/interface/idialogshowingoptions.md)): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-A promise that resolves once the dialog is successfully closed (after being shown). The promise rejects if the request is rejected or aborted.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `options`    | [`IDialogShowingOptions`](../../sp-dialog/interface/idialogshowingoptions.md) | _Optional._ Dialog showing options |
-
-
diff --git a/reference/spfx/sp-dialog/class/show-secondarydialog.md b/reference/spfx/sp-dialog/class/show-secondarydialog.md
deleted file mode 100644
index 4ef317bccd..0000000000
--- a/reference/spfx/sp-dialog/class/show-secondarydialog.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# show(options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Similar to
-
-**Signature:** _public show(dialog: [BaseDialog](../../sp-dialog/class/basedialog.md), options?: [IDialogShowingOptions](../../sp-dialog/interface/idialogshowingoptions.md)): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `options`    | [`IDialogShowingOptions`](../../sp-dialog/interface/idialogshowingoptions.md) | _Optional._ Dialog showing options |
-
-
diff --git a/reference/spfx/sp-dialog/interface/ialertoptions.md b/reference/spfx/sp-dialog/interface/ialertoptions.md
deleted file mode 100644
index 678d858607..0000000000
--- a/reference/spfx/sp-dialog/interface/ialertoptions.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# IAlertOptions interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Options for showing an alert dialog
-
-
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-dialog/interface/idialogconfiguration.md b/reference/spfx/sp-dialog/interface/idialogconfiguration.md
deleted file mode 100644
index 9724ed2ec7..0000000000
--- a/reference/spfx/sp-dialog/interface/idialogconfiguration.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IDialogConfiguration interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The interface for dialog configuration
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`isBlocking`      | `boolean` | Whether the dialog can be closed by clicking outside the dialog (on the overlay). |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-dialog/interface/idialogshowingoptions.md b/reference/spfx/sp-dialog/interface/idialogshowingoptions.md
deleted file mode 100644
index 76ad0c791f..0000000000
--- a/reference/spfx/sp-dialog/interface/idialogshowingoptions.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IDialogShowingOptions interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Options for showing a dialog
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`shouldAbort`      | `() => boolean` | Provide this callback if there is a case when you want to abort showing the dialog before it's approved by the framework. For example, you can check if a long time has passed since the request was made or the the component requesting the dialog is disposed and you don't want to show the dialog anymore. It is important to keep this callback lightweight so the framework can resolve it quickly and the user interface does not have to wait a long time for it. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-dialog/interface/ipromptoptions.md b/reference/spfx/sp-dialog/interface/ipromptoptions.md
deleted file mode 100644
index 8da363a4a1..0000000000
--- a/reference/spfx/sp-dialog/interface/ipromptoptions.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IPromptOptions interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Options for showing an prompt dialog
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`defaultValue`      | `string` | The default value for the input text field of prompt dialog |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-extension-base-module.md b/reference/spfx/sp-extension-base-module.md
deleted file mode 100644
index b901a67972..0000000000
--- a/reference/spfx/sp-extension-base-module.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# sp-extension-base package
-
-
-
-
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`BaseExtension`](./sp-extension-base/class/baseextension.md)     | The base class for all client-side extensions. |
-| [`ExtensionContext`](./sp-extension-base/class/extensioncontext.md)     | The base class for context objects for client-side extensions. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-extension-base/class/baseextension.md b/reference/spfx/sp-extension-base/class/baseextension.md
deleted file mode 100644
index 81e3c7ddc7..0000000000
--- a/reference/spfx/sp-extension-base/class/baseextension.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# BaseExtension <TProperties> class
-
-
-
-_Type parameters: `<TProperties>`_
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The base class for all client-side extensions.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`context`     | `public` | [`ExtensionContext`](../../sp-extension-base/class/extensioncontext.md) | Use context object to access common services and state associated with the component. |
-|`properties`     | `public` | `TProperties` | _Read-only._ Extension properties is a JavaScript object that are passed in by the application that initializes the extension. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`onDispose()`](ondispose-baseextension.md)     | `public` | `void` | This event hook is called immediately before the extension stops being used. It provides an opportunity to release any associated resources, cancel any outstanding requests, etc. |
-|[`onInit()`](oninit-baseextension.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<void> | This event hook is called when the client-side extension is first activated on the page. |
-
-
-
-
-
-### Remarks
-
-The constructor for this class is marked as internal; third party code should not inherit directly from this base class.
-
diff --git a/reference/spfx/sp-extension-base/class/extensioncontext.md b/reference/spfx/sp-extension-base/class/extensioncontext.md
deleted file mode 100644
index 489bb46a7d..0000000000
--- a/reference/spfx/sp-extension-base/class/extensioncontext.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# ExtensionContext class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The base class for context objects for client-side extensions.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`graphHttpClient`     | `public` | [`GraphHttpClient`](../../sp-http/class/graphhttpclient.md) | _Read-only._ The instance of GraphHttpClient created for this instance of extension |
-|`httpClient`     | `public` | [`HttpClient`](../../sp-http/class/httpclient.md) | _Read-only._ The instance of HttpClient created for this instance of extension |
-|`spHttpClient`     | `public` | [`SPHttpClient`](../../sp-http/class/sphttpclient.md) | _Read-only._ The instance of SpHttpClient created for this instance of extension |
-
-
-
-
-
-
-
-### Remarks
-
-The constructor for this class is marked as internal; third party code should not inherit directly from this base class.
-
diff --git a/reference/spfx/sp-extension-base/class/ondispose-baseextension.md b/reference/spfx/sp-extension-base/class/ondispose-baseextension.md
deleted file mode 100644
index cc93af6d34..0000000000
--- a/reference/spfx/sp-extension-base/class/ondispose-baseextension.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onDispose()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This event hook is called immediately before the extension stops being used. It provides an opportunity to release any associated resources, cancel any outstanding requests, etc.
-
-**Signature:** _@virtual public onDispose(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-extension-base/class/oninit-baseextension.md b/reference/spfx/sp-extension-base/class/oninit-baseextension.md
deleted file mode 100644
index bc437b74fc..0000000000
--- a/reference/spfx/sp-extension-base/class/oninit-baseextension.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onInit()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This event hook is called when the client-side extension is first activated on the page.
-
-**Signature:** _@virtual public onInit(): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http-module.md b/reference/spfx/sp-http-module.md
deleted file mode 100644
index fa08cdab93..0000000000
--- a/reference/spfx/sp-http-module.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# sp-http package
-
-Base communication layer for the SharePoint Framework
-
-This package defines the base communication layer for the SharePoint Framework. For REST calls, it handles authentication, logging, diagnostics, and batching. It also simplifies requests by adding default headers that follow the recommended best practices.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`GraphClientResponse`](./sp-http/class/graphclientresponse.md)     | The Response subclass returned by methods such as GraphHttpClient.fetch(). |
-| [`GraphHttpClient`](./sp-http/class/graphhttpclient.md)     | GraphHttpClient is used to perform REST calls against Microsoft Graph. It adds default headers and collects telemetry that helps the service to monitor the performance of an application. https://developer.microsoft.com/en-us/graph/ For communicating with non-Graph services, use the HttpClient or SPHttpClient class instead. |
-| [`GraphHttpClientConfiguration`](./sp-http/class/graphhttpclientconfiguration.md)     | The GraphHttpClientConfiguration object provides a set of switches for enabling/disabling various features of the GraphHttpClient class. Normally these switches are set (e.g. when calling GraphHttpClient.fetch()) by providing one of the predefined defaults from GraphHttpClientConfigurations, however switches can also be changed via the GraphHttpClientConfiguration.overrideWith() method. |
-| [`HttpClient`](./sp-http/class/httpclient.md)     | HttpClient implements a basic set of features for performing REST operations. The subclass SPHttpClient extends this basic functionality with SharePoint-specific enhancements. |
-| [`HttpClientConfiguration`](./sp-http/class/httpclientconfiguration.md)     | The HttpClientConfiguration object provides a set of switches for enabling/disabling various features of the HttpClient class. Normally these switches are set (e.g. when calling HttpClient.fetch()) by providing one of the predefined defaults from HttpClientConfigurations, however switches can also be changed via the HttpClientConfiguration.overrideWith() method. |
-| [`HttpClientResponse`](./sp-http/class/httpclientresponse.md)     | The Response subclass returned by methods such as HttpClient.fetch(). |
-| [`ODataVersion`](./sp-http/class/odataversion.md)     | Represents supported version of the 'OData-Version' header, which is part of the Open Data Protocol standard. |
-| [`SPHttpClient`](./sp-http/class/sphttpclient.md)     | SPHttpClient is used to perform REST calls against SharePoint. It adds default headers, manages the digest needed for writes, and collects telemetry that helps the service to monitor the performance of an application. For communicating with non-SharePoint services, use the HttpClient class instead. |
-| [`SPHttpClientCommonConfiguration`](./sp-http/class/sphttpclientcommonconfiguration.md)     | Common base class for SPHttpClientConfiguration and SPHttpClientBatchConfiguration. |
-| [`SPHttpClientConfiguration`](./sp-http/class/sphttpclientconfiguration.md)     | The SPHttpClientConfiguration object provides a set of switches for enabling/disabling various features of the SPHttpClient class. Normally these switches are set (e.g. when calling SPHttpClient.fetch()) by providing one of the predefined defaults from SPHttpClientConfigurations, however switches can also be changed via the SPHttpClientConfiguration.overrideWith() method. |
-| [`SPHttpClientResponse`](./sp-http/class/sphttpclientresponse.md)     | The Response subclass returned by methods such as SPHttpClient.fetch(). |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IGraphHttpClientConfiguration`](./sp-http/interface/igraphhttpclientconfiguration.md)   | Flags interface for GraphHttpClientCommonConfiguration  |
-| [`IGraphHttpClientConfigurations`](./sp-http/interface/igraphhttpclientconfigurations.md)   | This interface provides standard predefined GraphHttpClientConfiguration objects for use with the GraphHttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)  |
-| [`IGraphHttpClientOptions`](./sp-http/interface/igraphhttpclientoptions.md)   | This interface defines the options for the GraphHttpClient operations such as get(), post(), fetch(), etc. It is based on the WHATWG API standard parameters that are documented here: https://fetch.spec.whatwg.org/  |
-| [`IHttpClientConfiguration`](./sp-http/interface/ihttpclientconfiguration.md)   | Flags interface for HttpClientConfiguration.  |
-| [`IHttpClientConfigurations`](./sp-http/interface/ihttpclientconfigurations.md)   | This interface provides standard predefined HttpClientConfiguration objects for use with the HttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)  |
-| [`IHttpClientOptions`](./sp-http/interface/ihttpclientoptions.md)   | This interface defines the options for the HttpClient operations such as get(), post(), fetch(), etc. It is based on the whatwg API standard parameters that are documented here: https://fetch.spec.whatwg.org/  |
-| [`ISPHttpClientCommonConfiguration`](./sp-http/interface/isphttpclientcommonconfiguration.md)   | Flags interface for SPHttpClientCommonConfiguration  |
-| [`ISPHttpClientConfiguration`](./sp-http/interface/isphttpclientconfiguration.md)   | Flags interface for SPHttpClientConfiguration.  |
-| [`ISPHttpClientConfigurations`](./sp-http/interface/isphttpclientconfigurations.md)   | This interface provides standard predefined SPHttpClientConfiguration objects for use with the SPHttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)  |
-| [`ISPHttpClientOptions`](./sp-http/interface/isphttpclientoptions.md)   | This interface defines the options for the SPHttpClient operations such as get(), post(), fetch(), etc. It is based on the WHATWG API standard parameters that are documented here: https://fetch.spec.whatwg.org/  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/arraybuffer-httpclientresponse.md b/reference/spfx/sp-http/class/arraybuffer-httpclientresponse.md
deleted file mode 100644
index b5fa2a47ef..0000000000
--- a/reference/spfx/sp-http/class/arraybuffer-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# arrayBuffer()
-
-
-
-See documentation for whatwg-fetch:Body.arrayBuffer
-
-**Signature:** _public arrayBuffer(): [Promise](../../web-apis/class/promise.md)<ArrayBuffer>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<ArrayBuffer>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/beginbatch-sphttpclient.md b/reference/spfx/sp-http/class/beginbatch-sphttpclient.md
deleted file mode 100644
index 627c089b06..0000000000
--- a/reference/spfx/sp-http/class/beginbatch-sphttpclient.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# beginBatch()
-
-
-
-Begins an ODATA batch, which allows multiple REST queries to be bundled into a single web request.
-
-**Signature:** _public beginBatch(batchCreationOptions?: ISPHttpClientBatchCreationOptions): SPHttpClientBatch;_
-
-**Returns**: `SPHttpClientBatch`
-
-
-
-a promise that will return the result
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/blob-httpclientresponse.md b/reference/spfx/sp-http/class/blob-httpclientresponse.md
deleted file mode 100644
index be0cd1a3cb..0000000000
--- a/reference/spfx/sp-http/class/blob-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# blob()
-
-
-
-See documentation for whatwg-fetch:Body.blob
-
-**Signature:** _public blob(): [Promise](../../web-apis/class/promise.md)<Blob>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<Blob>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/clone-graphclientresponse.md b/reference/spfx/sp-http/class/clone-graphclientresponse.md
deleted file mode 100644
index 4e0aa621c6..0000000000
--- a/reference/spfx/sp-http/class/clone-graphclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clone()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-
-
-**Signature:** _@override public clone(): GraphHttpClientResponse;_
-
-**Returns**: `GraphHttpClientResponse`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/clone-httpclientresponse.md b/reference/spfx/sp-http/class/clone-httpclientresponse.md
deleted file mode 100644
index 370967b572..0000000000
--- a/reference/spfx/sp-http/class/clone-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clone()
-
-
-
-
-
-**Signature:** _@virtual public clone(): [HttpClientResponse](../../sp-http/class/httpclientresponse.md);_
-
-**Returns**: [`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/clone-sphttpclientresponse.md b/reference/spfx/sp-http/class/clone-sphttpclientresponse.md
deleted file mode 100644
index d583c54dc6..0000000000
--- a/reference/spfx/sp-http/class/clone-sphttpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clone()
-
-
-
-
-
-**Signature:** _@override public clone(): [SPHttpClientResponse](../../sp-http/class/sphttpclientresponse.md);_
-
-**Returns**: [`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/fetch-graphhttpclient.md b/reference/spfx/sp-http/class/fetch-graphhttpclient.md
deleted file mode 100644
index 1113d23827..0000000000
--- a/reference/spfx/sp-http/class/fetch-graphhttpclient.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# fetch(url,configuration,options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Generally, the parameters and semantics for HttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/ The GraphHttpClient subclass adds some additional behaviors that are convenient when working with SharePoint ODATA API's (which can be avoided by using HttpClient instead): - Default "Accept" and "Content-Type" headers are added if not explicitly specified.
-
-**Signature:** _public fetch(url: string,
-    configuration: [GraphHttpClientConfiguration](../../sp-http/class/graphhttpclientconfiguration.md),
-    options: [IGraphHttpClientOptions](../../sp-http/interface/igraphhttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<GraphHttpClientResponse>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | The url string should be relative to the graph server. Good: 'v1.0/me/events' Bad: '/v1.0/me/events', 'https://graph.microsoft.com/v1.0/me/events' |
-| `configuration`    | [`GraphHttpClientConfiguration`](../../sp-http/class/graphhttpclientconfiguration.md) | determines the default behavior of GraphHttpClient; normally this should be the latest version number from GraphHttpClientConfigurations |
-| `options`    | [`IGraphHttpClientOptions`](../../sp-http/interface/igraphhttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/fetch-httpclient.md b/reference/spfx/sp-http/class/fetch-httpclient.md
deleted file mode 100644
index 0c211b6efe..0000000000
--- a/reference/spfx/sp-http/class/fetch-httpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# fetch(url,configuration,options)
-
-
-
-Performs a REST service call. Although the SPHttpClient subclass adds additional enhancements, the parameters and semantics for HttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/
-
-**Signature:** _public fetch(url: string, configuration: [HttpClientConfiguration](../../sp-http/class/httpclientconfiguration.md),
-    options: [IHttpClientOptions](../../sp-http/interface/ihttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[HttpClientResponse](../../sp-http/class/httpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md) | determines the default behavior of HttpClient; normally this should be the latest version number from HttpClientConfigurations |
-| `options`    | [`IHttpClientOptions`](../../sp-http/interface/ihttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/fetch-sphttpclient.md b/reference/spfx/sp-http/class/fetch-sphttpclient.md
deleted file mode 100644
index e419e16e46..0000000000
--- a/reference/spfx/sp-http/class/fetch-sphttpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# fetch(url,configuration,options)
-
-
-
-Generally, the parameters and semantics for SPHttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/ The SPHttpClient subclass adds some additional behaviors that are convenient when working with SharePoint ODATA API's (which can be avoided by using HttpClient instead): - Default "Accept" and "Content-Type" headers are added if not explicitly specified. - For write operations, an "X-RequestDigest" header is automatically added - The request digest token is automatically fetched and stored in a cache, with support for preloading For a write operation, SPHttpClient will automatically add the "X-RequestDigest" header, which may need to be obtained by issuing a seperate request such as "https://example.com/sites/sample/_api/contextinfo". Typically the appropriate SPWeb URL can be guessed by looking for a reserved URL segment such as "_api" in the original URL passed to fetch(); if not, use ISPHttpClientOptions.webUrl to specify it explicitly.
-
-**Signature:** _public fetch(url: string, configuration: [SPHttpClientConfiguration](../../sp-http/class/sphttpclientconfiguration.md),
-    options: [ISPHttpClientOptions](../../sp-http/interface/isphttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[SPHttpClientResponse](../../sp-http/class/sphttpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md) | determines the default behavior of SPHttpClient; normally this should be the latest version number from SPHttpClientConfigurations |
-| `options`    | [`ISPHttpClientOptions`](../../sp-http/interface/isphttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/formdata-httpclientresponse.md b/reference/spfx/sp-http/class/formdata-httpclientresponse.md
deleted file mode 100644
index 37bb162100..0000000000
--- a/reference/spfx/sp-http/class/formdata-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# formData()
-
-
-
-See documentation for whatwg-fetch:Body.formData
-
-**Signature:** _public formData(): [Promise](../../web-apis/class/promise.md)<FormData>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<FormData>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/get-graphhttpclient.md b/reference/spfx/sp-http/class/get-graphhttpclient.md
deleted file mode 100644
index 82c0cbff03..0000000000
--- a/reference/spfx/sp-http/class/get-graphhttpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# get(url,configuration,options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Calls fetch(), but sets the method to 'GET'.
-
-**Signature:** _public get(url: string, configuration: [GraphHttpClientConfiguration](../../sp-http/class/graphhttpclientconfiguration.md),
-    options?: [IGraphHttpClientOptions](../../sp-http/interface/igraphhttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<GraphHttpClientResponse>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`GraphHttpClientConfiguration`](../../sp-http/class/graphhttpclientconfiguration.md) | determines the default behavior of GraphHttpClient; normally this should be the latest version number from GraphHttpClientConfigurations |
-| `options`    | [`IGraphHttpClientOptions`](../../sp-http/interface/igraphhttpclientoptions.md) | _Optional._ additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/get-httpclient.md b/reference/spfx/sp-http/class/get-httpclient.md
deleted file mode 100644
index 0448a5711c..0000000000
--- a/reference/spfx/sp-http/class/get-httpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# get(url,configuration,options)
-
-
-
-Calls fetch(), but sets the method to 'GET'.
-
-**Signature:** _public get(url: string, configuration: [HttpClientConfiguration](../../sp-http/class/httpclientconfiguration.md),
-    options?: [IHttpClientOptions](../../sp-http/interface/ihttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[HttpClientResponse](../../sp-http/class/httpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md) | determines the default behavior of HttpClient; normally this should be the latest version number from HttpClientConfigurations |
-| `options`    | [`IHttpClientOptions`](../../sp-http/interface/ihttpclientoptions.md) | _Optional._ additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/get-sphttpclient.md b/reference/spfx/sp-http/class/get-sphttpclient.md
deleted file mode 100644
index 356ff92d09..0000000000
--- a/reference/spfx/sp-http/class/get-sphttpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# get(url,configuration,options)
-
-
-
-Calls fetch(), but sets the method to 'GET'.
-
-**Signature:** _public get(url: string, configuration: [SPHttpClientConfiguration](../../sp-http/class/sphttpclientconfiguration.md),
-    options?: [ISPHttpClientOptions](../../sp-http/interface/isphttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[SPHttpClientResponse](../../sp-http/class/sphttpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md) | determines the default behavior of SPHttpClient; normally this should be the latest version number from SPHttpClientConfigurations |
-| `options`    | [`ISPHttpClientOptions`](../../sp-http/interface/isphttpclientoptions.md) | _Optional._ additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/getweburlfromrequesturl-sphttpclient.md b/reference/spfx/sp-http/class/getweburlfromrequesturl-sphttpclient.md
deleted file mode 100644
index df3ac856a0..0000000000
--- a/reference/spfx/sp-http/class/getweburlfromrequesturl-sphttpclient.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# getWebUrlFromRequestUrl(requestUrl)
-
-
-
-This uses a heuristic to guess the SPWeb URL associated with the provided REST URL. This is necessary for operations such as the X-RequestDigest and ODATA batching, which require POSTing to a separate REST endpoint in order to complete a request. For excample, if the requestUrl is "/sites/site/web/_api/service", the returned URL would be "/sites/site/web". Or if the requestUrl is "http://example.com/_layouts/service", the returned URL would be "http://example.com".
-
-**Signature:** _public static getWebUrlFromRequestUrl(requestUrl: string): string;_
-
-**Returns**: `string`
-
-
-
-the inferred SPWeb URL
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `requestUrl`    | `string` | The URL for a SharePoint REST service |
-
-
diff --git a/reference/spfx/sp-http/class/graphclientresponse.md b/reference/spfx/sp-http/class/graphclientresponse.md
deleted file mode 100644
index 605a2aa0f0..0000000000
--- a/reference/spfx/sp-http/class/graphclientresponse.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# GraphClientResponse class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The Response subclass returned by methods such as GraphHttpClient.fetch().
-
-
-## Constructor
-
-
-**Signature:** _public constructor(response: [Response](../../web-apis/class/response.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`clone()`](clone-graphclientresponse.md)     | `public` | `GraphHttpClientResponse` |  |
-
-
-
-
-
-### Remarks
-
-This is a placeholder. In the future, additional GraphHttpClient-specific functionality may be added to this class.
-
diff --git a/reference/spfx/sp-http/class/graphhttpclient.md b/reference/spfx/sp-http/class/graphhttpclient.md
deleted file mode 100644
index b60ce94e2d..0000000000
--- a/reference/spfx/sp-http/class/graphhttpclient.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# GraphHttpClient class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-GraphHttpClient is used to perform REST calls against Microsoft Graph. It adds default headers and collects telemetry that helps the service to monitor the performance of an application. https://developer.microsoft.com/en-us/graph/ For communicating with non-Graph services, use the HttpClient or SPHttpClient class instead.
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`configurations`     | `public` | [`IGraphHttpClientConfigurations`](../../sp-http/interface/igraphhttpclientconfigurations.md) | The standard predefined GraphHttpClientConfiguration objects for use with the GraphHttpClient class. |
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`GraphHttpClient`](../../sp-http/class/graphhttpclient.md)> | The service key for GraphHttpClient. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`fetch(url,configuration,options)`](fetch-graphhttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse> | Generally, the parameters and semantics for HttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/ The GraphHttpClient subclass adds some additional behaviors that are convenient when working with SharePoint ODATA API's (which can be avoided by using HttpClient instead): - Default "Accept" and "Content-Type" headers are added if not explicitly specified. |
-|[`get(url,configuration,options)`](get-graphhttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse> | Calls fetch(), but sets the method to 'GET'. |
-|[`post(url,configuration,options)`](post-graphhttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse> | Calls fetch(), but sets the method to 'POST'. |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/graphhttpclientconfiguration.md b/reference/spfx/sp-http/class/graphhttpclientconfiguration.md
deleted file mode 100644
index 87ec1293a1..0000000000
--- a/reference/spfx/sp-http/class/graphhttpclientconfiguration.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# GraphHttpClientConfiguration class
-
-_Implements: [`IGraphHttpClientConfiguration`](../../sp-http/interface/igraphhttpclientconfiguration.md)_
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The GraphHttpClientConfiguration object provides a set of switches for enabling/disabling various features of the GraphHttpClient class. Normally these switches are set (e.g. when calling GraphHttpClient.fetch()) by providing one of the predefined defaults from GraphHttpClientConfigurations, however switches can also be changed via the GraphHttpClientConfiguration.overrideWith() method.
-
-
-## Constructor
-Constructs a new instance of GraphHttpClientCommonConfiguration with the specified flags. The default values will be used for any flags that are missing or undefined. If overrideFlags is specified, it takes precedence over flags.
-
-**Signature:** _constructor(flags: [IGraphHttpClientConfiguration](../../sp-http/interface/igraphhttpclientconfiguration.md), overrideFlags?: IGraphHttpClientConfiguration);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`flags`     | `public` | [`IGraphHttpClientConfiguration`](../../sp-http/interface/igraphhttpclientconfiguration.md) |  |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/httpclient.md b/reference/spfx/sp-http/class/httpclient.md
deleted file mode 100644
index d7f6f613b5..0000000000
--- a/reference/spfx/sp-http/class/httpclient.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# HttpClient class
-
-
-
-
-
-
-
-HttpClient implements a basic set of features for performing REST operations. The subclass SPHttpClient extends this basic functionality with SharePoint-specific enhancements.
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`configurations`     | `public` | [`IHttpClientConfigurations`](../../sp-http/interface/ihttpclientconfigurations.md) | The standard predefined HttpClientConfiguration objects for use with the HttpClient class. |
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`HttpClient`](../../sp-http/class/httpclient.md)> | The service key for HttpClient. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`fetch(url,configuration,options)`](fetch-httpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)> | Performs a REST service call. Although the SPHttpClient subclass adds additional enhancements, the parameters and semantics for HttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/ |
-|[`get(url,configuration,options)`](get-httpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)> | Calls fetch(), but sets the method to 'GET'. |
-|[`post(url,configuration,options)`](post-httpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)> | Calls fetch(), but sets the method to 'POST'. |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/httpclientconfiguration.md b/reference/spfx/sp-http/class/httpclientconfiguration.md
deleted file mode 100644
index 6098badc10..0000000000
--- a/reference/spfx/sp-http/class/httpclientconfiguration.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# HttpClientConfiguration class
-
-_Implements: [`IHttpClientConfiguration`](../../sp-http/interface/ihttpclientconfiguration.md)_
-
-
-
-
-
-The HttpClientConfiguration object provides a set of switches for enabling/disabling various features of the HttpClient class. Normally these switches are set (e.g. when calling HttpClient.fetch()) by providing one of the predefined defaults from HttpClientConfigurations, however switches can also be changed via the HttpClientConfiguration.overrideWith() method.
-
-
-## Constructor
-Constructs a new instance of HttpClientConfiguration with the specified flags. The default values will be used for any flags that are missing or undefined. If overrideFlags is specified, it takes precedence over flags. *
-
-**Signature:** _constructor(flags: [IHttpClientConfiguration](../../sp-http/interface/ihttpclientconfiguration.md), overrideFlags?: IHttpClientConfiguration);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`flags`     | `public` | [`IHttpClientConfiguration`](../../sp-http/interface/ihttpclientconfiguration.md) |  |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`initializeFlags()`](initializeflags-httpclientconfiguration.md)     | `protected` | `void` | Child classes should override this method to initialize the flags object. |
-|[`overrideWith()`](overridewith-httpclientconfiguration.md)     | `public` | [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md) | Child classes should override this method to construct the child class type, rather than the base class type. |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/httpclientresponse.md b/reference/spfx/sp-http/class/httpclientresponse.md
deleted file mode 100644
index c622a55606..0000000000
--- a/reference/spfx/sp-http/class/httpclientresponse.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# HttpClientResponse class
-
-_Implements: [`Response`](../../web-apis/class/response.md)_
-
-
-
-
-
-The Response subclass returned by methods such as HttpClient.fetch().
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`bodyUsed`     | `public` | `boolean` | _Read-only._ See documentation for whatwg-fetch:Body.bodyUsed |
-|`headers`     | `public` | [`Headers`](../../web-apis/class/headers.md) | _Read-only._ See documentation for whatwg-fetch:Response.headers |
-|`nativeResponse`     | `public` | [`Response`](../../web-apis/class/response.md) |  |
-|`ok`     | `public` | `boolean` | _Read-only._ See documentation for whatwg-fetch:Response.ok |
-|`status`     | `public` | `number` | _Read-only._ See documentation for whatwg-fetch:Response.status |
-|`statusText`     | `public` | `string` | _Read-only._ See documentation for whatwg-fetch:Response.statusText |
-|`type`     | `public` | `string` | _Read-only._ See documentation for whatwg-fetch:Response.type |
-|`url`     | `public` | `string` | _Read-only._ See documentation for whatwg-fetch:Response.url |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`arrayBuffer()`](arraybuffer-httpclientresponse.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<ArrayBuffer> | See documentation for whatwg-fetch:Body.arrayBuffer |
-|[`blob()`](blob-httpclientresponse.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<Blob> | See documentation for whatwg-fetch:Body.blob |
-|[`clone()`](clone-httpclientresponse.md)     | `public` | [`HttpClientResponse`](../../sp-http/class/httpclientresponse.md) |  |
-|[`formData()`](formdata-httpclientresponse.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<FormData> | See documentation for whatwg-fetch:Body.formData |
-|[`json()`](json-httpclientresponse.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<any> | See documentation for whatwg-fetch:Body.json |
-|[`text()`](text-httpclientresponse.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<string> | See documentation for whatwg-fetch:Body.text |
-
-
-
-
-
-### Remarks
-
-This is a placeholder. In the future, additional HttpClient-specific functionality may be added to this class.
-
diff --git a/reference/spfx/sp-http/class/initializeflags-httpclientconfiguration.md b/reference/spfx/sp-http/class/initializeflags-httpclientconfiguration.md
deleted file mode 100644
index dfe5c8e0b8..0000000000
--- a/reference/spfx/sp-http/class/initializeflags-httpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# initializeFlags()
-
-
-
-Child classes should override this method to initialize the flags object.
-
-**Signature:** _@virtual protected initializeFlags(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/initializeflags-sphttpclientcommonconfiguration.md b/reference/spfx/sp-http/class/initializeflags-sphttpclientcommonconfiguration.md
deleted file mode 100644
index 88f6190755..0000000000
--- a/reference/spfx/sp-http/class/initializeflags-sphttpclientcommonconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# initializeFlags()
-
-
-
-
-
-**Signature:** _@override protected initializeFlags(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/initializeflags-sphttpclientconfiguration.md b/reference/spfx/sp-http/class/initializeflags-sphttpclientconfiguration.md
deleted file mode 100644
index 88f6190755..0000000000
--- a/reference/spfx/sp-http/class/initializeflags-sphttpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# initializeFlags()
-
-
-
-
-
-**Signature:** _@override protected initializeFlags(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/json-httpclientresponse.md b/reference/spfx/sp-http/class/json-httpclientresponse.md
deleted file mode 100644
index 49c73e44cd..0000000000
--- a/reference/spfx/sp-http/class/json-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# json()
-
-
-
-See documentation for whatwg-fetch:Body.json
-
-**Signature:** _public json(): [Promise](../../web-apis/class/promise.md)<any>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<any>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/odataversion.md b/reference/spfx/sp-http/class/odataversion.md
deleted file mode 100644
index 2417743aa9..0000000000
--- a/reference/spfx/sp-http/class/odataversion.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# ODataVersion class
-
-
-
-
-
-
-
-Represents supported version of the 'OData-Version' header, which is part of the Open Data Protocol standard.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`v3`     | `public` | [`ODataVersion`](../../sp-http/class/odataversion.md) | Represents version 3.0 for the 'OData-Version' header |
-|`v4`     | `public` | [`ODataVersion`](../../sp-http/class/odataversion.md) | Represents version 4.0 for the 'OData-Version' header |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`toString()`](tostring-odataversion.md)     | `public` | `string` | Returns the 'OData-Version' value, for example '4.0'. |
-|[`tryParseFromHeaders()`](tryparsefromheaders-odataversion.md)     | `public, static` | [`ODataVersion `](../../sp-http/class/odataversion.md),` undefined` | If the 'OData-Version' header is present, this returns the corresponding ODataVersion constant. An error is thrown if the version number is not supported. If the header is missing, then undefined is returned. |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/overridewith-httpclientconfiguration.md b/reference/spfx/sp-http/class/overridewith-httpclientconfiguration.md
deleted file mode 100644
index 1639f4c01c..0000000000
--- a/reference/spfx/sp-http/class/overridewith-httpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# overrideWith()
-
-
-
-Child classes should override this method to construct the child class type, rather than the base class type.
-
-**Signature:** _@virtual public overrideWith(sourceFlags: [I[HttpClientConfiguration](../../sp-http/class/httpclientconfiguration.md)](../../sp-http/interface/ihttpclientconfiguration.md)): HttpClientConfiguration;_
-
-**Returns**: [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/overridewith-sphttpclientcommonconfiguration.md b/reference/spfx/sp-http/class/overridewith-sphttpclientcommonconfiguration.md
deleted file mode 100644
index 64be30d893..0000000000
--- a/reference/spfx/sp-http/class/overridewith-sphttpclientcommonconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# overrideWith()
-
-
-
-
-
-**Signature:** _@override public overrideWith(sourceFlags: [I[SPHttpClientCommonConfiguration](../../sp-http/class/sphttpclientcommonconfiguration.md)](../../sp-http/interface/isphttpclientcommonconfiguration.md)): SPHttpClientCommonConfiguration;_
-
-**Returns**: [`SPHttpClientCommonConfiguration`](../../sp-http/class/sphttpclientcommonconfiguration.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/overridewith-sphttpclientconfiguration.md b/reference/spfx/sp-http/class/overridewith-sphttpclientconfiguration.md
deleted file mode 100644
index 8f41115a8e..0000000000
--- a/reference/spfx/sp-http/class/overridewith-sphttpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# overrideWith()
-
-
-
-
-
-**Signature:** _@override public overrideWith(sourceFlags: [I[SPHttpClientConfiguration](../../sp-http/class/sphttpclientconfiguration.md)](../../sp-http/interface/isphttpclientconfiguration.md)): SPHttpClientConfiguration;_
-
-**Returns**: [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/post-graphhttpclient.md b/reference/spfx/sp-http/class/post-graphhttpclient.md
deleted file mode 100644
index 5ec177d9da..0000000000
--- a/reference/spfx/sp-http/class/post-graphhttpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# post(url,configuration,options)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Calls fetch(), but sets the method to 'POST'.
-
-**Signature:** _public post(url: string, configuration: [GraphHttpClientConfiguration](../../sp-http/class/graphhttpclientconfiguration.md),
-    options: [IGraphHttpClientOptions](../../sp-http/interface/igraphhttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<GraphHttpClientResponse>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<GraphHttpClientResponse>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`GraphHttpClientConfiguration`](../../sp-http/class/graphhttpclientconfiguration.md) | determines the default behavior of GraphHttpClient; normally this should be the latest version number from GraphHttpClientConfigurations |
-| `options`    | [`IGraphHttpClientOptions`](../../sp-http/interface/igraphhttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/post-httpclient.md b/reference/spfx/sp-http/class/post-httpclient.md
deleted file mode 100644
index 24c14c90ac..0000000000
--- a/reference/spfx/sp-http/class/post-httpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# post(url,configuration,options)
-
-
-
-Calls fetch(), but sets the method to 'POST'.
-
-**Signature:** _public post(url: string, configuration: [HttpClientConfiguration](../../sp-http/class/httpclientconfiguration.md),
-    options: [IHttpClientOptions](../../sp-http/interface/ihttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[HttpClientResponse](../../sp-http/class/httpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`HttpClientResponse`](../../sp-http/class/httpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md) | determines the default behavior of HttpClient; normally this should be the latest version number from HttpClientConfigurations |
-| `options`    | [`IHttpClientOptions`](../../sp-http/interface/ihttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/post-sphttpclient.md b/reference/spfx/sp-http/class/post-sphttpclient.md
deleted file mode 100644
index 4781b057fa..0000000000
--- a/reference/spfx/sp-http/class/post-sphttpclient.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# post(url,configuration,options)
-
-
-
-Calls fetch(), but sets the method to 'POST'.
-
-**Signature:** _public post(url: string, configuration: [SPHttpClientConfiguration](../../sp-http/class/sphttpclientconfiguration.md),
-    options: [ISPHttpClientOptions](../../sp-http/interface/isphttpclientoptions.md)): [Promise](../../web-apis/class/promise.md)<[SPHttpClientResponse](../../sp-http/class/sphttpclientresponse.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)>
-
-
-
-a promise that will return the result
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | the URL to fetch |
-| `configuration`    | [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md) | determines the default behavior of SPHttpClient; normally this should be the latest version number from SPHttpClientConfigurations |
-| `options`    | [`ISPHttpClientOptions`](../../sp-http/interface/isphttpclientoptions.md) | additional options that affect the request |
-
-
diff --git a/reference/spfx/sp-http/class/sphttpclient.md b/reference/spfx/sp-http/class/sphttpclient.md
deleted file mode 100644
index 1eab0392d1..0000000000
--- a/reference/spfx/sp-http/class/sphttpclient.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# SPHttpClient class
-
-
-
-
-
-
-
-SPHttpClient is used to perform REST calls against SharePoint. It adds default headers, manages the digest needed for writes, and collects telemetry that helps the service to monitor the performance of an application. For communicating with non-SharePoint services, use the HttpClient class instead.
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`configurations`     | `public` | [`ISPHttpClientConfigurations`](../../sp-http/interface/isphttpclientconfigurations.md) | The standard predefined SPHttpClientConfiguration objects for use with the SPHttpClient class. |
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`SPHttpClient`](../../sp-http/class/sphttpclient.md)> | The service key for SPHttpClient. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`beginBatch()`](beginbatch-sphttpclient.md)     | `public` | `SPHttpClientBatch` | Begins an ODATA batch, which allows multiple REST queries to be bundled into a single web request. |
-|[`fetch(url,configuration,options)`](fetch-sphttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)> | Generally, the parameters and semantics for SPHttpClient.fetch() are essentially the same as the WHATWG API standard that is documented here: https://fetch.spec.whatwg.org/ The SPHttpClient subclass adds some additional behaviors that are convenient when working with SharePoint ODATA API's (which can be avoided by using HttpClient instead): - Default "Accept" and "Content-Type" headers are added if not explicitly specified. - For write operations, an "X-RequestDigest" header is automatically added - The request digest token is automatically fetched and stored in a cache, with support for preloading For a write operation, SPHttpClient will automatically add the "X-RequestDigest" header, which may need to be obtained by issuing a seperate request such as "https://example.com/sites/sample/_api/contextinfo". Typically the appropriate SPWeb URL can be guessed by looking for a reserved URL segment such as "_api" in the original URL passed to fetch(); if not, use ISPHttpClientOptions.webUrl to specify it explicitly. |
-|[`get(url,configuration,options)`](get-sphttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)> | Calls fetch(), but sets the method to 'GET'. |
-|[`getWebUrlFromRequestUrl(requestUrl)`](getweburlfromrequesturl-sphttpclient.md)     | `public, static` | `string` | This uses a heuristic to guess the SPWeb URL associated with the provided REST URL. This is necessary for operations such as the X-RequestDigest and ODATA batching, which require POSTing to a separate REST endpoint in order to complete a request. For excample, if the requestUrl is "/sites/site/web/_api/service", the returned URL would be "/sites/site/web". Or if the requestUrl is "http://example.com/_layouts/service", the returned URL would be "http://example.com". |
-|[`post(url,configuration,options)`](post-sphttpclient.md)     | `public` | [`Promise`](../../web-apis/class/promise.md)<[`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md)> | Calls fetch(), but sets the method to 'POST'. |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/sphttpclientcommonconfiguration.md b/reference/spfx/sp-http/class/sphttpclientcommonconfiguration.md
deleted file mode 100644
index b7c606d2e7..0000000000
--- a/reference/spfx/sp-http/class/sphttpclientcommonconfiguration.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# SPHttpClientCommonConfiguration class
-
-_Implements: [`ISPHttpClientCommonConfiguration`](../../sp-http/interface/isphttpclientcommonconfiguration.md)_
-
-
-
-
-
-Common base class for SPHttpClientConfiguration and SPHttpClientBatchConfiguration.
-
-
-## Constructor
-Constructs a new instance of SPHttpClientCommonConfiguration with the specified flags. The default values will be used for any flags that are missing or undefined. If overrideFlags is specified, it takes precedence over flags.
-
-**Signature:** _constructor(flags: [ISPHttpClientCommonConfiguration](../../sp-http/interface/isphttpclientcommonconfiguration.md), overrideFlags?: ISPHttpClientCommonConfiguration);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`flags`     | `public` | [`ISPHttpClientCommonConfiguration`](../../sp-http/interface/isphttpclientcommonconfiguration.md) |  |
-|`jsonRequest`     | `public` | `boolean` | _Read-only._ When this switch is true: If the 'Content-Type' header was not explicitly added for the request, then SPHttpClient will add it if the request is a write operation (i.e. an HTTP method other than 'GET', 'HEAD', or 'OPTIONS'). For OData 3.0, the value is 'application/json;odata=verbose;charset=utf-8'. For OData 4.0, the value is 'application/json;charset=utf-8'. |
-|`jsonResponse`     | `public` | `boolean` | _Read-only._ When this switch is true: If the 'Accept' header was not explicitly added for the request, then SPHttpClient will add it. For OData 3.0, the value is 'application/json'. For OData 4.0, the value is 'application/json;odata.metadata=minimal'. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`initializeFlags()`](initializeflags-sphttpclientcommonconfiguration.md)     | `protected` | `void` |  |
-|[`overrideWith()`](overridewith-sphttpclientcommonconfiguration.md)     | `public` | [`SPHttpClientCommonConfiguration`](../../sp-http/class/sphttpclientcommonconfiguration.md) |  |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/sphttpclientconfiguration.md b/reference/spfx/sp-http/class/sphttpclientconfiguration.md
deleted file mode 100644
index 00ae26a332..0000000000
--- a/reference/spfx/sp-http/class/sphttpclientconfiguration.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# SPHttpClientConfiguration class
-
-_Implements: [`ISPHttpClientConfiguration`](../../sp-http/interface/isphttpclientconfiguration.md)_
-
-
-
-
-
-The SPHttpClientConfiguration object provides a set of switches for enabling/disabling various features of the SPHttpClient class. Normally these switches are set (e.g. when calling SPHttpClient.fetch()) by providing one of the predefined defaults from SPHttpClientConfigurations, however switches can also be changed via the SPHttpClientConfiguration.overrideWith() method.
-
-
-## Constructor
-Constructs a new instance of SPHttpClientConfiguration with the specified flags. The default values will be used for any flags that are missing or undefined. If overrideFlags is specified, it takes precedence over flags.
-
-**Signature:** _constructor(flags: [ISPHttpClientConfiguration](../../sp-http/interface/isphttpclientconfiguration.md), overrideFlags?: ISPHttpClientConfiguration);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`defaultODataVersion`     | `public` | [`ODataVersion`](../../sp-http/class/odataversion.md) | _Read-only._ When this switch is specified (i.e. not undefined): If the 'OData-Version' header was not explictly added for the request, then SPHttpClient will add the header to specify the version indicated by defaultODataVersion. NOTE: Without an 'OData-Version' header, the SharePoint server currently defaults to Version 3.0 in most cases. The recommended version is 4.0. |
-|`defaultSameOriginCredentials`     | `public` | `boolean` | _Read-only._ When this switch is true: If RequestInit.credentials is not explicitly specified for the request, then SPHttpClient will assign it to be 'same-origin'. Without this switch, different web browsers may apply different defaults. For more information, see the spec: https://fetch.spec.whatwg.org/#cors-protocol-and-credentials |
-|`flags`     | `public` | [`ISPHttpClientConfiguration`](../../sp-http/interface/isphttpclientconfiguration.md) |  |
-|`requestDigest`     | `public` | `boolean` | _Read-only._ When this switch is true: If the 'X-RequestDigest' header was not explicitly added for the request, then SPHttpClient will add it if the request is a write operation (i.e. an HTTP method other than 'GET', 'HEAD', or 'OPTIONS'). The request digest is managed by the DigestCache service. In the case of a cache miss, an additional network request may be performed. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`initializeFlags()`](initializeflags-sphttpclientconfiguration.md)     | `protected` | `void` |  |
-|[`overrideWith()`](overridewith-sphttpclientconfiguration.md)     | `public` | [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md) |  |
-
-
-
-
-
diff --git a/reference/spfx/sp-http/class/sphttpclientresponse.md b/reference/spfx/sp-http/class/sphttpclientresponse.md
deleted file mode 100644
index 37385e385b..0000000000
--- a/reference/spfx/sp-http/class/sphttpclientresponse.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# SPHttpClientResponse class
-
-
-
-
-
-
-
-The Response subclass returned by methods such as SPHttpClient.fetch().
-
-
-## Constructor
-
-
-**Signature:** _public constructor(response: [Response](../../web-apis/class/response.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`clone()`](clone-sphttpclientresponse.md)     | `public` | [`SPHttpClientResponse`](../../sp-http/class/sphttpclientresponse.md) |  |
-
-
-
-
-
-### Remarks
-
-This is a placeholder. In the future, additional SPHttpClient-specific functionality may be added to this class.
-
diff --git a/reference/spfx/sp-http/class/text-httpclientresponse.md b/reference/spfx/sp-http/class/text-httpclientresponse.md
deleted file mode 100644
index 7acc63bf2b..0000000000
--- a/reference/spfx/sp-http/class/text-httpclientresponse.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# text()
-
-
-
-See documentation for whatwg-fetch:Body.text
-
-**Signature:** _public text(): [Promise](../../web-apis/class/promise.md)<string>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<string>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/tostring-odataversion.md b/reference/spfx/sp-http/class/tostring-odataversion.md
deleted file mode 100644
index 95d5675a8e..0000000000
--- a/reference/spfx/sp-http/class/tostring-odataversion.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# toString()
-
-
-
-Returns the 'OData-Version' value, for example '4.0'.
-
-**Signature:** _public toString(): string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/class/tryparsefromheaders-odataversion.md b/reference/spfx/sp-http/class/tryparsefromheaders-odataversion.md
deleted file mode 100644
index 85645e241a..0000000000
--- a/reference/spfx/sp-http/class/tryparsefromheaders-odataversion.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# tryParseFromHeaders()
-
-
-
-If the 'OData-Version' header is present, this returns the corresponding ODataVersion constant. An error is thrown if the version number is not supported. If the header is missing, then undefined is returned.
-
-**Signature:** _public static tryParseFrom[Headers](../../web-apis/class/headers.md)(headers: Headers): [ODataVersion](../../sp-http/class/odataversion.md) | undefined;_
-
-**Returns**: [`ODataVersion `](../../sp-http/class/odataversion.md),` undefined`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-http/interface/igraphhttpclientconfiguration.md b/reference/spfx/sp-http/interface/igraphhttpclientconfiguration.md
deleted file mode 100644
index 2bba4cfe42..0000000000
--- a/reference/spfx/sp-http/interface/igraphhttpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# IGraphHttpClientConfiguration interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Flags interface for GraphHttpClientCommonConfiguration
-
-
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/igraphhttpclientconfigurations.md b/reference/spfx/sp-http/interface/igraphhttpclientconfigurations.md
deleted file mode 100644
index 244ad0c96c..0000000000
--- a/reference/spfx/sp-http/interface/igraphhttpclientconfigurations.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IGraphHttpClientConfigurations interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This interface provides standard predefined GraphHttpClientConfiguration objects for use with the GraphHttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`v1`      | [`GraphHttpClientConfiguration`](../../sp-http/class/graphhttpclientconfiguration.md) | This configuration turns off every feature switch for HttpClient. The fetch() behavior will be essentially identical to the WHATWG standard API that is documented here: https://fetch.spec.whatwg.org/ |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/igraphhttpclientoptions.md b/reference/spfx/sp-http/interface/igraphhttpclientoptions.md
deleted file mode 100644
index d79b907d2d..0000000000
--- a/reference/spfx/sp-http/interface/igraphhttpclientoptions.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# IGraphHttpClientOptions interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This interface defines the options for the GraphHttpClient operations such as get(), post(), fetch(), etc. It is based on the WHATWG API standard parameters that are documented here: https://fetch.spec.whatwg.org/
-
-
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/ihttpclientconfiguration.md b/reference/spfx/sp-http/interface/ihttpclientconfiguration.md
deleted file mode 100644
index 74a69de6e2..0000000000
--- a/reference/spfx/sp-http/interface/ihttpclientconfiguration.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# IHttpClientConfiguration interface
-
-
-
-
-
-
-
-Flags interface for HttpClientConfiguration.
-
-
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/ihttpclientconfigurations.md b/reference/spfx/sp-http/interface/ihttpclientconfigurations.md
deleted file mode 100644
index 29a8f1bf83..0000000000
--- a/reference/spfx/sp-http/interface/ihttpclientconfigurations.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IHttpClientConfigurations interface
-
-
-
-
-
-
-
-This interface provides standard predefined HttpClientConfiguration objects for use with the HttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`v1`      | [`HttpClientConfiguration`](../../sp-http/class/httpclientconfiguration.md) | This configuration turns off every feature switch for HttpClient. The fetch() behavior will be essentially identical to the WHATWG standard API that is documented here: https://fetch.spec.whatwg.org/ |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/ihttpclientoptions.md b/reference/spfx/sp-http/interface/ihttpclientoptions.md
deleted file mode 100644
index d61a7206f9..0000000000
--- a/reference/spfx/sp-http/interface/ihttpclientoptions.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# IHttpClientOptions interface
-
-
-
-
-
-
-
-This interface defines the options for the HttpClient operations such as get(), post(), fetch(), etc. It is based on the whatwg API standard parameters that are documented here: https://fetch.spec.whatwg.org/
-
-
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/isphttpclientcommonconfiguration.md b/reference/spfx/sp-http/interface/isphttpclientcommonconfiguration.md
deleted file mode 100644
index c6760e88ed..0000000000
--- a/reference/spfx/sp-http/interface/isphttpclientcommonconfiguration.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# ISPHttpClientCommonConfiguration interface
-
-
-
-
-
-
-
-Flags interface for SPHttpClientCommonConfiguration
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`jsonRequest`      | `boolean` | When this switch is true: If the 'Content-Type' header was not explicitly added for the request, then SPHttpClient will add it if the request is a write operation (i.e. an HTTP method other than 'GET', 'HEAD', or 'OPTIONS'). For OData 3.0, the value is 'application/json;odata=verbose;charset=utf-8'. For OData 4.0, the value is 'application/json;charset=utf-8'. |
-|`jsonResponse`      | `boolean` | When this switch is true: If the 'Accept' header was not explicitly added for the request, then SPHttpClient will add it. For OData 3.0, the value is 'application/json'. For OData 4.0, the value is 'application/json;odata.metadata=minimal'. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/isphttpclientconfiguration.md b/reference/spfx/sp-http/interface/isphttpclientconfiguration.md
deleted file mode 100644
index d82112f380..0000000000
--- a/reference/spfx/sp-http/interface/isphttpclientconfiguration.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# ISPHttpClientConfiguration interface
-
-
-
-
-
-
-
-Flags interface for SPHttpClientConfiguration.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`defaultODataVersion`      | [`ODataVersion`](../../sp-http/class/odataversion.md) | When this switch is specified (i.e. not undefined): If the 'OData-Version' header was not explictly added for the request, then SPHttpClient will add the header to specify the version indicated by defaultODataVersion. NOTE: Without an 'OData-Version' header, the SharePoint server currently defaults to Version 3.0 in most cases. The recommended version is 4.0. |
-|`defaultSameOriginCredentials`      | `boolean` | When this switch is true: If RequestInit.credentials is not explicitly specified for the request, then SPHttpClient will assign it to be 'same-origin'. Without this switch, different web browsers may apply different defaults. For more information, see the spec: https://fetch.spec.whatwg.org/#cors-protocol-and-credentials |
-|`requestDigest`      | `boolean` | When this switch is true: If the 'X-RequestDigest' header was not explicitly added for the request, then SPHttpClient will add it if the request is a write operation (i.e. an HTTP method other than 'GET', 'HEAD', or 'OPTIONS'). The request digest is managed by the DigestCache service. In the case of a cache miss, an additional network request may be performed. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/isphttpclientconfigurations.md b/reference/spfx/sp-http/interface/isphttpclientconfigurations.md
deleted file mode 100644
index 174a41299a..0000000000
--- a/reference/spfx/sp-http/interface/isphttpclientconfigurations.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# ISPHttpClientConfigurations interface
-
-
-
-
-
-
-
-This interface provides standard predefined SPHttpClientConfiguration objects for use with the SPHttpClient class. In general, clients should choose the latest available version number, which enables all the switches that are recommended for typical scenarios. (If new switches are introduced in the future, a new version number will be introduced, which ensures that existing code will continue to function the way it did at the time when it was tested.)
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`v1`      | [`SPHttpClientConfiguration`](../../sp-http/class/sphttpclientconfiguration.md) | Version 1 enables these switches: consoleLogging = true; jsonRequest = true; jsonResponse = true; defaultSameOriginCredentials = true; defaultODataVersion = ODataVersion.v4; requestDigest = true |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-http/interface/isphttpclientoptions.md b/reference/spfx/sp-http/interface/isphttpclientoptions.md
deleted file mode 100644
index 53263c12e1..0000000000
--- a/reference/spfx/sp-http/interface/isphttpclientoptions.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# ISPHttpClientOptions interface
-
-
-
-
-
-
-
-This interface defines the options for the SPHttpClient operations such as get(), post(), fetch(), etc. It is based on the WHATWG API standard parameters that are documented here: https://fetch.spec.whatwg.org/
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`webUrl`      | `string` | For a write operation, SPHttpClient will automatically add the "X-RequestDigest" header, which may need to be fetched using a seperate request such as "https://example.com/sites/sample/_api/contextinfo". Typically the SPWeb URL ("https://example.com/sites/sample" in this example) can be guessed by looking for a reserved URL segment such as "_api" in the original REST query, however certain REST endpoints do not contain a reserved URL segment; in this case, the webUrl can be explicitly specified using this option. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility-module.md b/reference/spfx/sp-listview-extensibility-module.md
deleted file mode 100644
index e4df5485ed..0000000000
--- a/reference/spfx/sp-listview-extensibility-module.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# sp-listview-extensibility package
-
-
-
-
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`BaseFieldCustomizer`](./sp-listview-extensibility/class/basefieldcustomizer.md)     | This is the base class that third parties should extend when implementing a client-side extension that customizes the appearance of fields in a SharePoint ListView. In the component manifest, the "extensionType" should be set to "FieldCustomizer". |
-| [`BaseListViewCommandSet`](./sp-listview-extensibility/class/baselistviewcommandset.md)     | This is the base class that third parties should extend when implementing a client-side extension that provides a command set for a SharePoint list view. In the component manifest, the "extensionType" should be set to "ListViewCommandSet". |
-| [`CellFormatter`](./sp-listview-extensibility/class/cellformatter.md)     | This class provides some functions that facilitate formatting cell values. |
-| [`ColumnAccessor`](./sp-listview-extensibility/class/columnaccessor.md)     | Provides access to a ListView column, which is the visual presentation of a field. |
-| [`FieldCustomizerContext`](./sp-listview-extensibility/class/fieldcustomizercontext.md)     | This object provides contextual information for BaseFieldCustomizer. |
-| [`ListViewAccessor`](./sp-listview-extensibility/class/listviewaccessor.md)     | Provides access to a SharePoint ListView control. |
-| [`ListViewCommandSetContext`](./sp-listview-extensibility/class/listviewcommandsetcontext.md)     | This object provides contextual information for BaseListViewCommandSet. |
-| [`RowAccessor`](./sp-listview-extensibility/class/rowaccessor.md)     | Provides access to a ListView row, which is the visual presentation of a SharePoint list item. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IFieldCustomizerCellEventParameters`](./sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md)   | Event parmeters for BaseFieldCustomizer.onRenderCell()  |
-| [`IListViewCommandSetExecuteEventParameters`](./sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md)   |   |
-| [`IListViewCommandSetRefreshEventParameters`](./sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md)   |   |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/basefieldcustomizer.md b/reference/spfx/sp-listview-extensibility/class/basefieldcustomizer.md
deleted file mode 100644
index d1ab71fdbd..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/basefieldcustomizer.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# BaseFieldCustomizer <TProperties> class
-
-
-
-_Type parameters: `<TProperties>`_
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This is the base class that third parties should extend when implementing a client-side extension that customizes the appearance of fields in a SharePoint ListView. In the component manifest, the "extensionType" should be set to "FieldCustomizer".
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`context`     | `public` | [`FieldCustomizerContext`](../../sp-listview-extensibility/class/fieldcustomizercontext.md) | Use context object to access common services and state associated with the component. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`onDisposeCell()`](ondisposecell-basefieldcustomizer.md)     | `public` | `void` |  |
-|[`onRenderCell()`](onrendercell-basefieldcustomizer.md)     | `public` | `void` |  |
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/baselistviewcommandset.md b/reference/spfx/sp-listview-extensibility/class/baselistviewcommandset.md
deleted file mode 100644
index e899525a9b..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/baselistviewcommandset.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# BaseListViewCommandSet <TProperties> class
-
-
-
-_Type parameters: `<TProperties>`_
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This is the base class that third parties should extend when implementing a client-side extension that provides a command set for a SharePoint list view. In the component manifest, the "extensionType" should be set to "ListViewCommandSet".
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`context`     | `public` | [`ListViewCommandSetContext`](../../sp-listview-extensibility/class/listviewcommandsetcontext.md) | Use context object to access common services and state associated with the component. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`onExecute()`](onexecute-baselistviewcommandset.md)     | `public` | `void` | This event occurs when the command is invoked, e.g. because the user clicked on the toolbar button or menu item. |
-|[`onRefreshCommand()`](onrefreshcommand-baselistviewcommandset.md)     | `public` | `void` | This event occurs whenever the ListView state changes. It allows the implementor to tailor the appearance of the command. For example, to hide the command, assign event.visible = false. To customize the title, assign event.tile. |
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/cellformatter.md b/reference/spfx/sp-listview-extensibility/class/cellformatter.md
deleted file mode 100644
index 30186b918b..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/cellformatter.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# CellFormatter class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This class provides some functions that facilitate formatting cell values.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`renderAsText()`](renderastext-cellformatter.md)     | `public, static` | `string` | Renders the specified cell value as a text string without any markup. |
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/columnaccessor.md b/reference/spfx/sp-listview-extensibility/class/columnaccessor.md
deleted file mode 100644
index 2e72ae66cf..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/columnaccessor.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# ColumnAccessor class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Provides access to a ListView column, which is the visual presentation of a field.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`field`     | `public` | [`SPField`](../../sp-page-context/class/spfield.md) | _Read-only._ The server-side definition of the field. This property is read-only. |
-|`visible`     | `public` | `boolean` | _Read-only._ Whether to show this column in the list view. This property is read-only. |
-
-
-
-
-
-
-
-### Remarks
-
-A SharePoint "field" (SPField) defines the data storage for a property of a list item. (If the list item represents a document, then the field is sometimes called a "property".) A "column" is the visual presentation of a field, when displayed by the ListView.
-
diff --git a/reference/spfx/sp-listview-extensibility/class/fieldcustomizercontext.md b/reference/spfx/sp-listview-extensibility/class/fieldcustomizercontext.md
deleted file mode 100644
index e52bb4876d..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/fieldcustomizercontext.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# FieldCustomizerContext class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This object provides contextual information for BaseFieldCustomizer.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`column`     | `public` | [`ColumnAccessor`](../../sp-listview-extensibility/class/columnaccessor.md) | _Read-only._ Provides access to the column that the customizer will operate on. |
-|`field`     | `public` | [`SPField`](../../sp-page-context/class/spfield.md) | _Read-only._ Provides access to the SharePoint field that the customizer will operate on. |
-|`listView`     | `public` | [`ListViewAccessor`](../../sp-listview-extensibility/class/listviewaccessor.md) | _Read-only._ Provides access to the ListView control that the customizer will operate on. |
-|`pageContext`     | `public` | [`PageContext`](../../sp-page-context/class/pagecontext.md) | _Read-only._ The page context provides standard definitions for common SharePoint objects that need to be shared between the client-side application, web parts, and other components. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/getvalue-rowaccessor.md b/reference/spfx/sp-listview-extensibility/class/getvalue-rowaccessor.md
deleted file mode 100644
index b68b186d76..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/getvalue-rowaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getValue()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Retrieves the cell value for the specified column. The value will be a primitive JavaScript object such as a string, number, etc.
-
-**Signature:** _public abstract getValue(column: [ColumnAccessor](../../sp-listview-extensibility/class/columnaccessor.md)): any;_
-
-**Returns**: `any`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/getvaluebyname-rowaccessor.md b/reference/spfx/sp-listview-extensibility/class/getvaluebyname-rowaccessor.md
deleted file mode 100644
index e596c8640d..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/getvaluebyname-rowaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getValueByName()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Retrieves the cell value for the column/field with the specified internal name. The value will be a primitive JavaScript object such as a string, number, etc.
-
-**Signature:** _public abstract getValueByName(internalName: string): any;_
-
-**Returns**: `any`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/listviewaccessor.md b/reference/spfx/sp-listview-extensibility/class/listviewaccessor.md
deleted file mode 100644
index b4c2be02a1..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/listviewaccessor.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# ListViewAccessor class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Provides access to a SharePoint ListView control.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`columns`     | `public` | `ReadonlyArray<ColumnAccessor>` | _Read-only._ The columns in associated with this view, including hidden columns. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/listviewcommandsetcontext.md b/reference/spfx/sp-listview-extensibility/class/listviewcommandsetcontext.md
deleted file mode 100644
index a1f3629170..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/listviewcommandsetcontext.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# ListViewCommandSetContext class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This object provides contextual information for BaseListViewCommandSet.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`listView`     | `public` | [`ListViewAccessor`](../../sp-listview-extensibility/class/listviewaccessor.md) | _Read-only._ Provides access to the ListView control that the customizer will operate on. |
-|`manifest`     | `public` | `ICommandSetExtensionManifest` | _Read-only._  |
-|`pageContext`     | `public` | [`PageContext`](../../sp-page-context/class/pagecontext.md) | _Read-only._ The page context provides standard definitions for common SharePoint objects that need to be shared between the client-side application, web parts, and other components. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/ondisposecell-basefieldcustomizer.md b/reference/spfx/sp-listview-extensibility/class/ondisposecell-basefieldcustomizer.md
deleted file mode 100644
index e0c327a3d1..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/ondisposecell-basefieldcustomizer.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onDisposeCell()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-
-
-**Signature:** _@virtual public onDisposeCell(event: [IFieldCustomizerCellEventParameters](../../sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/onexecute-baselistviewcommandset.md b/reference/spfx/sp-listview-extensibility/class/onexecute-baselistviewcommandset.md
deleted file mode 100644
index 22a6936dc6..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/onexecute-baselistviewcommandset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onExecute()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This event occurs when the command is invoked, e.g. because the user clicked on the toolbar button or menu item.
-
-**Signature:** _@virtual public onExecute(event: [IListViewCommandSetExecuteEventParameters](../../sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/onrefreshcommand-baselistviewcommandset.md b/reference/spfx/sp-listview-extensibility/class/onrefreshcommand-baselistviewcommandset.md
deleted file mode 100644
index 76952371a8..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/onrefreshcommand-baselistviewcommandset.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onRefreshCommand()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-This event occurs whenever the ListView state changes. It allows the implementor to tailor the appearance of the command. For example, to hide the command, assign event.visible = false. To customize the title, assign event.tile.
-
-**Signature:** _@virtual public onRefreshCommand(event: [IListViewCommandSetRefreshEventParameters](../../sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/onrendercell-basefieldcustomizer.md b/reference/spfx/sp-listview-extensibility/class/onrendercell-basefieldcustomizer.md
deleted file mode 100644
index 0dbb1750af..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/onrendercell-basefieldcustomizer.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onRenderCell()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-
-
-**Signature:** _@virtual public onRenderCell(event: [IFieldCustomizerCellEventParameters](../../sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/renderastext-cellformatter.md b/reference/spfx/sp-listview-extensibility/class/renderastext-cellformatter.md
deleted file mode 100644
index 75e7b97a47..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/renderastext-cellformatter.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# renderAsText()
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Renders the specified cell value as a text string without any markup.
-
-**Signature:** _public static renderAsText(column: [ColumnAccessor](../../sp-listview-extensibility/class/columnaccessor.md), cellValue: any): string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-listview-extensibility/class/rowaccessor.md b/reference/spfx/sp-listview-extensibility/class/rowaccessor.md
deleted file mode 100644
index 3c07e64af2..0000000000
--- a/reference/spfx/sp-listview-extensibility/class/rowaccessor.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# RowAccessor class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Provides access to a ListView row, which is the visual presentation of a SharePoint list item.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`getValue()`](getvalue-rowaccessor.md)     | `public` | `any` | Retrieves the cell value for the specified column. The value will be a primitive JavaScript object such as a string, number, etc. |
-|[`getValueByName()`](getvaluebyname-rowaccessor.md)     | `public` | `any` | Retrieves the cell value for the column/field with the specified internal name. The value will be a primitive JavaScript object such as a string, number, etc. |
-
-
-
-
-
-### Remarks
-
-A SharePoint "list item" (SPListItem) is a data storage record in the content management system; it stores an array of values for the associated fields. A "row" is the visual presentation of a list item, when displayed by the ListView; it stores an array of cell values for the associated columns.
-
diff --git a/reference/spfx/sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md b/reference/spfx/sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md
deleted file mode 100644
index 5ff0106f56..0000000000
--- a/reference/spfx/sp-listview-extensibility/interface/ifieldcustomizercelleventparameters.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# IFieldCustomizerCellEventParameters interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Event parmeters for BaseFieldCustomizer.onRenderCell()
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`cellDiv`      | `HTMLDivElement` | The HTML "div" element that the extension will take ownership of. This ownership will end when onDisposeCell() is called. |
-|`cellStorage`      | `any` | An implementor-defined storage property. |
-|`cellValue`      | `any` | The value of the field being rendered. |
-|`row`      | [`RowAccessor`](../../sp-listview-extensibility/class/rowaccessor.md) | The row being rendered. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md b/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md
deleted file mode 100644
index d429239422..0000000000
--- a/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetexecuteeventparameters.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IListViewCommandSetExecuteEventParameters interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`commandId`      | `string` | The unique identifier for the command. This is specified as ICommandDefinition.commandId in the component manifest. |
-|`selectedRows`      | `ReadonlyArray<RowAccessor>` | The currently selected ListView rows, at the time when the event occurred. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md b/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md
deleted file mode 100644
index b1caeccbc8..0000000000
--- a/reference/spfx/sp-listview-extensibility/interface/ilistviewcommandsetrefresheventparameters.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# IListViewCommandSetRefreshEventParameters interface
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ariaLabel`      | `string` | To customize the ARIA label for the command, the onShowing() handler can assign a different value to this property. Otherwise, it will be the ICommandDefinition.ariaLabel as declared in the component manifest. |
-|`commandId`      | `string` | The unique identifier for the command. This is specified as ICommandDefinition.commandId in the component manifest. |
-|`selectedRows`      | `ReadonlyArray<RowAccessor>` | The currently selected ListView rows, at the time when the event occurred. |
-|`title`      | `string` | To customize the displayed title of the command, the onShowing() handler can assign a different value to this property. Otherwise, it will be the ICommandDefinition.title as declared in the component manifest. |
-|`visible`      | `boolean` | Specifies whether the command is displayed or not. To avoid showing the command, the onShowing() handler can assign false to this property. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-loader-module.md b/reference/spfx/sp-loader-module.md
deleted file mode 100644
index 5f656ee1f1..0000000000
--- a/reference/spfx/sp-loader-module.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# sp-loader package
-
-The SharePoint Framework loader
-
-Built on familiar standards such as SystemJS and WebPack, the loader is the first part of the SharePoint Framework to load on a page. It manages versioning and loading of client-side components, web parts, and other assets. It also implements the developer dashboard.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`SPComponentLoader`](./sp-loader/class/spcomponentloader.md)     | Component loader. Needs to be initialized with an implemented ISPComponentLoader. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`ILoadScriptOptions`](./sp-loader/interface/iloadscriptoptions.md)   | Options for the loadScript() method in ISPComponentLoader  |
-| [`ISPComponentLoader`](./sp-loader/interface/ispcomponentloader.md)   | Interface for the module loader. It allows to load modules and scripts (through SystemJS) and CSS on the page. Also allows access to the manifests that exist in the page.  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-loader/class/initialize-spcomponentloader.md b/reference/spfx/sp-loader/class/initialize-spcomponentloader.md
deleted file mode 100644
index d95a9f78d1..0000000000
--- a/reference/spfx/sp-loader/class/initialize-spcomponentloader.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# initialize()
-
-
-
-Initializes the component loader with an implementation. Must be called once before it can be used.
-
-**Signature:** _public static initialize(componentLoader: [ISPComponentLoader](../../sp-loader/interface/ispcomponentloader.md)): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-loader/class/loadcomponent-spcomponentloader.md b/reference/spfx/sp-loader/class/loadcomponent-spcomponentloader.md
deleted file mode 100644
index a010f23735..0000000000
--- a/reference/spfx/sp-loader/class/loadcomponent-spcomponentloader.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# loadComponent(manifest)
-
-
-
-Loads a component from a manifest.
-
-**Signature:** _public static loadComponent < TComponent >(manifest: IClientSideComponentManifest): [Promise](../../web-apis/class/promise.md)<TComponent>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<TComponent>
-
-
-
-A promise containing the loaded module.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `manifest`    | `IClientSideComponentManifest` | Manifest of the module to load. |
-
-
diff --git a/reference/spfx/sp-loader/class/loadcss-spcomponentloader.md b/reference/spfx/sp-loader/class/loadcss-spcomponentloader.md
deleted file mode 100644
index 82f46f0504..0000000000
--- a/reference/spfx/sp-loader/class/loadcss-spcomponentloader.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# loadCss(url)
-
-
-
-Inserts a <link ... /> tag for a stylesheet.
-
-**Signature:** _public static loadCss(url: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | The CSS file URL. |
-
-
diff --git a/reference/spfx/sp-loader/class/loadscript-spcomponentloader.md b/reference/spfx/sp-loader/class/loadscript-spcomponentloader.md
deleted file mode 100644
index 6bef1ed2be..0000000000
--- a/reference/spfx/sp-loader/class/loadscript-spcomponentloader.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# loadScript(url,options)
-
-
-
-Given a URL, load a script.
-
-**Signature:** _public static loadScript < TModule >(url: string, options?: [ILoadScriptOptions](../../sp-loader/interface/iloadscriptoptions.md)): [Promise](../../web-apis/class/promise.md)<TModule>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<TModule>
-
-
-
-A promise containing the loaded module.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | The script URL. |
-| `options`    | [`ILoadScriptOptions`](../../sp-loader/interface/iloadscriptoptions.md) | _Optional._ globalExportsName: If the script isn't an AMD module and loads a global member on the page, specify the global member's name. |
-
-
diff --git a/reference/spfx/sp-loader/class/spcomponentloader.md b/reference/spfx/sp-loader/class/spcomponentloader.md
deleted file mode 100644
index 456b6d0184..0000000000
--- a/reference/spfx/sp-loader/class/spcomponentloader.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# SPComponentLoader class
-
-
-
-
-
-
-
-Component loader. Needs to be initialized with an implemented ISPComponentLoader.
-
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`initialize()`](initialize-spcomponentloader.md)     | `public, static` | `void` | Initializes the component loader with an implementation. Must be called once before it can be used. |
-|[`loadComponent(manifest)`](loadcomponent-spcomponentloader.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<TComponent> | Loads a component from a manifest. |
-|[`loadCss(url)`](loadcss-spcomponentloader.md)     | `public, static` | `void` | Inserts a <link ... /> tag for a stylesheet. |
-|[`loadScript(url,options)`](loadscript-spcomponentloader.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<TModule> | Given a URL, load a script. |
-
-
-
-
-
diff --git a/reference/spfx/sp-loader/interface/iloadscriptoptions.md b/reference/spfx/sp-loader/interface/iloadscriptoptions.md
deleted file mode 100644
index 8600a81b18..0000000000
--- a/reference/spfx/sp-loader/interface/iloadscriptoptions.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# ILoadScriptOptions interface
-
-
-
-
-
-
-
-Options for the loadScript() method in ISPComponentLoader
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`globalExportsName`      | `string` | If set, the loaded script will be stored in a global variable under this name. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-loader/interface/ispcomponentloader.md b/reference/spfx/sp-loader/interface/ispcomponentloader.md
deleted file mode 100644
index 2b74386d17..0000000000
--- a/reference/spfx/sp-loader/interface/ispcomponentloader.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# ISPComponentLoader interface
-
-
-
-
-
-
-
-Interface for the module loader. It allows to load modules and scripts (through SystemJS) and CSS on the page. Also allows access to the manifests that exist in the page.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`loadComponent(manifest)`](loadcomponent-ispcomponentloader.md)      | [`Promise`](../../web-apis/class/promise.md)<TComponent> | Loads a component from a manifest. |
-|[`loadCss(url)`](loadcss-ispcomponentloader.md)      | `void` | Inserts a <link ... /> tag for a stylesheet. |
-|[`loadScript(url,options)`](loadscript-ispcomponentloader.md)      | [`Promise`](../../web-apis/class/promise.md)<TModule> | Given a URL, load a script. |
-
-
-
-
diff --git a/reference/spfx/sp-loader/interface/loadcomponent-ispcomponentloader.md b/reference/spfx/sp-loader/interface/loadcomponent-ispcomponentloader.md
deleted file mode 100644
index 5325af281b..0000000000
--- a/reference/spfx/sp-loader/interface/loadcomponent-ispcomponentloader.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# loadComponent(manifest)
-
-
-
-Loads a component from a manifest.
-
-**Signature:** _loadComponent < TComponent >(manifest: IClientSideComponentManifest): [Promise](../../web-apis/class/promise.md)<TComponent>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<TComponent>
-
-
-
-A promise containing the loaded module.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `manifest`    | `IClientSideComponentManifest` | Manifest of the module to load. |
-
-
diff --git a/reference/spfx/sp-loader/interface/loadcss-ispcomponentloader.md b/reference/spfx/sp-loader/interface/loadcss-ispcomponentloader.md
deleted file mode 100644
index 8c931040cf..0000000000
--- a/reference/spfx/sp-loader/interface/loadcss-ispcomponentloader.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# loadCss(url)
-
-
-
-Inserts a <link ... /> tag for a stylesheet.
-
-**Signature:** _loadCss(url: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | The CSS file URL. |
-
-
diff --git a/reference/spfx/sp-loader/interface/loadscript-ispcomponentloader.md b/reference/spfx/sp-loader/interface/loadscript-ispcomponentloader.md
deleted file mode 100644
index 0184ee1bd0..0000000000
--- a/reference/spfx/sp-loader/interface/loadscript-ispcomponentloader.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# loadScript(url,options)
-
-
-
-Given a URL, load a script.
-
-**Signature:** _loadScript < TModule >(url: string, options?: [ILoadScriptOptions](../../sp-loader/interface/iloadscriptoptions.md)): [Promise](../../web-apis/class/promise.md)<TModule>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<TModule>
-
-
-
-A promise containing the loaded module.
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `url`    | `string` | The script URL. |
-| `options`    | [`ILoadScriptOptions`](../../sp-loader/interface/iloadscriptoptions.md) | _Optional._ globalExportsName: If the script isn't an AMD module and loads a global member on the page, specify the global member's name. |
-
-
diff --git a/reference/spfx/sp-odata-types-module.md b/reference/spfx/sp-odata-types-module.md
deleted file mode 100644
index f013799df2..0000000000
--- a/reference/spfx/sp-odata-types-module.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# sp-odata-types package
-
-TypeScript interfaces for working with SharePoint REST APIs
-
-This package defines TypeScript interfaces that describe various ODATA objects returned by SharePoint REST APIs. It is useful when implementing data layers that interpret these types. This package has no performance cost because it does not contain any runtime code; it consists only of type definitions.
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IODataBasePermission`](./sp-odata-types/interface/iodatabasepermission.md)   | Data used for creating a SPPermission object.  |
-| [`IODataChangeToken`](./sp-odata-types/interface/iodatachangetoken.md)   | Represents an OData SP.ChangeToken object. For more information about this object  |
-| [`IODataContextWebInformation`](./sp-odata-types/interface/iodatacontextwebinformation.md)   | Represents an OData SP.ContextWebInformation object. For more information about this object  |
-| [`IODataList`](./sp-odata-types/interface/iodatalist.md)   | Represents an OData SP.List object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx  |
-| [`IODataListItem`](./sp-odata-types/interface/iodatalistitem.md)   | Represents an OData SP.ListItem object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx  |
-| [`IODataNavigationNode`](./sp-odata-types/interface/iodatanavigationnode.md)   | Represents an OData SP.NavigationNode object. https://msdn.microsoft.com/en-us/library/office/jj246311.aspx  |
-| [`IODataNavigationNodeCollection`](./sp-odata-types/interface/iodatanavigationnodecollection.md)   | Represents an OData Microsoft.SharePoint.Navigation.SPNavigation object. https://msdn.microsoft.com/en-us/library/office/ee557907.aspx  |
-| [`IODataUser`](./sp-odata-types/interface/iodatauser.md)   | Represents an OData SP.User object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx  |
-| [`IODataUserCustomAction`](./sp-odata-types/interface/iodatausercustomaction.md)   | Represents an OData SP.UserCustomAction object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/dn531432.aspx#bk_UserCustomAction  |
-| [`IODataWeb`](./sp-odata-types/interface/iodataweb.md)   | Represents an OData SP.Web object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatabasepermission.md b/reference/spfx/sp-odata-types/interface/iodatabasepermission.md
deleted file mode 100644
index bd8a2f63db..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatabasepermission.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IODataBasePermission interface
-
-
-
-
-
-
-
-Data used for creating a SPPermission object.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`High`      | `number` |  |
-|`Low`      | `number` |  |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatachangetoken.md b/reference/spfx/sp-odata-types/interface/iodatachangetoken.md
deleted file mode 100644
index 2399e7770e..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatachangetoken.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IODataChangeToken interface
-
-
-
-
-
-
-
-Represents an OData SP.ChangeToken object. For more information about this object
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`StringValue`      | `string` | Example: { StringValue: "1;3;9fb9199b-65f2-4a4a-b597-11d1a44422c1;635892156279130000;10721" } |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatacontextwebinformation.md b/reference/spfx/sp-odata-types/interface/iodatacontextwebinformation.md
deleted file mode 100644
index 337a1d6016..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatacontextwebinformation.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# IODataContextWebInformation interface
-
-
-
-
-
-
-
-Represents an OData SP.ContextWebInformation object. For more information about this object
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`FormDigestTimeoutSeconds`      | `number` | Example: 1800 |
-|`FormDigestValue`      | `string` | Example: "0x61B31CBF4C76C...B0,20 Jan 2016 02:24:43 -0000" |
-|`LibraryVersion`      | `string` | Example: "16.0.4919.3000" |
-|`SiteFullUrl`      | `string` | Example: "http:\u002f\u002fexample.com\u002fsites\u002fPubSite" |
-|`SupportedSchemaVersions`      | `string[]` | Example: [ "14.0.0.0", "15.0.0.0" ] |
-|`WebFullUrl`      | `string` | Example: "http:\u002f\u002fexample.com\u002fsites\u002fPubSite" |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatalist.md b/reference/spfx/sp-odata-types/interface/iodatalist.md
deleted file mode 100644
index c376f72e0f..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatalist.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# IODataList interface
-
-
-
-
-
-
-
-Represents an OData SP.List object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`BaseTemplate`      | `number` | The list definition type on which the list is based. |
-|`Created`      | `string` | Example: "/Date(1453294804000)/" |
-|`CurrentChangeToken`      | [`IODataChangeToken`](../../sp-odata-types/interface/iodatachangetoken.md) | The change token that will be used in logging the next change to the list. |
-|`Description`      | `string` | A description of the List. |
-|`EntityTypeName`      | `string` | Example: "MyListTitleList" |
-|`Hidden`      | `boolean` | A hidden list does not appear on the Documents and Lists page, Quick Launch bar, the Modify Site Content page, or the Add Column page as an option for lookup fields. |
-|`Id`      | `string` | Example: "/Guid(9fb9199b-65f2-4a4a-b597-11d1a44422c1)/" |
-|`LastItemDeletedDate`      | `string` | Example: "/Date(1453294809000)/" |
-|`LastItemModifiedDate`      | `string` | Example: "/Date(1453294809000)/" |
-|`ListItemEntityTypeFullName`      | `string` | Example: "SP.Data.MyListTitleListItem" |
-|`ParentWebUrl`      | `string` | Example: "/sites/PubSite" |
-|`TemplateFeatureId`      | `string` | Example: "/Guid(22a9ef51-737b-4ff2-9346-694633fe4416)/" |
-|`Title`      | `string` | Example: "Pages" |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatalistitem.md b/reference/spfx/sp-odata-types/interface/iodatalistitem.md
deleted file mode 100644
index 1ece4f4d02..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatalistitem.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# IODataListItem interface
-
-
-
-
-
-
-
-Represents an OData SP.ListItem object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ContentTypeId`      | `{ StringValue: string }` | Example: { StrinValue: "0x010100C5..." } |
-|`ID`      | `number` |  |
-|`Title`      | `string` | Title of the List Item |
-|`UniqueId`      | `string` | Example: "/Guid(d5369f3b-bd7a-412a-9c0f-7f0650bb5489)/" |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatanavigationnode.md b/reference/spfx/sp-odata-types/interface/iodatanavigationnode.md
deleted file mode 100644
index b895d217b7..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatanavigationnode.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# IODataNavigationNode interface
-
-
-
-
-
-
-
-Represents an OData SP.NavigationNode object. https://msdn.microsoft.com/en-us/library/office/jj246311.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`Children`      | [`IODataNavigationNode`](../../sp-odata-types/interface/iodatanavigationnode.md)[] | Gets or sets an array of Navigation Nodes that are children to the current node. |
-|`Id`      | `number` | Gets a value that specifies the identifier for the navigation node. |
-|`IsDocLib`      | `boolean` |  |
-|`IsExternal`      | `boolean` | Gets or sets a value that specifies whether the navigation node URL potentially corresponds to pages outside of the site collection. |
-|`IsVisible`      | `boolean` | Gets or sets a value that specifies if the node navigation link should be visible. |
-|`Title`      | `string` | Gets or sets a value that specifies the anchor text for the node navigation link. |
-|`Url`      | `string` | Gets or sets a value that specifies the URL to be stored with the navigation node. It must be a URL of relative form if IsExternal is false. It must be a URL of relative or absolute form. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatanavigationnodecollection.md b/reference/spfx/sp-odata-types/interface/iodatanavigationnodecollection.md
deleted file mode 100644
index 8011031298..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatanavigationnodecollection.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IODataNavigationNodeCollection interface
-
-
-
-
-
-
-
-Represents an OData Microsoft.SharePoint.Navigation.SPNavigation object. https://msdn.microsoft.com/en-us/library/office/ee557907.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`quickLaunch`      | [`IODataNavigationNode`](../../sp-odata-types/interface/iodatanavigationnode.md)[] | Gets an SPNavigationNode object that contains the nodes in the Quick Launch area of the site. |
-|`topNav`      | [`IODataNavigationNode`](../../sp-odata-types/interface/iodatanavigationnode.md)[] | Gets an SPNavigationNode object that contains the nodes in the top link bar for the website. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatauser.md b/reference/spfx/sp-odata-types/interface/iodatauser.md
deleted file mode 100644
index e8009b2337..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatauser.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# IODataUser interface
-
-
-
-
-
-
-
-Represents an OData SP.User object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`Email`      | `string` | Example: "someone@example.com" |
-|`Id`      | `number` |  |
-|`IsSiteAdmin`      | `boolean` | Boolean value that specifies whether the user is a site collection administrator. |
-|`LoginName`      | `string` | Example: "i:0#.w|domain\user" |
-|`PrincipalType`      | `number` | This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values. None: 0 User: 1 DistributionList: 2 SecurityGroup: 4 SharePointGroup: 8 All: 15 |
-|`Title`      | `string` | Example: "DOMAIN\user" |
-|`UserId`      | `IODataUserId` | Gets the information of the user that contains the user's name identifier and the issuer of the user's name identifier. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodatausercustomaction.md b/reference/spfx/sp-odata-types/interface/iodatausercustomaction.md
deleted file mode 100644
index 358b3da0c3..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodatausercustomaction.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# IODataUserCustomAction interface
-
-
-
-
-
-
-
-Represents an OData SP.UserCustomAction object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/dn531432.aspx#bk_UserCustomAction
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ClientSideComponentId`      | `string` | The unique identifier of the client-side component defined with SharePoint Framework<br/> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._ |
-|`ClientSideComponentProperties`      | `string` | Custom initialization properties for the client-side component.<br/> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._ |
-|`CommandUIExtension`      | `string` | Gets or sets a value that specifies an implementation specific XML fragment that determines user interface properties of the custom action. |
-|`Description`      | `string` | Gets or sets the description of the custom action. |
-|`Group`      | `string` | Gets or sets a value that specifies an implementation-specific value that determines the position of the custom action in the page. |
-|`Id`      | `string` | Gets a value that specifies the identifier (GUID) of the custom action. Example: "48309f28-53aa-43ed-b113-625120e5af6f" |
-|`ImageUrl`      | `string` | Gets or sets the URL of the image associated with the custom action. |
-|`Location`      | `string` | Gets or sets the location of the custom action. |
-|`RegistrationId`      | `string` | Gets or sets the value that specifies the identifier of the object associated with the custom action. |
-|`RegistrationType`      | `number` | Gets or sets the value that specifies the type of object associated with the custom action. |
-|`Rights`      | [`IODataBasePermission`](../../sp-odata-types/interface/iodatabasepermission.md) | Gets or sets the value that specifies the permissions needed for the custom action. |
-|`Scope`      | `number` | Gets a value that specifies the scope of the custom action. |
-|`ScriptBlock`      | `string` | Gets or sets the value that specifies the ECMAScript to be executed when the custom action is performed. |
-|`ScriptSrc`      | `string` | Gets or sets a value that specifies the URI of a file which contains the ECMAScript to execute on the page. |
-|`Sequence`      | `number` | Gets or sets the value that specifies an implementation-specific value that determines the order of the custom action that appears on the page. |
-|`Title`      | `string` | Gets or sets the display title of the custom action. |
-|`Url`      | `string` | Gets or sets the URL, URI, or ECMAScript (JScript, JavaScript) function associated with the action. |
-|`VersionOfUserCustomAction`      | `string` | Gets a value that specifies an implementation specific version identifier. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-odata-types/interface/iodataweb.md b/reference/spfx/sp-odata-types/interface/iodataweb.md
deleted file mode 100644
index 8f1d03fe15..0000000000
--- a/reference/spfx/sp-odata-types/interface/iodataweb.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# IODataWeb interface
-
-
-
-
-
-
-
-Represents an OData SP.Web object. For more information about this object see the MSDN documentation here: https://msdn.microsoft.com/en-us/library/office/jj860569.aspx
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`Created`      | `string` | Gets a value that specifies when the site was created. Example: "/Date(2016,0,20,12,58,7,0)/" |
-|`CurrentChangeToken`      | [`IODataChangeToken`](../../sp-odata-types/interface/iodatachangetoken.md) | Represents the unique sequential location of a change within the change log. |
-|`CustomMasterUrl`      | `string` | Gets or sets the URL for a custom master page file to apply to the website. Example: "/sites/PubSite/_catalogs/masterpage/seattle.master" |
-|`Description`      | `string` | Gets or sets the description for the site. |
-|`Id`      | `string` | Gets a value that specifies the site identifier for the site. Example: "/Guid(92ea328e-9f50-49a6-9da5-2f2dd5577041)/" |
-|`IsMultilingual`      | `boolean` | Value that represents if the web was |
-|`Language`      | `number` | Gets a value that specifies the LCID for the language that is used on the site. Example: 1033 |
-|`LastItemModifiedDate`      | `string` | Gets a value that specifies when an item was last modified in the site. Example: "/Date(1453618828000)/" |
-|`MasterUrl`      | `string` | Gets or sets the URL of the master page that is used for the website. Example: "/sites/PubSite/_catalogs/masterpage/seattle.master" |
-|`NoCrawl`      | `boolean` | Determines if a particular web will be crawled by search or not. |
-|`QuickLaunchEnabled`      | `boolean` | Gets or sets a value that specifies whether the Quick Launch area is enabled on the site. |
-|`RecycleBinEnabled`      | `boolean` | Gets or sets a value that determines whether the recycle bin is enabled for the website. |
-|`ServerRelativeUrl`      | `string` | Gets or sets the server-relative URL for the Web site. Example: "/sites/PubSite" |
-|`SiteLogoUrl`      | `string` | Gets the url for the logo of this particular site. |
-|`Title`      | `string` | The title of the web. |
-|`UIVersion`      | `number` | Gets or sets the user interface (UI) version of the Web site. Example: 15 |
-|`Url`      | `string` | Gets the absolute URL for the website. Example: "http://example.com/sites/PubSite" |
-|`WebTemplate`      | `string` | Gets the name of the site definition or site template that was used to create the site. Example: "BLANKINTERNET" |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context-module.md b/reference/spfx/sp-page-context-module.md
deleted file mode 100644
index 025100de35..0000000000
--- a/reference/spfx/sp-page-context-module.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# sp-page-context package
-
-Page context services for the SharePoint Framework
-
-The page context allows an application and its web parts to share common data about the current page, such as its contents, URL, list, user, permissions, navigation menu, etc.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`CultureInfo`](./sp-page-context/class/cultureinfo.md)     | This class is primarily used with the PageContext class. It provides culture info for the current user of the application. |
-| [`PageContext`](./sp-page-context/class/pagecontext.md)     | The page context provides standard definitions for common SharePoint objects that need to be shared between the client-side application, web parts, and other components. Typically the data is fetched via REST queries when navigating to a new page, but it can also be preloaded by the web server, or filled from a custom application cache. |
-| [`SPField`](./sp-page-context/class/spfield.md)     | The client-side equivalent for SharePoint SPField class. Used in Fields property of SPList and SPListItem classes. A field represents the data model for a column in SharePoint list view. |
-| [`SPList`](./sp-page-context/class/splist.md)     | This class is primarily used with the PageContext class. It provides contextual information for the SharePoint list that hosts the page. |
-| [`SPListItem`](./sp-page-context/class/splistitem.md)     | This class is primarily used with the PageContext class. It provides contextual information for the SharePoint list item that hosts the page. |
-| [`SPPermission`](./sp-page-context/class/sppermission.md)     | This class can be used to determine if the current user has a requested set of permissions. Specifies the built-in permissions available in SharePoint Foundation Derived from OneDriveWeb/ODBNext/odsp-shared https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx |
-| [`SPSite`](./sp-page-context/class/spsite.md)     | This class is primarily used with the PageContext class. It provides contextual information for the SharePoint site collection ("site") that hosts the page. |
-| [`SPUser`](./sp-page-context/class/spuser.md)     | This class is primarily used with the PageContext class. It provides contextual information for the SharePoint user that is accessing the page. |
-| [`SPWeb`](./sp-page-context/class/spweb.md)     | This class is primarily used with the PageContext class. It provides contextual information for the SharePoint site ("web") that hosts the page. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/cultureinfo.md b/reference/spfx/sp-page-context/class/cultureinfo.md
deleted file mode 100644
index cf7af455d0..0000000000
--- a/reference/spfx/sp-page-context/class/cultureinfo.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# CultureInfo class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides culture info for the current user of the application.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`currentCultureName`     | `public` | `string` | _Read-only._ This string determines the language default format for dates, times, numbers, currency values, the sorting order of text, casing conventions, and string comparisons. This property may have an empty string, but will never be undefined. Example: If the currentCultureName is "en-AU" then the application could use this information to display the date as 1/8 instead of 8/1. |
-|`currentUICultureName`     | `public` | `string` | _Read-only._ This string determines the default user interface language. This used for localization and translation of text. This property may have an empty string, but will never be undefined. Example: If the currentUICultureName is "es-MX", then the application could use this information to translate the word "hello" to "hola". |
-|`isRightToLeft`     | `public` | `boolean` | _Read-only._ This boolean represents the dominant direction of written text for the default user interface language. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/hasallpermissions-sppermission.md b/reference/spfx/sp-page-context/class/hasallpermissions-sppermission.md
deleted file mode 100644
index 2a111b7dc6..0000000000
--- a/reference/spfx/sp-page-context/class/hasallpermissions-sppermission.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# hasAllPermissions(...requestedPerms)
-
-
-
-Function for determining if a given permission mask has all of the requested permissions.
-
-**Signature:** _public hasAllPermissions(...requestedPerms: [SPPermission](../../sp-page-context/class/sppermission.md)[]): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `...requestedPerms`    | [`SPPermission`](../../sp-page-context/class/sppermission.md)[] | Any number of SPPermission objects to be compared against the original |
-
-
diff --git a/reference/spfx/sp-page-context/class/hasanypermissions-sppermission.md b/reference/spfx/sp-page-context/class/hasanypermissions-sppermission.md
deleted file mode 100644
index c0f33630eb..0000000000
--- a/reference/spfx/sp-page-context/class/hasanypermissions-sppermission.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# hasAnyPermissions(...requestedPerms)
-
-
-
-Function for determining if a given permission mask has any of the requested permissions.
-
-**Signature:** _public hasAnyPermissions(...requestedPerms: [SPPermission](../../sp-page-context/class/sppermission.md)[]): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `...requestedPerms`    | [`SPPermission`](../../sp-page-context/class/sppermission.md)[] | Any number of SPPermission objects to be compared against the original |
-
-
diff --git a/reference/spfx/sp-page-context/class/haspermission-sppermission.md b/reference/spfx/sp-page-context/class/haspermission-sppermission.md
deleted file mode 100644
index 5bfc48265b..0000000000
--- a/reference/spfx/sp-page-context/class/haspermission-sppermission.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# hasPermission(requestedPerm)
-
-
-
-Function for checking if a given permission mask has the requested permission.
-
-**Signature:** _public hasPermission(requestedPerm: [SPPermission](../../sp-page-context/class/sppermission.md)): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `requestedPerm`    | [`SPPermission`](../../sp-page-context/class/sppermission.md) | The SPPermission object to be compared against the original |
-
-
diff --git a/reference/spfx/sp-page-context/class/pagecontext.md b/reference/spfx/sp-page-context/class/pagecontext.md
deleted file mode 100644
index 2c7947e6ee..0000000000
--- a/reference/spfx/sp-page-context/class/pagecontext.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# PageContext class
-
-
-
-
-
-
-
-The page context provides standard definitions for common SharePoint objects that need to be shared between the client-side application, web parts, and other components. Typically the data is fetched via REST queries when navigating to a new page, but it can also be preloaded by the web server, or filled from a custom application cache.
-
-
-## Constructor
-
-
-**Signature:** _constructor(serviceScope: [ServiceScope](../../sp-core-library/class/servicescope.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`cultureInfo`     | `public` | [`CultureInfo`](../../sp-page-context/class/cultureinfo.md) | _Read-only._ It provides culture info for the current user of the application. This class is primarily used with the PageContext class. |
-|`isInitialized`     | `public` | `boolean` | _Read-only._ Returns whether the PageContext has been initialized. |
-|`legacyPageContext`     | `public` | `any` | _Read-only._ This property is provided to facilitate migration of legacy code. It returns a JavaScript object whose contents are similar to the _spPageContextInfo window variable from classic pages. The contents of this variable may change in future releases of SharePoint. New projects are encouraged to use the framework APIs instead, since they are documented and provide reliable backwards compatibility guarantees. |
-|`list`     | `public` | [`SPList `](../../sp-page-context/class/splist.md),` undefined` | _Read-only._ Contextual information for the SharePoint list that is hosting the page. If there is no list associated to the current page, this property will be undefined. |
-|`listItem`     | `public` | [`SPListItem `](../../sp-page-context/class/splistitem.md),` undefined` | _Read-only._ Contextual information for the SharePoint list item that is hosting the page. If there is no list item associated to the current page, this property will be undefined. |
-|`serviceKey`     | `public` | [`ServiceKey`](../../sp-core-library/class/servicekey.md)<[`PageContext`](../../sp-page-context/class/pagecontext.md)> | The service key for PageContext. |
-|`site`     | `public` | [`SPSite`](../../sp-page-context/class/spsite.md) | _Read-only._ Contextual information for the SharePoint site collection ("site") that is hosting the page. |
-|`user`     | `public` | [`SPUser`](../../sp-page-context/class/spuser.md) | _Read-only._ It provides contextual information for the SharePoint user that is accessing the page. This class is primarily used with the PageContext class. |
-|`web`     | `public` | [`SPWeb`](../../sp-page-context/class/spweb.md) | _Read-only._ Contextual information for the SharePoint site ("web") that is hosting the page. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/spfield.md b/reference/spfx/sp-page-context/class/spfield.md
deleted file mode 100644
index 84f3db421a..0000000000
--- a/reference/spfx/sp-page-context/class/spfield.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# SPField class
-
-
-
-
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-The client-side equivalent for SharePoint SPField class. Used in Fields property of SPList and SPListItem classes. A field represents the data model for a column in SharePoint list view.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`clientSideComponentId`     | `public` | [`Guid `](../../sp-core-library/class/guid.md),` undefined` | _Read-only._ The unique identifier of the client-side component associated with the field. |
-|`clientSideComponentProperties`     | `public` | `string` | _Read-only._ This property is only used when a ClientSideComponentId is specified. It is optional. If non-empty, the string must contain a JSON object with custom initialization properties whose format and meaning are defined by the client-side component. |
-|`displayName`     | `public` | `string` | _Read-only._ The display name of the field. This name is shown as column name in UI. |
-|`fieldType`     | `public` | `string` | _Read-only._ The type of the field represented as a string |
-|`id`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ The GUID identifier for this field. |
-|`internalName`     | `public` | `string` | _Read-only._ The internal name of the field. This name is usually used to find the field. |
-|`isRequired`     | `public` | `boolean` | _Read-only._ Whether the field is required for each list item in the list |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/splist.md b/reference/spfx/sp-page-context/class/splist.md
deleted file mode 100644
index fbf626c3c9..0000000000
--- a/reference/spfx/sp-page-context/class/splist.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# SPList class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides contextual information for the SharePoint list that hosts the page.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`id`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ The GUID that identifies the SPList on the server. This property could be undefined if the information isn't avalible. |
-|`permissions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | _Read-only._ Return the SPPermission object that represents the set of permissions that the current user has for interacting with the list. |
-|`serverRelativeUrl`     | `public` | `string` | _Read-only._ Returns the server-relative URL for this SPList. Example: "/sites/PubSite" |
-|`title`     | `public` | `string` | _Read-only._ Returns the title for this SPList. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/splistitem.md b/reference/spfx/sp-page-context/class/splistitem.md
deleted file mode 100644
index 99327c291e..0000000000
--- a/reference/spfx/sp-page-context/class/splistitem.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# SPListItem class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides contextual information for the SharePoint list item that hosts the page.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`id`     | `public` | `number` | _Read-only._ The number that identifies the SPListItem on the server. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/sppermission.md b/reference/spfx/sp-page-context/class/sppermission.md
deleted file mode 100644
index f638c47ce5..0000000000
--- a/reference/spfx/sp-page-context/class/sppermission.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# SPPermission class
-
-
-
-
-
-
-
-This class can be used to determine if the current user has a requested set of permissions. Specifies the built-in permissions available in SharePoint Foundation Derived from OneDriveWeb/ODBNext/odsp-shared https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx
-
-
-## Constructor
-
-
-**Signature:** _constructor(value: [IODataBasePermission](../../sp-odata-types/interface/iodatabasepermission.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`addAndCustomizePages`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Add, change, or delete HTML pages or web part Pages, and edit the Web site using a SharePoint Foundation–compatible editor. |
-|`addDelPrivateWebParts`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Add or remove personal web parts on a web part Page. |
-|`addListItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Add items to lists, add documents to document libraries, and add Web discussion comments. |
-|`applyStyleSheets`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Apply a style sheet (.css file) to the Web site. |
-|`applyThemeAndBorder`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Apply a theme or borders to the entire Web site. |
-|`approveItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Approve a minor version of a list item or document. |
-|`browseDirectories`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Enumerate files and folders in a Web site using Microsoft Office SharePoint Designer 2007 and WebDAV interfaces. |
-|`browserUserInfo`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View information about users of the Web site. |
-|`cancelCheckout`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Discard or check in a document which is checked out to another user. |
-|`createAlerts`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create e-mail alerts. |
-|`createGroups`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create a group of users that can be used anywhere within the site collection. |
-|`createSSCSite`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create a Web site using Self-Service Site Creation. |
-|`deleteListItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Delete items from a list, documents from a document library, and Web discussion comments in documents. |
-|`deleteVersions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Delete past versions of a list item or document. |
-|`editListItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Edit items in lists, edit documents in document libraries, edit Web discussion comments in documents, and customize web part Pages in document libraries. |
-|`editMyUserInfo`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Allows a user to change his or her user information, such as adding a picture. |
-|`emptyMask`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Has no permissions on the Web site. Not available through the user interface. |
-|`enumeratePermissions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Enumerate permissions on the Web site, list, folder, document, or list item. |
-|`fullMask`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Has all permissions on the Web site. Not available through the user interface. |
-|`layoutsPage`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View the layouts page? |
-|`manageAlerts`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Manage alerts for all users of the Web site. |
-|`manageLists`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create and delete lists, add or remove columns in a list, and add or remove public views of a list. |
-|`managePermissions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create and change permission levels on the Web site and assign permissions to users and groups. |
-|`managePersonalViews`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create, change, and delete personal views of lists. |
-|`manageSubwebs`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites. |
-|`manageWeb`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Grant the ability to perform all administration tasks for the Web site as well as manage content. Activate, deactivate,or edit properties of Web site scoped Features through the object model or through the user interface (UI). When grantedon the root Web site of a site collection, activate, deactivate, or edit properties of site collection scoped Features through the object model. To browse to the Site Collection Features page and activate or deactivate site collection scoped Features through the UI, you must be a site collection administrator. |
-|`open`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Allow users to open a Web site, list, or folder to access items inside that container. |
-|`openItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View the source of documents with server-side file handlers. |
-|`updatePersonalWebParts`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Update web parts to display personalized information. |
-|`useClientIntegration`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Use features that launch client applications; otherwise, users must work on documents locally and upload changes. |
-|`useRemoteAPIs`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | Use SOAP, WebDAV, or Microsoft Office SharePoint Designer 2007 interfaces to access the Web site. |
-|`value`     | `public` | [`IODataBasePermission`](../../sp-odata-types/interface/iodatabasepermission.md) | _Read-only._ Returns the value of this SPPermission object |
-|`viewFormPages`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View forms, views, and application pages, and enumerate lists. |
-|`viewListItems`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View items in lists, documents in document libraries, and view Web discussion comments. |
-|`viewPages`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View pages in a Web site. |
-|`viewUsageData`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View reports on Web site usage. |
-|`viewVersions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | View past versions of a list item or document. |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`hasAllPermissions(...requestedPerms)`](hasallpermissions-sppermission.md)     | `public` | `boolean` | Function for determining if a given permission mask has all of the requested permissions. |
-|[`hasAnyPermissions(...requestedPerms)`](hasanypermissions-sppermission.md)     | `public` | `boolean` | Function for determining if a given permission mask has any of the requested permissions. |
-|[`hasPermission(requestedPerm)`](haspermission-sppermission.md)     | `public` | `boolean` | Function for checking if a given permission mask has the requested permission. |
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/spsite.md b/reference/spfx/sp-page-context/class/spsite.md
deleted file mode 100644
index b6a467b4d7..0000000000
--- a/reference/spfx/sp-page-context/class/spsite.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# SPSite class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides contextual information for the SharePoint site collection ("site") that hosts the page.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`absoluteUrl`     | `public` | `string` | _Read-only._ Returns the absolute URL for this SPSite. Example: "https://example.com/sites/PubSite" |
-|`cdnPrefix`     | `public` | `string` | _Read-only._ Returns the prefix of the application's specified cdn or an empty string if there isn't one. |
-|`classification`     | `public` | `string` | _Read-only._ Returns the classification of the site. |
-|`correlationId`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ Returns the correlation id to the current server request. |
-|`id`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ The GUID that identifies the SPSite on the server. |
-|`isNoScriptEnabled`     | `public` | `boolean` | _Read-only._ Returns true if isNoScript has been enabled on the SPSite. |
-|`recycleBinItemCount`     | `public` | `number` | _Read-only._ The amount of items in the recyle bin. |
-|`serverRelativeUrl`     | `public` | `string` | _Read-only._ Returns the server-relative URL for this SPSite. Example: "/sites/PubSite" |
-|`serverRequestPath`     | `public` | `string` | _Read-only._ Returns serverRelativeUrl of the original request. Example: "/teams/SPClientTest/SitePages/Home.aspx" |
-|`sitePagesEnabled`     | `public` | `boolean` | _Read-only._ Returns true if SitePages are enabled on this SPSite. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/spuser.md b/reference/spfx/sp-page-context/class/spuser.md
deleted file mode 100644
index c5325c2a80..0000000000
--- a/reference/spfx/sp-page-context/class/spuser.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# SPUser class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides contextual information for the SharePoint user that is accessing the page.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`displayName`     | `public` | `string` | _Read-only._ The display name for the current user. Example: "John Doe" |
-|`email`     | `public` | `string` | _Read-only._ The email address for the current user. Example: "example@contoso.com" |
-|`isAnonymousGuestUser`     | `public` | `boolean` | _Read-only._ Returns if the current user is an anonymous guest. |
-|`isExternalGuestUser`     | `public` | `boolean` | _Read-only._ Returns true if the current user is an external guest. |
-|`loginName`     | `public` | `string` | _Read-only._ The login name for current user. Example: "i:0#.w|domain\user" |
-|`preferUserTimeZone`     | `public` | `boolean` | _Read-only._ This boolean represents if a the user or web's time zone settings should be used to display the current time. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-page-context/class/spweb.md b/reference/spfx/sp-page-context/class/spweb.md
deleted file mode 100644
index 4058bf0750..0000000000
--- a/reference/spfx/sp-page-context/class/spweb.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# SPWeb class
-
-
-
-
-
-
-
-This class is primarily used with the PageContext class. It provides contextual information for the SharePoint site ("web") that hosts the page.
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`absoluteUrl`     | `public` | `string` | _Read-only._ Returns the absolute URL for this SPWeb. Example: "https://example.com/sites/PubSite/SubWeb" |
-|`id`     | `public` | [`Guid`](../../sp-core-library/class/guid.md) | _Read-only._ The GUID that identifies the SPWeb on the server. |
-|`isAppWeb`     | `public` | `boolean` | _Read-only._ Returns true if this SPWeb the container web for an SPApp. |
-|`language`     | `public` | `number` | _Read-only._ Returns the locale identifier (LCID) for the default language of the website. Example: 1033 represents the locale identifier for en-US. |
-|`logoUrl`     | `public` | `string` | _Read-only._ Returns the absolute URL of the website logo. Example: https://example.com/sites/PubSite/SubWeb/logo.jpg |
-|`permissions`     | `public` | [`SPPermission`](../../sp-page-context/class/sppermission.md) | _Read-only._ Return the SPPermission object that represents the set of permissions that the current user has for interacting with the web. |
-|`serverRelativeUrl`     | `public` | `string` | _Read-only._ Returns the server-relative URL for this SPWeb. Example: "/sites/PubSite/SubWeb" |
-|`templateName`     | `public` | `string` | _Read-only._ Returns the string representing the numeric identifier for the site definition or site template that was used to create the site. Example: "1" represents the team site template when creating a new site on SharePoint. |
-|`title`     | `public` | `string` | _Read-only._ Returns the title of the current SPWeb. |
-
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base-module.md b/reference/spfx/sp-webpart-base-module.md
deleted file mode 100644
index ad2a314139..0000000000
--- a/reference/spfx/sp-webpart-base-module.md
+++ /dev/null
@@ -1,75 +0,0 @@
-# sp-webpart-base package
-
-SharePoint Framework support for building web parts
-
-A web part is a reusable visual object that a page author can add to their content, and customize using a property pane. Examples of web parts include an embedded video player, a map, a group calendar, a chart, etc. The sp-webpart-base package defines the APIs used by developers to create a custom web part.
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`BaseClientSideWebPart`](./sp-webpart-base/class/baseclientsidewebpart.md)     | This abstract class implements the the base functionality for a client side web part. Every client side web part needs to inherit from this class. Along with the base functionality, this class provides some APIs that can be used by the web part. These APIs fall in two catagories. The first category of APIs provide data and functionality. Example, the web part context (i.e. this.context). This API should be used to access contextual data relevant to this web part instance. The second category of APIs provide a base implementation for the web part lifecycle and can be overridden for an updated implementation. The render() API is the only API that is mandatory to be implemented/overridden by a web part. All other life cycle APIs have a base implementation and can be overridden based on the needs of the web part. Please refer to the documentation of the individual APIs to make the right decision. |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`IClientSideWebPartStatusRenderer`](./sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md)   | Interface to be implemented by a component that should display the loading indicator and error messages for a webpart.  |
-| [`IPlaceholderSpinnerProps`](./sp-webpart-base/interface/iplaceholderspinnerprops.md)   | Interface for properties used to display the loading spinner in the web part display area.  |
-| [`IPropertyPaneAccessor`](./sp-webpart-base/interface/ipropertypaneaccessor.md)   | Web part context property pane accessor interface. Provides some most commonly used utilities to access the property pane.  |
-| [`IPropertyPaneButtonProps`](./sp-webpart-base/interface/ipropertypanebuttonprops.md)   | PropertyPane button props.  |
-| [`IPropertyPaneCheckboxProps`](./sp-webpart-base/interface/ipropertypanecheckboxprops.md)   | PropertyPane CheckBox component props.  |
-| [`IPropertyPaneChoiceGroupOption`](./sp-webpart-base/interface/ipropertypanechoicegroupoption.md)   | PropertyPane ChoiceGroup option props.  |
-| [`IPropertyPaneChoiceGroupOptionIconProps`](./sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md)   | PropertyPane ChoiceGroup icon props.  |
-| [`IPropertyPaneChoiceGroupProps`](./sp-webpart-base/interface/ipropertypanechoicegroupprops.md)   | PropertyPane ChoiceGroup props.  |
-| [`IPropertyPaneConfiguration`](./sp-webpart-base/interface/ipropertypaneconfiguration.md)   | Web part configuration settings  |
-| [`IPropertyPaneCustomFieldProps`](./sp-webpart-base/interface/ipropertypanecustomfieldprops.md)   | PropertyPane CustomPropertyField props.  |
-| [`IPropertyPaneDropdownOption`](./sp-webpart-base/interface/ipropertypanedropdownoption.md)   | PropertyPane drop down options.  |
-| [`IPropertyPaneDropdownProps`](./sp-webpart-base/interface/ipropertypanedropdownprops.md)   | PropertyPane drop down component props.  |
-| [`IPropertyPaneField`](./sp-webpart-base/interface/ipropertypanefield.md)   | PropertyPane field.  |
-| [`IPropertyPaneGroup`](./sp-webpart-base/interface/ipropertypanegroup.md)   | PropertyPane group. Group is part of the PropertyPanePage.  |
-| [`IPropertyPaneLabelProps`](./sp-webpart-base/interface/ipropertypanelabelprops.md)   | PropertyPaneLabel component props.  |
-| [`IPropertyPaneLinkProps`](./sp-webpart-base/interface/ipropertypanelinkprops.md)   | PropertyPaneLink component props.  |
-| [`IPropertyPanePage`](./sp-webpart-base/interface/ipropertypanepage.md)   | PropertyPanePage interface.  |
-| [`IPropertyPanePageHeader`](./sp-webpart-base/interface/ipropertypanepageheader.md)   | PropertyPane header. This header remains same for all the pages.  |
-| [`IPropertyPaneSliderProps`](./sp-webpart-base/interface/ipropertypanesliderprops.md)   | PropertyPaneSliderProps component props.  |
-| [`IPropertyPaneTextFieldProps`](./sp-webpart-base/interface/ipropertypanetextfieldprops.md)   | PropertyPaneTextField component props.  |
-| [`IPropertyPaneToggleProps`](./sp-webpart-base/interface/ipropertypanetoggleprops.md)   | PropertyPaneToggle component props.  |
-| [`ISerializedServerProcessedData`](./sp-webpart-base/interface/iserializedserverprocesseddata.md)   | Contains collections of data that can be processed by server side services like search index and link fixup  |
-| [`ISerializedWebPartData`](./sp-webpart-base/interface/iserializedwebpartdata.md)   | This structure represents the part of the serialized state of a web part which is controlled by the web part. It is extended by IWebPartData which contains additional data added by the framework to the serialized data.  |
-| [`IWebPartContext`](./sp-webpart-base/interface/iwebpartcontext.md)   | The base context interface for client-side web parts.  |
-| [`IWebPartData`](./sp-webpart-base/interface/iwebpartdata.md)   | This structure represents the serialized state of a web part. When the serialize() API is called on a web part, the output should be this structure. The structure of the 'properties' field is owned by the web part and is specific to the web part. Each web part can decide the set of properties it wants to serialialize.  |
-| [`IWebPartPropertiesMetadata`](./sp-webpart-base/interface/iwebpartpropertiesmetadata.md)   | This structure is used to define metadata for web part propeties as a map of string to IWebPartPropertyMetadata The key should be a json path to the property in web part propeties. The json path supports the following operators: - Dot . for selecting object members e.g. person.name - Brackets [] for selecting array items e.g. person.photoURLs[0] - Bracketed asterisk [*] for array elements wildcard e.g. person.websites[*]. You can make combinations of these operators e.g. person.websites[*].url Important Note: Only one wildcard per path is supported. Example: Let's assume we have a web part with properties that have the following schema: { title: string; person: { name: string; bio: string; photoURLs: string[]; websites: { title: string; url: string; }[] } } We can define the metadata for the desired properties as following: { 'person.bio': { isRichContent: true }, 'person.photoURLs[*]': { isImageSource: true }, 'person.websites[*].url': { isLink: true } } This will make SharePoint servers aware of the content of your properties and run services such as search indexing, link fix-up, etc on the data. In case any of the values needs to update by these services, e.g link fix-up, the web part property bag is automatically updated.  |
-
-
-
-## Functions
-
-| Function	   | Returns | Description |
-|:-------------|:------|:---------------|
-| [`PropertyPaneButton(targetProperty,properties)`](./sp-webpart-base/function/propertypanebutton.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneButtonProps`](./../sp-webpart-base/interface/ipropertypanebuttonprops.md)>  | Helper method to create a Button on the PropertyPane.  |
-| [`PropertyPaneCheckbox(targetProperty,properties)`](./sp-webpart-base/function/propertypanecheckbox.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneCheckboxProps`](./../sp-webpart-base/interface/ipropertypanecheckboxprops.md)>  | Helper method to create a Checkbox on the PropertyPane.  |
-| [`PropertyPaneChoiceGroup(targetProperty,properties)`](./sp-webpart-base/function/propertypanechoicegroup.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneChoiceGroupProps`](./../sp-webpart-base/interface/ipropertypanechoicegroupprops.md)>  | Helper method to create a Choice Group on the PropertyPane.  |
-| [`PropertyPaneCustomField(targetProperty,properties)`](./sp-webpart-base/function/propertypanecustomfield.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneCustomFieldProps`](./../sp-webpart-base/interface/ipropertypanecustomfieldprops.md)>  | Helper method to create a custom field on the PropertyPane. The purpose of the custom field is to help the web part developer to add a custom control to the PropertyPane. The PropertyPane supports a host of inbuilt field types. While this list meets the demands of most web parts, but there are exceptional cases when web parts have special needs and need a special control. The custom field helps fill that gap.  |
-| [`PropertyPaneDropdown(targetProperty,properties)`](./sp-webpart-base/function/propertypanedropdown.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneDropdownProps`](./../sp-webpart-base/interface/ipropertypanedropdownprops.md)>  | Helper method to create a Dropdown on the PropertyPane.  |
-| [`PropertyPaneHorizontalRule(properties)`](./sp-webpart-base/function/propertypanehorizontalrule.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<void>  | Helper method to create a Horizontal Rule on the PropertyPane.  |
-| [`PropertyPaneLabel(targetProperty,properties)`](./sp-webpart-base/function/propertypanelabel.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneLabelProps`](./../sp-webpart-base/interface/ipropertypanelabelprops.md)>  | Helper method to create a Label on the PropertyPane.  |
-| [`PropertyPaneLink(targetProperty,properties)`](./sp-webpart-base/function/propertypanelink.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneLinkProps`](./../sp-webpart-base/interface/ipropertypanelinkprops.md)>  | Helper method to create a Link on the PropertyPane.  |
-| [`PropertyPaneSlider(targetProperty,properties)`](./sp-webpart-base/function/propertypaneslider.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneSliderProps`](./../sp-webpart-base/interface/ipropertypanesliderprops.md)>  | Helper method to create a Slider on the PropertyPane.  |
-| [`PropertyPaneTextField(targetProperty,properties)`](./sp-webpart-base/function/propertypanetextfield.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneTextFieldProps`](./../sp-webpart-base/interface/ipropertypanetextfieldprops.md)>  | Helper method to create a TextField on the PropertyPane.  |
-| [`PropertyPaneToggle(targetProperty,properties)`](./sp-webpart-base/function/propertypanetoggle.md) |[`IPropertyPaneField`](./../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneToggleProps`](./../sp-webpart-base/interface/ipropertypanetoggleprops.md)>  | Helper method to create a Toggle on the PropertyPane.  |
-
-
-## Enumerations
-
-| Enumeration	   | Description|
-|:-----------|:------------|
-|[`PropertyPaneButtonType`](./sp-webpart-base/enum/propertypanebuttontype.md)    | Enum for all the supported button types. |
-|[`PropertyPaneFieldType`](./sp-webpart-base/enum/propertypanefieldtype.md)    | Enum for all the supported PropertyPane field types. Names should be consistent with those in office-ui-fabric-react, be careful to get letter casing correct. |
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/class/baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/baseclientsidewebpart.md
deleted file mode 100644
index c696dfdc73..0000000000
--- a/reference/spfx/sp-webpart-base/class/baseclientsidewebpart.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# BaseClientSideWebPart <TProperties> class
-
-
-
-_Type parameters: `<TProperties>`_
-
-
-
-This abstract class implements the the base functionality for a client side web part. Every client side web part needs to inherit from this class. Along with the base functionality, this class provides some APIs that can be used by the web part. These APIs fall in two catagories. The first category of APIs provide data and functionality. Example, the web part context (i.e. this.context). This API should be used to access contextual data relevant to this web part instance. The second category of APIs provide a base implementation for the web part lifecycle and can be overridden for an updated implementation. The render() API is the only API that is mandatory to be implemented/overridden by a web part. All other life cycle APIs have a base implementation and can be overridden based on the needs of the web part. Please refer to the documentation of the individual APIs to make the right decision.
-
-
-## Constructor
-Constructor for the BaseClientSideWebPart class. If a sub class overrides the constructor, it needs to call super() as the first line of its constructor. It is highly recommended that the web part use the OnInit API to perform any web part specific initialization. Most of the web part features like this.context and this.properties are not available to be used before the the onInit part of the web part loading lifecycle. e.g. constructor() { super(); . . class specific constructor code .. }
-
-**Signature:** _constructor();_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`accessibleTitle`     | `public` | `string` | This property points to the accessible title of web part made available to screen readers. The base implementation returns that default title in the manifest. Web parts that want to provide more descriptive title containing contextual information need to override this API. |
-|`canOpenPopupOnRender`     | `public` | `boolean` | _Read-only._ This property indicates whether a web part can open a popup on initial render. In some environments the host re-renders the web parts frequently, and therefor, opening popups during render will cause popups to open repeatedly and hence poor user experience. As an example, the classic SharePoint pages perform postbacks and hence page re-render on all button clicks. If a web part needs to open a popup on render, it should use this API before opening the popup. If this API returns false, the web part should not open popup on initial render. Some web parts that open popups during render are the document embed web part that pops up the file picker on initial render, embedded video web part that pops up the PropertyPane on initial render. |
-|`context`     | `public` | [`IWebPartContext`](../../sp-webpart-base/interface/iwebpartcontext.md) | _Read-only._ This property is a pointer to the web part context. |
-|`dataVersion`     | `public` | [`Version`](../../sp-core-library/class/version.md) | _Read-only._ The value of this property is stored in the serialized data of the web part to allow developers to manage versioning of their web part. The default version is 1.0 |
-|`description`     | `public` | `string` | _Read-only._ Description of the WebPart |
-|`disableReactivePropertyChanges`     | `public` | `boolean` | _Read-only._ This property is used to change the web part's PropertyPane interaction from Reactive to NonReactive. The default behaviour is Reactive. Where, Reactive implies that changes made in the PropertyPane are transmitted to the web part instantly and the user can see instant updates. This helps the page creator get instant feedback and decide if they should keep the new configuration changes or not. NonReactive implies that the configuraiton changes are transmitted to the web part only after 'Apply' PropertyPane button is clicked. |
-|`displayMode`     | `public` | [`DisplayMode`](../../sp-core-library/enum/displaymode.md) | _Read-only._ This property is the current display mode of the web part. |
-|`domElement`     | `public` | `HTMLElement` | _Read-only._ This property is a pointer to the root DOM element of the web part. This is a DIV element and contains the whole DOM subtree of the web part. |
-|`isRenderAsync`     | `public` | `boolean` | _Read-only._ Indicates whether the web part is rendering in Async mode. Default value is false. If the web part overrides this field to return true, then it needs to call renderCompleted API after the web part rendering is complete. |
-|`previewImageUrl`     | `public` | `string `,` undefined` | This property points to the preview image for the web part. The base implementation returns undefined. Web parts that want to provide a valid preview image url need to override this API. The preview image url can be used to create a preview of the web part or of the page on which the web part is present. |
-|`properties`     | `public` | `TProperties` | _Read-only._ This property is the pointer to the custom property bag of the web part. |
-|`propertiesMetadata`     | `public` | [`IWebPartPropertiesMetadata `](../../sp-webpart-base/interface/iwebpartpropertiesmetadata.md),` undefined` | _Read-only._ This property defines metadata for the web part property bag. The metadata can help SharePoint understand the content of the properties better and perform relevant services on the data. |
-|`renderedFromPersistedData`     | `public` | `boolean` | _Read-only._ This property indicates whether the web part was rendered from the persisted data (serialized state from the last time that the web part was saved) or not. Example: When web part is added for the first time using toolbox then the value is false. |
-|`renderedOnce`     | `public` | `boolean` | _Read-only._ This property indicates whether the web part has been rendered once or not. After the first time rendering, the value of this property is always true. Till a full re-render of the web part happens. |
-|`title`     | `public` | `string` | _Read-only._ Title of the WebPart |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`clearError()`](clearerror-baseclientsidewebpart.md)     | `protected` | `void` | This API should be used to clear the error message from the web part display area. |
-|[`getPropertyPaneConfiguration()`](getpropertypaneconfiguration-baseclientsidewebpart.md)     | `protected` | [`IPropertyPaneConfiguration`](../../sp-webpart-base/interface/ipropertypaneconfiguration.md) | This API is used to ger the configuration to build the property pane for the web part. If the web part wants to use the PropertyPane for configuration, this API needs to be overridden and the web part needs to return the configuration for the PropertyPane. |
-|[`onAfterDeserialize(deserializedObject,dataVersion)`](onafterdeserialize-baseclientsidewebpart.md)     | `protected` | `TProperties` | This API is called after the web part is deserialized to an object, right before the property bag is populated. The default implementation is a no-op. A web part developer can override this API if the deserialized object does not fully reflect the initial state of the property bag. This gives the web part developer a chance to populate the property bag right after the data is deserialized to an object. |
-|[`onAfterPropertyPaneChangesApplied()`](onafterpropertypanechangesapplied-baseclientsidewebpart.md)     | `protected` | `void` | This API is invoked after the changes made on the PropertyPane are applied when the PropertyPane is used in Non-Reactive mode. This API is not invoked when the PropertyPane is used in Reactive mode. |
-|[`onBeforeSerialize()`](onbeforeserialize-baseclientsidewebpart.md)     | `protected` | `void` | This API is called before the web part is serialized. The default implementation is a no-op. The serialization process serializes the web part property bag i.e. this.properties. This API gives the web part a chance to update it's property bag before the serialization happens. Some web part's may keep their state other objects or even in the DOM. If a web part needs to persist some of that state, it needs to override this API and update the web part property bag to the latest state. If a web part updates the property bag with invalid property values, those will get persisted. So that should be avoided. The web part property bag should always contain valid property values. |
-|[`onDisplayModeChanged(oldDisplayMode)`](ondisplaymodechanged-baseclientsidewebpart.md)     | `protected` | `void` | This API is called when the display mode of a web part is changed. The default implementation of this API calls the web part render method to re-render the web part with the new display mode. If a web part developer does not want a full re-render to happen on display mode change, they can override this API and perform specific updates to the web part DOM to switch its display mode. |
-|[`onDispose()`](ondispose-baseclientsidewebpart.md)     | `protected` | `void` | This API should be used to refresh the contents of the PropertyPane. This API is called at the end of the web part lifecycle on a page. It should be used to dispose any local resources (i.e. DOM elements) that the web part is holding onto. This API is expected to be called in scenarios like page navigation i.e. the host is transitioning from one page to another and disposes the page that is being transitioned out. |
-|[`onInit()`](oninit-baseclientsidewebpart.md)     | `protected` | [`Promise`](../../web-apis/class/promise.md)<void> | This API should be overridden to perform long running operations e.g. data fetching from a remote service before the initial rendering of the web part. The loading indicator is displayed during the lifetime of this method. This API is called only once during the lifecycle of a web part. |
-|[`onPropertyPaneConfigurationComplete()`](onpropertypaneconfigurationcomplete-baseclientsidewebpart.md)     | `protected` | `void` | This API is invoked when the configuration is completed on the PropertyPane. It's invoked in the following cases: - When the CONFIGURATION_COMPLETE_TIMEOUT((currently the value is 5 secs) elapses after the last change. - When user clicks 'x'(close) button before the CONFIGURATION_COMPLETE_TIMEOUT elapses. - When user clciks 'Apply' button before the CONFIGURATION_COMPLETE_TIMEOUT elapses. - When the user switches web parts then the current web part gets this event. |
-|[`onPropertyPaneConfigurationStart()`](onpropertypaneconfigurationstart-baseclientsidewebpart.md)     | `protected` | `void` | This API is invoked when the configuration starts on the PropertyPane. It's invoked in the following cases: - When the PropertyPane is opened. - When the user switches web parts then the new web part gets this event. |
-|[`onPropertyPaneFieldChanged(propertyPath,oldValue,newValue)`](onpropertypanefieldchanged-baseclientsidewebpart.md)     | `protected` | `void` | This API is invoked after updating the new value of the property in the property bag when the PropertyPane is being used in Reactive mode. |
-|[`onPropertyPaneRendered()`](onpropertypanerendered-baseclientsidewebpart.md)     | `protected` | `void` | This API is invoked when the PropertyPane is rendered. From framework standpoint, we do not want to allow this event handler to be passed in, and trigger it. This api should be deprecated and then removed as part of refactoring. |
-|[`render()`](render-baseclientsidewebpart.md)     | `protected` | `void` | This API is called to render the web part. There is no base implementation of this API and the web part is required to override this API. |
-|[`renderCompleted()`](rendercompleted-baseclientsidewebpart.md)     | `protected` | `void` | This API should be called by web parts that perform Async rendering. Those web part are required to override the isRenderAsync API and return true. One such example is web parts that render content in an IFrame. The web part initiates the IFrame rendering in the render() API but the actual rendering is complete only after the iframe loading completes. |
-|[`renderError(error)`](rendererror-baseclientsidewebpart.md)     | `protected` | `void` | This API should be used to render an error message in the web part display area. Also logs the error message using the trace logger. |
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/class/clearerror-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/clearerror-baseclientsidewebpart.md
deleted file mode 100644
index a1419ee822..0000000000
--- a/reference/spfx/sp-webpart-base/class/clearerror-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clearError()
-
-
-
-This API should be used to clear the error message from the web part display area.
-
-**Signature:** _protected clearError(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/getpropertypaneconfiguration-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/getpropertypaneconfiguration-baseclientsidewebpart.md
deleted file mode 100644
index 95782479c2..0000000000
--- a/reference/spfx/sp-webpart-base/class/getpropertypaneconfiguration-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getPropertyPaneConfiguration()
-
-
-
-This API is used to ger the configuration to build the property pane for the web part. If the web part wants to use the PropertyPane for configuration, this API needs to be overridden and the web part needs to return the configuration for the PropertyPane.
-
-**Signature:** _@virtual protected getPropertyPaneConfiguration(): [IPropertyPaneConfiguration](../../sp-webpart-base/interface/ipropertypaneconfiguration.md);_
-
-**Returns**: [`IPropertyPaneConfiguration`](../../sp-webpart-base/interface/ipropertypaneconfiguration.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onafterdeserialize-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onafterdeserialize-baseclientsidewebpart.md
deleted file mode 100644
index b027cebe64..0000000000
--- a/reference/spfx/sp-webpart-base/class/onafterdeserialize-baseclientsidewebpart.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# onAfterDeserialize(deserializedObject,dataVersion)
-
-
-
-This API is called after the web part is deserialized to an object, right before the property bag is populated. The default implementation is a no-op. A web part developer can override this API if the deserialized object does not fully reflect the initial state of the property bag. This gives the web part developer a chance to populate the property bag right after the data is deserialized to an object.
-
-**Signature:** _@virtual protected onAfterDeserialize(deserializedObject: any, data[Version](../../sp-core-library/class/version.md): Version): TProperties;_
-
-**Returns**: `TProperties`
-
-
-
-The property bag of the web part
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `deserializedObject`    | `any` | The object deserialized from the stored data. Note that the schema of this object is not necessarily consistent with the current property bag, because the serialization could have been done by an older version of the web part |
-| `dataVersion`    | [`Version`](../../sp-core-library/class/version.md) | The data version of the stored data being deserialized. You can use this value to determine if the data was serialized by an older web part. Web parts can define their data version by overriding the dataVersion property. |
-
-
-### Remarks
-
-An important scenario to use deserialize is upgrading. An upgraded web part may load the data that was serialized by an older version of the web part that supported a different schema of the property bag, resulting the deserialized object to be incosistent with the current schema of the property bag. The developer can use onAfterDeserialize to check the dataVersion and fix the property bag.
-
diff --git a/reference/spfx/sp-webpart-base/class/onafterpropertypanechangesapplied-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onafterpropertypanechangesapplied-baseclientsidewebpart.md
deleted file mode 100644
index 32fe3b8130..0000000000
--- a/reference/spfx/sp-webpart-base/class/onafterpropertypanechangesapplied-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onAfterPropertyPaneChangesApplied()
-
-
-
-This API is invoked after the changes made on the PropertyPane are applied when the PropertyPane is used in Non-Reactive mode. This API is not invoked when the PropertyPane is used in Reactive mode.
-
-**Signature:** _@virtual protected onAfterPropertyPaneChangesApplied(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onbeforeserialize-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onbeforeserialize-baseclientsidewebpart.md
deleted file mode 100644
index 2dc0cf0c21..0000000000
--- a/reference/spfx/sp-webpart-base/class/onbeforeserialize-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onBeforeSerialize()
-
-
-
-This API is called before the web part is serialized. The default implementation is a no-op. The serialization process serializes the web part property bag i.e. this.properties. This API gives the web part a chance to update it's property bag before the serialization happens. Some web part's may keep their state other objects or even in the DOM. If a web part needs to persist some of that state, it needs to override this API and update the web part property bag to the latest state. If a web part updates the property bag with invalid property values, those will get persisted. So that should be avoided. The web part property bag should always contain valid property values.
-
-**Signature:** _@virtual protected onBeforeSerialize(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/ondisplaymodechanged-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/ondisplaymodechanged-baseclientsidewebpart.md
deleted file mode 100644
index d20ad97d77..0000000000
--- a/reference/spfx/sp-webpart-base/class/ondisplaymodechanged-baseclientsidewebpart.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# onDisplayModeChanged(oldDisplayMode)
-
-
-
-This API is called when the display mode of a web part is changed. The default implementation of this API calls the web part render method to re-render the web part with the new display mode. If a web part developer does not want a full re-render to happen on display mode change, they can override this API and perform specific updates to the web part DOM to switch its display mode.
-
-**Signature:** _@virtual protected on[DisplayMode](../../sp-core-library/enum/displaymode.md)Changed(oldDisplayMode: DisplayMode): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `oldDisplayMode`    | [`DisplayMode`](../../sp-core-library/enum/displaymode.md) | The old display mode. |
-
-
diff --git a/reference/spfx/sp-webpart-base/class/ondispose-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/ondispose-baseclientsidewebpart.md
deleted file mode 100644
index f6b4d8db03..0000000000
--- a/reference/spfx/sp-webpart-base/class/ondispose-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onDispose()
-
-
-
-This API should be used to refresh the contents of the PropertyPane. This API is called at the end of the web part lifecycle on a page. It should be used to dispose any local resources (i.e. DOM elements) that the web part is holding onto. This API is expected to be called in scenarios like page navigation i.e. the host is transitioning from one page to another and disposes the page that is being transitioned out.
-
-**Signature:** _@virtual protected onDispose(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/oninit-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/oninit-baseclientsidewebpart.md
deleted file mode 100644
index d1d6592fb6..0000000000
--- a/reference/spfx/sp-webpart-base/class/oninit-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onInit()
-
-
-
-This API should be overridden to perform long running operations e.g. data fetching from a remote service before the initial rendering of the web part. The loading indicator is displayed during the lifetime of this method. This API is called only once during the lifecycle of a web part.
-
-**Signature:** _@virtual protected onInit(): [Promise](../../web-apis/class/promise.md)<void>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<void>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationcomplete-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationcomplete-baseclientsidewebpart.md
deleted file mode 100644
index 4c1bde2032..0000000000
--- a/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationcomplete-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onPropertyPaneConfigurationComplete()
-
-
-
-This API is invoked when the configuration is completed on the PropertyPane. It's invoked in the following cases: - When the CONFIGURATION_COMPLETE_TIMEOUT((currently the value is 5 secs) elapses after the last change. - When user clicks 'x'(close) button before the CONFIGURATION_COMPLETE_TIMEOUT elapses. - When user clciks 'Apply' button before the CONFIGURATION_COMPLETE_TIMEOUT elapses. - When the user switches web parts then the current web part gets this event.
-
-**Signature:** _@virtual protected onPropertyPaneConfigurationComplete(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationstart-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationstart-baseclientsidewebpart.md
deleted file mode 100644
index 384f2d27ff..0000000000
--- a/reference/spfx/sp-webpart-base/class/onpropertypaneconfigurationstart-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onPropertyPaneConfigurationStart()
-
-
-
-This API is invoked when the configuration starts on the PropertyPane. It's invoked in the following cases: - When the PropertyPane is opened. - When the user switches web parts then the new web part gets this event.
-
-**Signature:** _@virtual protected onPropertyPaneConfigurationStart(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onpropertypanefieldchanged-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onpropertypanefieldchanged-baseclientsidewebpart.md
deleted file mode 100644
index 87be147d31..0000000000
--- a/reference/spfx/sp-webpart-base/class/onpropertypanefieldchanged-baseclientsidewebpart.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# onPropertyPaneFieldChanged(propertyPath,oldValue,newValue)
-
-
-
-This API is invoked after updating the new value of the property in the property bag when the PropertyPane is being used in Reactive mode.
-
-**Signature:** _@virtual protected onPropertyPaneFieldChanged(propertyPath: string, oldValue: any, newValue: any): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `propertyPath`    | `string` | JSON path of the property in the property bag. In the case of custom field, if no target property is provided then a custom value is assigned, which will be in the form of '__CustomField_<key provided when the custom field is created>'. |
-| `oldValue`    | `any` | Old value of the property. This value could be undefined/empty in the case of custom field. |
-| `newValue`    | `any` | New value of the property. This value could be undefined/empty in the case of custom field. |
-
-
diff --git a/reference/spfx/sp-webpart-base/class/onpropertypanerendered-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/onpropertypanerendered-baseclientsidewebpart.md
deleted file mode 100644
index 1f7d09e1f6..0000000000
--- a/reference/spfx/sp-webpart-base/class/onpropertypanerendered-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# onPropertyPaneRendered()
-
-
-
-This API is invoked when the PropertyPane is rendered. From framework standpoint, we do not want to allow this event handler to be passed in, and trigger it. This api should be deprecated and then removed as part of refactoring.
-
-**Signature:** _@virtual protected onPropertyPaneRendered(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/render-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/render-baseclientsidewebpart.md
deleted file mode 100644
index a0be1cfbe7..0000000000
--- a/reference/spfx/sp-webpart-base/class/render-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# render()
-
-
-
-This API is called to render the web part. There is no base implementation of this API and the web part is required to override this API.
-
-**Signature:** _protected abstract render(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/rendercompleted-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/rendercompleted-baseclientsidewebpart.md
deleted file mode 100644
index 2f98e5066d..0000000000
--- a/reference/spfx/sp-webpart-base/class/rendercompleted-baseclientsidewebpart.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# renderCompleted()
-
-
-
-This API should be called by web parts that perform Async rendering. Those web part are required to override the isRenderAsync API and return true. One such example is web parts that render content in an IFrame. The web part initiates the IFrame rendering in the render() API but the actual rendering is complete only after the iframe loading completes.
-
-**Signature:** _protected renderCompleted(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/class/rendererror-baseclientsidewebpart.md b/reference/spfx/sp-webpart-base/class/rendererror-baseclientsidewebpart.md
deleted file mode 100644
index b8d01a7e2c..0000000000
--- a/reference/spfx/sp-webpart-base/class/rendererror-baseclientsidewebpart.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# renderError(error)
-
-
-
-This API should be used to render an error message in the web part display area. Also logs the error message using the trace logger.
-
-**Signature:** _protected renderError(error: Error): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `error`    | `Error` | An error object containing the error message to render. |
-
-
diff --git a/reference/spfx/sp-webpart-base/enum/propertypanebuttontype.md b/reference/spfx/sp-webpart-base/enum/propertypanebuttontype.md
deleted file mode 100644
index ad2b6d5601..0000000000
--- a/reference/spfx/sp-webpart-base/enum/propertypanebuttontype.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# PropertyPaneButtonType enumeration
-Enum for all the supported button types.
-
-| Member	   | Description|
-|:-------------|:-------|
-|`Command`       | Optional actions. Typically used in a command bar at the top of a view, panel and inside an inline command bar. Examples: Command bar at the top of OneDrive, Outlook, SharePoint. Inline command bar on the top of SharePoint web parts. |
-|`Compound`       | Always used as a set with both Standard and Primary compound buttons. Typically used in a confirmation dialog. Examples: A confirmation dialog when a user discards a form or task with a possible significant time investment such as an email or a complex form |
-|`Hero`       | Hero button. |
-|`Icon`       | Same usage as Command button, when real estate does not allow for icons + labels or as secondary actions within the command bar. Typically used in Command bar in small and medium responsive web breakpoints. Also used on objects. Examples: OneDrive small and medium responsive web breakpoint Command Bars and view icons within the Command Bar. In SharePoint and OneDrive, Cards with social actions and images which allow users to access the image picker. In SharePoint, formatting experiences such as formatting a story within the Authoring experience. In Calendar, in the bottom of an event creation Callout when clicking inside an empty time range. |
-|`Normal`       | Optional completion action. Typically used at the end of a form or task when paired with the Primary button OR as a standalone button to undo an action. Examples: "Done" button which closes a container but doesn't make a server call or an "Undo" button when a user is uploading a file in OneDrive. |
-|`Primary`       | Preferred completion action when paired with a Standard button. Typically used at the end of a task or form. Examples: "Create", "Save", "Send" which makes a server call. |
diff --git a/reference/spfx/sp-webpart-base/enum/propertypanefieldtype.md b/reference/spfx/sp-webpart-base/enum/propertypanefieldtype.md
deleted file mode 100644
index e7c7398847..0000000000
--- a/reference/spfx/sp-webpart-base/enum/propertypanefieldtype.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# PropertyPaneFieldType enumeration
-Enum for all the supported PropertyPane field types. Names should be consistent with those in office-ui-fabric-react, be careful to get letter casing correct.
-
-| Member	   | Description|
-|:-------------|:-------|
-|`Button` :=11      | Button field. |
-|`CheckBox` :=2      | Checkbox field. |
-|`ChoiceGroup` :=10      | Choice Group field. |
-|`Custom` :=1      | Custom field. |
-|`Dropdown` :=6      | Dropdown field. |
-|`Heading` :=9      | Heading field. |
-|`HorizontalRule` :=12      | Horizontal Rule field. |
-|`Label` :=7      | Label field. |
-|`Link` :=13      | Link field. |
-|`Slider` :=8      | Slider field. |
-|`TextField` :=3      | TextField field. |
-|`Toggle` :=5      | Toggle field. |
diff --git a/reference/spfx/sp-webpart-base/function/propertypanebutton.md b/reference/spfx/sp-webpart-base/function/propertypanebutton.md
deleted file mode 100644
index 4f0e811f73..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanebutton.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneButton(targetProperty,properties)
-
-
-
-Helper method to create a Button on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneButtonProps`](../../sp-webpart-base/interface/ipropertypanebuttonprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the Button is associated to. |
-| `properties`    | [`IPropertyPaneButtonProps`](../../sp-webpart-base/interface/ipropertypanebuttonprops.md) | Strongly typed Button properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanecheckbox.md b/reference/spfx/sp-webpart-base/function/propertypanecheckbox.md
deleted file mode 100644
index f90e76fcab..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanecheckbox.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneCheckbox(targetProperty,properties)
-
-
-
-Helper method to create a Checkbox on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneCheckboxProps`](../../sp-webpart-base/interface/ipropertypanecheckboxprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the checkbox is associated to. |
-| `properties`    | [`IPropertyPaneCheckboxProps`](../../sp-webpart-base/interface/ipropertypanecheckboxprops.md) | Strongly typed Checkbox properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanechoicegroup.md b/reference/spfx/sp-webpart-base/function/propertypanechoicegroup.md
deleted file mode 100644
index 3a9c4782ab..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanechoicegroup.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneChoiceGroup(targetProperty,properties)
-
-
-
-Helper method to create a Choice Group on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneChoiceGroupProps`](../../sp-webpart-base/interface/ipropertypanechoicegroupprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the choice group is associated to. |
-| `properties`    | [`IPropertyPaneChoiceGroupProps`](../../sp-webpart-base/interface/ipropertypanechoicegroupprops.md) | Strongly typed Choice Group properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanecustomfield.md b/reference/spfx/sp-webpart-base/function/propertypanecustomfield.md
deleted file mode 100644
index fd26aef8d9..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanecustomfield.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneCustomField(targetProperty,properties)
-
-> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._
-
-Helper method to create a custom field on the PropertyPane. The purpose of the custom field is to help the web part developer to add a custom control to the PropertyPane. The PropertyPane supports a host of inbuilt field types. While this list meets the demands of most web parts, but there are exceptional cases when web parts have special needs and need a special control. The custom field helps fill that gap.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneCustomFieldProps`](../../sp-webpart-base/interface/ipropertypanecustomfieldprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    |  | target property for this field. This parameter is being deprecated in future releases. |
-| `properties`    | [`IPropertyPaneCustomFieldProps`](../../sp-webpart-base/interface/ipropertypanecustomfieldprops.md) | Strongly typed Custom field properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanedropdown.md b/reference/spfx/sp-webpart-base/function/propertypanedropdown.md
deleted file mode 100644
index d86cc8b7e4..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanedropdown.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneDropdown(targetProperty,properties)
-
-
-
-Helper method to create a Dropdown on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneDropdownProps`](../../sp-webpart-base/interface/ipropertypanedropdownprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the dropdown is associated to. |
-| `properties`    | [`IPropertyPaneDropdownProps`](../../sp-webpart-base/interface/ipropertypanedropdownprops.md) | Strongly typed Dropdown properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanehorizontalrule.md b/reference/spfx/sp-webpart-base/function/propertypanehorizontalrule.md
deleted file mode 100644
index 4a009c11e2..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanehorizontalrule.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# PropertyPaneHorizontalRule(properties)
-
-
-
-Helper method to create a Horizontal Rule on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<void>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `properties`    |  | Strongly typed Horizontal Rule properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanelabel.md b/reference/spfx/sp-webpart-base/function/propertypanelabel.md
deleted file mode 100644
index 8423a62a0a..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanelabel.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneLabel(targetProperty,properties)
-
-
-
-Helper method to create a Label on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneLabelProps`](../../sp-webpart-base/interface/ipropertypanelabelprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the label is associated to. |
-| `properties`    | [`IPropertyPaneLabelProps`](../../sp-webpart-base/interface/ipropertypanelabelprops.md) | Strongly typed Label properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanelink.md b/reference/spfx/sp-webpart-base/function/propertypanelink.md
deleted file mode 100644
index 13e74a7b21..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanelink.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneLink(targetProperty,properties)
-
-
-
-Helper method to create a Link on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneLinkProps`](../../sp-webpart-base/interface/ipropertypanelinkprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the Link is associated to. |
-| `properties`    | [`IPropertyPaneLinkProps`](../../sp-webpart-base/interface/ipropertypanelinkprops.md) | Strongly typed Link properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypaneslider.md b/reference/spfx/sp-webpart-base/function/propertypaneslider.md
deleted file mode 100644
index f2c5244aaa..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypaneslider.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneSlider(targetProperty,properties)
-
-
-
-Helper method to create a Slider on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneSliderProps`](../../sp-webpart-base/interface/ipropertypanesliderprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the slider is associated to. |
-| `properties`    | [`IPropertyPaneSliderProps`](../../sp-webpart-base/interface/ipropertypanesliderprops.md) | Strongly typed Slider properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanetextfield.md b/reference/spfx/sp-webpart-base/function/propertypanetextfield.md
deleted file mode 100644
index 40d6676c4d..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanetextfield.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneTextField(targetProperty,properties)
-
-
-
-Helper method to create a TextField on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneTextFieldProps`](../../sp-webpart-base/interface/ipropertypanetextfieldprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the textfield is associated to. |
-| `properties`    | [`IPropertyPaneTextFieldProps`](../../sp-webpart-base/interface/ipropertypanetextfieldprops.md) | Strongly typed TextField properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/function/propertypanetoggle.md b/reference/spfx/sp-webpart-base/function/propertypanetoggle.md
deleted file mode 100644
index 0d3a315596..0000000000
--- a/reference/spfx/sp-webpart-base/function/propertypanetoggle.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# PropertyPaneToggle(targetProperty,properties)
-
-
-
-Helper method to create a Toggle on the PropertyPane.
-
-**Signature:** __
-
-**Returns**: [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<[`IPropertyPaneToggleProps`](../../sp-webpart-base/interface/ipropertypanetoggleprops.md)>
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `targetProperty`    | `string` | Target property the toggle is associated to. |
-| `properties`    | [`IPropertyPaneToggleProps`](../../sp-webpart-base/interface/ipropertypanetoggleprops.md) | Strongly typed Toggle properties. |
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/__index-iwebpartpropertiesmetadata.md b/reference/spfx/sp-webpart-base/interface/__index-iwebpartpropertiesmetadata.md
deleted file mode 100644
index 94e9e18bb9..0000000000
--- a/reference/spfx/sp-webpart-base/interface/__index-iwebpartpropertiesmetadata.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# index()
-
-
-
-
-
-**Signature:** _[ key: string ]: IWebPartPropertyMetadata;_
-
-**Returns**: `IWebPartPropertyMetadata`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/clearerror-iclientsidewebpartstatusrenderer.md b/reference/spfx/sp-webpart-base/interface/clearerror-iclientsidewebpartstatusrenderer.md
deleted file mode 100644
index e323be6b1f..0000000000
--- a/reference/spfx/sp-webpart-base/interface/clearerror-iclientsidewebpartstatusrenderer.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# clearError(domElement)
-
-
-
-Clear the webpart error message.
-
-**Signature:** _clearError(domElement: HTMLElement): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `domElement`    | `HTMLElement` | the webpart container div. |
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/clearloadingindicator-iclientsidewebpartstatusrenderer.md b/reference/spfx/sp-webpart-base/interface/clearloadingindicator-iclientsidewebpartstatusrenderer.md
deleted file mode 100644
index 02bfff17db..0000000000
--- a/reference/spfx/sp-webpart-base/interface/clearloadingindicator-iclientsidewebpartstatusrenderer.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# clearLoadingIndicator(domElement)
-
-
-
-Clear the loading indicator.
-
-**Signature:** _clearLoadingIndicator(domElement: Element): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `domElement`    | `Element` | the webpart container div. |
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/displayloadingindicator-iclientsidewebpartstatusrenderer.md b/reference/spfx/sp-webpart-base/interface/displayloadingindicator-iclientsidewebpartstatusrenderer.md
deleted file mode 100644
index 77ab7b36bc..0000000000
--- a/reference/spfx/sp-webpart-base/interface/displayloadingindicator-iclientsidewebpartstatusrenderer.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# displayLoadingIndicator(domElement,loadingMessage,timeout)
-
-
-
-Display a loading spinner.
-
-**Signature:** _displayLoadingIndicator(domElement: Element, loadingMessage: string, timeout?: number): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `domElement`    | `Element` | the webpart container div. |
-| `loadingMessage`    | `string` | the message to be displayed when the loading spinner id displayed. |
-| `timeout`    | `number` | _Optional._ timeout to render the loading indicator. Default is 900ms. |
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md b/reference/spfx/sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md
deleted file mode 100644
index 8aec8ee034..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# IClientSideWebPartStatusRenderer interface
-
-
-
-
-
-
-
-Interface to be implemented by a component that should display the loading indicator and error messages for a webpart.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`clearError(domElement)`](clearerror-iclientsidewebpartstatusrenderer.md)      | `void` | Clear the webpart error message. |
-|[`clearLoadingIndicator(domElement)`](clearloadingindicator-iclientsidewebpartstatusrenderer.md)      | `void` | Clear the loading indicator. |
-|[`displayLoadingIndicator(domElement,loadingMessage,timeout)`](displayloadingindicator-iclientsidewebpartstatusrenderer.md)      | `void` | Display a loading spinner. |
-|[`renderError(domElement,error)`](rendererror-iclientsidewebpartstatusrenderer.md)      | `void` | Render the provided error message in the webpart container div. |
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iplaceholderspinnerprops.md b/reference/spfx/sp-webpart-base/interface/iplaceholderspinnerprops.md
deleted file mode 100644
index b09da1b638..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iplaceholderspinnerprops.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IPlaceholderSpinnerProps interface
-
-
-
-
-
-
-
-Interface for properties used to display the loading spinner in the web part display area.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`hideSpinner`      | `boolean` | Hide spinner at start if set to true. In such case, use state showSpinner to true when to show the spinner |
-|`label`      | `string` | Label associated with the spinner. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypaneaccessor.md b/reference/spfx/sp-webpart-base/interface/ipropertypaneaccessor.md
deleted file mode 100644
index c40f302ec6..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypaneaccessor.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# IPropertyPaneAccessor interface
-
-
-
-
-
-
-
-Web part context property pane accessor interface. Provides some most commonly used utilities to access the property pane.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`isPropertyPaneOpen()`](ispropertypaneopen-ipropertypaneaccessor.md)      | `boolean` | Returns true if the PropertyPane is open. |
-|[`isRenderedByWebPart()`](isrenderedbywebpart-ipropertypaneaccessor.md)      | `boolean` | Indicates whether the PropertyPane was initially opened by the web part. For example, if the web part calls this.context.propertyPane.open() then the property would be true, whereas if the property pane was opened by the host, then the value will be false. |
-|[`open()`](open-ipropertypaneaccessor.md)      | `void` | This API should be used to open the PropertyPane to help configure the web part. |
-|[`refresh()`](refresh-ipropertypaneaccessor.md)      | `void` | This API should be used to invoke the PropertyPane to help configure the web part. This operation only works when the PropertyPane is already open for the currently active web part. If the PropertyPane is opened for another web part, calling the refresh API will have no impact. |
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanebuttonprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanebuttonprops.md
deleted file mode 100644
index 4d075f222e..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanebuttonprops.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# IPropertyPaneButtonProps interface
-
-
-
-
-
-
-
-PropertyPane button props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ariaDescription`      | `string` | Detailed description of the button for the benefit of screen readers. Besides the compound button, other button types will need more information provided to screen reader. |
-|`ariaLabel`      | `string` | The aria label of the button for the benefit of screen readers. |
-|`buttonType`      | [`PropertyPaneButtonType`](../../sp-webpart-base/enum/propertypanebuttontype.md) | The type of button to render. Default value is ButtonType.normal. |
-|`description`      | `string` | Description of the action this button takes. Only used for compound buttons. |
-|`disabled`      | `boolean` | Whether the button is disabled. |
-|`icon`      | `string` | The button icon shown in command or hero type. |
-|`onClick`      | `(value: any) => any` | A callback which is invoked on the button click, which takes in the existing value for the bound property and returns the new value and which is then used to update the properties bag. This update will result in the re-render of the PropertyPane with the new props. |
-|`text`      | `string` | Display text of the element. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanecheckboxprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanecheckboxprops.md
deleted file mode 100644
index c31b261361..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanecheckboxprops.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# IPropertyPaneCheckboxProps interface
-
-
-
-
-
-
-
-PropertyPane CheckBox component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`checked`      | `boolean` | Whether the property pane checkbox is checked or not. Default value is false. |
-|`disabled`      | `boolean` | Whether the property pane checkbox is disabled or not. |
-|`text`      | `string` | Label to display next to the checkbox. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoption.md b/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoption.md
deleted file mode 100644
index 6916250cae..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoption.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# IPropertyPaneChoiceGroupOption interface
-
-
-
-
-
-
-
-PropertyPane ChoiceGroup option props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`checked`      | `boolean` | Whether the property pane choicegroup option is checked or not. Default value is false. |
-|`disabled`      | `boolean` | Whether the property pane choice group option is disabled or not. |
-|`iconProps`      | [`IPropertyPaneChoiceGroupOptionIconProps`](../../sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md) | The Icon component props for choice field. |
-|`imageSize`      | `{ width: number`,` height: number }` | The width and height of the image in px for choice field. |
-|`imageSrc`      | `string` | The src of image for choice field. |
-|`key`      | `string `,` number` | A required key to uniquely identify the option. |
-|`selectedImageSrc`      | `string` | The src of image for choice field which is selected. |
-|`text`      | `string` | The text string for the option. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md
deleted file mode 100644
index 40f2414b63..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupoptioniconprops.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# IPropertyPaneChoiceGroupOptionIconProps interface
-
-
-
-
-
-
-
-PropertyPane ChoiceGroup icon props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`officeFabricIconFontName`      | `string `,` null` | The name of the icon to use from th office fabric icon set. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupprops.md
deleted file mode 100644
index 77f1d80fed..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanechoicegroupprops.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IPropertyPaneChoiceGroupProps interface
-
-
-
-
-
-
-
-PropertyPane ChoiceGroup props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`label`      | `string` | Descriptive label for the choice group. |
-|`options`      | [`IPropertyPaneChoiceGroupOption`](../../sp-webpart-base/interface/ipropertypanechoicegroupoption.md)[] | The options for the choice group. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypaneconfiguration.md b/reference/spfx/sp-webpart-base/interface/ipropertypaneconfiguration.md
deleted file mode 100644
index 98bbe73994..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypaneconfiguration.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# IPropertyPaneConfiguration interface
-
-
-
-
-
-
-
-Web part configuration settings
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`currentPage`      | `number` | Page to be displayed on the PropertyPane. |
-|`loadingIndicatorDelayTime`      | `number` | Number of milli seconds to be delayed before the loading indicator is shown on the property pane. default is 500. |
-|`pages`      | [`IPropertyPanePage`](../../sp-webpart-base/interface/ipropertypanepage.md)[] | Total number of pages on the PropertyPane. |
-|`showLoadingIndicator`      | `boolean` | Indicates whether the loading indicator should be displayed on top of the property pane or not. This feature is intended to be used when the user is waiting on a promise to resolve. If set to true, overlay loading indicator appears after 500ms (web part author can override this behavior by using overlayLoadingIndicator property). The reason why we are not showing it immediately is that our intent is to never show the loading indicator. But in real life async requests could take long and it becomes necessary to display a loading indicator to the end user. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanecustomfieldprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanecustomfieldprops.md
deleted file mode 100644
index adce287784..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanecustomfieldprops.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# IPropertyPaneCustomFieldProps interface
-
-
-
-
-
-
-
-PropertyPane CustomPropertyField props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`context`      | `any` | Instance specific context. This context is passed back to the web part in the onRender and onDispose APIs. The web part can use this context to manage state information. |
-|`key`      | `string` | An UNIQUE key indicates the identity of this contorl. The PropertyPane uses ReactJS to render its components. ReactJS uses keys to identify a component and if it should be re-rendered or not. This is a performance feature in ReactJS. Please read the following link to understand how to pick the value of the key. |
-|`onDispose`      | `(domElement: HTMLElement, context?: any) => void` | This API is called when the component is unmounted from the host element. |
-|`onRender`      | `(
-    domElement: HTMLElement,
-    context?: any,
-    changeCallback?: (targetProperty?: string, newValue?: any) => void) => void` | This API will be called once the custom field is mounted on the host element. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownoption.md b/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownoption.md
deleted file mode 100644
index 405133bb4b..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownoption.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# IPropertyPaneDropdownOption interface
-
-
-
-
-
-
-
-PropertyPane drop down options.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`index`      | `number` | Index for this option. |
-|`key`      | `string `,` number` | A key to uniquely identify this option. |
-|`text`      | `string` | Text to render for this option. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownprops.md
deleted file mode 100644
index 5f5da3384c..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanedropdownprops.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# IPropertyPaneDropdownProps interface
-
-
-
-
-
-
-
-PropertyPane drop down component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`disabled`      | `boolean` | Whether the property pane dropdown option is disabled or not. |
-|`label`      | `string` | Descriptive label for the Dropdown. |
-|`options`      | [`IPropertyPaneDropdownOption`](../../sp-webpart-base/interface/ipropertypanedropdownoption.md)[] | Collection of options for this Dropdown. |
-|`selectedKey`      | `string `,` number` | The key of the initially selected option. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanefield.md b/reference/spfx/sp-webpart-base/interface/ipropertypanefield.md
deleted file mode 100644
index 45d82dcccb..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanefield.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# IPropertyPaneField <TProperties> interface
-
-
-
-_Type parameters: `<TProperties>`_
-
-
-
-PropertyPane field.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`properties`      | `TProperties` | Strongly typed properties object. Specific to each field type. Example: Checkbox has ICheckboxProps, TextField has ITextField props. |
-|`shouldFocus`      | `boolean` | Whether this control should be focused. default value is false. |
-|`targetProperty`      | `string` | Target property from the web part's property bag. |
-|`type`      | [`PropertyPaneFieldType`](../../sp-webpart-base/enum/propertypanefieldtype.md) | Type of the PropertyPane field. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanegroup.md b/reference/spfx/sp-webpart-base/interface/ipropertypanegroup.md
deleted file mode 100644
index 13e769ac37..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanegroup.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# IPropertyPaneGroup interface
-
-
-
-
-
-
-
-PropertyPane group. Group is part of the PropertyPanePage.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`groupFields`      | [`IPropertyPaneField`](../../sp-webpart-base/interface/ipropertypanefield.md)<any>[] | List of PropertyPane fields. |
-|`groupName`      | `string` | Display name for the group. For performance reasons, it's highly recommended to keep this name unique within the property pane page. |
-|`isCollapsed`      | `boolean` | Indicates whether the PropertyPane group is collapsed or not. Defaullt: false |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanelabelprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanelabelprops.md
deleted file mode 100644
index a0cb681bdc..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanelabelprops.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IPropertyPaneLabelProps interface
-
-
-
-
-
-
-
-PropertyPaneLabel component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`required`      | `boolean` | Whether the associated form field is required or not. If true, a red asterisk is displayed to the right of the label. Default value is false. |
-|`text`      | `string` | Display text fot the label. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanelinkprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanelinkprops.md
deleted file mode 100644
index a588a6f121..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanelinkprops.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# IPropertyPaneLinkProps interface
-
-
-
-
-
-
-
-PropertyPaneLink component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`disabled`      | `boolean` | Whether the property pane link is disabled or not. |
-|`href`      | `string` | Location to which the link is targetted to. |
-|`popupWindowProps`      | `IPopupWindowProps` | The props of pop up window. |
-|`target`      | `string` | This attribute specifies where to display the linked resource. Following values can be used: _self - (default) Load the response in the current page. _blank - Load the response into a new unnamed tab. _parent - Load the response in the parent of the current page. If no parent exists, then this option behaves same as '_self' _top - Load the response into the original window. |
-|`text`      | `string` | Display text for the link. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanepage.md b/reference/spfx/sp-webpart-base/interface/ipropertypanepage.md
deleted file mode 100644
index aba0592436..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanepage.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# IPropertyPanePage interface
-
-
-
-
-
-
-
-PropertyPanePage interface.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`displayGroupsAsAccordion`      | `boolean` | Indicates whether the groups on the PropertyPanePage are displayed as accordion or not. |
-|`groups`      | [`IPropertyPaneGroup`](../../sp-webpart-base/interface/ipropertypanegroup.md)[] | List of groups to be displayed on the PropertyPane page. |
-|`header`      | [`IPropertyPanePageHeader`](../../sp-webpart-base/interface/ipropertypanepageheader.md) | PropertyPane page header. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanepageheader.md b/reference/spfx/sp-webpart-base/interface/ipropertypanepageheader.md
deleted file mode 100644
index df4bf4b1cd..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanepageheader.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IPropertyPanePageHeader interface
-
-
-
-
-
-
-
-PropertyPane header. This header remains same for all the pages.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`description`      | `string` | Header to display. |
-|`image`      | `string` | Image url for the background image. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanesliderprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanesliderprops.md
deleted file mode 100644
index 9cd05f3f24..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanesliderprops.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# IPropertyPaneSliderProps interface
-
-
-
-
-
-
-
-PropertyPaneSliderProps component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ariaLabel`      | `string` | A description of the Slider for the benefit of screen readers. |
-|`disabled`      | `boolean` | Whether or not the Slider is disabled. |
-|`label`      | `string` | Description label of the Slider. |
-|`max`      | `number` | The max value of the Slider. |
-|`min`      | `number` | The min value of the Slider. |
-|`showValue`      | `boolean` | Whether to show the value on the right of the Slider. If you want to show the value by yourself, you may want to set this value to false. |
-|`step`      | `number` | The difference between the two adjacent values of the Slider. Defaults to 1. |
-|`value`      | `number` | The initial value of the Slider. Use this if you intend to pass in a new value as a result of onChange events. Defaults to min. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanetextfieldprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanetextfieldprops.md
deleted file mode 100644
index d5f149c731..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanetextfieldprops.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# IPropertyPaneTextFieldProps interface
-
-
-
-
-
-
-
-PropertyPaneTextField component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`ariaLabel`      | `string` | Aria Label for textfield, if any. |
-|`deferredValidationTime`      | `number` | Text field will start to validate after users stop typing for `deferredValidationTime` milliseconds. Default value is 200. |
-|`description`      | `string` | The textfield input description. |
-|`disabled`      | `boolean` | Whether the property pane textfield is enabled or not. |
-|`errorMessage`      | `string` | If set, this will be displayed as an error message. When onGetErrorMessage returns empty string, if this property has a value set then this will be displayed as the error message. So, make sure to set this only if you want to see an error message dispalyed for the text field. |
-|`label`      | `string` | Label for the textfield. |
-|`maxLength`      | `number` | Maximum number of characters that the PropertyPaneTextField can have. (If the value is set to a negative number, an exception will be thrown.) |
-|`multiline`      | `boolean` | Whether or not the textfield is a multiline textfield. Default value is false. |
-|`onGetErrorMessage`      | `(value: string) => string `, [`Promise`](../../web-apis/class/promise.md)<string> | The method is used to get the validation error message and determine whether the input value is valid or not. When it returns string: - If valid, it returns empty string. - If invalid, it returns the error message string and an error message is displayed below the text field. When it returns Promise<string>: - The resolved value is display as error message. - The rejected, the value is thrown away. |
-|`placeholder`      | `string` | placeholder text to be displayed in the Textfield. |
-|`resizable`      | `boolean` | Whether or not the multiline textfield is resizable. Default value is true. |
-|`rows`      | `number` | Specifies the visible height of a text area(multiline text TextField), in lines. This prop is used only when the multiline prop is set to true. |
-|`underlined`      | `boolean` | Whether or not the textfield is underlined. Default value is false. |
-|`validateOnFocusIn`      | `boolean` | Run validation when the PropertyPaneTextField is focused. default value is false |
-|`validateOnFocusOut`      | `boolean` | Run validation when the PropertyPaneTextField is out of focus or on blur. default value is false |
-|`value`      | `string` | Value to be displayed in the textfield when the value of the targetProperty in the manifest's property bag is empty or contains null value. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ipropertypanetoggleprops.md b/reference/spfx/sp-webpart-base/interface/ipropertypanetoggleprops.md
deleted file mode 100644
index e5eddacb63..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ipropertypanetoggleprops.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# IPropertyPaneToggleProps interface
-
-
-
-
-
-
-
-PropertyPaneToggle component props.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`checked`      | `boolean` | Checked state of the toggle. If you are maintaining state yourself, use this property. |
-|`disabled`      | `boolean` | Optional disabled flag. |
-|`key`      | `string `,` number` | A key to uniquely identify the field. |
-|`label`      | `string` | A label for the toggle. |
-|`offText`      | `string` | Test display when toggle is OFF. |
-|`onText`      | `string` | Text to display when toggle is ON. |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iserializedserverprocesseddata.md b/reference/spfx/sp-webpart-base/interface/iserializedserverprocesseddata.md
deleted file mode 100644
index 185c4a1180..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iserializedserverprocesseddata.md
+++ /dev/null
@@ -1,27 +0,0 @@
-# ISerializedServerProcessedData interface
-
-
-
-
-
-
-
-Contains collections of data that can be processed by server side services like search index and link fixup
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`htmlStrings`      | `{ [key: string]: string }` | A key-value map where keys are string identifiers and values are rich text with HTML format. SharePoint servers treat the values as HTML content and run services like safety checks, search index and link fixup on them. Example: { 'myRichDescription': '<div>Some standard <b>HTML content</b><a href='http://somelink'>A Link</a></div>' 'anotherRichText': <div class='aClass'><span style='color:red'>Some red text</div> } |
-|`imageSources`      | `{ [key: string]: string }` | A key-value map where keys are string identifiers and values are image sources. SharePoint servers treat the values as image sources and run services like search index and link fixup on them. Example: { 'myImage1': 'http://res.contoso.com/path/to/file' 'myImage2': 'https://res.contoso.com/someName.jpg' } |
-|`links`      | `{ [key: string]: string }` | A key-value map where keys are string identifiers and values are links. SharePoint servers treat the values as links and run services like link fixup on them. Example: { 'myWebURL': 'http://contoso.com' 'myFileLink': 'https://res.contoso.com/file.docx' } |
-|`searchablePlainTexts`      | `{ [key: string]: string }` | A key-value map where keys are string identifiers and values are strings that should be search indexed. The values are html-encoded before being sent to the server. The encoded values are visible to the search indexer, but are not treated as valid html. So, other services such as link fixup will not run on them. Example: { 'justSomeText': 'This is some plain text', 'anotherText': 'Can have <any> characters here: "<>&\'' } |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iserializedwebpartdata.md b/reference/spfx/sp-webpart-base/interface/iserializedwebpartdata.md
deleted file mode 100644
index f33861e363..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iserializedwebpartdata.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# ISerializedWebPartData interface
-
-
-
-
-
-
-
-This structure represents the part of the serialized state of a web part which is controlled by the web part. It is extended by IWebPartData which contains additional data added by the framework to the serialized data.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`dataVersion`      | [`Version`](../../sp-core-library/class/version.md) | Definition: Web part data version. Note that data version is different from the version field in the manifest. The manifest version is used to control the versioning of the web part code, while data version is used to control the versioning of the serialized data of the web part. Refer to dataVersion field of your web part for more information. Usage: versioning and evolving the serialized data of the web part Required: yes Type: Version Supported values: MAJOR.MINOR Example: "1.0" |
-|`properties`      | `any` | Definition: Web part specific properties. The individual web part owns the definition of these properties. Usage: used by the web part to manage its internal metadata and config data. The framework code never touches these properties. Required: yes Type: any Supported values: any JSON stringifiable object hierarchy. Example: { 'value': 'text value' } |
-|`serverProcessedContent`      | [`ISerializedServerProcessedData`](../../sp-webpart-base/interface/iserializedserverprocesseddata.md) | Definition: The collections of data that can be processed by server side services like search index and link fixup Required: no |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/ispropertypaneopen-ipropertypaneaccessor.md b/reference/spfx/sp-webpart-base/interface/ispropertypaneopen-ipropertypaneaccessor.md
deleted file mode 100644
index 5e04172c05..0000000000
--- a/reference/spfx/sp-webpart-base/interface/ispropertypaneopen-ipropertypaneaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# isPropertyPaneOpen()
-
-
-
-Returns true if the PropertyPane is open.
-
-**Signature:** _isPropertyPaneOpen(): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/isrenderedbywebpart-ipropertypaneaccessor.md b/reference/spfx/sp-webpart-base/interface/isrenderedbywebpart-ipropertypaneaccessor.md
deleted file mode 100644
index 388752ce93..0000000000
--- a/reference/spfx/sp-webpart-base/interface/isrenderedbywebpart-ipropertypaneaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# isRenderedByWebPart()
-
-
-
-Indicates whether the PropertyPane was initially opened by the web part. For example, if the web part calls this.context.propertyPane.open() then the property would be true, whereas if the property pane was opened by the host, then the value will be false.
-
-**Signature:** _isRenderedByWebPart(): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iwebpartcontext.md b/reference/spfx/sp-webpart-base/interface/iwebpartcontext.md
deleted file mode 100644
index d1aa86ea13..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iwebpartcontext.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# IWebPartContext interface
-
-
-
-
-
-
-
-The base context interface for client-side web parts.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`domElement`      | `HTMLElement` | Reference to the DOM element that hosts this client side component. |
-|`graphHttpClient`      | [`GraphHttpClient`](../../sp-http/class/graphhttpclient.md) | GraphHttpClient instance scoped to this web part.<br/> _This API is provided as a preview for developers and may change based on feedback that we receive.  Do not use this API in a production environment._ |
-|`httpClient`      | [`HttpClient`](../../sp-http/class/httpclient.md) | HttpClient instance scoped to this web part. |
-|`instanceId`      | `string` | Web part instance id. This is a globally unique value. |
-|`manifest`      | `IClientSideWebPartManifestInstance<any>` | Manifest for the client side web part. |
-|`pageContext`      | [`PageContext`](../../sp-page-context/class/pagecontext.md) | SharePoint page context. |
-|`propertyPane`      | [`IPropertyPaneAccessor`](../../sp-webpart-base/interface/ipropertypaneaccessor.md) | Accessor for common web part property pane operations. |
-|`spHttpClient`      | [`SPHttpClient`](../../sp-http/class/sphttpclient.md) | SPHttpClient instance scoped to this web part. |
-|`statusRenderer`      | [`IClientSideWebPartStatusRenderer`](../../sp-webpart-base/interface/iclientsidewebpartstatusrenderer.md) | Web part status renderer. |
-|`webPartTag`      | `string` | Web part tag to be used for logging and telemetry. |
-
-
-
-
-
-
-### Remarks
-
-A "context" object is a collection of well-known services and other objects that are likely to be needed by any business logic working with a component. Each component type has its own specialized extension of this interface, e.g. IWebPartContext for web parts, IExtensionContext for client-side extensions, etc.
-
diff --git a/reference/spfx/sp-webpart-base/interface/iwebpartdata.md b/reference/spfx/sp-webpart-base/interface/iwebpartdata.md
deleted file mode 100644
index 6d0de39b7f..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iwebpartdata.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# IWebPartData interface
-
-
-
-
-
-
-
-This structure represents the serialized state of a web part. When the serialize() API is called on a web part, the output should be this structure. The structure of the 'properties' field is owned by the web part and is specific to the web part. Each web part can decide the set of properties it wants to serialialize.
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`dataVersion`      | `string` | Definition: Web part data version. Note that data version is different from the version field in the manifest. The manifest version is used to control the versioning of the web part code, while data version is used to control the versioning of the serialized data of the web part. Refer to dataVersion field of your web part for more information. Usage: versioning and evolving the serialized data of the web part Required: yes Type: string Supported values: MAJOR.MINOR Example: "1.0" |
-|`description`      | `string` | Definition: web part description. Usage: display the description of the web part. Required: no Type: string Supported values: string with the description. Example: "Text" |
-|`id`      | `string` | Definition: universally unique web part Type id. Usage: uniquely identify a web part. Required: yes Type: GUID Supported values: any GUID Example: "dbef608d-3ad5-4f8f-b139-d916f2f0a294" |
-|`instanceId`      | `string` | Definition: universally unique instance id of the web part. A web part can have multiple instances on a page. This id is expected to be universally unique accross time and page boundaries. how used: used by the framework to uniquely identify an instance of a web part. mandatory: yes type: string supported values: a unique string. Could be GUID or other uniquely identifiable formats. example: ["dbef608d-3ad5-4f8f-b139-d916f2f0a294"] experimental: yes |
-|`properties`      | `any` | Definition: Web part specific properties. The individual web part owns the definition of these properties. Usage: used by the web part to manage its internal metadata and config data. The framework code never touches these properties. Required: yes Type: any Supported values: any JSON stringifiable object hierarchy. Example: { 'value': 'text value' } |
-|`serverProcessedContent`      | [`ISerializedServerProcessedData`](../../sp-webpart-base/interface/iserializedserverprocesseddata.md) | Definition: The collections of data that can be processed by server side services like search index and link fixup Required: no |
-|`title`      | `string` | Definition: web part title. Usage: display the name of the web part in the toolbox, web part gallery and the page. Required: yes Type: string Supported values: string less than 100 characters Example: "Text" |
-
-
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/iwebpartpropertiesmetadata.md b/reference/spfx/sp-webpart-base/interface/iwebpartpropertiesmetadata.md
deleted file mode 100644
index 055a7a6f89..0000000000
--- a/reference/spfx/sp-webpart-base/interface/iwebpartpropertiesmetadata.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# IWebPartPropertiesMetadata interface
-
-
-
-
-
-
-
-This structure is used to define metadata for web part propeties as a map of string to IWebPartPropertyMetadata The key should be a json path to the property in web part propeties. The json path supports the following operators: - Dot . for selecting object members e.g. person.name - Brackets [] for selecting array items e.g. person.photoURLs[0] - Bracketed asterisk [*] for array elements wildcard e.g. person.websites[*]. You can make combinations of these operators e.g. person.websites[*].url Important Note: Only one wildcard per path is supported. Example: Let's assume we have a web part with properties that have the following schema: { title: string; person: { name: string; bio: string; photoURLs: string[]; websites: { title: string; url: string; }[] } } We can define the metadata for the desired properties as following: { 'person.bio': { isRichContent: true }, 'person.photoURLs[*]': { isImageSource: true }, 'person.websites[*].url': { isLink: true } } This will make SharePoint servers aware of the content of your properties and run services such as search indexing, link fix-up, etc on the data. In case any of the values needs to update by these services, e.g link fix-up, the web part property bag is automatically updated.
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`index()`](__index-iwebpartpropertiesmetadata.md)      | `IWebPartPropertyMetadata` |  |
-
-
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/open-ipropertypaneaccessor.md b/reference/spfx/sp-webpart-base/interface/open-ipropertypaneaccessor.md
deleted file mode 100644
index e02bbe20ad..0000000000
--- a/reference/spfx/sp-webpart-base/interface/open-ipropertypaneaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# open()
-
-
-
-This API should be used to open the PropertyPane to help configure the web part.
-
-**Signature:** _open(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/refresh-ipropertypaneaccessor.md b/reference/spfx/sp-webpart-base/interface/refresh-ipropertypaneaccessor.md
deleted file mode 100644
index f9d7871112..0000000000
--- a/reference/spfx/sp-webpart-base/interface/refresh-ipropertypaneaccessor.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# refresh()
-
-
-
-This API should be used to invoke the PropertyPane to help configure the web part. This operation only works when the PropertyPane is already open for the currently active web part. If the PropertyPane is opened for another web part, calling the refresh API will have no impact.
-
-**Signature:** _refresh(): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/sp-webpart-base/interface/rendererror-iclientsidewebpartstatusrenderer.md b/reference/spfx/sp-webpart-base/interface/rendererror-iclientsidewebpartstatusrenderer.md
deleted file mode 100644
index 7606aab45e..0000000000
--- a/reference/spfx/sp-webpart-base/interface/rendererror-iclientsidewebpartstatusrenderer.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# renderError(domElement,error)
-
-
-
-Render the provided error message in the webpart container div.
-
-**Signature:** _renderError(domElement: HTMLElement, error: Error | string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-
-
-| Parameter	   | Type    | Description |
-|:-------------|:---------------|:------------|
-| `domElement`    | `HTMLElement` | the webpart container div. |
-| `error`    | `Error `,` string` | the error message. |
-
-
diff --git a/reference/spfx/web-apis-module.md b/reference/spfx/web-apis-module.md
deleted file mode 100644
index cc028c3aeb..0000000000
--- a/reference/spfx/web-apis-module.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# web-apis package
-
-
-
-
-
-
-## Classes
-
-| Class	   |  Description |
-|:-------------|:---------------|
-| [`Body`](./web-apis/class/body.md)     |  |
-| [`Headers`](./web-apis/class/headers.md)     |  |
-| [`Promise`](./web-apis/class/promise.md)     |  |
-| [`Request`](./web-apis/class/request.md)     |  |
-| [`Response`](./web-apis/class/response.md)     |  |
-
-
-
-## Interfaces
-
-| Interface	   |  Description |
-|:-------------|:---------------|
-| [`HeadersMap`](./web-apis/interface/headersmap.md)   |   |
-| [`RequestInit`](./web-apis/interface/requestinit.md)   |   |
-| [`ResponseInit`](./web-apis/interface/responseinit.md)   |   |
-| [`Thenable`](./web-apis/interface/thenable.md)   |   |
-| [`Window`](./web-apis/interface/window.md)   |   |
-
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/all-promise.md b/reference/spfx/web-apis/class/all-promise.md
deleted file mode 100644
index f0f602e501..0000000000
--- a/reference/spfx/web-apis/class/all-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# all()
-
-
-
-
-
-**Signature:** _public static all < T1, T2, T3, T4, T5, T6, T7, T8, T9, T10 >(values: [T1 | [Thenable](../../web-apis/interface/thenable.md)<T1>, T2 | Thenable<T2>, T3 | Thenable<T3>, T4 | Thenable <T4>, T5 | Thenable<T5>, T6 | Thenable<T6>, T7 | Thenable<T7>, T8 | Thenable<T8>, T9 | Thenable<T9>, T10 | Thenable<T10>]): [Promise](../../web-apis/class/promise.md)<[T1, T2, T3, T4, T5, T6, T7, T8, T9, T10]>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[T1, T2, T3, T4, T5, T6, T7, T8, T9, T10]>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/append-headers.md b/reference/spfx/web-apis/class/append-headers.md
deleted file mode 100644
index e7cbac2f59..0000000000
--- a/reference/spfx/web-apis/class/append-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# append()
-
-
-
-
-
-**Signature:** _append(name: string, value: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/arraybuffer-body.md b/reference/spfx/web-apis/class/arraybuffer-body.md
deleted file mode 100644
index 837c93dccc..0000000000
--- a/reference/spfx/web-apis/class/arraybuffer-body.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# arrayBuffer()
-
-
-
-
-
-**Signature:** _arrayBuffer(): [Promise](../../web-apis/class/promise.md)<ArrayBuffer>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<ArrayBuffer>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/blob-body.md b/reference/spfx/web-apis/class/blob-body.md
deleted file mode 100644
index 7c2f43e458..0000000000
--- a/reference/spfx/web-apis/class/blob-body.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# blob()
-
-
-
-
-
-**Signature:** _blob(): [Promise](../../web-apis/class/promise.md)<Blob>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<Blob>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/body.md b/reference/spfx/web-apis/class/body.md
deleted file mode 100644
index f94856afcb..0000000000
--- a/reference/spfx/web-apis/class/body.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Body class
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`bodyUsed`     | `public` | `boolean` |  |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`arrayBuffer()`](arraybuffer-body.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<ArrayBuffer> |  |
-|[`blob()`](blob-body.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<Blob> |  |
-|[`formData()`](formdata-body.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<FormData> |  |
-|[`json()`](json-body.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<any> |  |
-|[`text()`](text-body.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<string> |  |
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/catch-promise.md b/reference/spfx/web-apis/class/catch-promise.md
deleted file mode 100644
index 9ae7aaa19a..0000000000
--- a/reference/spfx/web-apis/class/catch-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# catch()
-
-
-
-
-
-**Signature:** _catch < U >(onRejected?: (error: any) => U | [Thenable](../../web-apis/interface/thenable.md)<U>): [Promise](../../web-apis/class/promise.md)<U>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<U>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/clone-response.md b/reference/spfx/web-apis/class/clone-response.md
deleted file mode 100644
index 1083f50a9b..0000000000
--- a/reference/spfx/web-apis/class/clone-response.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# clone()
-
-
-
-
-
-**Signature:** _clone(): [Response](../../web-apis/class/response.md);_
-
-**Returns**: [`Response`](../../web-apis/class/response.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/delete-headers.md b/reference/spfx/web-apis/class/delete-headers.md
deleted file mode 100644
index cb21aa3009..0000000000
--- a/reference/spfx/web-apis/class/delete-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# delete()
-
-
-
-
-
-**Signature:** _delete(name: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/error-response.md b/reference/spfx/web-apis/class/error-response.md
deleted file mode 100644
index 0491357597..0000000000
--- a/reference/spfx/web-apis/class/error-response.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# error()
-
-
-
-
-
-**Signature:** _static error(): [Response](../../web-apis/class/response.md);_
-
-**Returns**: [`Response`](../../web-apis/class/response.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/foreach-headers.md b/reference/spfx/web-apis/class/foreach-headers.md
deleted file mode 100644
index 3af7915c10..0000000000
--- a/reference/spfx/web-apis/class/foreach-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# forEach()
-
-
-
-
-
-**Signature:** _forEach(callback: (value: string, name: string) => void): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/formdata-body.md b/reference/spfx/web-apis/class/formdata-body.md
deleted file mode 100644
index 08b166b607..0000000000
--- a/reference/spfx/web-apis/class/formdata-body.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# formData()
-
-
-
-
-
-**Signature:** _formData(): [Promise](../../web-apis/class/promise.md)<FormData>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<FormData>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/get-headers.md b/reference/spfx/web-apis/class/get-headers.md
deleted file mode 100644
index 153585b9c5..0000000000
--- a/reference/spfx/web-apis/class/get-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# get()
-
-
-
-
-
-**Signature:** _get(name: string): string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/getall-headers.md b/reference/spfx/web-apis/class/getall-headers.md
deleted file mode 100644
index 30ebb9db63..0000000000
--- a/reference/spfx/web-apis/class/getall-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# getAll()
-
-
-
-
-
-**Signature:** _getAll(name: string): Array<string>;_
-
-**Returns**: `Array<string>`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/has-headers.md b/reference/spfx/web-apis/class/has-headers.md
deleted file mode 100644
index 45bfb6797d..0000000000
--- a/reference/spfx/web-apis/class/has-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# has()
-
-
-
-
-
-**Signature:** _has(name: string): boolean;_
-
-**Returns**: `boolean`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/headers.md b/reference/spfx/web-apis/class/headers.md
deleted file mode 100644
index b56897cbdc..0000000000
--- a/reference/spfx/web-apis/class/headers.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Headers class
-
-
-
-
-
-
-
-
-
-
-## Constructor
-
-
-**Signature:** _constructor(headers?:[Headers](../../web-apis/class/headers.md)|[HeadersMap](../../web-apis/interface/headersmap.md))_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`append()`](append-headers.md)     | `` | `void` |  |
-|[`delete()`](delete-headers.md)     | `` | `void` |  |
-|[`forEach()`](foreach-headers.md)     | `` | `void` |  |
-|[`get()`](get-headers.md)     | `` | `string` |  |
-|[`getAll()`](getall-headers.md)     | `` | `Array<string>` |  |
-|[`has()`](has-headers.md)     | `` | `boolean` |  |
-|[`set()`](set-headers.md)     | `` | `void` |  |
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/json-body.md b/reference/spfx/web-apis/class/json-body.md
deleted file mode 100644
index 57fc1faa63..0000000000
--- a/reference/spfx/web-apis/class/json-body.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# json()
-
-
-
-
-
-**Signature:** _json(): [Promise](../../web-apis/class/promise.md)<any>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<any>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/promise.md b/reference/spfx/web-apis/class/promise.md
deleted file mode 100644
index a92ceee06a..0000000000
--- a/reference/spfx/web-apis/class/promise.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Promise <T> class
-
-_Implements: [`Thenable`](../../web-apis/interface/thenable.md)_
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-## Constructor
-
-
-**Signature:** _constructor(callback: (resolve: (value?: T | [Thenable](../../web-apis/interface/thenable.md)<T>) => void, reject: (error?: any) => void) => void);_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`all()`](all-promise.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<[T1, T2, T3, T4, T5, T6, T7, T8, T9, T10]> |  |
-|[`catch()`](catch-promise.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<U> |  |
-|[`race()`](race-promise.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<T> |  |
-|[`reject()`](reject-promise.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<any> |  |
-|[`resolve()`](resolve-promise.md)     | `public, static` | [`Promise`](../../web-apis/class/promise.md)<T> |  |
-|[`then()`](then-promise.md)     | `` | [`Promise`](../../web-apis/class/promise.md)<U> |  |
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/race-promise.md b/reference/spfx/web-apis/class/race-promise.md
deleted file mode 100644
index 6644eb0648..0000000000
--- a/reference/spfx/web-apis/class/race-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# race()
-
-
-
-
-
-**Signature:** _public static race < T >(promises: (T | [Thenable](../../web-apis/interface/thenable.md)<T>)[]): [Promise](../../web-apis/class/promise.md)<T>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/redirect-response.md b/reference/spfx/web-apis/class/redirect-response.md
deleted file mode 100644
index 953b3a31d2..0000000000
--- a/reference/spfx/web-apis/class/redirect-response.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# redirect()
-
-
-
-
-
-**Signature:** _static redirect(url: string, status: number): [Response](../../web-apis/class/response.md);_
-
-**Returns**: [`Response`](../../web-apis/class/response.md)
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/reject-promise.md b/reference/spfx/web-apis/class/reject-promise.md
deleted file mode 100644
index 5e873d3f9d..0000000000
--- a/reference/spfx/web-apis/class/reject-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# reject()
-
-
-
-
-
-**Signature:** _public static reject(error: any): [Promise](../../web-apis/class/promise.md)<any>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<any>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/request.md b/reference/spfx/web-apis/class/request.md
deleted file mode 100644
index 75d51d7956..0000000000
--- a/reference/spfx/web-apis/class/request.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Request class
-
-
-
-
-
-
-
-
-
-
-## Constructor
-
-
-**Signature:** _constructor(input: string|[Request](../../web-apis/class/request.md), init?:[RequestInit](../../web-apis/interface/requestinit.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`cache`     | `public` | `RequestCache` |  |
-|`context`     | `public` | `RequestContext` |  |
-|`credentials`     | `public` | `RequestCredentials` |  |
-|`headers`     | `public` | [`Headers`](../../web-apis/class/headers.md) |  |
-|`method`     | `public` | `string` |  |
-|`mode`     | `public` | `RequestMode` |  |
-|`redirect`     | `public` | `RequestRedirect` |  |
-|`referrer`     | `public` | `string` |  |
-|`url`     | `public` | `string` |  |
-
-
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/resolve-promise.md b/reference/spfx/web-apis/class/resolve-promise.md
deleted file mode 100644
index ce9a824e8c..0000000000
--- a/reference/spfx/web-apis/class/resolve-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# resolve()
-
-
-
-
-
-**Signature:** _public static resolve < T >(value?: T | [Thenable](../../web-apis/interface/thenable.md)<T>): [Promise](../../web-apis/class/promise.md)<T>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<T>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/response.md b/reference/spfx/web-apis/class/response.md
deleted file mode 100644
index 4e687fc68c..0000000000
--- a/reference/spfx/web-apis/class/response.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# Response class
-
-
-
-
-
-
-
-
-
-
-## Constructor
-
-
-**Signature:** _constructor(body?: BodyInit, init?: [ResponseInit](../../web-apis/interface/responseinit.md));_
-
-**Returns**: 
-
-
-
-#### Parameters
-None
-
-
-## Properties
-
-| Property	   | Access Modifier | Type	| Description|
-|:-------------|:----|:-------|:-----------|
-|`headers`     | `public` | [`Headers`](../../web-apis/class/headers.md) |  |
-|`ok`     | `public` | `boolean` |  |
-|`status`     | `public` | `number` |  |
-|`statusText`     | `public` | `string` |  |
-|`type`     | `public` | `ResponseType` |  |
-|`url`     | `public` | `string` |  |
-
-
-
-
-## Methods
-
-| Method	   | Access Modifier | Returns	| Description|
-|:-------------|:----|:-------|:-----------|
-|[`clone()`](clone-response.md)     | `` | [`Response`](../../web-apis/class/response.md) |  |
-|[`error()`](error-response.md)     | `, static` | [`Response`](../../web-apis/class/response.md) |  |
-|[`redirect()`](redirect-response.md)     | `, static` | [`Response`](../../web-apis/class/response.md) |  |
-
-
-
-
-
diff --git a/reference/spfx/web-apis/class/set-headers.md b/reference/spfx/web-apis/class/set-headers.md
deleted file mode 100644
index dea06c6c07..0000000000
--- a/reference/spfx/web-apis/class/set-headers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# set()
-
-
-
-
-
-**Signature:** _set(name: string, value: string): void;_
-
-**Returns**: `void`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/text-body.md b/reference/spfx/web-apis/class/text-body.md
deleted file mode 100644
index fed30d58a8..0000000000
--- a/reference/spfx/web-apis/class/text-body.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# text()
-
-
-
-
-
-**Signature:** _text(): [Promise](../../web-apis/class/promise.md)<string>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<string>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/class/then-promise.md b/reference/spfx/web-apis/class/then-promise.md
deleted file mode 100644
index 422b7fea6f..0000000000
--- a/reference/spfx/web-apis/class/then-promise.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# then()
-
-
-
-
-
-**Signature:** _then < U >(onFulfilled?: (value: T) => U | [Thenable](../../web-apis/interface/thenable.md)<U>, onRejected?: (error: any) => U | Thenable<U>): [Promise](../../web-apis/class/promise.md)<U>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<U>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/interface/__index-headersmap.md b/reference/spfx/web-apis/interface/__index-headersmap.md
deleted file mode 100644
index bf9c8d79b9..0000000000
--- a/reference/spfx/web-apis/interface/__index-headersmap.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# index()
-
-
-
-
-
-**Signature:** _[ index: string ]: string;_
-
-**Returns**: `string`
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/interface/fetch-window.md b/reference/spfx/web-apis/interface/fetch-window.md
deleted file mode 100644
index b0e0d96680..0000000000
--- a/reference/spfx/web-apis/interface/fetch-window.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# fetch()
-
-
-
-
-
-**Signature:** _fetch(url: string|[Request](../../web-apis/class/request.md), init?: [RequestInit](../../web-apis/interface/requestinit.md)): [Promise](../../web-apis/class/promise.md)<[Response](../../web-apis/class/response.md)>;_
-
-**Returns**: [`Promise`](../../web-apis/class/promise.md)<[`Response`](../../web-apis/class/response.md)>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/interface/headersmap.md b/reference/spfx/web-apis/interface/headersmap.md
deleted file mode 100644
index a4cc7e647f..0000000000
--- a/reference/spfx/web-apis/interface/headersmap.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# HeadersMap interface
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`index()`](__index-headersmap.md)      | `string` |  |
-
-
-
-
diff --git a/reference/spfx/web-apis/interface/requestinit.md b/reference/spfx/web-apis/interface/requestinit.md
deleted file mode 100644
index fb45461b9a..0000000000
--- a/reference/spfx/web-apis/interface/requestinit.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# RequestInit interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`body`      | `BodyInit` |  |
-|`cache`      | `RequestCache` |  |
-|`credentials`      | `RequestCredentials` |  |
-|`headers`      | `HeaderInit`,`{ [index: string]: string }` |  |
-|`method`      | `string` |  |
-|`mode`      | `RequestMode` |  |
-|`redirect`      | `RequestRedirect` |  |
-
-
-
-
-
-
diff --git a/reference/spfx/web-apis/interface/responseinit.md b/reference/spfx/web-apis/interface/responseinit.md
deleted file mode 100644
index 7c85d933a0..0000000000
--- a/reference/spfx/web-apis/interface/responseinit.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# ResponseInit interface
-
-
-
-
-
-
-
-
-
-
-
-
-## Properties
-
-| Property	   | Type	| Description|
-|:-------------|:-------|:-----------|
-|`headers`      | `HeaderInit` |  |
-|`status`      | `number` |  |
-|`statusText`      | `string` |  |
-
-
-
-
-
-
diff --git a/reference/spfx/web-apis/interface/then-thenable.md b/reference/spfx/web-apis/interface/then-thenable.md
deleted file mode 100644
index f8a01f35a8..0000000000
--- a/reference/spfx/web-apis/interface/then-thenable.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# then()
-
-
-
-
-
-**Signature:** _then < U >(onFulfilled?: (value: T) => U | [Thenable](../../web-apis/interface/thenable.md)<U>, onRejected?: (error: any) => U | Thenable<U>): Thenable<U>;_
-
-**Returns**: [`Thenable`](../../web-apis/interface/thenable.md)<U>
-
-
-
-
-
-#### Parameters
-None
-
-
diff --git a/reference/spfx/web-apis/interface/thenable.md b/reference/spfx/web-apis/interface/thenable.md
deleted file mode 100644
index 18ec231724..0000000000
--- a/reference/spfx/web-apis/interface/thenable.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Thenable <T> interface
-
-
-
-_Type parameters: `<T>`_
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`then()`](then-thenable.md)      | [`Thenable`](../../web-apis/interface/thenable.md)<U> |  |
-
-
-
-
diff --git a/reference/spfx/web-apis/interface/window.md b/reference/spfx/web-apis/interface/window.md
deleted file mode 100644
index eb4d6bf920..0000000000
--- a/reference/spfx/web-apis/interface/window.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Window interface
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Methods
-
-| Method	   |  Returns	| Description|
-|:-------------|:-------|:-----------|
-|[`fetch()`](fetch-window.md)      | [`Promise`](../../web-apis/class/promise.md)<[`Response`](../../web-apis/class/response.md)> |  |
-
-
-
-