[files] change to kebab case (#103)

* preview * filenames with underscores * filename case * rename * landing * index * kebab case wins * update docs on case * update titles and some text in programs * patch
0LNetworkCommunity · Aug 1, 2024 · a5ef8f5 · a5ef8f5
1 parent 18d9b65
commit a5ef8f5
Show file tree

Hide file tree

Showing 81 changed files with 49 additions and 57 deletions.
diff --git a/docs/about/engineering_strategy.todo → docs/about/engineering-strategy.todo b/docs/about/engineering_strategy.todo → docs/about/engineering-strategy.todo
diff --git a/docs/about/getting_started.todo → docs/about/getting-started.todo b/docs/about/getting_started.todo → docs/about/getting-started.todo
diff --git a/docs/about/historical_tech_stack.todo → docs/about/historical-tech-stack.todo b/docs/about/historical_tech_stack.todo → docs/about/historical-tech-stack.todo
diff --git a/...announcements/news/carpe_beta_launched.md → ...announcements/news/carpe-beta-launched.md b/...announcements/news/carpe_beta_launched.md → ...announcements/news/carpe-beta-launched.md
diff --git a/...uncements/news/carpe_goes_multilingual.md → ...uncements/news/carpe-goes-multilingual.md b/...uncements/news/carpe_goes_multilingual.md → ...uncements/news/carpe-goes-multilingual.md
diff --git a/...ncements/news/new_milestones_for_carpe.md → ...ncements/news/new-milestones-for-carpe.md b/...ncements/news/new_milestones_for_carpe.md → ...ncements/news/new-milestones-for-carpe.md
diff --git a/...rchive/announcements/news/press_mysten.md → ...rchive/announcements/news/press-mysten.md b/...rchive/announcements/news/press_mysten.md → ...rchive/announcements/news/press-mysten.md
diff --git a/...fing_the_economics_of_blockchains_pt_3.md → ...fing-the-economics-of-blockchains-pt-3.md b/...fing_the_economics_of_blockchains_pt_3.md → ...fing-the-economics-of-blockchains-pt-3.md
diff --git a/..._the_economics_of_blockchains_pts_1__2.md → ...-the-economics-of-blockchains-pts-1--2.md b/..._the_economics_of_blockchains_pts_1__2.md → ...-the-economics-of-blockchains-pts-1--2.md
diff --git a/docs/archive/canonical/libra_liberated.md → docs/archive/canonical/libra-liberated.md b/docs/archive/canonical/libra_liberated.md → docs/archive/canonical/libra-liberated.md
diff --git a/.../canonical/technical/delay_towers_pt_0.md → .../canonical/technical/delay-towers-pt-0.md b/.../canonical/technical/delay_towers_pt_0.md → .../canonical/technical/delay-towers-pt-0.md
diff --git a/.../canonical/technical/delay_towers_pt_1.md → .../canonical/technical/delay-towers-pt-1.md b/.../canonical/technical/delay_towers_pt_1.md → .../canonical/technical/delay-towers-pt-1.md
diff --git a/.../canonical/technical/delay_towers_pt_2.md → .../canonical/technical/delay-towers-pt-2.md b/.../canonical/technical/delay_towers_pt_2.md → .../canonical/technical/delay-towers-pt-2.md
diff --git a/...elay_towers_pt_3_implementation_on_bft.md → ...elay-towers-pt-3-implementation-on-bft.md b/...elay_towers_pt_3_implementation_on_bft.md → ...elay-towers-pt-3-implementation-on-bft.md
diff --git a/...anonical/technical/proof_of_fee_part_1.md → ...anonical/technical/proof-of-fee-part-1.md b/...anonical/technical/proof_of_fee_part_1.md → ...anonical/technical/proof-of-fee-part-1.md
diff --git a/...anonical/technical/proof_of_fee_part_2.md → ...anonical/technical/proof-of-fee-part-2.md b/...anonical/technical/proof_of_fee_part_2.md → ...anonical/technical/proof-of-fee-part-2.md
diff --git a/...missioned_blockchain_with_delay_towers.md → ...missioned-blockchain-with-delay-towers.md b/...missioned_blockchain_with_delay_towers.md → ...missioned-blockchain-with-delay-towers.md
diff --git a/...archive/community/community_programs.todo → ...archive/community/community-programs.todo b/...archive/community/community_programs.todo → ...archive/community/community-programs.todo
diff --git a/docs/archive/community/hustle_karma.todo → docs/archive/community/hustle-karma.todo b/docs/archive/community/hustle_karma.todo → docs/archive/community/hustle-karma.todo
diff --git a/...on/a_brief_overview_of_system_policies.md → ...on/a-brief-overview-of-system-policies.md b/...on/a_brief_overview_of_system_policies.md → ...on/a-brief-overview-of-system-policies.md
diff --git a/docs/archive/econ/the_rulebook_at_genesis.md → docs/archive/econ/the-rulebook-at-genesis.md b/docs/archive/econ/the_rulebook_at_genesis.md → docs/archive/econ/the-rulebook-at-genesis.md
diff --git a/...roposals/october_2022_governance_recap.md → ...roposals/october-2022-governance-recap.md b/...roposals/october_2022_governance_recap.md → ...roposals/october-2022-governance-recap.md
diff --git a/...proposals/proposal_2210_1_final_supply.md → ...proposals/proposal-2210-1-final-supply.md b/...proposals/proposal_2210_1_final_supply.md → ...proposals/proposal-2210-1-final-supply.md
diff --git a/...proposals/proposal_2210_2_proof_of_fee.md → ...proposals/proposal-2210-2-proof-of-fee.md b/...proposals/proposal_2210_2_proof_of_fee.md → ...proposals/proposal-2210-2-proof-of-fee.md
diff --git a/...oposals/proposal_2210_3_musical_chairs.md → ...oposals/proposal-2210-3-musical-chairs.md b/...oposals/proposal_2210_3_musical_chairs.md → ...oposals/proposal-2210-3-musical-chairs.md
diff --git a/...posals/proposal_2210_4_repurpose_carpe.md → ...posals/proposal-2210-4-repurpose-carpe.md b/...posals/proposal_2210_4_repurpose_carpe.md → ...posals/proposal-2210-4-repurpose-carpe.md
diff --git a/...osal_2210_5_revenue_binding_primitives.md → ...osal-2210-5-revenue-binding-primitives.md b/...osal_2210_5_revenue_binding_primitives.md → ...osal-2210-5-revenue-binding-primitives.md
diff --git a/...ls/proposal_2210_6_faucets_for_workers.md → ...ls/proposal-2210-6-faucets-for-workers.md b/...ls/proposal_2210_6_faucets_for_workers.md → ...ls/proposal-2210-6-faucets-for-workers.md
diff --git a/...210_7_donor_directed_community_wallets.md → ...210-7-donor-directed-community-wallets.md b/...210_7_donor_directed_community_wallets.md → ...210-7-donor-directed-community-wallets.md
diff --git a/...l_2210_8_infrastructure_escrow_funding.md → ...l-2210-8-infrastructure-escrow-funding.md b/...l_2210_8_infrastructure_escrow_funding.md → ...l-2210-8-infrastructure-escrow-funding.md
diff --git a/...hive/proposals/scorpions_claw_proposal.md → ...hive/proposals/scorpions-claw-proposal.md b/...hive/proposals/scorpions_claw_proposal.md → ...hive/proposals/scorpions-claw-proposal.md
diff --git a/docs/archive/proposals/spring_forward .md → docs/archive/proposals/spring-forward .md b/docs/archive/proposals/spring_forward .md → docs/archive/proposals/spring-forward .md
diff --git a/.../proposals/team_arctika_recommendation.md → .../proposals/team-arctika-recommendation.md b/.../proposals/team_arctika_recommendation.md → .../proposals/team-arctika-recommendation.md
diff --git a/.../proposals/the_0l_network_constitution.md → .../proposals/the-0l-network-constitution.md b/.../proposals/the_0l_network_constitution.md → .../proposals/the-0l-network-constitution.md
diff --git a/docs/archive/technolgy/carpe_desktop_app.md → docs/archive/technology/carpe-desktop-app.md b/docs/archive/technolgy/carpe_desktop_app.md → docs/archive/technology/carpe-desktop-app.md
diff --git a/.../archive/technolgy/developer_resources.md → ...archive/technology/developer-resources.md b/.../archive/technolgy/developer_resources.md → ...archive/technology/developer-resources.md
diff --git a/docs/archive/technolgy/technology.md → docs/archive/technology/technology.md b/docs/archive/technolgy/technology.md → docs/archive/technology/technology.md
diff --git a/docs/cli-tools/archived/tower_archived.todo → docs/cli-tools/archived/tower-archived.todo b/docs/cli-tools/archived/tower_archived.todo → docs/cli-tools/archived/tower-archived.todo
diff --git a/...ools/archived/use_tower_cli_archived.todo → ...ools/archived/use-tower-cli-archived.todo b/...ools/archived/use_tower_cli_archived.todo → ...ools/archived/use-tower-cli-archived.todo
diff --git a/docs/cli-tools/first_steps.todo → docs/cli-tools/first-steps.todo b/docs/cli-tools/first_steps.todo → docs/cli-tools/first-steps.todo
diff --git a/docs/cli-tools/getting_started.todo → docs/cli-tools/getting-started.todo b/docs/cli-tools/getting_started.todo → docs/cli-tools/getting-started.todo
diff --git a/docs/cli-tools/query/getting_started.todo → docs/cli-tools/query/getting-started.todo b/docs/cli-tools/query/getting_started.todo → docs/cli-tools/query/getting-started.todo
diff --git a/docs/cli-tools/query/val_config.todo → docs/cli-tools/query/val-config.todo b/docs/cli-tools/query/val_config.todo → docs/cli-tools/query/val-config.todo
diff --git a/docs/cli-tools/txs/_category_.json → docs/cli-tools/txs/-category-.json b/docs/cli-tools/txs/_category_.json → docs/cli-tools/txs/-category-.json
diff --git a/docs/cli-tools/txs/generate_transaction.todo → docs/cli-tools/txs/generate-transaction.todo b/docs/cli-tools/txs/generate_transaction.todo → docs/cli-tools/txs/generate-transaction.todo
diff --git a/docs/community programs/moonshot_program.md b/docs/community programs/moonshot_program.md
diff --git a/docs/community programs/_category_.json → docs/community-programs/_category_.json b/docs/community programs/_category_.json → docs/community-programs/_category_.json
diff --git a/docs/community programs/a_good_list.md → docs/community-programs/a-good-list.md b/docs/community programs/a_good_list.md → docs/community-programs/a-good-list.md
@@ -1,4 +1,6 @@
-<h1>A Good List</h1> source: [https://github.com/0LNetworkCommunity/a-good-list/edit/main/README.md](https://github.com/0LNetworkCommunity/a-good-list/edit/main/README.md)
+# A Good List
+
+source: [https://github.com/0LNetworkCommunity/a-good-list/edit/main/README.md](https://github.com/0LNetworkCommunity/a-good-list/edit/main/README.md)
 
 <h2>What</h2>
 

diff --git a/.../community programs/application_studio.md → .../community-programs/application-studio.md b/.../community programs/application_studio.md → .../community-programs/application-studio.md
@@ -1,8 +1,8 @@
+# Newlab Application Studio Program
 Newlab (newlab.com) as a platform strives to pair frontier technology with real-world challenges and partners. Our multidisciplinary community and mothership at the Brooklyn Navy Yard is made up of over 750 members and 160 companies. We are a high-performing community of inventors, engineers, scientists and entrepreneurs reimagining 21st century infrastructure. Newlab has extensive experience pairing frontier technology with legacy industries and cities, investing in early-stage ventures, identifying winning teams as well as directly contributing to the growth of new I.P. and companies from the ground up.
 
 In addition to being a member of the 0L community and early miner, Newlab is starting a program to back teams that have clearly defined plans to leverage 0L for applications with real-world, measurable impact and utility (the “0L Application Studio”). Newlab is excited to serve as a platform to foster these real-world applications of 0L and help these efforts partner with industry to transform or leapfrog existing legacy infrastructure.
 
 If you would like to support this program, your contributions are welcome at: **bc25f79fef8a981be4636ac1a2d6f587**.
 
 Donations will be used to fund awards of the program, as determined by Newlab’s team in partnership with the 0L community. Newlab intends to be proactively involved in helping studio partners realize applications that have utility, impact and scale. In order to cover administrative costs, Newlab will collect 10% of the funds received.
-
diff --git a/...ams/danish_red_cross_humanitarian_fund.md → ...ams/danish-red-cross-humanitarian-fund.md b/...ams/danish_red_cross_humanitarian_fund.md → ...ams/danish-red-cross-humanitarian-fund.md
@@ -1,9 +1,6 @@
-
+# Danish Red Cross Humanitarian
 ## Introduction
 
-
-
-
 The Danish Red Cross (DRC) has existed under the Red Cross Mandate since 1876\. In Denmark, 34,000 volunteers are engaged in supporting the Red Cross vision. Currently, DRC has long-term partnerships in 30 countries and deploys US$200M on international activities, annually. It acts before, during and after disasters and health emergencies to meet the needs and improve the lives of vulnerable people. It does so with impartiality as to nationality, race, gender, religious beliefs, class, and political opinions. Under the auspices of Red Cross humanitarian principles, the DRC will administer the Humanitarian Digital Transformation and Systems Change Fund (the Fund) which aims to improve outcomes for communities affected by humanitarian crises by identifying, testing, and cultivating more effective and scalable technology and data enabled solutions.
 
 

diff --git a/...ams/deep_technology_innovation_program.md → ...ams/deep-technology-innovation-program.md b/...ams/deep_technology_innovation_program.md → ...ams/deep-technology-innovation-program.md
@@ -1,4 +1,4 @@
-
+# Blockscience Deep Technology Innovation Program
 BlockScience Inc is an engineering research and development firm, which has been operating in and around the distributing computing field since 2017\. BlockScience has collaborated with a wide range of industry and academic researchers on a variety of topics, including but not limited to mechanism design, distributed computing, collective intelligence and the social implications of algorithmic policymaking.
 
 

diff --git a/.../ftw_ongoing_full_time_workers_program.md → .../ftw-ongoing-full-time-workers-program.md b/.../ftw_ongoing_full_time_workers_program.md → .../ftw-ongoing-full-time-workers-program.md
@@ -1,5 +1,5 @@
-
-The iqlusion FTW Program aims to collect ongoing donations, and redistribute those donations to any engineers working full-time on the 0L platform on a monthly basis (collectively the FTW).
+# For The Win (FTW) Impact Program
+The Infinite Game FTW Program aims to collect ongoing donations, and redistribute those donations to any engineers working full-time on the 0L platform on a monthly basis (collectively the FTW).
 
 
 
@@ -112,7 +112,7 @@ Program viability presumes there is strong social consensus that FTW workers are
 
 
 
-Provisionally, the FTEP program is administered by iqlusion inc. Funds sent to this wallet are pass-through; destined to iqlusion for onward distribution in the same month. Futurely, a different entity may administer this program. Iqlusion has no claim nor fee on the funds sent to this address. The community will be notified in customary channels if ownership of the address changes.
+Provisionally, the FTEP program was administered by iqlusion inc. until Q3 2023. Funds sent to this were intended to be pass-through; destined to iqlusion for onward distribution in the same month. Iqlusion has no claim nor fee on the funds sent to this address. Subsequently administration was transferred to Infinite Game LLC.
 
 
 

diff --git a/...mmunity programs/human_rewards_program.md → ...mmunity-programs/human-rewards-program.md b/...mmunity programs/human_rewards_program.md → ...mmunity-programs/human-rewards-program.md
@@ -1,4 +1,4 @@
-
+# TTTS Human Rewards Program
 ## What
 
 
@@ -35,5 +35,3 @@ This account is operated via smart contract. And all outbound transactions will
 
 
 Donations can be sent here: **F605FE7F787551EEA808EE9ACDB98897**
-
-
diff --git a/docs/community-programs/moonshot-program.md b/docs/community-programs/moonshot-program.md
@@ -0,0 +1,30 @@
+# Moonshot Program
+Enceladus LLC is a small software development company involved in blockchain software development, including for 0L network. The company has not raised venture capital nor has any investment partners.
+
+## About
+Inspired by the well-known X-Prize awards, we think large and meaningful rewards are necessary to materialize frontier technologies which are ambitious, speculative, and non-obvious. As such, Enceladus has established “Moonshot Projects”. This program sponsors large rewards for teams with extraordinary background in technology, and a plausible path to deploying said technology in society. We are seeking breakthrough use-cases which depend on yet-unrealized innovations in distributed systems and cryptography. Success for “Moonshots” means producing a jump discontinuity for any industry or any human activity, but not necessarily immediately.
+
+
+
+
+The program principally aims to a) identify opportunities, b) match teams to opportunities, and c) manage an expert-led evaluation process for technical achievements. Financial awards or grants for technical achievements will be contributed from Enceladus proprietary funds.
+
+
+
+
+Donations to Enceladus for the Moonshot Program are accepted at the 0L account: **2057BCFB0189B7FD0ABA7244BA271661**.
+
+
+Donations will be used to fund awards of the program. For professional administration of the resources of the program Enceladus will retain an administrative fee up to 5% of the funds awarded to teams.
+
+
+Enceladus will mark this address as a “CommunityWallet” on chain. By that we mean:
+
+
+* that we will only disburse funds after polling the community.
+* funds will only be transferred to an 0L SlowWallet, which releases funds over time.
+* we allow 2/3 of validators (by voting power) to vote to reject our transactions.
+* if an epoch’s validator set decides to sunset this account (burn values and make inaccessible) for any reason, we will oblige.
+
+# Administration
+Initially the administrator of this program was Liberators of Libra LLC, which ceased operating in Dec 2022.
diff --git a/...c_research_and_experimentation_0l_fund.md → ...c-research-and-experimentation-0l-fund.md b/...c_research_and_experimentation_0l_fund.md → ...c-research-and-experimentation-0l-fund.md
@@ -1,5 +1,5 @@
-
-RadicalxChange Foundation, a 501©3 nonprofit, seeks to build a coherent and sustainable new political economy.
+# RxC Social Research and Experimentation
+RadicalxChange Foundation, a 501c3 nonprofit, seeks to build a coherent and sustainable new political economy.
 
 
 

diff --git a/...programs/social_infrastructure_program.md → ...programs/social-infrastructure-program.md b/...programs/social_infrastructure_program.md → ...programs/social-infrastructure-program.md
@@ -1,4 +1,4 @@
-
+# Blockscience Social Infrastructure Project
 Social infrastructures complement technical infrastructures provided by blockchain networks. This program is designed to provide capital to fund a wide range of benefits to 0L members in alignment with the mission, vision and values of the community.
 
 

diff --git a/...grams/the_iqlusion_engineering_program.md → ...grams/the-iqlusion-engineering-program.md b/...grams/the_iqlusion_engineering_program.md → ...grams/the-iqlusion-engineering-program.md
@@ -1,4 +1,4 @@
-
+# The iqlusion Engineering Program
 Iqlusion intends to supervise the evolution and extension of 0L blockchain from it’s current nascent form into a full feature base layer in the multichain world. We intend to establish a mature engineering program around 0L with design documents, ADR, pull requests and code review to ensure a stable and robust blockchain platform. Of particular interest to us is developing an engineering program to connect 0L to the Internet of Blockchains via support for Ethereum and IBC interoperability.
 
 

diff --git a/docs/community programs/tip_jar.md → docs/community-programs/tip-jar.md b/docs/community programs/tip_jar.md → docs/community-programs/tip-jar.md
@@ -1,4 +1,4 @@
-# TIP JAR
+# Tip Jar
 Source: https://github.com/infinite-game-llc/tip-jar/blob/main/README.md
 
 Core engineering on 0L has been an unfunded volunteer effort. For example, since about June 2019 the lead 0L developer -- github user `0o-de-lally` -- has contributed an estimated 5,060 man-hours exclusively to core protocol (last updated Sept 24th 2021). This effort was not compensated in any form.

