@@ -106,49 +106,49 @@ of a few ways:
106106
1071071 . ` SoftwareVersion ` component
108108
109- This component is used to embed the current version of the software into the documentation. An example of this would be:
109+ This component is used to embed the current version of the software into the documentation. An example of this would be:
110110
111- ``` jsx
112- < SoftwareVersion versionType= {" maj-min-pat" }/ > // e.g. 1.19.2
113- < SoftwareVersion versionType= {" maj-min" }/ > // e.g. 1.19
114- < SoftwareVersion versionType= {" maj" }/ > // e.g. 1
111+ ``` jsx
112+ < SoftwareVersion versionType= {" maj-min-pat" }/ > // e.g. 1.19.2
113+ < SoftwareVersion versionType= {" maj-min" }/ > // e.g. 1.19
114+ < SoftwareVersion versionType= {" maj" }/ > // e.g. 1
115115
116- // You can set the project name to be used for the versioning (defaults to paper):
117- < SoftwareVersion versionType= {" maj-min-pat" } project= {" velocity" }/ > // e.g. 3.3.0-SNAPSHOT
118- ```
116+ // You can set the project name to be used for the versioning (defaults to paper):
117+ < SoftwareVersion versionType= {" maj-min-pat" } project= {" velocity" }/ > // e.g. 3.3.0-SNAPSHOT
118+ ```
119119
1201202. ` Javadoc` component
121121
122- This component is used to embed a link to the current version of the corresponding Javadoc. An example of this would be:
122+ This component is used to embed a link to the current version of the corresponding Javadoc . An example of this would be:
123123
124- ``` jsx
125- < Javadoc name= {" org.bukkit.event.Event" }> here< / Javadoc>
126- // The project can also be set here, and defaults to Paper
127- ```
124+ ` ` ` jsx
125+ <Javadoc name={"org.bukkit.event.Event"}>here</Javadoc>
126+ // The project can also be set here, and defaults to Paper
127+ ` ` `
128128
1291293. ` VersionFormattedCode` component
130130
131- This component is used to embed a code block with the current version of the software. An example of this would be:
132-
133- ```` jsx
134- < VersionFormattedCode language= {" yaml" }>
135- ` ` ` ⠀
136- name: Paper-Test-Plugin
137- version: '1.0'
138- main: io.papermc.testplugin.TestPlugin
139- description: Paper Test Plugin
140- api-version: '%%_MAJ_MIN_PAT_MC_%%'
141- bootstrapper: io.papermc.testplugin.TestPluginBootstrap
142- loader: io.papermc.testplugin.TestPluginLoader
143- ` ` ` ⠀
144- < / VersionFormattedCode>
145-
146- // The possible placeholders are:
147- %% _MAJ_MIN_MC_ %% - Major- Minor Paper Version (E .g . 1 .20 )
148- %% _MAJ_MIN_PAT_MC_ %% - Major- Minor- Patch Paper Version (E .g . 1 .20 .4 )
149- %% _MAJ_MIN_VEL_ %% - Major Velocity Version (E .g . 3 .1 .0 )
150- %% _MAJ_MIN_PAT_VEL_ %% - Major- Minor- Patch Velocity Version (E .g . 3 .1 .1 - SNAPSHOT )
151- ````
131+ This component is used to embed a code block with the current version of the software . An example of this would be:
132+
133+ ` ` ` ` jsx
134+ < VersionFormattedCode language= {" yaml" }>
135+ ` ` ` ⠀
136+ name: Paper-Test-Plugin
137+ version: '1.0'
138+ main: io.papermc.testplugin.TestPlugin
139+ description: Paper Test Plugin
140+ api-version: '%%_MAJ_MIN_PAT_MC_%%'
141+ bootstrapper: io.papermc.testplugin.TestPluginBootstrap
142+ loader: io.papermc.testplugin.TestPluginLoader
143+ ` ` ` ⠀
144+ < / VersionFormattedCode>
145+
146+ // The possible placeholders are:
147+ %% _MAJ_MIN_MC_ %% - Major- Minor Paper Version (E .g . 1 .20 )
148+ %% _MAJ_MIN_PAT_MC_ %% - Major- Minor- Patch Paper Version (E .g . 1 .20 .4 )
149+ %% _MAJ_MIN_VEL_ %% - Major Velocity Version (E .g . 3 .1 .0 )
150+ %% _MAJ_MIN_PAT_VEL_ %% - Major- Minor- Patch Velocity Version (E .g . 3 .1 .1 - SNAPSHOT )
151+ ````
152152
153153When the major version of the software changes, the docs will still need to have a " snapshot" created to keep documentation
154154for older versions . This is done by using Docusaurus' s `version` command:
0 commit comments