SharePoint · Ashlesha-MSFT · Jun 22, 2026 · Jun 22, 2026 · Jun 22, 2026 · Jun 22, 2026
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
@@ -12,7 +12,7 @@ This article describes how you can batch queries and operations against the REST
 
 ## Executive summary of the $batch option
 
-SharePoint Online (and on-premises SharePoint 2016 and later) and the Office 365 APIs implement the OData  `$batch` query option, so you can rely on [the official documentation](https://www.odata.org/documentation/odata-version-3-0/batch-processing) for details about how to use it. (Another option is to see Andrew Connell's blog posts on the subject beginning at [Part 1 - SharePoint REST API Batching](https://www.voitanos.io/blog/part-1-sharepoint-rest-api-batching-understanding-batching-requests).)
+SharePoint Online (and on-premises SharePoint 2016 and later) and the Office 365 APIs implement the OData  `$batch` query option, so you can rely on [the official documentation](https://www.odata.org/documentation/odata-version-3-0/batch-processing) for details about how to use it.
 
 The following is a reminder of the major points:
 

diff --git a/docs/spfx/set-up-your-development-environment-gulp-toolchain.md b/docs/spfx/set-up-your-development-environment-gulp-toolchain.md
@@ -152,7 +152,6 @@ The SPFx build toolchain will replace this value on the fly with a value defined
 
 Developers can use the `SPFX_SERVE_TENANT_DOMAIN` OS environment variable to specify the tenant domain (or site URL) for serve configurations across different SPFx solutions. If a URL in the serve configuration (for example, `pageUrl` for Field Customizer) contains the `{tenantDomain}` placeholder, it will be automatically replaced with the variable's value.
 
-For more information on how to set the environment variable on your developer environment, including Windows or macOS, see [Setting the SharePoint Framework Hosted Workbench Test Site](https://www.voitanos.io/blog/set-spfx-hosted-workbench-test-site/).
 
 ## Optional tools
 
@@ -190,8 +189,7 @@ Depending on your scenario, you may need to maintain different development envir
 - Node version managers
 
 > [!TIP]
-> For more information on Node version managers, see [Better Node.js Install Management with Node Version Manager](https://www.voitanos.io/blog/better-node-js-install-management-with-node-version-manager/).
->
+> For more information on Node version managers.
 > - [Node Version Manager (NVM)](https://github.com/creationix/nvm): for macOS
 > - [Fast Node Manager (FNM)](https://github.com/Schniz/fnm): cross-platform (Windows and MacOS)
 > - [Node Version Switcher (NVS)](https://github.com/jasongin/nvs): cross-platform (Windows and MacOS)
@@ -218,7 +216,7 @@ In case the certificate is not added to the Trusted Root Certification Authority
 
 ### Unable to Install Packages with npm - Corporate Proxies
 
-If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [Configure npm for a corporate web proxy](https://www.voitanos.io/blog/node-npm-fix-proxy-config/)
+If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. 
 
 ## See also
 

diff --git a/docs/spfx/set-up-your-development-environment.md b/docs/spfx/set-up-your-development-environment.md
@@ -140,7 +140,6 @@ The SPFx build toolchain will replace this value on the fly with a value defined
 
 Developers can use the `SPFX_SERVE_TENANT_DOMAIN` OS environment variable to specify the tenant domain (or site URL) for serve configurations across different SPFx solutions. If a URL in the serve configuration (for example, `pageUrl` for Field Customizer) contains the `{tenantDomain}` placeholder, it will be automatically replaced with the variable's value.
 
-For more information on how to set the environment variable on your developer environment, including Windows or macOS, see [Setting the SharePoint Framework Hosted Workbench Test Site](https://www.voitanos.io/blog/set-spfx-hosted-workbench-test-site/).
 
 ## Optional tools
 
@@ -168,8 +167,6 @@ Depending on your scenario, you may need to maintain different development envir
 - Node version managers
 
 > [!TIP]
-> For more information on node version managers, see [Better Node.js Install Management with Node Version Manager](https://www.voitanos.io/blog/better-node-js-install-management-with-node-version-manager/).
->
 > - [Node Version Manager (NVM)](https://github.com/creationix/nvm): for macOS
 > - [Fast Node Manager (FNM)](https://github.com/Schniz/fnm): cross-platform (Windows and MacOS)
 > - [Node Version Switcher (NVS)](https://github.com/jasongin/nvs): cross-platform (Windows and MacOS)
@@ -196,7 +193,7 @@ In case the certificate is not added to the Trusted Root Certification Authority
 
 ### Unable to Install Packages with npm - Corporate Proxies
 
-If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. More information: [Configure npm for a corporate web proxy](https://www.voitanos.io/blog/node-npm-fix-proxy-config/)
+If your development environment is behind a corporate proxy, you need to configure npm to use that proxy. Refer to the [npm-config](https://docs.npmjs.com/misc/config) documents on how to configure your development environment behind a corporate proxy... specifically the **proxy** & **http-proxy** settings. 
 
 ## See also
 

diff --git a/docs/spfx/sharepoint-2016-support.md b/docs/spfx/sharepoint-2016-support.md
@@ -107,4 +107,3 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc
 - [SharePoint Framework Legacy Toolchain: Gulp & Webpack](toolchain/sharepoint-framework-toolchain.md)
 - [Set up your SharePoint Framework Gulp-Based development environment](set-up-your-development-environment-gulp-toolchain.md)
 - [SharePoint Framework development tools and libraries compatibility](compatibility.md)
-- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2016](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2016/)
diff --git a/docs/spfx/sharepoint-2019-and-subscription-edition-support.md b/docs/spfx/sharepoint-2019-and-subscription-edition-support.md
@@ -131,5 +131,3 @@ For more information, see [issue #1002](https://github.com/SharePoint/sp-dev-doc
 - [SharePoint Server 2019 development platform](../general-development/sharepoint-2019-development-platform.md).
 - [SharePoint Framework Legacy Toolchain: Gulp & Webpack](toolchain/sharepoint-framework-toolchain.md)
 - [Set up your SharePoint Framework Gulp-Based development environment](set-up-your-development-environment-gulp-toolchain.md)
-- [Definitive guide for developers: SharePoint Framework for SharePoint Server 2019](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-2019/).
-- [Definitive guide for developers: SharePoint Framework for SharePoint Server SE](https://www.voitanos.io/blog/definitive-guide-sharepoint-framework-sharepoint-server-subscription-edition/).
diff --git a/docs/spfx/sharepoint-framework-why.md b/docs/spfx/sharepoint-framework-why.md
@@ -37,7 +37,3 @@ Historically, developers created web parts as full trust C# assemblies that were
 However, current development models usually involve JavaScript running in a browser making REST API calls to the SharePoint and Microsoft 365 back-end workloads. C# assemblies don’t work in this world. Developers needed a new development model.
 
 The SharePoint Framework is the next evolution in SharePoint development.
-
-## See Also
-
-- [Why did Microsoft create the SharePoint Framework (SPFx)?](https://www.voitanos.io/blog/spfx-5w1h-why-did-microsoft-create-sharepoint-framework/)
diff --git a/docs/spfx/toolchain/configure-sass.md b/docs/spfx/toolchain/configure-sass.md
@@ -66,5 +66,4 @@ Refer to the Heft Sass plugin documentation for more information how to configur
 - [SharePoint Framework v1.16.1 release notes](../release-1.16.1.md)
 - [Heft-based toolchain (SPFx v1.22.0+)](sharepoint-framework-toolchain-rushstack-heft.md)
 - [Gulp-based toolchain (legacy)](sharepoint-framework-toolchain.md)
-- [Stefan Bauer: What’s new with SASS in SPFx v1.16.0](https://n8d.at/whats-new-with-sass-in-spfx-1-16-0)\
-- [Andrew Connell: Unboxing the SharePoint Framework (SPFx) v1.16.1 release](https://www.voitanos.io/blog/sharepoint-framework-v1-16-1-whats-in-latest-update-of-spfx/)
+- [Stefan Bauer: What’s new with SASS in SPFx v1.16.0](https://n8d.at/whats-new-with-sass-in-spfx-1-16-0)
diff --git a/docs/spfx/toolchain/customize-heft-toolchain-overview.md b/docs/spfx/toolchain/customize-heft-toolchain-overview.md
@@ -32,7 +32,7 @@ npx @rushstack/heft --help
 ```
 
 > [!TIP]
-> Similar to Gulp, Heft is installed locally within your project. However, [unlike Gulp that requires installing the Gulp CLI globally](https://www.voitanos.io/blog/mea-culpa-always-install-gulp-cli-globally-not-gulp/), you can install the same Heft npm package globally to simplify running Heft commands.
+> Similar to Gulp, Heft is installed locally within your project. If you prefer, you can also install Heft globally to simplify running Heft commands.
 >
 > ```console
 > npm install @rushstack/heft --global