fix(isolation): distDir -> frontendDist

Author: FabianLars

src/content/docs/concept/Inter-Process Communication/isolation.md

@@ -56,7 +56,7 @@ Because the point of the Isolation application is to protect against Development
 
 In this example, we will make a small hello-world style Isolation application and hook it up to an imaginary existing Tauri application. It will do no verification of the messages passing through it, only print the contents to the WebView console.
 
-For the purposes of this example, let's imagine we are in the same directory as `tauri.conf.json`. The existing Tauri application has it's `distDir` set to `../dist`.
+For the purposes of this example, let's imagine we are in the same directory as `tauri.conf.json`. The existing Tauri application has its `frontendDist` set to `../dist`.
 
 `../dist-isolation/index.html`:
 
@@ -87,12 +87,12 @@ Now, all we need to do is set up our `tauri.conf.json` [configuration](#configur
 
 ## Configuration
 
-Let's assume that our main frontend `distDir` is set to `../dist`. We also output our Isolation application to `../dist-isolation`.
+Let's assume that our main frontend `frontendDist` is set to `../dist`. We also output our Isolation application to `../dist-isolation`.
 
 ```json
 {
   "build": {
-    "distDir": "../dist"
+    "frontendDist": "../dist"
   },
   "app": {
     "security": {