chore: reflect latest workspace guide tooling

Author: NathanWalker

content/guide/code-sharing.md

@@ -25,9 +25,9 @@ If a "code sharing solution" is maintained by a framework that can often mean th
 
 ## Code Sharing Solutions
 
-Here are a few solitions to **code-sharing**, each having their pros and cons.
+Here are a few solutions to **code-sharing**, each having their pros and cons.
 
-### Nrwl Nx DevTools with @nativescript/nx
+### Nx with @nativescript/nx
 
 [Learn More about @nativescript/nx](https://github.com/NativeScript/nx)
 
@@ -42,28 +42,10 @@ Here are a few solitions to **code-sharing**, each having their pros and cons.
 
 - Learning curve if not used to Nx practices in general
 
-### Nrwl Nx DevTools with @nstudio/xplat
+### npm or yarn workspaces
 
-[Learn more about @nstudio/xplat](https://nstudio.io/xplat)
-
-**Pros:**
-
-- It's centered around JavaScript/TypeScript (lesson 1 and 5 above)
-- Uses standard build tooling like TypeScript or webpack to build code (lesson 2 above)
-- No custom file extensions to deal with (lesson 3 above)
-- Nx splits up "apps" and "libs" clearly identifying deployment/distribution targets "apps" that consume shared code "libs" (lesson 4 above)
-- It builds upon @nativescript/nx to further scale it across more paradigms so it's a natural extension when needed if already working in Nx with @nativescript/nx
-- Opinionated architecture is provided via xplat which helps to avoid common pitfalls from hard lessons learned in real world developments with cross platform mixtures
-
-**Cons:**
-
-- Learning curve if not used to Nx practices in general
-- Learning curve if you have not developed applications in large codebases before
-- Understanding the [basic fundamentals](https://nstudio.io/xplat/fundamentals/architecture) of the provided architecture
-
-### Yarn workspaces
-
-[Learn more about Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/)
+- [Learn more about npm workspaces](https://docs.npmjs.com/cli/using-npm/workspaces/)
+- [Learn more about Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/)
 
 **Pros:**
 

content/plugins/plugin-workspace-guide.md

@@ -128,7 +128,7 @@ At the prompt, enter the name of the package to add an `angular` folder to it wi
 One of the nice benefits of using our plugin workspaces is updating them is made simple and efficient through Nx tooling. The TSC maintains plugin workspace migrations so whenever one is available you can update your plugin workspace with just a few simple commands (which will often provide dependency version bumps of supporting packages to latest NativeScript versions, configuration improvements, as well as other welcome additions to help you create and maintain NativeScript plugins):
 
 ```bash
-yarn nx migrate @nativescript/plugin-tools
+npx nx migrate @nativescript/plugin-tools
 ```
 
 That will fetch `latest` version of `plugin-tools`, analyze the package to see if any migrations are available and then print a message if there are migrations to run.
@@ -137,10 +137,10 @@ Sometimes `@nativescript/plugin-tools` updates won't need any migrations so you
 
 ```bash
 // install latest updates
-yarn
+npm install
 
 // now run the migrations
-yarn nx migrate --run-migrations=migrations.json
+npx nx migrate --run-migrations=migrations.json
 ```
 
 Your plugin workspace will now be up to date regarding various configurations, settings and core dependencies. Depending on other customizations you made there may be other things to adjust on your own.
@@ -161,7 +161,7 @@ Not very often actually. Most plugin workspaces can maintain it's set of depende
 - TypeScript 5.6+
 - Angular 19+
 
-If you have any angular specific parts to your plugin, after running `yarn nx migrate @nativescript/plugin-tools` and then `yarn nx migrate --run-migrations ` with this migration you may see TypeScript errors like this:
+If you have any angular specific parts to your plugin, after running `npx nx migrate @nativescript/plugin-tools` and then `npx nx migrate --run-migrations ` with this migration you may see TypeScript errors like this:
 
 ```bash
 nativescript-checkbox/angular/index.ts:75:18 - error NG6008: Directive CheckedValueAccessor is standalone, and cannot be declared in an NgModule. Did you mean to import it instead?
@@ -184,7 +184,7 @@ This is expected with Angular 19. To resolve you can just add an explicit `stand
 
 - Migrates to Nx 18.2.3, NativeScript 8.6, and TypeScript ~5.4.x.
 
-After running `yarn nx migrate @nativescript/plugin-tools` and then `yarn nx migrate --run-migrations ` with this migration you'll likely see this message:
+After running `npx nx migrate @nativescript/plugin-tools` and then `npx nx migrate --run-migrations ` with this migration you'll likely see this message:
 
 ```bash
 [!] Some files can't be patched! You can run again with --verbose to get specific error detail. The following files are unable to be patched: