docs: improve fragment names section phrasing

Remove 'accidentally' - the warning is about intentional reuse,
and 'graphql-tag' is an implementation detail that users don't
need to know about.

Author: atharv-sys32

docs/source/data/fragments.mdx

@@ -43,15 +43,15 @@ Changes to the `NameParts` fragment automatically update the fields included in
 
 ## Unique fragment names {#unique-names}
 
-Fragment names must be unique across your entire application. If you accidentally reuse a fragment name, `graphql-tag` warns you about the conflict at runtime to prevent subtle bugs:
+Fragment names must be unique across your entire application. If you reuse a fragment name, the `graphql-tag` component will warn about the conflict at runtime to prevent subtle bugs:
 
 ```text
 Warning: fragment with name SomeFragment already exists.
 graphql-tag enforces all fragment names across your application to be unique; read more about
 this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names
 ```
 
-Always use descriptive, component-scoped fragment names (like `ItemFragment` or `UserProfileFragment`) to avoid accidental name collisions.
+Always use descriptive, component-scoped fragment names (like `ItemFragment` or `UserProfileFragment`) to avoid name collisions.
 
 ## Example usage