Cr4 updates

.gitignore

@@ -11,6 +11,9 @@ docs/.obsidian
 .docusaurus
 .cache-loader
 .yarnclean
+.yarn
+.pnp.cjs
+.pnp.loader.mjs
 
 # Misc
 .DS_Store

README.md

@@ -4,7 +4,7 @@
   </a>
 </h1>
 <h2 align="center">Bittensor Developer Docs</h2>
-<h3 align="center">https://docs.bittensor.com</h3>
+<h3 align="center">https://docs.learnbittensor.org</h3>
 
 -----------------------------------------------------------------------------
 
@@ -17,7 +17,7 @@ In most cases you only need to follow this basic approach. If you know what you
 ### Installation
 
 ```
-git clone https://github.com/opentensor/developer-docs.git
+git clone https://github.com/latent-to/developer-docs.git
 ```
 
 ```

WRITING-STYLE-GUIDE.md

@@ -1,13 +1,13 @@
 <h1 align="center">
-  <a href="https://www.docs.bittensor.com">
+  <a href="https://www.docs.learnbittensor.org">
     <img alt="Tao Logo" src="./static/img/tao-logo.png" />
   </a>
 </h1>
 <h2 align="center">Writing Style Guide</h2>
 
 -----------------------------------------------------------------------------
 
-When you write a developer document for Opentensor Foundation, your audience should find your documentation readable, informative, and concise. To accomplish these goals, here below are a few helpful writing style recommendations. We encourage you to stick to the writing style described on this page.
+When you write a developer document for the Bittensor documentation, your audience should find your documentation readable, informative, and concise. To accomplish these goals, here below are a few helpful writing style recommendations. We encourage you to stick to the writing style described on this page.
 
 # General principles