fix a few more links

packages/core/src/components/forms/input-group.md

@@ -17,7 +17,7 @@ the parent input.
     in CSS cannot accomodate buttons whose width varies due to text content. You should use icons on
     buttons instead.</p>
 
-    Conversely, the [`InputGroup`](#components.forms.input-group.js) React component _does_ support
+    Conversely, the [`InputGroup`](#core/components/forms/input-group.javascript-api) React component _does_ support
     arbitrary content in its right element.
 </div>
 

packages/core/src/components/menu/menu.md

@@ -9,9 +9,9 @@ package. Make sure to review the [general usage docs for JS components](#bluepri
 
 The `Menu` API includes three stateless React components:
 
-- [`Menu`](#components.menu.js.menu)
-- [`MenuItem`](#components.menu.js.menu-item)
-- [`MenuDivider`](#components.menu.js.menu-divider)
+- [`Menu`](#core/components/menu.menu)
+- [`MenuItem`](#core/components/menu.menu-item)
+- [`MenuDivider`](#core/components/menu.menu-divider)
 
 @### Sample usage
 
@@ -123,9 +123,9 @@ element as the `content` property of a `Popover`:
 
 When the user clicks a menu item that is not disabled and is not part of a submenu, the popover is
 automatically dismissed (in other words, the menu closes). This is because the `MenuItem` component
-adds the `pt-popover-dismiss` class to these items by default (see [Popover JavaScript
-API](#components.popover.js) for more information). If you want to opt out of this behavior, you can
-add the `shouldDismissPopover` prop to a `MenuItem`.
+adds the `pt-popover-dismiss` class to these items by default (see
+[Popover JavaScript API](#core/components/popover) for more information). If you want to opt out of
+this behavior, you can add the `shouldDismissPopover` prop to a `MenuItem`.
 
 Notice that selecting the menu item labeled "Table" in the example below does not automatically
 dismiss the `Popover`. Selecting other menu items does dismiss the popover.

packages/core/src/components/tabs2/tabs2.md

@@ -20,7 +20,8 @@ JavaScript component does this by default).
   <h5>Original `Tabs` API is deprecated since v1.11.0</h5>
   The original `Tabs` API has been deprecated in v1.11.0 favor of the simpler and more flexible
   `Tabs2` API described below. Documentation for the deprecated components can be found
-  [further below](#components.tabs.deprecated). This API will replace the deprecated one in v2.0.
+  [further below](#core/components/tabs.deprecated-javascript-api).
+  This API will replace the deprecated one in v2.0.
 </div>
 
 <div class="pt-callout pt-intent-primary pt-icon-info-sign">

packages/core/src/components/tooltip/tooltip.md

@@ -21,8 +21,8 @@ but you should keep it simple. If you need more space, consider using a popover
 <div class="pt-callout pt-intent-warning pt-icon-warning-sign">
     <h5>Button targets</h5>
     Buttons make great tooltip targets, but the `disabled` attribute will prevent all events so the enclosing `Tooltip`
-    will not know when to respond. Use [`AnchorButton`](#components.button.js.anchor-button) instead;
-    see the [callout here](#components.button.js) for more details.
+    will not know when to respond. Use [`AnchorButton`](#core/components/button.anchor-button) instead;
+    see the [callout here](#core/components/button.javascript-api) for more details.
 </div>
 
 @interface ITooltipProps

packages/table/README.md

@@ -23,4 +23,4 @@ or spreadsheet.
 npm install --save @blueprintjs/table
 ```
 
-### [Table Documentation](http://blueprintjs.com/docs/#components.table-js) | [Full Documentation](http://blueprintjs.com/docs) | [Source Code](https://github.com/palantir/blueprint)
+### [Table Documentation](http://blueprintjs.com/docs/#table-js) | [Full Documentation](http://blueprintjs.com/docs) | [Source Code](https://github.com/palantir/blueprint)