Fix broken link, locale URLs, xref, frontmatter key, and table formatting (#265)

docs: fix broken link, locale URLs, malformed xref, frontmatter key, and table formatting

- Fix empty link [DAX formula dependencies]() → xref:formula-fix-up-dependencies
- Fix non-English locale URLs: en-ie → en-us (tmdl.md), da-dk → en-us (Power-BI-Desktop-Integration.md)
- Fix malformed xref with space: "xref: desktop-limitations" → "xref:desktop-limitations"
- Fix invalid frontmatter key: "applies to:" → "applies_to:" (Power-BI-Desktop-Integration.md)
- Add missing closing | on 4 table rows (Command-line-Options, code-actions, editions)
- Fix stray ] → | typo in shortcuts3.md table

Found via automated doc linter (10 findings across 7 files).

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: eugman

content/features/Command-line-Options.md

@@ -292,7 +292,7 @@ The command line provides various details, depending on the switches used and an
 |Error|(Any)|Error loading file: ...|The file is corrupt or does not contain valid TOM metadata in a JSON format|
 |Error|(Any)|Error loading model: ...|Not able to connect to the provided Analysis Services instance, database not found, database metadata corrupt or database not of a supported compatibility level|
 |Error|-SCRIPT|Specified script file not found||
-|Error|-SCRIPT|Script compilation errors:|Script contained invalid C# syntax. Details will be outputted on the following lines.
+|Error|-SCRIPT|Script compilation errors:|Script contained invalid C# syntax. Details will be outputted on the following lines.|
 |Error|-SCRIPT|Script execution error: ...|Unhandled exception when executing the script.|
 |Information|-SCRIPT|Script line #: ...|Use of the `Info(string)` or `Output(string)` methods within the script.|
 |Warning|-SCRIPT|Script warning: ...|Use of the `Warning(string)` method within the script.|

content/features/code-actions.md

@@ -86,7 +86,7 @@ The Code Actions below will appear with orange dots under the first two characte
 | -- | --- | --- |
 | DI001 | [Remove unused variable](xref:DI001) | Variables not referenced anywhere should be removed. Example:<br>`VAR a = 1 VAR b = 2 RETURN a` -> `VAR a = 1 RETURN a` |
 | DI002 | [Remove all unused variables](xref:DI002) | Variables that are not being used (directly or indirectly through other variables) in the `RETURN` part of a variable block should be removed. Example:<br>`VAR a = 1 VAR b = a RETURN 123` -> `123` |
