Update content references: IFT -> Logos (#70)

Author: jorge-campo

README.md

@@ -4,14 +4,14 @@
 </p>
 -->
 
-# IFT Documentation (🚧 This is a work in progress)
+# Logos Documentation (🚧 This is a work in progress)
 
-**Unified, docs-as-code workflow for projects under the [Institute of Free Technology](https://free.technology/)**.
+**Unified, docs-as-code workflow for the Logos projects (https://free.technology/logos)**.
 
 <!-- Write in Markdown → merge a PR → GitBook publishes your product docs automatically.-->
 
 <!-- Todo
-[![CI](https://github.com/ift/onedoc/actions/workflows/ci.yml/badge.svg)](actions/workflows/ci.yml)
+[![CI](https://github.com/logos/onedoc/actions/workflows/ci.yml/badge.svg)](actions/workflows/ci.yml)
 -->
 
 [![Project board](https://img.shields.io/badge/Project-Board-blue)](https://github.com/orgs/status-im/projects/155/views/1)
@@ -61,7 +61,7 @@ For style, naming and review rules see the **[Style Guide](docs/STYLE_GUIDE.md)*
 
 <!--
 Questions or ideas? Join us on **Discord → `#onedoc`**  
-Invite link: <https://discord.gg/ift-onedoc>
+Invite link: <https://discord.gg/logos-onedoc>
 -->
 
 Licensed under MIT.

manual/README.md

@@ -1,6 +1,6 @@
-# IFT technical documentation guide
+# Logos technical documentation guide
 
-This guide is for the subject-matter experts (SMEs) who contribute to [IFT projects](https://free.technology/) ↗ documentation: the developers, infrastructure engineers, and other technical contributors responsible for designing and implementing features. It is written for technical experts who need to produce clear, effective documentation for the solutions they create, but who are not professional technical writers.
+This guide is for the subject-matter experts (SMEs) who contribute to [Logos projects](https://free.technology/logos) ↗ documentation: the developers, infrastructure engineers, and other technical contributors responsible for designing and implementing features. It is written for technical experts who need to produce clear, effective documentation for the solutions they create, but who are not professional technical writers.
 
 Our core assumption is that the primary barrier to writing documentation is the lack of a clear and repeatable process. This guide provides that process. It is designed to remove ambiguity, eliminate "blank page" anxiety, and offers a predictable workflow to create high-quality documentation consistently.
 

project/briefings/onedoc/slides.md

@@ -2,24 +2,24 @@
 theme: dracula
 transition: slide-left
 title: OneDoc Project Briefing
-author: campo@ift
+author: campo@Logos
 browserExporter: 
 download: true
-exportFilename: ift-onedoc-project-briefing
+exportFilename: Logos-onedoc-project-briefing
 export:
     format: pdf
 ---
 
 # OneDoc project briefing
 
-A unified, AI-aware stack for IFT user docs
+A unified, AI-aware stack for Logos user docs
 
 --- 
 
 # OneDoc project goal
 
 <div class="mt-20 text-3xl">
-	To unify IFT's user-facing documentation on an AI-native platform (GitBook) with a "docs-as-code" workflow and clear roles, ensuring consistent, high-quality, and easily discoverable documentation to encourage greater developer adoption and contributions.
+	To unify Logos's user-facing documentation on an AI-native platform (GitBook) with a "docs-as-code" workflow and clear roles, ensuring consistent, high-quality, and easily discoverable documentation to encourage greater developer adoption and contributions.
 </div>
 
 <div class="absolute right-30px bottom-30px">
@@ -58,7 +58,7 @@ A unified, AI-aware stack for IFT user docs
 # 1️⃣ What does **unified platform** mean?
 
 <div class="mt-20 text-3xl">
-	Consolidate all user-facing documentation for IFT projects onto a single, AI-native platform, specifically GitBook, to provide a central access point for users.
+	Consolidate all user-facing documentation for Logos projects onto a single, AI-native platform, specifically GitBook, to provide a central access point for users.
 </div>
 
 <div class="absolute right-30px bottom-30px">
@@ -86,11 +86,11 @@ A unified, AI-aware stack for IFT user docs
 </div>
 
 <div class="mt-5 text-xl">
-	Define clear roles and responsibilities, including a project team (technical writers) and dedicated documentation owners within each IFT project, to ensure accountability for content creation and maintenance.
+	Define clear roles and responsibilities, including a project team (technical writers) and dedicated documentation owners within each Logos project, to ensure accountability for content creation and maintenance.
 </div>
 
 <div class="mt-5 text-xl">
-	Documentation owners continue reporting to their respective team leads, and not the project team, ensuring that writers fully integrate and align with their own team. This federated model avoids a centralized "IFT Docs" department.
+	Documentation owners continue reporting to their respective team leads, and not the project team, ensuring that writers fully integrate and align with their own team. This federated model avoids a centralized "Logos Docs" department.
 </div>
 
 <div class="absolute right-30px bottom-30px">
@@ -127,7 +127,7 @@ A unified, AI-aware stack for IFT user docs
 
 --
 
-##### ⬥ Once only / ⭑ Once per IFT project
+##### ⬥ Once only / ⭑ Once per Logos project
 
 <div class="absolute right-30px bottom-30px">
 	<SlideCurrentNo /> / <SlidesTotal />
@@ -143,11 +143,11 @@ A unified, AI-aware stack for IFT user docs
 | 7. Project documentation (III) ⬥                  | Style guide and templates updates                      |
 | 8. Linter implementation ⬥                        | Write VALE linter rules and linter implementation      |
 | 9. Project documentation (IV) ⬥                   | Training materials                                     |
-| 10. Training and mentoring ⭑                      | Training and mentoring the IFT project owner|
+| 10. Training and mentoring ⭑                      | Training and mentoring the Logos project owner|
 
 --
 
-##### ⬥ Once only / ⭑ Once per IFT project
+##### ⬥ Once only / ⭑ Once per Logos project
 
 <div class="absolute right-30px bottom-30px">
 	<SlideCurrentNo /> / <SlidesTotal />