Merge pull request #2639 from Pankaj-Thakur/patch-3

Update finance-operations-faq.md
MicrosoftDocs · Jul 5, 2024 · 4a72941 · 4a72941
2 parents dfc9d11 + 0cab376
commit 4a72941
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 5 deletions.
diff --git a/power-platform/developer/unified-experience/finance-operations-faq.md b/power-platform/developer/unified-experience/finance-operations-faq.md
@@ -174,7 +174,6 @@ Learn more about observability: [Monitoring and telemetry using Application Insi
 
 ### See also
 
-
 [Unified Development Experience for Finance and Operations | Dynamics 365 FastTrack Tech Talk Dev](https://www.youtube.com/watch?v=OuEZ1rXkpYY)  
 [Unified developer experience for finance and operations apps](finance-operations-dev-overview.md)  
 [Install and configure development tools](finance-operations-install-config-tools.md)  

diff --git a/power-platform/developer/unified-experience/finance-operations-innerloop.md b/power-platform/developer/unified-experience/finance-operations-innerloop.md
@@ -21,7 +21,6 @@ Let's start by talking about a development machine with multiple unified develop
 
 ## Multiple unified development environments
 
-s
 A developer machine can be used to connect to multiple unified development environments. However, an instance of Visual Studio can at any time be connected to only one environment and have only one metadata configuration active. You can switch the active configuration using the menu item **Extensions** > **Dynamics 365** > **Configure Metadata**.
 
 Switching the active metadata configuration doesn't change the environment you're connected to. You can change it from the Visual Studio menu item **Tools** > **Connect to Dataverse**.

diff --git a/power-platform/developer/unified-experience/finance-operations-pipelines.md b/power-platform/developer/unified-experience/finance-operations-pipelines.md
@@ -43,10 +43,11 @@ Optionally, you can choose to generate a separate Lifecycle Services format pack
 
     :::image type="content" source="../media/unified-experience/pipelines-locate-artifacts.png" alt-text="Image of solution artifacts in Azure DevOps.":::
 
-> [!NOTE]
-> If you see the error - 'An item with the specified name c:\3c5d3d3b-4428-4901-9357-4559d510e2a8\modelName already exists.' please ensure that you do not have duplicate modules as only 1 version per module is accepted.
+   > [!NOTE]
+   > If you see this error:<p/>
+   > 'An item with the specified name <initial drive path>\3c5d3d3b-4428-4901-9357-4559d510e2a8\<model> already exists.' <p/>
+   > please ensure that you do not have duplicate modules as only 1 version per module is accepted.
 
-
 ## Link to your deploy pipeline
 
 Follow these next instructions to link to your deployment pipeline.