From 454529d7142db84003eef86664379ed4c755726f Mon Sep 17 00:00:00 2001
From: Andre Brisco <91817010+abrisco@users.noreply.github.com>
Date: Mon, 2 Sep 2024 23:06:42 -0700
Subject: [PATCH] docs: updated docs with additional Bazel example (#4508)

* docs: updated docs with additional Bazel example

* fixed link
---
 guide/src/building-and-distribution.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/guide/src/building-and-distribution.md b/guide/src/building-and-distribution.md
index c137a1a3995..b93ceea921e 100644
--- a/guide/src/building-and-distribution.md
+++ b/guide/src/building-and-distribution.md
@@ -92,8 +92,9 @@ If you're packaging your library for redistribution, you should indicated the Py
 
 To use PyO3 with bazel one needs to manually configure PyO3, PyO3-ffi and PyO3-macros. In particular, one needs to make sure that it is compiled with the right python flags for the version you intend to use.
 For example see:
-1. https://github.com/OliverFM/pytorch_with_gazelle -- for a minimal example of a repo that can use PyO3, PyTorch and Gazelle to generate python Build files.
-2. https://github.com/TheButlah/rules_pyo3 -- which has more extensive support, but is outdated.
+1. https://github.com/abrisco/rules_pyo3 -- General rules for building extension modules.
+2. https://github.com/OliverFM/pytorch_with_gazelle -- for a minimal example of a repo that can use PyO3, PyTorch and Gazelle to generate python Build files.
+3. https://github.com/TheButlah/rules_pyo3 -- is somewhat dated.
 
 #### Platform tags