diff --git a/...ty programs/university_of_toronto_msrg.md → ...ty-programs/university-of-toronto-msrg.md b/...ty programs/university_of_toronto_msrg.md → ...ty-programs/university-of-toronto-msrg.md
@@ -1,4 +1,4 @@
-
+# University of Toronto MSRG Lab
 D is for Donations
 
 

diff --git a/...unity programs/working_group_key_roles.md → ...unity-programs/working-group-key-roles.md b/...unity programs/working_group_key_roles.md → ...unity-programs/working-group-key-roles.md
diff --git a/docs/core-devs/dev_quick_start.todo → docs/core-devs/dev-quick-start.todo b/docs/core-devs/dev_quick_start.todo → docs/core-devs/dev-quick-start.todo
diff --git a/docs/core-devs/formal_verification.todo → docs/core-devs/formal-verification.todo b/docs/core-devs/formal_verification.todo → docs/core-devs/formal-verification.todo
diff --git a/docs/core-devs/governance_fixtures.todo → docs/core-devs/governance-fixtures.todo b/docs/core-devs/governance_fixtures.todo → docs/core-devs/governance-fixtures.todo
diff --git a/docs/core-devs/move_coding_conventions.todo → docs/core-devs/move-coding-conventions.todo b/docs/core-devs/move_coding_conventions.todo → docs/core-devs/move-coding-conventions.todo
diff --git a/docs/core-devs/move_data_initialization.md → docs/core-devs/move-data-initialization.md b/docs/core-devs/move_data_initialization.md → docs/core-devs/move-data-initialization.md
diff --git a/docs/core-devs/smoke_tests.todo → docs/core-devs/smoke-tests.todo b/docs/core-devs/smoke_tests.todo → docs/core-devs/smoke-tests.todo
diff --git a/docs/core-devs/testnet_deploy.todo → docs/core-devs/testnet-deploy.todo b/docs/core-devs/testnet_deploy.todo → docs/core-devs/testnet-deploy.todo
diff --git a/docs/edit-docs/editing.md b/docs/edit-docs/editing.md
@@ -21,10 +21,10 @@
 ## Conventions
 
 ### Filenames
