Update packages

Author: xPaw

_articles/abilities/datadriven/datadriven-ability-events-modifiers.md

@@ -9,24 +9,6 @@ A guide that tries to cover every Ability & Modifier Event of the *ability_datad
 
 ![img](/images/external/T7W828Q.png)
 
-- [Ability Events](#Comment_28)
-  - [Spell Start](#Comment_28)
-  - [Toggleable Abilities](#Comment_29)
-  - [Channeled Abilities](#Comment_30)
-  - [Death and Spawn](#Comment_31)
-  - [Projectiles](#Comment_32)
-  - [Item Equip](#Comment_33)
-  - [Others](#Comment_34)
-- [Modifier Events](#Comment_35)
-  - [Create and Destroy](#Comment_35)
-  - [Repeating Actions](#Comment_36)
-  - [Attacks](#Comment_37)
-  - [Damage](#Comment_38)
-  - [Killing and Dying](#Comment_39)
-  - [Orbs](#Comment_40)
-  - [Others](#Comment_41)
-
-<br />
 <a name="start"></a>
 This is an Intermediate guide that expects some knowledge of the most common first-level keyvalues. If unsure about the meaning of any of them, check the [DataDriven Ability Breakdown](/abilities/ability-keyvalues).
 

_articles/abilities/item-keyvalues.md

@@ -11,8 +11,10 @@ A comprehensive guide to npc_items_custom and coding items
 
 Start with "item_" and your item name. If you **don't** put `item_` at the begging of an item, bad things happen
 
-`"item_custom"
-{ ... }`
+```
+"item_custom"
+{ ... }
+```
 
 Each item needs its proper ID for purchasing on the shop, although you can define items without an ID if you only plan to create them through Lua.
 Do not override Dota IDs, use IDs between 1000~2000
@@ -173,7 +175,7 @@ Apart from this values specially related to items, you can add ***everything***
 "AbilityCastAnimation" "ACT_DOTA_CAST_ABILITY_1"
 "AbilityManaCost" "100"
 "AbilityValues"
-{ ... }
+{...}
 ```
 
 **[Ability Events](datadriven/datadriven-ability-events-modifiers)** like `"OnSpellStart"`, `"OnOwnerDied"` or `"OnEquip"` also go here in the main block.
@@ -278,7 +280,7 @@ This is how Basher is disallowed for certain heroes
 "InvalidHeroes" "npc_dota_hero_spirit_breaker;npc_dota_hero_faceless_void"
 ```
 
-For the Scripted, more powerful version, read more on [Item Restrictions & Requirements](scripting/item-restrictions-requirements)
+For the Scripted, more powerful version, read more on [Item Restrictions & Requirements](/scripting/item-restrictions-requirements)
 
 ------
 
@@ -310,9 +312,9 @@ Displays "[ALLIES] Gather for **ItemName** here."
 
 ![img](/images/external/duiGf-025d66f1cd.jpg)
 
-```~
+```
 "ItemAlertable"	"1"
-```~
+```
 
 
 ---

_articles/panorama/webpack.md

@@ -162,7 +162,7 @@ You can find more packages built for Panorama using this search query: [keywords
 
 webpack loaders are packages that process your files before webpack puts them into a bundle.
 
-One good example of a loader is [`babel-loader`](https://www.npmjs.com/package/babel-loader), which processes your code with Babel, allowing you to use newer JavaScript features, and non-standard syntax extensions, such as [JSX](react#JSX).
+One good example of a loader is [`babel-loader`](https://www.npmjs.com/package/babel-loader), which processes your code with Babel, allowing you to use newer JavaScript features, and non-standard syntax extensions, such as [JSX](react#jsx).
 
 First you need to install a few dependencies:
 

_articles/scripting-introduction.md

@@ -20,7 +20,7 @@ Go into your <addonName>/scripts/ folder. The 2 main script folders are **
 * npc_**abilities**_override.txt - Modified dota abilities/items with changed values.
 * **herolist**.txt - List of the heroes available for picking.
 
-These files are defined using KeyValues (KV) and are the core of the the **DataDriven system**. While they fulfill the definition of a programming language, it’s more like a big table containing all the possible data in a static document. it uses a relatively simple syntax whose only special characters are curly braces and quotes, with alternating sets of "Key" and "Value" or "Key" {table} pairs, where table is another set of KeyValues.
+These files are defined using KeyValues (KV) and are the core of the the **DataDriven system**. While they fulfill the definition of a programming language, it’s more like a big table containing all the possible data in a static document. it uses a relatively simple syntax whose only special characters are curly braces and quotes, with alternating sets of "Key" and "Value" or "Key" `{table}` pairs, where `table` is another set of KeyValues.
 
 KV will define the data of abilities/items/units, while more elaborate behavior is handled with Lua or TypeScript.
 

_articles/scripting/item-drop-system.md

@@ -142,7 +142,7 @@ The 'or 100' and 'or 1' are just to make sure that if the "Chance" or "Multiple"
 
 Sometimes doing "50% of item 1 and 50% of item 2" is too random, because it will mean sometimes a mob will drop nothing, and sometimes it might drop 2. In order to reduce the randomness and ensure a certain combination of items will drop, the most common approach is to have a set list of possible drops, and make it so that the unit will drop only one of that set at random.
 
-To do this, instead of tying a single item to each item table, there will be yet another table of the { possible Set of items } that we want this creature to drop:
+To do this, instead of tying a single item to each item table, there will be yet another table of the \{possible Set of items\} that we want this creature to drop:
 
 ```
 "Drops" 

_articles/scripting/lava-damage.md

@@ -21,7 +21,7 @@ It should change to the specified (trigger) material.
 <StaticVideo path="/videos/WaterloggedQuarrelsomeDutchshepherddog.mp4" />
 
 Then convert the mesh to Entity by pressing Ctrl+T or find the `Outliner` => Right Click => Selected Meshes => Tie to Entity.
-Afterwards, name it plus assign this Entity script to lavatrigger.lua <-- you can name it whatever you want.
+Afterwards, name it plus assign this Entity script to lavatrigger.lua &lt;-- you can name it whatever you want.
 
 ![](/images/external/5eZycip.png)
 

_articles/tools/setting-up-for-collaboration.mdx

@@ -52,7 +52,7 @@ eight
 >>>>>>> branch-a
 ```
 
-Basically everything between '<<<<<<<HEAD' and '=====' is what you have for that line, everything between the '==========' line and the '>>>>>>>' line is what you pulled from the remote. Resolve the conflict by just removing everything except the code you want to keep. This can be your stuff, the stuff from the remote or even both! A fixed file could look like this (I chose to keep both):
+Basically everything between `<<<<<<<HEAD` and `=====` is what you have for that line, everything between the `==========` line and the `>>>>>>>` line is what you pulled from the remote. Resolve the conflict by just removing everything except the code you want to keep. This can be your stuff, the stuff from the remote or even both! A fixed file could look like this (I chose to keep both):
 
 ```
 nine

api/src/components/Docs/types.tsx

@@ -58,10 +58,10 @@ const ReferenceType: React.FC<{ name: string }> = ({ name }) => {
       type.kind === "class" || type.kind === "enum"
         ? name
         : type.kind === "constant"
-        ? "constants"
-        : type.kind === "function"
-        ? "functions"
-        : undefined,
+          ? "constants"
+          : type.kind === "function"
+            ? "functions"
+            : undefined,
       type.kind === "constant" || type.kind === "function" ? name : undefined,
     ];
   }, [name]);

api/src/components/Docs/utils/filtering.tsx

@@ -121,11 +121,11 @@ export function doSearch(declarations: api.Declaration[], words: string[]): api.
               ),
             }
           : declaration.kind === "enum"
-          ? {
-              ...declaration,
-              members: declaration.members.filter(composeFilters([filterName, filterAvailability])),
-            }
-          : undefined;
+            ? {
+                ...declaration,
+                members: declaration.members.filter(composeFilters([filterName, filterAvailability])),
+              }
+            : undefined;
 
       if (partialDeclaration && partialDeclaration.members.length > 0) {
         return partialDeclaration;

api/src/index.html

@@ -1,4 +1,4 @@
-<!DOCTYPE html>
+<!doctype html>
 <html lang="en">
   <head>
     <meta charset="UTF-8" />