diff --git a/gf-guide/article.md b/gf-guide/article.md
index 46196a1..991f60b 100644
--- a/gf-guide/article.md
+++ b/gf-guide/article.md
@@ -2,14 +2,14 @@
-# Article and Description files
+# The Article file
{:.no_toc}
-🦉 Both the ARTICLE.en_us.html and DESCRIPTION.en_us.html files are used to bring the information that appears in the #About section on any specimen page of Google Fonts to provide further information about the font family.
+🦉 The ARTICLE.en_us.html file provides the information that appears in the #About section of any specimen page on Google Fonts, giving readers further details about the font family.
-The team member onboarding the font will create any of these files. Thus, the actual file a designer should write carefully is the README.md file of the font's repository, as the information in it will be crucial to create a descriptive #About section.
+The team member onboarding the font creates this file. The file a designer should write carefully is the README.md file of the font's repository, as the information in it is crucial to building a descriptive #About section.
@@ -25,40 +25,42 @@ The team member onboarding the font will create any of these files. Thus, the ac
## The Article
-The Article file is a new expanded version of the `DESCRIPTION.en_us.html` file that includes images and longer-form information and content. It appears on the Google Fonts site as the main content in the About & License section. For example, see the About page of [Playpen Sans](https://fonts.google.com/specimen/Playpen+Sans/about), and then view the `ofl/playpensans` directory in the Google Fonts repo: [github.com/google/fonts/tree/main/ofl/playpensans](https://github.com/google/fonts/tree/main/ofl/playpensans).
+The Article file includes images and longer-form information and content. It appears on the Google Fonts site as the main content in the About & License section. For example, see the About page of [Playpen Sans](https://fonts.google.com/specimen/Playpen+Sans/about), and then view the `ofl/playpensans` directory in the Google Fonts repo: [github.com/google/fonts/tree/main/ofl/playpensans](https://github.com/google/fonts/tree/main/ofl/playpensans).
-The `ARTICLE.en_us.html` file and images should live in an `article/` directory alongside the `METADATA.pb` file in the root of the `ofl/fontname` directory. Typically, only the Noto fonts are expected to combine the `DESCRIPTION.en_us.html` and `ARTICLE.en_us.html` files. For all the other families (non-Noto), if an article with images is added, the description should be overwritten by the Article. This means that, in the case of adding expanded content and images, we should shift all the Description content to the Article and delete the `DESCRIPTION.en_us.html`.
+The `ARTICLE.en_us.html` file and its images should live in an `article/` directory alongside the `METADATA.pb` file in the root of the `ofl/fontname` directory.
+
+Every family now uses an `ARTICLE.en_us.html` file, even when it contains no images. (The legacy `DESCRIPTION.en_us.html` file has been retired: all of the About content now lives in the Article.)
Here are some guidelines for how to prepare the `article/` directory and files:
### Requirements
-- **Pay attention to the content.** Feel free to write a comprehensive text that will pay tribute to your project. Here are added examples of 'About' sections on Google Fonts. Ojuju and Roboto Flex.
-- **Should be written in the third person.**
+- **Pay attention to the content.** Feel free to write a comprehensive text that pays tribute to your project. Here are some examples of 'About' sections on Google Fonts: Ojuju and Roboto Flex.
+- **It should be written in the third person.**
- **Copywriting should not be inappropriate, stereotypical, or offensive.** For example, "This family demonstrates a feminine energy with its fragile aspect" is unacceptable.
-- **The text length** should be around 500 words, and more than 100 characters.
-- **If the font is derived from another font,** it should mention the original with a URL to the font on GF if it exists.
-- **All links in it must be properly working.**
-- **Should not contain biography information.** This bio info should go in the [designer's credits](./profile). We accept credits if they are not mentioned in the credit section (for example, help on development, specific names of people involved if only a collective name is credited, etc.).
-- **It must include a hypertext link to the upstream repository.** That is the designer’s GitHub repository. This line of text usually goes at the end of the first paragraph, before the line that separates it from the added text when the article has a long text.
+- **The text length** should be around 500 words, and no fewer than 100 characters.
+- **If the font is derived from another font,** it should mention the original with a URL to the font on Google Fonts if it exists.
+- **All links in it must work properly.**
+- **It should not contain biography information.** Bio info should go in the [designer's credits](./profile). We accept credits if they are not already mentioned in the credits section (for example, help with development, or the specific names of people involved when only a collective name is credited).
+- **It must include a hypertext link to the upstream repository** — that is, the designer's GitHub repository. This line of text usually goes at the end of the first paragraph, before the line that separates it from the added text when the article is long.
-You can copy/paste the following line (don’t forget to adjust the URL):
+You can copy and paste the following line (don't forget to adjust the URL):
``` code
- To contribute, see github.com/owner/fontname
+ To contribute, see github.com/owner/fontname
```
-- **The text should be updated when the font is upgraded** to let people know what changed.
+- **The text should be updated when the font is upgraded,** to let people know what changed.
Example:
> This font was upgraded in July 2021 to expand its language coverage. It now supports Greek and Cyrillic.
-- **We only accept** **`.en_us`** **extension**, but you can definitely add a translation to the description when the font primarily targets an audience reading a non-Latin script.
-- If the primary script of your font is not Latin, we strongly recommend you also provide a translation of the text using the actual main script. **This localized text must be in the same HTML snippet as the English text.**
+- **We only accept the** **`.en_us`** **extension,** but you can add a translation to the text when the font primarily targets an audience reading a non-Latin script.
+- If the primary script of your font is not Latin, we strongly recommend that you also provide a translation of the text using the actual main script. **This localized text must be in the same HTML snippet as the English text.**
### Format text with the font family
-You may format text with the font family by using HTML span tags with the `"autonym"` class. This should not be used to style the entire document. Use it sparingly to document available features in the font family. For example, to style the text "THIS TEXT" with the font family, enter HTML like this:
+You may format text with the font family by using HTML span tags with the `"autonym"` class. This should not be used to style the entire document; use it sparingly to document available features in the font family. For example, to style the text "THIS TEXT" with the font family, enter HTML like this:
```html
THIS TEXT
@@ -66,58 +68,60 @@ You may format text with the font family by using HTML span tags with the `"auto
### Images
-Please refer to the [Promote your font](./promotion.md) section of this Guide for fully detailed information on these images. The following summarizes the main specifications for the required images.
+The Article file supports images, which must live in the `article/` directory alongside `ARTICLE.en_us.html`. For the full image specifications — formats, file sizes, resolution, and social media requirements — see the [Promote your font](./promotion.md) section of this Guide. In summary:
-- Supported image formats: JPG, PNG, SVG, but there is a strong preference for JPG/SVG. JPEGs are optimized so that lower resolution images will be downloaded on smaller viewport sizes.
-- Max image size for SVG is 800 KB; for other formats, it is 1.75 MB (enforced by knowledge_graph.py GitHub workflow)
-The recommended width is at least 1000px. You don't need any particular proportions; the container will resize the image.
+- Supported formats: JPG, PNG and SVG, with a strong preference for JPG/SVG. JPEGs are optimized so that lower-resolution images are downloaded on smaller viewport sizes.
+- Recommended width: at least 1000px. You don't need any particular proportions; the container will resize the image.
- Resolution: 72dpi.
+- Maximum file size: 800 KB for SVG; 1.75 MB for other formats (enforced by the `knowledge_graph.py` GitHub workflow).
+- Maximum resolution allowed: 1024 px (height) × 2048 px (width). Feel free to choose the ratio you want!
+
+The images in this repository are licensed under the CC https://creativecommons.org/licenses/by-sa/4.0/. This license mention must be present in the repository, inside the `documentation` folder (see [Promote your font](./promotion.md) for details).
+
+
+
#### Videos
-There are two options to include videos in the Article file: `MP4` with a max file size of 1.4 MB; and a `YouTube` link.
+There are two options for including videos in the Article file: an `MP4` with a maximum file size of 1.4 MB, or a `YouTube` link.
-- For the `MP4` video inclusion, it must follow this format:
+- For an `MP4` video, it must follow this format:
``
-or, if you need to loop it:
-
+ or, if you need to loop it:
+
``````
- You can see these cases as reference: Danfo, Savate
-
+ You can use these cases as reference: Danfo, Savate
-- For the `YouTube` link, this option requires a cover image to display as preview, and must follow the following format:
+- The `YouTube` link option requires a cover image to display as a preview, and must follow this format:
- ``
-
- `