-filenames are in "snakecase", lowercase, with underscore for spaces. The file extension should always be `.md`.
+filenames are in "kebab case", lowercase, with dash for spaces. The file extension should always be `.md`.
 
 Like this:
- `this_is_a_file.md`
+ `this-is-a-file.md`
 
 ### Metadata
 At the top of an `.md` file you may include some metadata which Docusaurus will be able to read and use for parts of the UX (e.g. titles, is it hidden, menu position).
@@ -46,7 +46,7 @@ You should always have a document that begins with a section title.
 You should not include a `title` field in metadata, instead you should carefully consider the actual header in the document.
 
 ### Menu Labels
-The fallback behavior for menu link names will be the filename, e.g.: `this_is_a_file`.
+The fallback behavior for menu link names will be the filename, e.g.: `this-is-a-file`.
 However if your Doc begins with a header title, e.g.: `# My Article`, then the menu label will be exactly that.
 To override both cases you can include this item to the metadata: `sidebar_label: Actual Label`.
 

diff --git a/docs/misc/communtiy_wallet_activation.md → docs/misc/communtiy-wallet-activation.md b/docs/misc/communtiy_wallet_activation.md → docs/misc/communtiy-wallet-activation.md
diff --git a/docs/misc/genesis_instructions.todo → docs/misc/genesis-instructions.todo b/docs/misc/genesis_instructions.todo → docs/misc/genesis-instructions.todo
diff --git a/docs/misc/hot_upgrades.todo → docs/misc/hot-upgrades.todo b/docs/misc/hot_upgrades.todo → docs/misc/hot-upgrades.todo
diff --git a/docs/misc/key_rotation.todo → docs/misc/key-rotation.todo b/docs/misc/key_rotation.todo → docs/misc/key-rotation.todo
diff --git a/docs/misc/sybil_resistance.todo → docs/misc/sybil-resistance.todo b/docs/misc/sybil_resistance.todo → docs/misc/sybil-resistance.todo
diff --git a/docs/misc/tool_design.todo → docs/misc/tool-design.todo b/docs/misc/tool_design.todo → docs/misc/tool-design.todo
diff --git a/docs/misc/validator_registration.todo → docs/misc/validator-registration.todo b/docs/misc/validator_registration.todo → docs/misc/validator-registration.todo
diff --git a/docs/validators/detailed_instructions.todo → docs/validators/detailed-instructions.todo b/docs/validators/detailed_instructions.todo → docs/validators/detailed-instructions.todo
diff --git a/docs/validators/getting_started.todo → docs/validators/getting-started.todo b/docs/validators/getting_started.todo → docs/validators/getting-started.todo
diff --git a/docs/validators/hot_upgrades.todo → docs/validators/hot-upgrades.todo b/docs/validators/hot_upgrades.todo → docs/validators/hot-upgrades.todo
diff --git a/docs/validators/validator_quickstart.todo → docs/validators/validator-quickstart.todo b/docs/validators/validator_quickstart.todo → docs/validators/validator-quickstart.todo
diff --git a/docs/validators/vfn_setup.todo → docs/validators/vfn-setup.todo b/docs/validators/vfn_setup.todo → docs/validators/vfn-setup.todo
diff --git a/docs/validators/with_docker_setup.todo → docs/validators/with-docker-setup.todo b/docs/validators/with_docker_setup.todo → docs/validators/with-docker-setup.todo