!fixup more minor fixes

Author: dmkozh

core/cap-0085.md

@@ -25,7 +25,7 @@ The factory pattern is commonly used in smart contract protocols to deploy many
 
 Because some upgrades carry security fixes, or are not backwards-compatible with the previous version, there is incentive for the upgrade to apply atomically across the entire fleet. Moreover, this is a manual process that puts the burden of tracking all the active instances on the admin, which is error-prone and can lead to some instances being left behind.
 
-Ecosystems that manage reusable code via proxies, such as Ethereum, achieve this with the beacon proxy pattern.
+Ecosystems that manage reusable code via proxies, such as Ethereum, achieve this with the [beacon proxy](https://docs.openzeppelin.com/contracts/5.x/api/proxy#beacon) pattern.
 
 Stellar has no equivalent today. Each contract instance defines its own Wasm hash, and we do not provide host functions equivalent to the proxy primitives in other chains (like `fallback` or `delegatecall`) that beacon implementations rely on. 
 
@@ -76,9 +76,9 @@ index 0e67dc3..b1c8593 100644
  {
      CONTRACT_EXECUTABLE_WASM = 0,
 -    CONTRACT_EXECUTABLE_STELLAR_ASSET = 1
-+    CONTRACT_EXECUTABLE_STELLAR_ASSET = 1,
++    CONTRACT_EXECUTABLE_STELLAR_ASSET = 1
 +#ifdef CAP_0085
-+    CONTRACT_EXECUTABLE_EXTERNAL_REF = 2
++    ,CONTRACT_EXECUTABLE_EXTERNAL_REF = 2
 +#endif
 +};
 +