Fix broker links due to invalid package (#694)

site/_includes/explanations/partitioned-topics.md

@@ -28,4 +28,4 @@ Key hash | If a key property has been specified on the message, the partitioned
 Single default partition | If no key is provided, each producer's message will be routed to a dedicated partition, initially random selected | Per-producer ordering
 Round robin distribution | If no key is provided, all messages will be routed to different partitions in round-robin fashion to achieve maximum throughput. | None
 
-In addition to these default modes, you can also create a custom routing mode if you're using the [Java client](../../clients/Java) by implementing the {% javadoc MessageRouter client com.yahoo.pulsar.client.api.MessageRouter %} interface.
+In addition to these default modes, you can also create a custom routing mode if you're using the [Java client](../../clients/Java) by implementing the {% javadoc MessageRouter client org.apache.pulsar.client.api.MessageRouter %} interface.

site/docs/latest/admin-api/brokers.md

@@ -11,7 +11,7 @@ Pulsar brokers consist of two components:
 
 * The [`brokers`](../../reference/CliTools#pulsar-admin-brokers) command of the [`pulsar-admin`](../../reference/CliTools#pulsar-admin) tool
 * The `/admin/brokers` endpoint of the admin [REST API](../../reference/RestApi)
-* The `brokers` method of the {% javadoc PulsarAdmin admin com.yahoo.pulsar.client.admin.PulsarAdmin %} object in the [Java API](../../clients/Java)
+* The `brokers` method of the {% javadoc PulsarAdmin admin org.apache.pulsar.client.admin.PulsarAdmin %} object in the [Java API](../../clients/Java)
 
 In addition to being configurable when you start them up, brokers can also be [dynamically configured](#dynamic-broker-configuration).
 

site/docs/latest/admin/GeoReplication.md

@@ -20,7 +20,7 @@ Geo-replication must be enabled on a per-{% popover property %} basis in Pulsar.
 
 Although geo-replication must be enabled between two clusters, it's actually managed at the {% popover namespace %} level. You must do the following to enable geo-replication for a namespace:
 
-* [Create a global namespace](#creating-a-global-namespace)
+* [Create a global namespace](#creating-global-namespaces)
 * Configure that namespace to replicate between two or more provisioned clusters
 
 Any message published on *any* topic in that namespace will then be replicated to all clusters in the specified set.
@@ -84,7 +84,7 @@ Once you've created a global namespace, any topics that producers or consumers c
 
 By default, messages are replicated to all clusters configured for the namespace. You can restrict replication selectively by specifying a replication list for a message. That message will then be replicated only to the subset in the replication list.
 
-Below is an example for the [Java API](../../clients/Java). Note the use of the `setReplicationClusters` method when constructing the {% javadoc Message client com.yahoo.pulsar.client.api.Message %} object:
+Below is an example for the [Java API](../../clients/Java). Note the use of the `setReplicationClusters` method when constructing the {% javadoc Message client org.apache.pulsar.client.api.Message %} object:
 
 ```java
 List<String> restrictReplicationTo = new ArrayList<>;

site/docs/latest/getting-started/Clients.md

@@ -20,7 +20,7 @@ Library | Purpose
 [`org.apache.pulsar.client.api`](/api/client) | The [Pulsar Java client](../../clients/Java) for producing and consuming messages on Pulsar {% popover topics %}
 [`org.apache.pulsar.client.admin`](/api/admin) | The Java client for the [Pulsar admin interface](../../admin-api/overview)
 
-<!-- * [`com.yahoo.pulsar.broker`](/api/broker) -->
+<!-- * [`org.apache.pulsar.broker`](/api/broker) -->
 
 ## Python client
 

site/docs/latest/getting-started/ConceptsAndArchitecture.md

@@ -69,7 +69,7 @@ Messages can be acknowledged either one by one or cumulatively. With cumulative
 
 #### Listeners
 
-Client libraries can provide their own listener implementations for consumers. The [Java client](../../clients/Java), for example, provides a {% javadoc MesssageListener client com.yahoo.pulsar.client.api.MessageListener %} interface. In this interface, the `received` method is called whenever a new message is received.
+Client libraries can provide their own listener implementations for consumers. The [Java client](../../clients/Java), for example, provides a {% javadoc MesssageListener client org.apache.pulsar.client.api.MessageListener %} interface. In this interface, the `received` method is called whenever a new message is received.
 
 ### Topics