LRDOCS-7258 Fix Links | 7.1.x

develop/reference/articles/10-sample-projects/01-apps/greedy-policy-option-portlet.markdown

@@ -54,11 +54,11 @@ Here are each module's file structures:
 
 Here are the things you can learn using the sample modules:
 
-1.  [Binding a component's service reference to the highest ranked service instance that's available initially.](#binding-a-newly-deployed-components-service-reference-to-the-highest-rankin)
+1.  [Binding a component's service reference to the highest ranked service instance that's available initially.](#binding-a-newly-deployed-components-service-reference-to-the-highest-ranking-service-instance-thats-available-initially)
 
-2.  [Deploying a module with a higher ranked service instance for binding to greedy references immediately.](#deploying-a-module-with-a-higher-ranked-service-instance-for-binding-to-gre)
+2.  [Deploying a module with a higher ranked service instance for binding to greedy references immediately.](#deploying-a-module-with-a-higher-ranked-service-instance-for-binding-to-greedy-references-immediately)
 
-3.  [Configuring a component to reference a different service instance dynamically.](#configuring-a-component-to-reference-a-different-service-instance-dynamical)
+3.  [Configuring a component to reference a different service instance dynamically.](#configuring-a-component-to-reference-a-different-service-instance-dynamically)
 
 Let's walk through the demonstration.
 
@@ -155,7 +155,7 @@ The `GreedyPortlet` class is similar to `ReluctantPortlet`, except its
 
 The greedy policy option lets the component switch to using a higher ranked
 `SomeService` instance if one becomes active in the system. The section
-[*Deploying a module with a higher ranked service instance for binding to greedy references immediately*](#deploying-a-module-with-a-higher-ranked-service-instance-for-binding-to-gre)
+[*Deploying a module with a higher ranked service instance for binding to greedy references immediately*](#deploying-a-module-with-a-higher-ranked-service-instance-for-binding-to-greedy-references-immediately)
 demonstrates this portlet switching to a higher ranked service.
 
 It's time to see this module's portlets and service in action.

develop/reference/articles/10-sample-projects/02-extensions/document-action.markdown

@@ -28,7 +28,7 @@ selecting *Show Actions* from the portlet's Configuration menu.
 ## What API(s) and/or code components does this sample highlight?
 
 This sample leverages the
-[PortletConfigurationIcon](@product-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/portlet/configuration/icon/PortletConfigurationIcon.html)
+[PortletConfigurationIcon](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/portlet/configuration/icon/PortletConfigurationIcon.html)
 API.
 
 ## How does this sample leverage the API(s) and/or code component?

develop/reference/articles/10-sample-projects/02-extensions/screen-name-validator.markdown

@@ -31,7 +31,7 @@ You can test this sample by following the following steps:
 ## What API(s) and/or code components does this sample highlight?
 
 This sample leverages the
-[ScreenNameValidator](@product-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/security/auth/ScreenNameValidator.html)
+[ScreenNameValidator](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/security/auth/ScreenNameValidator.html)
 API.
 
 ## How does this sample leverage the API(s) and/or code component?

develop/reference/articles/10-sample-projects/04-themes/template-context-contributor.markdown

@@ -18,7 +18,7 @@ Context contributors allow non-JSP developers an easy way to inject variables
 into their Liferay templates.
 
 This sample leverages the
-[TemplateContextContributor](@product-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/template/TemplateContextContributor.html)
+[TemplateContextContributor](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/template/TemplateContextContributor.html)
 API.
 
 ## How does this sample leverage the API(s) and/or code component?

develop/reference/articles/100-felix-gogo-shell.markdown

@@ -12,7 +12,7 @@ portlet. You can access this portlet in the Control Panel → *Configuration*
 
 | **Note:** You can also interact with @product@'s module framework via a local
 | telnet session. To do this, you must have
-| [Developer Mode enabled](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-using-portal-developer-properties).
+| [Developer Mode enabled](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-using-portal-developerproperties).
 | 
 | To open the Gogo shell via telnet, execute the following command:
 | 

develop/reference/articles/1000-customization-with-ext/01-customizing-core-functionality-with-ext/01-creating-an-ext-plugin.markdown

@@ -11,7 +11,7 @@ the complexity of your @product@ installation, you should only use an Ext plugin
 if you're sure you can't accomplish your goal in a different way. You can		
 create Ext plugins using the pre-configured `war-core-ext` project
 template/archetype. See the
-[`war-core-ext`](/docs/7-1/reference/-/knowledge_base/r/war-core-ext-template)
+[`war-core-ext`](/docs/7-1/reference/-/knowledge_base/r/war-core-ext)
 project template article for information on how to create an Ext plugin, its
 folder structure, and other important details.
 

develop/reference/articles/1000-customization-with-ext/01-customizing-core-functionality-with-ext/02-anatomy-of-an-ext-plugin.markdown

@@ -7,7 +7,7 @@ header-id: anatomy-of-an-ext-plugin
 [TOC levels=1-4]
 
 There are two ways you can structure your Ext plugin. The
-[`war-core-ext`](/docs/7-1/reference/-/knowledge_base/r/war-core-ext-template)
+[`war-core-ext`](/docs/7-1/reference/-/knowledge_base/r/war-core-ext)
 project template/archetype creates the default layout:
 
 - `[project name]-ext/`

develop/tutorials/articles-dxp/100-tooling/02-liferay-ide/01-installing-liferay-ide.markdown

@@ -16,9 +16,9 @@ to get acquainted with its supported Liferay versions and application servers.
 In this tutorial, you'll learn the different methods available for installing
 Liferay Dev Studio:
 
-- [install the Dev Studio bundle from scratch](#install-the-liferay-developer-studio-bundle)
-- [install Dev Studio into an existing Eclipse instance using an update URL](#install-liferay-developer-studio-into-eclipse-environment)
-- [install Dev Studio into an existing Eclipse instance using a ZIP file](#install-liferay-ide-into-eclipse-from-a-zip-file)
+- [install the Dev Studio bundle from scratch](#install-the-liferay-dev-studio-bundle)
+- [install Dev Studio into an existing Eclipse instance using an update URL](#install-liferay-dev-studio-into-eclipse-environment)
+- [install Dev Studio into an existing Eclipse instance using a ZIP file](#install-liferay-dev-studio-into-eclipse-from-a-zip-file)
 
 **Important:** If you're installing Dev Studio into an existing Eclipse
 environment, you must be on Eclipse Oxygen or newer. For instructions on

develop/tutorials/articles/100-tooling/02-liferay-ide/08-managing-projects-with-liferay-ide.markdown

@@ -38,7 +38,7 @@ deployed successfully.
 ![Figure 2: You can check to see if your project deployed successfully to Liferay using the Gogo shell.](../../../images/gogo-deploy-successful.png)
 
 Dev Studio's Gogo shell usage requires
-[Developer Mode](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-in-liferay-ide)
+[Developer Mode](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-in-dev-studio-ce)
 to be enabled. Developer Mode is enabled in
 [Liferay Workspace](/docs/7-1/tutorials/-/knowledge_base/t/liferay-workspace)
 by default.

develop/tutorials/articles/100-tooling/02-liferay-ide/14-using-maven-in-liferay-ide.markdown

@@ -9,7 +9,7 @@ header-id: using-maven-in-liferay-ide
 You can take full advantage of Maven in Liferay Dev Studio with its built-in
 Maven support. In this tutorial, you'll learn about the following topics:
 
-- [Installing Maven Plugins for Liferay Dev Studio](#installing-maven-plugins-for-liferay-ide)
+- [Installing Maven Plugins for Liferay Dev Studio](#installing-maven-plugins-for-liferay-dev-studio)
 - [Creating Maven Projects](#creating-maven-projects)
 - [Importing Maven Projects](#importing-maven-projects)
 - [Using the POM Graphic Editor](#using-the-pom-graphic-editor)

develop/tutorials/articles/100-tooling/03-blade-cli/06-managing-your-liferay-server-with-blade-cli.markdown

@@ -48,7 +48,7 @@ server's OSGi container.
 ![Figure 1: Blade CLI accesses the Gogo shell script to run the `lb` command.](../../../images/blade-sh.png)
 
 You can run any Gogo command using `blade sh`. This command requires
-[Developer Mode](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-using-portal-developer-properties)
+[Developer Mode](/docs/7-1/tutorials/-/knowledge_base/t/using-developer-mode-with-themes#setting-developer-mode-for-your-server-using-portal-developerproperties)
 to be enabled. Developer Mode is enabled in
 [Liferay Workspace](/docs/7-1/tutorials/-/knowledge_base/t/liferay-workspace)
 by default. See the

develop/tutorials/articles/100-tooling/04-liferay-workspace/07-validating-modules-against-the-target-platform/02-modifying-the-target-platforms-capabilities.markdown

@@ -36,7 +36,7 @@ resolver to bypass this.
 There are three ways you can do this:
 
 - [Embed the third party library in your module](#embed-the-third-party-library-in-your-module)
-- [Add the third party library's capabilities to the current static set of resolver capabilities](#add-the-third-party-librarys-capabilities-to-the-current-static-set-of-reso)
+- [Add the third party library's capabilities to the current static set of resolver capabilities](#add-the-third-party-librarys-capabilities-to-the-current-static-set-of-resolver-capabilities)
 - [Skip the resolving process for your module](#skip-the-resolving-process-for-your-module)
 
 For help resolving third party dependency errors, see the

develop/tutorials/articles/110-portlets/05-jsf-portlets-with-liferay-faces/03-generating-a-jsf-project-manually/03-defining-jsf-portlet-descriptors.markdown

@@ -166,7 +166,7 @@ WAR-style portlet descriptors.
 Great! You now have a good idea of how to specify and define general descriptor
 files for your JSF portlet. JSF portlets also use Liferay descriptors, which you
 can learn more about in the
-[Liferay Descriptors](/docs/7-1/tutorials/-/knowledge_base/t/spring-mvc#liferay-descriptors)
+[Liferay Descriptors](/docs/7-1/tutorials/-/knowledge_base/t/configuring-a-spring-mvc-portlet#liferay-descriptors)
 sub-section.
 
 Now that your portlet descriptors are defined, you'll begin working on your JSF

develop/tutorials/articles/170-assets/05-rendering-an-asset/01-creating-asset-renderer.markdown

@@ -9,7 +9,7 @@ header-id: creating-an-asset-renderer
 In this tutorial, you'll learn how to create an `Asset Renderer` and associate your JSP templates with it, along with configuring several other options.
 
 To learn how an asset renderer is created, you'll create the pre-existing
-[`BlogsEntryAssetRenderer`](@app-ref@/collaboration/latest/javadocs/com/liferay/blogs/web/asset/BlogsEntryAssetRenderer.html)
+[`BlogsEntryAssetRenderer`](https://github.com/liferay/liferay-portal/blob/7.1.3-ga4/modules/apps/blogs/blogs-web/src/main/java/com/liferay/blogs/web/asset/BlogsEntryAssetRenderer.java)
 class, which configures the asset renderer framework for the Blogs application.
 
 1.  Create a new package in your existing project for your asset-related
@@ -18,19 +18,19 @@ class, which configures the asset renderer framework for the Blogs application.
 
 2.  Create your `-AssetEntry` class for your application in the new `-.asset`
     package and have it implement the
-    [`AssetEntry`](@platform-ref@/7.0-latest/javadocs/portal-kernel/com/liferay/asset/kernel/model/AssetEntry.html)
+    [`AssetEntry`](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/asset/kernel/model/AssetEntry.html)
     interface. Consider the `BlogsEntryAssetRenderer` class as an example:
 
         public class BlogsEntryAssetRenderer
             extends BaseJSPAssetRenderer<BlogsEntry> implements TrashRenderer {
 
     The `BlogsEntryAssetRenderer` class extends the
-    [`BaseJSPAssetRenderer`](@platform-ref@/7.0-latest/javadocs/portal-kernel/com/liferay/asset/kernel/model/BaseJSPAssetRenderer.html),
+    [`BaseJSPAssetRenderer`](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/asset/kernel/model/BaseJSPAssetRenderer.html),
     which is an extension class intended for those who plan on using JSP
     templates to generate their asset's HTML. The `BaseJSPAssetRenderer` class
     implements the `AssetRenderer` interface. You'll notice the asset renderer
     is also implementing the
-    [`TrashRenderer`](@platform-ref@/7.0-latest/javadocs/portal-kernel/com/liferay/portal/kernel/trash/TrashRenderer.html)
+    [`TrashRenderer`](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/trash/TrashRenderer.html)
     interface. This is a common practice for many applications, so they can use
     @product@'s Recycle Bin.
 

develop/tutorials/articles/170-assets/05-rendering-an-asset/03-creating-factory-asset-renderer.markdown

@@ -16,7 +16,7 @@ renderer factory.
 
 1.  Create an `-AssetRenderFactory` class in the same folder as its asset
     renderer class. For blogs, the
-    [`BlogsEntryAssetRendererFactory`](@app-ref@/collaboration/latest/javadocs/com/liferay/blogs/web/asset/BlogsEntryAssetRendererFactory.html)
+    [`BlogsEntryAssetRendererFactory`](https://github.com/liferay/liferay-portal/blob/7.1.3-ga4/modules/apps/blogs/blogs-web/src/main/java/com/liferay/blogs/web/asset/BlogsEntryAssetRendererFactory.java)
     class resides in the `com.liferay.blogs.web` module's
     `com.liferay.blogs.web.asset` package. The factory class should extend the
     `BaseAssetRendererFactory` class and the asset type should be specified as

develop/tutorials/articles/240-product-navigation/03-extending-the-simulation-menu.markdown

@@ -20,7 +20,7 @@ with this tutorial.
 There are few differences between the Simulation Menu and Product Menu, mostly
 because they extend the same base classes. The Simulation Menu, by default, is
 made up of only one panel category and one panel app. Liferay provides the
-[`SimulationPanelCategory`](@app-ref@/web-experience/latest/javadocs/com/liferay/product/navigation/simulation/application/list/SimulationPanelCategory.html)
+[`SimulationPanelCategory`](https://github.com/liferay/liferay-portal/blob/7.1.3-ga4/modules/apps/product-navigation/product-navigation-simulation-web/src/main/java/com/liferay/product/navigation/simulation/web/internal/application/list/SimulationPanelCategory.java)
 class, a hidden category needed to hold the `DevicePreviewPanelApp`. This is the
 app and functionality you see in the Simulation Menu by default.
 

develop/tutorials/articles/240-product-navigation/04-providing-the-user-personal-bar.markdown

@@ -75,7 +75,7 @@ existing default portlet.
      `service` element should be `ViewPortletProvider.class`.
 
 4.  Update the class's declaration to extend the 
-    [BasePortletProvider](@platform-ref@/7.0-latest/javadocs/portal-kernel/com/liferay/portal/kernel/portlet/BasePortletProvider.html)
+    [BasePortletProvider](@platform-ref@/7.1-latest/javadocs/portal-kernel/com/liferay/portal/kernel/portlet/BasePortletProvider.html)
     abstract class and implement `ViewPortletProvider`:
 
         public class ExampleViewPortletProvider extends BasePortletProvider implements ViewPortletProvider {

discover/portal/articles/100-web-experience-management/02-building-a-site/06-configuring-pages/02-configuring-individual-pages/01-customizing-pages.markdown

@@ -136,5 +136,5 @@ JavaScript code remains in one place.
 
 This configuration option is also available for Page Sets like Public Pages and
 Private Pages. Visit 
-[Executing JavaScript in Site Pages](/docs/7-1/user/-/knowledge_base/u/creating-and-managing-pages#executing-javascript-in-site-pages)
+[Executing JavaScript in Site Pages](/docs/7-1/user/-/knowledge_base/u/advanced-page-set-options#executing-javascript-in-site-pages)
 for more information on doing this for Page Sets.