-| DI003 | [Remove table name](xref:DI003) | Measure references should not include the table name, as the table name is unnecessary when referencing measures. Moreover, this practice makes measure references more easily distinguishable from column references. Example:<br>`Sales[Total Sales]` -> `[Total Sales]` 
+| DI003 | [Remove table name](xref:DI003) | Measure references should not include the table name, as the table name is unnecessary when referencing measures. Moreover, this practice makes measure references more easily distinguishable from column references. Example:<br>`Sales[Total Sales]` -> `[Total Sales]` |
 | DI004 | [Add table name](xref:DI004) | Column references should include the table name to avoid ambiguities and to more easily distinguish column references from measure references. Example:<br>`SUM([SalesAmount])` -> `SUM(Sales[SalesAmount])` |
 | DI005 | [Rewrite table filter as scalar predicate](xref:DI005) | A common anti-pattern in DAX is to filter a table inside a [`CALCULATE`](https://dax.guide/CALCULATE) filter argument when it is sufficient to filter one or more columns from that table. Example:<br>`CALCULATE([Total Sales], FILTER(Products, Products[Color] = "Red"))` -> `CALCULATE([Total Sales], KEEPFILTERS(Products[Color] = "Red"))`<br>This Code Action supports various variations of the original expression. |
 | DI006 | [Split multi-column filter into multiple filters](xref:DI006) | When filtering a table on multiple columns combined using `AND` (or the equivalent `&&` operator), better performance can often be achieved by specifying multiple filters, one for each column. Example:<br>`CALCULATE(..., Products[Color] = "Red" && Products[Size] = "Large")` -> `CALCULATE(..., Products[Color] = "Red", Products[Size] = "Large")` |

content/features/tmdl.md

@@ -19,7 +19,7 @@ applies_to:
 ---
 # Tabular Model Definition Language (TMDL)
 
-**TMDL** is a model metadata file format [announced by Microsoft in April 2023](https://powerbi.microsoft.com/en-ie/blog/announcing-public-preview-of-the-tabular-model-definition-language-tmdl/). It aims to provide a human-readable, text-based alternative to the JSON-based model.bim file format. TMDL is inspired by YAML, and as such, is easy to read and write, with minimal use of string quotes and escape characters. It also serializes a model as several smaller files in a folder structure, and is therefore also better suited for version control integration.
+**TMDL** is a model metadata file format [announced by Microsoft in April 2023](https://powerbi.microsoft.com/en-us/blog/announcing-public-preview-of-the-tabular-model-definition-language-tmdl/). It aims to provide a human-readable, text-based alternative to the JSON-based model.bim file format. TMDL is inspired by YAML, and as such, is easy to read and write, with minimal use of string quotes and escape characters. It also serializes a model as several smaller files in a folder structure, and is therefore also better suited for version control integration.
 
 ## Enabling TMDL in Tabular Editor 3
 

content/getting-started/Power-BI-Desktop-Integration.md

@@ -1,7 +1,7 @@
 ---
 uid: desktop-integration
 title: Power BI Desktop Integration
-applies to:
+applies_to:
   products:
     - product: Tabular Editor 2
       full: true
@@ -16,7 +16,7 @@ applies to:
 ---
 # Power BI Desktop Integration
 
-[Power BI Desktop supports External Tools](https://docs.microsoft.com/da-dk/power-bi/create-reports/desktop-external-tools) which allows Tabular Editor to perform  modeling operations when working with Imported or DirectQuery data in Desktop.
+[Power BI Desktop supports External Tools](https://docs.microsoft.com/en-us/power-bi/create-reports/desktop-external-tools) which allows Tabular Editor to perform  modeling operations when working with Imported or DirectQuery data in Desktop.
 
 ![image](~/content/assets/images/getting-started/power-bi-desktop-integration.png)
 
@@ -45,6 +45,6 @@ Once connected to the instance of Analysis Services, an external tool can obtain
 
 ## Supported Modeling Operations
 
-As of the June 2025 Power BI Desktop update, there are no longer any unsupported write operations. In other words, third party tools can now freely modify any aspect of the semantic model hosted in Power BI Desktop, including adding and removing tables and columns, changing data types, etc. However, if you're using a version of Power BI Desktop prior to the June 2025 update, please view the limitations in the [Desktop Limitations](xref: desktop-limitations) article.
+As of the June 2025 Power BI Desktop update, there are no longer any unsupported write operations. In other words, third party tools can now freely modify any aspect of the semantic model hosted in Power BI Desktop, including adding and removing tables and columns, changing data types, etc. However, if you're using a version of Power BI Desktop prior to the June 2025 update, please view the limitations in the [Desktop Limitations](xref:desktop-limitations) article.
 
 More information in [the official blog post](https://powerbi.microsoft.com/en-us/blog/open-and-edit-any-semantic-model-with-power-bi-tools/).

content/getting-started/editions.md

@@ -33,7 +33,7 @@ We consider the **highlighted** flavors of Analysis Services to be Enterprise-Ti
 
 Please refer to the matrix below for the full overview of supported scenarios:
 
-|Scenario / Edition|Desktop|Business|Enterprise
+|Scenario / Edition|Desktop|Business|Enterprise|
 |---|---|---|---|
 |External Tool for Power BI Desktop|<span class="emoji"><span class="emoji">&#10004;</span></span>|<span class="emoji">&#10004;</span>|<span class="emoji">&#10004;</span>|
 |Load/save model metadata to disk**|<span class="emoji">&#10060;</span>|<span class="emoji">&#10004;</span>*|<span class="emoji">&#10004;</span>|
@@ -66,7 +66,7 @@ Specifically, [Azure AS Basic Tier and SQL Server Standard Edition does not supp
 
 Similarly, [Power BI Premium-Per-User workspaces do not support Direct Lake datasets](https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview#prerequisites), which is why Power BI models using this feature also requires TE3 Enterprise Edition.
 
-|Model type|Feature|Business|Enterprise
+|Model type|Feature|Business|Enterprise|
 |---|---|---|---|
 |Azure AS / SSAS|Perspectives|<span class="emoji">&#10060;</span>|<span class="emoji">&#10004;</span>|
 |Azure AS / SSAS|Multiple partitions|<span class="emoji">&#10060;</span>|<span class="emoji">&#10004;</span>|

content/how-tos/undo-redo.md

@@ -11,4 +11,4 @@ applies_to:
 ## Undo/Redo support
 Any change you make in Tabular Editor can be undone using CTRL+Z and subsequently redone using CTRL+Y. There is no limit to the number of operations that can be undone, but the stack is reset when you open a Model.bim file or load a model from a database.
 
-When deleting objects from the model, all translations, perspectives and relationships that reference the deleted objects are also automatically deleted (whereas Visual Studio normally shows an error message that the object cannot be deleted). If you make a mistake, you can use the Undo functionality to restore the deleted object, which will also restore any translations, perspectives or relationships that were deleted. Note that even though Tabular Editor can detect [DAX formula dependencies](), Tabular Editor will not warn you in case you delete a measure or column which is used in the DAX expression of another measure or calculated column.
+When deleting objects from the model, all translations, perspectives and relationships that reference the deleted objects are also automatically deleted (whereas Visual Studio normally shows an error message that the object cannot be deleted). If you make a mistake, you can use the Undo functionality to restore the deleted object, which will also restore any translations, perspectives or relationships that were deleted. Note that even though Tabular Editor can detect [DAX formula dependencies](xref:formula-fix-up-dependencies), Tabular Editor will not warn you in case you delete a measure or column which is used in the DAX expression of another measure or calculated column.

content/references/shortcuts3.md

@@ -101,7 +101,7 @@ applies_to:
 |Command|Shortcut|
 |---|---|
 |Go to definition|F12|
-|Peek definition|Alt+F12]
+|Peek definition|Alt+F12|
 |Refactor|Ctrl+R|
 |Show auto-complete|Ctrl+Space|
 |Show calltip|Ctrl+Shift+Space|