From f97d76873afc4bcf0a7ac512afb8da877d4ee402 Mon Sep 17 00:00:00 2001
From: Chetan Padhen <99749401+Chetax@users.noreply.github.com>
Date: Mon, 3 Apr 2023 10:04:40 +0530
Subject: [PATCH] readme: new url to polymer-modulizer #5704

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e6639b58e..eb67833d5 100644
--- a/README.md
+++ b/README.md
@@ -119,7 +119,7 @@ Migrating to Polymer 3.0 by hand is mostly mechanical:
 * Templates should be encoded in JS modules using a `static get template()` getter on PolymerElement subclasses using the `html` tagged template literal function (which parses `HTMLTemplateElement`s out of strings in JS) rather than using `<template>` elements in a `<dom-module>`
 * All dependencies should be imported JS module imports rather than HTML Imports.
 
-However, the [`polymer-modulizer`](https://github.com/Polymer/polymer-modulizer) tool automates the vast majority of this migration work.  Please see details on that repo for automated conversion of Polymer 2.0 apps and elements to Polymer 3.0.
+However, the [`polymer-modulizer`](https://github.com/Polymer/tools/tree/master/packages/modulizer) tool automates the vast majority of this migration work.  Please see details on that repo for automated conversion of Polymer 2.0 apps and elements to Polymer 3.0.
 
 👀 **Looking for Polymer v2.x?** Please see [the v2 branch](https://github.com/Polymer/polymer/tree/2.x).